Dear friend!
Please refer to the following information:
Common Causes of Failed TE Links
Common causes of failed TE links at the optical layer are as follows:
Cause 1: Alarms are generated at the optical interface where a failed TE link exists on the FIU board.
Cause 2: The board software does not match the NE software.
Cause 3: Physical fibers are connected inappropriately.
Cause 4: The nodes that are configured as pass-through nodes are upgraded as ASON nodes.
Common causes of failed TE links at the electrical layer are as follows:
Cause 1: Alarms are generated on the failed TE links on the OTU board.
Cause 2: The board software does not match the NE software.
Cause 3: Physical fibers are connected inappropriately.
Procedure
TE links at the optical layer
Cause 1: Check whether alarms that are intended for traditional WDM equipment are generated at the optical interface on the FIU board. If yes, handle these alarms by referring to the procedure for handling the alarms intended for traditional WDM equipment. For details about the procedure, see the Alarms and Performance Events Reference.
Cause 2: Check the NE software and the board software. Determine the board software that matches the NE software according to the Version Mapping Table. If the NE software does not match the board software, reload the board software.
Cause 3: Check whether certain physical fibers are connected inappropriately. If yes, rectify the connections.
If the TE links at both ends are disabled but a query of alarms shows that no abnormal alarms are generated, check whether fibers are connected inappropriately according to the network diagram.
Cause 4: If a pass-through node is upgraded as an ASON node, migrate all the services that pass through the node to another trail. After that, disable and then immediately enable the LMP protocols at the source and sink nodes of the services.
TE links at the electrical layer
Cause 1: Check whether alarms that are intended for traditional WDM equipment are generated at the OTU board where the failed TE link exists. If yes, handle these alarms by referring to the procedure for handling the alarms intended for traditional WDM equipment. For details about the procedure, see the Alarms and Performance Events Reference.
Cause 2: Check the NE software and the board software. Determine the board software that matches the NE software according to the Version Mapping Table. If the NE software does not match the board software, reload the board software.
Cause 3: Check whether certain physical fibers are connected inappropriately. If yes, rectify the connections.
If the TE links at both ends are disabled but a query of alarms shows that no abnormal alarms are generated, check whether fibers are connected inappropriately according to the network diagram.
More: Handling Failed TE Links
Thanks！
