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.


The NS2 Boards Report BUS_ERR Alarms When the ODU1SNCP Is Configured

Publication Date:  2012-07-25 Views:  75 Downloads:  0
Issue Description

Two OptiX OSN 6800 stations constitute a ring that uses the ODU1-SNCP protection.

The version of the OptiX OSN 6800 is both stations, slots 1 and 2 are configured with the NS2 boards, slot 3 is configured with the TQS, and slots 9 and 10 are configured with the XCS boards. The NS2 and XCS boards report BUS_ERR alarms simultaneously when the ODU1 is configured with the SNCP service. The BUS_ERR alarms remain active.

The NS2 boards report eight BUS_ERR alarms with the following parameters: 0X01 0X01 0X2F (0X2e, 0X2c, 0X2d, 0X40, 0X41, 0X42, 0X43)  0XFF.

The XCS boards report eight BUS_ERR alarms with the following parameters: 0X01 0X06 0X03 (0X02, 0X01, 0X00) 0XFF     0X01 0X03 0X03 (0X02, 0X01, 0X00) 0XFF.
Alarm Information
Handling Process

Change the service type at the TQS client to STM-16.

The alarms are cleared.

Configure the actual service.

The alarms are cleared.


Root Cause

When the TQS client adds the OTU1 service, the XCS and NS2 boards (cross connections are configured between these

boards and the TQS) report BUS_ERR alarms (because the PN11 alarm of the OTU1 is inserted into the TQS) if R_LOS, OTU1_LOF,

OTU1_LOM, or OTU1_AIS alarm exists at the TQS client.


1.         By default, the service type at the TQS is OTU1.

2.         This defect cannot be solved through software improvement because the defect exists in all versions (the description in case SC0000379631 is incorrect).

3.         Set the service at the TQS as STM-16 due to both the lack of OTU1 service requirements in the mainland of China and the version defects.