> 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
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
> 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
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
Hello all.
I have a question of whether the functionality is implemented or
"implementable".
I want to send a TRAP every time, not only when the state of the condition
changes.
E.g.
*snmpd.conf*
sh myScript /usr/local/bin/load.sh one
monitor -r 60 "my monitor on" extResult >= 1
monitor -r 60 "my
