L2VPN_1.3.6.1.4.1.2011.5.25.119.9.2.23 hwL2vpnOamMismatch

Trap Buffer Description

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])

The local and remote TTSIs were inconsistent.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Error
Mnemonic Code	hwL2vpnOamMismatch
Trap OID	1.3.6.1.4.1.2011.5.25.119.9.2.23
MIB	HUAWEI-L2VPN-OAM-MIB
Alarm ID	0x00003325
Alarm Name	hwL2vpnOamMismatch
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	L2VPN_1.3.6.1.4.1.2011.5.25.119.9.2.24 hwL2vpnOamMismatchClear

Trap Buffer Parameters

Parameter	Description
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.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.119.9.1.1	hwL2vpnServiceType	-
1.3.6.1.4.1.2011.5.25.119.9.1.2	hwL2vpnProtocolType	-
1.3.6.1.4.1.2011.5.25.119.9.1.3	hwL2vpnVcID	-
1.3.6.1.4.1.2011.5.25.119.9.1.4	hwL2vpnVcType	-
1.3.6.1.4.1.2011.5.25.119.9.1.5	hwL2vpnPeerAddr	-
1.3.6.1.4.1.2011.5.25.119.9.1.6	hwL2vpnIfIndex	-
1.3.6.1.4.1.2011.5.25.119.9.1.7	hwL2vpnPwMaster	-
1.3.6.1.4.1.2011.5.25.119.9.1.8	hwL2vpnRmtSiteID	-
1.3.6.1.4.1.2011.5.25.119.9.1.9	hwL2vpnInLabel	-
1.3.6.1.4.1.2011.5.25.119.9.1.10	hwL2vpnOutLabel	-
1.3.6.1.4.1.2011.5.25.119.9.1.11	hwL2vpnIfName	-
1.3.6.1.4.1.2011.5.25.119.9.1.12	hwL2vpnVsiName	-

Impact on the System

After OAM is deployed and an APS instance is bound to the PW protection group: - The service traffic will be switched from the primary PW to the secondary PW if OAM reports an alarm about the primary PW. - The service traffic will not be switched or affected if OAM reports an alarm about the secondary PW.

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.