On 9 March 2011 16:42, Kumar, Ashish <xml.de...@gmail.com> wrote: > I do apologise if this questions has been asked earlier but searching the > mailing list did not yield any positive results. > > We are using net-snmp 5.3.1 on Red Hat EL 5 and the system has been up for > quite a long time > > # uptime > 16:32:44 up 533 days, 40 min, 1 user, load average: 4.09, 4.73, 4.46
Note that this is longer than the 497 days (roughly) which corresponds to the maximum value supported by the TimeTicks syntax. This is a 32-bit value, measured in centi-seconds. Hence the values for sysUpTime and hrSyetmUptime will each wrap every 16 months or so. > # snmpwalk -v2c -cpublic server1 hrSystemUpTime > HOST-RESOURCES-MIB::hrSystemUptime.0 = Timeticks: (310395313) 35 days, > 22:12:33.13 That would match with the overall system uptime listed above. (497+35.plenty=532.plenty ~= 533) > # snmpwalk -v2c -cpublic server1 sysUptime > DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (2530155015) 292 days, > 20:12:30.15 My suspicion is that the SNMP agent wasn't started immediately (or was restarted at some point after the system had been running for several months). So the value for hrSysUptime may not match that for hrSystemUptime. You could check this by looking at the process information for the agent process on that host. Dave ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
