: Known Issues in VM-Series Plugin 3.0.0
Focus
Focus

Known Issues in VM-Series Plugin 3.0.0

Table of Contents

Known Issues in VM-Series Plugin 3.0.0

The following list describes known issues in the VM-Series Plugin 3.0.0.

PLUG-10392

License information is not updated when cores are changed using CLI.

PLUG-10069

When upgrading the VM-Series firewall running PAN-OS 10.1.0, 10.1.1, 10.1.2, 10.1.3, or 10.1.4 in an HA deployment, you must first upgrade the VM-Series plugin to version 2.1.5 before upgrading to PAN-OS 10.2. Additionally, the upgrade must be performed in the following order:
  1. Upgrade VM-Series plugin to 2.1.5 on the Active peer.
  2. Upgrade VM-Series plugin to 2.1.5 on the Passive peer.
  3. Upgrade PAN-OS to 10.2 on the Passive peer.
  4. Upgrade PAN-OS to 10.2 on the Active peer.

PLUG-10082

Virtual Machines with actual memory greater than 120GB will be recognized as Tier-4(T4-128GB model) firewall.

PLUG-9987

On a VM deployed in Azure environment, the validate button at
Device
VM-Series
Azure HA Configuration
Edit
displays the error
resource-mgr-endpoint is invalid
if the resource manager endpoint is not configured.

PLUG-9983

AWS PA-VM does not associate with a collector group on Panorama, if the collector group name is given as userdata on AWS, during bootstrap.

PLUG-9933

In OCI cloud, logging in to PA-VM fails if user data is missing a new line.
Fixed in VM-Series plugin 2.1.8.

PLUG-9868

In AWS FIPS-CC enabled PA-VMs, the HA failover is impaired on interface-move mode.

PLUG-9771

Performance impact(high utilization of the CPU) is observed on vmxnet3(Esxi) and ena(AWS) driver based VM-Series Firewalls due to
dpdk-rx-queue-num
set to 1 for PAYG images.

Recommended For You