FortiGate lab 20 of 25
SD-WAN: members, SLAs and rules
Build SD-WAN from scratch over two ISPs: members in a zone, one route and one policy, a performance SLA that measures each link, and rules that pin the admin PC, send web traffic to the best link and keep DNS on the cheap link while it meets its SLA. Then degrade ISP-A and watch traffic move.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 5,632 MB in total. That fits the free demo too.
In your workspace: Shared, then FortiGate NSE 4 guided labs, then 20 - SD-WAN - members SLAs and rules
- Level
- Advanced
- Time
- About 75 minutes
- Nodes need
- 4 vCPU, 5,632 MB
- Smallest plan
- Lite
The scenario
Harbourside's two ISPs are both cabled and addressed, but FGT1 has no routes and no policies yet: nothing leaves the office. Instead of the routing tricks from labs 08 and 09, the network lead wants SD-WAN: measure both links all the time, keep the admin PC on ISP-A (the managed-service provider allow-lists it), send web traffic over whichever link is performing best, and keep DNS on ISP-A, the cheaper link, as long as it meets its SLA.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| FGT1 | port1 (ISP-A) | 203.0.113.1/24 | ISP-A gateway 203.0.113.254 (INET eth0) |
| FGT1 | port3 (ISP-B) | 192.0.2.1/24 | ISP-B gateway 192.0.2.254 (INET eth1) |
| FGT1 | port2 (LAN) | 10.1.10.1/24 | PC1 10.1.10.10, H1 by DHCP |
| INET | lo | 198.51.100.0/24 | public DNS .53 (the SLA target), www.example.com .10 |
SLA targets: latency under 100 ms, jitter under 50 ms, packet loss under 5%.
What you’ll practise
- Explain SD-WAN members, zones, performance SLAs and rules, and the implicit rule
- Add interfaces to SD-WAN with gateways, a static route to the zone and a policy
- Measure link quality with a performance SLA and read it in the CLI and GUI
- Write manual, best-quality and lowest-cost (SLA) rules
- Degrade a link and prove which link each rule chooses
The tasks
- Start the lab
- SD-WAN building blocks
- Members, route and policy
- A performance SLA
- Rules for each kind of traffic
- Degrade ISP-A and watch the rules react
- Recover (optional)
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
- FGT1
port1to INETeth0 - FGT1
port3to INETeth1 - FGT1
port2to LAN (network) - PC1
eth0to LAN (network) - H1
eth0to LAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| FGT1 | 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 |
| PC1 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 2,048 MB |
| H1 | 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 NSE 4 guided labs.Open
20 - SD-WAN - members SLAs and rulesand 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 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.