After hot standby is configured, you can run the display hrp interface command to check the configuration and the working status of the heartbeat interface.
Run the display hrp interface command in any view to check the heartbeat interface and its working status.
HRP_M<sysname> display hrp interface GigabitEthernet0/0/2 : running GigabitEthernet0/0/1 : ready
Operating Status |
Description |
|---|---|
| Normal | |
running |
If the FW has multiple heartbeat interfaces in the ready state, the FW selects the first heartbeat interface to form a heartbeat link and sets the state of the heartbeat interface to running. If there is only one heartbeat interface in the ready state, it will be in the running state. The interface in the running state is responsible for sending heartbeat packets (Hello packets), VGMP packets, configuration and entry backup packets, heartbeat link detection packets, VGMP packets, and configuration consistency check packets. |
ready |
If the physical and protocol states of the heartbeat interface on the local FW are both Up, the heartbeat interface sends heartbeat link detection packets to the peer heartbeat interface. If the peer heartbeat interface can respond to this packet (also send heartbeat link detection packets), the FW will set the state of the local heartbeat interface to ready. The heartbeat interface in the ready state is the standby heartbeat interface. If the heartbeat interface or link in the running state is faulty, the heartbeat interface in the ready state takes over the current heartbeat interface in the configuration sequence. To ensure that the heartbeat link is normal, the heartbeat interface in the ready state continuously sends heartbeat link detection packets to the peer heartbeat interface for detection. |
| Abnormal | |
down |
This is displayed when the physical and protocol states of the heartbeat interface on the local FW is Down. |
invalid |
This state is displayed (the physical state is Up, and the protocol state is Down) if the heartbeat interface on the local FW is incorrectly configured. For example, the specified heartbeat interface is a Layer 2 interface or the IP address of the heartbeat interface is not configured. |
negotiation failed |
This state is displayed if the local and peer devices fail to negotiate the active/standby status. The possible cause is that the software version of the local device is inconsistent with that of the peer device, the configuration of the local or peer device is incorrect, the peer heartbeat interface is Down, the HRP source or destination port number is changed, or the underlying link is disconnected. |