This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

NPM 10.4.1 how to select Cisco temperature sensor?

After upgrading to NPM 10.4.1 and NTA 3.10.0 hf3, I see a bunch of new statistics being listed for our Cisco nodes; power, temperature and other.  Great stuff, except for the following:

1) I have yet to find where I can select the sensors to be monitored.

2) The sensors monitored are incomplete or randomly selected. Example: on a WS-C4510R+E with a Sup7E, I get the following:

 UpPower Supply

 UpTemperature

 UpOther

UpPower Supply 1 FanNormal1

UpPower Supply 2 FanNormal1

UpTe5/1 Receive Power SensorNormal-2.6

UpTe5/1 Transmit Power SensorNormal-2.1

UpTe5/3 Receive Power SensorNormal-2.8

UpTe5/3 Transmit Power SensorNormal-2.1


While on a C2960S, I get:

 UpFan

 UpPower Supply

 UpTemperature

   UpSW#1, Sensor#1, GREENNormal26 °C


If I look at an older WS-C4510 chassis with a Sup5:

 UpTemperature

 UpOther

UpPower Supply 1 FanNormal1

UpPower Supply 2 FanNormal1


It looks like Solarwinds is not polling / interpreting the correct snmp oid's for newer Cisco equipment/IOS releases.


Questions:

How can I get the actual PSU's monitored and not the TenGig interfaces?

How can I get the Chassis temperature monitored and not the TenGig interfaces?

How can I remove the TenGig Transmit and Receive power sensors?

Where do I get to select which of these sensors to monitor?

Where can I place these sensors in the appropriate category?


We are currently running:
Orion Core 2012.2.1, SAM 5.0.1, NPM 10.4.1, NTA 3.10.0, IVIM 1.5.0

thanks in advance,

Adam D'Auria

  • Along these same issues, we have Cisco Telepresnce now showing Camera and Main Display Temps.... this would be great, but when the system goes into standby the polling reads these as not functioning and shows to be critical.  Once the system is back in use, we go green.... but this sure looks bad on our summary page and disctracts from any real issue.

  • I'd really like some kind of answer about this.  I've seen other similar complaints in the forums but I have yet to see a meaningful response from Solarwinds.

    Is this an accepted "known issue"?

    Is it scheduled to be fixed?

    -- if so, when?

    -- if not, why not?

    Is there a workaround?

    -- if so, please share it.