Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

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