We built a custom version of check_snmp_uptime that handles the 32-bit rollover.
It's implemented by keeping a history file for each device, which records the last value of the uptime counter. That way we can recognize when a rollover has occurred. Not very elegant, but it works. I can send it to you and/or the list if you'd like. Mike Mike Dorman Lead Systems Engineer Latisys-Denver, LLC (303) 268-1504 direct [email protected] www.latisys.com > From: unix <[email protected]> > Reply-To: Opsview Users <[email protected]> > Date: Wed, 03 Feb 2010 14:55:53 +0100 > To: opsview-users <[email protected]> > Subject: Re: [opsview-users] check_snmp_uptime bug > > On 2010-01-04 15:13, James Peel wrote: >> >>> can it be that check_snmp_uptime has a bug? >> >> >> This sounds like a 16 bit counter issue, so potentially this plugin >> needs updating. >> >> -- >> James > > Think it's a 32 bits (timeticks) problem. Max is 2^32 - 1 = 4294967295 > == 497 days > Day 498 is reported as day 1, causing events in our enviroment. > > /Urban > > _______________________________________________ > Opsview-users mailing list > [email protected] > http://lists.opsview.org/lists/listinfo/opsview-users _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
