OSPF Labs and Study Path
Move from core link-state concepts to multi-area design and systematic troubleshooting. Each page links configuration theory with commands and verification checks.
OSPF Labs and Study Path: OSPF Labs
Start with the fundamentals
Build advanced designs
Verify and troubleshoot
Use neighbor, LSDB, interface and routing-table checks to isolate adjacency and reachability problems.
Related networking resources
Compare OSPF behavior with the other protocols in the routing labs hub, inspect public addressing with the IP Location Finder, and review address translation in the Cisco NAT configuration guide.
Recommended OSPF learning sequence
Begin with a single area and two routers. Confirm that hello packets create a Full adjacency and that connected networks appear as OSPF routes. Add a broadcast segment to observe the DR and BDR election, then introduce a second area through an area border router. This sequence makes the neighbor state machine, LSDB, and routing table easier to correlate.
After the baseline works, compare router, network, summary, external, and NSSA LSAs. Practice cost changes and equal-cost paths before adding authentication or filtering. Finish with a controlled failure—shut a link, change an area ID, or create an MTU mismatch—and use evidence to identify the exact stage that failed.
Commands to collect before troubleshooting
show ip ospf neighbor— neighbor state, peer address, DR role, and dead timer.show ip ospf interface brief— participating interfaces, process, area, cost, and state.show ip ospf database— the LSAs held in the local link-state database.show ip route ospf— installed intra-area, inter-area, and external routes.show ip protocols— process settings, router ID, networks, filters, and passive interfaces.
Capture output from both ends of a link before resetting the process. A missing neighbor, a neighbor stuck in ExStart, a missing LSA, and a route rejected by policy require different fixes.
Production safety notes
OSPF process resets and broad debug commands can interrupt routing or increase CPU. Prefer show commands, logs, and a limited packet capture. Confirm the maintenance impact before changing router IDs, area types, authentication, summarization, or interface network types because those changes can rebuild adjacencies or alter reachability.
These labs explain protocol behavior, but a production design also needs redundancy, capacity planning, security controls, monitoring, configuration backups, and vendor-specific validation.