AdvancedPublished 2026-07-03
EIGRP Stub Routing on a Spoke (Hub-and-Spoke, AS 100)
Bundle lab
Configure a classic hub-and-spoke EIGRP domain where the single-homed branch (R2) is made an EIGRP stub, limiting query scope while still advertising its LAN. Validate that R1 flags R2 as a stub neighbor, routes still exchange, and query behavior is scoped appropriately.
Learning objectives
- Build a hub-and-spoke EIGRP domain using a single AS (100) and classless operation (no auto-summary).
- Configure R2 (single-homed spoke) as an EIGRP stub advertising only connected routes.
- Ensure LAN-facing interfaces are passive so EIGRP never forms adjacencies toward hosts.
- Verify the stub flag from the hub (R1) and confirm normal route advertisement continues.
- Compare behavior with and without a stub to understand how query scope is reduced.
Troubleshooting focus
- Confirm all routers use the same EIGRP AS (100) and default K-values.
- Check that each transit subnet is enabled under EIGRP with the correct wildcard mask.
- Ensure host-facing interfaces are passive; only router-to-router transits should form neighbors.
- Verify that R2 is actually in stub mode (eigrp stub connected) and that R1 recognizes it as a stub neighbor.
- If a route is missing, confirm it is connected and matched by a network statement on the originating router.
Topology
Subscribe to preview this lab's topology.
See plansGrade your work
How this lab is graded
- Build it your way. Where a lab lets you choose a value — a VLAN name, an interface description — grading checks that you configured it, not which name you picked. Names that another line has to reference, like an ACL applied with
access-class, are stated in the guide and do have to match. - Addresses, modes and protocol keywords are exact. An IP address, a subnet mask,
switchport mode trunk, an encapsulation — these carry the meaning of the lab, so they are graded as written in the guide. - Grading reads your saved configuration. Export the lab from CML after you have configured it, and make sure anything you set is in the running-config — a change that only exists in a terminal session never reaches the grader.
- You can submit as many times as you like. Your best score stands, and each attempt tells you which checks passed so you can work the gaps.
- Scored something you believe is correct? Use Report an issue on this page — that is exactly how the grading fixes in the changelog got found.
Create a free account to submit your lab for grading.
Create a free accountFound a problem with this lab?
Please sign in to report a problem — tying it to your attempts lets us reproduce and fix it faster.