Creating Hub SD-WAN templates
For the consistent configuration, we also recommend enabling SD-WAN on the Hubs. When creating SD-WAN templates for the Hub, follow general steps 1-3 that are described in Creating Edge SD-WAN templates.
This includes creating the two SD-WAN zones named underlay and overlay.
|
On the Hubs, the members of the overlay zone will be the dial-up tunnel interfaces. |
The image below demonstrates a template named Hub-Gold from our example project, and the template is prepared for Hub devices that serve the West Region (such as site1-H1):
Regarding the steps 4-5 (Performance SLAs and SD-WAN Rules) from Creating Edge SD-WAN templates, the following guidelines apply:
- Generally, configuring Performance SLAs and/or SD-WAN Rules on the Hubs is not mandatory. Quite often the Hub can provide Internet access using conventional routing, both for the workloads behind the Hub itself and for the Remote Internet Access from the Edges.
- For Edge-to-Edge traffic and ADVPN exchanges, no SD-WAN configuration is necessary on the Hubs. The Edge devices make the steering decisions for this traffic. The Hubs implement the "overlay stickiness" principle, preferring to stay within the overlay chosen by the originating Edge. This principle is implemented using Policy Routes, generated by our Jinja CLI templates.
- However, if the Hub has multiple Internet access options (such as multiple ISPs), it is also possible to control the steering using SD-WAN Rules, similar to the Edges.
- Additionally, it may be beneficial to monitor generic Internet connectivity from the Hubs (for example, using DNS probes towards 8.8.8.8), if only for visibility. In this case, it is enough to configure the corresponding Performance SLAs, without any SD-WAN Rules.
- Finally, there are special cases that require SD-WAN Rules on the Hubs, such as controlling Hub-to-Edge traffic.
Once the SD-WAN Templates are ready, assign them to the correct device groups. The following image demonstrates the assignment in our example project:
