L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.6 hwPWVcBackup

Description

L2V/2/PWE3VC_BACKUP_T:OID [oid] The status of the PWE3 VC turned BACKUP. (VcId=[GAUGE], VcType=[INTEGER], PeerAddress=[IPADDR], InterfaceIndex=[INTEGER], VcInboundLabel=[GAUGE], VcOutboundLabel=[GAUGE], SecondaryPw=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], SysUpTime=[TIMETICK], InterfaceName=[STRING], SwitchVcId=[GAUGE], ActiveState=[INTEGER])

Indicates that a VC turns to the backup state.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.119.4.1.2.6	Major	other(1)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
VcId	ID of a VC.
VcType	Type of a VC: 0: Initial value 1: FR 2: ATM AAL5 3: ATM cell relay 4: VLAN 5: Ethernet 6: HDLC 7: PPP 9: ATM cell VCC 10: ATM cell VPC 11: IP-layer 2 (used for heterogeneous IP-interworking between Huawei devices and non-Huawei devices) 12: ATM, 1-to-1 VCC cell mode 13: ATM, 1-to-1 VPC cell mode 14: ATM, AAL5 PDU VCC TRANSPORT 64: Heterogeneous IP-interworking
PeerAddress	IP address of a peer
InterfaceIndex	Interface index
VcInboundLabel	Incoming label of a VC.
VcOutboundLabel	Outgoing label of a VC
SecondaryPw	Whether the PW is a secondary PW: 1: The PW is a secondary PW. 2: The PW is not a secondary PW.
HWL2VpnStateChangeReason	Cause for the VC status change
SysUpTime	Time for the system startup
InterfaceName	Interface name
SwitchVcId	ID of the switching VC
ActiveState	Active state

Impact on the System

The VRRP status affects the service.

Possible Causes

A VC turned to the backup state.

Procedure

View user logs to check the causes of the VRRP change. You can perform operations according to the specific cause.
- If the cause is priority calculation, go to Step 6.
- If the cause is that the MASTER_DOWN timer expired, go to Step 2.
- If the cause is the change of the BFD session status, go to Step 2.
- If the cause is the change of the interface status, go to Step 2.
- If the cause is admin-vrrp DROVE, go to Step 6.
Run the display vrrp command to check the status of the VRRP backup group on the former master switch.
- If the VRRP backup group is in the Initialize state, it indicates that the former switch is faulty. Locate the cause of the fault and restore the master switch. Go to Step 8.
- If the VRRP backup group is in the Backup state, go to Step 6.
- If the VRRP backup group is in the Master state, go to Step 3.
Check whether the master link is faulty.
- If BFD is configured, go to Step 4.
- If BFD is not configured, go to Step 5.
Run the display vrrp command to check the status of the BFD session.
- If the BFD session is Down, it indicates that the former master link is faulty. Locate the cause of the fault and restore the master link. Go to Step 8.
- If the BFD session is Up, go to Step 7.
Run the display vrrp [ interface interface-type interface-number ] [virtual-router-id ] statistics command to check whether the VRRP packets are normally forwarded.
- If not, it indicates that the link is faulty. Locate the cause of the fault and restore the link. Go to Step 8.
- If so, go to Step 7.
On the former master switch and backup switch, run the display vrrp command to check whether the configured priority of the VRRP is consistent with the running priority.
- If not, it indicates that the link monitored through VRRP is faulty. Locate the cause of the fault and restore the monitored link. Go to Step 8.
- If so, go to Step 7.
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.4.1.2.3 hwPWVcDown

L2V_1.3.6.1.4.1.2011.5.25.119.4.1.2.4 hwPWVcUp