SNMP plugin warn/critical range issues?

[Karl DeBisschop]

Shayne Lebrun writes: 

> Ok, the SNMP plugin seems to assume that higher values is better. 
> 
> To elaborate: I'm checking signal strength on some wireless radios.  0-25
> would be critical, 26-35 would be warning, and 36+ would be all systems go. 
> 
> ./check_snmp -H 111.222.111.222 -o .1.3.6.1.4.1.762.2.5.2.1.7.1
> SNMP OK - 72 
> 
> Fine. 
> 
> ./check_snmp -H 111.222.111.222 -o .1.3.6.1.4.1.762.2.5.2.1.7.1 -w 26:35 -c
> 0:25
> SNMP CRITICAL - *72* 
> 
> 
> Now, 72 isn't between 26 and 35, and it isn't between 0 and 25.  Am I
> misinterpreting the help file, or am I just insane? :-)

You specify the range that is OK. Thus: 

check_snmp -w 36: -c 26: 

(from --help: 

 - Ranges are inclusive and are indicated with colons. When specified as
 'min:max' STATE_OK will be returned if the result is within the indicated
 range or is equal to the upper or lower bound. A non-OK state will be
 returned if the result is outside the specified range.
) 

In another email, you ask about negative values. That requires a code 
change. We're trying to get a release out, I'm on the fence, but I'll call 
that a bug and fix it, unless others feel it's a feature request. 


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com