AdvancedPublished 2026-06-23
OSPFv2 Multi-Area Capstone: 3-Rtr Line, Auth, LAN Host Intact
Bundle lab
Advanced CCNP OSPFv2 multi-area capstone. Build a three-router line topology with area 10 at the branch, area 0 at the core, and MD5 authentication on the area 0 transit. Advertise all loopbacks and a branch user LAN. Validate end-to-end reachability from the branch host to every router loopback and the core LAN. Includes realistic enterprise management and verification flows.
Learning objectives
- Design and configure multi-area OSPFv2 over a realistic branch-to-core topology with an ABR.
- Implement and verify OSPF MD5 authentication on area 0 transit links.
- Advertise router loopbacks and a branch LAN while keeping user-facing interfaces passive.
- Verify inter-area route exchange from end hosts and troubleshoot common adjacency and reachability issues.
Troubleshooting focus
- No neighbor between RTR-REGIONAL-ABR and RTR-CORE-DC: Check both ends have MD5 enabled with identical key-id and key, and that the interface is in area 0 on both routers.;
show ip ospf interfaceconfirms authentication is enabled;show ip ospf neighborgives the state, which should be FULL. - No neighbor between RTR-BRANCH-EDGE and RTR-REGIONAL-ABR: check the area IDs (both area 10), the wildcard for 10.0.12.0/30, and that the interface is not passive.
- Routes to loopbacks or LANs are missing: confirm those networks are matched by OSPF network statements. Passive keeps them advertised; it does not withdraw them.
- CLIENT-BRANCH10 pings fail although adjacencies are up: verify host IP/mask/gateway, then that RTR-CORE-DC sees 10.10.10.0/24 and RTR-BRANCH-EDGE sees 10.20.20.0/24.
- Adjacencies never settle or the LSDB is unstable: recheck the router-ids — each must match that router's own Loopback0 and be unique.
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.