FortiGate lab 18 of 25
Redundant IPsec VPN over two ISPs
Add a second tunnel over the second ISP, tune dead peer detection, use route distance so the backup takes over by itself, prove it by failing the primary ISP, and compare active-standby with active-active designs.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 7,680 MB in total. That fits the free demo too.
In your workspace: Shared, then FortiGate NSE 4 guided labs, then 18 - Redundant IPsec VPN over two ISPs
- Level
- Advanced
- Time
- About 60 minutes
- Nodes need
- 5 vCPU, 7,680 MB
- Smallest plan
- Lite
The scenario
The tunnel you built in lab 17 now carries the branch's accounting system, and last week ISP-A was down for two hours. Both sites have a second internet line from ISP-B. Add a second tunnel over ISP-B that takes over by itself when ISP-A fails, and hands traffic back when it recovers. The primary tunnel (HQ-to-BR-A / BR-to-HQ-A) is already built and working.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| FGT-HQ | port1 / port3 | 203.0.113.1/24 / 192.0.2.1/24 | ISP-A / ISP-B (gateways .254) |
| FGT-HQ | port2 | 10.1.10.1/24 | PC1 10.1.10.10 |
| FGT-BR | port1 / port3 | 203.0.113.2/24 / 192.0.2.2/24 | ISP-A / ISP-B (gateways .254) |
| FGT-BR | port2 | 10.2.10.1/24 | H2 10.2.10.50 |
Second tunnel (teaching values): HQ-to-BR-B / BR-to-HQ-B over ISP-B, IKEv2, pre-shared key LabVpnKey2!, des-sha256, DH group 14.
Evaluation licence. These FortiGates run with low-strength encryption only, so IPsec offers DES only (
des-md5todes-sha512): no AES, no 3DES. The lab usesdes-sha256with DH group 14 to get working tunnels. Never use DES in production: use AES-256-GCM (aes256gcm-prfsha384) with DH group 19, 20 or 21.
What you’ll practise
- Build a second, independent tunnel over a second ISP
- Tune dead peer detection so failures are noticed in seconds
- Use route distance so a backup tunnel takes over automatically
- Fail the primary path and watch routes and sessions move
- Compare active-standby, active-active and SD-WAN overlays for redundant VPNs
The tasks
- Start the lab
- Check the primary tunnel and its DPD
- A second tunnel over ISP-B
- Routes and policies for the backup
- Fail ISP-A and watch the switch-over
- Choosing a redundancy design (reading task)
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
- FGT-HQ
port1to ISP-A (network) - FGT-BR
port1to ISP-A (network) - INET
eth0to ISP-A (network) - FGT-HQ
port3to ISP-B (network) - FGT-BR
port3to ISP-B (network) - INET
eth1to ISP-B (network) - FGT-HQ
port2to PC1eth0 - FGT-BR
port2to H2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| FGT-HQ | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 MB |
| FGT-BR | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 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 |
| H2 | 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 NSE 4 guided labs.Open
18 - Redundant IPsec VPN over two ISPsand 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
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.