L2VPN_1.3.6.1.4.1.2011.5.25.119.4.1.2.3 hwPWVcDown

Trap Buffer Description

The status of the PWE3 VC turned DOWN. (VcId=[VcId], VcType=[VcType], PeerAddress=[PeerAddress], InterfaceIndex=[InterfaceIndex], VcInboundLabel=[VcInboundLabel], VcOutboundLabel=[VcOutboundLabel], SecondaryPw=[SecondaryPw], HWL2VpnStateChangeReason=[HWL2VpnStateChangeReason], SysUpTime=[SysUpTime], InterfaceName=[InterfaceName], SwitchVcId=[SwitchVcId], TunnelPolicyName=[TunnelPolicyName])

Indicates that a VC of the PWE3 goes Down.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	hwPWVcDown
Trap OID	1.3.6.1.4.1.2011.5.25.119.4.1.2.3
MIB	HUAWEI-PWE3-MIB
Alarm ID	0x0d4c0001
Alarm Name	hwPWVcDown
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	L2VPN_1.3.6.1.4.1.2011.5.25.119.4.1.2.4 hwPWVcUp

Trap Buffer Parameters

Parameter	Description
VcId	VC ID.
VcType	VC type.
PeerAddress	IP address of a peer.
InterfaceIndex	AC interface index.
VcInboundLabel	Incoming label of a VC.
VcOutboundLabel	Outgoing label of a VC.
SecondaryPw	Flag indicating whether the PW is a secondary PW: 1: secondary PW. 2: non-secondary PW.
HWL2VpnStateChangeReason	Cause of the VC status change.
SysUpTime	System startup time.
InterfaceName	AC interface name.
SwitchVcId	Switch VC ID.
TunnelPolicyName	Name of a tunnel policy.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.4	hwPWVcPeerAddr	hwPWVcID hwPWVcType
1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.15	hwPWVcIfIndex	hwPWVcID hwPWVcType
1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.6	hwPWVcInboundLabel	hwPWVcID hwPWVcType
1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.7	hwPWVcOutboundLabel	hwPWVcID hwPWVcType
1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.27	hwPWVcSecondary	hwPWVcID hwPWVcType
1.3.6.1.4.1.2011.5.25.119.4.1.1.8	hwPWVcStateChangeReason	-
1.3.6.1.2.1.1.3	sysUpTime	-
1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.49	hwPWVcIfName	hwPWVcID hwPWVcType
1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.9	hwPWVcSwitchID	hwPWVcID hwPWVcType
1.3.6.1.4.1.2011.5.25.119.4.1.1.1.1.23	hwPWVcTnlPolicyName	hwPWVcID hwPWVcType

Impact on the System

The PWE3 service is interrupted and traffic is blocked.

Possible Causes

Cause 1: Invalid reason type.
Cause 3: Local VC Deleted.
Cause 4: LDP Session Down.
Cause 6: Same LDP mapping was received with different label and MTU.
Cause 8: LDP mapping was received with mismatching interface parameters.
Cause 12: New LDP mapping message was received but remote VC or local VC is Down.
Cause 13: LDP Withdrawn Received.
Cause 14: LDP release message was received.
Cause 19: Interface Down.
Cause 20: Encapsulation changed.
Cause 24: Tunnel was Down.
Cause 31: LDP Notification Not-Forwarding.
Cause 32: PW was recreated.
Cause 41: Local PSN Fault.
Cause 43: BFD for pw status changed to Down.
Cause 47: Manual set was enabled.
Cause 60: MTU Unmatched.
Cause 94: AC or PW token exceed.

Procedure

Cause 1: Invalid reason type.
1. Check whether the alarm alarm-name hwPWVcDown initial-startup enable command has been run.
- If so, go to Step 2.
- If not, go to Step 4.
2. Check whether the service is newly created.
- If so, go to Step 3.
- If not, go to Step 4.
3. Complete the service configuration according to the product manual. Then, check whether the alarm is cleared.
- If so, go to Step 5.
- If not, go to Step 4.
4. Collect alarm information and configuration information, and then contact technical support personnel.

5. End.
Cause 3: Local VC Deleted.
1. Confirm that whether the VPWS connection is need to be deleted.
- If so, go to Step 4.
- If not, go to Step 2.
2. Recreate the VPWS connection. Then, check whether the alarm is cleared.
- If so, go to Step 4.
- If not, go to Step 3.
3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.
Cause 4: LDP Session Down.
1. Run the display mpls ldp session command to check the status of the LDP session to the remote end. If the LDP session of the peer does not exist, or the LDP session is not in Operational state, restore the status of the LDP session. Then, check whether the alarm is cleared.
- If so, go to Step 3.
- If not, go to Step 2.
2. Collect alarm information and configuration information, and then contact technical support personnel.

3. End.
Cause 6: Same LDP mapping was received with different label and MTU.
1. Run the reset pw command to reset local PW. Then, check whether the alarm is cleared.
- If so, go to Step 3.
- If not, go to Step 2.
2. Collect alarm information and configuration information, and then contact technical support personnel.

3. End.
Cause 8: LDP mapping was received with mismatching interface parameters.
1. Run the display mpls l2vc interface interface-type interface-number command to check whether the MTU is same of local PW and remote PW. If the interface is ATM or TDM, check whether the parameters of the interfaces is same.
- If so, go to Step 3.
- If not, go to Step 2.
2. Make sure the MTU and parameters of the ATM or TDM interfaces is coincident. Then, check whether the alarm is cleared.
- If so, go to Step 4.
- If not, go to Step 3.
3. Contact technical support personnel.

4. End.
Cause 12: New LDP mapping message was received but remote VC or local VC is Down.
1. Run the display mpls l2vc command to check whether the MTUs of the local and remote PWs are the same. If the interface is an ATM or TDM interface, check whether the interface parameters are consistent.
- If yes, go to Step 3.
- If not, go to Step 2.
2. Reconfigure the MTUs to be the same and modify the parameters of the ATM or TDM interfaces to be the same. Then, check whether the fault is rectified.
- If the fault is rectified, go to Step 4.
- If the fault persists, go to Step 3.
3. Collect alarm and configuration information, and contact technical support engineers.

4. End.
Cause 13: LDP Withdrawn Received.
1. Check whether the VPWS connection is need to be deleted by manual. If not, run the mpls l2vc command to restore the connection. Then, check whether the alarm is cleared.
- If so, go to Step 3.
- If not, go to Step 2.
2. Collect alarm information and configuration information, and then contact technical support personnel.

3. End.
Cause 14: LDP release message was received.
1. Run the display mpls l2vc command to check whether the control words configured on the local and remote ends are the same. If the interface is an ATM or TDM interface, check whether the interface parameters are consistent.
- If yes, go to Step 3.
- If not, go to Step 2.
2. Reconfigure the control words to ensure that the control words at both ends of the PW are the same. In addition, modify the parameters of the ATM or TDM interface to be the same. Then, check whether the fault is rectified.
- If the fault is rectified, go to Step 4.
- If the fault persists, go to Step 3.
3. Collect alarm and configuration information, and contact technical support engineers.

4. End.
Cause 19: Interface Down.
1. Run the display mpls l2vc interface interface-type interface-number command to check the status of the AC interface.
- If the AC state is Down, go to Step 2.
- If the AC state is Up, go to Step 3.
2. Run the display interface interface-type interface-number command to view the physical and link status of the interface. If the status of the interface is Down, restore the physical and link status to Up. Then, check whether the alarm is cleared.
- If so, go to Step 4.
- If not, go to Step 3.
3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.
Cause 20: Encapsulation changed.
1. Run the display mpls l2vc command to check whether the local and remote PW encapsulation types are the same.
- If they are the same, go to Step 2.
- If they are different, change them to be the same and go to Step 3.
2. Collect alarm information and configuration information, and then contact technical support personnel.

3. End.
Cause 24: Tunnel was Down.
1. Run the display mpls l2vc command to check whether the tunnel ID exists.
- If the tunnel ID exists, go to Step 3.
- If the tunnel ID does not exist, go to Step 4.
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 31: LDP Notification Not-Forwarding.
1. Run the display mpls l2vc interface interface-type interface-number command to check the status of the remote AC interface.
- If the AC state is Down, go to Step 2.
- If the AC state is Up, go to Step 3.
2. Run the display interface interface-type interface-number command to view the physical and link status of the remote interface. If the status of the interface is Down, restore the physical and link status to Up. Then, check whether the alarm is cleared.
- If so, go to Step 5.
- If not, go to Step 3.
3. Run the display mpls l2vc vc-id command to check the VC tunnel/token info field in the command output. If VC tunnel/token info is displayed as 0 tunnels/tokens, it indicates that no tunnel is selected by a PW. Run the display mpls l2vc interface interface-type interface-number command to check the tunnel policy name field in the command output. If tunnel policy name is displayed as "--", it indicates that an LDP LSP is used as the tunnel for a PW or no tunnel policy is configured. An MPLS TE tunnel can be used for a PW only after a tunnel policy is configured. If tunnel policy name is not displayed as "--", it indicates that a tunnel policy is adopted. In this case, you can run the display this command in the tunnel policy view to view the tunnel policy configuration. Modify the configuration on the outbound interface on a public network and restore the tunnel connected to the peer. Then, check whether the alarm is cleared.
- If so, go to Step 5.
- If not, go to Step 4.
4. Collect alarm information and configuration information, and then contact technical support personnel.

5. End.
Cause 32: PW was recreated.
1. 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 41: Local PSN Fault.
1. Run the display tunnel-info all command to check information about the tunnel connected to the peer. Modify the configuration on the outbound interface on a public network and restore the tunnel connected to the peer. Then, check whether the alarm is cleared.

2. Collect alarm information and configuration information, and then contact technical support personnel.

3. 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 and check whether the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm persists, go to Step 4.
3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.
Cause 60: MTU Unmatched.
1. Run the display mpls l2vc interface interface-type interface-number command to check whether the local VC MTU is the same as remote VC MTU.
- If so, go to Step 3.
- If not, go to Step 2.
2. Check the MTU of the local AC interface and the MTU of the remote AC interface. If two MTUs are not the same, modify them to be the same. Then, check whether the alarm is cleared.
- If so, go to Step 5.
- If not, go to Step 3.
3. Run the display mpls l2vc interface interface-type interface-number command to check the local control word is the same as the remote control word. Note that they are the same only when both are either in the enable state or in the disable state. Then, check whether the alarm is cleared.
- If so, go to Step 5.
- If not, go to Step 4.
4. Collect alarm information and configuration information, and then contact technical support personnel.

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