FortiGate SD-WAN lab 8 of 14
ADVPN shortcuts between spokes
Stop branch-to-branch traffic hairpinning through HQ: enable ADVPN so the hub offers shortcuts and the spokes build direct IPsec tunnels on demand, then prove the shortcut with the tunnel list, the routing table and a traceroute, and see how SD-WAN treats a shortcut.
Run this lab
It needs Standard: its 8 nodes are set to 8 vCPU and 9,216 MB in total.
In your workspace: Shared, then FortiGate SD-WAN guided labs, then 08 - ADVPN shortcuts between spokes
- Level
- Advanced
- Time
- About 75 minutes
- Nodes need
- 8 vCPU, 9,216 MB
- Smallest plan
- Standard
The scenario
Leeds and Bristol now share a warehouse system and phone each other all day. Every packet between them crosses HQ: up one overlay to the hub, back down another, twice the delay and twice the load on HQ's lines. You'll enable ADVPN (Auto-Discovery VPN), so the depots build direct tunnels to each other when they need them and drop back to the hub when they don't.
| Device | ISP-A | ISP-B | LAN | Tunnel addresses (A / B) |
|---|---|---|---|---|
| HUB | 203.0.113.1 | 192.0.2.1 | 10.1.10.0/24 | 172.16.1.254 / 172.16.2.254 |
| BR1 | 203.0.113.2 | 192.0.2.2 | 10.2.10.0/24, H2 .50 | 172.16.1.2 / 172.16.2.2 |
| BR2 | 203.0.113.3 | 192.0.2.3 | 10.3.10.0/24, H3 .50 | 172.16.1.3 / 172.16.2.3 |
Evaluation licence. IPsec on these FortiGates offers DES only, so the overlays and shortcuts use
des-sha256with DH group 14. Production uses AES-256-GCM with DH group 19, 20 or 21.
What you’ll practise
- Explain ADVPN: shortcut offers, on-demand spoke-to-spoke tunnels and why BGP must keep the spoke's next hop
- Enable auto-discovery-sender on the hub and auto-discovery-receiver on the spokes
- Trigger a shortcut and identify it in the tunnel list and the routing table
- Prove the direct path with traceroute
- Relate shortcuts to SD-WAN members, health checks and rules
The tasks
- Start the lab
- The hairpin
- Enable ADVPN
- Build a shortcut
- Shortcuts and SD-WAN
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- HUB
port1to ISP-A (network) - HUB
port2to ISP-B (network) - HUB
port3to H1eth0 - BR1
port1to WANeth0 - WAN
eth1to ISP-A (network) - BR1
port2to ISP-B (network) - BR1
port3to H2eth0 - BR2
port1to ISP-A (network) - BR2
port2to ISP-B (network) - BR2
port3to H3eth0 - INET
eth0to ISP-A (network) - INET
eth1to ISP-B (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| HUB | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 MB |
| BR1 | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 MB |
| BR2 | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 MB |
| INET | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| WAN | Alpine WAN emulator | clbalpinewanem-alpine-wanem-3-20-3 | 1 vCPU, 512 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| H2 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| H3 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
FortiGate SD-WAN guided labs.Open
08 - ADVPN shortcuts between spokesand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More FortiGate SD-WAN labs
Related labs in other courses
CloudLabBox is independent of Fortinet. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.