Fortinet Document Library

Version:


Table of Contents

FortiGate-VM on Microsoft Hyper-V

Resources

Upgrade Path Tool
  • Select version:
  • 6.0
6.0.0
Download PDF
Copy Link

High availability

FortiGate-VM High Availability (HA) supports having two VMs in an HA cluster on either the same physical platform or different platforms. The primary consideration is that all of the interfaces involved, be able to communicate efficiently over TCP/IP connection sessions.

Heartbeat

There are two options for setting up the HA heartbeat: unicast and broadcast. Broadcast is the default HA heartbeat configuration. However, the broadcast configuration may not be ideal for FortGate VM because it may require special settings on the host. In most cases, the unicast configuration would be preferred.

The differences between the unicast heartbeat setup the broadcast heartbeat setup are:

  • The unicast method does not change the FortiGate-VM interface MAC addresses to virtual MAC addresses.
  • Unicast HA only supports two FortiGate VMs.
  • Unicast HA heartbeat interfaces must be connected to the same network and you must add IP addresses to these interfaces.

Unicast

The unicast settings are configured in the CLI of the FortiGate-VM. The syntax is as follows:

config system ha

set unicast-hb {enable/disable}

set unicast-hb-peerip {IP address of the peer's heartbeat interface}

end

Setting

Description

unicast-hb Enable or disable (the default) unicast HA heartbeat.
unicast-hb-peerip The IP address of the HA heartbeat interface of the other FortiGate VM in the HA cluster.

Broadcast

Broadcast HA heartbeat packets are non-TCP packets that use Ethertype values 0x8890, 0x8891, and 0x8890. These packets use automatically assigned link-local IPv4 addresses in the 169.254.0.x range for HA heartbeat interface IP addresses.

For 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.

In addition, you must configure the VM platform to allow MAC address spoofing for the FortiGate-VM data interfaces. 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.

By default the FortiGate-VM for Hyper-V has promiscuous mode enabled in the XML configuration file in the FortiGate-VM Hyper-V image. If you have problems with HA mode, confirm that this is still enabled. With promiscuous mode enabled and the correct MAC spoofing settings, you should be able to configure HA between two or more FortiGate-VM for Hyper-V instances.

Resources

High availability

FortiGate-VM High Availability (HA) supports having two VMs in an HA cluster on either the same physical platform or different platforms. The primary consideration is that all of the interfaces involved, be able to communicate efficiently over TCP/IP connection sessions.

Heartbeat

There are two options for setting up the HA heartbeat: unicast and broadcast. Broadcast is the default HA heartbeat configuration. However, the broadcast configuration may not be ideal for FortGate VM because it may require special settings on the host. In most cases, the unicast configuration would be preferred.

The differences between the unicast heartbeat setup the broadcast heartbeat setup are:

  • The unicast method does not change the FortiGate-VM interface MAC addresses to virtual MAC addresses.
  • Unicast HA only supports two FortiGate VMs.
  • Unicast HA heartbeat interfaces must be connected to the same network and you must add IP addresses to these interfaces.

Unicast

The unicast settings are configured in the CLI of the FortiGate-VM. The syntax is as follows:

config system ha

set unicast-hb {enable/disable}

set unicast-hb-peerip {IP address of the peer's heartbeat interface}

end

Setting

Description

unicast-hb Enable or disable (the default) unicast HA heartbeat.
unicast-hb-peerip The IP address of the HA heartbeat interface of the other FortiGate VM in the HA cluster.

Broadcast

Broadcast HA heartbeat packets are non-TCP packets that use Ethertype values 0x8890, 0x8891, and 0x8890. These packets use automatically assigned link-local IPv4 addresses in the 169.254.0.x range for HA heartbeat interface IP addresses.

For 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.

In addition, you must configure the VM platform to allow MAC address spoofing for the FortiGate-VM data interfaces. 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.

By default the FortiGate-VM for Hyper-V has promiscuous mode enabled in the XML configuration file in the FortiGate-VM Hyper-V image. If you have problems with HA mode, confirm that this is still enabled. With promiscuous mode enabled and the correct MAC spoofing settings, you should be able to configure HA between two or more FortiGate-VM for Hyper-V instances.