Link-state protocols describe local links and prefixes, distribute those descriptions through a routing scope, and let each router calculate paths from a topology database. OSPF and IS-IS are common examples.
Routing · Lesson 6
Link State Protocols
Learn how link-state protocols form adjacencies, flood topology information, and calculate paths.
Forming Adjacencies
Routers discover compatible neighbors and form protocol adjacencies according to interface type, area, timers, authentication, and other parameters. Seeing hello packets does not guarantee a full adjacency; mismatched configuration can stop the state machine earlier.
What does receiving an OSPF hello fail to prove?
Flooding Link-State Information
Each router originates advertisements about its relevant state. Neighbors reliably flood newer information through the defined area or domain, rather than keeping updates only between the original neighboring pair. Sequence and aging mechanisms distinguish current information and remove stale state.
Why is link-state information flooded beyond one neighbor?
Calculating Shortest Paths
After building a link-state database, a router runs a shortest-path-first algorithm, commonly Dijkstra's algorithm, from itself as the root. OSPF sums interface costs; policy and equal-cost rules influence which results are installed.
“Shortest” means lowest protocol cost, not necessarily fewest routers or lowest measured application latency. Cost design must reflect operational intent.
What does “shortest” mean in a link-state path calculation?
Areas and Convergence
OSPF areas limit topology flooding and calculation scope, with Area 0 serving as the backbone for normal inter-area design. Summarization and area types can intentionally give different routers different database detail.
After a link change, detection, advertisement flooding, SPF calculation, route installation, and forwarding recovery each take time. Faster convergence than a simple distance-vector design is possible, but not automatic under every failure or configuration.
What should be measured during an OSPF convergence investigation?
Lesson complete
You finished Link State Protocols
You can now follow link-state routing from neighbor discovery to installed paths.
Distinguish hello reception from a full adjacency.
Explain reliable flooding through a routing scope.
Interpret shortest path as lowest configured protocol cost.
Measure every control- and data-plane convergence stage.
Keep your learning progress
Create a free account to save this lesson and continue learning on any device.
Create a free account