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>

Reminder

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

upgrade

Wrong parameter set in NQ2 lead to ODU0_PM_SSF alarm of TOG

Publication Date:  2012-07-25 Views:  56 Downloads:  0
Issue Description
A TN52TOG and TN54NQ2 placed in slot16 and slot5 of OSN8800 (V100R002C02SPC800), the TN52TOG report ODU0_PM_SSF alarm after configuring ODU0 between TN52TOG and TN54NQ2.The service is interrupted.

Alarm Information
TN52TOG report ODU0_PM_SSF alarm
Handling Process
1 Checked alarm, had no the other alarms in this NE.
2 Checked the parameter of NQ2; we found the Line Rate mode is Speedup Mode. Changed the parameter from     Speedup Mode to Normal Mode, the ODU0_PM_SSF alarm disappeared. The service is OK.
Root Cause
1 R-LOS,ODUk_TCMn_SSF, ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn_AIS, ODUk_TCMn_LTC, ODUk_TCMn_TIM or OTUk_TIM cause ODU0_PM_SSF.
2 the wrong parameter set in NQ2.

Suggestions
According to G.709 protocol, OUD0 service cannot map from ODU0 ---> ODU2e ---> OTU2v, so the Speedup Mode  of NQ2  lead to ODU0_PM_SSF alarm of TOG.

END