When the LCAS function is not enabled on either the source NE or the sink NE, LCAS negotiation faults arise and the LCAS configuration fails if the bound path is configured before the cross-connect service is configured. You can rectify the fault by deleting the existing configurations at both ends and enabling the LCAS function at both ends.
Symptom
For the point-to-point NE A and NE B, the LCAS function is enabled at NE A but disabled at NE B. After the bound paths are configured for the data processing boards at both ends and the cross-connect service is configured from the data processing board to the line board, LCAS negotiation at NE A becomes abnormal, that is, all the timeslots are deleted or only one timeslot remains.
Cause Analysis
The fault arises owning to the version and working principles of the LCAS function. Hence, the following situations should be prevented:
- The LCAS function is disabled at one end.
- The bound paths are configured before the cross-connection service is configured.
Procedure
- Query the status of the LCAS function at both ends, and ensure that the function is enabled at both ends.
- Query the paths bound at both ends, and delete the existing configurations.
- Query and delete the cross-connect service configured between the data processing board and the line board.
- Configure the cross-connect service between the data processing board and the line board, and then configure the bound paths. The alarm disappears, and the troubleshooting is complete.
MORE BLOG:
No comments:
Post a Comment