What’s New in VM-Series Plugin 2.1.4
Table of Contents
Expand all | Collapse all
-
-
-
-
- Features Introduced in Zero Touch Provisioning 2.0
- Known Issues in the Zero Touch Provisioning 2.0.4 Release
- Known Issues in the Zero Touch Provisioning 2.0.3 Release
- Known Issues in the Zero Touch Provisioning 2.0.2 Release
- Known Issues in the Zero Touch Provisioning 2.0.1 Release
- Known Issues in the Zero Touch Provisioning 2.0.0 Release
- Limitations
-
-
What’s New in VM-Series Plugin 2.1.4
The VM-Series plugin 2.1.4 introduces
one new enhancement—limit the number vCPUs licensed.
Set the Number of Licensed vCPUs
You can now specify the number of vCPUs that
are licensed when using Software NGFW credits instead of licensing
all the vCPUs available on your chosen compute instance. This allows
you to use a larger compute instance without consuming more Software
NGFW credits than necessary.
You can specify the number of vCPUs to be licensed using a new
bootstrap plugin op command or the VM-Series firewall CLI.
- To set the number of cores when bootstrapping a VM-Series firewall, add the following command to your init-cfg.txt file.plugin-op-commands=set-cores:<number-of-cores>For example:plugin-op-commands=set-cores:4
- To set the number of cores on a VM-Series firewall that has already been deployed, use the following CLI command.request plugins vm_series set-cores cores <number-of-cores>For example:request plugins vm_series set-cores cores 16You must reboot the VM-Series firewall for this change to take effect.
You can verify that the vCPU change has taken affect using the show plugins vm_series cores command
in the VM-Series CLI.
If you need to downgrade your VM-Series from 2.1.4 to a previous
version, you must set the number of cores back to the default value
for your VM-Series firewall. This does not occur automatically upon
downgrade.