Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Alert triggers with a delay for node reboot

Alert triggers with a delay for node reboot

Created by Norbert Skurzewski, last modified by MindTouch on Jun 23, 2016

Views: 2,099 Votes: 0 Revisions: 5


Node rebooted alerts are being sent with a 10-15 minute delay.


NPM 11.5.3 and earlier


The cause was an issue with the Microsoft SNMP Agent which is responsible for the node reboot alerts. The node reboot alert is based on a restart of the SNMP Agent and not a poll like Up/Down status alert.

The SNMP Agent caused an issue after the node restarted and did not allow it to send a reboot information to Solarwinds so we could not trigger the reboot alert.


  1. To check if this is the case, reboot your node and make note of the time.
  2. Go to the Orion Web Console and check if an event has been created for the reboot (Home tab > Events).
  3. If there are no events after 2 minutes, this could be a symptom of SNMP Agent issue.
  4. To check it, run the SNMP Walk.
  5. If the SNMP Walk times out, this means that you have an issue with the SNMP Agent.
  6. When you finally get the alert, check SysUpTime from the device run by running SNMP Walk.
  7. Check OID (time in in hundredths of a second since the last boot).
  8. Once you confirm that the boot time is accurate with the time you have restarted the node, check the Events in Orion Web Console.
  9. If the event has been created for example 10 minutes after the reboot it means your SNMP Agent is faulty.
  10. You can also check if the SNMP Agent is faulty by restarting it in services, if it triggers an alert in roughly 2 minutes and after reboot of the node it triggers in 10 minutes it means Agent does not work correctly.


Once you confirm that the issue is caused by the Microsoft SNMP Agent, you will have to either research their knowledge base or contact them directly. They will advise you what steps to take to resolve SNMP Agent issue as it is their product.


Last modified