Check_snmp Issue

[Aaron Conaway]

I've checked the archives and online for this problem, but any solution
I have found does not work for me.  My ultimate goal is to just check if
SNMP is running on a box; I could care less what any SNMP value is.  

As you can see below, if I do an snmpget on ifNumber.0, it returns 107.
That's fine and dandy since I don't really care what the value is.  If I
do a check_snmp to the same OID, I get 107, but it is a warning status.
If I set the warning range to 108:, it returns a warning state, but the
value of 107 is between asterisks.  If I set the critical range to 108:,
I get a critical state with the value of 107 between asterisks.

I know just enough SNMP to be dangerous, but I am obviously missing
something basic here.  Can anyone help?

[nagios at palpatine libexec]$ snmpget -c ******** -v 1 ******** ifNumber.0
RFC1213-MIB::ifNumber.0 = INTEGER: 107
[nagios at palpatine libexec]$ ./check_snmp -H ******** -C ******** -o
ifNumber.0
SNMP WARNING - 107
[nagios at palpatine libexec]$ ./check_snmp -H ******** -C ******** -o
ifNumber.0 -w 108:
SNMP WARNING - *107*
[nagios at palpatine libexec]$ ./check_snmp -H ******** -C ******** -o
ifNumber.0 -c 108:
SNMP CRITICAL - *107*
[nagios at palpatine libexec]$ ./check_snmp -V
check_snmp (nagios-plugins 1.3.0) 1.24
[nagios at palpatine libexec]$ ../bin/nagios -V

Nagios 1.0

----------
Aaron Conaway
Network Engineer III
Verisign, Inc. -- Telecom Services Division
http://www.verisign.com
Office:  912.527.4343
Fax:  912.527.4014


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null