Hub SD-WAN Templates

To configure the Hub SD-WAN Template interactively:

1. Follow step 1 from Edge SD-WAN Templates to create a new template.

   image

2. Follow step 2 from Edge SD-WAN Templates to create the two SD-WAN Zones "underlay" and "overlay".

3. Follow step 3 from Edge SD-WAN Templates to create SD-WAN Members.

   On the Hubs, the members of the "overlay" zone will be the Dial-Up tunnel interfaces. Refer to the Generated objects and naming conventions section.

4. Optionally, follow step 4 from Edge SD-WAN Templates to set installation targets for some of the Members, in order to be able to use this SD-WAN Template for different types of Hubs. The following screenshot demonstrates a generic “Hub-SDWAN” template which can be used for both regions in our example project.

   

5. Create the necessary Performance SLAs:

   • On the Hubs, the main reason for configuring Performance SLA for the corporate (internal) traffic is to support Hub-to-Edge SD-WAN. As mentioned in the previous section, the Spokes will normally embed the measured health into the probes, signaling this information to the Hubs. The following screenshot illustrates a Performance SLA configured on the Hub to process this information:

     

   • If the Hub has multiple Internet access options (such as multiple ISPs), it is possible to control the steering using SD-WAN Rules, similar to the Spokes. You can follow the guidelines summarized in step 5 from the previous section, in order to configure the required Performance SLA for this.

   • Additionally, it may be beneficial to monitor generic Internet connectivity from the Hubs (e.g. using DNS probes towards 8.8.8.8), if only for the visibility purposes. In this case, it is enough to configure the corresponding Performance SLAs, without any SD-WAN Rules.

6. It is not necessary to activate ADVPN 2.0 on the Hub.

7. It is generally not necessary to configure any SD-WAN Rules on the Hub. The Hub will rely on the conventional routing, including the Hub-to-Edge SD-WAN support, as explained in the respective section of the SD-WAN / SD-Branch Architecture for MSSPs guide.

   However, there are special cases that may require SD-WAN Rules on the Hubs. The most straightforward example is the Internet Access for the workloads behind the Hub itself, when the Hub has multiple Internet access options (multiple ISPs). In this case, it is possible to control the steering using SD-WAN Rules, similar to the Spokes.