Known Issues in the Panorama Plugin for Azure 5.2.3
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 the Panorama Plugin for Azure 5.2.3
Known issues in the Panorama Plugin for Azure 5.2.3.
The following list describes known issues in the Panorama plugin for Azure 5.2.3:
PLUG-21927
In a High Availability (HA) configuration where the Secondary Panorama is
active, the Panorama IP dropdown in the Cloud Device Group parameters incorrectly
displays the Public IP of the Secondary Panorama. This results in a mismatch where the
displayed Public IP belongs to the Secondary peer, while the displayed Private IP
belongs to the Primary peer.
PLUG-21908
The Azure plugin 5.2.3 becomes unresponsive if you create a new Cloud Device
Group (DG) that references a Template Stack already in use by another Cloud DG. This
configuration causes the commit handler to stall, preventing subsequent operations even
though the plugin daemon remains running.