Known Issues in VM-Series Plugin 2.1.12
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.1.12
The following list describes known issues in the VM-Series Plugin 2.1.12.
PLUG-12368
On the VM-Series for NSX-T, jumbo frame packets larger than 1500 are dropped by the
VM-Series when DPDK is enabled.
Workaround: Restart the link state on each interface on the VM-Series firewall. To
do this, change the Link State setting on the
Advanced tab of the interface configuration and perform a
commit. Then return the to the Advanced tab of the interface
configuration and set the Link State back to the previous setting
and perform a commit.
PLUG-10392
License information is not updated when
cores are changed using CLI.
PAN-196146
The VM-Series firewall on Azure does
not boot up with a hostname (specified in an init-cgf.txt or user
data) when bootstrapped.
PLUG-10720
Device registration fails in 10.1.X devices
where init-cfg is configured as DNS.
PLUG-10722
In some intermittent cases, it is observed
that the dp-cores are not reset to default, when the dp-core value
is set to 0.