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

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

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.

DeviceInterfaceAddressConnects to
FGT1port1 (ISP-A)203.0.113.1/24ISP-A gateway 203.0.113.254 (INET eth0)
FGT1port3 (ISP-B)192.0.2.1/24ISP-B gateway 192.0.2.254 (INET eth1)
FGT1port2 (LAN)10.1.10.1/24PC1 10.1.10.10, H1 by DHCP
INETlo198.51.100.0/24public 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

  1. Start the lab
  2. SD-WAN building blocks
  3. Members, route and policy
  4. A performance SLA
  5. Rules for each kind of traffic
  6. Degrade ISP-A and watch the rules react
  7. 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.

Topology of SD-WAN - members SLAs and rules4 nodes and 1 network, 5 links. Every link is listed as text below the diagram.FGT1INETPC1H1LANport2eth0eth0port1eth0port3eth1
4 nodes and 1 network, with the interface names each link uses.
Nodes in SD-WAN: members, SLAs and rules, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
FGT1Fortinet FortiGatefortinet-FGT-v7.0.17.M-build06821 vCPU, 2,048 MB
INETEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
PC1EVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 2,048 MB
H1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder FortiGate NSE 4 guided labs.

  3. Open 20 - SD-WAN - members SLAs and rules and 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

All 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.