Active-Active Lab
Active-Active Lab
Change Hostname:
Now, you should login to MASTER Firewall, I recommend changing the hostname before login,
this will improve the ability to identify the different FortiGate Unit Firewall.
Configure Interfaces:
Go to Network>Interfaces select port1 Click Edit. In Alias type WAN, change the Address Mode
to Manual type IP/Netmask 192.168.122.100/24, in Administrative access leave all the rest of
configuration default and press OK button. The firewall will be disconnected login with new
Management IP address which is the WAN IP address as well.
Go to Network>Interfaces select port2 Click Edit in Alias type LAN, change the Address Mode to
Manual type IP/Netmask 192.168.1.100/24, in Administrative access only checked PING leave
all the rest of configuration default & press OK.
Change Hostname:
Now, you should login to SLAVE Firewall, I recommend changing the hostname before login,
this will improve the ability to identify the different FortiGate Unit Firewall.
HA Active-Active Configuration:
Same as master, Go to System > HA Select the Active-Active mode. Give Device Priority to
SLAVE Firewall a lower number than the Master one (50). Set the same group name and same
password for the cluster which already set on MASTER Firewall. Enable Session Pickup: Enable
this option to sync master to backup machine. Check the interface you want to monitor
normally internet. Enable two heartbeat to create a stable HA.
Verification:
Check the status of cluster group make sure master and slave machine are correct. Go to
Primary Firewall go to System > HA you will find both firewall setting here. The HA status page
shows both FortiGate in the cluster. It also shows that Primary is the primary (master) and the
page also shows that Backup is the primary (master) FortiGate.
Go to Dashboard > Status, The HA Status dashboard widget also shows synchronization status.
Failover Verification:
Let’s put continue ping from any LAN PC.
Let’s powered off the primary Firewall you will be logging into the backup FortiGate.
You will see a momentary pause in the ping results, until traffic diverts to the backup FortiGate,
allowing the ping traffic to continue.
Check the host name to verify the FortiGate that you have logged into. The FortiGate continues
to operate in HA mode.
if restart the primary FortiGate, after a few minutes it should rejoin the cluster and operate as
the backup FortiGate. Traffic should not be disrupted when the restarted primary unit rejoins
the cluster. The Override behavior allows firewall with higher numerical value to resume as
Primary Firewall enable Override on Primary Firewall.
PrimaryFW # config system ha
PrimaryFW (ha) # set override enable
Change the hostname of the FortiGate
config system global
set hostname PrimaryFW
end
Configure HA on Primary Firewall
config system ha
set group-id 1
set group-name "HAG"
set mode a-p
set hbdev "port3" 200 "port4" 100
set override disable
set priority 100
set monitor "port1"
end
Configured a policy to allow traffic from LAN to WAN
config firewall policy
edit 1
set name "LAN2WAN"
set srcintf "port2"
set dstintf "port1"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
set logtraffic all
set logtraffic-start enable
end