Whether LP_UNEQ is a condition for SNCP switching


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?
Board hardware restrictions. Some boards can be upgraded to resolve the problem, whereas some cannot.
No version of SSN1GXCSA, SSN1EXCSA, or SSQ1CXL supports LP_UNEQ detection.

Other related questions:
Whether the SNCP and ASON conflict
Whether the SNCP and ASON conflict: VC4 SNCP services can be directly upgraded to diamond services and do not need to be deleted.

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.

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.

Relationship between the switching detection time of ODUK SNCP protection and a fast SD protection switching condition
The switching detection time (unit: 10 ms) described in the product documentation is used in cascading scenarios. The SD enable status for protection determines whether protection switching is triggered when an SD condition is detected. Fast SD protection switching is based on bit errors and implemented by setting the DEG detection time window (ms) of the SM overhead.

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.

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