Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

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

Overview

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

Environment

  • NPM all versions

Cause 

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.

Resolution

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

Tags

Classifications

Public