Plan Your Topology for SD-WAN with Auto VPN

PAN-OS & Panorama

1. 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.
2. Log in to the Panorama Web Interface.
3. (PAN-OS 9.1.2 and later versions, and SD-WAN plugin 1.0.2 and later versions) 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 you Commit, all tunnels are dropped and new tunnels are used, so perform this task during a time you have low traffic.

   1. Select PanoramaSD-WANVPN Clusters.
   2. At the bottom of the screen, select VPN Address Pool.

      

   3. Select IPv4 or IPv6 and Add an address pool with one or more (up to 20) Member IP address and netmask ranges, for example, 192.168.0.0/16 or 2001::/16, respectively.
   4. Click OK.

      

      (SD-WAN plugin 2.2.0 and later versions) 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 Panorama CN with your address pool changes:

      1. 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.
      2. Update the VPN address pool, and then do a local Commit.
      3. Perform the Panorama onboarding again, and then do a local Commit and Push.
4. Configure the VPN cluster. Repeat this step to create VPN clusters as needed.

   1. Select PanoramaSD-WANVPN Clusters and Add a VPN cluster.
   2. Enter a descriptive name for the VPN cluster.

      Underscores and spaces are not supported in the VPN cluster name and result in monitoring (PanoramaSD-WANMonitoring) 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.
   3. Select the VPN cluster Type.

      Only Hub-Spoke VPN cluster type is supported in PAN-OS 10.0.2 and earlier 11.0 versions. Beginning with PAN-OS 10.0.3, you can Create a Full Mesh VPN Cluster with DDNS Service.
   4. (SD-WAN plugin 3.2.0 and later versions) Select the Authentication type: Pre Shared Key or Certificate. 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 to Certificate for 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.
   5. (PAN-OS 11.1.8 and later 11.1 versions, SD-WAN plugin 3.2.3 and later 3.2 versions) As quantum computing technology advances, traditional encryption methods used in VPNs and other secure communications become increasingly vulnerable to attacks. In Advanced NGFW SD-WAN, we have introduced Post Quantum VPN to address this emerging threat with quantum-resistant encryption methods to protect your SD-WAN overlay.

      Post-Quantum Pre-Shared Key (PQ-PPK) is one of the key components of post-quantum VPN that enhances the security of your IPSec tunnels by adding an additional layer of quantum-resistant encryption. The SD-WAN plugin allows you to enable post-quantum VPN features for your VPN clusters and manage the associated settings. When enabled, the plugin automatically generates and manages strong PQ-PPKs for your IPSec tunnels. The SD-WAN plugin configures IKE and IPSec Crypto profiles to use quantum-safe algorithms when post-quantum VPN is enabled. The PQ PPK is enabled by default for new VPN clusters.

      Select PQ PPK to enable PQ-PPK for your SD-WAN overlay.

      

      A warning appears:

      

      Select OK to enable post-quantum VPN for the VPN cluster. The SD-WAN plugin will automatically generate 10 strong PQ-PPKs to use with the IPSec tunnels. The SD-WAN plugin will configure the IPSec tunnels to use PQ-PPK with the negotiation mode set to preferred.

      

      • PQ-PPK isn’t supported on the PA-220 firewall.
      • PQ-PPK is supported only with Pre Shared Key authentication type.
      • Existing VPN clusters won’t have post-quantum VPN configured by default. This approach ensures there is no disruption to existing IPSec connectivity. However, you have the flexibility to manually enable post-quantum VPN for an existing cluster if desired. When you do so, the IPSec tunnels won’t be immediately affected. Instead, the post-quantum capabilities will be negotiated when the keys expire or when the tunnel is renegotiated. This gradual adoption strategy allows you to implement quantum-safe encryption at your own pace, balancing security enhancements with operational stability.

      If you want to refresh the PQ-PPK list, use the Refresh PQPPK List in the VPN cluster configuration. It regenerates the new post-quantum pre-shared keys and updates the keys on all SD-WAN devices within the selected VPN cluster.

      (HA deployments only) For Panorama in HA configuration, all PQ-PPK information is synchronized between the active and passive peers, ensuring seamless failover. Similarly, for HA active/passive firewalls, the PQ-PPK list and all pre-shared keys, including post-quantum key information, are synchronized between the devices. This synchronization ensures that the PQ-PPK configuration remains consistent and operational across the HA pair, maintaining the quantum-safe encryption capabilities of your SD-WAN overlay even during failover events.
   6. Add one or more branch devices that you determined need to communicate with each other.

      • (SD-WAN plugin 1.0.1 and later versions) Select Group HA Peers to display the branch devices that are HA peers together.

        

      • Select the branch devices to add to the cluster.
      • Click OK.
   7. Add one or more hub devices that you determined need to communicate with the branch devices.

      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.

      For the SD-WAN versions earlier than 3.1.3, you can add up to four SD-WAN hub firewalls to a VPN cluster.

      (SD-WAN plugin 3.2.1 and later versions) You can add up to 16 SD-WAN hub firewalls to a VPN cluster. Only four of the 16 hubs can have the same hub priority within a VPN cluster due to ECMP. Any attempt to configure the same priority for more than four SD-WAN hubs would result in a commit error.

      • (SD-WAN plugin 1.0.1 and later versions) Select Group HA Peers to display the hub devices that are HA peers together.
      • Select the hubs to add to the cluster and click OK.

        

      • 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 for the SD-WAN versions earlier than 3.1.3. With SD-WAN plugin 3.2.1 and later versions, you can add up to 16 SD-WAN hub firewalls to a VPN cluster. 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 Priority	Local Preference
        1	250
        2	200
        3	150
        4	100

        If 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 (NetworkVirtual RoutersECMP) and ECMP Multiple AS Support is enabled for BGP (NetworkVirtual RoutersBGPAdvanced).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.
        • If you selected Group HA Peers, select the pair and click in the Hub Failover Priority field; enter a single Priority (range is 1 to 4), which applies to both hubs in the HA pair, and click OK.

          

          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 select Group HA Peers and Submit.
        • For hubs that are not HA pairs, select a hub and click in the Hub Failover Priority field; enter a priority (range is 1 to 4).

          

   8. Click OK to save the VPN cluster.
5. (PAN-OS 9.1.2 and later versions, and SD-WAN plugin 1.0.2 and later versions) 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. The Prefix(es) to Redistribute field accepts a list of prefixes, rather than just a single prefix.

   1. Select PanoramaSD-WANDevices and select a branch firewall.
   2. Select BGP and Add one or more IP addresses with netmask to Prefix(es) to Redistribute.
   3. Click OK.
6. Commit and Commit to Panorama.
7. (SD-WAN plugin 2.0.1 and later 2.0 versions) If your hub firewalls in a hub-spoke VPN cluster have DHCP or PPPoE interfaces, you must use DDNS. Select NetworkInterfacesEthernet and in the Template field, select Template-stack for a hub.
8. (SD-WAN plugin 2.0.1 and later 2.0 versions) Select the interfaces whose IP address indicates Dynamic-DHCP Client or PPPOE, click Override on the bottom of the screen, and click OK to close.
9. (SD-WAN plugin 2.0.1 and later 2.0 versions) Verify on Panorama that the DDNS settings were configured.

   1. Select NetworkInterfacesEthernet and select the same interface again.
   2. Select AdvancedDDNS.
   3. See that the DDNS settings were automatically configured with a Hostname and the Vendor set to Palo Alto Networks DDNS.
   4. Click OK.
10. (SD-WAN plugin 2.0.1 and later 2.0 versions) Commit and Commit to Panorama.
11. 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 command show interface sdwan? to see the SD-WAN interfaces.

    1. Select Commit and Push to Devices.
    2. Edit Selections on the lower left side of the screen.

       

    3. Deselect Filter Selected.
    4. Click on Deselect All.
    5. Select your hub Device Group. Select Include Device and Network Templates at 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.

       

    6. Select the Templates tab and Deselect All.
    7. The Push Scope is the Device Group. Push the configuration to the hub(s).
12. Push the configuration to the branch(es) by repeating the prior step, but selecting your branch Device Group.
13. (PAN-OS 9.1.2 and later versions, and SD-WAN plugin 1.0.2 and later versions) 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.

    1. Select PanoramaSD-WANVPN Clusters and select a cluster.
    2. At the bottom of the screen, select Refresh IKE Key.

       

    3. A message appears notifying you that Refreshing 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 | No Select Yes if you wish to continue.
    4. Commit.

       After you Refresh IKE Key, you must commit to the entire cluster; a partial commit will bring down tunnels.
    5. Push to Devices.