No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NEs Are Frequently Unreachable to the T2000 due to the Mutual Trace of the Clocks

Publication Date:  2012-07-25 Views:  53 Downloads:  0
Issue Description
The OptiX OSN 6800 NE is configured at the following stations: A (NE ID: 700/701), B (NE ID: 702/703), C (NE ID: 704/705), D (NE ID: 706/707), E (NE ID: 708), F (NE ID: 709/710). The six stations form a ring network. Station A is the OLA station, and the other stations are back-to-back OTM stations. At station B, NE 703 in the direction of station C is often unreachable to the T2000 and NE 702 in the direction of station A also sometimes unreachable to the T2000. 
Alarm Information
The NEs at station B are often unreachable to the T2000.  
Handling Process
1. At station B, the field engineers log in to NE 703 on site by using an Ethernet cable. When the engineers log in to NE 702 through NE 703, the communication fails from time to time. When NE 702 functions as the gateway NE, the same symptom occurs after the engineers log in to NE 703.
2. Shut down the ESCs on the OTU boards in NE 702 and NE 703 and the ESCs on other NEs, so that the supervisory is transmitted through the OSC. As a result, the fault persists.
3. The engineers run :cm-get-eccroute; command to query the ECC routing information of NE 702 and NE 703. Only NE 702 or NE 703 is displayed in the routing table, and other NEs are not displayed.
4. The engineers run the :cm-get-bdinfo;, cm-get-chaninfo; and cm-get-chanerror; commands separately to query the ECC port information of NE 702 and NE 703. It is found that two ports on the 5-SC2 boards of NEs 702 and 703 have the CR error, and the errors increase gradually. In the query of the SC2 current performance data, it is found that the CRC4 bit error exists.
5. The engineers apply a self-loop at the optical interface on the 5-SC2 boards of NEs 702 and 703. Check whether the CR errors stop increasing. If so, the board is normal.
6. The engineers check the clock configuration on site through the T2000. Clocks are set on the entire network. According to the fiber connection relation provided by the engineering documents, the clock on NE 709 is set as internal clock, NE 709/700/701/702/703 traces the clock on NE 710, and the clock on NE 708/707/706/705/704 traces the clock on NE 710 from another direction.
7. The engineers apply a self-loop at the optical interface on the SC2. It is found that the actual fiber connections differ from the fiber connections specified in the engineering documents. Hence, the clock setting on the existing network is incorrect. The clocks at stations B and C trace each other. The clock setting for other NEs may be also incorrect. After a confirmation with R&D, it is found that the clocks on the OptiX OSN 6800 need not be set. After the clocks on the entire network are set on site to Internal on the T2000, the problem is solved. 
 
Root Cause
1. All OTU boards in the OptiX OSN 6800 support ESC. If the function of the ESC on an NE is unstable, the NE may be unreachable to the T2000. In this case, turn off the ESC on all the OTU boards and force the supervisory data to be transmitted through the OSC.
2. As the NEs at two directions of station B are unreachable to the T2000, and the two SC2 boards have the CR and CRC4 errors. The probability that SCC boards or SC2 boards on the two NEs are faulty is low. Thus, this is common problem on the NE.
3. If two clocks trace each other, the availability of the ECC cannot be ensured. The fiber connections shown in the as-built document differ from the actual fiber connections of the equipment. As a result, relevant clocks trace each other. This problem is detected only when a self-loop is configured on the SC2 on site. This makes the troubleshooting more difficult.
4. In general, the clock need not be configured for the OptiX OSN 6800. The clock on the entire network is set to the free-run mode. The clock trace source needs to be set only when the orderwire is configured. 
 
Suggestions
Null

END