Check_snmp problems

[Julian Hein]

Hi Bill,				



> I was unable to find a solution to this problem from a search
 of the list.

> 

> When using check_snmp to check cpu usage on a host, I get warnings
 even when

> the retrieved value falls within an acceptable range. Assuming
 that my

> syntax was wrong, I tried multiple variations, but the result
 is the same.

> 

> Does anyone have a solution to this problem?

> 

> monitor-server# ./check_snmp -v -H 192.168.123.156 -o

> .1.3.6.1.2.1.25.3.3.1.2.1 -w 100: -c 90: -C public

> /usr/local/bin/snmpget -t 1 -r 9 -m ALL -v 1 -c public 192.168.123.156:
161

> .1.3.6.1.2.1.25.3.3.1.2.1

> HOST-RESOURCES-MIB::hrProcessorLoad.1 = INTEGER: 1

> SNMP CRITICAL - *1*



This is a flaw with check_snmp and MIBs with incorrect syntax. If
 you use OIDs, you could just disable MIB parsing with "-m :". It
 is also documented in the Nagios FAQ: http://www.nagios.org/faqs/viewfaq
.php?faq_id=208



Julian


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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