CloudLabBox
Try the free demo

FortiGate lab 25 of 25

Capstone: HQ cluster and branch over SD-WAN and IPsec

Build Harbourside's network from a requirements list: an HA cluster at head office with redundant internet, a published web server, directory admins, web filtering and syslog, and a branch that uses SD-WAN for the internet and two IPsec tunnels back to head office.

Run this lab

It needs Standard: its 7 nodes are set to 7 vCPU and 9,216 MB in total.

In your workspace: Shared, then FortiGate NSE 4 guided labs, then 25 - Capstone - HQ cluster and branch over SD-WAN and IPsec

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 7 vCPU and 9,216 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 180 minutes
Nodes need
7 vCPU, 9,216 MB
Smallest plan
Standard

The scenario

This is your final project for Harbourside Logistics. The hardware is racked, cabled and addressed; everything else is up to you. Read the requirements, plan, build, and prove each requirement. There are no step-by-step instructions: the hints point you at the right lab if you get stuck.

DeviceInterfaceAddressConnects to
FGT-HQ-A / FGT-HQ-B (cluster)port1 / port3203.0.113.1/24 / 192.0.2.1/24ISP-A / ISP-B (gateways .254)
FGT-HQ-A / FGT-HQ-B (cluster)port210.1.10.1/24HQ LAN: H1 (reserve 10.1.10.50)
FGT-HQ-A / FGT-HQ-B (cluster)port510.1.30.1/24Servers: SRV1 10.1.30.10 (web, LDAP, RADIUS, syslog)
FGT-HQ-A ↔ FGT-HQ-Bport4heartbeat
FGT-BRport1 / port3 / port2203.0.113.2 / 192.0.2.2 / 10.2.10.1 (/24)ISP-A / ISP-B / H2 10.2.10.50

Teaching values: admin password Cl@ssLab1; HA password HaLabKey1!; IPsec keys LabVpnKey1! (ISP-A tunnel) and LabVpnKey2! (ISP-B tunnel), des-sha256, DH 14; directory as in lab 11 (bind CN=fgt-bind,OU=Service,DC=corp,DC=lab / BindPass1!, users' password Training1!).

Evaluation licence. IPsec offers DES only (the lab uses des-sha256 with DH group 14; in production use AES-256-GCM, aes256gcm-prfsha384, with DH group 19, 20 or 21), the GUI runs over HTTP, and there is no FortiGuard, so web filtering uses a static URL filter.

What you’ll practise

  • Plan and build a complete two-site FortiGate design from requirements
  • Combine HA, routing, NAT, VIPs, authentication, security profiles, logging, IPsec and SD-WAN
  • Prove each requirement with the right command or test

The tasks

  1. Start the lab
  2. High availability at HQ
  3. HQ addressing, DHCP and routing
  4. HQ policies, NAT and web filtering
  5. Directory administrators and logging at HQ
  6. Two tunnels between HQ and the branch
  7. SD-WAN for the branch's internet

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 Capstone - HQ cluster and branch over SD-WAN and IPsec7 nodes and 4 networks, 16 links. Every link is listed as text below the diagram.FGT-HQ-AFGT-HQ-BFGT-BRINETSRV1H1H2ISP-AISP-BHQ-LANHQ-SERVERSeth0eth0port1port5eth0eth1port2port2port3port4port4port2eth0port1port3port5port1port3
7 nodes and 4 networks, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • FGT-HQ-A port1 to ISP-A (network)
  • FGT-HQ-B port1 to ISP-A (network)
  • FGT-BR port1 to ISP-A (network)
  • INET eth0 to ISP-A (network)
  • FGT-HQ-A port3 to ISP-B (network)
  • FGT-HQ-B port3 to ISP-B (network)
  • FGT-BR port3 to ISP-B (network)
  • INET eth1 to ISP-B (network)
  • FGT-HQ-A port2 to HQ-LAN (network)
  • FGT-HQ-B port2 to HQ-LAN (network)
  • H1 eth0 to HQ-LAN (network)
  • FGT-HQ-A port5 to HQ-SERVERS (network)
  • FGT-HQ-B port5 to HQ-SERVERS (network)
  • SRV1 eth0 to HQ-SERVERS (network)
  • FGT-HQ-A port4 to FGT-HQ-B port4
  • FGT-BR port2 to H2 eth0
Nodes in Capstone: HQ cluster and branch over SD-WAN and IPsec, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
FGT-HQ-AFortinet FortiGatefortinet-FGT-v7.0.17.M-build06821 vCPU, 2,048 MB
FGT-HQ-BFortinet FortiGatefortinet-FGT-v7.0.17.M-build06821 vCPU, 2,048 MB
FGT-BRFortinet FortiGatefortinet-FGT-v7.0.17.M-build06821 vCPU, 2,048 MB
INETEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
SRV1EVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
H1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
H2Alpine 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 25 - Capstone - HQ cluster and branch over SD-WAN and IPsec 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.