CCNP ENARSI lab 34 of 35
Capstone 1: build the Merganser enterprise WAN
Build a complete enterprise WAN from bare addressing: an OSPF core, an EIGRP data centre joined by safe mutual redistribution, an eBGP Internet edge that feeds a default route, and an encrypted phase 3 DMVPN for the branches in its own OSPF area, then prove every path end to end.
Run this lab
It needs Standard: its 8 nodes are set to 8 vCPU and 4,608 MB in total.
In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 34 - Capstone 1 - build the Merganser enterprise WAN
- Level
- Advanced
- Time
- About 150 minutes
- Nodes need
- 8 vCPU, 4,608 MB
- Smallest plan
- Standard
The scenario
Merganser Group has merged three networks and you are the engineer who joins them. Everything is cabled and addressed; no routing, VPN or service is configured, except on the provider's router. Build the design below, then prove it works from every corner. Work in the order of the tasks: each one depends on the one before.
| Router | Role | Key addresses |
|---|---|---|
| HQ1, HQ2 | head-office core; OSPF area 0; EIGRP to the data centre; redistribution points | Lo0 10.255.0.1 / .2; HQ1–HQ2 10.0.12.0/24; to DC 172.20.101.0/24 and 172.20.102.0/24 |
| DC | data centre, EIGRP named mode DC, AS 100 | LANs 172.20.0.0/24–172.20.3.0/24 (Lo1–Lo4), Lo0 172.20.255.1 |
| EDGE | Internet edge: OSPF area 0 and 10, eBGP, DMVPN hub | Lo0 10.255.0.3; to HQ1 10.0.13.0/24, to HQ2 10.0.23.0/24; Internet 198.51.100.1/30; Tunnel0 172.16.0.1/24 |
| ISP | provider AS 64501 (configured) | 198.51.100.2 (EDGE), .5 (BR1), .9 (BR2); content 192.0.2.1 |
| BR1 | branch 1, DMVPN spoke, DHCP server for PC1 | Internet 198.51.100.6/30; LAN 10.10.1.1/24; Tunnel0 172.16.0.11 |
| BR2 | branch 2, DMVPN spoke | Internet 198.51.100.10/30; LAN Lo1 10.10.2.1/24; Tunnel0 172.16.0.12 |
Design rules
- OSPF process 1: area 0 on HQ1, HQ2 and EDGE (loopbacks and core links, point-to-point network type), router IDs 1.1.1.1, 2.2.2.2, 3.3.3.3. Area 10 is the DMVPN: tunnels use the point-to-multipoint network type; branch router IDs 11.11.11.11 and 12.12.12.12; BR1's LAN is passive. EDGE summarises area 10 as 10.10.0.0/16 and originates a default route into OSPF from its BGP default.
- EIGRP: named instance
DC, AS 100, on DC (all of 172.20.0.0/16) and on HQ1/HQ2 (their DC links). Router IDs 1.1.1.1, 2.2.2.2 and 5.5.5.5. - Redistribution on both HQ1 and HQ2, both directions, with tags: EIGRP → OSPF tagged 90 (deny tag 110), OSPF → EIGRP tagged 110 (deny tag 90), seed metric 1000000 10 255 1 1500,
subnetsinto OSPF. - BGP: EDGE in AS 64500 peers with 198.51.100.2 (AS 64501) with MD5 password
Merg-Bgp-Key, and originates 203.0.113.0/24 (static route to Null0). - DMVPN phase 3: Tunnel0 on EDGE (hub) and both branches: NHRP network ID 10, authentication
MERGKEY, tunnel key 10, IP MTU 1400, MSS 1360, NHRP redirect on the hub and shortcut on the spokes, IPsec profileDMVPN-PROF(IKEv2 keyringDMVPN-KRwith keyMerg-Dmvpn-Psk, transform setDMVPN-TSAES-256/SHA-256 transport mode). - DHCP on BR1: pool
BR1-LANfor 10.10.1.0/24 (gateway .1, DNS 192.0.2.53, domainmerganser.lab), excluding .1–.9. - The branches keep their static default route to the ISP for Internet traffic (split tunnelling).
What you’ll practise
- Design and configure OSPF areas, network types and summarisation for a core and a DMVPN area
- Join an EIGRP named-mode domain to OSPF at two points without feedback
- Peer eBGP with an authenticated provider, originate the company prefix and inject a default route into OSPF
- Build an IKEv2-protected phase 3 DMVPN running OSPF point-to-multipoint
- Serve DHCP at a branch and verify the whole design end to end
The tasks
- OSPF area 0
- EIGRP data centre and redistribution
- The Internet edge
- The encrypted DMVPN and area 10
- Branch DHCP
- Prove the design
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
- HQ1
Gi0/0to DCGi0/0 - HQ2
Gi0/0to DCGi0/1 - HQ1
Gi0/1to HQ2Gi0/1 - HQ1
Gi0/2to EDGEGi0/0 - HQ2
Gi0/2to EDGEGi0/1 - EDGE
Gi0/2to ISPGi0/0 - ISP
Gi0/1to BR1Gi0/0 - ISP
Gi0/2to BR2Gi0/0 - BR1
Gi0/1to PC1eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| HQ1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| HQ2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| EDGE | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| DC | 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 |
| BR1 | 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 |
| PC1 | 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 ENARSI 300-410 guided labs.Open
34 - Capstone 1 - build the Merganser enterprise WANand 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.