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>Search


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


The External Clock Configuration Is Invalid and Thus No Switching Occurs Because the Clock Modes Are Different in the NE Software Configuration and in the Jumper Configuration of the SCC

Publication Date:  2012-07-25 Views:  76 Downloads:  0
Issue Description
The clock priorities of the OptiX Metro 1000 V2 equipment (NE A) are as follows from high to low:
A. Trace the external lock on NE B through the line board.
B. Trace the external clock of NE A.
C. Trace the internal clock of NE A.
One day, the external clock was removed from NE B to verify clock protection switching. The locks on NEs A and B were not switched. After the whole-network clock tracing was queried again, the fault persisted and no alarm was available on the NMS and NE software. 
Alarm Information
Handling Process
Modify the DIP setting of the SCC. 
Root Cause
Check the DIP setting of the clock module on the SCC. The Bits mode is set. Then, use the command line to query the DIP setting of the NE software. The Hz mode is set on the NE software. In addition, it is confirmed that the two external clocks are of good quality. After 24 hours, however, the phenomenon persists and the clocks are not switched.
Therefore, it is confirmed that this fault is caused by an inherent defect of the OptiX Metro 1000 V2 equipment. When the working mode of the external clock of the OptiX Metro 1000 equipment is different in the jumper configuration and in the software configuration, the external clock fails but the system still reports that the clock is available. After the DIP setting of the SCC is changed to the same as that in the NE software configuration, the fault is rectified.
This fault exists in all versions. 
The DIP setting of the SCC must be the same as that in the software configuration.