Details
-
Bug
-
Resolution: Fixed
-
Trivial
-
None
-
Professional Edition
Description
It seems to be that the poller is not adding the sensor threshold values for transceivers into the database.
Values for "sensor_limit" and "sensor_limit_low" are missing, but they are present in the snmp-walk.
See attached snmpwalk debug.
Attachments
Activity
The values from
entSensorThresholdValue.2224410.3 = -1059981 | |
entSensorThresholdValue.2224410.4 = 450002 |
are not added to the database in
"sensor_limit_warn": 0, |
"sensor_limit_low_warn": 0, |
.
Works well for the voltages now You're great!
I found another issue but now with dBm values...
entSensorType.2224410 = dBm |
entSensorScale.2224410 = milli |
entSensorPrecision.2224410 = 5 |
entSensorValue.2224410 = -421360 |
entSensorStatus.2224410 = ok |
entSensorValueTimeStamp.2224410 = 0 |
entSensorValueUpdateRate.2224410 = 10 |
entSensorMeasuredEntity.2224410 = 2224129 |
entPhysicalDescr.2224410 = Power Sensor |
entPhysicalName.2224410 = 0/0-PORT-23-Rx Lane 0 Power |
entPhysicalClass.2224410 = sensor |
entPhysicalContainedIn.2224410 = 2224129 |
entPhysicalParentRelPos.2224410 = 8 |
entSensorThresholdSeverity.2224410.1 = minor |
entSensorThresholdSeverity.2224410.2 = minor |
entSensorThresholdSeverity.2224410.3 = major |
entSensorThresholdSeverity.2224410.4 = major |
entSensorThresholdSeverity.2224410.5 = critical |
entSensorThresholdSeverity.2224410.6 = critical |
entSensorThresholdRelation.2224410.1 = lessOrEqual |
entSensorThresholdRelation.2224410.2 = greaterOrEqual |
entSensorThresholdRelation.2224410.3 = lessOrEqual |
entSensorThresholdRelation.2224410.4 = greaterOrEqual |
entSensorThresholdRelation.2224410.5 = lessOrEqual |
entSensorThresholdRelation.2224410.6 = greaterOrEqual |
entSensorThresholdValue.2224410.1 = 0 |
entSensorThresholdValue.2224410.2 = 0 |
entSensorThresholdValue.2224410.3 = -1059981 |
entSensorThresholdValue.2224410.4 = 450002 |
entSensorThresholdValue.2224410.5 = -1459670 |
entSensorThresholdValue.2224410.6 = 749999 |
{
|
"table": "sensors", |
"rows": |
[
|
{
|
"sensor_id": 16472, |
"sensor_deleted": 0, |
"sensor_class": "dbm", |
"device_id": 696, |
"poller_type": "snmp", |
"sensor_oid": ".1.3.6.1.4.1.9.9.91.1.1.1.1.4.2224410", |
"sensor_mib": null, |
"sensor_object": null, |
"sensor_index": "2224410", |
"sensor_type": "cisco-entity-sensor", |
"sensor_descr": "Cisco QSFP28 100G LR4 Pluggable Optics Module - Power - 0/0-PORT-23-Rx Lane 0 Power", |
"sensor_unit": null, |
"sensor_multiplier": 0.00000001, |
"sensor_limit": 0.00749999, |
"sensor_limit_warn": 0, |
"sensor_limit_low": -0.0145967, |
"sensor_limit_low_warn": 0, |
"sensor_custom_limit": 0, |
"entPhysicalIndex_measured": null, |
"measured_class": null, |
"measured_entity": null, |
"entPhysicalIndex": "2224410", |
"entPhysicalClass": null, |
"sensor_ignore": 0, |
"sensor_disable": 0, |
"sensor_value": -0.00421, |
"sensor_event": "warning", |
"sensor_status": "Sensor warning thresholds exceeded.", |
"sensor_polled": 1542792605, |
"sensor_last_change": 1539337519 |
}
|
]
|
}
|
The value from .3 is not getting added to the db. Just checked with latest r9625.
Thank you.
(I will report this to Cisco... like with every strange issue )
Derp, your Cisco devices always produce strange problems..
Here another case, when both limits exist, but critical is zero:
entSensorThresholdSeverity.2130160.1 = minor
|
entSensorThresholdSeverity.2130160.2 = minor
|
entSensorThresholdSeverity.2130160.3 = major
|
entSensorThresholdSeverity.2130160.4 = major
|
entSensorThresholdSeverity.2130160.5 = critical
|
entSensorThresholdSeverity.2130160.6 = critical
|
entSensorThresholdRelation.2130160.1 = lessOrEqual
|
entSensorThresholdRelation.2130160.2 = greaterOrEqual
|
entSensorThresholdRelation.2130160.3 = lessOrEqual
|
entSensorThresholdRelation.2130160.4 = greaterOrEqual
|
entSensorThresholdRelation.2130160.5 = lessOrEqual
|
entSensorThresholdRelation.2130160.6 = greaterOrEqual
|
entSensorThresholdValue.2130160.1 = 31000000
|
entSensorThresholdValue.2130160.2 = 34650000
|
entSensorThresholdValue.2130160.3 = 29700000
|
entSensorThresholdValue.2130160.4 = 36300000
|
entSensorThresholdValue.2130160.5 = 0
|
entSensorThresholdValue.2130160.6 = 0
|
Should be fixed in r9625.
This is useless debug.
Please attach debug for sensors discovery:
./discovery.php -d -m sensors -h <device>
|
Cisco uses minor thresholds as random limit (as critical, as warning)..