Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

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

Node Down alert is not triggered after a reboot

Updated: July 19, 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.
  • In some cases, it was due to SQL DB connection issues.

Resolution

 

 

Last modified

Tags

Classifications

Public