CloudLabBox
Try the free demo

FortiGate SD-WAN lab 11 of 14

Monitoring and diagnostics

Investigate a complaint the way an SD-WAN operator does: turn on SLA logging and warning thresholds, reproduce a lossy, jittery ISP with the WAN emulator, then read the health-check history, SD-WAN event logs, interface SLA logs, a packet capture of the probes and a debug-flow trace of a user's session.

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 11 - Monitoring and diagnostics

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

Staff at Leeds say video calls "break up" every afternoon, but nobody can say when or on which line. BR1 measures both ISPs with INET_SLA, yet nothing is logged, so there is no history to look at. You'll make BR1 record SLA changes, reproduce the afternoon's problem on ISP-A with the WAN emulator, and work through the diagnostic tools an SD-WAN operator uses, from logs to a packet capture and a debug-flow trace.

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

BR1 has INET_SLA (ping 198.51.100.53 every 500 ms, target 1: 100 ms, 50 ms, 5%) and rule 1 Web-Best-Quality (TCP 80, lowest packet loss).

What you’ll practise

  • Log SLA failures and passes, and set warning and alert thresholds
  • Read SD-WAN events, health-check history and interface bandwidth logs
  • Capture health-check probes with the packet sniffer
  • Trace a session through SD-WAN rule, route and policy with debug flow
  • Find the same information in the GUI's SD-WAN pages and dashboard widgets

The tasks

  1. Start the lab
  2. Make SLA changes leave a trail
  3. Reproduce the afternoon
  4. Read the history
  5. Capture the probes
  6. Trace one session
  7. The same picture in the GUI

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 Monitoring and diagnostics5 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 Monitoring and diagnostics, 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 11 - Monitoring and diagnostics 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.