Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

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
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 61 Votes: 0 Revisions: 8

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
21:41, 22 Jun 2016

Tags

Classifications

Public