L2VPN/3/hwL2vpnOamMismatch_active

Message

L2VPN/3/hwL2vpnOamMismatch_active: OAM reported a Mismatch alarm. (ServiceType=[ServiceType], ProtocolType=[ProtocolType], VcID=[VcID], VcType=[VcType], PeerAddr=[PeerAddr], IfIndex=[IfIndex], PwMaster=[PwMaster], RmtSiteID=[RmtSiteID], InLabel=[InLabel], OutLabel=[OutLabel], IfName=[IfName], VsiName=[VsiName])

Description

The local and remote TTSIs were inconsistent.

Parameters

Parameter Name	Parameter Meaning
ServiceType	Type of service: - 0: VLL - 1: VPLS
ProtocolType	Type of protocol: - 0: SVC - 1: LDP - 2: BGP (not supported)
VcID	VC ID.
VcType	VC type.
PeerAddr	IP address of the peer.
IfIndex	Interface index.
PwMaster	PW identifier: - 1: primary PW - 2: secondary PW
RmtSiteID	Remote site ID.
InLabel	VC in-label.
OutLabel	VC out-label.
IfName	Interface name.
VsiName	VSI name.

Possible Causes

Cause 1: MPLS OAM configurations were incorrect.
Cause 2: The PW detected by OAM became faulty.

Procedure

The troubleshooting procedure is as follows: 1. Run the display mpls l2vc or display mpls static-l2vc command to check whether the status and type of the PW fault are consistent with that reported by the alarm. If they are consistent, go to Step 2. If they are inconsistent, go to Step 5. 2. Run the display mpls oam l2vc all verbose command to check whether the status and type of the MPLS OAM fault are consistent with that reported by the alarm. If they are consistent, go to Step 3. If they are inconsistent, go to Step 5. 3. Run the display this command in the MPLS-OAM view to check MPLS OAM configurations. If the configurations are correct, go to Step 4. If the configurations are incorrect, go to Step 5. 4. Perform the troubleshooting operations described in hwPWVcDown and hwSvcDown to rectify the fault. If the fault is rectified, go to Step 6. If the fault persists, go to Step 5. 5. Collect alarm information and configuration information, and then contact technical support personnel. 6. End.