Create a VPN Cluster
Table of Contents
Expand all | Collapse all
-
- Create a Link Tag
- Configure an SD-WAN Interface Profile
- Configure a Physical Ethernet Interface for SD-WAN
- Configure an Aggregate Ethernet Interface and Subinterfaces for SD-WAN
- Configure Layer 3 Subinterfaces for SD-WAN
- Configure a Virtual SD-WAN Interface
- Create a Default Route to the SD-WAN Interface
-
- Create a Path Quality Profile
-
- Create a SaaS Quality Profile
- Use Case: Configure SaaS Monitoring for a Branch Firewall
- Use Case: Configure a Hub Firewall Failover for SaaS Monitoring from a Branch Firewall to the Same SaaS Application Destination
- Use Case: Configure a Hub Firewall Failover for SaaS Monitoring from a Branch Firewall to a Different SaaS Application Destination
- SD-WAN Traffic Distribution Profiles
- Create a Traffic Distribution Profile
- Create an Error Correction Profile
- Configure an SD-WAN Policy Rule
- Allow Direct Internet Access Traffic Failover to MPLS Link
- Configure DIA AnyPath
- Distribute Unmatched Sessions
- Configure HA Devices for SD-WAN
- Create a VPN Cluster
- Create a Full Mesh VPN Cluster with DDNS Service
- Create a Static Route for SD-WAN
- Configure Advanced Routing for SD-WAN
Create a VPN Cluster
Create a VPN cluster to group branches and hubs that communicate with each other into
a logical group.
In your SD-WAN configuration, you must configure one or more VPN clusters to
determine which branches communicate with which hubs and creates a secure connection
between the branch and hub devices. VPN clusters are logical groupings of devices,
so consider things such as geographical location or function when logically grouping
your devices.
PAN-OS
®
supports both hub-spoke and full mesh SD-WAN VPN topologies. In a
hub-spoke topology, a centralized firewall hub at a primary office or location acts
as the gateway between branch devices. The hub-to-branch connection is a VPN tunnel.
In this configuration, traffic between branches must pass through the hub.The first time you Configure a Virtual SD-WAN Interface with direct internet access (DIA)
links for an SD-WAN hub or branch firewall, a VPN cluster called
autogen_hubs_cluster
is automatically created and
the SD-WAN firewall is automatically added to the VPN cluster. This allows the
Panorama™ management server to Monitor SD-WAN Application and Link Performance for devices that are protected by the
SD-WAN firewall and accessing resources outside of your corporate network.
Additionally, any SD-WAN firewall with DIA links that you configure in the future
are automatically added to the autogen_hubs_cluster
VPN
cluster containing all hubs and branches with DIA links to allow Panorama to monitor
application and link performance. The
autogen_hubs_cluster
is purely for monitoring
application and link health, and not to create VPN tunnels between the hubs and
branches with DIA links. If you need to connect hubs and branches with VPN tunnels,
you must create a new VPN cluster and add all the required hubs and branches to that
cluster.When you select
Pre-shared key
as an Authentication
Type
, a strong, random IKE preshared key is created for all hubs and
branches in the VPN cluster to secure the VPN tunnels, and each firewall has a
master key that encrypts the preshared key. The system secures the preshared key,
even from the administrator. You can refresh the IKE preshared key, which Panorama
sends to all members of the cluster. Refresh the preshared key when cluster members aren't
busy.
When you select
Certificate
as the Authentication
Type
, then the hubs and branches in the SD-WAN VPN cluster is based
on the certificate-based
authentication.After the SD-WAN Plugin is upgraded to 2.1.0, the hub and branch firewalls in a
single VPN cluster must all run either PAN-OS 10.0.4 (or a later 10.0 release) or
10.1.0, not a combination of the two releases.
When viewing VPN clusters, if no data is present or the screen indicates that
SD-WAN is undefined, check in the Compatibility Matrix that the Panorama
release you're using supports the SD-WAN plugin release you're trying to use.
Whether an IPv4 or IPv6 IPSec tunnel is formed between two Ethernet ports (or
subinterface or AE interface) (DIA link) depends on whether the Ethernet interface
(or subinterface or AE interface) has an IPv4 or IPv6 address. If both of the
interfaces have an IPv4 address, an IPv4 tunnel is brought up. If both of the
interfaces have an IPv6 address, an IPv6 tunnel is brought up. In the case of dual
stack, an IPv4 tunnel is brought up.
The tunnel interface IP address comes from the VPN pool. You can create an IPv6
address pool independent of an IPv4 address pool. If both IPv4 and IPv6 addresses
are configured, the tunnel interface is assigned an IPv4 address only, as shown in
the following table. If the IPv4 VPN address pool is exhausted and an IPv6 address
pool exists, the tunnel interface is assigned an IPv6 address. If only IPv4 is
configured, the tunnel will use an IPv4 address. If only IPv6 is configured, the
tunnel will use an IPv6 address.
VPN Pool | Configured | ||
---|---|---|---|
IPv4 | Yes | Yes | No |
IPv6 | Yes | No | Yes |
Tunnel Interface IP | IPv4 Only | IPv4 Only | IPv6 Only |
- Plan your branch and hub VPN topology to determine which branches communicate with each of your hubs. For more information, see Plan Your SD-WAN Configuration.
- Specify IP address ranges for the IPSec VPN tunnels that Auto VPN configuration creates.Auto VPN configuration creates a VPN tunnel between a hub and branches and assigns IP addresses to the tunnel endpoints. Enter subnet ranges that you want Auto VPN to use as VPN tunnel addresses. You can enter up to 20 IP prefix/netmask ranges. Auto VPN draws from that pool for VPN tunnel addresses, drawing from the largest range (for the address family) first, and then drawing from the next largest range when necessary. You must configure at least one range for the pool. If you don’t perform this step before pushing the configuration to a hub or branch, the Commit and Push will fail.If you upgrade from an earlier SD-WAN Plugin release, you must check that your ranges are still correct. If they aren't, enter new ranges. After youCommit, all tunnels are dropped and new tunnels are used, so perform this task during a time you have low traffic.
- Select.PanoramaSD-WANVPN Clusters
- At the bottom of the screen, selectVPN Address Pool.
- SelectIPv4orIPv6andAddan address pool with one or more (up to 20)MemberIP address and netmask ranges, for example, 192.168.0.0/16 or 2001::/16, respectively.
- ClickOK.Don't simply change an existing address pool if Prisma Access is onboarded. If you need to change an address pool, perform the following steps during a maintenance window to update the branch and the Prisma Access CN with your address pool changes:
- Use Panorama to access an SD-WAN branch and delete the existing onboarding that the address pool change will impact; then do a local Commit.
- Update the VPN address pool, and then do a local Commit.
- Perform the Prisma Access onboarding again, and then do a local Commit and Push.
- Configure the VPN cluster. Repeat this step to create VPN clusters as needed.
- SelectandPanoramaSD-WANVPN ClustersAdda VPN cluster.
- Enter a descriptive name for the VPN cluster.Underscores and spaces are not supported in the VPN cluster name and result in monitoring () data for the cluster not to be displayed. Choose the name of the VPN cluster carefully so you do not need to change the name in the future. SD-WAN monitoring data is generated based on the old cluster name and cannot be reconciled to a new cluster name, and will cause issues with the number of reported clusters when monitoring your VPN clusters or generating reports.PanoramaSD-WANMonitoring
- Select the VPN clusterType.OnlyHub-SpokeVPN cluster type is supported in PAN-OS 10.0.2 and earlier 11.0 releases. Beginning with PAN-OS 10.0.3, you can Create a Full Mesh VPN Cluster with DDNS Service.
- (SD-WAN plugin 3.2.0 and later releases) Select theAuthentication type: Pre Shared KeyorCertificate. It's mandatory to specify the authentication type to add a device in a VPN cluster. A VPN cluster should have the same authentication type selected for all its devices.When you select the authentication type for a VPN cluster, only the branches and hubs that are configured with the same authentication type (as the VPN cluster) can be added to the VPN cluster. For example, when you select certificate as authentication type for a VPN cluster, then all the hubs and branches that are added to the cluster should be configured with certificate as the authentication type.You can't modify the authentication type or VPN cluster name of a VPN cluster that has been configured already. To make a change, remove the VPN cluster and its SD-WAN devices and configure it again using the new authentication type or VPN cluster name. By default, we support the pre-shared authentication type for the devices in a VPN cluster (if the certificate method is not selected manually).
- One you've configured the VPN cluster, you cannot change the cluster name or its authentication type (both cluster and device level).
- You cannot have different authentication types within a single VPN cluster. That is, a VPN cluster authentication type must match with all the SD-WAN devices in the VPN cluster. Any difference would result in a commit failure.
- You can have different VPN clusters with different authentication types configured.
- In a VPN cluster, you cannot have SD-WAN devices with different authentication types selected. If an SD-WAN hub is part of two VPN clusters, then the two clusters should be configured with the same authentication type.
If you want to change the authentication type toCertificatefor an existing VPN cluster, delete the VPN cluster and create it again with the authentication type of your choice.After creating a VPN cluster with certificate authentication type, if you want to downgrade to a PAN-OS or SD-WAN plugin version that does not support certificate authentication type, follow these steps:- Delete the existing VPN cluster. SD-WAN device authentication will automatically change to pre-shared key on downgrade.
- Downgrade to the PAN-OS or SD-WAN plugin version of your preference. See the system requirements for SD-WAN for the minimum PAN-OS and SD-WAN plugin versions required for configuring the certificate authentication type.
Follow the steps mentioned in the Upgrade and Downgrade Considerations before you upgrade or downgrade your current SD-WAN plugin. - Addone or more branch devices that you determined need to communicate with each other.
- SelectGroup HA Peersto display the branch devices that are HA peers together.
- Select the branch devices to add to the cluster.
- ClickOK.
- Addone or more hub devices that you determined need to communicate with the branch devices.Up to four SD-WAN hub firewalls can be added to a VPN cluster. SD-WAN hubs in an HA configuration are considered as a single SD-WAN hub firewall.MPLS and satellite link types will form tunnels with only the same link type; for example, MPLS-to-MPLS and satellite-to-satellite. Tunnels will not be created between an MPLS link and an Ethernet link, for example.
- SelectGroup HA Peersto display the hub devices that are HA peers together.
- Select the hubs to add to the cluster and clickOK.
- For any new or previously existing VPN cluster that has more than one hub, you must prioritize the hubs to determine a) that traffic be sent to a particular hub, and b) the subsequent hub failover order. The hub failover priority range is 1 to 4. If you upgrade, the default priority is set to 4. The plugin internally translates the hub failover priority to a BGP local preference number as shown in the following table. The lower the priority value, the higher the priority and local preference. A cluster supports a maximum of four hubs. An active/passive HA pair counts as one hub. Multiple hubs can have the same priority; an HA pair must have the same priority. Panorama uses the branch’s BGP template to push the local preference of the hubs to the branches in the cluster.Hub Failover PriorityLocal Preference1250220031504100If multiple hubs have the same priority, Panorama enables ECMP in two places on each branch firewall to determine how branches select the path. ECMP is enabled for the virtual router () andNetworkVirtual RoutersECMPECMP Multiple AS Supportis enabled for BGP ().If all hubs in the cluster have a unique priority, ECMP is disabled on the branches. If a hub priority configuration changes, Panorama reevaluates whether to enable or disable ECMP.NetworkVirtual RoutersBGPAdvanced
- If you selectedGroup HA Peers, select the pair and click in theHub Failover Priorityfield; enter a singlePriority(range is 1 to 4), which applies to both hubs in the HA pair, and clickOK.The Hub Failover Priority for HA Peers window appears only for configured HA pairs. If you add a new HA pair, you must configure the Hub Failover Priority for each of the two new peers independently.You will get an error message if you assign different priorities to hubs that are ungrouped HA peers and then you selectGroup HA PeersandSubmit.
- For hubs that are not HA pairs, select a hub and click in theHub Failover Priorityfield; enter a priority (range is 1 to 4).
- ClickOKto save the VPN cluster.
- Advertise additional prefixes at the branch to the hub.The firewall automatically redistributes (advertises) all non-public, connected routes from the branch to the hub. You can also redistribute any additional prefixes from the branch to the hub. ThePrefix(es) to Redistributefield accepts a list of prefixes, rather than just a single prefix.
- Selectand select a branch firewall.PanoramaSD-WANDevices
- SelectBGPandAddone or more IP addresses with netmask toPrefix(es) to Redistribute.
- ClickOK.
- CommitandCommit to Panorama.
- (SD-WAN Plugin 2.0.1 and later 2.0 releases) If your hub firewalls in a hub-spoke VPN cluster have DHCP or PPPoE interfaces, you must use DDNS. Selectand in theNetworkInterfacesEthernetTemplatefield, select Template-stack for a hub.
- (SD-WAN Plugin 2.0.1 and later 2.0 releases) Select the interfaces whose IP address indicatesDynamic-DHCP ClientorPPPOE, clickOverrideon the bottom of the screen, and clickOKto close.
- (SD-WAN Plugin 2.0.1 and later 2.0 releases) Verify on Panorama that the DDNS settings were configured.
- Selectand select the same interface again.NetworkInterfacesEthernet
- Select.AdvancedDDNS
- See that the DDNS settings were automatically configured with aHostnameand theVendorset toPalo Alto Networks DDNS.
- ClickOK.
- (SD-WAN Plugin 2.0.1 and later 2.0 releases)CommitandCommit to Panorama.
- Push the configuration to the hub(s).When Panorama creates virtual SD-WAN interfaces for hubs, Panorama doesn't necessarily create the interfaces using contiguous interface numbers. It might randomly skip an interface number, for example, sdwan.921, sdwan.922, sdwan.924, sdwan.925. Despite the discontiguous numbering, Panorama creates the correct number of SD-WAN interfaces. Use the operational CLI commandshow interface sdwan?to see the SD-WAN interfaces.
- SelectCommitandPush to Devices.
- Edit Selectionson the lower left side of the screen.
- DeselectFilter Selected.
- Click onDeselect All.
- Select your hub Device Group. SelectInclude Device and Network Templatesat the bottom of the screen. You must push to hubs before pushing to branches.Most branches have dynamic IP addresses through their service providers, so branches must initiate the IKE/IPSec connection because the hub doesn’t have the branches’ IP address.To ensure that the hub is ready to receive the IKE/IPSec connections, the hub’s configuration must be committed and pushed before the branch’s configuration. Thus, when the branch configurations are pushed and the branches initiate the connection to the hub, the hub is ready.
- Select theTemplatestab andDeselect All.
- ThePush Scopeis the Device Group.Pushthe configuration to the hub(s).
- Push the configuration to the branch(es) by repeating the prior step, but selecting your branch Device Group.
- Refresh the IKE preshared key.If you need to change the current IKE key that is used to secure the IPSec connections between VPN cluster devices, perform this step to randomly generate a new key for the cluster.Perform this step when cluster members aren't busy.
- Selectand select a cluster.PanoramaSD-WANVPN Clusters
- At the bottom of the screen, selectRefresh IKE Key.
- A message appears notifying you thatRefreshing the IKE key will generate a new security association (SA) for every SD-WAN firewall in the VPN cluster. This may cause a service disruption. Do you wish to continue? Yes | NoSelectYesif you wish to continue.
- Commit.After youRefresh IKE Key, you must commit to the entire cluster; a partial commit will bring down tunnels.
- Push to Devices.