Fortinet black logo

New Features

Support automatic vCPU hot-add in FortiGate-VM for S-series and FortiFlex licenses 7.2.4

Copy Link
Copy Doc ID 77966226-6996-11ec-bdf2-fa163e15d75b:44112
Download PDF

Support automatic vCPU hot-add in FortiGate-VM for S-series and FortiFlex licenses 7.2.4

FortiGate-VM supports automatic vCPU hot-add/hot-remove to the limit of the license entitlement after activating an S-series license or a FortiFlex license. This enhancement removes the requirement for the CLI command execute cpu add <number_of_new_vCPUs> to be run or a reboot to be performed when the FortiGate-VM has a lower number of vCPUs allocated than the licensed number of vCPUs.

The following example spins up a new FortiGate-VM assigned with four vCPU:

FGT-CPU-Demo # get system status

Version: FortiGate-VM64 v7.2.4,build1371,221129 (interim)

...

Serial-Number: FGVM123456

License Status: Invalid

VM Resources: 1 CPU/1 allowed, 1993 MB RAM/2048 MB allowed

Log hard disk: Available

Hostname: FGT-CPU-Demo

FGT-CPU-Demo # execute cpu show

Active CPU number: 1

Total CPU number: 4

When activating an S-series license with four vCPU seats on the FortiGate-VM, you do not need to run execute cpu add <number_of_new_vCPUs> or reboot the FortiGate-VM. The FortiGate-VM automatically consumes four vCPUs out of four vCPUs allowed:

FGT-CPU-Demo # get system status

Version: FortiGate-VM64 v7.2.4,build1371,221129 (interim)

...

Serial-Number: FGVM123456

License Status: Valid

License Expiration Date: 2023-05-05

VM Resources: 4 CPU/4 allowed, 1993 MB RAM <===before this spec, without a reboot or "exec cpu add x" manually, FGT v7.2.3 shows "VM Resources: 1 CPU/4 allowed, 2007 MB RAM"

Log hard disk: Available

Hostname: FGT-CPU-Demo

FGT-CPU-Demo # execute cpu show

Active CPU number: 4

Total CPU number: 4

Support automatic vCPU hot-add in FortiGate-VM for S-series and FortiFlex licenses 7.2.4

FortiGate-VM supports automatic vCPU hot-add/hot-remove to the limit of the license entitlement after activating an S-series license or a FortiFlex license. This enhancement removes the requirement for the CLI command execute cpu add <number_of_new_vCPUs> to be run or a reboot to be performed when the FortiGate-VM has a lower number of vCPUs allocated than the licensed number of vCPUs.

The following example spins up a new FortiGate-VM assigned with four vCPU:

FGT-CPU-Demo # get system status

Version: FortiGate-VM64 v7.2.4,build1371,221129 (interim)

...

Serial-Number: FGVM123456

License Status: Invalid

VM Resources: 1 CPU/1 allowed, 1993 MB RAM/2048 MB allowed

Log hard disk: Available

Hostname: FGT-CPU-Demo

FGT-CPU-Demo # execute cpu show

Active CPU number: 1

Total CPU number: 4

When activating an S-series license with four vCPU seats on the FortiGate-VM, you do not need to run execute cpu add <number_of_new_vCPUs> or reboot the FortiGate-VM. The FortiGate-VM automatically consumes four vCPUs out of four vCPUs allowed:

FGT-CPU-Demo # get system status

Version: FortiGate-VM64 v7.2.4,build1371,221129 (interim)

...

Serial-Number: FGVM123456

License Status: Valid

License Expiration Date: 2023-05-05

VM Resources: 4 CPU/4 allowed, 1993 MB RAM <===before this spec, without a reboot or "exec cpu add x" manually, FGT v7.2.3 shows "VM Resources: 1 CPU/4 allowed, 2007 MB RAM"

Log hard disk: Available

Hostname: FGT-CPU-Demo

FGT-CPU-Demo # execute cpu show

Active CPU number: 4

Total CPU number: 4