Addressed Issues in VM-Series Plugin 2.0.2
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
-
-
Addressed Issues in VM-Series Plugin 2.0.2
The following list describes addressed
issues in VM-Series plugin 2.0.2.
PLUG-6280
Monitoring VM-Series firewalls using
AWS CloudWatch fails if you are using a VPC endpoint to communicate
with the VM-Series firewall management port.
This issue is addressed in VM-Series plugin version 2.0.2,
and it introduces a change in default behavior. Prior versions used
HTTP for communication to the Cloudwatch endpoint. In version 2.0.2
and later VM-Series plugin uses HTTPS to communicate with the Cloudwatch
endpoint.
PLUG-6196
Upgrading PanOS to 10.0.1 with VM-Series
plugin 2.0.1, VM-Series plugin fails to boot the system in AWS MP
BYOL images.
This issue is addressed in VM-Series plugin version 2.0.2.
Workaround:
Upgrade the VM-Series plugin to version 2.0.2 before upgrading
PAN-OS to 10.0.1.
PLUG-6015
In some VM-Series firewall HA deployments
on Azure, if the active management server makes a connection request
to Azure that does not resolve, you might see the UI freeze, delayed
commits, or synchronization loss in an HA pair.
This issue is addressed in VM-Series plugin version 1.0.13
and later, and version 2.0.2 and later.