[Nagiosplug-help] check_snmp always "warning"

[Mike Feetham]

Charles,

I haven't had a coffee yet this morning, but doesn't "-w 0:1000" mean
trigger a warning for any value between 0 and 1000?


-----Original Message-----
From: nagiosplug-help-admin at lists.sourceforge.net
[mailto:nagiosplug-help-admin at lists.sourceforge.net] On Behalf Of Charles
Sprickman
Sent: Monday, September 27, 2004 3:52 PM
To: nagiosplug-help at lists.sourceforge.net
Subject: [Nagiosplug-help] check_snmp always "warning"

Hi,

Running nagios + nagios-plugins 1.3.1 and I'm trying to make a simple load 
average snmp check using "check_snmp".  Reading the destructions, this
should 
work:

root at miko[/usr/local/etc/nagios]# /usr/local/libexec/nagios/check_snmp -H 
spamd1 -o laLoadInt.1 -w 0:1000 -c 0:10000 -C deadbeef

The "-w" and "-c" paramaters are supposed to be a range where things are
marked 
"OK", so a warning level that only triggers outside the range of 0-1000
should 
not return a warning, correct?  But I get the following:

SNMP WARNING - 18

The OID I'm querying is an integer value:

root at miko[/usr/local/etc/nagios]# /usr/local/bin/snmpget -t 1 -r 9 -m ALL -v
1 
-c deadbeef spamd1:161  laLoadInt.1
UCD-SNMP-MIB::laLoadInt.1 = INTEGER: 35

Am I doing something completely wrong or is there a problem in "check_snmp"?

OS is FreeBSD 4.8, plugins built from ports.

Thanks,

Charles

___
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet - www.bway.net
spork at bway.net - 212.655.9344



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Nagiosplug-help mailing list
Nagiosplug-help at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
::: Please include plugins version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null