This recipe is part of the process of deploying FortiGate HA for AWS. See below for the rest of the recipes in this process:
- Customize the CFT template
- Check the prerequisites
- Review the network failover diagram
- Invoke the CFT template
- Connect to the FortiGates
- [Connectivity test] Configure FortiGate firewall policy
- [Failover test] Shut down FortiGate A
- Let’s test if the configuration synchronizes between the two FortiGate instances by creating a new incoming firewall policy. Navigate to Policy & Objects > IP4 Policy, then click Create New. Enter the policy name, specify incoming and outgoing ports, source, destination, and service. In this example, all is selected for all options. Select security policies as desired, then click OK.
The policy has been created.
- Log into FortiGate B by connecting to its management port at https://184.108.40.206. Your IP address will be different. The username is admin. If HA works, the password is the same as FortiGate A. Otherwise, the login password is FortiGate B’s instance ID.
The same new firewall policy has automatically been created on FortiGate B.
Latest posts by In Hye Lee (see all)
- Connect to the FortiGate - February 21, 2018
- Deploying FortiGate for GCP - February 21, 2018
- (Connectivity test) Configure FortiGate firewall policies and virtual IPs - February 14, 2018