On 17/10/06, Ravi S M <[EMAIL PROTECTED]> wrote:
> I am getting traps when my monitored process goes down, but when it comes up
> the traps are not generated. My "snmpd.conf" looks like this

> monitor ..... "Process named" prErrorFlag.1 != 0

That is correct.
This monitor line will trigger (and generate a trap) when the
condition is matched,
i.e. the prErrorFlag goes from 0 to non-0.

When the condition is cleared (goes from non-0 to 0), then this
re-arms the trigger so it's ready to fire again.  But it does *not*
"reverse-fire" the trigger, to generate another trap.

The easiest way to do this would probably be to have a parallel
monitor line, with the same test in reverse:

    monitor -u myuser -r 10 -i -o prNames.1 -o prErrMessage.1 "Process named OK"
        prErrorFlag.1 == 0


Also note that if you're using the 5.3.x line (or the upcoming 5.4
code), you can use a single "monitor" line to handle *all* your "proc"
entries:

monitor -u myuser -r 10 -o prNames -o prErrMessage "Processes"
prErrorFlag  !=  0

You don't have to have a separate monitor line for each "proc" entry.
This didn't work reliably in the earlier releases, but does with 5.3 and above.

Dave

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to