[c-nsp] "snmpEngineTime" seems to wrap with "sysUpTime" in old IOS release

[Chuck Church]

I'm not sure if the snmpenginetime wrapping would increment the
snmpEngineBoots, but it would make sense that it would.  If that is the
case, there are definitely bugs from a 8 or so years ago where devices
didn't update their snmpEngineBoots counter upon reload.  So you'd reboot
switch, snmpEngineBoots didn't increment on the device (I guess it's stored
in NVRAM), and the SNMP manager would stop talking to the device since
snmpenginetime was no longer what it was expecting, and the snmpengineboot
hadn't incremented.

Chuck

-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
Nathan Lannine
Sent: Thursday, April 6, 2017 12:23 PM
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] "snmpEngineTime" seems to wrap with "sysUpTime" in old
IOS release

> How to explain this behavior? Is it likely some kind of SNMP agent

I may not have this totally right, but I believe sysUpTime is a 32-bit
value, which will only go out about 400 and some odd days before it wraps to
0.
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/