CCNP ENARSI lab 23 of 35
DMVPN phase 3 with IKEv2 and IPsec protection
Turn a working phase 2 DMVPN into phase 3, so the hub can summarise while spokes still build direct tunnels through NHRP redirects and shortcuts, then encrypt every tunnel with an IKEv2 and IPsec profile.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 2,560 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 23 - DMVPN phase 3 with IKEv2 and IPsec protection
- Level
- Advanced
- Time
- About 75 minutes
- Nodes need
- 5 vCPU, 2,560 MB
- Smallest plan
- Lite
The scenario
Ibis Pharmacy's DMVPN (lab 22) works, but two problems have come up. The company plans 200 branches, and in phase 2 every spoke must carry every other spoke's LAN with that spoke as next hop: the hub can't summarise, so every branch router needs a full routing table. And the security team has noticed that the tunnels are plain GRE over the Internet: anyone on the path can read prescription images.
You'll move to phase 3, which lets the hub send just a summary and still gives direct spoke-to-spoke traffic, and then protect every tunnel with IPsec negotiated by IKEv2.
| Device | Public (NBMA) address | Tunnel0 | LAN |
|---|---|---|---|
| HUB | 198.51.100.1 | 172.16.0.1/24 | 10.1.1.0/24 |
| BR2 | 203.0.113.2 | 172.16.0.2/24 | 10.2.2.0/24 |
| BR3 | 203.0.113.6 | 172.16.0.3/24 | 10.3.3.0/24 |
| BR4 | 203.0.113.10 | 172.16.0.4/24 | 10.4.4.0/24 |
Starting point: the phase 2 DMVPN from lab 22 (mGRE everywhere, EIGRP AS 10, hub with split horizon and next-hop-self disabled). IPsec settings: IKEv2 keyring DMVPN-KR with one wildcard peer and pre-shared key Ibis-Dmvpn-Psk, IKEv2 profile DMVPN-IKEV2, transform set DMVPN-TS (AES-256, SHA-256, transport mode), IPsec profile DMVPN-PROF.
What you’ll practise
- Explain the difference between DMVPN phases 2 and 3 and why phase 3 scales better
- Configure NHRP redirect on the hub and NHRP shortcut on the spokes
- Summarise towards the spokes and still get direct spoke-to-spoke traffic
- Build an IKEv2 keyring, IKEv2 profile, transform set and IPsec profile
- Protect mGRE tunnels with tunnel protection and verify IKE and IPsec security associations
The tasks
- Look at phase 2's cost
- Convert to phase 3
- Watch a shortcut being built
- Build the IKEv2 and IPsec profiles
- Protect the tunnels
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
- HUB
Gi0/0to ISPGi0/0 - BR2
Gi0/0to ISPGi0/1 - BR3
Gi0/0to ISPGi0/2 - BR4
Gi0/0to ISPGi0/3
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| HUB | 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 |
| BR2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| BR3 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| BR4 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 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
CCNP ENARSI 300-410 guided labs.Open
23 - DMVPN phase 3 with IKEv2 and IPsec protectionand 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 ENARSI 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.