Models
FortiGate-VM is available with different CPU and RAM sizes and you can deploy it on various private and public cloud platforms. The following table shows the models conventionally available to order, also known as bring your own license models. See Order types.
|
Model name |
vCPU minimum |
vCPU maximum |
|---|---|---|
|
FG-VM01/01v/01s |
1 | 1 |
|
FG-VM02/02v/02s |
1 | 2 |
|
FG-VM04/04v/04s |
1 | 4 |
|
FG-VM08/08v/08s |
1 | 8 |
|
FG-VM16/16v/16s |
1 | 16 |
|
FG-VM32/32v/32s |
1 | 32 |
|
FG-VMUL/ULv/ULs |
1 | Unlimited |
|
With the changes in the FortiGuard extended IPS database introduced in FortiOS 7.4.0, some workloads that depend on the extended IPS database must have the underlying VM resized to 8 vCPU or more to continue using the extended IPS database. See Support full extended IPS database for FortiGate VMs with eight cores or more. For information about changing the instance type on an existing VM, see Change the size of a virtual machine. For more information about the VM series, see Virtual Machine series. |
|
|
The v-series and s-series do not support virtual domains (VDOMs) by default. To add VDOMs, you must separately purchase perpetual VDOM addition 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. Azure allows any RAM size with certain CPU models. 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 provisioning a virtual FortiGate may be the number of interfaces it can accommodate rather than its processing capabilities. In some cloud environments, 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 that the license indicates does not restrict the FortiGate-VM from working, regardless of how many vCPUs the virtual instance includes. However, only the licensed number of vCPUs process traffic and management tasks. The FortiGate-VM does not use the rest of the vCPUs.
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.