snmp traps / syslog message for optical values out normal range

  • 9 August 2019
  • 4 replies

How can I get my XOS device to send snmp-trap or syslog message if the optical values are out of normal range?

show port 1:1 transceiver information

Port Temp TxPower RxPower TxBiasCurrent Voltage-Aux1/ Voltage-Aux2
(Celsius) (dBm) (dBm) (mA) Vcc (Volts) (Volts)
1:1 39.81 2.02 0.53* 8.86 3.31 N/A
N/A - parameter not applicable to transceiver connected to the port
* - value is out of normal range
-inf - negative infinity, parameter not defined

4 replies

Userlevel 6
Long standing feature request that many of us have requested before. We are still waiting. Only way I can think of is some kind of intelligent script that id's the type of optic, via a telnet session and gives it a pass or fail for your server.

What is bad is that really is not good enough. You need to be able to track the light levels over time and like us in a metro network with thousands of links you have to know what the reading was before you had a fiber event to know if the repair was good. We try and maintain optical readings with dates taken in an open text area in our snmp server views on interconnecting links

Userlevel 6
Really you want the data exposed via SNMP ... which is a feature request:
Userlevel 6
Yes ... the ability to pull this info just like you pull and chart any other port stats would be a plus. Anyone that exposes their snmp info or network management systems to outside parties or connections should have strict security policies in place not allowing just anyone to have access ...
Userlevel 6
Interesting discovery... My team just informed me there is a new trap being put out only by the 670G2 that is a low light level warning. Problem is that the switch is sending it out as a ENTERASYS-MIB-NAMES|etsysModuleName-5624-1- Since the snmp server associates the switch with a EXOS mib it does not know what to do .... Seems we are closer to getting info.

the switch is logging info too

08/09/2019 10:42:59.40 Port 24 RX Power Sensor=low warning Value= 0.44 mW

Now we just need to get the trap updated to be a EXOS trap and we would be one step closer.