Fortinet Document Library

Version:


Table of Contents

About FortiGate for Azure

Deploying FortiGate on Azure

Deploying auto scaling on Azure

Single FortiGate-VM Deployment

Use case: High availability for FortiGate on Azure

Use case: Automatically updating dynamic addresses using Fabric connector

Resources

Upgrade Path Tool
6.0.0
Copy Link

Accessing FortiGate Instances

The following details how to access the FortiGate inside the autoscaling group.

  1. Go to the external load balancer > Inbound NAT rules.

  2. Currently, there are four rules: a rule for SSH access, and one for HTTPS access to each instance. The below shows the SSH access rule, then the HTTPS access rule.

    To access each FortiGate instance, you can use SSH or HTTPS to access the public IP address and port. In the above example, you would do the following to access instances 1 and 2:

    • Instance 1:
      • SSH: 40.81.156.247 port 50000
      • HTTPS: 40.81.156.247 port 4000
    • Instance 2:
      • SSH: 40.81.156.247 port 50001
      • HTTPS: 40.81.156.247 port 4001

Resources

Accessing FortiGate Instances

The following details how to access the FortiGate inside the autoscaling group.

  1. Go to the external load balancer > Inbound NAT rules.

  2. Currently, there are four rules: a rule for SSH access, and one for HTTPS access to each instance. The below shows the SSH access rule, then the HTTPS access rule.

    To access each FortiGate instance, you can use SSH or HTTPS to access the public IP address and port. In the above example, you would do the following to access instances 1 and 2:

    • Instance 1:
      • SSH: 40.81.156.247 port 50000
      • HTTPS: 40.81.156.247 port 4000
    • Instance 2:
      • SSH: 40.81.156.247 port 50001
      • HTTPS: 40.81.156.247 port 4001