NG-SDH Device Cannot Identify the G.811 Clock Quality

When the NG-SDH device is connected to the BITS clock source, the NG-SDH device cannot identify the clock quality. After the specified clock quality is set to a proper level, the fault is rectified.

Product

NG-SDH, OSN 3500

Fault Type

Synchronization clock loss

Symptom

When the NG-SDH device is connected to a BITS clock source (the clock source quality is G.811 clock quality), the NG-SDH device cannot automatically extract the clock configuration to identify the clock quality. When the clock quality is queried through the NMS, it is found that the clock source for synchronization is unavailable.

Cause Analysis

The clock quality of the device has a low priority. The BITS clock source quality cannot be identified in the phase-locked loop.

Procedure

1. In the main topology of the NMS, right-click the NE to be set, and then choose NE Explorer.
2. Choose Configuration > Clock > Clock Subnet Configuration from the Function tree.
3. On the Clock Quality > Clock Source Quality tab, select External Clock Source.
4. In the Configuration Quality field, right-click, and then choose G.811 Clock Signal.
5. Click Apply.
6. After the device is set to be synchronized with the external clock source, in the Configuration Quality field, right-click, choose Automatic Extraction, and then click Apply.
    NOTE:

   Querying clock synchronization status

   1. In the NE Explorer, choose an NE. Choose Configuration > Clock > Clock Synchronization Status from the Function Tree.
   2. Click Query to query the clock synchronization status from the NE.
7. Click Query, and confirm that the device can identify the clock quality in the Clock Source Quality.
    NOTE:

   If the queried result in step 7 is that the synchronization clock source is unavailable, set the configuration quality to G.811 Clock Signal.

Reference Information

The troubleshooting method of the device clock is as follows:

Determine whether the extended SSM protocol is enabled on the device. If the extended SSM protocol is not enabled, enable the protocol and specify the clock IDs of the external and internal clock sources. Make sure that the clock IDs in the subnet are unique.

How to do when Occasional Hot Patch Installation Failures?

when Ring MSP Configuration Failures on SSN1SLQ16 Boards on OSN 3500 Products

How to do when Bit Errors Occur in Lower Order Path Due to Improper Grounding