Fortinet black logo

Handbook

Active-active HA in transparent mode

6.0.0
Copy Link
Copy Doc ID 4afb0436-a998-11e9-81a4-00505692583a:586294
Download PDF

This section describes a simple HA network topology that includes an HA cluster of two generic FortiGates installed between an internal network and the internet and running in transparent mode.

Example topology

The figure below shows a transparent mode FortiGate HA cluster consisting of two FortiGates (FGT_ha_1 and FGT_ha_2) installed between the internet and internal network. The topology includes a router that performs NAT between the internal network and the internet. The cluster management IP address is 10.11.101.100.

Transparent mode HA network topology

Port3 and port4 are used as the heartbeat interfaces. Because the cluster consists of two FortiGates, you can make the connections between the heartbeat interfaces using crossover cables. You could also use switches and regular ethernet cables.

General configuration steps

This section includes GUI and CLI procedures. These procedures assume that the FortiGates are running the same FortiOS firmware build and are set to the factory default configuration.

In this example, the configuration steps are identical to the NAT mode configuration steps until the cluster is operating. When the cluster is operating, you can switch to transparent mode and add basic configuration settings to cluster.

General configuration steps
  1. Apply licenses to the FortiGates to become the cluster.
  2. Configure the FortiGates for HA operation.
    • Optionally change each unit’s host name.
    • Configure HA.
  3. Connect the cluster to the network.
  4. Confirm that the cluster units are operating as a cluster.
  5. Switch the cluster to transparent mode and add basic configuration settings to the cluster.
    • Switch to transparent mode, add the management IP address and a default route.
    • Add a password for the admin administrative account.
    • View cluster status from the GUI or CLI.

Configuring a transparent mode active-active cluster of two FortiGates - GUI

Use the following procedures to configure the FortiGates for HA operation using the FortiGate GUI. These procedures assume you are starting with two FortiGates with factory default settings.

note icon Waiting until you have established the cluster to switch to transparent mode means fewer configuration steps because you can switch the mode of the cluster in one step.
To configure the first FortiGate (host name FGT_ha_1)
  1. Register and apply licenses to the FortiGate before configuring it for HA operation. This includes licensing for FortiCare Support, IPS, AntiVirus, Web Filtering, Mobile Malware, FortiClient, FortiCloud, and additional virtual domains (VDOMs). All FortiGates in the cluster must have the same level of licensing for FortiGuard, FortiCloud, FortiClient, and VDOMs. FortiToken licenses can be added at any time because they are synchronized to all cluster members.

    If the FortiGates in the cluster will be running FortiOS Carrier, apply the FortiOS Carrier license before configuring the cluster (and before applying other licenses). Applying the FortiOS Carrier license sets the configuration to factory defaults, requiring you to repeat steps performed before applying the license.

    You can also install any third-party certificates on the primary FortiGate before forming the cluster. Once the cluster is formed, third-party certificates are synchronized to the backup FortiGate.

  2. Click on the System Information dashboard widget and select Configure settings in System > Settings.
  3. Enter a new Host Name for this FortiGate.

    New Name FGT_ha_1
  4. Select OK.
  5. Go to System > HA and change the following settings:

    Mode Active-Active
    Group Name example2.com
    Password HA_pass_2

    note icon This is the minimum recommended configuration for an active-active HA cluster. You can configure other HA options at this point, but if you wait until the cluster is operating you will only have to configure these options once for the cluster instead of separately for each cluster unit.
  6. Select OK.

    The FortiGate negotiates to establish an HA cluster. When you select OK you may temporarily lose connectivity with the FortiGate as the HA cluster negotiates and the FGCP changes the MAC address of the FortiGate interfaces. The MAC addresses of the FortiGate interfaces change to the following virtual MAC addresses:

    • port1 interface virtual MAC: 00-09-0f-09-00-00
    • port2 interface virtual MAC: 00-09-0f-09-00-01
    • port3 interface virtual MAC: 00-09-0f-09-00-02
    • port4 interface virtual MAC: 00-09-0f-09-00-03

    To reconnect sooner, you can update the ARP table of your management PC by deleting the ARP table entry for the FortiGate (or just deleting all arp table entries). You may be able to delete the arp table of your management PC from a command prompt using a command similar to arp -d.

    To confirm these MAC address changes, you can use the get hardware nic (or diagnose hardware deviceinfo nic) CLI command to view the virtual MAC address of any FortiGate interface. For example, use the following command to view the port1 interface virtual MAC address (MAC) and the port1 permanent MAC address (Permanent_HWaddr):

    get hardware nic port1

    .

    .

    .

    Current_HAaddr 00:09:0f:09:00:00

    Permanent_HWaddr 02:09:0f:78:18:c9

    .

    .

    .

  7. Power off the first FortiGate.
To configure the second FortiGate (host name FGT_ha_2)
  1. Register and apply licenses to the FortiGate before configuring it for HA operation.


  2. Click on the System Information dashboard widget and select Configure settings in System > Settings.
  3. Enter a new Host Name for this FortiGate.

    New Name FGT_ha_2
  4. Select OK.
  5. Go to System > HA and change the following settings:

    Mode Active-Active
    Group Name example2.com
    Password HA_pass_2
  6. Select OK.

    The FortiGate negotiates to establish an HA cluster. When you select OK you may temporarily lose connectivity with the FortiGate as the HA cluster negotiates and because the FGCP changes the MAC address of the FortiGate interfaces.

    To reconnect sooner, you can update the ARP table of your management PC by deleting the ARP table entry for the FortiGate (or just deleting all arp table entries). You may be able to delete the arp table of your management PC from a command prompt using a command similar to arp -d.

  7. Power off the second FortiGate.
To connect the cluster to the network
  1. Connect the port1 interfaces of FGT_ha_1 and FGT_ha_2 to a switch connected to the internet.
  2. Connect the port2 interfaces of FGT_ha_1 and FGT_ha_2 to a switch connected to the internal network.
  3. Connect the port3 interfaces of FGT_ha_1 and FGT_ha_2 together. You can use a crossover Ethernet cable or regular Ethernet cables and a switch.
  4. Connect the port4 interfaces of the cluster units together. You can use a crossover Ethernet cable or regular Ethernet cables and a switch.
  5. Power on the cluster units.

    The units start and negotiate to choose the primary unit and the subordinate unit. This negotiation occurs with no user intervention and normally takes less than a minute.

    When negotiation is complete the cluster is ready to be configured for your network.

To switch the cluster to transparent mode

Switching from NAT to transparent mode involves adding the transparent mode management IP address and default route.

note icon This is the minimum recommended configuration for an active-active HA cluster. You can configure other HA options at this point, but if you wait until the cluster is operating you will only have to configure these options once for the cluster instead of separately for each cluster unit.
  1. Start a web browser and browse to the address https://192.168.1.99 (remember to include the “s” in https://).

    The FortiGate Login is displayed.

  2. Type admin in the Name field and select Login.
  3. Under System Information, beside Operation Mode select Change.
  4. Set Operation Mode to transparent.
  5. Configure basic transparent mode settings.

    Operation Mode Transparent
    Management IP/Mask 10.11.101.100/24
    Default Gateway 10.11.101.2
  6. Select Apply.

    The cluster switches to operating in transparent mode. The virtual MAC addresses assigned to the cluster interfaces do not change.

To view cluster status

Use the following steps to view the cluster dashboard and cluster members list to confirm that the cluster units are operating as a cluster.

note icon Once the cluster is operating, because configuration changes are synchronized to all cluster units, configuring the cluster is the same as configuring an individual FortiGate. You could have performed the following configuration steps separately on each FortiGate before you connected them to form a cluster.
  1. Start a web browser and browse to the address https://10.11.101.100 (remember to include the “s” in https://).

    The FortiGate Login is displayed.

  2. Type admin in the Name field and select Login.

    The FortiGate dashboard is displayed.

    The HA Status dashboard widget displays how long the cluster has been operating (Uptime) and the time since the last failover occurred (State Changed). You can hover over the State Changed time to see the event that caused the state change. You can also click on the HA Status dashboard widget to configure HA settings or to get a listing of the most recent HA events recorded by the cluster.

  3. Go to System > HA to view the cluster members list.

    The list shows both cluster units, their host names, their roles in the cluster, and their device priorities. You can use this list to confirm that the cluster is operating normally. For example, if the list shows only one cluster unit then the other unit has left the cluster for some reason.

To troubleshoot the cluster configuration

If the cluster members list and the dashboard do not display information for both cluster units, the FortiGates are not functioning as a cluster. See Troubleshooting to troubleshoot the cluster.

To add basic configuration settings to the cluster

Use the following steps to configure the cluster. Note that the following are example configuration steps only and do not represent all of the steps required to configure the cluster for a given network.

  1. Log into the cluster GUI.
  2. Go to System > Administrators.
  3. Edit admin and select Change Password.
  4. Enter and confirm a new password.
  5. Select OK.
note icon You added a default gateway when you switched to transparent mode so you don’t need to add a default route as part of the basic configuration of the cluster at this point.

Configuring a transparent mode active-active cluster of two FortiGates - CLI

Use the following procedures to configure the FortiGates for transparent mode HA operation using the FortiGate CLI.

To configure each FortiGate for HA operation
  1. Power on the FortiGate.
  2. Connect a null modem cable to the communications port of the management computer and to the FortiGate Console port.
  3. Start HyperTerminal, enter a name for the connection, and select OK.
  4. Configure HyperTerminal to connect directly to the communications port on the computer to which you have connected the null modem cable and select OK.
  5. Select the following port settings and select OK.

    Bits per second 9600
    Data bits 8
    Parity None
    Stop bits 1
    Flow control None
  6. Press Enter to connect to the FortiGate CLI.

    The FortiGate CLI login prompt appears. If the prompt does not appear, press Enter. If it still does not appear, power off your FortiGate and power it back on. If you are connected, at this stage you will see startup messages that will confirm you are connected. The login prompt will appear after the startup has completed.

  7. Type admin and press Enter twice.
  8. Register and apply licenses to the FortiGate.
  9. Change the host name for this FortiGate. For example:

    config system global

    set hostname FGT_ha_1

    end

  10. Configure HA settings.

    config system ha

    set mode a-a

    set group-name example2.com

    set password HA_pass_2

    end

    note icon This is the minimum recommended configuration for an active-active HA cluster. You can also configure other HA options, but if you wait until after the cluster is operating you will only have to configure these options once for the cluster instead of separately for each cluster unit.

    The FortiGate negotiates to establish an HA cluster. You may temporarily lose network connectivity with the FortiGate as the HA cluster negotiates and the FGCP changes the MAC address of the FortiGate interfaces. The MAC addresses of the FortiGate interfaces change to the following virtual MAC addresses:

    • port1 interface virtual MAC: 00-09-0f-09-00-00
    • port2 interface virtual MAC: 00-09-0f-09-00-01
    • port3 interface virtual MAC: 00-09-0f-09-00-02
    • port4 interface virtual MAC: 00-09-0f-09-00-03

    To reconnect sooner, you can update the ARP table of your management PC by deleting the ARP table entry for the FortiGate (or just deleting all arp table entries). You may be able to delete the arp table of your management PC from a command prompt using a command similar to arp -d.

    To confirm these MAC address changes, you can use the get hardware nic (or diagnose hardware deviceinfo nic) CLI command to view the virtual MAC address of any FortiGate interface. For example, use the following command to view the port1 interface virtual MAC address (MAC) and the port1 permanent MAC address (Permanent_HWaddr):

    get hardware nic port1

    .

    .

    .

    Current_HAaddr 00:09:0f:09:00:00

    Permanent_HWaddr 02:09:0f:78:18:c9

    .

    .

    .

  11. Display the HA configuration (optional).

    get system ha

    group-id : 0

    group-name : example2.com

    mode : a-a

    password : *

    hbdev : "port3" 50 "port4" 50

    session-sync-dev :

    route-ttl : 10

    route-wait : 0

    route-hold : 10

    sync-config : enable

    encryption : disable

    authentication : disable

    hb-interval : 2

    hb-lost-threshold : 20

    hello-holddown : 20

    arps : 5

    arps-interval : 8

    session-pickup : disable

    update-all-session-timer: disable

    session-sync-daemon-number: 1

    link-failed-signal : disable

    uninterruptible-upgrade: enable

    ha-mgmt-status : disable

    ha-eth-type : 8890

    hc-eth-type : 8891

    l2ep-eth-type : 8893

    ha-uptime-diff-margin: 300

    vcluster2 : disable

    vcluster-id : 1

    override : disable

    priority : 128

    slave-switch-standby: disable

    minimum-worker-threshold: 1

    monitor :

    pingserver-monitor-interface:

    pingserver-failover-threshold: 0

    pingserver-slave-force-reset: enable

    pingserver-flip-timeout: 60

    vdom : "root"

  12. Power off the FortiGate.
To configure the second FortiGate (host name FGT_ha_2)
  1. Power on the FortiGate.
  2. Connect a null modem cable to the communications port of the management computer and to the FortiGate Console port.
  3. Start HyperTerminal, enter a name for the connection, and select OK.
  4. Configure HyperTerminal to connect directly to the communications port on the computer to which you have connected the null modem cable and select OK.
  5. Select the following port settings and select OK.

    Bits per second 9600
    Data bits 8
    Parity None
    Stop bits 1
    Flow control None
  6. Press Enter to connect to the FortiGate CLI.

    The FortiGate CLI login prompt appears. If the prompt does not appear, press Enter. If it still does not appear, power off your FortiGate and power it back on. If you are connected, at this stage you will see startup messages that will confirm you are connected. The login prompt will appear after the startup has completed.

  7. Type admin and press Enter twice.
  8. Register and apply licenses to the FortiGate.
  9. Change the host name for this FortiGate.

    config system global

    set hostname FGT_ha_2

    end

  10. Configure HA settings.

    config system ha

    set mode a-a

    set group-name example2.com

    set password HA_pass_2

    end

    The FortiGate negotiates to establish an HA cluster. You may temporarily lose network connectivity with the FortiGate as the HA cluster negotiates and because the FGCP changes the MAC address of the FortiGate interfaces.

    To reconnect sooner, you can update the ARP table of your management PC by deleting the ARP table entry for the FortiGate (or just deleting all arp table entries). You may be able to delete the arp table of your management PC from a command prompt using a command similar to arp -d.

  11. Display the HA configuration (optional).

    get system ha

    group-id : 0

    group-name : example2.com

    mode : a-a

    password : *

    hbdev : "port3" 50 "port4" 50

    session-sync-dev :

    route-ttl : 10

    route-wait : 0

    route-hold : 10

    sync-config : enable

    encryption : disable

    authentication : disable

    hb-interval : 2

    hb-lost-threshold : 20

    hello-holddown : 20

    arps : 5

    arps-interval : 8

    session-pickup : disable

    update-all-session-timer: disable

    session-sync-daemon-number: 1

    link-failed-signal : disable

    uninterruptible-upgrade: enable

    ha-mgmt-status : disable

    ha-eth-type : 8890

    hc-eth-type : 8891

    l2ep-eth-type : 8893

    ha-uptime-diff-margin: 300

    vcluster2 : disable

    vcluster-id : 1

    override : disable

    priority : 128

    schedule : round-robin

    monitor :

    pingserver-monitor-interface:

    pingserver-failover-threshold: 0

    pingserver-slave-force-reset: enable

    pingserver-flip-timeout: 60

    vdom : "root"

    schedule : round-robin

  12. Power off the FortiGate.
To connect the cluster to the network
  1. Connect the port1 interfaces of FGT_ha_1 and FGT_ha_2 to a switch connected to the internet.
  2. Connect the port2 interfaces of FGT_ha_1 and FGT_ha_2 to a switch connected to the internal network.
  3. Connect the port3 interfaces of FGT_ha_1 and FGT_ha_2 together. You can use a crossover Ethernet cable or regular Ethernet cables and a switch.
  4. Connect the port4 interfaces of the cluster units together. You can use a crossover Ethernet cable or regular Ethernet cables and a switch.
  5. Power on the cluster units.

    The units start and negotiate to choose the primary unit and the subordinate unit. This negotiation occurs with no user intervention and normally takes less than a minute.

    When negotiation is complete the cluster is ready to be configured for your network.

To connect to the cluster CLI and switch the cluster to transparent mode
  1. Determine which cluster unit is the primary unit.

    • Use the null-modem cable and serial connection to re-connect to the CLI of one of the cluster units.
    • Enter the command get system status.
    • If the command output includes Current HA mode: a-a, master, the cluster units are operating as a cluster and you have connected to the primary unit. Continue with Step 2.
    • If the command output includes Current HA mode: a-a, backup, you have connected to a subordinate unit. Connect to the other cluster unit, which should be the primary unit and continue with Step 2.

    note icon If the command output includes Current HA mode: standalone, the cluster unit is not operating in HA mode.
  2. Change to transparent mode.

    config system settings

    set opmode transparent

    set manageip 192.168.20.3/24

    set gateway 192.168.20.1

    end

    The cluster switches to transparent Mode, and your administration session is disconnected.

    You can now connect to the cluster CLI using SSH to connect to the cluster internal interface using the management IP address (192.168.20.3).

To view cluster status

Use the following steps to view cluster status from the CLI.

  1. Determine which cluster unit is the primary unit.

    • Use the null-modem cable and serial connection to re-connect to the CLI of one of the cluster units.
    • Enter the command get system status.
    • If the command output includes Current HA mode: a-a, master, the cluster units are operating as a cluster and you have connected to the primary unit. Continue with the next step (step 2 below).
    • If the command output includes Current HA mode: a-a, backup, you have connected to a subordinate unit. Connect the null-modem cable to the other cluster unit, which should be the primary unit and continue with the next step (step 2 below).

    note icon If the command output includes Current HA mode: standalone, the cluster unit is not operating in HA mode and you should review your HA configuration.
  2. Enter the following command to confirm the HA configuration of the cluster:

    get system ha status
    HA Health Status: OK
    Model: FortiGate-XXXX
    Mode: HA A-P
    Group: 0
    Debug: 0
    Cluster Uptime: 7 days 00:30:26
    .
    .
    .

    You can use this command to confirm that the cluster is healthy and operating normally, some information about the cluster configuration, and information about how long the cluster has been operating. Information not shown in this example includes how the primary unit was selected, configuration synchronization status, usage stats for each cluster unit, heartbeat status, and the relative priorities of the cluster units.

To troubleshoot the cluster configuration

If the cluster members list and the dashboard do not display information for both cluster units the FortiGates are not functioning as a cluster. See Troubleshooting to troubleshoot the cluster.

To add a password for the admin administrative account
  1. Add a password for the admin administrative account.

    config system admin

    edit admin

    set password <psswrd>

    end

This section describes a simple HA network topology that includes an HA cluster of two generic FortiGates installed between an internal network and the internet and running in transparent mode.

Example topology

The figure below shows a transparent mode FortiGate HA cluster consisting of two FortiGates (FGT_ha_1 and FGT_ha_2) installed between the internet and internal network. The topology includes a router that performs NAT between the internal network and the internet. The cluster management IP address is 10.11.101.100.

Transparent mode HA network topology

Port3 and port4 are used as the heartbeat interfaces. Because the cluster consists of two FortiGates, you can make the connections between the heartbeat interfaces using crossover cables. You could also use switches and regular ethernet cables.

General configuration steps

This section includes GUI and CLI procedures. These procedures assume that the FortiGates are running the same FortiOS firmware build and are set to the factory default configuration.

In this example, the configuration steps are identical to the NAT mode configuration steps until the cluster is operating. When the cluster is operating, you can switch to transparent mode and add basic configuration settings to cluster.

General configuration steps
  1. Apply licenses to the FortiGates to become the cluster.
  2. Configure the FortiGates for HA operation.
    • Optionally change each unit’s host name.
    • Configure HA.
  3. Connect the cluster to the network.
  4. Confirm that the cluster units are operating as a cluster.
  5. Switch the cluster to transparent mode and add basic configuration settings to the cluster.
    • Switch to transparent mode, add the management IP address and a default route.
    • Add a password for the admin administrative account.
    • View cluster status from the GUI or CLI.

Configuring a transparent mode active-active cluster of two FortiGates - GUI

Use the following procedures to configure the FortiGates for HA operation using the FortiGate GUI. These procedures assume you are starting with two FortiGates with factory default settings.

note icon Waiting until you have established the cluster to switch to transparent mode means fewer configuration steps because you can switch the mode of the cluster in one step.
To configure the first FortiGate (host name FGT_ha_1)
  1. Register and apply licenses to the FortiGate before configuring it for HA operation. This includes licensing for FortiCare Support, IPS, AntiVirus, Web Filtering, Mobile Malware, FortiClient, FortiCloud, and additional virtual domains (VDOMs). All FortiGates in the cluster must have the same level of licensing for FortiGuard, FortiCloud, FortiClient, and VDOMs. FortiToken licenses can be added at any time because they are synchronized to all cluster members.

    If the FortiGates in the cluster will be running FortiOS Carrier, apply the FortiOS Carrier license before configuring the cluster (and before applying other licenses). Applying the FortiOS Carrier license sets the configuration to factory defaults, requiring you to repeat steps performed before applying the license.

    You can also install any third-party certificates on the primary FortiGate before forming the cluster. Once the cluster is formed, third-party certificates are synchronized to the backup FortiGate.

  2. Click on the System Information dashboard widget and select Configure settings in System > Settings.
  3. Enter a new Host Name for this FortiGate.

    New Name FGT_ha_1
  4. Select OK.
  5. Go to System > HA and change the following settings:

    Mode Active-Active
    Group Name example2.com
    Password HA_pass_2

    note icon This is the minimum recommended configuration for an active-active HA cluster. You can configure other HA options at this point, but if you wait until the cluster is operating you will only have to configure these options once for the cluster instead of separately for each cluster unit.
  6. Select OK.

    The FortiGate negotiates to establish an HA cluster. When you select OK you may temporarily lose connectivity with the FortiGate as the HA cluster negotiates and the FGCP changes the MAC address of the FortiGate interfaces. The MAC addresses of the FortiGate interfaces change to the following virtual MAC addresses:

    • port1 interface virtual MAC: 00-09-0f-09-00-00
    • port2 interface virtual MAC: 00-09-0f-09-00-01
    • port3 interface virtual MAC: 00-09-0f-09-00-02
    • port4 interface virtual MAC: 00-09-0f-09-00-03

    To reconnect sooner, you can update the ARP table of your management PC by deleting the ARP table entry for the FortiGate (or just deleting all arp table entries). You may be able to delete the arp table of your management PC from a command prompt using a command similar to arp -d.

    To confirm these MAC address changes, you can use the get hardware nic (or diagnose hardware deviceinfo nic) CLI command to view the virtual MAC address of any FortiGate interface. For example, use the following command to view the port1 interface virtual MAC address (MAC) and the port1 permanent MAC address (Permanent_HWaddr):

    get hardware nic port1

    .

    .

    .

    Current_HAaddr 00:09:0f:09:00:00

    Permanent_HWaddr 02:09:0f:78:18:c9

    .

    .

    .

  7. Power off the first FortiGate.
To configure the second FortiGate (host name FGT_ha_2)
  1. Register and apply licenses to the FortiGate before configuring it for HA operation.


  2. Click on the System Information dashboard widget and select Configure settings in System > Settings.
  3. Enter a new Host Name for this FortiGate.

    New Name FGT_ha_2
  4. Select OK.
  5. Go to System > HA and change the following settings:

    Mode Active-Active
    Group Name example2.com
    Password HA_pass_2
  6. Select OK.

    The FortiGate negotiates to establish an HA cluster. When you select OK you may temporarily lose connectivity with the FortiGate as the HA cluster negotiates and because the FGCP changes the MAC address of the FortiGate interfaces.

    To reconnect sooner, you can update the ARP table of your management PC by deleting the ARP table entry for the FortiGate (or just deleting all arp table entries). You may be able to delete the arp table of your management PC from a command prompt using a command similar to arp -d.

  7. Power off the second FortiGate.
To connect the cluster to the network
  1. Connect the port1 interfaces of FGT_ha_1 and FGT_ha_2 to a switch connected to the internet.
  2. Connect the port2 interfaces of FGT_ha_1 and FGT_ha_2 to a switch connected to the internal network.
  3. Connect the port3 interfaces of FGT_ha_1 and FGT_ha_2 together. You can use a crossover Ethernet cable or regular Ethernet cables and a switch.
  4. Connect the port4 interfaces of the cluster units together. You can use a crossover Ethernet cable or regular Ethernet cables and a switch.
  5. Power on the cluster units.

    The units start and negotiate to choose the primary unit and the subordinate unit. This negotiation occurs with no user intervention and normally takes less than a minute.

    When negotiation is complete the cluster is ready to be configured for your network.

To switch the cluster to transparent mode

Switching from NAT to transparent mode involves adding the transparent mode management IP address and default route.

note icon This is the minimum recommended configuration for an active-active HA cluster. You can configure other HA options at this point, but if you wait until the cluster is operating you will only have to configure these options once for the cluster instead of separately for each cluster unit.
  1. Start a web browser and browse to the address https://192.168.1.99 (remember to include the “s” in https://).

    The FortiGate Login is displayed.

  2. Type admin in the Name field and select Login.
  3. Under System Information, beside Operation Mode select Change.
  4. Set Operation Mode to transparent.
  5. Configure basic transparent mode settings.

    Operation Mode Transparent
    Management IP/Mask 10.11.101.100/24
    Default Gateway 10.11.101.2
  6. Select Apply.

    The cluster switches to operating in transparent mode. The virtual MAC addresses assigned to the cluster interfaces do not change.

To view cluster status

Use the following steps to view the cluster dashboard and cluster members list to confirm that the cluster units are operating as a cluster.

note icon Once the cluster is operating, because configuration changes are synchronized to all cluster units, configuring the cluster is the same as configuring an individual FortiGate. You could have performed the following configuration steps separately on each FortiGate before you connected them to form a cluster.
  1. Start a web browser and browse to the address https://10.11.101.100 (remember to include the “s” in https://).

    The FortiGate Login is displayed.

  2. Type admin in the Name field and select Login.

    The FortiGate dashboard is displayed.

    The HA Status dashboard widget displays how long the cluster has been operating (Uptime) and the time since the last failover occurred (State Changed). You can hover over the State Changed time to see the event that caused the state change. You can also click on the HA Status dashboard widget to configure HA settings or to get a listing of the most recent HA events recorded by the cluster.

  3. Go to System > HA to view the cluster members list.

    The list shows both cluster units, their host names, their roles in the cluster, and their device priorities. You can use this list to confirm that the cluster is operating normally. For example, if the list shows only one cluster unit then the other unit has left the cluster for some reason.

To troubleshoot the cluster configuration

If the cluster members list and the dashboard do not display information for both cluster units, the FortiGates are not functioning as a cluster. See Troubleshooting to troubleshoot the cluster.

To add basic configuration settings to the cluster

Use the following steps to configure the cluster. Note that the following are example configuration steps only and do not represent all of the steps required to configure the cluster for a given network.

  1. Log into the cluster GUI.
  2. Go to System > Administrators.
  3. Edit admin and select Change Password.
  4. Enter and confirm a new password.
  5. Select OK.
note icon You added a default gateway when you switched to transparent mode so you don’t need to add a default route as part of the basic configuration of the cluster at this point.

Configuring a transparent mode active-active cluster of two FortiGates - CLI

Use the following procedures to configure the FortiGates for transparent mode HA operation using the FortiGate CLI.

To configure each FortiGate for HA operation
  1. Power on the FortiGate.
  2. Connect a null modem cable to the communications port of the management computer and to the FortiGate Console port.
  3. Start HyperTerminal, enter a name for the connection, and select OK.
  4. Configure HyperTerminal to connect directly to the communications port on the computer to which you have connected the null modem cable and select OK.
  5. Select the following port settings and select OK.

    Bits per second 9600
    Data bits 8
    Parity None
    Stop bits 1
    Flow control None
  6. Press Enter to connect to the FortiGate CLI.

    The FortiGate CLI login prompt appears. If the prompt does not appear, press Enter. If it still does not appear, power off your FortiGate and power it back on. If you are connected, at this stage you will see startup messages that will confirm you are connected. The login prompt will appear after the startup has completed.

  7. Type admin and press Enter twice.
  8. Register and apply licenses to the FortiGate.
  9. Change the host name for this FortiGate. For example:

    config system global

    set hostname FGT_ha_1

    end

  10. Configure HA settings.

    config system ha

    set mode a-a

    set group-name example2.com

    set password HA_pass_2

    end

    note icon This is the minimum recommended configuration for an active-active HA cluster. You can also configure other HA options, but if you wait until after the cluster is operating you will only have to configure these options once for the cluster instead of separately for each cluster unit.

    The FortiGate negotiates to establish an HA cluster. You may temporarily lose network connectivity with the FortiGate as the HA cluster negotiates and the FGCP changes the MAC address of the FortiGate interfaces. The MAC addresses of the FortiGate interfaces change to the following virtual MAC addresses:

    • port1 interface virtual MAC: 00-09-0f-09-00-00
    • port2 interface virtual MAC: 00-09-0f-09-00-01
    • port3 interface virtual MAC: 00-09-0f-09-00-02
    • port4 interface virtual MAC: 00-09-0f-09-00-03

    To reconnect sooner, you can update the ARP table of your management PC by deleting the ARP table entry for the FortiGate (or just deleting all arp table entries). You may be able to delete the arp table of your management PC from a command prompt using a command similar to arp -d.

    To confirm these MAC address changes, you can use the get hardware nic (or diagnose hardware deviceinfo nic) CLI command to view the virtual MAC address of any FortiGate interface. For example, use the following command to view the port1 interface virtual MAC address (MAC) and the port1 permanent MAC address (Permanent_HWaddr):

    get hardware nic port1

    .

    .

    .

    Current_HAaddr 00:09:0f:09:00:00

    Permanent_HWaddr 02:09:0f:78:18:c9

    .

    .

    .

  11. Display the HA configuration (optional).

    get system ha

    group-id : 0

    group-name : example2.com

    mode : a-a

    password : *

    hbdev : "port3" 50 "port4" 50

    session-sync-dev :

    route-ttl : 10

    route-wait : 0

    route-hold : 10

    sync-config : enable

    encryption : disable

    authentication : disable

    hb-interval : 2

    hb-lost-threshold : 20

    hello-holddown : 20

    arps : 5

    arps-interval : 8

    session-pickup : disable

    update-all-session-timer: disable

    session-sync-daemon-number: 1

    link-failed-signal : disable

    uninterruptible-upgrade: enable

    ha-mgmt-status : disable

    ha-eth-type : 8890

    hc-eth-type : 8891

    l2ep-eth-type : 8893

    ha-uptime-diff-margin: 300

    vcluster2 : disable

    vcluster-id : 1

    override : disable

    priority : 128

    slave-switch-standby: disable

    minimum-worker-threshold: 1

    monitor :

    pingserver-monitor-interface:

    pingserver-failover-threshold: 0

    pingserver-slave-force-reset: enable

    pingserver-flip-timeout: 60

    vdom : "root"

  12. Power off the FortiGate.
To configure the second FortiGate (host name FGT_ha_2)
  1. Power on the FortiGate.
  2. Connect a null modem cable to the communications port of the management computer and to the FortiGate Console port.
  3. Start HyperTerminal, enter a name for the connection, and select OK.
  4. Configure HyperTerminal to connect directly to the communications port on the computer to which you have connected the null modem cable and select OK.
  5. Select the following port settings and select OK.

    Bits per second 9600
    Data bits 8
    Parity None
    Stop bits 1
    Flow control None
  6. Press Enter to connect to the FortiGate CLI.

    The FortiGate CLI login prompt appears. If the prompt does not appear, press Enter. If it still does not appear, power off your FortiGate and power it back on. If you are connected, at this stage you will see startup messages that will confirm you are connected. The login prompt will appear after the startup has completed.

  7. Type admin and press Enter twice.
  8. Register and apply licenses to the FortiGate.
  9. Change the host name for this FortiGate.

    config system global

    set hostname FGT_ha_2

    end

  10. Configure HA settings.

    config system ha

    set mode a-a

    set group-name example2.com

    set password HA_pass_2

    end

    The FortiGate negotiates to establish an HA cluster. You may temporarily lose network connectivity with the FortiGate as the HA cluster negotiates and because the FGCP changes the MAC address of the FortiGate interfaces.

    To reconnect sooner, you can update the ARP table of your management PC by deleting the ARP table entry for the FortiGate (or just deleting all arp table entries). You may be able to delete the arp table of your management PC from a command prompt using a command similar to arp -d.

  11. Display the HA configuration (optional).

    get system ha

    group-id : 0

    group-name : example2.com

    mode : a-a

    password : *

    hbdev : "port3" 50 "port4" 50

    session-sync-dev :

    route-ttl : 10

    route-wait : 0

    route-hold : 10

    sync-config : enable

    encryption : disable

    authentication : disable

    hb-interval : 2

    hb-lost-threshold : 20

    hello-holddown : 20

    arps : 5

    arps-interval : 8

    session-pickup : disable

    update-all-session-timer: disable

    session-sync-daemon-number: 1

    link-failed-signal : disable

    uninterruptible-upgrade: enable

    ha-mgmt-status : disable

    ha-eth-type : 8890

    hc-eth-type : 8891

    l2ep-eth-type : 8893

    ha-uptime-diff-margin: 300

    vcluster2 : disable

    vcluster-id : 1

    override : disable

    priority : 128

    schedule : round-robin

    monitor :

    pingserver-monitor-interface:

    pingserver-failover-threshold: 0

    pingserver-slave-force-reset: enable

    pingserver-flip-timeout: 60

    vdom : "root"

    schedule : round-robin

  12. Power off the FortiGate.
To connect the cluster to the network
  1. Connect the port1 interfaces of FGT_ha_1 and FGT_ha_2 to a switch connected to the internet.
  2. Connect the port2 interfaces of FGT_ha_1 and FGT_ha_2 to a switch connected to the internal network.
  3. Connect the port3 interfaces of FGT_ha_1 and FGT_ha_2 together. You can use a crossover Ethernet cable or regular Ethernet cables and a switch.
  4. Connect the port4 interfaces of the cluster units together. You can use a crossover Ethernet cable or regular Ethernet cables and a switch.
  5. Power on the cluster units.

    The units start and negotiate to choose the primary unit and the subordinate unit. This negotiation occurs with no user intervention and normally takes less than a minute.

    When negotiation is complete the cluster is ready to be configured for your network.

To connect to the cluster CLI and switch the cluster to transparent mode
  1. Determine which cluster unit is the primary unit.

    • Use the null-modem cable and serial connection to re-connect to the CLI of one of the cluster units.
    • Enter the command get system status.
    • If the command output includes Current HA mode: a-a, master, the cluster units are operating as a cluster and you have connected to the primary unit. Continue with Step 2.
    • If the command output includes Current HA mode: a-a, backup, you have connected to a subordinate unit. Connect to the other cluster unit, which should be the primary unit and continue with Step 2.

    note icon If the command output includes Current HA mode: standalone, the cluster unit is not operating in HA mode.
  2. Change to transparent mode.

    config system settings

    set opmode transparent

    set manageip 192.168.20.3/24

    set gateway 192.168.20.1

    end

    The cluster switches to transparent Mode, and your administration session is disconnected.

    You can now connect to the cluster CLI using SSH to connect to the cluster internal interface using the management IP address (192.168.20.3).

To view cluster status

Use the following steps to view cluster status from the CLI.

  1. Determine which cluster unit is the primary unit.

    • Use the null-modem cable and serial connection to re-connect to the CLI of one of the cluster units.
    • Enter the command get system status.
    • If the command output includes Current HA mode: a-a, master, the cluster units are operating as a cluster and you have connected to the primary unit. Continue with the next step (step 2 below).
    • If the command output includes Current HA mode: a-a, backup, you have connected to a subordinate unit. Connect the null-modem cable to the other cluster unit, which should be the primary unit and continue with the next step (step 2 below).

    note icon If the command output includes Current HA mode: standalone, the cluster unit is not operating in HA mode and you should review your HA configuration.
  2. Enter the following command to confirm the HA configuration of the cluster:

    get system ha status
    HA Health Status: OK
    Model: FortiGate-XXXX
    Mode: HA A-P
    Group: 0
    Debug: 0
    Cluster Uptime: 7 days 00:30:26
    .
    .
    .

    You can use this command to confirm that the cluster is healthy and operating normally, some information about the cluster configuration, and information about how long the cluster has been operating. Information not shown in this example includes how the primary unit was selected, configuration synchronization status, usage stats for each cluster unit, heartbeat status, and the relative priorities of the cluster units.

To troubleshoot the cluster configuration

If the cluster members list and the dashboard do not display information for both cluster units the FortiGates are not functioning as a cluster. See Troubleshooting to troubleshoot the cluster.

To add a password for the admin administrative account
  1. Add a password for the admin administrative account.

    config system admin

    edit admin

    set password <psswrd>

    end