
OPERATIONAL DEFECT DATABASE
...

...
After 497 days, sysUpTime becomes 0 due to 32-bit OID limitation. Therefore, snmpEngineTime.0 variable is supposed to be workaround to the sysUpTime variable roll over. However, from test in all XR devices, we see snmpEngineTime is rested when sysUpTime roll over as described in IOS bug, CSCeh49492 which addressed same issue. Snmpd process : RP/0/RP0/CPU0:crs1#show processes snmpd detail Thu Jul 26 10:58:51.276 BDG Job Id: 391 PID: 454917 Executable path: /disk0/hfr-base-3.8.4/bin/snmpd Instance #: 1 Version ID: 00.00.0000 Respawn: ON Respawn count: 1 Max. spawns per minute: 12 Last started: Thu Mar 3 01:56:41 2011 <<< bash-3.00$ snmpwalk -v 2c -c xxx a.b.c.d 1.3.6.1.2.1.1.3 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (123700445) 14 days, 7:36:44.45 bash-3.00$ bash-3.00$ snmpwalk -v 2c -c xxx a.b.c.d 1.3.6.1.6.3.10.2.1.3 SNMP-FRAMEWORK-MIB::snmpEngineTime.0 = INTEGER: 1238709 seconds
Issue happens after 497 days.
None.
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.