If you wish to use different names and ranges than the ones in the Deployment parameters table, use parameters that will not conflict with the on-premises network. If the on-premises network overlaps with the IP range 172.16.0.0/16, you must select and set up a different network range and subnets.
The following table summarizes the parameters that are used in these deployments for reference. You can find steps on how to connect the FortiGate NVA to the Azure Stack Hub VNET to in your on-premises network.įor more information on how to deploy the FortiGate solution in an active-passive (HA) set up, see the details in the Fortinet Document Library article HA for FortiGate-VM on Azure. This procedure uses the Single FortiGate-VM deployment. Information on how to acquire these licenses, see the Fortinet Document Library article Registering and downloading your license. To activate the FortiGate NVA, you will need at least one available FortiGate license file. If you do not have the Fortinet FortiGate-VM For Azure BYOL and FortiGate NGFW - Single VM Deployment (BYOL) available in your Azure Stack Hub Marketplace, contact your cloud operator.
0 kommentar(er)
