Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Network Performance Monitor (NPM) > After upgrading to NPM 11.5, temperature alert readings are incorrect

After upgrading to NPM 11.5, temperature alert readings are incorrect

Table of contents
No headers

After upgrading to NPM 11.5, some customers may receive alerts for incorrect temperature readings if their SolarWinds.HardwareHealth.Pollers.dll.config file was edited in the previous version of NPM.

To fix this issue, do one of the following:

  • If most of your Cisco devices are responding correctly using the CISCO-ENTITY-SENSOR MIB (default option), you can change the MIB for individual nodes to the CISCO-ENVMON-MIB (preferred):
    • Go to Edit Properties for an individual node. At the bottom of the page, select the Preferred Cisco MIB option under Hardware Health Polling. Change it to CISCO-ENVMON-MIB, submit, and then poll again. Values should now be correct.
  • If most of your Cisco devices are responding correctly using the CISCO-ENVMON-MIB, you can change the MIB for individual nodes to the CISCO-ENTITY-SENSOR MIB:
    • (1) Change the MIB that is polled globally for all nodes in Orion. Go to Polling Settings. At the bottom of the page, select the Preferred Cisco MIB option under Hardware Health Polling. Change it to CISCO-ENVMON-MIB.
    • (2) Go to Edit Properties for an individual node. At the bottom of the page, select the Preferred Cisco MIB option under Hardware Health Polling. Change it to CISCO-ENTITY-SENSOR-MIB, submit, and then poll again.

When upgrading from NPM 11.5 to higher versions, this issue should not occur.

Last modified

Tags

Classifications

Public