This recipe is part of the process of deploying FortiGate HA load-balancing for Microsoft Azure using Azure load balancer. See below for the rest of the recipes in this process:
- Basic concepts
- Traffic flow
- Azure load balancer
- Inbound NAT rules
- Load balancing rules
- Locate FortiGate HA for Azure in the Azure portal or Azure marketplace
- Determine your licensing model
- Configure FortiGate initial parameters
- Create VNet and subnets in network settings
- Select Azure instance type
- Assign Azure IP address
- Validate deployment resources
- Create FortiGate instances
- Connect to the FortiGate
- [Use case] Set up a Windows Server in the protected network
- Configure FortiGate firewall policies and virtual IPs
- [Failover test] Create load balancing rules and access the Windows Server via remote desktop
- In the third step, FortiGate IP address assignment, you will configure a static public IP address for FortiGate node A and for node B. If you click First public IP address resource name, you will see a preconfigured name, with Dynamic selected. Leave these as shown, as there is no need to click Create New unless you want to change the name.
To access FortiGate’s management GUI console or to connect by SSH, you need public addresses assigned to FortiGate node A and node B. Static IP addresses are more convenient, as they are configured by default. Usually the default configuration is fine without modification.
- After confirmation, click OK.
- Repeat the process for node B, then click OK.
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