Method used to change the protection type from SNCP/I to SNCP/N

4

Conversion between SNCP protection types is not allowed. You need to convert the SNCP service into a common service, and convert the common service into the desired type of SNCP service.

Other related questions:
ODUk SNCP protection of the SNC/N type
ODUk SNCP (SNC/N) protects services against defects detected at the ODUk path (ODUkP) layer or ODUk TCM (ODUkT) sub-layers in E2E mode. It detects defects at the ODUk layer itself. The connection may be directly monitored by use of listen-only (non-intrusive) monitoring of the original characteristic information.

Selection of the SNCP protection type during configuration of the ODUk SNCP protection on TOM boards
1. SNC/I: SNC protection for inherent monitoring (1) Description: This method protects services (for example, server-layer trails and server/ODUk adaptation) against defects detected on the ODUk link. No defect detection is performed at the ODUk layer itself. Connections are indirectly monitored by using the data that is inherently available from the server-layer network. (2) Application scenario: a. The subnet that ODUk signals traverse does not have an electrical regeneration site. b. The tributary boards can receive any client-side services. 2. SNC/N: SNC protection for non-intrusive monitoring (1). Description: This method protects services against defects detected at the E2E ODUk path (ODUkP) layer or ODUk TCM (ODUkT) sub-layers. Defect detection is performed at the ODUk layer itself. The connections are directly monitored by use of listen-only (non-intrusive) monitoring of the original characteristic information. (2) Application scenario: a. No limit is set on the type of sites in the subnet where ODUk signals traverse. b. In case of SNC/N (PM), it is recommended that tributary boards receive non-OTN services. In case of SNC/N (TCM), tributary boards can receive any client-side services. 3. SNC/S: SNC protection for sub-layer monitoring (1) Description: This method protects services against defects detected at the TCM sub-layer (ODUkT) of the ODUk protection. Switching can be triggered only by defects of the protected domain. An ODUk fault cannot trigger protection switching. (2) Application scenario: a. No limit is set on the type of sites in the subnet where ODUk signals traverse. b. Tributary boards can receive any client-side services.

Method used to modify the SNCP protection mode
Question: SNCP protection uses the SNC/I mode, which processes only the SM overhead. When the SNC/I mode is used to protect pass-through services, there is a bug in this mode, and you need to change this mode to the SNC/N mode to protect trunk or pass-through services. Answer: 1. Convert SNC/I protection services into common cross-connections. 2. Enable PM non-intrusive monitoring. 3. Convert the common cross-connections into SNCP services.

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.

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