Network Management

Cisco Hardware Health Sensors Show Warning State After Upgrading to OSH/NPM 2026.2

After upgrading to SolarWinds Observability Self-Hosted (OSH) or Network Performance Monitor (NPM) 2026.2, Cisco chassis devices may display new Hardware Health sensors in a Warning state. This article explains why this occurs, how to verify whether the sensors are reporting a real issue, and the available options to address the alert noise.

First published date

6/11/2026 8:41 PM

Last published date

7/15/2026 11:16 PM

Overview

Following an upgrade to OSH/NPM 2026.2, the following new Hardware Health sensors appear under the Other (Warning) category for Cisco chassis devices:

  • FRU Status Change Notifications

  • Power Supply Output Change Notifications

These sensors appear immediately after the upgrade and affect any Cisco chassis device that is actively monitored via SNMP Hardware Health polling, including:

  • Cisco Catalyst 9300 / 9400 / 9500 / 9600 series

  • Cisco Nexus 7000 / 9000 series

  • Cisco ASR / ISR platforms

This article explains why this occurs, how to verify whether the sensors are reporting a real issue, and the available options to address the alert noise.

Product section

Orion Platform

Cause

This behavior is by design in OSH/NPM 2026.2. As part of the Cisco modular Hardware Health enhancement introduced in this release, SolarWinds now polls the CiscoFRUNotificationSettings table from the CISCO-ENTITY-FRU-CONTROL-MIB. This table contains two OIDs that indicate whether FRU-related SNMP trap notifications are enabled or disabled at the device level:

  • cefcMIBEnableStatusNotification (OID: 1.3.6.1.4.1.9.9.117.1.3.1)

  • cefcEnablePSOutputChangeNotif (OID: 1.3.6.1.4.1.9.9.117.1.3.2)

These are TruthValue SNMP data types with the following status mapping:

OID Value

Meaning

SolarWinds Status

1 (True)

Notifications enabled on device

Up (green)

2 (False)

Notifications disabled on device

Warning (yellow)

Most Cisco devices have these SNMP trap notifications disabled by default. When SolarWinds polls these OIDs and receives a value of 2 (False/disabled), It interprets this as a non-healthy state and displays the sensor as a Warning. Prior to 2026.2, these OIDs were not polled, so the sensors did not exist and no warning was generated.

These sensors do not reflect actual hardware conditions such as temperature, fan status, voltage, or PSU failure. The Warning does not indicate a hardware fault on the device.

Resolution

NOTE: Before taking any action, verify the sensor values as described below. These sensors provide a legitimate data point about the device's SNMP trap configuration. Suppressing them removes that visibility. Confirm the current state with your network team before proceeding.

Verify the Sensor Values First

  1. Log in to the SolarWinds Platform Web Console.

  2. Go to Settings > All Settings > Node & Group Management > Manage Hardware Sensors.

  3. Search for the sensors named FRU Status Change Notifications or Power Supply Output Change Notifications.

  4. Check the Last Value column:

    • Value = 1 — The notification is enabled on the device. The sensor is providing accurate information, and the Warning reflects the device's actual SNMP trap configuration. Confirm whether this is intentional before suppressing.

    • Value = 2 — The notification is disabled on the device. This is the default state for most Cisco devices and does not indicate a hardware problem. 

      Choose one of the resolution options below based on your environment and requirements. These are alternative resolution paths, and only one is typically needed.

Additional Notes:

Cisco IOS

For Cisco IOS operating system, running the following command will enable SNMP traps:

snmp-server enable traps fru-ctrl

Resolution 1 — Disable the Specific Sensors Per Node (Recommended)

This is the most targeted option. It suppresses only the FRU notification setting sensors without removing visibility into the actual FRU module, PSU, or fan health.

  1. Log in to the SolarWinds Platform Web Console.

  2. Go to Settings > All Settings > Node & Group Management > Manage Hardware Sensors.

  3. Filter or search for sensors named FRU Status Change Notifications and Power Supply Output Change Notifications under the Other (Warning) category.

  4. Select the sensors and click Disable.

  5. Click Submit.

  6. Allow 10–15 minutes for the status to update.

Resolution 2 — Use the IgnoredEventTypes Advanced Setting (Global)

Use this option in large environments where the FRU polling is generating excessive hardware health events across many nodes.

  1. Log in to the SolarWinds Platform Web Console.

  2. Go to Settings > All Settings > Advanced Configuration.

  3. Locate the setting: HardwareHealth.Data.HardwareHealth.IgnoredEventTypes

  4. Set the value to one or more of the following (comma-separated): HardwareInfo, HardwareCategory, HardwareItem

  5. Click Submit.

NOTE: This is a global setting and will affect hardware health event generation across all nodes, not only Cisco devices.

Resolution 3 — Switch the Preferred Cisco MIB Per Node

Use this option only if you do not require FRU module-level health visibility (line cards, PSUs, fan trays) for a specific device.

  1. Log in to the SolarWinds Platform Web Console.

  2. Go to Settings > Manage Nodes and locate the affected node.

  3. Select the node and click Edit Properties.

  4. Scroll down to the Hardware Health Polling section.

  5. From the Preferred Cisco MIB drop-down, select CISCO-ENVMON-MIB.

  6. Click Submit.

  7. Allow 10–15 minutes for polling to update.

Warning: Switching to CISCO-ENVMON-MIB removes FRU module, PSU, and fan tray visibility entirely for that node. This is a per-node change and does not affect other nodes.