Fortinet white logo
Fortinet white logo

New Features

FortiManager-HA support automatic VRRP failover in Azure 7.4.2

FortiManager-HA support automatic VRRP failover in Azure 7.4.2

FortiManager-HA support automatic VRRP failover in Azure.

To configure automatic VRRP failover in Azure:
  1. Create FortiManager-VM in one ResourceGroup in same or different subnets.

  2. Allocate a secondary private IP (static) to be used as VIP of FortiManager-HA. Secondary IP will be assigned to the instance when its mode transitioned to master by fmgutil to call Azure cloud APIs within the instance itself

  3. Or create a static public IP in the ResourceGroup to be used as VIP.

  4. Enable Managed Identity for the VM and assign role with read-write access to the resource group. This is for VM to re-assign VIP.

  5. Configure FortiManager-HA, use private IP as peer IP, and the static public IP as VIP.

To configure FortiManager HA:
  1. On FortiManager, configure high availability at System Settings > HA.

    See the FortiManager Administration Guide for more information on configuring HA.

    When configuring HA, use the primary private IP as the Peer IP and the external static IP as the Cluster Virtual IP.

  2. Import the Azure Root CA to FortiManager. In order for the fmgutil to call the Azure API successfully, you must import the Azure Cloud CA certificate to each FortiManager instance. For more information on the CA used by Microsoft Entra ID (formerly Azure AD), see https://learn.microsoft.com/en-us/azure/security/fundamentals/azure-CA-details.

    1. Go to System Settings > Certificates > CA Certificates.

    2. Click Import.

    3. Browse to the file location and select it, or drag-and-drop it into the pop-up window.

    4. Click OK.

FortiManager-HA support automatic VRRP failover in Azure 7.4.2

FortiManager-HA support automatic VRRP failover in Azure 7.4.2

FortiManager-HA support automatic VRRP failover in Azure.

To configure automatic VRRP failover in Azure:
  1. Create FortiManager-VM in one ResourceGroup in same or different subnets.

  2. Allocate a secondary private IP (static) to be used as VIP of FortiManager-HA. Secondary IP will be assigned to the instance when its mode transitioned to master by fmgutil to call Azure cloud APIs within the instance itself

  3. Or create a static public IP in the ResourceGroup to be used as VIP.

  4. Enable Managed Identity for the VM and assign role with read-write access to the resource group. This is for VM to re-assign VIP.

  5. Configure FortiManager-HA, use private IP as peer IP, and the static public IP as VIP.

To configure FortiManager HA:
  1. On FortiManager, configure high availability at System Settings > HA.

    See the FortiManager Administration Guide for more information on configuring HA.

    When configuring HA, use the primary private IP as the Peer IP and the external static IP as the Cluster Virtual IP.

  2. Import the Azure Root CA to FortiManager. In order for the fmgutil to call the Azure API successfully, you must import the Azure Cloud CA certificate to each FortiManager instance. For more information on the CA used by Microsoft Entra ID (formerly Azure AD), see https://learn.microsoft.com/en-us/azure/security/fundamentals/azure-CA-details.

    1. Go to System Settings > Certificates > CA Certificates.

    2. Click Import.

    3. Browse to the file location and select it, or drag-and-drop it into the pop-up window.

    4. Click OK.