Hello, everyone!
Today, I'd like to share a case with you.
Problem Description
On a ring where the OSN 3500 (NE C) is deployed, a new OSN 1500 (NE D) is connected to the C. When the OSN 1500 is created on the NMS, a message is displayed indicating that the background is busy and cannot be created.
Problem Analysis
1. In the ECC link management of the NE C and gateway NE A, you can see the OSN 1500 device. Therefore, the fault is not caused by the ECC failure of the OSN 1500 device.
2. Check whether parameters are set during the creation of the OSN 1500 device and whether the gateway NE and account password is set correctly.
3. When users view the manufacturing information and SDH performance of the C board on the NMS, frame freezing occurs or a message indicating a failure is displayed.
4. Check the distance between the gateway NE A and NE C. Check whether the ECC path of NE C is in the B direction of the NE. Check the board manufacturing information on the NE B. It is found that the query is normal.
5. Check the optical path between NE B and NE C. It is found that the optical power reaches the threshold and there are a large number of regenerator section and multiplex section bit errors.
6. Disable the DCC bytes of the optical board in the C direction on NE B so that the ECC route of the NE C is switched to the E direction of the NE. Then, create the OSN 1500 NE (NE D) normally.
7. On site, handle the optical path between NE B and NE C. After the bit errors are cleared, switch the ECC route of NE C back to the B direction of the NE. The test is normal.
Root Cause
The new OSN 1500 cannot be created because of bit errors on the line.
Solution Description
After the line bit errors are rectified, the communication is normal. Because bit errors occur on the NG-SDH, ECC routes are not switched. Therefore, when handling NE monitoring faults, you need to consider the monitoring exceptions caused by bit errors.
Welcome to leave a message below.
We study together.
Thank you!
