Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > Hardware health Undefined for SNMP polled devices

Hardware health Undefined for SNMP polled devices

Table of contents
Created by Jane Baylon, last modified by James Fahey on Jan 24, 2017

Views: 3,609 Votes: 0 Revisions: 4


This article provides information about the cause of a hardware health monitoring undefined error.



NPM version 11.0.1 and later


This situation usually happens when Topology pollers are on for node and causing high load on device thus other pollers such as hardware health might get timeouts.


The topology polling interval is usually somewhere around 30 minutes, so if the situation more like happens in this interval it is hot candidate.


Are you polling that device using SNMP v2 or v3? If you are using this, try changing it to SNMP v1 and see if the issue goes away after that. One of the changes in the new versions of NPM is that, we use SNMP v1 when polling a node.


There are a few cases were some devices do not like SNMP getting bulk requests and will fail to respond; hence the intermittent unknown hardware status.


To correct this, set the device to SNMP v1 and from NPM > edit the Node Properties > use SNMP v1 which in turn will poll using SNMP to get requests. Make sure to give it sometime to poll after making the change.


Creating too many custom thresholds for Hardware Health sensors can cause polling to stop or timeout.




Last modified