Case-7: XC_UNSWITCH alarm at cross-connect board in OSN8800 DWDM NE

Tanjil
Tanjil  Platinum  (1)
6 years 5 months ago  View: 1233  Reply: 1
1F

Problem: XC_UNSWITCH alarm at cross-connect board in OSN8800 DWDM NE


Findings:

At first cold reset performed from NMS, but alarm not cleared. Even BD_STATUS alarm not reported.

Same happen after physical reset.

After NE data upload to NMS, alarm cleared.


Causes:

1.       The interruption of communication caused cross-connections could not be configured to cross connect boards, both of cross connect boards were started to report XC_UNSWITCH alarms.

2.       The cross-connect board or the line board fails to respond to the cross-connect matrix switching command issued by the NE software, and as a result is not updated with the cross-connect matrix configured by the NE software.

3.       The board reports communication alarms which cause failure and then check whether the XC_UNSWITCH alarm is cleared.


Solution:

The root cause is that there was not idle task to handle the alarm related work, then the data status in U2000 memory was disordered.  Users can upload the NEs to solve the problem temporarily.
Through the uploading operation, U2000 can restore the data status in U2000 memory

Tina.hu
Tina.hu  Gold 
6 years 5 months ago
2F

Dear Tanjil,

Thank you for your post. :)