FortiGate SD-WAN lab 14 of 14
Capstone - a three-site SD-WAN rollout
Build a complete SD-WAN for HQ and two depots from addressed but empty FortiGates: underlay members with health checks and direct internet access, dial-up overlays on both ISPs, iBGP with the hub as route reflector, ADVPN shortcuts, and rules for corporate and web traffic. Then cut Leeds' main ISP and prove that everything keeps working.
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 14 - Capstone - a three-site SD-WAN rollout
- Level
- Advanced
- Time
- About 150 minutes
- Nodes need
- 8 vCPU, 9,216 MB
- Smallest plan
- Standard
The scenario
Kestrel Logistics has bought new FortiGates for HQ and the Leeds and Bristol depots. They arrive addressed (interfaces, DHCP for the LAN hosts and the address objects LAN-NET and CORP-NETS) and nothing else: no SD-WAN, no routes, no policies, no tunnels. You are the engineer for the go-live. Build the network to the design below, then prove it survives losing Leeds' main ISP.
Addressing
| Device | ISP-A (port1) | ISP-B (port2) | LAN (port3) | Tunnel addresses A / B | Router ID |
|---|---|---|---|---|---|
| HUB | 203.0.113.1 | 192.0.2.1 | 10.1.10.1/24, H1 .50 | 172.16.1.254 / 172.16.2.254 | 10.200.0.1 (loopback Lo) |
| BR1 | 203.0.113.2 (through WAN) | 192.0.2.2 | 10.2.10.1/24, H2 .50 | 172.16.1.2 / 172.16.2.2 | 10.200.0.2 |
| BR2 | 203.0.113.3 | 192.0.2.3 | 10.3.10.1/24, H3 .50 | 172.16.1.3 / 172.16.2.3 | 10.200.0.3 |
Design
| Area | Requirement |
|---|---|
| Underlay | every site: members 1 (port1, gateway 203.0.113.254) and 2 (port2, gateway 192.0.2.254) in zone underlay; health check INET_SLA (ping 198.51.100.53, 500 ms, failtime 3, recoverytime 3, target 1: 100 ms, 50 ms, 5%); default route to underlay; policy LAN-to-Internet with NAT |
| Overlays | hub dial-up OL_A (port1) and OL_B (port2), net-device disable, exchange-interface-ip enable, ADVPN sender; spokes HUB_A and HUB_B with ADVPN receiver; IKEv2, PSK LabVpnKey1!, des-sha256, DH 14, DPD on idle every 5 s |
| Spoke SD-WAN | members 3 (HUB_A) and 4 (HUB_B) in zone overlay; health check HUB_HC to 10.200.0.1 (same timers and target as INET_SLA); summary route 10.0.0.0/8 to zone overlay (distance 250) above a blackhole for 10.0.0.0/8 (distance 254) |
| Routing | iBGP AS 65000; HUB is route reflector with neighbor ranges for both overlays and advertises 10.1.10.0/24 and 10.200.0.1/32; spokes peer with both hub addresses, use ibgp-multipath and advertise their LAN; the hub sends additional paths (additional-path send, adv-additional-path 2) and the spokes receive them (additional-path receive); keepalive 5 s and hold time 15 s on every overlay session |
| Rules (spokes) | 1 Corporate: lowest cost, CORP-NETS, HUB_HC target 1, members 3, 4. 2 Web-Best-Quality: best quality on latency with INET_SLA, TCP 80, members 1, 2 |
| Policies | spokes: LAN to overlay and back for CORP-NETS, no NAT; hub: spokes to HQ, HQ to spokes, spoke to spoke, and PING from the tunnels to Lo |
Evaluation licence. IPsec on these FortiGates offers DES only, so this design uses
des-sha256with DH group 14. A production design would use AES-256-GCM with DH group 19, 20 or 21.
What you’ll practise
- Plan and build underlay SD-WAN with health checks and direct internet access on three sites
- Build dial-up overlays on two ISPs with ADVPN
- Run iBGP over the overlays with the hub as route reflector
- Write rules for corporate and internet traffic
- Prove failover of internet, corporate and spoke-to-spoke traffic when an ISP fails
The tasks
- Start the lab
- Underlay and direct internet access
- Overlays with ADVPN
- BGP
- Rules
- Go-live test: lose Leeds' ISP-A
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
14 - Capstone - a three-site SD-WAN rolloutand 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.