Known Issues in Panorama Interconnect Plugin 1.0.2

The following list describes known issues in the Panorama Interconnect plugin 1.0.2.

PLUG-1565

Synchronize Config
(
Panorama
Interconnect
Panorama 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-1138

The Panorama Interconnect information (
Panorama
Interconnect
) loads slowly when managing a large set of Panorama Nodes and devices.

PLUG-1137

You are unable to search for Devices by Name when using the search field (
Panorama
Interconnect
Devices
).

PLUG-1101

On the Panorama Controller, you cannot group Panorama Nodes (
Panorama
Interconnect
Panorama Nodes
Group HA Peers
) in a high availability (HA) configuration if they are configured with an IPv6 IP address.

PLUG-1100

Multiple duplicate Panorama Node plugin upgrade and synchronization jobs are seen in the Tasks page (
Panorama
Interconnect
Tasks
) on the Panorama Controller when upgrading or synchronizing Panorama Nodes at scale.

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-670

Tasks (
Panorama
Interconnect
Tasks
) are not displayed in chronological order when the Panorama Controller and Panorama Nodes are in different time zones.

PLUG-602

Refreshing or navigating to a different tab in the Panorama web interface deselects Panorama Nodes (
Panorama
Interconnect
Panorama Nodes
) and firewalls (
Panorama
Interconnect
Devices
).

PLUG-561

After reverting the Panorama Controller configuration (
Panorama
Setup
Operations
or
Config
Revert 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 (
Panorama
Interconnect
Panorama Nodes
) and firewalls (
Panorama
Interconnect
Devices
).

PLUG-557

When the Panorama Controller is in an HA configuration, the passive HA peer does not get updated with the Panorama Node PAN-OS and Interconnect plugin versions, and which results in a
not in sync
status.

Recommended For You