Hello, everyone!
Today will share with you a case about wrongly patch cord connection between the WSS board which makes the OCH down.
Problem Description
The service belongs to the ASON optical layer network and the och just from site A to site B (there's no path-through site )but after creating the NS4 line board report R_LOS alarm, Och down.
Handling procedure
1. Through R_LOS alarm on NS4, that we can be determined that the och path not working and the issue is on the optical route.
2. Because of its ASON so before trouble-shooting we lock the route,
Then take one site close the optical laser to Check the optical power changes point of the multiplexed wavelengths. and also another site
Based on the comparison of optical power changes of multiplexed wavelengths, Huawei preliminarily determined that the fault was located between two WSS boards.
3. Check the NS4 line board parameter config and confirm that the new och take lambda 60.
4. Take the OPM8 board free port connects to the first WSS20 board port MONI which is on the TX route directly to scan the Lamba 60 we can get it.
5. Take the OPM8 scan of the lambda 60 on the second WSS20 board MONO port which TX route directly but we can't get the lambda. as the following picture.
6. Query the service configuration check one by one confirm that the port on WSS20 board which is used by this OCH there were no others, so it's the first use by our OCH.
7. After changing the patchcord between the first and second WSS20 AM/DM port then on the second WSS20 MONO and the third WSS20 MONI port we can get the lambda 60 but on the fourth still can't.
8. Check and confirm that the och between the third and fourth WSS20 AM/DM port it's new also.
9. Repeat step 4-8 to check another directly get the same result.
Root cause
The patch cord between the AM and DM ports between two WSS20 boards at the site is incorrectly connected.
Solution
Re-connect the patchcord between AM and DM port on different WSS20 board in site
That's all! Hope you find my post useful. Please let me know in the comment section if you have any further concerns or remarks.
Thank you!
