CloudLabBox
Try the free demo

FortiGate SD-WAN lab 1 of 14

Members and zones on a two-ISP branch

Move a branch from a single static route on ISP-A to SD-WAN over two ISPs: clear the old references, put both links into an underlay zone as members, point one route and one policy at the zone, and use member priority to make ISP-B a hot standby.

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 01 - Members and zones on a two-ISP branch

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

The scenario

Kestrel Logistics runs its Leeds depot (BR1) on one internet line, ISP-A. A second line from ISP-B was installed last month and sits unused, cabled to port2. The network lead wants both lines working under SD-WAN before the depot's busy season: ISP-A stays the main line because it has the better contract, ISP-B carries traffic the moment ISP-A fails, and later labs will add health checks and rules on top.

DeviceInterfaceAddressConnects to
BR1port1 (ISP-A)203.0.113.2/24ISP-A gateway 203.0.113.254, through the WAN emulator
BR1port2 (ISP-B)192.0.2.2/24ISP-B gateway 192.0.2.254
BR1port3 (LAN)10.2.10.1/24PC1 10.2.10.10, H1 10.2.10.50 (DHCP reservation)
INETeth0, eth1203.0.113.254, 192.0.2.254both ISPs' gateways
INETlo198.51.100.0/24public DNS .53, www.example.com .10 and other test sites

http://www.example.com/whoami answers with the address it saw: client=203.0.113.2 means BR1 left through ISP-A, client=192.0.2.2 through ISP-B.

What you’ll practise

  • Explain underlay and overlay links, SD-WAN members, zones and the implicit rule
  • Remove the references that stop an interface joining SD-WAN
  • Add members with gateways to a custom zone and route and permit traffic through the zone
  • Read members, zones and routes with diagnose sys sdwan and the routing table
  • Use member priority for active and standby links and prove failover on link loss

The tasks

  1. Start the lab
  2. The depot before SD-WAN
  3. Members in an underlay zone
  4. One route and one policy for the zone
  5. Fail ISP-A and come back
  6. Look at 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.

Topology of Members and zones on a two-ISP branch5 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 Members and zones on a two-ISP branch, 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 01 - Members and zones on a two-ISP branch 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.