Use snmpEngineTime as a fallback for uptime #1477

Merged
merged 2 commits into from Jul 20, 2015

Projects

None yet

4 participants

@laf
Member
laf commented Jul 19, 2015

Fixes #1426 and in some way #1017

snmpEngineTime is good for 135 years uptime. The issue with hrSystemUptime and sysUptime is they roll at around 496 days which then marks a device as rebooted.

If uptime is less than snmpEngineTime and it's numeric then we use snmpEngineTime as uptime value and carry on.

@laf laf Use snmpEngineTime as primary uptime value
894a96c
@laf laf added Bug Polling labels Jul 19, 2015
@laf
Member
laf commented Jul 19, 2015

Hang fire with this one.

@laf laf assigned laf and unassigned laf Jul 19, 2015
@laf
Member
laf commented Jul 19, 2015

All good. Thought the uptime graph wasn't working but as I rebooted a box with over 400 days of uptime you can't see the data in the graph at the moment.

@laf laf Fall back to using snmpEngineTime rather than be the default
1265fc4
@laf laf changed the title from Use snmpEngineTime as primary uptime value to Use snmpEngineTime as a fallback for uptime Jul 19, 2015
@f0o f0o merged commit 3fcfb40 into librenms:master Jul 20, 2015

2 checks passed

Auto-Deploy Build finished.
Details
Scrutinizer No new issues
Details
@adammmmm
adammmmm commented Aug 6, 2015

We have a couple Cisco routers with more than 496 days uptime. Is this supposed to start working automatically or do we need to do anything like rediscover or whatever?
The event log is getting spammed with "Device rebooted after 1 years, 131 days, 21h" every 5 minutes now.

@laf
Member
laf commented Aug 6, 2015

Hi @adammmmm should be automatic - especially on Cisco stuff - assuming you've updated.

run ./poller.php -h HOSTNAME -d -r -m system

Post a link to the debug on dpaste.de in another issue so we can track this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment