CCNP ENCOR lab 17 of 36
IPsec: static VTI with IKEv2, and GRE over IPsec
Encrypt Fernhill's branch links across the internet two ways: a static virtual tunnel interface with IKEv2 to Bristol, and GRE protected by IPsec with IKEv1 to Glasgow, then route both with OSPF and read the security associations.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 4,096 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENCOR 350-401 guided labs, then 17 - IPsec - static VTI with IKEv2 and GRE over IPsec
- Level
- Advanced
- Time
- About 80 minutes
- Nodes need
- 6 vCPU, 4,096 MB
- Smallest plan
- Lite
The scenario
The GRE tunnels from lab 16 work, but the audit team has pointed out that GRE sends everything in clear text across the internet. Fernhill Freight's hub router in Leeds (R1) must now encrypt its links to Bristol (R2) and Glasgow (R3):
- Bristol gets the modern design: a static virtual tunnel interface (VTI) protected by IPsec and negotiated with IKEv2.
- Glasgow's router is managed by a partner who only supports IKEv1, so it keeps a GRE tunnel, now protected with IPsec.
OSPF must run over both tunnels so the three sites reach each other through Leeds.
| Device | Interface | Address | Notes |
|---|---|---|---|
| R1 (hub) | Gi0/0 | 203.0.113.2/30 | Internet |
| R1 | Lo10 / Lo0 | 10.10.30.1/24 / 10.255.0.1/32 | HQ servers |
| R1 | Tunnel1 / Tunnel2 | 172.16.12.1/30 / 172.16.13.1/30 | to R2 / to R3 |
| R2 (Bristol) | Gi0/0 / Gi0/1 / Tunnel1 | 203.0.113.6/30 / 10.20.10.1/24 / 172.16.12.2/30 | PC2 10.20.10.10 |
| R3 (Glasgow) | Gi0/0 / Gi0/1 / Tunnel2 | 203.0.113.10/30 / 10.30.10.1/24 / 172.16.13.2/30 | PC3 10.30.10.10 |
| ISP | Gi0/0 / Gi0/1 / Gi0/2 | 203.0.113.1 / .5 / .9 | don't change |
Security policy: AES-256, SHA-256, Diffie-Hellman group 14. Pre-shared keys: Fh-Br1stol-VPN (Leeds–Bristol) and Fh-Glasg0w-VPN (Leeds–Glasgow). Each router already has a default route to the ISP. Router IDs: R*n* = n.n.n.n.
Topology: R1, R2 and R3 each connect to the ISP router; PC2 sits behind R2 and PC3 behind R3.
What you’ll practise
- Explain what IPsec provides, the two IKE phases, ESP, and tunnel versus transport mode
- Build IKEv2 proposals, policies, keyrings and profiles, and an IPsec profile
- Configure a static VTI (tunnel mode ipsec ipv4) and route over it
- Protect a GRE tunnel with IPsec in transport mode using IKEv1
- Verify IKE and IPsec security associations and packet counters
The tasks
- Know what you're building
- IKEv2 building blocks on R1 and R2
- The static VTI to Bristol
- GRE over IPsec to Glasgow with IKEv1
- Route over both tunnels
- Prove the traffic is protected
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
- R1
Gi0/0to ISPGi0/0 - R2
Gi0/0to ISPGi0/1 - R3
Gi0/0to ISPGi0/2 - R2
Gi0/1to PC2eth0 - R3
Gi0/1to PC3eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| ISP | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R3 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| PC2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC3 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNP ENCOR 350-401 guided labs.Open
17 - IPsec - static VTI with IKEv2 and GRE over IPsecand 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 CCNP ENCOR labs
Related labs in other courses
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.