Why multi-area OSPF
A single OSPF area works for small networks but does not scale. This chapter explains why areas exist and how a backbone ties them together.
Analogy: a country divided into states
Each state keeps its own detailed map, while the country shares only summaries between states. This keeps maps small.
- Every router in an area holds the same link-state database, so a large area means a large database and heavy calculation.
- Areas limit the spread of detailed topology and hide changes inside an area from the rest.
- Area zero is the backbone; every other area must connect to it.
- Area border routers sit between areas and pass summary information.
- Good design keeps areas small enough for stable calculation and aligned with geography or function.
Areas meet at the backbone.
A company with twelve sites puts each region in its own area. A link flap in one region no longer forces every router in the company to recalculate.
Common mistake: putting the whole network in one area because it works today. Growth then forces a painful redesign.
Everything recalculates
One flapping link makes every router busy.
Lesson: split the network into areas and summarise at borders.
Why use more than one area?
To keep databases small and contain the effect of topology changes.
Key takeaways
- Same database per area.
- Backbone is area zero.
- Area border routers.
- Smaller calculations.
- Design by region.