When the LWC board receives the Ethernet POS service, an R_OOF alarm is generated intermittently on the LWC board is interconnected with the third-party equipment because the clock setting of the client data equipment is improper.
Symptom
On a WDM network(such as OSN6800, OSN8800), the SSEM4LWC01 boards are used at the ends and the TRC board is used as the regeneration board to establish the 2.5G IP circuit. In addition, the data equipment is used at both of the client sides. After services are added and run for a period, an R_OOF alarm is generated intermittently on both the client side and WDM side of the LWC, and the data equipment also reports bit errors. As a result, services are interrupted.
Cause Analysis
The clock of the data equipment is set to trace a line clock by default. The data equipment at both ends adopts the default settings, so the clocks are traced mutually. In this case, change the clock of the data equipment at one end to trace an internal clock to solve the problem.
Procedure
- Apply a self-loop at the WDM-side port on the data equipment, and it is found that the system is normal. Release the self-loop and restore the original fiber connection, the R_OOF alarm persists.
- On the WDM side of the LWC board, apply a self-loop between the IN and OUT ports by using a fiber jumper (an optical attenuator must be installed between the two ports). The data equipment runs normally and the LWC no longer reports the R_OOF alarm intermittently. Release the self-loop and restore the original fiber connection, the R_OOF alarm is reported intermittently again. This indicates that the board is normal.
- Check the data configuration of the data equipment. It is found that the clocks of the data equipment at both ends trace each other.
Reference Information
In the case of the traditional WDM equipment, the client equipment is generally required to provide clock data and the wavelength conversion board is required only to transmit the clock data transparently.
No comments:
Post a Comment