L2VPN_1.3.6.1.4.1.2011.5.25.119.2.2.1 hwKompellaVcDown

Trap Buffer Description

The status of the Kompella VC turned DOWN. (VcVpnName=[VcVpnName], CeId=[CeId], InterfaceIndex=[InterfaceIndex], RemoteCeId=[RemoteCeId], SecondaryVc=[SecondaryVc], HWL2VpnStateChangeReason=[HWL2VpnStateChangeReason], PeerAddress=[PeerAddress], TunnelPolicyName=[TunnelPolicyIndex], ActiveState=[ActiveState])

A BGP VC went Down.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	hwKompellaVcDown
Trap OID	1.3.6.1.4.1.2011.5.25.119.2.2.1
MIB	HUAWEI-KOMPELLA-MIB
Alarm ID	0x00F1008b
Alarm Name	hwKompellaVcDown
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	L2VPN_1.3.6.1.4.1.2011.5.25.119.2.2.2 hwKompellaVcUp

Trap Buffer Parameters

Parameter	Description
VcVpnName	MPLS L2VPN instance name
CeId	ID of the local CE
InterfaceIndex	Index of an AC interface
RemoteCeId	ID of the remote CE
SecondaryVc	Secondary VC
HWL2VpnStateChangeReason	Reason of the VC status change
PeerAddress	Peer IP address of the PW
TunnelPolicyIndex	Name of the tunnel policy used by the PW
ActiveState	PW forwarding status

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.119.2.1.4.1.8	hwKompellaVcSecondary	hwKompellaVpnName hwKompellaCeID hwKompellaVcIfIndex hwKompellaVcRmtCeID
1.3.6.1.4.1.2011.5.25.119.2.1.10	hwKompellaVcStateChangeReason	-
1.3.6.1.4.1.2011.5.25.119.2.1.4.1.27	hwKompellaVcPeerAddr	hwKompellaVpnName hwKompellaCeID hwKompellaVcIfIndex hwKompellaVcRmtCeID
1.3.6.1.4.1.2011.5.25.119.2.1.4.1.6	hwKompellaVcTnlPolicyName	hwKompellaVpnName hwKompellaCeID hwKompellaVcIfIndex hwKompellaVcRmtCeID
1.3.6.1.4.1.2011.5.25.119.2.1.4.1.18	hwKompellaVcIsActive	hwKompellaVpnName hwKompellaCeID hwKompellaVcIfIndex hwKompellaVcRmtCeID

Impact on the System

Services will be interrupted.

Possible Causes

Cause 1: Invalid reason type.
Cause 3: Local VC Deleted.
Cause 24: Tunnel was Down.
Cause 43: BFD for pw status changed to Down.
Cause 47: Manual set was enabled.
Cause 94: PW or AC token exceed.

Procedure

Cause 1: Invalid reason type.
1. Collect alarm information and configuration information, and then contact technical support personnel.

2. End.
Cause 3: Local VC Deleted.
1. Check whether the VPWS connection needs to be deleted.
- If the VPWS connection needs to be deleted, go to Step 4.
- If the VPWS connection does not need to be deleted, go to Step 2.
2. Run the connection command to re-establish the VPWS connection. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.
Cause 24: Tunnel was Down.
1. Run the display mpls l2vpn connection interface interface-type interface-number command to check whether the PW has a tunnel ID.
- If the tunnel ID exists, go to Step 3.
- If the tunnel ID does not exist, go to Step 2.
2. Check whether the public network interface is Down. If it is Down, bring it Up and then run the display tunnel-info all command to check the tunnel status. After the tunnel goes Up, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.
Cause 43: BFD for pw status changed to Down.
1. Perform the troubleshooting operations described in hwBfdSessDown to rectify the fault. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm persists, go to Step 2.
2. Collect alarm information and configuration information, and then contact technical support personnel.

3. End.
Cause 47: Manual set was enabled.
1. Run the display this command on the AC interface to check whether the manual-set pw-ac-fault configuration exists.
- If the configuration exists, go to Step 2.
- If the configuration does not exist, go to Step 3.
2. Run the undo manual-set pw-ac-fault command to delete the configuration and then check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.
Cause 94: PW or AC token exceed.
1. Collect alarm information and configuration information, and then contact technical support personnel.