L2VPN/2/hwSvcDown_active

Message

L2VPN/2/hwSvcDown_active: The status of the SVC VC turned DOWN. (InterfaceIndex=[InterfaceIndex], InterfaceIndex=[InterfaceIndex2], SvcId=[SvcId], SVcType=[SVcType], PeerAddress=[PeerAddress], SvcInboundLabel=[SvcInboundLabel], SvcOutboundLabel=[SvcOutboundLabel], HWL2VpnStateChangeReason=[HWL2VpnStateChangeReason], InterfaceName=[InterfaceName], TunnelPolicyName=[TunnelPolicyName])

Description

An SVC PW went Down.

Parameters

Parameter Name	Parameter Meaning
InterfaceIndex	AC interface index.
InterfaceIndex2	AC interface index.
SvcId	SVC PW ID.
SVcType	SVC type.
PeerAddress	Peer address.
SvcInboundLabel	Incoming label of an SVC PW.
SvcOutboundLabel	Outgoing label of an SVC PW.
HWL2VpnStateChangeReason	Cause of the VC status change.
InterfaceName	AC interface name.
TunnelPolicyName	Name of the referenced tunnel policy.

Possible Causes

Cause 1: Invalid reason type.
Cause 3: VC was deleted.
Cause 19: Interface was Down.
Cause 24: Tunnel was Down.
Cause 32: PW was recreated.
Cause 41: Local PSN Fault.
Cause 94: AC or PW of SVC service token exceed.

Procedure

Cause 1: Invalid reason type.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 3: VC was 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 19: Interface was Down.
1. Run the display mpls static-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 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 static-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 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.
- 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 94: AC or PW of SVC service token exceed.
Collect alarm information and configuration information, and then contact technical support personnel.