>>>>> On Tue, 26 Oct 2004 12:46:41 -0400, Binh Nguyen <[EMAIL PROTECTED]> said:
Binh> Since sysUpTime is measured in one hundredth of a second, it Binh> will take approximately 497 days for this 32 bit counter to Binh> wrap. 497 days is not long enough because some telco equipment Binh> is let to run for several years. Am I missing something? Are Binh> there any resolutions/workaround to lift this limit? sysUpTime is specified in an IETF document and thus, no, we can't just "change it". Managers are supposed to be smart enough that when they see a sysUpTime wrap they should deal appropriately with counters and treat it as a discontinuity. What exactly is your problem? Are you just looking to see how long your device is up and you don't want to think its been reset when it hasn't? -- Wes Hardaker Sparta ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
