The hrp interface command specifies the heartbeat interface.
The undo hrp interface command deletes the heartbeat interface configuration.
hrp interface interface-type interface-number remote { ipv4-address | ipv6-address } [ heartbeat-only ]
undo hrp interface interface-type interface-number
| Parameter | Description | Value |
|---|---|---|
interface-type interface-number |
Specifies the interface type and interface number. |
The interface type is GigabitEthernet and its subinterface, Eth-Trunk and its subinterface, or VLANIF. |
remote ipv4-address |
Specifies the IPv4 address of the remote heartbeat interface. |
The value is in dotted decimal notation. |
remote ipv6-address |
Specifies the IPv6 address of the remote heartbeat interface. |
The address is a 32-digit hexadecimal number in the X:X:X:X:X:X:X:X format. |
heartbeat-only |
Configures the heartbeat interface only to transmit the control negotiation packets of HRP, but not back up connection status. |
- |
Usage Scenario
In hot standby networking, two FWs informs each other of configurations and status information through VGMP packets, HRP heartbeat packets, HRP link probe packets, HRP data packets, and consistency check packets. All these packets are sent to the peer end through the heartbeat interface.
Prerequisite
The interfaces with vrrp virtual-mac enable configured cannot function as the HRP heartbeat interface. If an interface is configured with vrrp virtual-mac enable, delete the configuration before using it as the heartbeat interface.
Configuration Impact
You can use a service interface or a dedicated interface as the heartbeat interface. The heartbeat interface is used only to transmit HRP heartbeat packets. You are advised to configure a dedicated heartbeat interface to ensure hot standby stability.
When service interfaces are used as the heartbeat interface and connection status backup occupies a large number of bandwidth resources, the capabilities of service interfaces may be insufficient with the service traffic. As a result, the status of the dual systems becomes unstable. You can set parameter heartbeat-only for the heartbeat interface to transmit only control and negotiation packets, such as VGMP and HRP heartbeat packets.
The heartbeat interfaces of the two FWs can be directly connected or through a switch or router. Direct connection is recommended. When the IP addresses of the heartbeat interfaces on the two FWs are on the same network segment, the system directly sends heartbeat packets based on the direct route without searching the routing table. If the IP addresses of the heartbeat interfaces on the two FWs are on different network segments, the system searches the routing table for the next hop of the heartbeat packets. Ensure that the heartbeat link is reachable to prevent affecting the setup of the hot standby status.
The FW supports a maximum of 16 heartbeat interfaces. If there are multiple heartbeat interfaces, FW uses one of them to send heartbeat packets, and the others are standby. If the currently used heartbeat interface is faulty, a standby one is used. The configuration sequence determines the priorities of the heartbeat interfaces.
Follow-up Procedure
A heartbeat interface must be added to a security zone before it can send and receive packets. The FWs do not implement security policy checks on VGMP and HRP heartbeat packets. Therefore, you do not need to configure security policies for these packets.
Precautions
The MGMT interface (MEth0/0/0) cannot be used as the heartbeat interface.
It is recommended that the heartbeat interface bandwidth be 30% or higher of the service interface bandwidth. You are advised to use an Eth-Trunk interface as the heartbeat interface to improve network availability and increase the bandwidth of the heartbeat link.