Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Hardware Sensors do not affect the status of a map

Hardware Sensors do not affect the status of a map

Created by Zoltán Jalsovszky, last modified by MindTouch on Jun 23, 2016

Views: 15 Votes: 1 Revisions: 4


This article provides brief information and steps to resolve the error when one of the objects (Volume, Interfaces, SAM applications, etc.) you are trying to add to a map is in a critical or down state. 

This is not working for Hardware Sensors - even if you add a hardware sensor to a map and it is in Critical status, the map status will not be changed.


  • NPM version 11.5
  • SAM version 6.2


Network Atlas can reflect hardware sensor status, but it is not enabled by default:

1. Click Start > SolarWinds Orion > Advanced Features > Database Manager.
2. Click Add default server.
3. Right-click SolarWindsOrion database, and then select New query.
4. Paste the following query and click on Execute:

UPDATE NodeChildStatusParticipation
SET Enabled = 1
WHERE EntityType IN ('Orion.HardwareHealth.HardwareCategoryStatus', 'Orion.HardwareHealth.HardwareInfo', 'Orion.HardwareHealth.HardwareItem')


5. Restart all Orion services and Network Atlas.




Last modified
22:24, 22 Jun 2016