Netonix Forums

You guys have a seperate OID where the uptime is correct:
HOST-RESOURCES-MIB::hrSystemUptime.0 = Timeticks: (5992862) 16:38:48.62

But this is what you get if you poll the standard sysUptime:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3119604450) 361 days, 1:34:04.50

Hmm, I don't see this on any of my switches. Nor has anyone else reported it. Maybe it just needs a restart. If you don't want to reboot the switch you can just run "/etc/init.d/snmpd restart" at the command line.

I've restarted and its the same across all my Netonix

This is the standard sysUptime which is incorrect:
.1.3.6.1.2.1.1.3.0 = Timeticks: (3162658189) 366 days, 1:09:41.89

This is the one that is correct on the equipment:
.1.3.6.1.2.1.25.1.1.0 = Timeticks: (49085850) 5 days, 16:20:58.50

On the ones what do show 366 days on the sysUptime, if you reboot after a minute or so it does reset, even though firmware upgrades didn't fix the issue when it rebooted then.

Even after it resets, there is a difference of 1-3 minutes in uptime between the 2 OIDs for uptime, so there is something not quite right.

Every one that had the error was showing 366 days

Can you post a screenshot of the Status page and Log from one of the switches?

I've since rebooted the 6 that were having issues and they are no longer showing the 366 days of uptime via SNMP. Its got to be a bug in how it gets the information or the initialization.

I am still seeing this on 1.4.9 with some of my switches. Restarting snmp does not correct the uptime error.


[~]# snmpwalk -v 2c -c xxxx 10.10.10.10 .1.3.6.1.2.1.1.3.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1304840275) 151 days, 0:33:22.75

[~]# snmpwalk -v 2c -c xxxx 10.10.10.10 .1.3.6.1.2.1.25.1.1.0
HOST-RESOURCES-MIB::hrSystemUptime.0 = Timeticks: (49135922) 5 days, 16:29:19.22

[~]# /etc/init.d/snmpd restart
Stopping snmpd: [ OK ]
Starting snmpd: [ OK ]

[~]# snmpwalk -v 2c -c xxxx 10.10.10.10 .1.3.6.1.2.1.1.3.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1304886032) 151 days, 0:41:00.32

I'll be on vacation until the 30th, but I can look into it further when I get back.