Re: Traps and frequency

2008-07-14 Thread José Eduardo Martins
More on my problem. From the manual: monitor [OPTIONS] NAME EXPRESSION (bla, bla, bla). *This monitor entry will not fire again until the monitored condition first becomes false, and then matches again.* (bla, bla, bla). Is there any way to overcome this behaviour? I.e., always fire the monitor, f

RE: Traps and frequency

2008-07-14 Thread Mike Ayers
> From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of José Eduardo Martins > Sent: Monday, July 14, 2008 7:46 AM > monitor [OPTIONS] NAME EXPRESSION > (bla, bla, bla). This monitor entry will not fire again > until the monitored condition first becomes false, and th

Re: Traps and frequency

2008-07-15 Thread José Eduardo Martins
I agree with you completely. But my boss doesn't. :-) I tried to explain him to meaning of synchronous (snmp getnext) and asynchronous (snmp trap or informs) notifications, but they "explained" me that they didn't even needed snmp access to the agent. They had configured the monitor software (open

RE: Traps and frequency

2008-07-15 Thread Mike Ayers
> From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of José Eduardo Martins > Is it right to trust snmp-v2 informs to have a certain degree > of trust that the message was received? Like so: if the inform succeeds, then the notification *was* delivered to the applicati