The LBE, LDG and LQG boards report the LINK_ERR or LINK_STATUS alarm.
Cause Analysis
The causes for the alarms must be ascertained before the correct solutions can be found.
Procedure
- The trigger conditions for the LBE or LBES board to generate the LINK_ERR alarm are as follows:
- The receive sequence (at the physical coding sublayer (PCS)) at the peer or local end is incorrect.
- The bit error ratio is extremely high.
- The synchronization frame is lost.
- Bit synchronization is lost.
- Signals are lost.
- The trigger conditions for the LOG board to generate the LINK_ERR alarm are as follows:
- Bit synchronization is lost.
- When auto-negotiation is enabled, the LINK_ERR alarm is reported if the auto-negotiation fails.
- When LPT is enabled, the board reports the LINK_ERR alarm if the service network is faulty or the peer board reports LINK_ERR.
- The trigger conditions for the LDG board to generate the LINK_STATUS alarm are as follows:
- Bit synchronization is lost.
- When auto-negotiation is enabled, the LINK_STATUS alarm is reported if the auto-negotiation fails.
- When LPT is enabled, the board reports the LINK_STATUS alarm if the service network is faulty or the peer board reports LINK_STATUS. When the optical interface on the client side is inlooped, neither LINK_ERR nor LINK_STATUS is reported.
- When no light is received on the client side, LINK_ERR or LINK_STATUS is suppressed because the R_LOS alarm is reported. If the client-side link is normal but no packet is sent or received, only ALM_DATA_RLOS or ALM_DATA_TLOS is reported.
No comments:
Post a Comment