VRRP_1.3.6.1.4.1.2011.5.25.127.2.30.2 hwVrrpExtTrapNonMaster

Trap Buffer Description

The VRRP status changed between backup and initialize. (ifIndex=[ifIndex], VrId=[VrId], MasterIpAddr=[MasterIpAddr], sysName=[sysName], ifName=[ifName], CurrentState=[CurrentState], ChangeReason=[ChangeReason])

The VRRP status changed between Backup and Initialize.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	vrrpTrapNonMaster
Trap OID	1.3.6.1.4.1.2011.5.25.127.2.30.2
MIB	HUAWEI-VRRP-EXT-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
Alarm Type	This is an event trap and does not involve alarm type.
Raise or Clear	This is an event trap and does not involve alarm generation or clearance.
Match trap	-

Trap Buffer Parameters

Parameter	Description
ifIndex	Index of the interface where VRRP is configured.
MasterIpAddr	IP address of the master device.
sysName	System name.
ifName	Name of the interface where VRRP is configured.
CurrentState	Initialize Backup.
ChangeReason	Status change reason.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.2.1.68.1.3.1.8	vrrpOperPrimaryIpAddr	ifIndex vrrpOperVrId
1.3.6.1.2.1.1.5	sysName	-
1.3.6.1.2.1.31.1.1.1.1	ifName	ifIndex
1.3.6.1.2.1.68.1.3.1.3	vrrpOperState	ifIndex vrrpOperVrId
1.3.6.1.4.1.2011.5.25.127.1.7	hwVrrpExtStateChangeReasonString	-

Impact on the System

Cause 1: The VRRP status changes from Backup to Initialize, which may cause service interruptions.

Cause 2: The VRRP status changed from Initialize to Backup, which did not affect services.

Possible Causes

The VRRP status changes from Backup to Initialize. Possible causes are as follows:

Cause 1: The device on which the VRRP group is configured is faulty.

Cause 2: The interface on which the VRRP group is configured or the directly connected link is faulty.

The VRRP status changes from Initialize to Backup.

Possible causes are as follows:

Cause 1. The device on which the VRRP group is configured recovers from a fault.

Cause 2: The VRRP-enabled interface or the directly connected link recovered.

Procedure

1. Check whether the value of CurentState is Initialize or Backup.

If the value of CurentState is Initialize, go to Step 2.
If the value of CurentState is Backup, go to Step 6.

2. Check whether the interface on which the VRRP group is configured or the link monitored by BFD that is associated with VRRP is Up.

If the interface on which the VRRP group is configured is Up, go to Step 3.
If the link monitored by BFD that is associated with VRRP is Up, go to Step 4.

3. Run the display this interface command in the view of the interface on which the VRRP group is configured to check the physical and protocol statuses of the interface.

If the physical status of the interface is Down, the link connected to the interface fails. Rectify the fault and check whether the VRRP group has recovered.
If the VRRP group has recovered, go to Step 6.
If the VRRP group has not recovered, go to Step 5.
If the physical status of the interface is Up but its protocol status is Down, the IP address of the interface has been deleted. Reassign an IP address to the interface and check whether the VRRP group has recovered.
If the VRRP group has recovered, go to Step 6.
If the VRRP group has not recovered, go to Step 5.
If the physical and protocol statuses of the interface are both Up, the IP address of the interface is not on the same network segment as the virtual IP address of the VRRP group. Reassign an IP address to the interface and ensure that the IP address is on the same network segment as the virtual IP address of the VRRP group. Then check whether the VRRP group has recovered.
If the VRRP group has recovered, go to Step 6.
If the VRRP group has not recovered, go to Step 5.

4. Run the display vrrp command and check whether the value of BFD-Session State in the command output is UP.

If the value of BFD-Session State in the command output is DOWN, the original standby link fails. Rectify the fault and check whether the VRRP group has recovered.
If the VRRP group has recovered, go to Step 6.
If the VRRP group has not recovered, go to Step 5.
If the value of BFD-Session State in the command output is UP, go to Step 5.

5. Collect log information and configuration information, and then contact technical support personnel.

6. End.