OSPF Passive Interface: When to Use and Configure it?
In the dynamic landscape of networking, optimizing routing protocols is crucial to ensure efficient data flow. Open Shortest…
An ABR (Area Border Router) is an OSPF router that has interfaces in two or more OSPF areas — at least one of which must be Area 0 (the backbone). ABRs maintain a separate LSDB for each area they belong to and generate Type 3 LSAs (Summary LSAs) to advertise routes between areas. ABRs are the key to inter-area route summarization in OSPF.
Key takeaways
- ABR = router with interfaces in Area 0 AND at least one non-backbone OSPF area
- ABRs maintain a separate LSDB (Link State Database) for each area they participate in
- ABRs generate LSA Type 3 (Summary LSA) to advertise routes from one area to others
- Route summarization must be configured manually on ABRs — OSPF does not auto-summarize
- ABR summarization command: area {area-id} range {prefix} {mask}
- ABRs are different from ASBRs — ASBR redistributes external routes into OSPF (LSA Type 5)
- One ABR can connect to multiple non-backbone areas simultaneously
An Area Border Router (ABR) is an OSPF router with interfaces in two or more areas, one of which must be the backbone, area 0. It is the boundary between areas and the only device that can pass routing information across one.
OSPF’s scaling design depends on it. Within an area, every router holds an identical link-state database and reruns SPF on any change. Areas contain that: a topology change inside area 10 does not force area 20’s routers to recalculate, because they never had area 10’s topology to begin with.
What an ABR Does
- Maintains a separate LSDB per area. An ABR connected to areas 0, 10 and 20 holds three distinct databases and runs SPF separately for each.
- Generates Type 3 Summary LSAs. It takes the routes it learned inside one area and re-advertises them into the others as network reachability, without the topology detail. This is the mechanism that hides topology between areas.
- Is the only place inter-area summarisation can happen. Unlike EIGRP, which summarises on any interface, OSPF summarises at area boundaries only.
- Injects default routes into stub areas. A stub area’s routers reach external destinations via a default route the ABR originates.
- Filters between areas, if configured, using area filter-lists.
The Golden Rule
Every area must connect to area 0. All inter-area traffic passes through the backbone, area 10 cannot reach area 20 directly even if an ABR touches both, because OSPF’s inter-area routing is strictly hub-and-spoke through the backbone.
The design consequences:
- Area 0 must be contiguous. A partitioned backbone splits the OSPF domain.
- An area physically separated from area 0 needs a virtual link across an intervening area, a workaround, not a design, and one that should be removed as soon as the topology allows.
! Virtual link across area 10, between two ABRs' router IDs
ABR1(config-router)# area 10 virtual-link 3.3.3.3
ABR2(config-router)# area 10 virtual-link 1.1.1.1OSPF Router Roles
| Role | Definition | Generates |
|---|---|---|
| Internal router | All interfaces in one area | Type 1, Type 2 |
| Backbone router | At least one interface in area 0 | Type 1, Type 2 |
| ABR | Interfaces in two or more areas, including area 0 | Type 3, Type 4 |
| ASBR | Redistributes routes from outside OSPF | Type 5, Type 7 in an NSSA |
One router can hold several roles at once, an ABR that also redistributes static routes is both ABR and ASBR.
LSA Types an ABR Handles
| Type | Name | Originated by | Flooded within |
|---|---|---|---|
| 1 | Router LSA | Every router | Its own area only |
| 2 | Network LSA | The DR on a multi-access segment | Its own area only |
| 3 | Summary LSA | ABR | Other areas, carries prefixes, not topology |
| 4 | ASBR Summary | ABR | Tells other areas how to reach the ASBR |
| 5 | External LSA | ASBR | The whole domain, except stub areas |
| 7 | NSSA External | ASBR in an NSSA | The NSSA only; the ABR translates it to Type 5 |
Type 3 is the important one to understand. It says “network 10.20.0.0/16 is reachable through me, at this cost”, with no information about the links or routers inside the originating area. That is exactly why a flapping link in area 10 does not trigger SPF runs in area 20: the Type 3 LSA does not change unless reachability itself changes.
Inter-Area Summarisation
Summarising at the ABR is the single most effective OSPF scaling measure. It reduces the number of Type 3 LSAs, shrinks routing tables elsewhere, and, critically, hides instability, because a single component network flapping does not change the summary.
ABR(config)# router ospf 1
ABR(config-router)# area 10 range 10.10.0.0 255.255.0.0This replaces every 10.10.x.x route from area 10 with one advertisement into the other areas. The area X range command applies to the area the routes came from.
Two things worth knowing:
- The summary’s cost defaults to the lowest cost among its components (or the highest, depending on RFC compliance mode). Set it explicitly with
costif you need deterministic behaviour. - The ABR installs a Null0 route for the summary, so traffic to a non-existent component within the range is discarded rather than looped.
Summarisation only works if addressing is contiguous per area. This is why OSPF designs allocate address blocks per area up front, retrofitting summarisation onto a scattered address plan is not possible.
Filtering between areas
ABR(config)# ip prefix-list NO-LAB deny 10.99.0.0/16 le 32
ABR(config)# ip prefix-list NO-LAB permit 0.0.0.0/0 le 32
ABR(config-router)# area 10 filter-list prefix NO-LAB inStub Areas and the ABR’s Role
| Area type | Type 3 allowed | Type 5 allowed | Type 7 allowed | ABR injects default |
|---|---|---|---|---|
| Standard | Yes | Yes | No | No |
| Stub | Yes | No | No | Yes |
| Totally stubby | No | No | No | Yes |
| NSSA | Yes | No | Yes | Optional |
| Totally NSSA | No | No | Yes | Yes |
! On every router in the area
Router(config-router)# area 10 stub
! On the ABR only, for totally stubby
ABR(config-router)# area 10 stub no-summary
! NSSA, allows an ASBR inside the stub area
ABR(config-router)# area 10 nssa
ABR(config-router)# area 10 nssa default-information-originateThe stub flag must match on every router in the area or adjacencies will not form. Only the no-summary keyword is ABR-only.
Totally stubby is the practical choice for branch sites: routers there hold their own area’s routes plus a single default. Routing tables stay tiny and SPF runs stay cheap.
Verification
Router# show ip ospf
Router# show ip ospf border-routers
Router# show ip ospf database summary
Router# show ip route ospfshow ip ospf states plainly whether the router is an ABR and how many areas it is attached to. In the routing table, inter-area routes are marked O IA.
Design Guidance
- Keep ABRs to two or three areas. Each area means another LSDB and another SPF process. An ABR in eight areas is doing eight times the work.
- Deploy ABRs in pairs for redundancy, a single ABR isolates its area when it fails.
- Allocate contiguous address blocks per area so summarisation is possible. Decide this before deployment.
- Always summarise at the ABR. It is the main reason areas exist.
- Make branch areas totally stubby unless something there needs full routing information.
- Treat virtual links as temporary. They add complexity and fail in ways that are hard to diagnose.
- Set router IDs explicitly on ABRs, a changing router ID restarts OSPF and drops every adjacency.
Frequently Asked Questions
What makes a router an ABR?
Having interfaces in two or more OSPF areas, one of which is area 0. A router connecting area 10 and area 20 without touching the backbone is not a valid ABR and inter-area routing will not work through it.
Can an ABR also be an ASBR?
Yes. If it redistributes routes from another protocol or from static routes into OSPF, it is both. This is common at a site’s edge router.
Where can OSPF summarise routes?
Only at an ABR (with area X range, for inter-area routes) or an ASBR (with summary-address, for external routes). Unlike EIGRP, OSPF cannot summarise on an arbitrary interface.
Why must every area touch area 0?
To prevent inter-area routing loops. OSPF’s distance-vector-like behaviour between areas has no loop-detection mechanism, so the design mandates a strict hub-and-spoke through the backbone.
What is a virtual link?
A logical tunnel through a transit area that connects a disconnected area to area 0. It works, but it is a repair for a broken topology and should be replaced with a real backbone connection where possible.
How many areas can one ABR handle?
There is no protocol limit, but each area costs memory for an LSDB and CPU for its own SPF runs. Two or three is normal design practice; more than that concentrates too much work in one device. See the routing protocols guide for broader context.
