Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Network Performance Monitor (NPM) > Node Down alert is not triggered after a reboot

Node Down alert is not triggered after a reboot

Updated: October 2, 2017


When you reboot a server, the Node Down alert is not triggered and no alert email is received.


  • NPM all versions


The response interval is too short to trigger the Node Down alert before the server starts responding. 

If the polling interval is set to the two-minute default, a node must be unresponsive for up to four minutes before it triggers the alert. Most servers respond to pings within two minutes, while virtual machines (VMs) may respond within ten seconds.


Configure the Node Rebooted alert. Because of how quickly a node can reboot, there is no way to trigger the Node Down alert. 

See NPM poll down nodes for details about how a Node Down alert is triggered. 



Last modified