Failover means that when one FW in a hot standby network fails, the other FW takes over services from the faulty FW. The FW monitors different fault events based on the configured trigger conditions. When a fault occurs, a failover is triggered in a timely manner to ensure service continuity.
The conditions for triggering a failover include heartbeat loss and VGMP group status change.
Heartbeat loss
The FW monitors the heartbeat packets of the peer device to determine whether the peer device is alive and whether a failover is required. In hot standby networking, two FWs send heartbeat packets to each other through the heartbeat link. The default interval for sending heartbeat packets is 1000 ms. If a FW does not receive a heartbeat packet from the peer device for five consecutive heartbeat intervals, it determines that the peer device is faulty and triggers a failover.
VGMP Group Status Change
The FW receives VGMP packets from the peer device through the heartbeat link, learns the priority of the VGMP group on the peer device, and compares the priorities of the local and peer VGMP groups to determine whether to perform a failover. When an interface, or link of the FW is faulty, the priority of the VGMP group decreases. For details, see Table 1. If the priority of the local VGMP group is lower than that of the peer, the state of the local VGMP group changes to standby. Meanwhile, the FW sends a VGMP packet to the peer device to instruct the peer device to perform a failover.
Fault Event |
Description |
|---|---|
An interface monitored by a VGMP group is faulty. |
The impact of the interface fault on the VGMP group priority depends on the configuration. The details are as follows:
NOTE:
If a member interface of a trunk interface is faulty or a member interface is added to or deleted from the trunk interface, the VGMP group priority is affected. You can run the undo hrp track trunk-member enable command to cancel the monitoring of trunk member interface status by the VGMP group. |
A link monitored by a VGMP group is faulty. |
A VGMP group can monitor the link status in the following ways and adjust the priority of the VGMP group:
|
Table 2 shows the FW failover operations when different fault events occur.
Fault Event |
Failover |
Operation on the Faulty Device |
Operation on the Normal Device |
Description |
|---|---|---|---|---|
The entire device is faulty. |
Yes |
N/A |
After five heartbeat intervals, the state of the VGMP group changes to active. |
When the state of the VGMP group changes to active, the FW performs the following operations to divert network traffic to itself:
When the state of a VGMP group changes to standby, the FW performs the following operations to divert network traffic to the peer device for forwarding:
|
The heartbeat link is faulty. |
Yes |
After five heartbeat intervals, the state of the VGMP group changes to active. |
After five heartbeat intervals, the state of the VGMP group changes to active. |
|
An interface monitored by a VGMP group is faulty. |
Yes |
The priority of the VGMP group decreases. The VGMP group is switched to the standby state. A VGMP packet is sent to instruct the peer to perform failover. |
After receiving the VGMP packet from the peer device, the device changes the VGMP group to the active state. |
|
A link monitored by a VGMP group is faulty. |
Yes |
The priority of the VGMP group decreases. The VGMP group is switched to the standby state. A VGMP packet is sent to instruct the peer to perform failover. |
After receiving the VGMP packet from the peer device, the device changes the VGMP group to the active state. |