Network Management
Node is up but the node down alert is triggered in the SolarWinds Platform
The article shows an explanation and steps to follow, given the behavior of "falsely" identified statuses for nodes Polled in the SolarWinds Platform
First published date
Last published date
Overview
The SolarWinds Platform sends an alert email and incorrectly reports that a node monitored by ICMP is down.
Product section
Cause
Resolution
Please follow these steps:
- Open the SolarWinds Platform Web Console.
- Navigate to the Node Details view of the node that has triggered the alert.
In the URL of this page you will see something like this:
http(s)://{YourOrionServer}/Orion/NetPerfMon/NodeDetails.aspx?NetObject=N:1
In the sample URL above, the NodeID is 1 (This is coming from NetObject=N:1)
- RDP to Main Poller.
- Open Database Manager (Default location: C:\Program Files (x86)\SolarWinds\Orion\DatabaseManager.exe).
- Locate the ResponseTime tables and filter them with your NodeID. For this action you can use the following query:
-- Scripts are not supported under any SolarWinds support program or service. -- Scripts are provided AS IS without warranty of any kind. SolarWinds further -- disclaims all warranties including, without limitation, any implied warranties -- of merchantability or of fitness for a particular purpose. The risk arising -- out of the use or performance of the scripts and documentation stays with you. -- In no event shall SolarWinds or anyone else involved in the creation, -- production, or delivery of the scripts be liable for any damages whatsoever -- (including, without limitation, damages for loss of business profits, business -- interruption, loss of business information, or other pecuniary loss) arising -- out of the use of or inability to use the scripts or documentation. -- Select rows from a Table or View '[ResponseTime_CS]' in schema '[dbo]' DECLARE @NID INT = 1 -- Replace 1 with your NodeID value. SELECT * FROM [dbo].[ResponseTime_CS] WHERE [NodeID] = @NID AND [Availability] <> 100 - Locate the time the alert was triggered and check if the availability for the node is not 100.
- If the value for the Availability is not at 100 for the time the alert was triggered, the alert is valid. Please remember that data is summarized from detailed to hourly after 7 days by default and daily after 30 days by default. This will reduce the precision, but if the value is not 100 for Availability, this would still indicate expected behavioral and valid alert.
- In case the Availability is at 100 and the alert was still triggered for this node, further investigation needs to be performed by Technical Support into this issue.