Known Issues in VM-Series Plugin 2.0.5
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
-
-
Known Issues in VM-Series Plugin 2.0.5
The following list describes known issues in the VM-Series
plugin 2.0.5.
PLUG-8043
Performance impact or high CPU utilization might be
seen on VMXNET3 (ESXi) and AWS Elastic Network Adapter (ENA) driver-based
VM-Series firewalls when dpdk-rx-queue-num is
set to 1 and the model type is VM-300, VM-500, or VM-700.
This issue is addressed in VM-Series plugin version 2.0.7.
Workaround: Use VM-Series plugin 2.0.4.
PLUG-7756
Bootstrapping a VM 700 with 7 data NICs on Azure results
in an all_task crash error.
This issue is fixed in VM-Series plugin version 2.0.6.
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.