Mutiple IA5000s are reporting NE_COMMU_BREAK alarm very frequently

Dear friend!
To solve this problem completely, we must solve the fault indicated by this alarm.

Which NMS does they report such alarms?

Dear friend!
Multiple NEs repeatedly report this alarm. The possible causes are as follows:

1. The network scale is too large. As a result, the management channel between NEs is congested. As a result, the processing capability of the GNE is limited. You can add multiple GNEs to solve this problem.
2. Another NMS uses the same NE account to log in to the NEs. As a result, user login conflicts occur. You are advised to log in to an NE using only one account.
3. The communication between the NMS and GNEs and between GNEs and non-GNEs is unstable. You are advised to check whether the physical link is normal.
Thank you!

Hello, one of the reasons for this warning may be that the communication between the off-management alarm network element and the network management is interrupted.

Step 1: Check the ML-PPP port status of NE10 and find that there is no problem with the link and the business is normal all the time. Eliminate DCN channel quality problems.

Step 2: Check the network element IP of NE30 and find that the core route of a DCN channel is repeated with that of NE10. It is confirmed that the setting of NE30 network element IP is wrong.

Step 3: Change the network element IP of NE30 on the network management. After the prompt is returned successfully, it is found that the two network elements are still intermittently de-managed.

Step 4: Try to query the information of NE30 network element. The IP of NE30 network element is still the error value before modification. The operation of network administrator to modify the IP of NE30 network element is not successful.

Step 5: Repeat the operation of modifying NE30 network element IP several times until the intermittent network element de-piping failure disappears.

I hope I can help you.