Trigger conditions of ODUk SNCP switching


The conditions for triggering automatic ODUk SNCP switching are as follows:
The board cannot be detected (for example, the board is removed or undergoes a cold reset).
There are board alarms indicating SF and SD.

Other related questions:
ODUk SNCP protection switching conditions
ODUk SNCP is classified into SNC/I, SNC/N, and SNC/S. The difference between the three protection schemes lies in that they have different monitoring capabilities and therefore have different trigger conditions.

Whether LP_UNEQ is a condition for SNCP switching
Question: According to ITU-T suggestions, the standard LP_UNEQ alarm is inserted if no lower-order service is configured. However, some OSN devices cannot detect the LP_UNEQ alarm for triggering SNCP switching. Why? Analysis: Board hardware restrictions. Some boards can be upgraded to resolve the problem, whereas some cannot. Answer: No version of SSN1GXCSA, SSN1EXCSA, or SSQ1CXL supports LP_UNEQ detection.

Switching time of ODUk SNCP protection
The switching time of ODUk SNCP protection cannot exceed 50 ms, excluding the detection time.

Switching conditions of ODU0 SNCP protection
For SNC/N (PM), alarms in the SM and PM sections at the server layer and SF alarms in the PM section at the current layer are used as trigger conditions.

Precautions for selecting the SNCP type during ODUk SNCP configuration
When configuring ODUk SNCP protection, you are advised to set the SNCP type to SNC/N to enable non-intrusive monitoring on both the source and sink ends of the protection group. This setting facilitates network monitoring. In cascading or nested protection scenarios, however, you are advised to set the SNCP type to SNC/S.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top