There are scripts for some network hardware that check environmentals and they deal with that by tracking the last value, and if the last value was near wrap over, it doesn't treat it as a reload.
-----Original Message----- From: Devel [mailto:[email protected]] On Behalf Of Florian Lohoff Sent: Thursday, October 23, 2014 2:06 AM To: [email protected] Subject: uptime monitoring via check_snmp / counter wrap Hi, i am currently monitoring sysuptime via check-snmp command_line $USER1$/check_snmp -H $HOSTADDRESS$ -C $_HOSTCOMMUNITY$ -P 2c -o .1.3.6.1.2.1.1.3.0 -c 90000: The 90000 is basically that i want the first 15 Minutes after boot the alarm to be critical. Now obviously with a 32 bit counter this counter wraps at least every 497 days. flo@p2:~$ echo $[ 2**32 / 100 / 86400 ] 497 This causes the above statement to actually show a reboot/sysuptime ALARM. I dont see any way around this as the wrap depends on the last value found via check_snmp so it would need some kind of persistence of data. Is there a better sysuptime check? Flo -- Florian Lohoff [email protected]
