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
- 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.
| Site | Address | Notes |
|---|---|---|
| www.example.com | 198.51.100.10 | general site, stays on ISP-A |
| news.example.net | 198.51.100.11 | read by people in browsers |
| files.example.com | 198.51.100.13 | file transfers on TCP 80 and 443 |
| shop.example.com | 198.51.100.14 | resolved 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
- Start the lab
- What the internet service database gives you here
- A custom internet service
- An FQDN destination
- Application steering
- 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.
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
04 - Internet service and application steeringand 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.