CloudLabBox
Try the free demo

FortiGate SD-WAN lab 5 of 14

SD-WAN routing and sessions

Follow a session through BR1's decisions: policy routes, then SD-WAN rules, then the routing table. Prove that a policy route beats a rule, watch a session stay on its old link after the routing changes, clear it or let snat-route-change move it, and make the FortiGate's own DNS traffic follow SD-WAN.

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 05 - SD-WAN routing and sessions

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 70 minutes
Nodes need
5 vCPU, 6,144 MB
Smallest plan
Lite

The scenario

The Leeds depot's guest kiosk (H1, 10.2.10.50) must leave through ISP-B for everything, by contract with the depot's landlord, while staff web traffic follows the SD-WAN rule that keeps it on ISP-A. A contractor solved it with a policy route, and now nobody can explain why the kiosk ignores the SD-WAN rules, or why a long download stayed on the old line after a change. You'll work through BR1's decisions one by one, then make BR1's own DNS queries use ISP-B too.

DeviceInterfaceAddress
BR1port1 (ISP-A, member 1)203.0.113.2/24, gateway 203.0.113.254
BR1port2 (ISP-B, member 2)192.0.2.2/24, gateway 192.0.2.254
BR1port3 (LAN)10.2.10.1/24: PC1 .10, H1 .50

BR1 starts with both members in underlay (equal priority), INET_SLA, one zone default route, the LAN policy and rule 1 Web-via-ISP-A (TCP 80 to member 1).

What you’ll practise

  • Explain the order of route lookup: policy routes, SD-WAN rules, then the routing table
  • Read zone and member routes, the routing database and the policy-route table
  • Prove that a regular policy route takes precedence over an SD-WAN rule
  • Read the session table and explain why sessions keep their route, and what re-evaluates them
  • Steer the FortiGate's own (local-out) DNS traffic with SD-WAN

The tasks

  1. Start the lab
  2. Where routes come from
  3. A policy route beats an SD-WAN rule
  4. Sessions keep their route
  5. The FortiGate's own traffic

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 routing and sessions5 nodes and 1 network, 6 links. Every link is listed as text below the diagram.BR1WANINETPC1H1LANport3eth0eth0port1eth0eth1eth0port2eth1
5 nodes and 1 network, with the interface names each link uses.
Every link, as text
  • BR1 port1 to WAN eth0
  • WAN eth1 to INET eth0
  • BR1 port2 to INET eth1
  • BR1 port3 to LAN (network)
  • PC1 eth0 to LAN (network)
  • H1 eth0 to LAN (network)
Nodes in SD-WAN routing and sessions, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
BR1Fortinet FortiGatefortinet-FGT-v7.0.17.M-build06821 vCPU, 2,048 MB
WANAlpine WAN emulatorclbalpinewanem-alpine-wanem-3-20-31 vCPU, 512 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 SD-WAN guided labs.

  3. Open 05 - SD-WAN routing and sessions 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 SD-WAN labs

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