Hi all,
I am having an issue with all of the devices I added showing warning all
the time. It is a simple snmp check to see if the amps are above
160warn/180critical. They always say warning even though they are less
than the specified 160. One thing to note is once it hits the 160 mark
it gets the * value * in turn, showing that it is actually in the
warning range. I have shown the neccesary data I hope below. Any/all
help is greatly appreciated.
# uname -a
FreeBSD server.example.net 5.5-RELEASE-p2 FreeBSD 5.5-RELEASE-p2 #3: Tue
Oct 9 22:39:13 EST 2007
r...@server.example.net:/usr/obj/usr/src/sys/MONITOR i386
Nagios
Version 2.0b3
# ./check_snmp -V
check_snmp (nagios-plugins 1.4.3) 1.58
From the webui
APC-RR-R3-1.hou
check_rr_amp
WARNING 04-07-2009 13:00:17 8d 3h 17m 2s 10/10 SNMP WARNING - 90
APC-RR-R3-2.hou
check_rr_amp
WARNING 04-07-2009 12:57:52 18d 2h 46m 48s 10/10 SNMP WARNING - *160*
^note the * 160 * for the one that actually is in the warning range.
from checkcommands.cfg
define command {
command_name check_rr_amp
command_line $USER1$/check_snmp -H $HOSTADDRESS$ -o
mib-2.33.1.4.4.1.3.1 -C cPanel -w $ARG1$ -c $AR
}
From the hosts config file.
define service{
host_name APC-RR-R1-1.hou
service_description check_rr_amp
check_command check_rr_amp!159!179
max_check_attempts 10
normal_check_interval 5
retry_check_interval 3
check_period 24x7
notification_interval 30
notification_period 24x7
notification_options w,c,r
contact_groups backup-admins
}
Thanks!
-=Tom
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Nagios-users mailing list
Nagios-users@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
