zNetLaB › Guided labs › Enterprise
DMVPN phase 3 with EIGRP
Enterprise Advanced 4 devices 4 checked tasks 100 points Plan lab
A hub and two spokes on an internet underlay. Register the spokes with NHRP, run EIGRP over the tunnel, and let the hub redirect spoke-to-spoke traffic. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
A hub and two spokes on an internet underlay. Register the spokes with NHRP, run EIGRP over the tunnel, and let the hub redirect spoke-to-spoke traffic.
Your role: a network engineer on the enterprise team. Level: Advanced Done when: all 4 goals show as passed (100 points).
Network status
Devices: 4 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. HUB, INET, S1, S2 start with an empty configuration. Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure. Goals
Both spokes are registered on the hub (30 pts) Spoke 1 has learned the LAN behind spoke 2 (30 pts) The hub redirects and spokes use shortcuts (10 pts) Spoke 1 reaches the LAN behind spoke 2 (30 pts) The activity, in order
Both spokes are registered on the hub Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Spoke 1 has learned the LAN behind spoke 2 Why: If the prefix is not in the routing table, the router drops packets for it, whatever else is configured. Verify with: show ip route The hub redirects and spokes use shortcuts Why: This is the task that checks your configuration directly: the line must really be there, not just look right. Verify with: show running-config Spoke 1 reaches the LAN behind spoke 2 Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 192.168.102.1 Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong. Why this matters
A hub and two spokes on an internet underlay. Register the spokes with NHRP, run EIGRP over the tunnel, and let the hub redirect spoke-to-spoke traffic.
What you will be able to do
Both spokes are registered on the hub
Spoke 1 has learned the LAN behind spoke 2
The hub redirects and spokes use shortcuts
Spoke 1 reaches the LAN behind spoke 2
The network
Catalyst 8000V — 4 devices in all, already cabled.
Gi1 Gi1 Gi1 Gi2 Gi1 Gi3 HUB INET S1 S2 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
HUB Catalyst 8000V configure it INET Catalyst 8000V configure it S1 Catalyst 8000V configure it S2 Catalyst 8000V configure it
Cabling
HUB Gi1 ↔ INET Gi1 S1 Gi1 ↔ INET Gi2 S2 Gi1 ↔ INET Gi3
What is configured at the start
Nothing is configured to start with beyond the addresses above: you build the configuration from a clean start.
Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 Both spokes are registered on the hub 30 Checked automatically against the device’s live state (dmvpnPeers). 2 Spoke 1 has learned the LAN behind spoke 2 30 On S1: show ip route lists 192.168.102.1/32. 3 The hub redirects and spokes use shortcuts 10 On HUB: show running-config contains the line(s) matching ip nhrp redirect. 4 Spoke 1 reaches the LAN behind spoke 2 30 On S1: ping 192.168.102.1 must succeed.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
INET interface GigabitEthernet1
ip address 203.0.113.2 255.255.255.252
no shutdown
exit
interface GigabitEthernet2
ip address 203.0.113.6 255.255.255.252
no shutdown
exit
interface GigabitEthernet3
ip address 203.0.113.10 255.255.255.252
no shutdown
exit HUB interface GigabitEthernet1
ip address 203.0.113.1 255.255.255.252
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 203.0.113.2
interface Loopback1
ip address 192.168.100.1 255.255.255.255
exit
interface Tunnel0
ip address 10.0.0.1 255.255.255.0
no ip redirects
ip nhrp authentication KEY
ip nhrp map multicast dynamic
ip nhrp network-id 1
ip nhrp redirect
no ip split-horizon eigrp 100
no ip next-hop-self eigrp 100
tunnel source GigabitEthernet1
tunnel mode gre multipoint
tunnel key 100
no shutdown
exit
router eigrp 100
network 10.0.0.0 0.0.0.255
network 192.168.100.1 0.0.0.0
exit S1 interface GigabitEthernet1
ip address 203.0.113.5 255.255.255.252
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 203.0.113.6
interface Loopback1
ip address 192.168.101.1 255.255.255.255
exit
interface Tunnel0
ip address 10.0.0.11 255.255.255.0
no ip redirects
ip nhrp authentication KEY
ip nhrp map 10.0.0.1 203.0.113.1
ip nhrp map multicast 203.0.113.1
ip nhrp network-id 1
ip nhrp nhs 10.0.0.1
ip nhrp shortcut
tunnel source GigabitEthernet1
tunnel mode gre multipoint
tunnel key 100
no shutdown
exit
router eigrp 100
network 10.0.0.0 0.0.0.255
network 192.168.101.1 0.0.0.0
exit S2 interface GigabitEthernet1
ip address 203.0.113.9 255.255.255.252
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 203.0.113.10
interface Loopback1
ip address 192.168.102.1 255.255.255.255
exit
interface Tunnel0
ip address 10.0.0.12 255.255.255.0
no ip redirects
ip nhrp authentication KEY
ip nhrp map 10.0.0.1 203.0.113.1
ip nhrp map multicast 203.0.113.1
ip nhrp network-id 1
ip nhrp nhs 10.0.0.1
ip nhrp shortcut
tunnel source GigabitEthernet1
tunnel mode gre multipoint
tunnel key 100
no shutdown
exit
router eigrp 100
network 10.0.0.0 0.0.0.255
network 192.168.102.1 0.0.0.0
exit Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.