Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Node is up but the node down alert is triggered

Node is up but the node down alert is triggered

Created by Dennis Harnett, last modified by MindTouch on Jun 23, 2016

Views: 4,218 Votes: 0 Revisions: 3

Overview

Orion sends an alert email and incorrectly reports that a node monitored by ICMP is down.

Environment

NPM 11.5.2

Cause 

This occurs when the ICMP does not reach the node. The data will then be stored as NULL in the database and alert that rely on the ICMP will be triggered.

Resolution

  1. Take note of the node ID for the node reported. This can be found in the URL for the Node N=***
  2. Open the database manager.
  3. Open the Orion database.
  4. Right-click node response time.
  5. Enter the following query:
    Select * from dbo.responsetime_detail_(date of the alert) where NodeID = '***' (** equals the node ID found in Step 1).
    Entries that appear as NULL in the time frame are those that have been marked as down. 
    Note: The node may be too busy to send the ICMP but is still up and working as expected. Treat this alert as a warning to investigate the node in question.

 

Last modified

Tags

Classifications

Public