Contents

HH3C-VRRP-EXT-MIB· 1

About this MIB· 1

MIB file name· 1

Root object 1

Scalar objects· 1

hh3cVrrpExtVrId ( 1.3.6.1.4.1.25506.2.24.2.1.1) 1

hh3cVrrpExtIpAddressType· 1

(1.3.6.1.4.1.25506.2.24.2.1.2) 1

hh3cVrrpExtIfIndex (1.3.6.1.4.1.25506.2.24.2.1.3) 1

hh3cVrrpExtIfDescr ( 1.3.6.1.4.1.25506.2.24.2.1.4) 2

hh3cVrrpExtOldState· 2

(1.3.6.1.4.1.25506.2.24.2.1.5) 2

hh3cVrrpExtNewState· 2

(1.3.6.1.4.1.25506.2.24.2.1.6) 2

hh3cVrrpExtStateChangeReason (1.3.6.1.4.1.25506.2.24.2.1.7) 2

Tabular objects· 2

hh3cVrrpExtTable· 2

Notifications· 3

hh3cVrrpExtStateChange· 3

hh3cVrrpExtV3ProtoError 6

 

 

HH3C-VRRP-EXT-MIB

About this MIB

This MIB describes the VRRP extended table entries.

MIB file name

hh3c-vrrp-ext.mib

Root object

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cVrrpExt(24)

Scalar objects

hh3cVrrpExtVrId ( 1.3.6.1.4.1.25506.2.24.2.1.1)

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cVrrpExtVrId ( 1.3.6.1.4.1.25506.2.24.2.1.1)	accessible-for-notify	Integer32	Interger(1..255)	VRID of the VRRP group.	Supported

 

hh3cVrrpExtIpAddressType

(1.3.6.1.4.1.25506.2.24.2.1.2)

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cVrrpExtIpAddressType (1.3.6.1.4.1.25506.2.24.2.1.2)	accessible-for-notify	Integer32	ipv4(1) ipv6(2)	Address type of the VRRP group.	Supported

 

hh3cVrrpExtIfIndex (1.3.6.1.4.1.25506.2.24.2.1.3)

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cVrrpExtIfIndex (1.3.6.1.4.1.25506.2.24.2.1.3)	accessible-for-notify	Integer32	Interger(1..255)	Interface index configured for the VRRP group.	Supported

 

hh3cVrrpExtIfDescr ( 1.3.6.1.4.1.25506.2.24.2.1.4)

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cVrrpExtIfDescr ( 1.3.6.1.4.1.25506.2.24.2.1.4)	accessible-for-notify	DisplayString	DisplayString (SIZE(0..255))	Interface description configured for the VRRP group.	Supported

 

hh3cVrrpExtOldState

(1.3.6.1.4.1.25506.2.24.2.1.5)

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cVrrpExtOldState (1.3.6.1.4.1.25506.2.24.2.1.5)	accessible-for-notify	INTEGER	initialize(1) backup(2) master(3)	Old VRRP group state.	Supported

 

hh3cVrrpExtNewState

(1.3.6.1.4.1.25506.2.24.2.1.6)

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cVrrpExtNewState (1.3.6.1.4.1.25506.2.24.2.1.6)	accessible-for-notify	INTEGER	initialize(1) backup(2) master(3)	New VRRP group state.	Supported

 

hh3cVrrpExtStateChangeReason (1.3.6.1.4.1.25506.2.24.2.1.7)

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cVrrpExtStateChangeReason (1.3.6.1.4.1.25506.2.24.2.1.7)	accessible-for-notify	Integer32	0..12	VRRP group state change reason.	Supported

 

Tabular objects

hh3cVrrpExtTable

About this table

This table contains information about the VRRP extended operations.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Not supported

Columns

The table indexes are ifIndex, vrrpOperVrId, and hh3cVrrpExtTrackInterface.

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cVrrpExtTrackInterface(1.3.6.1.4.1.25506.2.24.1.1.1.1)	not-accessible	INTEGER	INTEGER( 0..2147483647)	Index of the interface associated with VRRP.	Not supported
hh3cVrrpExtPriorityReduce(1.3.6.1.4.1.25506.2.24.1.1.1.2)	read-create	Integer32	Interger(1..255)	Reduced priority for the VRRP-Track association.	Not supported
hh3cVrrpExtRowStatus(1.3.6.1.4.1.25506.2.24.1.1.1.3)	read-create	RowStatus	active(1), notInService(2), notReady(3), createAndGo(4), createAndWait(5), destroy(6)	Row status of the table.	Not supported

 

Notifications

hh3cVrrpExtStateChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.24.2.0.1	A state change occurs on the device.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the VRRP state changes on the device. Possible causes might include the following:

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

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

The device changes to the IP address owner.

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

System impact

Identify the system impact based on the output from the display vrrp command.

If one device is the master and the other device is the backup, a master/backup switchover occurs, which has no impact on services.

If other situations exist, the VRRP group is abnormal, and services might be affected.

Status control

This notification cannot be disabled.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.24.2.1.1  (hh3cVrrpExtVrId)	VRID of the VRRP group.	N/A	Integer32	Interger(1..255)
1.3.6.1.4.1.25506.2.24.2.1.2  (hh3cVrrpExtIpAddressType)	VRRP group address type.	N/A	INTEGER	ipv4(1), ipv6(2)
1.3.6.1.4.1.25506.2.24.2.1.3  (hh3cVrrpExtIfIndex)	Interface index configured for the VRRP group.	N/A	InterfaceIndex	Integer32 (1..2147483647)
1.3.6.1.4.1.25506.2.24.2.1.4  (hh3cVrrpExtIfDescr)	Interface description configured for the VRRP group.	N/A	DisplayString	DisplayString (SIZE(0..255))
1.3.6.1.4.1.25506.2.24.2.1.5  (hh3cVrrpExtOldState)	Old VRRP group state.	N/A	INTEGER	initialize(1), backup(2), master(3)
1.3.6.1.4.1.25506.2.24.2.1.6  (hh3cVrrpExtNewState)	New VRRP group state.	N/A	INTEGER	initialize(1), backup(2), master(3)
1.3.6.1.4.1.25506.2.24.2.1.7 (hh3cVrrpExtStateChangeReason)	VRRP group state change reason.	N/A	Integer32	0..12

 

Recommended action

Resolve this issue based on the VRRP state change reason carried in the trap message:

1.If the value is 1, the VRRP negotiation timer has expired. As a best practice, take the following actions:

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.

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.

Identify whether the VRRP configuration is incorrect by executing the display current-configuration | include 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.If the value is 2, the virtual MAC address configuration has failed. To resolve this issue, copy the VRRP group configuration and create the VRRP group again.

3.If the value is 3, an interface event has been received. Identify whether the interfaces where the VRRP group resides 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

4.If the value is 4, the interface IP address has been deleted. Identify whether the IP address of the interface is deleted.

Execute the display interface brief command on the local device to view the device interface IP address. If the IP address of the interface is deleted, configure the IP address again.

5.If the value is 5, the track entry state has changed. Execute the display vrrp command to obtain the ID of the associated track entry, and then use the display track command to locate and resolve the track entry fault.

6.If the value is 6, a VRRP packet has been received, and no action is required.

7.If the value is 7, the device changes to the IP address owner. As a best practice, take the following actions:

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

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

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

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.

8.If the value is 8, the hardware resources are insufficient. Delete the unnecessary VRRP groups and ACL entries to release the hardware resources.

9.If the value is 9, no packets have been received upon expiration of the timeout timer. Take the actions as described in step 1.

10.If the value is 10, a packet with priority 0 has been received. As a best practice, take the following actions:

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.

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.

11.If the value is 11, a preemption has occurred.

  - If the preemption is manually triggered by the administrator, no action is required.

  - If the preemption is automatically performed, the monitored object is faulty, and you need to further locate the reason for the automatic preemption.

12.If the value is 12, the master VRRP group has changed. 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 take further actions based on the reason displayed in the trap of the master VRRP group.

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

hh3cVrrpExtV3ProtoError

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.24.2.0.2	VRRPv3 receives packets with an incorrect protocol type.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when VRRPv3 receives packets with an incorrect protocol type.

System impact

Protocol type configuration inconsistency on both ends results in failures of master and backup negotiation and VRRP group creation.

Status control

This notification cannot be disabled.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.24.2.1.1  (hh3cVrrpExtVrId)	VRID of the VRRP group.	N/A	Integer32	Interger(1..255)
1.3.6.1.4.1.25506.2.24.2.1.2  (hh3cVrrpExtIpAddressType)	VRRP group address type.	N/A	INTEGER	ipv4(1), ipv6(2)
1.3.6.1.4.1.25506.2.24.2.1.3  (hh3cVrrpExtIfIndex)	Interface index configured for the VRRP group.	N/A	InterfaceIndex	Integer32 (1..2147483647)
1.3.6.1.4.1.25506.2.24.2.1.4 (hh3cVrrpExtIfDescr)	Interface description configured for the VRRP group.	N/A	DisplayString	DisplayString (SIZE(0..255))

 

Recommended action

To resolve this issue:

1.Execute the display vrrp verbose command on the local and peer devices to verify that the Version field value in the command output is the VRRP protocol version used by the local device. If the versions are inconsistent, execute the vrrp version command to edit the version number.

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