fortinet/azure-templates

Disable VNET selection based on address range when deploying FortGate

suwonbuffalo opened this issue · 5 comments

suwonbuffalo commented

Hi.
I was trying to install FortiGate at Azure marketplace and found something strange.

If the VNET address space is prefix25-32, VNET selection is disabled.
And prefix28-32 doesn't appear on the selection list either.
Please refer to the picture.
image
image

I want to use VNET address range as prefix26.

Please let me know why VNET selection is disabled.
Also, I wonder if it is Azure or Fortinet restrictions.

I look forward to hearing from you.
Have a nice day

jvhoof commented

Hi,

Thank you for contacting Fortinet. We have reviewed your report and it seems the minimum values are a little too strict. We will be working on getting these changed. For now, can you try with the templates on the GitHub repo below which already have the changes applied. Select the deployment you would like and use the 'Deploy to Azure' button next to the Azure Portal Wizard text.

https://github.com/40net-cloud/fortinet-azure-solutions/tree/main/FortiGate

Hope this helps you in your deployment.

Kind regards,

Joeri

suwonbuffalo commented

Hi, Joeri

Thank you for your quick reply.

I deployed Fortgate using the modified template.
The creation of a new VNET seems to remove the address space (prefix25 to 32).
However, previously created VNETs are still not available.
image

I look forward to hearing from you about this.
Have a nice day :)

jvhoof commented

Hi,

One limitation I hadn't removed was the size of the subnet. It has now been lowered to the smalest size possible for the deployment. Can you retry again in the below repo?

https://github.com/40net-cloud/fortinet-azure-solutions/tree/main/FortiGate

Regards,

Joeri

suwonbuffalo commented

Hi, Joeri

Thank you for applying the revised VNET form

Thank you.

  • 👍1
jvhoof commented

Closing the issue now. We will publish this on the repo here as well this week.