Contents

VRRP-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

vrrpTrapNewMaster 1

vrrpTrapAuthFailure· 3

VRRP-MIB

About this MIB

This MIB contains general VRRP entries.

MIB file name

rfc2787-vrrp.mib

Notifications

vrrpTrapNewMaster

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.68.0.1	Indicates that the sending device has transitioned to master state.	Informational	Warning	N/A	ON

 

Notification triggers

This notification is generated when a device transitions to Master state. Possible causes might include the following:

1.     Cause 1: A network failure occurs, which results in VRRP negotiation timeout for the master device.

2.     Cause 2: The VRRP priority on the local device is higher through priority calculation.

3.     Cause 3: The device changes to the IP address owner.

4.     Cause 4: A switchover occurs to the master VRRP group, and the device transitions to Master state accordingly.

System impact

If the local device becomes the master and the peer device state is Backup, the VRRP group is operating correctly, which has no impact on services.

If the local device becomes the master and the peer device state is not Backup, the VRRP group might fail to operate correctly.

Status control

ON

CLI: Use the snmp-agent trap enable vrrp new-master command.

OFF

CLI: Use the undo snmp-agent trap enable vrrp new-master command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.2.1.68.1.3.1.7 (vrrpOperMasterIpAddr)	Real (primary) IP address of the master router that is used as the source address of VRRP advertisement packets.	ifIndex vrrpOperVrId	IpAddress	OCTET STRING (4)

 

Recommended action

To resolve this issue:

1.     As a best practice to resolve the issue mentioned in cause 1, take the following actions:

a.     Identify whether the peer device is faulty. Execute the display vrrp command on the peer device. If the value for the State field in the command output is Initialize, the peer device is faulty. Locate the failure cause, and recover the peer device.

b.     Identify whether the connected interfaces of the VRRP group are faulty. Execute the display interface command on the local and peer devices to view the connected interface state of the VRRP group. If the interface state is Down, locate and process the interface fault.

c.     Identify whether the VRRP configuration is incorrect by executing the display current-configuration | inculde vrrp command on the local and peer devices.

-     IPv4 VRRP requires version consistency. If the versions are inconsistent, execute the vrrp version command in interface view to edit the version number. IPv6 VRRP supports only VRRPv3 that is not configurable.

-     IPv4 VRRP requires authentication mode consistency. In addition, make sure authentication keys, if configured, are consistent. If the previous settings are inconsistent, execute the vrrp vrid authentication-mode command in interface view to edit the settings. IPv6 VRRP does not support authentication.

2.     As a best practice to resolve the issue mentioned in cause 2, take the following actions:

a.     Execute the display vrrp verbose command on the local and peer devices to view the configured VRRP priority (Config pri field).

-     If the configuration is correct, no action is required.

-     If the configuration is incorrect, execute the vrrp vrid priority command in interface view to edit the configuration.

b.     Execute the display vrrp verbose command on the local and peer devices to view the configured VRRP priority (Config pri field) and effective VRRP priority (Running pri field). If the values are inconsistent, view the associated track entry number, and the use the display track command to locate and resolve the track entry fault.

3.     As a best practice to resolve the issue mentioned in cause 3, take the following actions:

a.     Execute the display vrrp command without parameters on the local device to view the virtual IP address of the VRRP group.

b.     Execute the display interface brief command on the local device to view the device interface IP address.

c.     Determine whether to configure the local device as the IP address owner of the VRRP group.

d.     If the IP address of an interface on a device in the VRRP group is the same as the virtual IP address of the VRRP group, the device is called the IP address owner. If the VRRP group contains an IP address owner, it acts as the master as long as it is operating correctly.

-     If the device is required to be configured as the IP address owner, no action is required.

-     If the device is not required to be configured as the IP address owner, execute the vrrp vrid command in interface view to edit the virtual IP address of the VRRP group.

4.     As a best practice to resolve the issue mentioned in cause 4, take the following actions:

Execute the display vrrp verbose command on the local device to obtain the name of the associated master VRRP group from the Follow Name field. Then locate the switchover reason for the master VRRP group based on the recommended actions for the issues mentioned in cause 1, 2, and 3.

5.     If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

vrrpTrapAuthFailure

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.68.0.2	Indicates the received VRRP packet contains an authentication type or authentication key that conflicts with the local configuration.	Informational	Warning	N/A	ON

 

Notification triggers

This notification is generated upon receiving a VRRP packet from a router with an authentication type or authentication key setting that conflicts with the local router.

System impact

Authentication mode inconsistency on both ends of the VRRP group results in master and backup negotiation failure.

Status control

ON

CLI: Use the snmp-agent trap enable vrrp auth-failure command.

OFF

CLI: Use the undo snmp-agent trap enable vrrp auth-failure command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.2.1.68.1.5 (vrrpTrapPacketSrc)	IP address of the received VRRP packet.	N/A	IpAddress	OCTET STRING (4)
1.3.6.1.2.1.68.1.6 (vrrpTrapAuthErrorType)	Potential types of configuration conflicts.	N/A	INTEGER	invalidAuthType(1), authTypeMismatch(2), authFailure(3)

 

Recommended action

To resolve this issue:

1.     View the interface authentication parameters through the Auth Type and Key fields in the output from the display vrrp command. If the authentication mode and key settings on both ends are inconsistent, execute the vrrp vrid authentication-mode command in interface view to edit the authentication mode and key settings.

2.     If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.