check_snmp giving warnings below warning threshold

[nagios at mm.quex.org]

On Wed, Sep 29, 2004 at 11:02:05AM +0100, Stephen Patterson wrote:

> I'm using check_snmp like this to monitor the CPU on cisco switches
> and routers, it should warn at 60% and critical at 80%, but it
> indicates warning at any value. Can anyone spot any errors with this
> configuration?
> 
> define command {
>         command_name    cisco-cpu
>         command_line    /usr/lib/nagios/plugins/check_snmp -H $HOSTADDRESS$ -m none -C public -o .1.3.6.1.4.1.9.9.109.1.1.1.1.3.1 -w 60 -c 80
>         }
> 
> and from command line: 
> root at zaphod:~$ /usr/lib/nagios/plugins/check_snmp -H 192.168.253.171
> -m none -C public -o .1.3.6.1.4.1.9.9.109.1.1.1.1.3.1 -w 60 -c 80
> SNMP WARNING - 22

check_snmp is a bit strange in that the warning and critical values
are (if you read the output of check_snmp -h) ranges which will NOT
result in a warning/critical status.  This makes some sense as any
unknown/unexpected value will trigger an alert.

So you need to change your settings to something like
 -w 0-60 -c 0-80


-------------------------------------------------------
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