using monitor to trap (extend vs proxy)

Greg Oliver <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <1326337154.15369.10.camel@ghost>
I've been banging my head most of the day trying to make something work.
I'm trying to use the monitor feature to trap (resulting in email) to
notify me when another process's snmp engine is not responding.  

I have a mix of java jvms and regular system tasks to monitor.  The
system tasks are trivial, but since java only shows "java" in the proc
table, I am using the jvm's built-in snmp server to query health.  This
all works dandy.

I have "extend"ed the enterprise mib with shell scripts that walk the
JVM servers (all one machine, several different ports), and that is
successful.

I have also "proxy"ed them to the jvm's snmp monitors, and that works as
well (quite a bit cleaner too)..

I have an issue with each, and I know I'm trying to take the easy way
out, but here are my issues:

The extend method returns the get as a string of the original walk
command, so I can do no compares.  Both methods do not trap if the
remote snmp is unavailable (main issue).  So, if the jvm is up and
running, everything is a-ok.  If it is not, the monitor does not fail,
just says:

disman:event:trigger:monitor: Running trigger (TEST)
proxy: proxy handler starting, mode = 160
proxy: length=16, base_len=2, name_len=2
proxy: sending pdu
proxy: got timed out... requests = 0x908c858
proxy:   ignoring timeout
disman:event:trigger:monitor: Trigger query (get) failed: 5
failed to run mteTrigger query

Successful:

disman:event:trigger:monitor: Running trigger (TEST)
proxy: proxy handler starting, mode = 160
proxy: length=16, base_len=2, name_len=2
proxy: sending pdu
proxy: got response... JVM-MANAGEMENT-MIB::jvmOSProcessorCount.0

Is there any way to make it trap on this failure?

relevant portions snmpd.conf included for proxy test since that solution
seems much cleaner.  I will have several lines (1 for each jvm when
completed) if I can somehow get the trap to fire when the monitor fails
to get any results from the proxied connection.

proxy -v 2c -c public 127.0.0.1:9089 .1.4 .1.3

monitor -r 20 -S -I TEST ! .1.4.6.1.4.1.42.2.145.3.163.1.1.6.4.0 

Thanks!


------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.