Fortinet Document Library

Version:


Table of Contents

VMware ESXi Cookbook

Resources

Upgrade Path Tool
6.2.0
Download PDF
Copy Link

FortiGate-VM virtual licenses and resources

The primary requirement for the provisioning of a FortiGate-VM 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 that the license indicates does not restrict the FortiGate 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.

License

1 vCPU

2 vCPU

4 vCPU

8 vCPU

16 vCPU

32 vCPU

FGT-VM08

OK

OK

OK

OK

8 vCPUs used for traffic and management. The rest are not used.

8 vCPUs used for traffic and management. The rest are not used.

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.

Public compared to private clouds

The behavior differs between private and public clouds:

  • Private clouds (ESXi/KVM/Xen/Hyper-V): Both licensed vCPUs and RAM are affected.
  • Public clouds (AWS/Azure/GCP/OCI/Aliyun): Only licensed vCPU is affected.

For example, you can activate FG-VM02 on a FGT-VM with 4vCPUs with 16 GB of RAM, running on a private VM platform. Only 2 vCPU and 4 GB of RAM, as licensed, is consumable.

Likewise, you can activate FG-VM02 on a FGT-VM c5.2xlarge EC2 instance with 8 vCPUs running on AWS. Only 2 vCPU is consumable, and there is no limit on the RAM size. Licenses for public clouds are also referred to as bring your own license.

Resources

FortiGate-VM virtual licenses and resources

The primary requirement for the provisioning of a FortiGate-VM 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 that the license indicates does not restrict the FortiGate 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.

License

1 vCPU

2 vCPU

4 vCPU

8 vCPU

16 vCPU

32 vCPU

FGT-VM08

OK

OK

OK

OK

8 vCPUs used for traffic and management. The rest are not used.

8 vCPUs used for traffic and management. The rest are not used.

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.

Public compared to private clouds

The behavior differs between private and public clouds:

  • Private clouds (ESXi/KVM/Xen/Hyper-V): Both licensed vCPUs and RAM are affected.
  • Public clouds (AWS/Azure/GCP/OCI/Aliyun): Only licensed vCPU is affected.

For example, you can activate FG-VM02 on a FGT-VM with 4vCPUs with 16 GB of RAM, running on a private VM platform. Only 2 vCPU and 4 GB of RAM, as licensed, is consumable.

Likewise, you can activate FG-VM02 on a FGT-VM c5.2xlarge EC2 instance with 8 vCPUs running on AWS. Only 2 vCPU is consumable, and there is no limit on the RAM size. Licenses for public clouds are also referred to as bring your own license.