L2VPN/3/hwL2vpnOamMismerge_active: OAM reported a Mismerge 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])
TTSI mismerge occurred after OAM received both correct and incorrect packets for three consecutive periods.
Parameter Name | Parameter Meaning |
---|---|
ServiceType |
Type of the service:
|
ProtocolType |
Type of the protocol:
|
VcID |
VC ID. |
VcType |
VC type. |
PeerAddr |
IP address of the peer. |
IfIndex |
Interface index. |
PwMaster |
PW identifier:
|
RmtSiteID |
Remote site ID. |
InLabel |
VC in-label. |
OutLabel |
VC out-label. |
IfName |
Interface name. |
VsiName |
VSI name. |
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.
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.
3. Run the display this command in the MPLS-OAM view to check MPLS OAM configurations.
4. Perform the troubleshooting operations described in hwPWVcDown and hwSvcDown to rectify the fault.
5. Collect alarm information and configuration information, and then contact technical support personnel.
6. End.