Checking the Hot Standby Status

After hot standby is configured, you can run the display hrp state command to check the hot standby status, including the role, priority, bandwidth usage of the heartbeat interface, last status switching information, hot standby configuration parameters and function status, and status of the items monitored by VGMP groups on the local and remote ends.

Run the display hrp state [ verbose ] command in any view to check the hot standby status.

HRP_M<sysname> display hrp state verbose
 Role: active, peer: standby           /*Roles of the local and peer devices*/
 Running priority: 45000, peer: 45000  /*VGMP group priorities of the local and peer device*/
 Backup channel usage: 0.00%           /*Bandwidth usage of the current heartbeat interface*/
 Stable time: 0 days, 0 hours, 11 minutes
 Last state change information: 2018-05-06 14:31:24 HRP core state changed, old_state = abnormal(active), new_state = normal, local_priority = 45000, peer_priority = 45000.
                                       /*Information about the last status switching of the local VGMP group*/

 Configuration:
 hello interval:              1000ms   /*Interval for sending VGMP, HRP, and HRP link detection packets*/
 preempt:                     60s      /*VGMP group preemption delay*/
 mirror configuration:        off      /*Whether the mirroring mode is enabled*/
 mirror session:              off      /*Whether quick session backup is enabled*/
 track trunk member:          on       /*Whether VGMP tracking Eth-Trunk member interfaces is enabled*/
 auto-sync configuration:     on       /*Whether configuration commands are automatically backed up*/
 auto-sync connection-status: on       /*Whether status entries are automatically backed up*/
 adjust ospf-cost:            on       /*Whether the cost of OSPF routes is adjusted according to the active/standby status*/
 adjust ospfv3-cost:          on       /*Whether the cost of OSPFv3 routes is adjusted according to the active/standby status*/
 adjust bgp-cost:             on       /*Whether the MED value of BGP routes is adjusted according to the active/standby status*/
 nat resource:                off      /*Whether NAT resources are used by segment.*/

 Detail information:
           GigabitEthernet0/0/2 vrrp vrid 1: active       /*VRRP group state*/
                   IP-Link abc(VSYS:public): up           /*State of the IP-link monitored by the VGMP group*/
                              BFD session 1: up           /*State of the BFD session monitored by the VGMP group*/
                                    vlan 20: enable       /*State of the VLAN monitored by the VGMP group*/
                       GigabitEthernet0/0/3: up           /*State of the interface monitored by the VGMP group*/
 GigabitEthernet0/0/2(OSPF peer IP:2.2.2.2): Full         /*State of the OSPF neighbor monitored by the VGMP group*/
                       BGP peer IP(3.2.2.2): Established  /*State of the BGP peer monitored by the VGMP group*/
                                  ospf-cost: +0           /*Cost of advertised OSPF routes*/
                                ospfv3-cost: +0           /*Cost of advertised OSPFv3 routes*/
                                   bgp-cost: +0           /*MED value added to advertised BGP routes*/

If any of the following information is displayed in the command output, the hot standby status or the item monitored by a VGMP group is abnormal: should, abnormal, unknown, warning, initial, down, failed, Non-full, and Non-established. For details about the exceptions, see Table 1. Analyze and locate the fault based on the description in the table until the exception is rectified.

**Table 1** Description of hot standby status exceptions
Category	Description of Abnormal Output Information
Role	# The actual running roles of the two devices are inconsistent with the configuration. The expected running role is displayed in the parentheses. Role: active, peer: standby (should be "active-active") In different networking environments, the following information is displayed in normal situations: Active/standby networking, Role: active, peer: standby is displayed on the active device, and Role: standby, peer: active is displayed on the standby device. Load balancing networking: Role:active, peer:active is displayed on both active and standby devices.
Role	# The status of the peer device cannot be obtained. If hot standby is not enabled on the peer device (hrp enable), no heartbeat interface is configured, or the heartbeat interface is faulty, the role of the peer device is displayed as unknown. Role: active, peer: unknown Running priority: 47004, peer: unknown Core state: abnormal(active), peer: unknown
VGMP group	# The status of the VGMP groups on the local and peer devices is abnormal (should be normal). Core state: abnormal(active), peer: abnormal(standby)
VGMP group	# The priority of the VGMP group on the local device is different from that on the peer device. This exception indicates that the active/standby switchover will occur. In normal cases, the priorities of the VGMP groups on the two devices are the same. Running priority: 47004, peer: 46002
Heartbeat interface	# It is recommended that the bandwidth of the current heartbeat interface be greater than or equal to 30% of the peak service traffic. If the remaining bandwidth of the heartbeat interface does not reach 30% of the peak service traffic, you are advised to replan the heartbeat interface. Backup channel usage: 80%
	# The interval at which Hello packets are sent is different from that on the peer device. Warning: The interval for sending Hello messages is inconsistent with that of the peer device. Run the hrp timer hello command to change the interval, so that the two devices use the same interval.
	# The current heartbeat interface is configured with the heartbeat-only parameter. Warning: The connection-status backup function is disabled automatically, for the running backup channel can only transfer control messages. Check whether the actual requirements are consistent with the configuration. The heartbeat-only parameter is generally configured in the following situations: When the service interface functions as the HRP backup channel, if the bandwidth used for connection status backup is too large, the service traffic may exceed the bearer capability of the service interface. As a result, the status of the two devices is unstable. To prevent this problem, configure the heartbeat-only parameter for the heartbeat interface, so that the backup channel is used only for transmitting HRP control negotiation packets.
VRRP group	# If the status of the VRRP group on the current device is initial, the interface configured with the VRRP group is Down. GigabitEthernet0/0/2 vrrp vrid 1: initial
	# The VRRP group on the current device is in the standby state, but it should be in the active state. GigabitEthernet0/0/2 vrrp vrid 1: standby (should be "active")
	# The VRRP group fails to negotiate with the peer. The possible cause is that VRRP packets cannot be exchanged between the local and peer devices or the configuration of the local or peer device is incorrect. GigabitEthernet0/0/2 vrrp vrid 1: standby (negotiation failed)
VGMP group monitoring items	# The status of the VGMP group monitoring item configured on the current device is abnormal. As a result, the priority of the VGMP group on the current device decreases and an active/standby switchover is triggered. IP-Link abc(VSYS:public): down BFD session 1: down GigabitEthernet0/0/3: down GigabitEthernet0/0/2(OSPF peer IP:2.2.2.2): Non-full BGP peer IP(3.2.2.2): Non-established