Monday, June 27, 2016

The TDX Board Reports the BUS_ERR Alarm When Cross-Connections Are Configured on the Board Because the Service Type of the Board Is Not Set

The TDX board reports the BUS_ERR alarm when cross-connections are configured on the board because the service type of the board is not set.

Fault Type

Electrical Cross-connection
Tributary Unit and Line Unit
BUS_ERR

Symptom

When the ODU2 cross-connections between the TDX and ND2 boards in the OptiX OSN 6800 on a network are configured, the boards report the BUS_ERR alarm.

Cause Analysis

This problem occurs when the input service type of the board is not set before cross-connections are configured on the board. The problem, however, does not affect the normal operation of the boards on the network.

Procedure

  1. Replace the TDX board to check whether it is faulty. The BUS_ERR alarm, however, persists after the board is replaced.
  2. Reseat the TDX board to check whether it is loose in its slot. The BUS_ERR alarm, however, persists after the board is reseated.
  3. Test the WDM-side signal rates of the TDX and ND2 boards. The test result shows that the WDM-side signal rate of the TDX board is 11.1 Gbit/s while that of the ND2 board is 10.7 Gbit/s. When the cross-connections between the TDX and ND2 boards are configured, the TDX board receives signals at a rate of 11.1 Gbit/s while the rate of the signals sent from the ND2 board is 10.7 Gbit/s. As a result, the boards report the BUS_ERR alarm. If the service type of the TDX board is set to STM-64, the TDX board receives signals at a rate of 11.1 Gbit/s and the problem is solved.

Result

Currently, only the TN12TDX, TN11TQX, TN11ND2, and TN12NS2 boards report the BUS_ERR alarm in the preceding case. These boards support ODU2 cross-connections.
Therefore, the input service type of the TDX board should be set before ODU2 cross-connections are configured on the board.

No comments:

Post a Comment