Limitations
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
-
-
Limitations
The following are limitations
associated with the Panorama™ Interconnect plugin.
Issue ID | Description |
|---|---|
PAN-165488 Panorama Interconnect
Plugin 1.0 only | Installation of the Panorama Interconnect
Plugin 1.0 fails on a Panorama management server running PAN-OS 10.1.1
and later releases because PHP sessions used to access the Panorama
Controller and all Panorama Nodes web interfaces must store session
IDs in a separate and private directory configured with ownership
and permissions that limit only necessary users to access this information. Workaround: Upgrade the Panorama Interconnect
Plugin to plugin version 1.1 before you upgrade your Panorama
Controller and Panorama Nodes to PAN-OS 10.1.1 or later release. |
PLUG-8991 | You cannot revert (PanoramaSetupOperations) the
Panorama Interconnect configuration. To make any Panorama
Interconnect configuration changes, you must make the changes on
the Panorama Controller and synchronize the configuration with your Panorama
Nodes. |
|
PLUG-8346
|
The Panorama Controller is unable to communicate with Panorama Nodes
when Network Address Translation (NAT) connections are
configured.
|
PLUG-1565 | Synchronize Config (PanoramaInterconnectPanorama Nodes) fails on the
passive high availability (HA) peer when the Panorama Node is in
a HA configuration. Workaround: Log in to the web interface
of the active Panorama Node and synchronize the configuration to
the passive HA peer. |
PLUG-697 | In rare cases, the _interconnect user
is not created after the Panorama Interconnect plugin is successfully installed. Workaround:
Uninstall the Panorama Interconnect plugin, restart configd,
and re-install the Panorama Interconnect plugin. |
PLUG-680 | Push Common Config fails
when pushing the common configuration from the Panorama Controller
to Panorama Nodes if an SSL profile is configured using certificates created
on the Panorama Controller. Workaround: Configure a
certificate on each Panorama Node to which you are pushing a configuration
that references a certificate. |
PLUG-561 | After reverting the Panorama Controller
configuration (PanoramaSetupOperations or ConfigRevert Changes),
Panorama Nodes and firewalls added on the Panorama Controller are
not removed even after a commit force. Workaround:
After you revert the Panorama configuration, manually Delete the
Panorama Nodes (PanoramaInterconnectPanorama Nodes) and firewalls
(PanoramaInterconnectDevices). |