Overview
In virtual machine (VM) and cloud environments that do not support heartbeat communication with Layer 2 Ethernet frames (see HA heartbeat interface), you can set up a Layer 3 unicast HA heartbeat when configuring HA. This consists of enabling the feature and adding a peer IP address. The peer IP address is the IP address of the HA heartbeat interface of the other FortiWeb VM in the HA cluster.
Unicast HA is only supported in active-passive (AP) and Active-Active High Volume (AAH) modes. The heartbeat interfaces must be connected to the same network, and the IP addresses must be added to these interfaces. The operation mode must be Reverse Proxy.
Prerequisites
In this article, we assume you already have deployed the following:
-
Two or more FortiWeb-VMs running on KVM. The FortiWeb version should be 7.0.1 or higher, and they should be in Reverse Proxy mode.
-
Client (Ubuntu 18.04) * 1
-
Sever (Ubuntu 18.04) * 2
In the following sections, we will use an example to illustrate the steps. In this example, there is a server policy configured with VIP 10.159.33.200, and the real servers' IP addresses are 10.0.0.100 & 10.0.1.100.
Refer to the network diagram below.
