L2VPN/2/hwVplsVcDown_active

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00 Log Reference

This document provides the explanations, causes, and recommended actions of logs on the product.

Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).

Message

L2VPN/2/hwVplsVcDown_active:The status of the VPLS VC turned DOWN. (VsiName=[STRING], PwId=[GAUGE], RemoteIp=[IPADDR], PwType=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK], TunnelPolicyName=[STRING])

Description

The log was generated when the VPLS VC was Down.

Parameters

Parameter Name	Parameter Meaning
VsiName	Indicates the name of a VSI.
PwId	Indicates the ID of a PW.
RemoteIp	Indicates the IP address of the remote peer.
PwType	Indicates the type of a PW: 1: normal 2: other
HWL2VpnStateChangeReason	Indicates the cause of the VC status change.
SysUpTime	Indicates the time for system startup.
TunnelPolicyName	Indicates the name of a tunnel policy.

Possible Causes

Cause 1: Invalid reason type.

Cause 3: VC was deleted.

Cause 4: LDP session was 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 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: VSI was shuted.

Cause 64: Undo set Admin VSI.

Procedure

Cause 1: Invalid reason type.
Contact technical support personnel.
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. Contact technical support personnel.
4. End.
Cause 4: LDP session was 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. Contact technical support personnel.
4. End.
Cause 6: Same LDP mapping was received with different label and MTU.
1. Reset the local PW. Then, check whether the alarm is cleared.
  - If so, go to Step 3.
  - If not, go to Step 2.
2. 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 so, go to Step 3.
  - If not, go to Step 2.
2. Make sure the MTU 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.
If the causes are below, please use these procedures.
- Cause 12: New LDP mapping message was received but remote VC or local VC is Down.
- Cause 13: LDP withdraw message was received.
- Cause 20: Encapsulation changed.
- 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.
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.
  - 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 10. 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 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.
  If the AC interface (in the field of Interface Name in the command output) 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 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.
  If the PW 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 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 tunnel all command to check that the session becomes operational, and then check whether the alarm is cleared.
  - If so, go to Step 5.
  - If not, go to Step 4.
4. Contact technical support personnel.
5. End.
Cause 61: VSI was shuted.
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.
  If the VSI is Admin 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. Contact technical support personnel.
4. End.
Cause 64: Undo set 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. Contact technical support personnel.
3. End.

Translation

简体中文

Download

Updated: 2019-04-20

Document ID: EDOC1100039602

Downloads: 133

Average rating:

This Document Applies to these Products