Contents

HH3C-VSRP-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

hh3cVsrpPeerConnDownTrap· 1

hh3cVsrpPeerConnUPTrap· 2

hh3cVsrpInstanceStateChangeTrap· 3

 

 

HH3C-VSRP-MIB

About this MIB

This MIB is defined to obtain VSRP information.

MIB file name

hh3c-vsrp.mib

Notifications

hh3cVsrpPeerConnDownTrap

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.254.1.0.1	The TCP connection to a VSRP peer goes down.	Error	Major	1.3.6.1.4.1.25506.2.254.1.0.2 (hh3cVsrpPeerConnUPTrap)	ON

 

Notification triggers

This notification is sent when the TCP connection to a VSRP peer goes down.

System impact

The VSRP feature cannot operate correctly.

Status control

ON

CLI: Use the snmp-agent trap enable vsrp command.

OFF

CLI: Use the undo snmp-agent trap enable vsrp command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.254.1.1.1 (hh3cVsrpPeerName)	VSRP peer name.	N/A	DisplayString	(1..31)
1.3.6.1.4.1.25506.2.254.1.1.2 (hh3cVsrpPeerConnDownReason)	Reason for the TCP connection down event.	N/A	DisplayString	(1..255)

 

Recommended action

To resolve this issue:

1.Locate the issue based on the TCP disconnection reason carried in the notification:

  - If the reason is Negative track entry, execute the display vsrp peer command to view the number (Track ID field) and status (Track status field) of the track entry associated with the VSRP peer. Then execute the display track and display interface commands to troubleshoot the status change.

  - If the reason is Configuration deletion and the configuration is deleted mistakenly, use the peer command in VSRP peer view to reconfigure the TCP connection to the VSRP peer.

  - If the reason is Abnormal network connection, troubleshoot the network connection issue.

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

hh3cVsrpPeerConnUPTrap

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.254.1.0.2	A TCP connection is set up with a VSRP peer.	Recovery	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is sent when a TCP connection is set up with a VSRP peer.

System impact

No impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable vsrp command.

OFF

CLI: Use the undo snmp-agent trap enable vsrp command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.254.1.1.1 (hh3cVsrpPeerName)	VSRP peer name.	N/A	DisplayString	(1..31)

 

Recommended action

No action is required.

hh3cVsrpInstanceStateChangeTrap

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.254.1.0.3	The status of a VSRP instance changes.	Error	Major	N/A (N/A)	ON

 

Notification triggers

This notification is sent when the status of a VSRP instance changes.

System impact

The VSRP instance status change will result in master and backup role switchover for VSRP, as well as traffic and service switchover.

Status control

ON

CLI: Use the snmp-agent trap enable vsrp command.

OFF

CLI: Use the undo snmp-agent trap enable vsrp command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.4.1.25506.2.254.1.1.3 (hh3cVsrpInstanceName)	VSRP instance name.	N/A	DisplayString	(1..31)
1.3.6.1.4.1.25506.2.254.1.1.4 (hh3cVsrpInstanceOldState)	Old status.	N/A	DisplayString	(1..255)
1.3.6.1.4.1.25506.2.254.1.1.5 (hh3cVsrpInstanceNewState)	New status.	N/A	DisplayString	(1..255)
1.3.6.1.4.1.25506.2.254.1.1.6 (hh3cVsrpInstChangeReason)	Reason for the VSRP instance status change.	N/A	DisplayString	(1..255)

 

Recommended action

To resolve this issue:

1.Locate the issue based on the VSRP instance status change reason carried in the notification.

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

 

Reason

Action

 

The VSRP instance failed to register VRRP events, and the VSRP local status changed

Use the display vrrp command to check the status of the related VRRP group. If the VRRP group is abnormal, troubleshoot the issue, such as use the display current-configuration vrrp command to verify correctness of the VRRP group configuration.

 

The VSRP instance was unbound from VRRP, and the VSRP local state changed

No action is required.

 

The S-Trunk binding of the VSRP instance was set to the initialization state, and the VSRP local state changed

Use the display s-trunk verbose command to check the status of the related smart trunk. If the smart trunk is abnormal, troubleshoot the issue, such as use the display current-configuration s-trunk command to verify correctness of the smart trunk configuration.

 

The VSRP instance was unbound from S-Trunk, and the VSRP local state changed

No action is required.

 

The UP backup interface binding of the VSRP instance was set to the initialization state, and the VSRP local state changed

Use the display up-backup-profile command to check the status of the related UP backup interface.

Use the display up-backup-profile switchover-history virtual-mac command to check the switchover history for the UP backup interface.

If the UP backup interface is abnormal, first troubleshoot the issue.

 

The VSRP instance was unbound from a UP backup interface, and the VSRP local state changed

No action is required.

 

The VRRP configuration bound to the VSRP instance had state change, and the VSRP local state changed

Use the display vrrp command to check the status of the related VRRP group. If the VRRP group is abnormal, troubleshoot the issue, such as use the display current-configuration vrrp command to verify correctness of the VRRP group configuration.

 

The S-Trunk configuration bound to the VSRP instance had state change, and the VSRP local state changed

Use the display s-trunk verbose command to check the status of the related smart trunk. If the smart trunk is abnormal, troubleshoot the issue, such as use the display current-configuration s-trunk command to verify correctness of the smart trunk configuration.

 

The UP backup interface bound to the VSRP instance had state change, and the VSRP local state changed

Use the display up-backup-profile command to check the status of the related UP backup interface.

Use the display up-backup-profile switchover-history virtual-mac command to check the switchover history for the UP backup interface.

If the UP backup interface is abnormal, first troubleshoot the issue.

 

The UP backup interfaces bound to VSRP instances had state change, and the VSRP local state of these VSRP instances changed

Use the display up-backup-profile command to check the status of the related UP backup interface.

Use the display up-backup-profile switchover-history virtual-mac command to check the switchover history for the UP backup interface.

If the UP backup interface is abnormal, first troubleshoot the issue.

 

The VSRP local state changed in processing buffered status change messages

Determine whether the VSRP instance collaborates with VRRP, S-trunk, or UP backup interface, and then troubleshoot the VSRP status change issue.

 

The VSRP instance backup ID was set, and the VSRP peer state changed

No action is required.

 

The TCP disconnection timer timed out, and the VSRP peer state changed

Troubleshoot TCP connection issues and network connectivity issues.

 

The TCP connection went down, and the VSRP peer state changed due to configuration deletion

No action is required.

 

The TCP connection went down, and the VSRP peer state changed because the associated track entry changed to negative

Check the status of the track entry associated in VSRP peer view and troubleshoot the track entry status change.

 

The VSRP peer state changed after the peer status change message was received

Troubleshoot the VSRP peer status change, such as use the display vsrp instance command to view the VSRP status information.

 

VSRP split-brain prevention was performed, and the VSRP instance state changed

No action is required.

 

The VSRP peer state changed after the forced backup switchover message was received

No action is required.