Known Issues in Panorama Plugin for Azure 3.2.1
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 Panorama Plugin for Azure 3.2.1
The following list describes known issues
in the Panorama plugin for Azure 3.2.1.
PLUG-10437
After a successful VM-Series firewall
deployment in PAN-OS 10.0.9 and above, and Azure Plugin 3.2.0; it
is observed that the deployment status displays as Warning,
even though the firewalls are successfully connected to the Panorama.
PLUG-10774
Orchestration deployment might fail in
unsupported regions such as canadaeast, as the migration to workspace
based appinsights instance is not yet implemented.
PLUG-10792
While using CIDR notations below /22
in Azure deployments, ensure that the vNet address space does not
overlap with any other vNet in the same organization.
Workaround: It is recommended to use CIDR notations below
/16, although /22 is allowed.
Fixed in Panorama plugin for Azure 3.2.1.
PLUG-10896
In Azure 3.2.1 deployments where a vNet
is connected to vWAN, an InvalidAuthenticationTokenTenant error
is observed in the deployment logs. However, no change in functionality
is observed.
PLUG-10972
Following an upgrade of Azure plugin
from 3.2.0 to 3.2.1, an exception related to MS connection is observed
in the monitoring logs.