Review the known issues in the VM-Series Plugin 2.1.4.
The following list describes known issues in the VM-Series
Plugin 2.1.4.
PLUG-9667
If you set the number of dataplane cores
higher than the number of cores supported by the VM-Series firewall,
and you then increase the total number of cores and set the cores,
the number of dataplane cores return to the default ratio (3 dataplane
to 1 management plane) after reboot.
Workaround
: After setting the number cores and rebooting
the firewall, you must reset the number of dataplane cores.
PLUG-9638
When setting the number of cores using
the init-cfg.txt file for bootstrapping along with authcodes, the
VM-Series firewall does not get the serial number and displays incorrect vm-license
although the firewall comes up with required amount of cores.
Workaround
: Do not include both an authcode and the set
cores op command in an init-cfg.txt file. Instead, bootstrap with
an authcode and manually set the cores using the CLI or set the
cores in the init-cfg.txt file and apply the authcode manually.
PLUG-4179
When you bootstrap the VM-Series firewall with
dhcp-accept-server-hostname=yes
in
the
init-cfg.txt
file, then subsequently update
the hostname for the VM-Series firewall, the hostname does not update
in the
<namespace>_dimension
CloudWatch
metrics.
Workaround:
To change the hostname after boot up, use
one of the following methods to prevent the firewall from accepting
the hostname sent by the DHCP server:
CLI command:
dhcp-accept-server-hostname=no
init-cfg.txt
file: Remove
dhcp-accept-server-hostname=yes
,
or set
dhcp-accept-server-hostname=no
.
PLUG-3562
In OCI, if you assign secondary IP addresses
to HA interfaces, those IP addresses are incorrectly moved to the
passive HA peer in the event of a failover.
