FortiGate SD-WAN lab 4 of 14

Internet service and application steering

Steer traffic by what it is rather than by port: see why the evaluation unit's internet service database has names but no addresses, build a custom internet service and an FQDN destination instead, then steer web browsers with an application group and watch FortiGate learn the application before the rule takes over.

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 04 - Internet service and application steering

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

The scenario

The Leeds depot's ISP-A line is busy during the day. The network lead wants three kinds of traffic moved to ISP-B, wherever the servers live: the file-transfer service at files.example.com, the online shop at shop.example.com (whose addresses the shop changes now and then), and all web browsing by people, as opposed to tools and scripts. Everything else stays on ISP-A, the main line.

SiteAddressNotes
www.example.com198.51.100.10general site, stays on ISP-A
news.example.net198.51.100.11read by people in browsers
files.example.com198.51.100.13file transfers on TCP 80 and 443
shop.example.com198.51.100.14resolved by name

BR1 starts with both ISPs in underlay, INET_SLA, and ISP-B as the standby (member priority 10), so anything no rule matches leaves through ISP-A.

What you’ll practise

  • Explain internet services (ISDB) as SD-WAN destinations and what the evaluation licence lacks
  • Create a custom internet service and an FQDN address and steer them with rules
  • Steer by application with application control, an application group and the app cache
  • Explain why the first session to an application uses another rule
  • Order application, internet-service and address rules correctly

The tasks

  1. Start the lab
  2. What the internet service database gives you here
  3. A custom internet service
  4. An FQDN destination
  5. Application steering
  6. Read the rules as FortiGate does

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 Internet service and application steering5 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.
Nodes in Internet service and application steering, 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 04 - Internet service and application steering 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.