Network Management

Hardware health Undefined for SNMP polled devices

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

First published date

10/30/2018 3:09 AM

Last published date

1/28/2022 3:16 AM

Overview

This page will give info on the possible cause of an HWH "undefined error".

Product section

Network Performance Monitor

Cause

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

Resolution

The topology polling interval is usually somewhere around 30 minutes, so if the situation more 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 where 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 some time to poll after making the change.

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

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.