NPM 10.4 - Hardware Sensor .. Juniper EX Fans running at full speed..

Hello all,

We recently upgraded from 10.3 to 10.4.. I'm having a love/hate relationship with the Hardware Sensors. I love that I can get rid of a lot of my custom pollers to monitor hardware health. I hate that I don't have control of the thresholds.. For example, I don't want a warning message when a Juniper Fan is running at full speed.. But I want to know when the Fan has failed.

I'm sure someone is going tell me to run some SQL script to modify the DB.. Which really is an unacceptable answer.. As this should be built into the Web GUI..

So, is there a method to configure the Hardware Sensor not to going in warning state when a Juniper Fan is running at full speed?

TIA,

Ken

Find more posts tagged with

network_monitoring

pita

network_management

npm

Accepted answers

All comments

DONDERKA

Hi,

unfortunately there are no thresholds to be set. We get the sensor status from the device itself and all statuses reported by the device have predefined status value in our system. There is currently now way to change that in your environment.

Please submit a feature request through the support for this functionality.

Thanks

Dalibor

kenosmith3

It's funny that solarwinds decided to issue warning for a FAN running at full speed. However, Juniper won't issues a Chassis alarm for the same condition.. I don't think that it a feature request that is needed, as it more of a bug fix request.. I'll just tell my staff to ignore the hardware sensors and it should be fix in 2014 or so..

sja

True...

I have the same fan alert from EX4200

Solarwinds know the oid of juniper fan running ar full speed ...

I will ignore (juniper does)

When the fan is stoping and temp is on the way up that is when it will be usefull..

/SJA

bbarltrop

We addressed the false positives by editing the alert conditions. We broke up the hardware alerts in to 2 different ones: one for sensor status equal to warning and one for sensor status equal to critical. For the warning alert we changed the trigger condition to ALL of the following

Hardware Sensor Status is qual to Warning

Hardware Sensor Original Status is not equal to Running at full speed

We also had a bunch of false alarms fo X2 and Xenpack 10 gig optics. We found 2 ways to address this. One was by adding a condition group where NONE of the following apply:

Hardware Sensor Display Naim begins with Te

I thought that might inadvertantly filter out too much, though. We tried changing it to so that the "contains NONE of" condition group had several lines where the sensor display name "contains" and listing the various sensors in question, one on each line. However, it seems having a "none of" sub group where the top level is "all of" broke the alert manager boolean logic. What finally worked was doing 4 seperate "none of" condition groups where each group only has a single "Hardware Sensor Display Name contains Bias Current Sensor", for instance.

No more false positives on the alert board. Now if only they will add the cisco 4500 power supplies to the managed components I will be happy.

dingo-rock

We had the same problem with the Hardware Health MIB reporting Fans running at high speed - however it went away when we upgraded the Juniper OS to 12.3R3.4 !