Precautions for selecting the SNCP type during ODUk SNCP configuration

19

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.

Other related questions:
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.

ODUk SNCP service configuration procedure
ODUk SNCP service creation by trail: (1) Configure TCM overheads of the line board. (2) Set board parameters. (3) Create a client trail. (4) Create ODUk SNCP protection. (5) Check ODUk SNCP protection status. ODUk SNCP service creation by single site: 1. Configure ODUk SNCP protection at the transmit site. (1) Configure OTN overheads of the line board. (2) Set board parameters. (3) Create ODUk SNCP protection. 2. (Optional) Configure an electrical regeneration site. (1) Set board parameters. (2) Create bidirectional electrical cross-connection services. 3. Configure ODUk SNCP protection of the receive site. 4. Check ODUk SNCP protection status.

ODUk SNCP protection of the SNC/I type
ODUk SNCP (SNC/I) protects services against defects detected at the ODUk link connection (such as server layer trails and server/ODUk adaptation functions). It does not detect defects at the ODUk layer itself. Connections may be indirectly monitored by using the data that is inherently available from the server layer network.

Procedure for configuring ODUk SNCP services
The procedure for configuring ODUk SNCP services is as follows: 1. Determine the type of the ODUk SNCP to be configured. 2. Configure the OTN overheads for line boards. 3. Create an SNCP service.

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.

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