SD-WAN Features
Table of Contents
Expand All
|
Collapse All
Next-Generation Firewall Docs
-
PAN-OS 11.1 & Later
- PAN-OS 11.1 & Later
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.0 (EoL)
- PAN-OS 9.1 (EoL)
- Cloud Management of NGFWs
-
- Management Interfaces
-
- Launch the Web Interface
- Use the Administrator Login Activity Indicators to Detect Account Misuse
- Manage and Monitor Administrative Tasks
- Commit, Validate, and Preview Firewall Configuration Changes
- Commit Selective Configuration Changes
- Export Configuration Table Data
- Use Global Find to Search the Firewall or Panorama Management Server
- Manage Locks for Restricting Configuration Changes
-
-
- Define Access to the Web Interface Tabs
- Provide Granular Access to the Monitor Tab
- Provide Granular Access to the Policy Tab
- Provide Granular Access to the Objects Tab
- Provide Granular Access to the Network Tab
- Provide Granular Access to the Device Tab
- Define User Privacy Settings in the Admin Role Profile
- Restrict Administrator Access to Commit and Validate Functions
- Provide Granular Access to Global Settings
- Provide Granular Access to the Panorama Tab
- Provide Granular Access to Operations Settings
- Panorama Web Interface Access Privileges
-
- Reset the Firewall to Factory Default Settings
-
- Plan Your Authentication Deployment
- Pre-Logon for SAML Authentication
- Configure SAML Authentication
- Configure Kerberos Single Sign-On
- Configure Kerberos Server Authentication
- Configure TACACS+ Authentication
- Configure TACACS Accounting
- Configure RADIUS Authentication
- Configure LDAP Authentication
- Configure Local Database Authentication
- Configure an Authentication Profile and Sequence
- Test Authentication Server Connectivity
- Troubleshoot Authentication Issues
-
- Keys and Certificates
- Default Trusted Certificate Authorities (CAs)
- Certificate Deployment
- Configure the Master Key
- Export a Certificate and Private Key
- Configure a Certificate Profile
- Configure an SSL/TLS Service Profile
- Configure an SSH Service Profile
- Replace the Certificate for Inbound Management Traffic
- Configure the Key Size for SSL Forward Proxy Server Certificates
-
- HA Overview
-
- Prerequisites for Active/Active HA
- Configure Active/Active HA
-
- Use Case: Configure Active/Active HA with Route-Based Redundancy
- Use Case: Configure Active/Active HA with Floating IP Addresses
- Use Case: Configure Active/Active HA with ARP Load-Sharing
- Use Case: Configure Active/Active HA with Floating IP Address Bound to Active-Primary Firewall
- Use Case: Configure Active/Active HA with Source DIPP NAT Using Floating IP Addresses
- Use Case: Configure Separate Source NAT IP Address Pools for Active/Active HA Firewalls
- Use Case: Configure Active/Active HA for ARP Load-Sharing with Destination NAT
- Use Case: Configure Active/Active HA for ARP Load-Sharing with Destination NAT in Layer 3
- HA Clustering Overview
- HA Clustering Best Practices and Provisioning
- Configure HA Clustering
- Refresh HA1 SSH Keys and Configure Key Options
- HA Firewall States
- Reference: HA Synchronization
-
- Use the Dashboard
- Monitor Applications and Threats
- Monitor Block List
-
- Report Types
- View Reports
- Configure the Expiration Period and Run Time for Reports
- Disable Predefined Reports
- Custom Reports
- Generate Custom Reports
- Generate the SaaS Application Usage Report
- Manage PDF Summary Reports
- Generate User/Group Activity Reports
- Manage Report Groups
- Schedule Reports for Email Delivery
- Manage Report Storage Capacity
- View Policy Rule Usage
- Use External Services for Monitoring
- Configure Log Forwarding
- Configure Email Alerts
-
- Configure Syslog Monitoring
-
- Traffic Log Fields
- Threat Log Fields
- URL Filtering Log Fields
- Data Filtering Log Fields
- HIP Match Log Fields
- GlobalProtect Log Fields
- IP-Tag Log Fields
- User-ID Log Fields
- Decryption Log Fields
- Tunnel Inspection Log Fields
- SCTP Log Fields
- Authentication Log Fields
- Config Log Fields
- System Log Fields
- Correlated Events Log Fields
- GTP Log Fields
- Audit Log Fields
- Syslog Severity
- Custom Log/Event Format
- Escape Sequences
- Forward Logs to an HTTP/S Destination
- Firewall Interface Identifiers in SNMP Managers and NetFlow Collectors
- Monitor Transceivers
-
- User-ID Overview
- Enable User-ID
- Map Users to Groups
- Enable User- and Group-Based Policy
- Enable Policy for Users with Multiple Accounts
- Verify the User-ID Configuration
-
- App-ID Overview
- App-ID and HTTP/2 Inspection
- Manage Custom or Unknown Applications
- Safely Enable Applications on Default Ports
- Applications with Implicit Support
-
- Prepare to Deploy App-ID Cloud Engine
- Enable or Disable the App-ID Cloud Engine
- App-ID Cloud Engine Processing and Policy Usage
- New App Viewer (Policy Optimizer)
- Add Apps to an Application Filter with Policy Optimizer
- Add Apps to an Application Group with Policy Optimizer
- Add Apps Directly to a Rule with Policy Optimizer
- Replace an RMA Firewall (ACE)
- Impact of License Expiration or Disabling ACE
- Commit Failure Due to Cloud Content Rollback
- Troubleshoot App-ID Cloud Engine
- Application Level Gateways
- Disable the SIP Application-level Gateway (ALG)
- Maintain Custom Timeouts for Data Center Applications
-
- Policy Types
- Policy Objects
- Track Rules Within a Rulebase
- Enforce Policy Rule Description, Tag, and Audit Comment
- Move or Clone a Policy Rule or Object to a Different Virtual System
-
- External Dynamic List
- Built-in External Dynamic Lists
- Configure the Firewall to Access an External Dynamic List
- Retrieve an External Dynamic List from the Web Server
- View External Dynamic List Entries
- Exclude Entries from an External Dynamic List
- Enforce Policy on an External Dynamic List
- Find External Dynamic Lists That Failed Authentication
- Disable Authentication for an External Dynamic List
- Register IP Addresses and Tags Dynamically
- Use Dynamic User Groups in Policy
- Use Auto-Tagging to Automate Security Actions
- CLI Commands for Dynamic IP Addresses and Tags
- Application Override Policy
- Test Policy Rules
-
- Network Segmentation Using Zones
- How Do Zones Protect the Network?
-
PAN-OS 11.1 & Later
- PAN-OS 11.1 & Later
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure a PPPoE Client on a Subinterface
- Configure an IPv6 PPPoE Client
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DHCP Overview
- Firewall as a DHCP Server and Client
- Firewall as a DHCPv6 Client
- DHCP Messages
- Dynamic IPv6 Addressing on the Management Interface
- Configure an Interface as a DHCP Server
- Configure an Interface as a DHCPv4 Client
- Configure an Interface as a DHCPv6 Client with Prefix Delegation
- Configure the Management Interface as a DHCP Client
- Configure the Management Interface for Dynamic IPv6 Address Assignment
- Configure an Interface as a DHCP Relay Agent
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Create a Source NAT Rule with Persistent DIPP
- PAN-OS
- Strata Cloud Manager
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
-
- Enable Advanced Routing
- Logical Router Overview
- Configure a Logical Router
- Create a Static Route
- Configure BGP on an Advanced Routing Engine
- Create BGP Routing Profiles
- Create Filters for the Advanced Routing Engine
- Configure OSPFv2 on an Advanced Routing Engine
- Create OSPF Routing Profiles
- Configure OSPFv3 on an Advanced Routing Engine
- Create OSPFv3 Routing Profiles
- Configure RIPv2 on an Advanced Routing Engine
- Create RIPv2 Routing Profiles
- Create BFD Profiles
- Configure IPv4 Multicast
- Configure MSDP
- Create Multicast Routing Profiles
- Create an IPv4 MRoute
-
-
PAN-OS 11.1
- PAN-OS 11.2
- PAN-OS 11.1
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.0 (EoL)
- PAN-OS 9.1 (EoL)
- PAN-OS 9.0 (EoL)
- PAN-OS 8.1 (EoL)
- Cloud Management and AIOps for NGFW
-
- Networking Features
- Decryption Features
- Certificate Management Features
- Management Features
- Panorama Features
- Mobile Infrastructure Security Features
- SD-WAN Features
- Zone Protection Features
- GlobalProtect Features
- IoT Security Features
- Virtualization Features
- Authentication Features
- Advanced WildFire Features
- Hardware Features
-
- PAN-OS 11.1.2 Known Issues
- PAN-OS 11.1.2-h18 Addressed Issues
- PAN-OS 11.1.2-h16 Addressed Issues
- PAN-OS 11.1.2-h15 Addressed Issues
- PAN-OS 11.1.2-h14 Addressed Issues
- PAN-OS 11.1.2-h12 Addressed Issues
- PAN-OS 11.1.2-h9 Addressed Issues
- PAN-OS 11.1.2-h4 Addressed Issues
- PAN-OS 11.1.2-h3 Addressed Issues
- PAN-OS 11.1.2-h1 Addressed Issues
- PAN-OS 11.1.2 Addressed Issues
SD-WAN Features
What new SD-WAN features are in PAN-OS 11.1?
Monitor Bandwidth on SD-WAN Devices
May 2024
October 2024
|
Currently it's difficult for the network administrators to quickly identify
the cause for an application’s poor performance in an SD-WAN device. It's because
there isn't enough information available to identify the issue and the available
limited information (such as VPN statistics, Panorama's device health statistics,
and link health statistics) are located between Panorama and firewalls. It becomes a
time consuming activity for the administrators to correlate this information and
locate the performance issues on an SD-WAN device.
We’ve introduced bandwidth which is a primary
measure of a link performance in addition to existing
jitter, latency, and
packet loss performance measures. For a VPN cluster, you
will now be able to view the bandwidth of a tunnel and a physical interface for a
selected site by default. There is no configuration required from the user to view
the bandwidth of a tunnel.
Additional Private Link Types Support on SD-WAN Device
April 2024
May 2024
|
You can now configure additional point-to-point private link
types, Private Link1, Private
Link2, Private Link3, and Private
Link4 along with the existing private link types
(MPLS, Satellite,
Microwave/Radio) for one to one connectivity while
configuring the SD-WAN Interface Profile.
These private link types enable you to avail reliable providers for your remote
regions to establish one to one connection with the overlay network and avoid
provider outages.
Additional SD-WAN Hubs in VPN Cluster
April 2024
May 2024
|
The number of hubs to configure in a VPN cluster has been
increased from 4 to 16. Only four of the 16 hubs can have the same hub priority
within a VPN cluster due to ECMP.
Multiple Virtual Routers Support on SD-WAN Hubs
February 2024
May 2024
|
With earlier SD-WAN plugin versions, you can't have SD-WAN configurations on multiple
virtual routers. By default, a sdwan-default virtual router is created and it
enables Panorama to automatically push the router configurations. Due to this
restriction, customers faces difficulty and spends additional effort in some of the
SD-WAN deployments:
User Scenario (in SD-WAN Deployments) | Single Virtual Router Configuration on SD-WAN Hub | Multiple Virtual Routers Configuration on SD-WAN Hub |
---|---|---|
Overlapping IP addresses from different branches connecting to the same hub | Customers may need to reconfigure the overlapping subnets to unique address spaces. |
Enable Multi-VR Support on the
SD-WAN hub device.
The traffic from different branches is directed to
different virtual routers on a single hub to keep the traffic
separate.
|
Government regulations that disallow different entities to function on the same virtual router | Customers won’t be able to separate routing of different entities with a single virtual router. | Enable Multi-VR Support on the SD-WAN hub
device to keep the traffic of different entities separate.
Multiple virtual routers on the SD-WAN hub maps the branches
to different virtual routers on the hub that provides logical
separation between the branches. |
SD-WAN plugin now supports multiple virtual routers on the SD-WAN
hubs that enable you to have overlapping IP subnet addresses on branch
devices connecting to the same SD-WAN hub. Multiple virtual routers can run multiple
instances of routing protocols with a neighboring router with overlapping address
spaces configured on different virtual router instances. Multiple virtual router
deployments provide the flexibility to maintain multiple virtual routers, which are
segregated for each virtual router instance.
However, the number of virtual routers supported on the PAN-OS SD-WAN hub
varies by platform.
Benefits:
- A hub with multiple virtual router configuration logically separates the routing for each branch office that it is connected with.
- Branches sharing the same SD-WAN hub can reuse the same IP subnet address.
The following figure illustrates an SD-WAN hub with two virtual routers. By enabling
multiple virtual routers support on the SD-WAN hub, the four branches
connecting to the same SD-WAN hub (but different virtual routers) can have
overlapping IP subnets or belong to different entities and function independently
because their traffic goes to different virtual routers.

IKEv2 Certificate Authentication Support for Stronger Authentication
November 2023
|
The SD-WAN plugin now supports the certificate authentication type in addition to the
default pre-shared key type for user environments that have strong security
requirements. We support the IKEv2 certificate authentication type on
all SD-WAN supported hardware and software devices.
You can configure certificate-based authentication for the following topologies,
provided that you have configured all SD-WAN devices in the topology with the same
(or certificate) authentication type:
- VPN clusters (hub-and-spoke and mesh)
- PAN-OS firewalls connecting to Prisma Access compute nodes
Generate certificates for the SD-WAN
device using your own certificate authority (CA). Add and deploy the generated
certificates in bulk across your SD-WAN cluster and autogenerate the SD-WAN overlay
using the certificate-based authentication.
Public Cloud SD-WAN High Availability (HA)
November 2023
|
You can now reduce complexity and increase resiliency by adding high availability to
your SD-WAN for next-generation firewall public cloud deployments. Configure up to
four IP addresses per SD-WAN
interface, allowing you to deploy SD-WAN on public clouds to achieve failover in
high availability active/passive configurations. Minimize the downtime and ensure
session survivability using the active/passive HA failover in public cloud SD-WAN
environments.
Currently, you can avail this feature on deployments using VM-Series in Azure and AWS
public cloud HA environments by configuring a second floating IP address on the
SD-WAN interfaces. The floating IP on the SD-WAN interface of the external zone must
match with that of the internal zone. In the illustration, observe that 10.0.2.100
is the common floating IP between the external and internal zones during a HA
failover.

This feature is supported on PAN-OS 11.1.0 and above and on IPv4 addresses
only.
The following illustration is an example of VM-Series deployment in Azure HA
A/P topology and shows how the secondary floating IP address is from
the same subnet and applied to both trust and untrust zones of the SD-WAN
interface.

In AWS instances, you can configure HA A/P failover using
multiple ways, one of which is using a second IP address that acts as the floating
IP.

SD-WAN IPv6 Support
November 2023
|
SD-WAN supports IPv6 interfaces, beginning with SD-WAN plugin 3.2. You have the
flexibility to onboard branch locations in a hybrid IPv4/IPv6 environment or a full
IPv6 environment. SD-WAN IPv6 support uses intelligent application path steering
technology to provide application reliability and SLAs for IPv6 environments. SD-WAN
IPv6 support includes the following changes:
- You can configure a physical Ethernet interface to have a static IPv6 address.
- You can configure a static IPv6 route.
- The Advanced Routing Engine allows you to configure IPv6 BGP routing.
- SD-WAN provides health monitoring for the next hop from SD-WAN-enabled IPv6 interfaces and health monitoring for a VPN tunnel endpoint.
- Path monitoring now allows you to use addresses from an IP4 VPN address pool or an IPv6 VPN address pool.
- When an SD-WAN interface is enabled for IPv6, Auto VPN configuration creates a DIA interface named sdwan.9016, which has IPv6 physical interfaces as member interfaces. The default IPv6 route points to the sdwan.9016 interface. The user interface allows you to specify whether the virtual interface is a DIA IPv4 interface, DIA IPv6 interface, or tunnel interface (which can have a mix of IPv4 tunnel interfaces and IPv6 tunnel interfaces). An Ethernet interface can belong to both the sdwan.901 virtual interface and the sdwan.9016 virtual interface.
SD-WAN supports dual stack in the event that one ISP provides you with only an IPv4
address and another ISP provides you with only an IPv6 address. You will create
separate virtual SD-WAN interfaces. An IPv4 DIA virtual interface will have Ethernet
with an IPv4 address, while an IPv6 DIA virtual interface will have Ethernet with an
IPv6 address.
If a DIA link between a branch and a hub has only IPv6 addresses on the interfaces at
each end, the tunnel is created using IPv6 addresses. If the branch and hub have
IPv4 addresses on the interfaces, the tunnel is created using IPv4 addresses. If the
branch and hub use both IPv4 and IPv6 addresses on the interfaces, the tunnel is
created using IPv4 addresses only (IPv4 addresses are preferred). If there is a
mismatch of address family identifiers (AFI) between the hub and branch, no tunnel
configuration is generated for that pair of interfaces.
Similarly, a VPN address pool can have both IPv4 and IPv6 addresses configured, in
which case IPv4 addresses are preferred for the tunnel interface and tunnel
monitoring. If the IPv4 addresses in the VPN address pool are exhausted, then IPv6
addresses are used for the tunnel interface and tunnel monitoring.
You can also have independent IPv4 VPN address pools that contain IPv4 addresses and
IPv6 VPN address pools that contain IPv6 addresses.