Yes. You must set a physical IP address for the interface before you set the virtual IP address of the VRRP group on the interface. The physical IP address and the virtual address of the IPv4 VRRP group can reside on the same network segment or different network segments. But the physical IP address and the virtual address of the IPv6 VRRP group must reside on the same network segment.
Preemption starts after the original active firewall recovers. If the preemption delay of the active firewall is too shorter than that on the standby firewall, the active firewall may switch status before the session entries on the standby firewall are completely synchronized to the active firewall. As a result, some services may be interrupted. Therefore, the active firewall requires a longer preemption delay.
Preemption does not start after the standby firewall recovers. Therefore, preemption delay is meaningless for the standby firewall and you can use the default preemption delay.
No. When the active firewall fails, services are immediately switched to the standby firewall. After the original active firewall recovers, it must wait for the preemption delay before preempting During the process, the standby firewall is working. Therefore, the long preemption delay of the active firewall does not affect the failure response speed.
VGMP Hello packets are known as heartbeat packets and are used to check the operating status of the active and standby firewalls. If the standby VGMP group does not receive any VGMP Hello packet from the peer within five consecutive Hello intervals, the standby VGMP group considers that the peer fails and switches to the active state. Therefore, a short VGMP Hello interval enhances the failure response speed of the firewall.
However, if the interval is too short, the hot standby status may become unstable. When the CPU is overloaded, the task of sending VGMP Hello packets cannot be scheduled, resulting in a false switchover. Therefore, the default value, 1 second, is recommended.
No. The heartbeat interfaces can be connected either directly or through intermediate devices, such as switches or routers. Directly connection between the heartbeat interfaces is recommended.
Not required.
If the active device is restarted or powered off, configurations are automatically synchronized from the standby device after the active device recovers from the fault and is restarted. That is, in this scenario, configuration changes on the standby device can also be synchronized to the active device.
The configuration can be automatically synchronized after restart only after you run the hrp base config enable command to enable the corresponding function. If the function is disabled, the configuration is not automatically synchronized from the standby device after the active device is restarted.
No. If you do so, the active/standby switchover will be performed frequently once the directly connected Layer 2 interface on one firewall goes Down.
Not always. The "Do you want to synchronically save the configuration to the startup saved-configuration file on peer device?" message is displayed only when either of the following conditions is met: