Dears, I want to share with you a problem that I had with the alarm active in the MDU MA5616 and MA5628.

 

MA5628 

---

In the U2000 we could found that an alarm appears but these ports never were used. If you acknowledge
and clear the alarms from the U2000, after sync the device the alarms appear again.
Please check the following details:

 

By telnet you could check the alarms active with the following command: “display alarm active all list”

 

And you could see that this alarm is active in the device 

To clear this alarm you should execute the command: “alarm active clear all”

 

 

After that you could check that the alarm in the equipment disappear and in the U2000 automatically sync the device and now the site appear
“Green” without alarms

 
 

In the alarms details you could see that the alarm was clear by the NE operator (by the device)

 

MA5616

---

 

In this case is a similar case, but in this case appear other alarms in the ETH ports ETH 1 to 7 that are not in use.

 

We should follow the same procedure that before and the alarms were cleared.  

IMPORTANT: This command doesn’t disable the alarms; only clear the active alarms that sometime were active on the
device and never were cleared in the device. 
 

To evade this problem in a future new equipment execute the command “alarm active clear all” before to add the equipment in the U2000.

 

Good post.

There are too many alarms in the system indeed.

Thank you for sharing.

Cool! thansk for your detailed post,very useful!!

Good post! Very detailed information.

To prevent alarms of events of specific ports or slots, you can also use the command trap filter. After using trap filter on the CLI interface, the filtered alarms and events will not appear on the device CLI or U2000 manager.

This command is usually used during commissioning. Before the service is deployed, the alarms and events need not be handled. So we filtered them on the un-used ports or slots. After everything is ready, we run the command undo trap filter. Then the alarms and events can be displayed on the CLI and U2000, which help us moniter the service fault.