Submit a ticketCall us

WebinarFREE IT Monitoring Webcast

Don’t miss out on our webcast, Essential IT Monitoring with SolarWinds ipMonitor, where we will show you how to keep an eye on your IT environment from one centralized, affordable, and lightweight monitoring tool: SolarWinds® ipMonitor®.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Check false Alert for Volume

Check false Alert for Volume

Created by Gary O'Donovan, last modified by Harry Griffiths on May 25, 2017

Views: 1,826 Votes: 2 Revisions: 7


This article provides brief information to check the Orion Database Volumes table when you receive false Alerts for a specific server.


This will allow the SolarWinds support team to discount information in the Orion Database for being responsible for  triggering the Alert. (If the Device is sending incorrect information to Orion, and the Alert is being triggered based on the information in the Orion Database, in which case it would not be considered a False Alert).



All NPM versions



The issue is caused by incorrect logic on the Alert or Information in the Orion Database that triggers the Alert. For example, a Device reporting incorrectly to Orion, or a Device in an Error State.


To Check the Volume table:

1. Open the Orion Database Manager, and then add Default Server.

2. Go to Volumes, and then select Execute Query.

3. Open the Nodes details page and find the Node ID as per example below



4. Run the following query on the Database to find the target Volume:

SELECT * FROM [dbo].[Volumes]
WHERE NodeID =42

You can now view the following information in the Volumes table, which will help determine if the alert we are receiving is false.



You may see the device down and is not responding


StatusLED - Down.gif



-  N

In these cases, go to manage nodes and do a list resources against the node.


See if there the mentioned volume is unchecked and if so please add it back in.


Go back to manage nodes and click the + sign to expand the node in question.


Remove the old volume.


This could be caused by:

* Volume been replaced/removed from server

* re-indexing of the volume


Last modified