CloudLabBox
Try the free demo

FortiGate lab 8 of 25

Static routing, ECMP and link monitoring

Add a second ISP, compare the routing table with the routing database, use distance and priority for backup and load sharing, detect an upstream failure with a link monitor, and stop private traffic leaking with blackhole routes.

Run this lab

It needs Lite: its 4 nodes are set to 4 vCPU and 5,632 MB in total. That fits the free demo too.

In your workspace: Shared, then FortiGate NSE 4 guided labs, then 08 - Static routing ECMP and link monitoring

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
4 vCPU, 5,632 MB
Smallest plan
Lite

The scenario

Harbourside has signed a second internet contract: ISP-B is cabled to FGT1's port3. Today all traffic leaves through ISP-A, and last month ISP-A's core failed while its router next to you stayed up: the firewall kept sending traffic into a black hole for an hour. Build routing that uses both ISPs, notices failures beyond the ISP router, and never leaks private addresses to the internet.

DeviceInterfaceAddressConnects to
FGT1port1 (ISP-A)203.0.113.1/24ISP-A router 203.0.113.254 (INET eth0)
FGT1port3 (ISP-B)192.0.2.1/24ISP-B router 192.0.2.254 (INET eth1)
FGT1port2 (LAN)10.1.10.1/24PC1 10.1.10.10, H1 by DHCP
INETlo198.51.100.0/24public DNS .53, www.example.com .10 (reachable through both ISPs)

What you’ll practise

  • Read the routing table and the routing database and explain the difference
  • Use administrative distance and priority to build backup and equal-cost routes
  • Detect a failure beyond the next hop with a link monitor and fail over
  • Share traffic over two ISPs with ECMP
  • Add blackhole routes for private address space

The tasks

  1. Start the lab
  2. Routing table and routing database
  3. A floating backup route through ISP-B
  4. Detect an upstream failure with a link monitor
  5. Use both ISPs with ECMP
  6. Blackhole routes for private space

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 Static routing ECMP and link monitoring4 nodes and 1 network, 5 links. Every link is listed as text below the diagram.FGT1INETPC1H1LANport2eth0eth0port1eth0port3eth1
4 nodes and 1 network, with the interface names each link uses.
Every link, as text
  • FGT1 port1 to INET eth0
  • FGT1 port3 to INET eth1
  • FGT1 port2 to LAN (network)
  • PC1 eth0 to LAN (network)
  • H1 eth0 to LAN (network)
Nodes in Static routing, ECMP and link monitoring, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
FGT1Fortinet FortiGatefortinet-FGT-v7.0.17.M-build06821 vCPU, 2,048 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 NSE 4 guided labs.

  3. Open 08 - Static routing ECMP and link monitoring 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 labs

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