how do you disable alerting for hardware sensors in which the interface is ADMIN SHUT.

bigdata

Hardware sensors for optics frequenlty enter critical state with values that are clearaly at the end of the bounds check (100W, .0000000001, -40.00 sBm)

however, shutting down the interface does not appear to mute the hardware sensor (optics) for the interface in question.

i want to know if there is a way to link up the hardware sensor interface name with the interface property, so I can exclude interfaces that are in an admin down state from alarming.

from the switch

switch# sh inter status | incl Et[3|4]

Et3                                      disabled     1        full   10G    10GBASE-LR <-- disabled interfaces

Et4                                      disabled     1        full   10G    10GBASE-LR <-- disabled interfaces

switch# sh inter transceiver detail

mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable.

++ : high alarm, +  : high warning, -  : low warning, -- : low alarm.

A2D readouts (if they differ), are reported in parentheses.

The threshold values are calibrated.

<snip>

                         High Alarm  High Warn   Low Alarm   Low Warn

           Tx Power      Threshold   Threshold   Threshold   Threshold

Port       (dBm)         (dBm)       (dBm)       (dBm)       (dBm)

-------    ------------  ----------  ----------  ----------  ----------

Et3        -40.00        2.01        1.00        -7.96       -6.99

Et4        -40.00        2.01        1.00        -7.96       -6.99

<snip>

mesverrum

It's likely going to be a real mess to do so because the Cisco hardware OID's don't give you much to work with there to correlate a hardware sensor to a specific interface except the name, but even those aren't always exactly the same format so trying to match them across might be an exercise in building patterns like Etxxx or Etxxx/zzz but not like Etxxxy and not like yEtxxx, etc.

The cisco hardware sensors for fiber stuff over SNMP have always been so sketchy that I often just disable them across the board rather than try to fight all the false positives the kick up.