Cisco Certified Network Associate (CCNA) 200-301 · Free study guide

IP connectivity: deterministic route selection

Routing feels complex when several decisions are blended together. A router first needs candidate routes in its table. It then chooses the most specific matching prefix for the destination. Administrative distance decides between different sources offering the same prefix, while a protocol's metric decides among that protocol's paths. Keeping these stages separate removes many common errors.

Read every field in a routing entry

A route source code identifies how the route entered the table: connected, local, static, or a dynamic protocol such as OSPF. The prefix and mask define which destinations match. The next hop identifies the neighbor used to continue the path, and an exit interface may also be shown. Bracketed values often include administrative distance and metric. A gateway of last resort points to default behavior when no more-specific route matches.

Connected and local routes appear from active addressed interfaces. A connected prefix covers the attached network; a local host route represents the device's own interface address. Do not confuse either with a learned remote route.

Apply longest-prefix match first

Suppose a table contains 0.0.0.0/0, 10.0.0.0/8, 10.24.0.0/16, and 10.24.7.0/24. A packet for 10.24.7.90 uses the /24 because it fixes the most leading bits, even if another route has a lower administrative distance. Distance does not let a less-specific route defeat a more-specific match.

Administrative distance matters when routes from different sources describe the same prefix length and network. A protocol metric compares paths within the same routing process. The winning next hop may itself require a route lookup; that recursive resolution must reach a connected path before forwarding works.

Design static routes by purpose

A default route summarizes every destination not otherwise known. A network route covers a prefix. A host route names one IPv4 or IPv6 address with the full host prefix. A floating static uses a higher administrative distance so a more preferred route wins while healthy, leaving the static as a backup.

Choose next-hop, exit-interface, or fully specified syntax according to media and platform behavior. Then verify the route entered the table and that its next hop resolves. A syntactically accepted route can remain unusable if the exit path is down or recursion fails.

IPv4 and IPv6 share these purposes but not command spelling or address format. Do not translate an IPv4 dotted mask into an IPv6 configuration. Use explicit prefix lengths and test the intended family.

Form OSPFv2 neighbors from prerequisites

Single-area OSPFv2 exchanges IPv4 reachability after neighbors agree on required parameters and can communicate on the link. Area, timers, network type, and subnet compatibility are common checks. Router IDs must be unique and stable enough for operations. They identify routers inside OSPF; they do not need to be routable interface addresses, though operators often choose deliberate values.

On a point-to-point network, there is no need to elect a designated router for the two-node segment. Broadcast networks elect a DR and BDR to reduce adjacency and flooding complexity. Election is not simply highest interface address in all cases; priority and router ID participate, and the process is not generally preemptive after roles settle.

Verify neighbors before routes. A full adjacency with no expected prefix points toward advertisement or filtering rather than basic neighbor formation. A missing adjacency means route-table troubleshooting is premature.

Understand first-hop redundancy from the host's view

Hosts usually know one default-gateway address. First-hop redundancy lets multiple routers cooperate behind a virtual IP and virtual MAC so a role change does not require host reconfiguration. One device forwards for the virtual gateway while another can take over. The protocol maintains state and detects loss according to its rules.

This protects the first routed hop, not the entire path. Upstream routing, switching, and service dependencies still require resilience. Confirm virtual state and also test whether the active device has a usable onward path.

Work a forwarding scenario end to end

A host sends to a remote prefix, so it frames the packet toward its default gateway. The gateway removes the incoming Layer 2 header, looks up the destination IP, chooses the longest prefix, resolves the next hop, decrements the packet's hop field, and builds a new Layer 2 header for the outgoing segment. Each router repeats that process. Ethernet MAC addresses are local to each segment; the IP destination guides the routed path.

If the final network exists but the return path does not, a one-way capture can mislead. Test both directions and include security policy, translation, and host firewalls where they apply.

Use a disciplined verification stack

Start with interface state and addressing. Read connected and local routes. Check static next-hop resolution or OSPF neighbor state. Inspect the exact destination lookup rather than the whole table. Test incrementally with ping or trace tools where policy permits, and compare control-plane belief to actual forwarding evidence.

Never use a successful ping as universal proof. It validates one protocol flow between two addresses at one moment. The routing model tells you what should happen; multiple independent observations tell you whether it did.