cancel
Showing results for 
Search instead for 
Did you mean: 

snmp sysUpTime

snmp sysUpTime

AlexanderT
New Contributor
So ,snmp counter is overflowed after ~ 497 days. How to deal with this ?

snmpwalk -v 2c -c XXXXXX sw2.g50.kv 1.3.6.1.2.1.1.3
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (56035204) 6 days, 11:39:12.04

sw2.g50.kv.7 # show version | i ImageImage : ExtremeXOS version 15.3.1.4 v1531b4-patch1-31 by release-manager
sw2.g50.kv.8 # show switch | i UpTime
System UpTime: 503 days 14 hours 8 minutes 47 seconds
1 REPLY 1

Ty_Izzet
Extreme Employee
Pavel, as per the MIB definition, the sysUpTime object is a 32-bit number. The elapsed time is represented as number of TimeTicks i.e. 1/100the of a second. So, it will wraparound after 497 days.

Given 2^32-1 = 42949672 (seconds), divide by 86,400 (seconds in a day) = 497 days

There appears to be no workaround to this and it is designed per RFC1213.

You might be able to poll snmpEngineTime (1.3.6.1.6.3.10.2.1.3) for the uptime of the SNMP process, however this may not be as accurate. However a 'show switch' output will always work.
GTM-P2G8KFN