Query of the SNCP service configuration and protection switching on WDM devices

15

Choose <b>Function Tree</b> > <b>Configuration</b> > <b>WDM service management</b> > <b>SNCP service control</b> to query the WDM service configuration and protection switching status.

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.

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.

Service direction in ODUk SNCP protection
ODUk SNCP uses the dual feeding and selective receiving function of electrical-layer cross-connections to protect services on line boards and OCh fibers.

Method used to convert an SNCP service into a common WDM service
For details, see the related product documentation. Note that this conversion operation may interrupt services.

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.

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