SDH ASON failure by low Order Cross-Connect in OSN7500 & Hardware Upgrade of Cross-connect Board
Hi ,
Today I want to share with you a case, about SDH-ASON failure by Low order Cross-Connect capacity and Hardware Upgrade of Cross-connect Board in OSN7500.
Description
- As we Upgrade our network into MS-OTN , we still have a big legacy network, that depends mainly on SDH , the network is based on Huawei OSN7500 - V100R010C03 in the core level, which provision several types of services and protection like SDH ASON.
The problem cause
- The SDH cross-connection is low level in VC12,VC3 or high level in VC4, when fiber cut and ASON protection happens, some VC4 Trail Server that start or end (add or drop) from a specific NE fail to change the route, As ASON needs to create new VC12 services from this NE .
- After checking remaining cross-connect capacity in this NE, we found that only a few VC12 service still available.


Site before Upgrade
Solution
- To best solve for the problem is to change the cross-connect board with higher capacity and capabilities, In our NE the used was UXCSA and the new one is IXCSA.
Procedures and steps of Hard upgrade
1-Make sure of the software version and compatibility of the new boards.
2-Upload NE data to server.
3-Make a backup to the server and to the NE (GSCC board).
4-Delete the Standby cross-connect board usually (slot-10).
5-Ask the personnel on-site to change the UXCSA with the IXCSA.
6-The board indicator SRV lights up when the IXCSA is online, and an alarm (HSC_UNIVAIL) should appear , Wait for about 10 minutes after the install of the new board and make sure that the alarm (HSC_UNIVAIL) has disappeared.
7-Make a switch for the Main board usually (slot-9) to the standby Cross-connect.
8- Delete the Standby cross-connect board (slot-9).
9-Ask the personnel on-site to change the UXCSA with the IXCSA.
10-An alarm (HSC_UNIVAIL) should appear , Wait for about 10 minutes after the install of the new board and make sure that the alarm (HSC_UNIVAIL) has disappeared.

site after change

11-Perform a consistency check from Configuration > NE Configuration Data Management , make sure that there is no change in the data between server and NE.
12-Restore Active/ Standby Switching of Cross Connect board using NCE.
Welcome to feedback


