SD-WAN Features
Table of Contents
SD-WAN Features
What new SD-WAN features are in PAN-OS 11.1?
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.