FortiGate SD-WAN lab 3 of 14
SD-WAN rules and steering strategies
Write four SD-WAN rules, one per strategy: manual for the admin PC, best quality for web traffic, lowest cost (SLA) for DNS and maximise bandwidth for file transfers. Then slow ISP-A down with the WAN emulator and prove which link each rule chooses, and why.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 6,144 MB in total. That fits the free demo too.
In your workspace: Shared, then FortiGate SD-WAN guided labs, then 03 - SD-WAN rules and steering strategies
- Level
- Intermediate
- Time
- About 75 minutes
- Nodes need
- 5 vCPU, 6,144 MB
- Smallest plan
- Lite
The scenario
Both of the Leeds depot's lines are now measured by INET_SLA, but every session still follows the implicit rule. The network lead has written down what each kind of traffic should do:
| Traffic | Requirement | Strategy |
|---|---|---|
| Anything from PC1 (10.2.10.10) | always ISP-A: the managed-service provider only accepts that address | manual |
| Web (TCP 80) | whichever line has the lowest latency right now | best quality |
| DNS (UDP 53) | ISP-A, the cheap line, while it meets target 1; otherwise ISP-B | lowest cost (SLA) |
| File transfers to files.example.com (198.51.100.13, TCP 80) | both lines together while they meet target 2 | maximise bandwidth (SLA) |
INET_SLA probes 198.51.100.53 every 500 ms. Target 1: latency 100 ms, jitter 50 ms, loss 5%. Target 2: latency 250 ms, jitter 100 ms, loss 10%. ISP-A costs less per gigabyte than ISP-B.
What you’ll practise
- Explain how SD-WAN rules match traffic top-down and fall back to the implicit rule
- Configure manual, best quality, lowest cost (SLA) and maximise bandwidth (SLA) rules
- Use member cost, link-cost-factor and SLA targets in rules
- Read rule decisions with diagnose sys sdwan service and the policy-route table
- Predict and prove each rule's choice when one link degrades
The tasks
- Start the lab
- How rules are matched
- Manual and best quality
- Lowest cost (SLA) and maximise bandwidth (SLA)
- Slow ISP-A down
- Watch it in the GUI (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
- BR1
port1to WANeth0 - WAN
eth1to INETeth0 - BR1
port2to INETeth1 - BR1
port3to LAN (network) - PC1
eth0to LAN (network) - H1
eth0to LAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| BR1 | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 MB |
| WAN | Alpine WAN emulator | clbalpinewanem-alpine-wanem-3-20-3 | 1 vCPU, 512 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 SD-WAN guided labs.Open
03 - SD-WAN rules and steering strategiesand 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.