Known Issues in SD-WAN Plugin 2.1
Table of Contents
Expand all | Collapse all
-
-
-
-
-
- Features Introduced in Enterprise Data Loss Prevention 4.0.3
- Known Issues in Enterprise DLP Plugin 4.0.3
- Features Introduced in Enterprise Data Loss Prevention 4.0.2
- Known Issues in Enterprise DLP Plugin 4.0.2
- Features Introduced in Enterprise Data Loss Prevention 4.0.1
- Known Issues in Enterprise DLP Plugin 4.0.1
- Features Introduced in Enterprise Data Loss Prevention 4.0.0
- Known Issues in Enterprise DLP Plugin 4.0.0
-
- Features Introduced in Enterprise Data Loss Prevention 3.0.8
- Features Introduced in Enterprise Data Loss Prevention 3.0.7
- Features Introduced in Enterprise Data Loss Prevention 3.0.6
- Features Introduced in Enterprise Data Loss Prevention 3.0.5
- Features Introduced in Enterprise Data Loss Prevention 3.0.4
- Features Introduced in Enterprise Data Loss Prevention 3.0.3
- Features Introduced in Enterprise Data Loss Prevention 3.0.2
- Features Introduced in Enterprise Data Loss Prevention 3.0.1
- Features Introduced in Enterprise Data Loss Prevention 3.0.0
- Known Issues in Enterprise Data Loss Prevention 3.0.8
- Known Issues in Enterprise Data Loss Prevention 3.0.7
- Known Issues in Enterprise Data Loss Prevention 3.0.6
- Known Issues in Enterprise Data Loss Prevention 3.0.5
- Known Issues in Enterprise Data Loss Prevention 3.0.4
- Known Issues in Enterprise Data Loss Prevention (DLP) Plugin 3.0.3
- Known Issues in Enterprise Data Loss Prevention (DLP) Plugin 3.0.0
-
- Features Introduced in Enterprise Data Loss Prevention 1.0.8
- Features Introduced in Enterprise Data Loss Prevention 1.0.3
- Features Introduced in Enterprise Data Loss Prevention 1.0.1
- Known Issues in Enterprise Data Loss Prevention (DLP) Plugin 1.0.8
- Known Issues in Enterprise Data Loss Prevention (DLP) Plugin 1.0.7
- Known Issues in Enterprise Data Loss Prevention (DLP) Plugin 1.0.6
- Known Issues in Enterprise Data Loss Prevention (DLP) Plugin 1.0.4
- Known Issues in Enterprise Data Loss Prevention (DLP) Plugin 1.0.3
- Known Issues in Enterprise Data Loss Prevention (DLP) Plugin 1.0.2
- Known Issues in Enterprise Data Loss Prevention (DLP) Plugin 1.0.1
- Features Introduced in the Enterprise Data Loss Prevention (DLP) Cloud Service
- Limitations
-
-
Known Issues in SD-WAN Plugin 2.1
List of known issues in SD-WAN 2.1 release.
The following list includes all known
issues that impact an SD-WAN 2.1 release. This list includes both
outstanding issues and issues that are addressed, as well as known issues
that apply more generally or that are not identified by a specific
issue ID. Refer to PAN-OS Release Notes for
additional known issues affecting SD-WAN Plugin 2.1.
PAN-220919
Description of PAN-220919.
Auto VPN creates a virtual SD-WAN interface named sdwan.901 for direct internet access
(DIA) and creates a virtual SD-WAN interface named sdwan.9xx for VPN tunnels. When you
enable Auto VPN, the SD-WAN plugin creates the SD-WAN interfaces automatically. Hence,
it's not necessary for you to create SD-WAN interfaces manually. The SaaS quality
profile works only with one DIA interface that is sdwan.901.
Auto VPN also creates its own default route that uses the sdwan.901 interface as its
egress interface and uses a low metric of 5, so that the sdwan.901 interface is
preferred over the default route you created.
There might be scenarios where you want to create an SD-WAN interface manually (other
than what the SD-WAN plugin creates automatically) like the following:
- Configuring SD-WAN direct internet access (DIA) links only and no VPN connections between the hub and branch locations
- (Not recommended) Deploying SD-WAN manually between SD-WAN sites without Panorama management server
In such cases, you must configure the manually created SD-WAN interface outside of the
SDWAN.9xx range containing a route with a metric higher than the default value.
PAN-215897
Description of PAN-215897.
In a Panorama high availability (HA) deployment, the SD-WAN interface goes down and all
the tunnel interfaces disappear from the tab when you push the configuration changes from the secondary
Panorama.
Network
IPSec Tunnels
Workaround
: If you have set up a HA pair in Panorama, don't push the configuration
from the secondary Panorama when the primary Panorama is active. Always push the
configuration changes from the primary Panorama when it's active.PAN-190173
Pre-shared keys are not synchronized across the Panorama
management servers in a high availability (HA) configuration, leading
to tunnel flaps during an HA failover when you or ).
Push to
Devices
(Commit
Push to Devices
Commit
Commit and Push
This issue is addressed in SD-WAN plugin 2.2.3 and 3.1.0-h6.
PAN-158465
On the Panorama management server running
PAN-OS 10.0.3 or later PAN-OS 10.0 release, reverting or loading
a Panorama configuration ()
that impacts the template stack configuration containing the SD-WAN interface
() erroneously removes
the Security Zone from the SD-WAN interface configuration resulting
in a commit failure.
Panorama
Setup
Operations
Network
Interfaces
SD-WAN
PLUG-11223
Description of PLUG-11223.
In a high availability (HA) deployment, the SD-WAN tunnel will go down due to a key ID
mismatch when the following events occur in sequence:
- An HA failover
- The SD-WAN plugin cache removes the current HA pair relation from the database whendebug plugins sd_wan drop-config-cache allcommand is executed
- A commit and push fails on either the hub or a branch active node
In certain scenarios, replacing one of the HA devices during the RMA process can cause
the SD-WAN tunnel to go down due to a key ID mismatch. For more details, refer to Replace an SD-WAN Device.
Workaround
: Resolve the Key ID mismatch by ensuring that the Peer
Identification
of the hub firewall matches with the Local
Identification
of the branch firewall and the Local
Identification
of the hub firewall matches with the Peer
Identification
of the branch firewall.- Log in to the hub or a branch firewall where the SD-WAN tunnel is down due to Key ID mismatch and select.NetworkNetwork ProfilesIKE Gateways
- Select the IKE gateway of the hub firewall and clickOverrideat the bottom of the screen.
- Copy theLocal Identificationvalue from the hub firewall to thePeer Identificationvalue in the branch firewall.
- Copy thePeer Identificationvalue from the hub firewall to theLocal Identificationvalue in the branch firewall.
- ClickOKandCommityour changes.
This issue is addressed in SD-WAN plugin 2.2.5
,
3.1.3
.PLUG-10796
On the Panorama management server, a
commit () hangs at 99% and causes the
commit queue to fill up, preventing any subsequent commits on Panorama.
Commit
Commit
to Panorama
This issue is addressed in SD-WAN plugin 2.2.2 and 3.0.2.
PLUG-10165
On the Panorama management server, commits
()
fail if your SD-WAN firewalls associated with the SD-WAN plugin ()
configuration are removed from Panorama management ().
Commit
Commit to Panorama
Panorama
SD-WAN
Panorama
Managed Devices
Summary
Workaround:
Remove the SD-WAN configuration after you
remove your SD-WAN firewalls from Panorama management. - Selectand search forPanoramaPluginssd_wan.
- Remove Config.
- ClickOKto confirm removing the SD-WAN configuration from Panorama.
This is addressed in SD-WAN plugin 2.2.2 and 3.0.2.
PLUG-10047
This issue is resolved in SD-WAN version 2.1.2.
You cannot add a branch firewall configured with an MPLS, Satellite,
or Microwave/Radio interface () to a VPN Cluster () if the hub firewall or any branch
firewall in the VPN Cluster are not also configured with at least
one MPLS, Satellite, or Microwave/Radio interface.
Network
Network Profiles
SD-WAN Interface
Profile
Panorama
SD-WAN
VPN
Clusters
For example, you cannot add a branch firewall configured with
MPLS and Wifi interfaces to a VPN Cluster where the firewall members
do not have at least one MPLS interface configured.
PLUG-9421
The Panorama plugin for SD-WAN is unable to recognize
when the master key ()
is updated on the Panorama management server.
Panorama
Master Key and Diagnostics
Workaround:
Select Commit
and Commit
and Push
to your managed firewalls leveraging SD-WAN
after updating the master key on Panorama.This issue is addressed in PAN-OS 10.2.1-h1 and SD-WAN plugin
2.2.1.
PLUG-7598
This is resolved in SD-WAN version 2.1.1.
A SD-WAN Interface Profile () configured with
a
Network
SD-WAN Interface Profile
Microwave/Radio Link
or Other
Type of Link
as the Link Type do not function as a Peer-to-Peer
link.PLUG-3343
The SD-WAN plugin fails to display any
of the monitoring for a site and cluster with a space in the name.
Workaround:
Remove the space from the name and Commit
.PAN-123040
When you try to view network QoS statistics on an SD-WAN
branch or hub, the QoS statistics and the hit count for the QoS
rules don’t display. A workaround exists for this issue. Please
contact Support for information about the workaround.