Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
Professional Edition
-
None
Description
Some SFP modules have invalid alarm/warning limits in their EPROM, for example:
Current Alarms Warnings
|
Measurement High Low High Low
|
----------------------------------------------------------------------------
|
Temperature 41.08 C 100.00 C -10.00 C 95.00 C -5.00 C
|
Voltage 3.27 V 3.59 V 2.90 V 3.50 V 3.00 V
|
Current 20.29 mA 100.00 mA 1.00 mA 80.00 mA 2.00 mA
|
Tx Power -6.00 dBm 6.99 dBm -15.08 dBm 4.99 dBm -13.01 dBm
|
Rx Power -7.42 dBm 1.99 dBm 0.00 dBm 0.00 dBm -30.00 dBm
|
Here the Rx Power alarm range is 0 dBm to 1.99 dBm, and warning range is -30 dBm to 0 dBm.
It is just a normal (but probably cheap) 1000BASE-LR transceiver.
Obviously the alarm limits are impossible since alarm/warning ranges do not overlap.
It would be useful if Observium could detect such situations and automatically ignore ranges that are impossible.
Attachments
Activity
I think you mean yellow color for limit ranges.
They mean that you have set custom limits in device edit page for this sensors.
I will change this color to avoid confusion with warning states.
In 11484 I have no alerts on for unrealistic limits so I guess it is OK. A few SFP dBm measurements have the limits in amber (as in the above comment screenshot) I guess that indicates the alarm/warning limits were not correct on the SFP PROM?
In addition to the E1/14 screenshot above there are 2 more:
Perhaps a hover popup could explain what the amber color in the limit means...
Please try update to latest revision and rediscovery device.
Limits should be updated.
Fixed in r11484.
Added snmpwalk and discovery, the problem interface is Ethernet1/14.
Edit: and how Observium sees the interface, alarm is on, observium version is 11483:
There is no way to set the attachments not public?
Another module which is missing some limits:
Current Alarms Warnings
|
Measurement High Low High Low
|
----------------------------------------------------------------------------
|
Temperature 24.78 C 85.00 C -40.00 C 70.00 C 0.00 C
|
Voltage 3.27 V 3.59 V 3.00 V 3.59 V 3.00 V
|
Current 20.29 mA 80.00 mA 0.00 mA 80.00 mA 10.00 mA
|
Tx Power -4.06 dBm 3.00 dBm -30.00 dBm 0.00 dBm -30.00 dBm
|
Rx Power -7.77 dBm 3.00 dBm N/A 0.00 dBm N/A
|
If some limit (for example lower limit) is missing, then Observium should alarm only on the limit that is listed - in this case only if the upper alarm/warning limit is exceeded.
Currently Observium alarms for any values. It seems to consider only the High limits and warn for anything under it.
Please make and attach additional information about the device:
- full snmp dump from device:
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalksnmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf device not support SNMP version 2c, replace -v2c with -v1.
- If you have problems with discovery or poller processes, please do and attach these debugs:
./discovery.php -d -h <device>./poller.php -d -h <device>
- additionally attach device and/or vendor specific MIB files
Note, this comment is added automatically.
Oops, yes I mean that yellow. Oops because that then explains why the alarms "worked" - I had put custom limits to avoid Observium using the senseless limits read from the SFP PROM.
Turned off the custom limits, ran discovery, still no alarms on those three dBm measurements that had screenshots above.
So looks like it works better than before. Before the custom limits were needed in order to not have alarms.