Known Issues in VM-Series Plugin 1.0.9
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 1.0.9
The following list describes known issues in the VM-Series
Plugin 1.0.9.
PLUG-4501
On Azure, Active/Passive HA configurations
that use a floating IP address sometimes experience loss of traffic
after failover.
Upon failover, Azure starts moving the floating
IP address from the primary to the secondary. If the HA pair is
restored and control returns to the primary before the IP address
moves to the secondary, traffic is lost.
Workaround:
To restore traffic, you must temporarily suspend
the primary so that the secondary (which has the floating IP address)
is active.
This issue is fixed in VM-Series plugin version 1.0.12.
PLUG-4394
On Azure, Active/Passive HA configurations
that use a floating IP address sometimes experience loss of traffic
after failover.
Upon failover, Azure starts moving the floating
IP address from the primary to the secondary. If the HA pair is
restored and control returns to the primary before the IP address
moves to the secondary, traffic is lost.
Workaround:
To restore traffic, you must temporarily suspend
the primary so that the secondary (which has the floating IP address)
is active.
This issue is fixed in VM-Series plugin version 1.0.12.
PLUG-3509
HA behavior is inconsistent for VM-Series
firewalls deployed on Azure.
This issue is fixed in VM-Series plugin version 1.0.12.
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.
PLUG-3650
HA behavior is inconsistent for VM-Series
firewalls deployed on Azure.
This issue is fixed in VM-Series plugin version 1.0.12.
PLUG-3643
On Azure and GCP, the VM-Series firewall
boots in maintenance mode when jumbo packet mode is enabled. This
issue occurred if you deploy the VM-100 on an instance with 8CPUs/16GB
of memory or greater or the VM-300 on an instance with 16CPUs/56GB
of memory or greater.
This issue is fixed in VM-Series plugin 1.0.11
PLUG-3743
The VM-Series plugin cannot collect Google
Stackdriver metrics for the VM-Series firewall on GCP.
This issue is fixed in VM-Series plugin 1.0.11 With
this fix, the VM-Series firewall can publish PAN-OS metrics to Google
Stackdriver.
PLUG-3721
On VM-Series firewalls deployed using
a flexible Pay-As-You-Go (PAYG) license, the Dashboard and
under DeviceLicenses in
the web interface or using request license info in
the CLI displays the capacity license as VM-300 regardless of the
capacity license applied.
Workaround: Execute the command show system info to
verify the capacity license applied to your VM-Series firewall.