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>Search


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


Alarm message ODU_SNCP_STA_INDI on protection channel

Publication Date:  2012-07-25 Views:  129 Downloads:  0

Issue Description

Alarm message ODU_SNCP_STA_INDI is periodically apperared on protection channel on ODU_SNCP ring. On protection channels there is errors
Traffic on working channel have not any problems. If switch on protection channel - traffic have not any problem.

Alarm Information

Alarms on protection channels:

severity name alarm source location occurrence time(ct) cleared time(ct) type ne type affiliated subnet alarm parameters(hex)
minor odu_sncp_sta_indi vlm0156_15 / 1032-vlm0156_15_1 0-subrack-30-52ns3-71(odu2lp/odu2lp)-odu3:4 10/05/2011 16:31:17 10/05/2011 16:31:21 communication - centralnyj-filial  0xff 0xff 0xff 0xff 0xff
minor odu_sncp_sta_indi vlm0156_15 / 1032-vlm0156_15_1 0-subrack-30-52ns3-71(odu2lp/odu2lp)-odu3:3 10/05/2011 16:31:17 10/05/2011 16:31:21 communication - centralnyj-filial  0xff 0xff 0xff 0xff 0xff

Handling Process

We are checked version consystency - no any problem. Checked all protections boards performance and found that board have not any problems, all optical performance is normal, but board is really produce odu2_pm_bbe, odu2_pm_fesesr(%), odu2_pm_feses(s), odu2_pm_es(s) and this bad performance is exist only on protection channel.
We are ask consultation from R&D, they ask us collect some system data and answer us that TXSL boards is received from client side bad signal with frequency offset about 30ppm and 35ppm. According the standard, it should be ± 20ppm. And because our protection path have some synchronized subrack, so protection channel have bad performance and have odu_sncp_sta_indi alarms.
We are ask customer to check their external equipment connected to our DWDM network. Customer found that external equipment (datacom devices) have synchronized each other, that's why frequency offset was so bad. They has changed clock configuration for this equipment (one site is master, other is slave) and after this problem was solved.

Root Cause

Possible problem reasons:

1. Version consystency problem 
2. Some boards on protection channel have problem.
3. External equipment give us no-standart optical signal.


Some times external equipment signal quality can affec performance of our equipment. If you cannot find a reason for problem in our equipment you need check signal parameters of connected equipment. May be received signal does not belong to standart signal.