To configure a virtual switch that connects heartbeat interfaces:
#Vmware 6.0 documentation mac
This is required because in broadcast mode, the FGCP applies virtual MAC addresses to FortiGate data interfaces, and these virtual MAC addresses mean that matching interfaces of the FortiGate-VM instances in the cluster will have the same virtual MAC addresses. In addition, you must configure the VM platform to allow MAC address spoofing for the FortiGate-VM data interfaces. These packets use automatically assigned link-local IPv4 addresses in the 169.254.0.x range for HA heartbeat interface IP addresses.įor FortiGate-VMs to support a broadcast HA heartbeat configuration, you must configure the virtual switches that connect heartbeat interfaces to operate in promiscuous mode and support MAC address spoofing. The IP address of the HA heartbeat interface of the other FortiGate-VM in the HA cluster.īroadcast HA heartbeat packets are non-TCP packets that use Ethertype values 0x8890, 0x8891, and 0x8890. Set unicast-hb-peerip Įnable or disable (the default) unicast HA heartbeat. The unicast settings are configured in the CLI of the FortiGate-VM. Unicast HA heartbeat interfaces must be connected to the same network and you must add IP addresses to these interfaces.Unicast HA only supports two FortiGate-VMs.
Broadcast is the default HA heartbeat configuration. There are two options for setting up the HA heartbeat: unicast and broadcast. The primary consideration is that all interfaces involved be able to communicate efficiently over TCP/IP connection sessions.
#Vmware 6.0 documentation license
Validating the FortiGate-VM license with FortiManagerįortiGate-VM High Availability (HA) supports having two VMs in an HA cluster on the same physical platform or different platforms. Uploading the FortiGate-VM virtual appliance license Registering the FortiGate-VM virtual applianceĭownloading the FortiGate-VM virtual appliance deployment package FortiGate-VM virtual appliance evaluation licenseįortiGate-VM virtual licenses and resources