Fortinet Document Library

Version:


Table of Contents

Azure Cookbook

Resources

Upgrade Path Tool

Azure Cookbook

6.2.0
Download PDF
Copy Link

Models

FortiGate-VM is available with different CPU and RAM sizes and can be deployed on various private and public cloud platforms. The following table shows the models conventionally available to order, also known as BYOL models. See Order types.

Model name

vCPU minimum

vCPU maximum

FG-VM01 or 01v 1 1
FG-VM02 or 02v 1 2
FG-VM04 or 04v 1 4
FG-VM08 or 08v 1 8
FG-VM16 or 16v 1 16
note icon

The v-series does not support virtual domains (VDOMs) by default. To run VDOMs on v-models, you must purchase additional VDOM licenses. You can add and stack VDOMs up to the maximum supported number after initial deployment.

Generally, there are RAM size restrictions to FortiGate-VM BYOL licenses. However, these restrictions do not apply to Azure deployments. Any RAM size with certain CPU models are allowed. Licenses are based on the number of CPUs (the number of vCPU cores for Azure) only.

Previously, platform-specific models such as FortiGate-VM for Azure with an Azure-specific orderable menu existed. However, the common model now applies to all supported platforms.

For information about each model's order information, capacity limits, and adding VDOMs, see the FortiGate-VM datasheet.

The primary requirement for the provisioning of a virtual FortiGate may be the number of interfaces it can accommodate rather than its processing capabilities. In some cloud environments, the options with a high number of interfaces tend to have high numbers of vCPUs.

The licensing for FortiGate-VM does not restrict whether the FortiGate can work on a VM instance in a public cloud that uses more vCPUs than the license allows. The number of vCPUs indicated by the license does not restrict the FortiGate-VM from working, regardless of how many vCPUs are included in the virtual instance. However, only the licensed number of vCPUs process traffic and management tasks. The rest of the vCPUs are unused.

The following shows an example for FGT-VM08:

License

1 vCPU

2 vCPU

4 vCPU

8 vCPU

16 vCPU

32 vCPU

FGT-VM08

OK

OK

OK

OK

The FortiGate-VM uses eight vCPUs used for traffic and management. It does not use the rest.

The FortiGate-VM uses eight vCPUs used for traffic and management. It does not use the rest.

You can provision a VM instance based on the number of interfaces you need and license the FortiGate-VM for only the processors you need.

Resources

Models

FortiGate-VM is available with different CPU and RAM sizes and can be deployed on various private and public cloud platforms. The following table shows the models conventionally available to order, also known as BYOL models. See Order types.

Model name

vCPU minimum

vCPU maximum

FG-VM01 or 01v 1 1
FG-VM02 or 02v 1 2
FG-VM04 or 04v 1 4
FG-VM08 or 08v 1 8
FG-VM16 or 16v 1 16
note icon

The v-series does not support virtual domains (VDOMs) by default. To run VDOMs on v-models, you must purchase additional VDOM licenses. You can add and stack VDOMs up to the maximum supported number after initial deployment.

Generally, there are RAM size restrictions to FortiGate-VM BYOL licenses. However, these restrictions do not apply to Azure deployments. Any RAM size with certain CPU models are allowed. Licenses are based on the number of CPUs (the number of vCPU cores for Azure) only.

Previously, platform-specific models such as FortiGate-VM for Azure with an Azure-specific orderable menu existed. However, the common model now applies to all supported platforms.

For information about each model's order information, capacity limits, and adding VDOMs, see the FortiGate-VM datasheet.

The primary requirement for the provisioning of a virtual FortiGate may be the number of interfaces it can accommodate rather than its processing capabilities. In some cloud environments, the options with a high number of interfaces tend to have high numbers of vCPUs.

The licensing for FortiGate-VM does not restrict whether the FortiGate can work on a VM instance in a public cloud that uses more vCPUs than the license allows. The number of vCPUs indicated by the license does not restrict the FortiGate-VM from working, regardless of how many vCPUs are included in the virtual instance. However, only the licensed number of vCPUs process traffic and management tasks. The rest of the vCPUs are unused.

The following shows an example for FGT-VM08:

License

1 vCPU

2 vCPU

4 vCPU

8 vCPU

16 vCPU

32 vCPU

FGT-VM08

OK

OK

OK

OK

The FortiGate-VM uses eight vCPUs used for traffic and management. It does not use the rest.

The FortiGate-VM uses eight vCPUs used for traffic and management. It does not use the rest.

You can provision a VM instance based on the number of interfaces you need and license the FortiGate-VM for only the processors you need.