Details
Minor Description
Can you interpret the "Low-Alarm" as replied trough snmp for a bad dBm signal?
root@observium:/opt/observium# snmpwalk -v 2c -c <community> mlx-xy .1.3.6.1.4.1.1991.1.1.3.3.6.1.3.4 |
iso.3.6.1.4.1.1991.1.1.3.3.6.1.3.4 = STRING: " -024.9485 dBm: Low-Alarm " |
|
|
MySQL Entry
|
{
|
"table": "sensors", |
"rows": |
[
|
{
|
"sensor_id": 15420, |
"sensor_deleted": 0, |
"sensor_class": "dbm", |
"device_id": 145, |
"poller_type": "snmp", |
"sensor_oid": ".1.3.6.1.4.1.1991.1.1.3.3.6.1.3.4", |
"sensor_mib": null, |
"sensor_object": null, |
"sensor_index": "4", |
"sensor_type": "brocade-dom-rx", |
"sensor_descr": "10GigabitEthernet1/4 DOM RX Power", |
"sensor_unit": null, |
"sensor_multiplier": 1, |
"sensor_limit": null, |
"sensor_limit_warn": null, |
"sensor_limit_low": null, |
"sensor_limit_low_warn": null, |
"sensor_custom_limit": 0, |
"entPhysicalIndex_measured": null, |
"measured_class": "port", |
"measured_entity": "15780", |
"entPhysicalIndex": "4", |
"entPhysicalClass": null, |
"sensor_ignore": 0, |
"sensor_disable": 0, |
"sensor_value": -24.94850, |
"sensor_event": "ok", |
"sensor_status": "", |
"sensor_polled": 2147483647, |
"sensor_last_change": 0 |
}
|
]
|
}
|
RX/TX: Possible replies are "Low-Alarm",",Low-Warn","Normal","High-Warn" and "High-Alarm". More information are available on http://www.brocade.com/content/html/en/administration-guide/netiron-05900-adminguide/GUID-A5EE20BF-DB7F-4B9E-A75B-CA2757979FC0.html
Attachments
Activity
Please rename the Bug, i forgot to change the name.
I.e. to "Brocade RX/TX SNMP dBm Status Handling"
This would involve some method of pushing these values into the status entity type, which would need some extensions to that code to handle mangling these values.