Description of the problem

An OSN3500 device EFT8 single board does not report ETH_LOS alarms at a site in a network company.

Alarm information

ETH_LOS

Processing

Possible reasons for not reporting ETH_LOS alarms:

a: The alarm itself does not exist, looking at the wrong port.

b: The alarm is suppressed.

c: The alarm exists, but it is set to not report automatically.

d: The network administrator has blocked the alarms.

e: Corresponding to the failure of the Ethernet single board or the main control board.

1: Login to the device through the command line to query the current alarm, there is no such alarm, there is no PROG light on the panel of the single board.

2：Check the alarm suppression status, it is not suppressed, as shown in the figure:

3: Check the alarm shielding rules, fault - settings - shielding rules, there is no shielding rules for this network element pair.

4：Check the auto-report setting, the alarm is in auto-report:

5: Check whether you are looking at the wrong corresponding physical port. you can confirm the RMON performance value traffic of the single board port to confirm that no traffic is in the disconnected state on the corresponding port:

6: Check the reversal status of the alarm, the alarm is not reversed, try to reverse and then prohibit the error error code "38169, when the reversal event of a port is set to do not monitor, can not be set to reverse the alarm", from the alarm error must be the existence of the alarm suppression or blocking action will report this error.

7: Try to inhibit the alarm suppression of the single board to do a suppression of the issue, and then change to not inhibit the issue, check the network element alarms, normal reporting, the problem is solved.

Root Cause

The alarm suppression on the network management side does not match the suppression state of the device, and the alarm on the device side is actually in the suppression state, so the device does not report the alarm, and then the network management does not report the alarm.

Solution

The network administrator reconfigures the alarm suppression state of the abnormal single board, and issues a new suppression and de-suppression command to the device, and then the alarm is reported normally.