To troubleshoot the cluster configuration
If the cluster members list and the dashboard do not display information for both cluster units, the FortiGate units are not functioning as a cluster. See Active-active HA cluster in Transparent mode on page 1373 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 web-based manager.
2. Go to System > Admin > Administrators.
3. Edit admin and select Change Password.
4. Enter and confirm a new password.
5. Select OK.
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 FortiGate units – CLI
Use the following procedures to configure the FortiGate units for Transparent mode HA operation using the FortiGate CLI.
To configure each FortiGate unit for HA operation
1. Power on the FortiGate unit.
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 unit CLI login prompt appears.If the prompt does not appear, press Enter. If it still does not appear, power off your FortiGate unit 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 unit. This includes FortiCloud activation, FortiClient licensing, and FortiToken licensing, and entering a license key if you purchased more than 10 Virtual Domains (VDOMS).
9. 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.
10. Change the host name for this FortiGate unit. For example:
config system global
set hostname FGT_ha_1 end
11. Configure HA settings.
config system ha set mode a-a
set group-name example2.com set password HA_pass_2
end
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 unit negotiates to establish an HA cluster. You may temporarily lose network connectivity with the FortiGate unit as the HA cluster negotiates and the FGCP changes the MAC address of the FortiGate unit 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 l port2 interface virtual MAC: 00-09-0f-09-00-01 l port3 interface virtual MAC: 00-09-0f-09-00-02 l 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 unit (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 unit 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
10. 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 helo-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”
11. Power off the FortiGate unit.
To configure the second FortiGate unit (host name FGT_ha_2)
1. Power on the FortiGate unit.
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 unit CLI login prompt appears.If the prompt does not appear, press Enter. If it still does not appear, power off your FortiGate unit 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 unit. This includes FortiCloud activation, FortiClient licensing, and
FortiToken licensing, and entering a license key if you purchased more than 10 Virtual Domains (VDOMS).
9. Change the host name for this FortiGate unit.
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 unit negotiates to establish an HA cluster. You may temporarily lose network connectivity with the FortiGate unit as the HA cluster negotiates and because the FGCP changes the MAC address of the FortiGate unit interfaces.
To reconnect sooner, you can update the ARP table of your management PC by deleting the ARP table entry for the FortiGate unit (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 helo-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 unit.