Analysis on the cause that the T2000 reports the OSC_RDI alarm in the case of a fiber break

In the case of a fiber break, if a user logs in to the same NE through different client computers, the OSC_RDI alarm is reported automatically because of alarm synchronization.

Product

OptiX OSN3500

OptiX OSN7500

Fault Type

Optical Supervisory Channel Unit

OSC_RDI

Symptom

On one DWDM link, there are two OptiX Metro 6100 NEs, namely, NE A and NE B. NE A and NE B are connected to different T2000 clients.

One of the two fibers between NE A and NE B is broken. As a result, the SC1 board on NE B reports the R_LOS alarm, but no alarm is generated on NE A.

To check the optical power, the user exits from NE B on the T2000 connected to NE B, and then logs in to NE B remotely through NE A. In this case, both the T2000 client connected to NE A and the T2000 client connected to NE B report the OSC_RDI.

Cause Analysis

In general, automatic reporting of the OSC_RDI alarm is disabled by default. It is not reported unless the alarm synchronization function is enabled. Otherwise, the OSC_RDI alarm does not appear on the T2000 and thus is not reported. In this example, users from different T2000 clients have logged in to NE A. As a result, automatic synchronization of the alarms on the NE and the alarms on the T2000 is enabled. Thus, the NE reports the OSC_RDI alarm to the T2000.

Procedure

1. In the case of a fiber break, do not log in to the same NE from two clients to prevent such a problem.

Result

The problem is solved after the operation is finished as the requests.

Reference Information

None.

How to do when Failing to Connect the 155 Mbit/s Optical Port on the Router of Company C

TD Alarms Falsely Reported by Some Boards Using Pluggable Optical Modules in WDM Products

Interconnection Between the OLT and the Switch Fails