When I try both "Deploy to Azure" options it's giving following error:

There was an error downloading the template from URI 'https://raw.githubusercontent.com/40net-cloud/fortinet-azure-solutions/fwb-an-license/FortiWeb/Active-Active/mainTemplate.json'. Ensure that the template is publicly accessible and that the publisher has enabled CORS policy on the endpoint. To deploy this template, download the template manually and paste the contents in the 'Build your own template in the editor' option below.
There was an error downloading from URI 'https://raw.githubusercontent.com/40net-cloud/fortinet-azure-solutions/fwb-an-license/FortiWeb/Active-Active/createUiDefinition.json'. Ensure that the template is publicly accessible and that the publisher has enabled CORS policy on the endpoint.

I noticed that during the creation of the Route Server peers (pointing to the fortigates) .69 and .70 are the peers created however shouldn't this be the internal IPs of the two fortigates which are .68 and .69?

Thank you!

Hi Joeri,

The last configuration steps (udr rewrite and cluster ip failover) are not needed if you use the internal loadbalancer that your script deploys, am i correct?

Some of theses sku are available for Availability Zone such as : 'Standard_F4s_v2' but it is not supported

Deployment template validation failed: 'The provided value 'Standard_F4s_v2' for the template parameter 'instanceType' at line '71' and column '24' is not valid. The parameter value is not part of the allowed value(s):
'Standard_F4s,Standard_F8s,Standard_F16s,Standard_F4,Standard_F8,Standard_F16,Standard_F8s_v2,Standard_F16s_v2,Standard_F32s_v2,Standard_DS3_v2,Standard_DS4_v2,Standard_DS5_v2,Standard_D8s_v3,Standard_D16s_v3,Standard_D32s_v3'.'. (Code: InvalidTemplate)

I've found an issue in the VNET peering template that breaks the deployment script. The script defines the template parameter "fortiGateNamePrefix" but the ARM template is expecting "fortigateNamePrefix". Simply changing the case of the letter "g" fixes this.

Enter location (e.g. eastus2): australiasoutheast

--> Deployment in 'australiasoutheast' location ...

Enter prefix: lojmelb

--> Using prefix 'lojmelb' for all resources ...

Enter username: loj

--> Using username 'loj' ...

Enter password:
--> Creating lojmelb-RG resource group ...
{
"id": "/subscriptions/75de9f41-d4c2-4597-bbe3-c69fe62f9528/resourceGroups/lojmelb-RG",
"location": "australiasoutheast",
"managedBy": null,
"name": "lojmelb-RG",
"properties": {
"provisioningState": "Succeeded"
},
"tags": null,
"type": "Microsoft.Resources/resourceGroups"
}
--> Validation deployment in lojmelb-RG resource group ...
unrecognized template parameter 'fortiGateNamePrefix'. Allowed parameters: acceleratedNetworking, adminPassword, adminUsername, fortigateImageSKU, fortigateImageVersion, fortigateNamePrefix, fortinetTags, instanceType, location, publicIP2Name, publicIP2NewOrExisting, publicIP2ResourceGroup, publicIP3Name, publicIP3NewOrExisting, publicIP3ResourceGroup, publicIPName, publicIPNewOrExisting, publicIPResourceGroup, subnet1Name, subnet1Prefix, subnet1Spoke1Name, subnet1Spoke1Prefix, subnet1Spoke2Name, subnet1Spoke2Prefix, subnet2Name, subnet2Prefix, subnet3Name,subnet3Prefix, subnet4Name, subnet4Prefix, subnet5Name, subnet5Prefix, subnet6Name, subnet6Prefix, vnetAddressPrefix, vnetAddressPrefixSpoke1, vnetAddressPrefixSpoke2, vnetName, vnetNameSpoke1, vnetNameSpoke2, vnetNewOrExisting, vnetNewOrExistingSpoke1, vnetNewOrExistingSpoke2, vnetResourceGroup, vnetResourceGroupSpoke1, vnetResourceGroupSpoke2
--> Validation failed ...

Happy to simply open a pull request?

I deployed FortiGate to Azure from the site below.

FortiGate Next-Generation Firewall in Azure GWLB
https://github.com/fortinetsolutions/Azure-Templates/tree/master/GWLB

When deploying, if I select "fortinet_fg-vm_payg_20190624" for the "Forti Gate Image SKU", I can access the FortiGate site,
but if I select "fortinet_fg-vm", I will not be able to access the FortiGate site.

How can BYOD use FortiGate?

Have to change it to "fortigate_vwan_nva" to make it work.
the default vaule is "'fortinet-sdwan-and-ngfw' or 'fortinet-ngfw'. but it does not work.

fortinet-azure-solutions/FortiGate/AzureVirtualWAN/terraform/varible.tf

variable "fgt_sku" {
default = "fortigate_vwan_nva"
}

since 7.2.1
"config system cluster-sync" is moved to "config system standalone-cluster"

Love what you have done with these templates, so easy to deploy and with different scenarios. We want to use AvailabilityZones/Active-Active-ELB-ILB-AZ and it works well, but now we also want to do Vnet peering, and its a bit confusing to select the FortiGate/VNET-Peering/ as that is only Active-Passive?

Any guidance would be appreciated.

Dear team,

When creating a project running in /fortinet-azure-solutions-main/fortinet-azure-solutions-main/FortiGate/Terraform/VNET-Peering

The Fortinet VM cannot be created, please help on this issue

Error:
azurerm_virtual_machine.fgtbvm: Still creating... [7m30s elapsed]

Error: compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: Code="InternalServerError" Message="Encountered internal server error. Diagnostic information: timestamp '20210602T051811Z', subscription id '53621724-10de-4a6b-85f0-f8a78d823588', tracking id '57856138-c373-4334-bd03-24c6bd663f12', request correlation id 'b2e706f0-2ac2-8f0a-2df2-392889e18a7f'."

on 03-fortigate.tf line 280, in resource "azurerm_virtual_machine" "fgtavm":
280: resource "azurerm_virtual_machine" "fgtavm" {

Error: compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: Code="InternalServerError" Message="Encountered internal server error. Diagnostic information: timestamp '20210602T051811Z', subscription id '53621724-10de-4a6b-85f0-f8a78d823588', tracking id '92df99ce-568f-400e-9d8a-30e566d56a48', request correlation id 'b2e706f0-2ac2-8f0a-2df2-392889e18a7f'."

on 03-fortigate.tf line 465, in resource "azurerm_virtual_machine" "fgtbvm":
465: resource "azurerm_virtual_machine" "fgtbvm" {

[root@shaoboopsbmwcentos7 VNET-Peering]#

Hi,
I have successfully deployed the HA (Active/Passive) and connected over SSH and verified all the configurations.
Then, i connected over GUI and applied the licenses on both the Firewall.
Once done, i couldnt reach the firewalls either via GUI and SSH.
Then, i managed to login via Cluster IP (active node) thro SSH and noticed that, all the configuration of the active node were reseted to factory defaults with WAN interface on DHCP.

Kindly, could you please shed some light on what went wrong.
Thanks
Hameed

Hi there!

I've tried to deploy this solution on an Azure test Subscription using Azure Cloud Shell and if throws an error while attempting to create NIC4 for both vms.

Deployment failed. Correlation ID: 29dddaf0-66ca-4b9e-aad0-c2f1fb7edcb3. {
"error": {
"code": "InvalidRequestFormat",
"message": "Cannot parse the request.",
"details": [
{
"code": "MissingJsonReferenceId",
"message": "Value for reference id is missing. Path properties.ipConfigurations[0].properties.publicIPAddress."
}
]
}
}

Same error occurs while trying to create using the ARM template directly on Azure Portal.

error.txt

Hi Joeri,
Thanks for your support.

I tried to deploy the below and got this error.

https://github.com/jvhoof/fortinet-azure-solutions/tree/master/FortiGate/Active-Passive-SDN

Only change i made is, added the "Standard_DS3v2: under Parameter -> Instance Type (See the image attached).

I have received the below error.

{"telemetryId":"737e0034-5fb3-4e93-b392-46f339cec370","bladeInstanceId":"Blade_b3f4104aaf8249bb8565dd6dae0c3091_0_0","galleryItemId":"Microsoft.Template","createBlade":"DeployToAzure","code":"MultipleErrorsOccurred","message":"Multiple error occurred: BadRequest,BadRequest. Please see details.","details":[{"code":"InvalidTemplateDeployment","message":"The template deployment failed with error: 'The resource with id: '/subscriptions/efbc14f0-5afe-4e56-92db-6b2fe58a43a4/resourceGroups/RGRP_AZ_LCL_USNC_CORE/providers/Microsoft.Compute/virtualMachines/fw_az_lcl_usnc_prod-FGT-A' failed validation with message: 'The requested size for resource '/subscriptions/efbc14f0-5afe-4e56-92db-6b2fe58a43a4/resourceGroups/RGRP_AZ_LCL_USNC_CORE/providers/Microsoft.Compute/virtualMachines/fw_az_lcl_usnc_prod-FGT-A' is currently not available in location 'northcentralus' zones '' for subscription 'efbc14f0-5afe-4e56-92db-6b2fe58a43a4'. Please try another size or deploy to a different location or zones. See https://aka.ms/azureskunotavailable for details.'.'."},{"code":"InvalidTemplateDeployment","message":"The template deployment failed with error: 'The resource with id: '/subscriptions/efbc14f0-5afe-4e56-92db-6b2fe58a43a4/resourceGroups/RGRP_AZ_LCL_USNC_CORE/providers/Microsoft.Compute/virtualMachines/fw_az_lcl_usnc_prod-FGT-B' failed validation with message: 'The requested size for resource '/subscriptions/efbc14f0-5afe-4e56-92db-6b2fe58a43a4/resourceGroups/RGRP_AZ_LCL_USNC_CORE/providers/Microsoft.Compute/virtualMachines/fw_az_lcl_usnc_prod-FGT-B' is currently not available in location 'northcentralus' zones '' for subscription 'efbc14f0-5afe-4e56-92db-6b2fe58a43a4'. Please try another size or deploy to a different location or zones. See https://aka.ms/azureskunotavailable for details.'.'."}]}