VRRP_1.3.6.1.4.1.2011.5.25.127.2.30.1 hwVrrpExtTrapMasterDown

Trap Buffer Description

The VRRP status changed from master to another state. (ifIndex=[ifIndex], VrId=[VrId], MasterIpAddr=[MasterIpAddr], sysName=[sysName], ifName=[ifName], CurrentState=[CurrentState], ChangeReason=[ChangeReason])

VRRP was changed from master to another state.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	vrrpTrapMasterDown
Trap OID	1.3.6.1.4.1.2011.5.25.127.2.30.1
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 on which VRRP is configured.
MasterIpAddr	IP address of the master device in the VRRP group.
sysName	System name.
ifName	Name of the interface on which VRRP is configured.
CurrentState	Current VRRP status.
ChangeReason	VRRP status change reason.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.2.1.68.1.3.1.7	vrrpOperMasterIpAddr	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

If master/backup switchover occurs normally, services are not affected.
If master/backup switchover occurs abnormally, services may be interrupted.

Possible Causes

Cause 1: priority calculation: The VRRP priority of the master or backup device changed. Cause 2: interface down: The master device's interface on which VRRP is configured went Down. Cause 3: standby deleted: VRRP was deleted. Cause 4: admin-vrrp drove: The status of mVRRP changed. Cause 5: ip change: The IP address of the interface on which VRRP is configured changed. Cause 6: link BFD session down: The link BFD session associated with VRRP went Down. Cause 7: link BFD down-number changed: The number of Down link BFD sessions associated with VRRP changed. Cause 8: exiting load-balance group: VRRP exited the load-balance redundancy group (LBRG). Cause 9: becoming normal-vrrp: The LBRG without a virtual IP address became a common VRRP group.

Procedure

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

If the status is Initialize, go to Step 2.
If the status is Backup, go to Step 3.

2. If the original active device is faulty, check the fault cause and recover the active device.

Check whether the interface on which VRRP is configured is normal. If the interface is abnormal, go to Step 4.

3. Run the display vrrp command to check the configured VRRP priority and running priority of the original master and backup devices.

Check whether the interface monitored by VRRP or BFD is faulty and whether the priority is increased or decreased. Locate the cause of the fault and restore the monitored link. If the link is normal, go to Step 6.
If the interface tracked by the VRRP group or the BFD session is normal, go to Step 5.

4. Run the display this interface command in the view of the interface where the VRRP group is configured to check the physical status and protocol status of the interface.

If the physical status of the interface is Down, the link is faulty. Locate the cause of the fault, restore the link, and go to Step 6.
If the physical status is Up, check the protocol status. If the protocol status is Down, the IP address has been deleted. Go to step 6.
If the protocol status is Up, the IP address is on a different network segment from the virtual IP address of the VRRP group.

5. Collect log and configuration information, and contact Huawei technical support personnel.Check whether the local and peer configurations are correct. If not, correct them.

6. End.