Always a WARNING state from check_snmp

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Marco Borsani
> Sent: Wednesday, September 07, 2005 8:41 AM
> To: NAGIOS
> Subject: [Nagios-users] Always a WARNING state from check_snmp
> Importance: High
> 
> 
> Hi all!
> 
> I am testing check_snmp on a Cisco FW.
> All it seems to be OK when I checking Memory or Connections, but when
I
> checking CPU (for istance cpmCPUTotal5sec) I always receive a WARNING
> state.
> 
> You can see (in the follwing line command) that I don't mention any
> warning/critial range (!)
> 
> #> ./check_snmp -H HOSTADDRESS -o .1.3.6.1.4.1.9.9.109.1.1.1.1.3.1 -C
> public
> #> SNMP WARNING - 9

Since SNMP data can be anything, and it doesn't have any idea what
you're checking based on the OID, how is the plugin supposed to know
whether that result is good or not unless you provide warning and
critical ranges? IMHO the plugin behavior is appropriate in this case.

As for it working for your memory test, there are generic default values
defined in check_snmp.c (powers of 2) that your memory and connection
tests apparently fall within.

--
Marc


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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