zNetLaB › Guided labs › Enterprise
EIGRP stub — a spoke that is never a transit path
Enterprise Intermediate 3 devices 4 checked tasks 100 points Plan lab
A branch router sits between the hub and a lab router it also talks to. Left alone it is a transit path — the hub learns the lab network through it and queries it on every change. Make it an EIGRP stub that advertises only its own connected networks. 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 branch router sits between the hub and a lab router it also talks to. Left alone it is a transit path — the hub learns the lab network through it and queries it on every change. Make it an EIGRP stub that advertises only its own connected networks.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 4 goals show as passed (100 points).
Network status
Devices: 3 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. HUB starts with addresses (G0/0 10.0.12.1/24, L0 1.1.1.1/32) and EIGRP 100 already configured. BRANCH starts with addresses (G0/0 10.0.12.2/24, G0/1 10.0.23.2/24, L0 2.2.2.2/32) and EIGRP 100 already configured. LAB starts with addresses (G0/0 10.0.23.3/24, L0 3.3.3.3/32) and EIGRP 100 already configured. 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
BRANCH is an EIGRP stub (20 pts) The hub still learns BRANCH’s own loopback (25 pts) The hub no longer learns the lab network through BRANCH (30 pts) BRANCH itself still reaches both sides (25 pts) The activity, in order
BRANCH is an EIGRP stub Why: Each goal is a state the lab can check on the running device. Verify with: show running-config The hub still learns BRANCH’s own loopback Why: The code tells you HOW a route was learned, which tells you which process to look at if it is wrong. Verify with: show ip route The hub no longer learns the lab network through BRANCH Why: A route that should not exist is a leak or a loop waiting to happen. Verify with: show ip route BRANCH itself still reaches both sides Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 1.1.1.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 branch router sits between the hub and a lab router it also talks to. Left alone it is a transit path — the hub learns the lab network through it and queries it on every change. Make it an EIGRP stub that advertises only its own connected networks.
What you will be able to do
BRANCH is an EIGRP stub
The hub still learns BRANCH’s own loopback
The hub no longer learns the lab network through BRANCH
BRANCH itself still reaches both sides
The network
ISR 2911 — 3 devices in all, already cabled.
Gi0/0 10.0.12.1/24 Gi0/0 10.0.12.2/24 Gi0/1 10.0.23.2/24 Gi0/0 10.0.23.3/24 HUB BRANCH LAB Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
HUB ISR 2911 configure it BRANCH ISR 2911 configure it LAB ISR 2911 configure it
Cabling
HUB Gi0/0 ↔ BRANCH Gi0/0 BRANCH Gi0/1 ↔ LAB Gi0/0
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
HUB interface g0/0
ip address 10.0.12.1 255.255.255.0
no shutdown
exit
interface lo0
ip address 1.1.1.1 255.255.255.255
no shutdown
exit
router eigrp 100
network 10.0.12.0 0.0.0.255
network 1.1.1.1 0.0.0.0
no auto-summary BRANCH interface g0/0
ip address 10.0.12.2 255.255.255.0
no shutdown
exit
interface g0/1
ip address 10.0.23.2 255.255.255.0
no shutdown
exit
interface lo0
ip address 2.2.2.2 255.255.255.255
no shutdown
exit
router eigrp 100
network 10.0.0.0 0.255.255.255
network 2.2.2.2 0.0.0.0
no auto-summary LAB interface g0/0
ip address 10.0.23.3 255.255.255.0
no shutdown
exit
interface lo0
ip address 3.3.3.3 255.255.255.255
no shutdown
exit
router eigrp 100
network 10.0.23.0 0.0.0.255
network 3.3.3.3 0.0.0.0
no auto-summary 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 BRANCH is an EIGRP stub 20 Checked automatically against the device’s live state (eigrpStub). 2 The hub still learns BRANCH’s own loopback 25 On HUB: show ip route lists 2.2.2.2/32 with code D. 3 The hub no longer learns the lab network through BRANCH 30 On HUB: show ip route does not list 3.3.3.3/32. 4 BRANCH itself still reaches both sides 25 On BRANCH: ping 1.1.1.1 must succeed. and On BRANCH: ping 3.3.3.3 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:
BRANCH router eigrp 100
eigrp stub connected summary Where this is examined
This lab practises these topics in the zNetLaB certification courses:
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.