Cisco 200-301: Dynamic Routing and IP Connectivity — Study Guide

By Laurynas Brazys · 14 August 2026 · #cisco #200-301 #certification #exam-prep #study-guide

Part of the Cisco CCNA 200-301 — Study Guide. Practice with verified answers in the Cisco exam hub, or take timed practice tests on ExamRoll.io.

Overview

Dynamic routing enables routers to exchange reachability information automatically so the network converges when links or devices change. The control plane runs routing protocols to build the Routing Information Base (RIB), while the data plane forwards packets by comparing the destination IP to the Forwarding Information Base (FIB/CEF). Interior Gateway Protocols (IGPs) such as OSPF, EIGRP, and IS-IS operate within a single administrative domain (an autonomous system), prioritizing fast convergence and simplicity. Exterior Gateway Protocols (EGPs) such as BGP interconnect autonomous systems, prioritizing policy and scalability over speed. A sound IP connectivity design aligns IGP domains with addressing hierarchy, uses summarization to contain failure scope, and couples first-hop gateway redundancy with consistent routing so endpoints always have a working default gateway and the network has a viable return path.

OSPF Fundamentals: Neighbor Formation, Areas, LSAs, DR/BDR, Costs

OSPFv2 (IPv4) and OSPFv3 (IPv6) are link-state IGPs: each router floods Link-State Advertisements (LSAs), builds a consistent link-state database (LSDB), and runs SPF to compute loop-free paths.

Neighbor formation

• Hellos discover neighbors and maintain adjacencies. Key parameters must match: Area ID, network type, Hello/Dead timers, authentication, and for OSPFv2 the subnet mask; for OSPFv3, link-local adjacency uses interface scope and no mask field.
• Routers progress through states: Down, Init, 2-Way, ExStart, Exchange, Loading, Full. On broadcast/NBMA segments, most neighbors remain 2-Way unless elected DR/BDR or forming a full adjacency with the DR/BDR.

Areas and LSAs

• Area 0 is the backbone; all other areas must connect to it, typically via Area Border Routers (ABRs).
• Common LSA types in OSPFv2: 1 Router, 2 Network (from DR), 3 Summary (ABR), 4 ASBR Summary, 5 External, 7 NSSA External (translated to 5 by ABR). OSPFv3 reworks formats but retains the roles.
• Design intent: keep areas topologically stable and summarizable to reduce SPF churn and LSDB size.

DR/BDR on multiaccess networks

• On broadcast and NBMA networks, OSPF elects a Designated Router (DR) and Backup DR to reduce adjacency count and LSA flooding. Election is based on OSPF interface priority (0 prevents election) then highest Router ID. Elections are non-preemptive; a better router joining later does not take over automatically.

Costs and reference bandwidth

• OSPF path cost is the sum of interface costs. Default cost = reference-bandwidth (100 Mbps by default) divided by interface bandwidth (in Mbps), truncated. Modern links require increasing the reference bandwidth to avoid identical costs on fast interfaces, for example: router ospf 10 auto-cost reference-bandwidth 100000

Network types

• Broadcast (Ethernet): DR/BDR used; Hellos multicast to 224.0.0.5/6 (FF02::5/6 for v3).
• Point-to-point: no DR/BDR; simplified adjacency.
• NBMA: Frame Relay/ATM; manual neighbor configuration often required; DR/BDR used.
• Point-to-multipoint: neighbor discovery per spoke; no DR/BDR; useful to avoid NBMA pitfalls.

Common adjacency failures

• Area ID or authentication mismatch, Hello/Dead timer mismatch, MTU mismatch (ExStart/Exchange stuck), duplicate Router IDs, subnet/mask mismatch (v2), network type mismatch, unicast neighbor misconfiguration on NBMA, and ACLs blocking 89/OSPF or multicast.

Single-Area OSPF Configuration and Verification

IPv4 OSPFv2 example (single area 0)

• Interfaces with correct IP addressing and masks.
• Process configuration and interface selection: router ospf 10 router-id 1.1.1.1 passive-interface default no passive-interface GigabitEthernet0/0 network 10.1.0.0 0.0.0.255 area 0
• Optional interface tuning: interface GigabitEthernet0/0 ip ospf cost 10 ip ospf network point-to-point
• Verification: show ip ospf neighbor show ip ospf interface GigabitEthernet0/0 show ip ospf database show ip route ospf show ip protocols

IPv6 OSPFv3 example (single area 0) ipv6 unicast-routing ipv6 router ospf 10 router-id 2.2.2.2 interface GigabitEthernet0/0 ipv6 address 2001:db8:10:1::1/64 ipv6 ospf 10 area 0

Operational reasoning

• Passive interfaces advertise connected prefixes without forming adjacencies, reducing unnecessary Hellos and attack surface on access networks.
• Setting the router ID explicitly prevents instability during interface flaps.
• Aligning network statements or interface OSPF commands with summarizable boundaries reduces LSDB size.

Route Selection, Loop Prevention, Summarization, ECMP, Unequal Paths, and FHRP

Route selection order

• Longest prefix match first.
• If multiple routes match equally, prefer the one with the lowest administrative distance (AD). Typical defaults: connected 0, static 1, eBGP 20, EIGRP 90, OSPF 110, IS-IS 115, RIP 120, iBGP 200.
• If AD ties, prefer the lowest metric per protocol.

Static and floating static routes

• Standard static uses default AD 1: ip route 0.0.0.0 0.0.0.0 192.0.2.1
• Floating static provides backup to a dynamic route by raising AD: ip route 0.0.0.0 0.0.0.0 198.51.100.1 250

Loop prevention

• Link-state protocols compute loop-free trees via SPF; LSA aging and sequence numbers flush stale data.
• Distance-vector protocols rely on split horizon, route poisoning, and holddowns.
• Redistribution between protocols can create loops; use route tags, careful directionality, and summarization to bound feedback.
• Micro-loops during convergence can occur; summarization and hierarchical design reduce blast radius.

Summarization principles

• Summarize at area boundaries (ABRs) and ASBRs to minimize SPF scope and LSA count. Inject a matching static to Null0 for each summary to avoid attracting unknown more-specifics and blackholing traffic when specifics vanish.
• Trade-offs: Summarization may hide alternate equal-cost exit paths and can cause suboptimal routing.

ECMP and unequal paths

• Equal-Cost Multi-Path (ECMP) installs multiple next-hops for the same prefix when metrics tie. CEF uses per-flow hashing by default to avoid reordering. OSPF typically supports up to 4 or 16 equal paths; configurable with maximum-paths.
• Unequal-cost load sharing is a design feature of EIGRP (variance). Use cautiously; unequal paths can increase jitter and complicate troubleshooting.
• Avoid per-packet load sharing for most applications; per-destination/per-flow is safer.

FHRP and routing interaction

• HSRP, VRRP, and GLBP provide default gateway redundancy on LANs. Ensure the active gateway has a valid upstream route; otherwise devices send traffic to a gateway with no exit.
• Track upstream health to influence FHRP: interface Vlan10 standby 10 ip 192.0.2.1 standby 10 priority 110 standby 10 preempt standby 10 track GigabitEthernet0/1 decrement 30
• If dynamic routing runs on the SVIs, align OSPF costs and FHRP priorities to prevent asymmetric return paths and unnecessary traffic hairpinning.

Troubleshooting the Routing Control Plane and End-to-End Reachability

Systematic approach

• Physical and link-layer: interfaces up/up, speed/duplex, errors, and VLAN assignments.
• IP layer: addressing and masks, ARP/ND entries for local peers, default gateway on hosts.
• Control plane: confirm protocol enablement, neighbor adjacencies, timers, and LSDB consistency.

Key tools and commands

• End-to-end testing:
  • ping: quick reachability test; use extended ping to set source interface/address, size, DF bit, and repeat count to expose MTU or asymmetry issues.
  • traceroute: identifies path and where TTL expires; helps distinguish forward-path vs return-path issues.
• Route inspection:
  • show ip route / show ipv6 route to confirm longest prefix match and next-hop.
  • show ip cef exact-route src dst to validate FIB lookup on IOS.
• OSPF health:
  • show ip ospf neighbor detail for state, dead timer, DR/BDR roles.
  • show ip ospf interface for network type, cost, timers, MTU.
  • show ip ospf database for LSA presence/age.
  • debug ip ospf adj and events (use sparingly in maintenance windows).
• Policy and filters:
  • show ip protocols to see passive interfaces, networks, redistribution, and distance.
  • Inspect ACLs, control-plane policing, and infrastructure ACLs that might block OSPF (IP proto 89) or BGP (TCP/179).
• Typical failure modes:
  • OSPF ExStart/Exchange stuck (MTU/auth mismatch).
  • Routes present in RIB but traffic dropped due to missing ARP/ND, CEF punt, or ACL.
  • Default gateway reachable but no default route in the core; or default present but blackholed due to upstream failure and no tracking/floating static.

Operational trade-offs

• Faster convergence often increases control-plane churn; summarization and area design strike a balance.
• ECMP improves throughput and resiliency but complicates deterministic troubleshooting; standardize hashing algorithms and monitor path symmetry.

Practical Problem Scenario

Northwind Textiles is migrating from static routes to OSPF in a two-site topology connected by dual WAN links. Users intermittently lose access to an ERP server at HQ during WAN failovers, and helpdesk sees inconsistent traceroutes.

1. Establish a clean single-area OSPF design

• Configure area 0 across HQ and Branch on both WAN links. Assign loopback router IDs explicitly.
• Rationale: A single backbone area simplifies convergence and avoids ABR complexity during migration. Stable router IDs prevent unnecessary SPF recalculations upon interface changes.

2. Normalize interface costs and reference bandwidth

• Set auto-cost reference-bandwidth 10000 and tune per-interface ip ospf cost so the primary WAN has lower cost than the backup.
• Rationale: Explicit cost modeling ensures deterministic primary/backup selection and avoids equal-cost ambiguity due to the outdated 100 Mbps default reference.

3. Enable ECMP only if both links are truly equal

• If links are equal, configure maximum-paths 2 and confirm identical end-to-end metrics. Otherwise, keep a single best path.
• Rationale: ECMP can improve throughput but may cause asymmetric flows and confusing traceroutes when paths are not equivalent.

4. Deploy HSRP with upstream tracking on HQ user VLANs

• Configure HSRP with preempt and track the WAN-facing interface; decrease priority on WAN failure.
• Rationale: Hosts keep a stable default gateway IP, but HSRP moves the active role to the distribution switch with a working WAN, preventing blackholes when the preferred exit fails.

5. Implement a floating static default as a safety net

• On the Branch, add ip route 0.0.0.0 0.0.0.0 BackupNextHop 250.
• Rationale: If OSPF adjacencies drop entirely, the Branch still has a last-resort path to the ISP CE, restoring basic reachability while routing recovers.

6. Validate and monitor the control plane

• Verify neighbors and LSDB with show ip ospf neighbor and show ip ospf database; confirm route selection with show ip route and CEF lookups. Run extended ping with a sourced address from the Branch LAN and traceroute to the ERP server. Enable logging for OSPF adjacency events and track Hello/Dead timers.
• Rationale: Source-specific tests prove both forward and return paths. Monitoring adjacency flaps pinpoints unstable links or mismatched timers that could trigger failover.

7. Summarize Branch routes toward HQ

• Advertise a summary for Branch user subnets at the Branch edge and install a Null0 static for the summary.
• Rationale: Reduces LSDB size and SPF impact during access-layer churn and prevents loops if a more-specific route disappears.

This stepwise plan aligns gateway redundancy with dynamic routing policy, removes ambiguous path selection, and provides deterministic failover with clear troubleshooting signals.

← IPv6 Addressing and IPv6 Routing · All domains · IP Services →

Practice these questions → · Timed practice on ExamRoll.io →