OSPF Routing
The link-state interior routing protocol: every router learns the full network map and computes shortest paths — instant convergence math in exchange for design discipline.
What is OSPF?
OSPF (Open Shortest Path First) is the dominant interior gateway protocol in enterprise and data-center networks. Unlike distance-vector protocols that gossip route summaries, OSPF is link-state: every router floods link-state advertisements describing its connections until all routers share an identical topology database, then each independently runs Dijkstra’s shortest-path algorithm over that map. Same map, same math, loop-free consistent forwarding — and convergence after a failure in seconds, driven by recomputation rather than rumor propagation.
Design vocabulary that matters
Areas bound the flooding domain: Area 0 is the backbone, other areas attach to it, and area-border routers summarize between them — the mechanism that keeps thousand-router networks from drowning in LSA churn. Cost is the metric (classically inverse bandwidth); traffic engineering in OSPF means tuning costs. Designated routers on shared segments prevent n² adjacency explosions. The perennial exam-and-reality distinction: OSPF for interior routing where you control both ends; BGP for exterior/policy routing between organizations — clouds run massive BGP fabrics, while OSPF lives on in campus networks, Direct Connect-adjacent enterprise edges, and hybrid designs redistributing between the two.
Where cloud engineers actually meet it
Mostly at the hybrid boundary: your network team’s OSPF domain redistributes into BGP toward AWS/Azure over VPN or Direct Connect. Redistribution is where the bodies are buried — mutual redistribution loops, metric translation surprises, and one bad summary route hijacking a data center.
What people get wrong
- Skipping area design “for now”: a flat Area 0 with hundreds of routers converges slowly and floods constantly; retrofitting areas is surgery.
- Leaving default costs on mixed-speed links — legacy defaults can rate a 10G and 100G path identically without reference-bandwidth tuning.
- Redistributing without filters: OSPF↔BGP redistribution minus route filtering is the classic self-inflicted outage.
Primary source: RFC 2328 — OSPF Version 2
Historical figures and technical concepts for informational purposes only. Not technical, professional, legal, or financial advice. Sources: Official Documentation.