L2VPN_1.3.6.1.4.1.2011.5.25.119.1.2.3 hwVplsVsiDown

Trap Buffer Description

The status of the VPLS VSI turned DOWN. (VsiName=[VsiName], InterfaceIndex=[InterfaceIndex], VsiId=[VsiId], HWL2VpnStateChangeReason=[HWL2VpnStateChangeReason], VsiStatus=[VsiStatus], InterfaceName=[InterfaceName])

The VPLS VSI changed from Up to Down.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	hwVplsVsiDown
Trap OID	1.3.6.1.4.1.2011.5.25.119.1.2.3
MIB	HUAWEI-VPLS-EXT-MIB
Alarm ID	0x0d4f0000
Alarm Name	hwVplsVsiDown
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	L2VPN_1.3.6.1.4.1.2011.5.25.119.1.2.4 hwVplsVsiUp

Trap Buffer Parameters

Parameter	Description
VsiName	Indicates the name of a VSI.
InterfaceIndex	Indicates the interface index.
VsiId	Indicates the ID of a VSI.
HWL2VpnStateChangeReason	Indicates the cause of the VSI status change.
VsiStatus	Indicates the status of the VSI: 1: VSI Up 2: VSI Down 3: VSI Admin down
InterfaceName	Indicates the interface name.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.119.1.1.1.1.4	hwVplsVsiID	hwVplsVsiName
1.3.6.1.4.1.2011.5.25.119.1.1.8	hwVplsStateChangeReason	-
1.3.6.1.4.1.2011.5.25.119.1.1.1.1.6	hwVplsStatus	hwVplsVsiName
1.3.6.1.2.1.31.1.1.1.1	ifName	ifIndex

Impact on the System

VPLS Services will be interrupted and the traffic will be blocked.

Possible Causes

Cause 1: Invalid reason type.
Cause 3: VC was 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 withdraw message was received.
Cause 14: LDP release message was received.
Cause 19: Interface was Down.
Cause 20: Encapsulation changed.
Cause 24: Tunnel was Down.
Cause 31: LDP notification message was not forwarded.
Cause 32: PW was recreated.
Cause 37: Local AC fault.
Cause 41: Local PSN Fault.
Cause 60: MTU Unmatched.
Cause 61: Manual set VSI Down.
Cause 64: Undo manual set VSI admin-vsi.
Cause 94: AC token exceed or PW token exceed or VSI token exceed.
Cause 98: Related EVPN Inclusive Multicast route is valid.

Procedure

Cause 1: Invalid reason type.
1. Check whether the alarm alarm-name hwVplsVsiDown 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: VC was deleted.
1. Confirm that whether the VPLS VC is need to be deleted.
- If so, go to Step 4.
- If not, go to Step 2.
2. Recreate the VPLS VC 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 whether the session of the peer is operational.
- If so, go to Step 3.
- If not, go to Step 2.
2. Recreate the LDP section. 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 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 vsi verbose 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. Collect alarm information and configuration information, and then 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 vsi name vsi-name verbose command to check the VSIs on the local device and the peer device. In the case of the LDP VSI, check the VSIs with the same VSI ID. In the case of the BGP VSI, check the VSIs with the same VPN target.
- If the AC interface (in the field of Interface Name in the command output) is Down, go to Step 2.
- If the status of the VSI is Admin Down, go to Step 3.
- If the MTUs or the encapsulation types on the local and peer devices are inconsistent, go to Step 4.
- If the PW does not exist, go to Step 5.
- If the PW is Down, go to Step 9.
2. Restore the AC interface to Up, and check whether the alarm is cleared.
- If so, go to Step 11.
- If not, go to Step 1.
3. Run the undo shutdown command in the VSI view to check whether the alarm is cleared.
- If so, go to Step 11.
- If not, go to Step 1.
4. Run the mtu mtu command in the VSI view to set the MTUs of the VSIs on both ends to be consistent. Run the encapsulation command to set the encapsulation types on both ends to be consistent. Then, check whether the alarm is cleared.
- If so, go to Step 11.
- If not, go to Step 1.
5. Run the display vsi name vsi-name verbose command to check whether the session on the VSI peer is Up.
- If not, go to Step 6.
- If so, go to Step 7.
6. Run the display mpls ldp session command to check whether the session of the peer is operational.
- If so, go to Step 10.
- If not, go to Step 11.
7. Run the display vsi name vsi-name verbose command to check whether the session of the VSI peer has the tunnel ID.
- If so, go to Step 9.
- If not, go to Step 8.
8. Check whether the interface on the public network is Down. Set the interface on the public network to be Up, and then check the LDP configuration. Run the display mpls ldp session command to check that the session becomes operational, and then check whether the alarm is cleared.
- If so, go to Step 11.
- If not, go to Step 10.
9. Check the configurations of the routes and public network interfaces one by one. If the configuration is correct, go to Step 14. If the configuration is incorrect, restore the configuration and check whether the alarm is cleared.
- If so, go to Step 11.
- If not, go to Step 10.
10. Contact technical support personnel.

11. End.
Cause 13: LDP withdraw message was received.
1. Run the display vsi name vsi-name verbose command to check the VSIs on the local device and the peer device. In the case of the LDP VSI, check the VSIs with the same VSI ID. In the case of the BGP VSI, check the VSIs with the same VPN target.
- If the AC interface (in the field of Interface Name in the command output) is Down, go to Step 2.
- If the status of the VSI is Admin Down, go to Step 3.
- If the MTUs or the encapsulation types on the local and peer devices are inconsistent, go to Step 4.
- If the PW does not exist, go to Step 5.
- If the PW is Down, go to Step 9.
2. Restore the AC interface to Up, and check whether the alarm is cleared.
- If so, go to Step 11.
- If not, go to Step 1.
3. Run the undo shutdown command in the VSI view to check whether the alarm is cleared.
- If so, go to Step 11.
- If not, go to Step 1.
4. Run the mtu mtu command in the VSI view to set the MTUs of the VSIs on both ends to be consistent. Run the encapsulation command to set the encapsulation types on both ends to be consistent. Then, check whether the alarm is cleared.
- If so, go to Step 11.
- If not, go to Step 1.
5. Run the display vsi name vsi-name verbose command to check whether the session on the VSI peer is Up.
- If not, go to Step 6.
- If so, go to Step 7.
6. Run the display mpls ldp session command to check whether the session of the peer is operational.
- If so, go to Step 10.
- If not, go to Step 11.
7. Run the display vsi name vsi-name verbose command to check whether the session of the VSI peer has the tunnel ID.
- If so, go to Step 9.
- If not, go to Step 8.
8. Check whether the interface on the public network is Down. Set the interface on the public network to be Up, and then check the LDP configuration. Run the display mpls ldp session command to check that the session becomes operational, and then check whether the alarm is cleared.
- If so, go to Step 11.
- If not, go to Step 10.
9. Check the configurations of the routes and public network interfaces one by one. If the configuration is correct, go to Step 14. If the configuration is incorrect, restore the configuration and check whether the alarm is cleared.
- If so, go to Step 11.
- If not, go to Step 10.
10. Contact technical support personnel.

11. End.
Cause 14: LDP release message was received.
The same as Cause 13.
Cause 19: Interface was Down.
1. Run the display vsi name vsi-name verbose command to check the VSIs on the local device and the peer device. In the case of the LDP VSI, check the VSIs with the same VSI ID. In the case of the BGP VSI, check the VSIs with the same VPN target. If the PW is Down, go to Step 2.

2. Restore the AC interface to Up, and 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 20: Encapsulation changed.
The same as Cause 13.
Cause 24: Tunnel was Down.
1. Run the display vsi name vsi-name verbose command to check the VSIs on the local device and the peer device. In the case of the LDP VSI, check the VSIs with the same VSI ID. In the case of the BGP VSI, check the VSIs with the same VPN target. If the AC interface (in the field of Interface Name in the command output) is Down, go to Step 2.

2. Run the display vsi name vsi-name verbose command to check whether the session of the VSI peer has the tunnel ID.
- If so, go to Step 4.
- If not, go to Step 3.
3. 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 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 31: LDP notification message was not forwarded.
The same as Cause 13.
Cause 32: PW was recreated.
The same as Cause 13.
Cause 37: Local AC fault.
The same as Cause 13.
Cause 41: Local PSN Fault.
The same as Cause 13.
Cause 60: MTU Unmatched.
1. Run the display vsi verbose 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. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.
Cause 61: Manual set VSI Down.
1. Run the display vsi name vsi-name verbose command to check the VSIs on the local device and the peer device. In the case of the LDP VSI, check the VSIs with the same VSI ID. In the case of the BGP VSI, check the VSIs with the same VPN target. If the PW is Down, go to Step 2.

2. Run the undo shutdown command in the VSI view to 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 64: Undo manual set VSI admin-vsi.
1. Set the type of VSI as Admin VSI to 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 94: AC token exceed or PW token exceed or VSI token exceed.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 98: Related EVPN Inclusive Multicast route is valid.
Collect alarm information and configuration information, and then contact technical support personnel.