MPLS-OAM/3/hwMplsOamBidirectionalTunnelUnAva

Message

MPLS-OAM/3/hwMplsOamBidirectionalTunnelUnAva: BidirectionalTunnel enter unavaliable. (TunnelIndex=[TunnelIndex], AvailableState=[AvailableState], DefectType=[DefectType], BdiDefectType=[BdiDefectType])

Description

OAM detected that the static bidirectional co-routed LSP was unavailable.

Parameters

Parameter Name Parameter Meaning

TunnelIndex

Indicates the ID of a MIB object.

AvailableState

Indicates the availability state of an OAM. - 0: Available - 1: Unavailable

DefectType

Indicates the type of the defect: - 0: Indicates no defect. - 1: Indicates the server layer defect arising below the MPLS network layer. - 2: Indicates the peer maintenance entity defect arising outside the MPLS sub-network. - 3: Indicates the defect of the packet loss for the connectivity detection. - This defect occurs if no FDI packet is received from the server layer or lower level LSP, and no CV or FFD packet with expected TTSI is received. - For the LSP that is detected by the CV packet, the egress LSR does not receive the expected CV packet in 3 consecutive seconds. - For the LSP that is detected by the FFD packet, the egress LSR does not receive the expected FFD packet in any period of three consecutive intervals for sending the FFD packet. - If there is an incoming FDI packet from the server layer, the defect type is set to dServer; if there is an incoming FDI packet from the lower level LSP within the MPLS network, the defect type is set to dPeerMe. In both cases, no more defects occur on this LSP. - 4: The defect of mismatching TTSI. This defect occurs when unexpected and no expected TTSI is carried in the incoming CV or FFD packets. - For the LSP that is detected by the CV packet, the egress LSR receives the CV or FFD packet with unexpected TTSI in 3 seconds and does not receive the CV packet with the expected TTSI. - For the LSP that is detected by the FFD packet, the egress LSR receives the CV or FFD packet with unexpected TTSI in any period of three consecutive intervals and does not receive the FFD packet with expected TTSI. - 5: TTSI mismerge defect. - For the LSP that is detected by the CV packet, the egress LSR receives the CV or FFD packet with the unexpected TTSI and the CV packet with the expected TTSI in of 3 seconds. - For the LSP that is detected by the FFD packet, the egress LSR receives the CV or FFD packet with unexpected TTSI and the FFD packet with the expected FFD packet in any period of three consecutive intervals. - 6: Receiving excess rate of CV or FFD OAM packets. - For the LSP that is detected by the CV packet, the egress LSR receives five or more than five CV packets with expected TTSI in 3 seconds. - For the LSP that is detected by the FFD packet, the egress LSR receives five or more than five FFD packets with expected TTSI in the period of three consecutive intervals. - 7: An unknown defect that is detected in the MPLS layer and affects the user plane traffic. This defect is not detected by MPLS OAM; it is reported to MPLS OAM. - 8: OAM Ingress Down.

BdiDefectType

Indicates the BDI defect type.

Possible Causes

The static bidirectional co-routed LSP monitored by OAM entered the unavailable state, and the MEP did not receive CCMs from the RMEP within five consecutive intervals.

Procedure

1. Run the display interface tunnel command to check whether the link is Up.

  • If the link is Up, go to Step 2.
  • If the link is Down, go to Step 3.

2. Run the display interface command to check whether any physical interface connected to the MPLS TE tunnel is shut down.

  • If any physical interface connected to the MPLS TE tunnel is shut down, go to Step 5.
  • If no physical interface connected to the MPLS TE tunnel is shut down, go to Step 3.

3. Run the display this command in the MPLS OAM view to view the MPLS OAM configuration, and run the display mpls oam bidirectional-tunnel command in the system view to view the LSP configuration. Based on the outputs of the preceding commands, check whether the MPLS OAM and LSP configurations are consistent.

  • If they are consistent, go to Step 4.
  • If they are inconsistent, go to Step 5.

4. Collect log information and configuration information, and then contact technical support personnel.

5. End.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >