Setting up two new FortiGates as an FGCP cluster

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.

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.

config system global

set hostname FGT_ha_2 end

11. Configure HA settings.

config system ha set mode a-p

set group-name example1.com set password HA_pass_1

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.

12. Display the HA configuration (optional).

get system ha group-id : 0

group-name : example1.com mode : a-p

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”

13. Power off the FortiGate unit.

This entry was posted in FortiOS 5.4 Handbook and tagged , on by .

About Mike

Michael Pruett, CISSP has a wide range of cyber-security and network engineering expertise. The plethora of vendors that resell hardware but have zero engineering knowledge resulting in the wrong hardware or configuration being deployed is a major pet peeve of Michael's. This site was started in an effort to spread information while providing the option of quality consulting services at a much lower price than Fortinet Professional Services. Owns PacketLlama.Com (Fortinet Hardware Sales) and Office Of The CISO, LLC (Cybersecurity consulting firm).

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.