No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


Incorrect Service Configuration Causes an ODU1 SNCP Switching Failure

Publication Date:  2012-07-24 Views:  97 Downloads:  0
Issue Description
A new OSN 6800 is deployed. The TQS and NS2 are used to configure ODU1 SNCP. After services are configured, SNCP switching fails.
NEs A-B-C-D-E-A form a 10 Gbit/s WDM ring network. All NEs are OADM sites.
The services in a wavelength are activated between NE A and NE B by using 192.1 THz. The NS2 in slot 11 is active and that in slot 12 is standby on NE B. The TQS in slot 1 is a tributary board.
After services are configured, the meter tests that NE B is normal. Remove the IN fiber on the NS2 in slot 11 on NE B. The meter shows LOS and the NS2 in slot 12 reports an ODU1_PM-BDI alarm. The corresponding NS2 on NE A reports an ODU1_PM-OCI alarm.
The NE software is and T2000 version is V2R4C01B024.                   
Alarm Information
ODU1_PM-BDI, ODU1_PM-OCI, and no ODU_SNCP_PS            
Handling Process
1. If there is no ODU_SNCP_PS alarm, no SNCP switching occurs.
2. Check the networkwide electrical cross-connect service configuration and networking diagram. The standby channel passes the ODU1 electrical repeater and sub-wavelength SNCP services at all sites are SNC/I.
3. Change the SNCP service type to SNC/N and enable non-intrusive monitoring of PM overheads.
4. Perform a switching test again. The switching succeeds.             
Root Cause
1. When there is an ODU1 electrical repeater, SNC/N sub-wavelength SNCP services must be configured. In addition, the non-intrusive monitoring function of the PM overhead should be enabled.
2. SNC/I just monitors overheads at the SM layer, while SNC/N monitors overheads at SM and PM layers.             
Perform SNCP tests on a newly deployed site as specified.