I guess that depends - are they using the same OIDs as other platforms that use dBm use? If so that's a bug on their end.. if it's just a wrong unit setting on our side we could fix that :-)
Tom
On 6/4/2018 9:25 PM, Richard Savage wrote:
Hi
Its seems as though Cisco in their wisdom have changed how the power levels are reported for optical SFP’s and they now by default report in mW and not dBm on the ASR9k platform. When observium SNMP’s them its pulling the mW values now and thus its throwing the sensor values off and creating alerts.
Can observium be made to change these back to dBm readings using a simple calculation and pull the thresholds as well as before? Calculation: /P/_(dBm) = 10 ⋅ log_10 (/P/_(mW) / 1mW)
This is whats seen on the CLI for the exact same port:
Thresholds: Alarm High Warning High Warning Low Alarm Low Temperature: +95.000 C +90.000 C -20.000 C -25.000 C Voltage: 3.800 Volt 3.700 Volt 2.900 Volt 2.800 Volt Bias: 90.000 mAmps 80.000 mAmps 3.000 mAmps 2.000 mAmps Transmit Power: 1.59000 mW (2.01397 dBm) 1.26000 mW (1.00371 dBm) 0.20000 mW (-6.98970 dBm) 0.16000 mW (-7.95880 dBm) Receive Power: 1.26000 mW (1.00371 dBm) 1.00000 mW (0.00000 dBm) 0.01260 mW (-18.99629 dBm) 0.01000 mW (-20.00000 dBm) Temperature: 30.434 Voltage: 3.264 Volt Tx Bias: 33.722 mAmps Tx Power: 0.53550 mW (-2.71241 dBm) Rx Power: 0.22890 mW (-6.40354 dBm)
Many Thanks
Richard
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
