Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
A false alert indicating that a monitored object has rebooted triggers even when the monitored object is actually up and functioning as normal.
All NPM versions
This is a known issue that arises when a monitored device provides incorrect values for the
sysUpTime OID. SolarWinds NPM determines whether or not a device has rebooted by polling the value returned by the
sysUpTime is a 32-bit counter reporting the number of 100ths of a second since the monitored object last booted. For more information, see the
sysUpTime entry in the Cisco SNMP Object Navigator. If the currently polled value is less than the previously polled value, SolarWinds NPM considers the monitored object to have rebooted, and, if reboot alerts are configured, they will fire after the new, lower
sysUpTime value is written to the database.
hrSystemUptime OID also reports time since last boot, but SolarWinds NPM does not currently poll this OID.
Depending on the vendor and type of the object you are monitoring, there may be a workaround to address this false reboot issue:
sysUpTimewill randomly reset back to zero or will begin to count backwards. Both cases will lead SolarWinds NPM to indicate false reboots. SolarWinds is unable to directly address the issue in this case, and you will need to contact your device vendor for a solution. For more information about creating a Universal Device Poller to poll
hrSystemUptime, see the section "Creating an
hrSystemUptimeUniversal Device Poller".
If it is a Windows device that is apparently rebooting, uninstall and then reinstall the SNMP agent on the Windows server, as follows:
18.104.22.168.22.214.171.124.1, and then click Next.
timeticks / 100 = seconds
timeticks / 6000 = minutes
timeticks / 360000 = hours
timeticks / 8640000 = days