Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Network Performance Monitor (NPM) > False reboot alert for specific node

False reboot alert for specific node

Updated November 29th, 2016

Overview

A false alert indicating that a monitored object has rebooted triggers even when the monitored object is actually up and functioning as normal.

Environment

All NPM versions

Resolution

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 OID. 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.


Note: The 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:

Cisco

  • If, for any reason, the device SNMP agent is restarted on the monitored object, SolarWinds NPM may indicate a false reboot.
  • There are known issues on devices from Cisco and other vendors where 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 hrSystemUptime Universal Device Poller".

Linux/Unix/Mac

Windows

If it is a Windows device that is apparently rebooting, uninstall and then reinstall the SNMP agent on the Windows server, as follows:

  1. Log on to your SolarWinds server using an account with administrative privileges.
  2. Click Start > Control Panel > Add or Remove Programs.
  3. Click Add/Remove Windows Components.
  4. Click Management and Monitoring Tools, and then click Details.
  5. Clear Simple Network Management Protocol,and then click OK.
  6. Click Next on the Windows Components window, and then click Finish after completing the Windows Components Wizard.
    Note: You may be prompted to provide your Windows Operating System media or to restart your computer.
  7. After restarting, install the SNMP agent again, as follows:
    1. Log on to your SolarWinds server using an account with administrative privileges.
    2. Click Start > Control Panel > Add or Remove Programs.
    3. Click Add/Remove Windows Components.
    4. Click Management and Monitoring Tools, and then click Details.
    5. Clear Simple Network Management Protocol,and then click OK.
    6. Click Next on the Windows Components window, and then click Finish after completing the Windows Components Wizard.
      Note: You may be prompted to provide your Windows Operating System media or to restart your computer.

Creating an hrSystemUptime Universal Device Poller

  1. Log in as an administrator to the Orion Web Console on the SolarWinds server that is polling the object for which you want to disable topology calculations.
  2. Click Start > All Programs > SolarWinds Orion > Network Performance Monitor > Universal Device Poller.
  3. Click New Universal Device Poller.
  4. In the OID field enter 1.3.6.1.2.1.25.1.1, and then click Next.
  5. Click + as necessary to check all affected devices, and then click Next.
  6. indicate display options as desired, and then click Finish.

 

Time Ticks Conversion:

timeticks / 100 = seconds

timeticks / 6000 = minutes

timeticks / 360000 = hours

timeticks / 8640000 = days

 

 

Last modified

Tags

Classifications

Public