Fortinet Document Library

Version:


Table of Contents

FortiGate-VM on Microsoft Hyper-V

Resources

Upgrade Path Tool
  • Select version:
  • 6.0
6.0.0
Download PDF
Copy Link

FortiGate-VM virtual licenses and resources

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.

FortiOS 6.0.1 and earlier

Previously, if you needed a virtual instance with a high number of interfaces you needed to purchase a FortiGate-VM license for a high number of vCPUs regardless of whether you needed the processing power. If you attempt to install FortiGate-VM, licensed for a specific number of vCPUs on a public cloud instance that is configured with more vCPUs than the FortiGate is licensed for, the instance will not run.

Example for FortiOS 6.0.1 and earlier
License 1 vCPU 2 vCPU 4 vCPU 8 vCPU 16 vCPU 32 vCPU
FGT-VM08 OK OK OK OK Will not run Will not run

FortiOS 6.0.2 and later

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 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.

Example for FortiOS 6.0.2 and later
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 effected
  • Public clouds (AWS/Azure/GCP/OCI/Aliyun): Only licensed vCPU is effected

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

Likewise, you can activate FG-VM02 on a FGT-VM c5.2xlarge EC2 instance with 8vCPUs running on AWS. Only 2vCPU will be consumable, and there is no limit on the RAM size. Licenses for public clouds are also referred to as Bring Your Own License (BYOL).

Resources

FortiGate-VM virtual licenses and resources

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.

FortiOS 6.0.1 and earlier

Previously, if you needed a virtual instance with a high number of interfaces you needed to purchase a FortiGate-VM license for a high number of vCPUs regardless of whether you needed the processing power. If you attempt to install FortiGate-VM, licensed for a specific number of vCPUs on a public cloud instance that is configured with more vCPUs than the FortiGate is licensed for, the instance will not run.

Example for FortiOS 6.0.1 and earlier
License 1 vCPU 2 vCPU 4 vCPU 8 vCPU 16 vCPU 32 vCPU
FGT-VM08 OK OK OK OK Will not run Will not run

FortiOS 6.0.2 and later

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 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.

Example for FortiOS 6.0.2 and later
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 effected
  • Public clouds (AWS/Azure/GCP/OCI/Aliyun): Only licensed vCPU is effected

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

Likewise, you can activate FG-VM02 on a FGT-VM c5.2xlarge EC2 instance with 8vCPUs running on AWS. Only 2vCPU will be consumable, and there is no limit on the RAM size. Licenses for public clouds are also referred to as Bring Your Own License (BYOL).