L2V_1.3.6.1.4.1.2011.5.25.119.1.2.3 hwVplsVsiDown

Description

L2V/2/VPLSVSI_DWN_T:OID [oid] The status of the VPLS VSI turned DOWN. (VsiName=[STRING], InterfaceIndex=[INTEGER], VsiId=[GAUGE], HWL2VpnStateChangeReason=[INTEGER], VsiStatus=[INTEGER], InterfaceName=[STRING])

The VPLS VSI changed from Up to Down.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.119.1.2.3	Major	qualityOfServiceAlarm(3)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
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. For details, refer to hwVplsStateChangeReason in the appendix of HUAWEI-VPLS-EXT-MIB.
VsiStatus	Indicates the status of the VSI: 1: VSI Up 2: VSI Down 3: VSI Admin down
InterfaceName	Indicates the interface name.

Impact on the System

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

Possible Causes

The status of the physical link or the VPLS configuration of any VSI device was changed.

Procedure

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 12.
Restore the AC interface to Up, and check whether the alarm is cleared.
- If so, go to Step 14.
- If not, go to Step 1.
Run the undo shutdown command in the VSI view to check whether the alarm is cleared.
- If so, go to Step 14.
- If not, go to Step 1.
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 the alarm is cleared, go to Step 14.
- If the alarm is not cleared, go to Step 1.
Run the display vsi name vsi-name verbose command to check the PW signaling.
- If it is LDP, go to Step 6.
- If it is BGP, go to Step 7.
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 8.
- If so, go to Step 9.
Run the display bgp peer command to check whether the BGP peer is established.
- If so, go to Step 13.
- If not, go to Step 10.
Run the display mpls ldp session command to check whether the session of the peer is operational.
- If so, go to Step 13.
- If not, go to Step 11.
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 12.
- If not, go to Step 11.
Configure the BGP connection to be established, and check whether the alarm is cleared.
- If so, go to Step 14.
- If not, go to Step 13.
Check whether the interface on the public network is Down. Set the interface on the public network to be Up, and then change 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 14.
- If not, go to Step 13.
Repeat the preceding steps on the remote device. Then, check whether the alarm is cleared.
- If so, go to Step 14.
- If not, go to Step 13.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

L2V_1.3.6.1.4.1.2011.5.25.119.1.2.4 hwVplsVsiUp