VMware ESXi and vSphere Cluster Management

OSPF Route Summarization

Learn how OSPF route summarization works, where ABR and ASBR summaries are configured, how to calculate aggregate prefixes, and how to verify results.

OSPF route summarization combines multiple more-specific network prefixes into one less-specific aggregate prefix. Instead of advertising several individual routes to another area, an OSPF router can advertise one route that represents them.

This lesson covers inter-area summarization on an Area Border Router (ABR) and external-route summarization on an Autonomous System Boundary Router (ASBR).

Why Use OSPF Route Summarization?

Suppose an area contains many contiguous networks such as 10.0.0.0/24, 10.0.1.0/24, and 10.0.2.0/24. A summary can advertise one aggregate instead of every individual prefix, provided the aggregate accurately represents the intended networks.

• Fewer routing-table entries: Routers in other areas can store one aggregate instead of multiple component routes.
• Reduced LSA flooding scope: A summary LSA represents reachability across an area boundary, so changes to every component prefix do not need to be represented individually in other areas.
• Less SPF-related work: Fewer advertised prefixes can reduce routing-table memory use and the amount of route information routers process.
• More stable external information: Component-route changes can be hidden from routers that receive only the aggregate.

Summarization changes the reachability information advertised outside the source area. It does not erase the component routes from the originating area's topology database. Routers inside that area still maintain and use the individual topology information.

Important OSPF Terms

• OSPF: Open Shortest Path First, a link-state interior gateway protocol.
• Route summarization: Advertising one aggregate route in place of multiple more-specific routes.
• ABR: An Area Border Router connects multiple OSPF areas. It can originate inter-area summaries.
• ASBR: An Autonomous System Boundary Router injects external routes into OSPF through redistribution.
• Inter-area route: A route learned from another OSPF area. Cisco IOS commonly displays it as O IA.
• External route: A route introduced through redistribution. Cisco IOS commonly displays it as O E1 or O E2.
• LSA: A Link-State Advertisement used to distribute OSPF topology and reachability information.
• Summary LSA: An inter-area advertisement generated by an ABR to describe networks in another area.
• Aggregate prefix: The network address and prefix length representing a group of contiguous subnets.
• CIDR: Classless Inter-Domain Routing notation, such as /23, for expressing a prefix length.
• Null route: A discard route that may be used in some summarization designs to prevent loops or unintended forwarding. Its need and behavior must be validated for the platform and design.

OSPF Summarization Versus EIGRP Summarization

OSPF does not perform automatic route summarization. An administrator must explicitly configure a summary at an appropriate OSPF boundary.

OSPF summaries are not configured freely on every OSPF router. An internal router cannot summarize arbitrary routes on behalf of unrelated areas. The summary must be configured according to the router's OSPF role:

• An ABR summarizes intra-area routes when advertising them into other areas.
• An ASBR summarizes redistributed external routes before advertising them into OSPF.

This differs from the way EIGRP summarization is commonly configured, where an EIGRP interface can be used as a summarization point for routes sent out that interface. Do not apply that model to OSPF area boundaries.

Where OSPF Route Summarization Is Configured

ABR Inter-Area Summarization

An ABR has interfaces in at least two OSPF areas. It can summarize routes that exist in one attached area and advertise the aggregate into the other attached areas.

The area ID in the command identifies the source area containing the component routes. The command is applied under the OSPF routing process on the ABR.

router ospf 1
 area AREA_ID range NETWORK_ADDRESS SUBNET_MASK

For example:

router ospf 1
 area 0 range 10.0.0.0 255.255.254.0

This command summarizes routes from area 0 into the other area or areas attached to the ABR. The mask 255.255.254.0 is /23.

ASBR External-Route Summarization

An ASBR redistributes routes from another routing source, such as static routes or another routing protocol, into OSPF. These routes are external to the OSPF domain or process.

External routes are summarized with the ASBR command below, not with the ABR area range command:

router ospf 1
 summary-address 172.16.0.0 255.255.252.0

The two mechanisms are distinct: area range summarizes routes learned within an OSPF area, while summary-address summarizes routes redistributed by an ASBR.

Calculating an Aggregate Prefix

A correct summary must cover the intended networks and align with a valid CIDR boundary. The process is:

1. List the component networks.
2. Confirm that they are contiguous or otherwise fit exactly within the intended aggregate.
3. Compare their binary network bits to find the common prefix length.
4. Convert that common prefix length into the aggregate network address and subnet mask.
5. Check the complete address range covered by the aggregate.

Two Adjacent /24 Networks

Consider these networks:

• 10.0.0.0/24: addresses from 10.0.0.0 through 10.0.0.255
• 10.0.1.0/24: addresses from 10.0.1.0 through 10.0.1.255

The networks share the first 23 bits and differ only in the final bit of the third octet. Therefore, they combine precisely into 10.0.0.0/23, with mask 255.255.254.0. The resulting range is exactly 10.0.0.0 through 10.0.1.255.

Alignment matters. A /23 beginning at 10.0.1.0 would not be a valid aligned representation of these two /24 networks. For a /23, the third-octet network values occur in blocks of two: 0, 2, 4, and so on.

Worked Multi-Area OSPF Example

Use this three-router topology:

• R1: In area 0, with 10.0.0.0/24 and 10.0.1.0/24 behind it.
• R2: The ABR, with one side in area 0 and the other side in area 1.
• R3: A remote router in area 1.

R1 learns the two component networks within the source area. R2, as the ABR, advertises them toward area 1. Before summarization, R3 can learn two separate inter-area routes.

Configure the ABR

On R2, enter OSPF router configuration mode and identify area 0 as the source area:

R2# configure terminal
R2(config)# router ospf 1
R2(config-router)# area 0 range 10.0.0.0 255.255.254.0

After the summary is advertised into area 1, R3 should learn:

R3# show ip route ospf
O IA 10.0.0.0/23 [110/...] via <R2-next-hop>

The exact administrative distance, metric, next hop, and interface depend on the topology and platform output. The important change is that the two /24 entries are represented by one O IA /23 entry on R3.

Traffic for 10.0.0.0/24 and 10.0.1.0/24 still travels toward R2. R2 retains reachability to the individual component networks and forwards traffic toward the correct destination. Summarization changes what R3 knows about the prefixes; it does not merge the actual destination networks into one physical subnet.

Risks and Design Considerations

Broad Summaries Can Advertise Unused Addresses

An aggregate announces reachability for every address covered by its prefix. A 10.0.0.0/16 summary therefore claims reachability for all addresses from 10.0.0.0 through 10.0.255.255, even if only two /24 networks exist.

A remote router may send traffic for an unused covered subnet to the ABR. If the ABR has no valid path for that destination, the traffic can be dropped or become a traffic sink. This is a potential blackholing problem.

• Use the most specific aggregate that accurately represents the intended reachable networks.
• Plan contiguous address blocks before assigning subnets.
• Verify the full range represented by every summary.
• Understand that a summary can hide component-route failures from routers that receive only the aggregate.
• Consider whether a platform-generated or manually configured null route is needed to prevent unintended forwarding or loops; validate the design separately.

Address Planning for Summarization

Summarization is easiest when related networks are allocated from one aligned block. For example, assigning adjacent /24 networks inside an aligned /23 or /22 makes an accurate aggregate possible. Scattered addressing can force a broader summary or prevent exact summarization entirely.

Verification Commands

Verify both the advertisement seen by another-area routers and the ABR's internal reachability to the component networks.

Check the Receiving Router

R3# show ip route ospf

Before summarization, look for separate O IA entries for 10.0.0.0/24 and 10.0.1.0/24. After summarization, look for one O IA 10.0.0.0/23 entry. Confirm that the component prefixes are no longer learned as distinct inter-area routes where the summary is received.

Inspect OSPF Summary Information

R2# show ip ospf database summary

Use the summary database output to inspect inter-area summary advertisements. Output details vary by platform and software version.

Confirm Area Placement and Adjacencies

R2# show ip ospf neighbor
R2# show ip ospf interface brief

These commands help confirm that the summarizing router has interfaces in the expected areas and has working OSPF neighbor adjacencies. An ordinary internal router cannot perform an ABR summary merely because the command is present in its configuration.

Verify the ABR's Component Routes

R2# show ip route 10.0.0.0
R2# show ip route 10.0.1.0

R2 must still have routes to the individual component networks. If those routes are absent in the source area, the summary cannot provide useful end-to-end reachability.

Troubleshooting

Separate Routes Still Appear on the Remote Router

• Confirm that the command was applied to the ABR, not an internal router.
• Check that the area ID is the area containing the component routes.
• Verify that the aggregate network address and mask cover the intended routes.
• Inspect the ABR's source-area routing table to ensure the component routes are actually learned.
• Confirm that the remote router receives routes through the expected ABR.
• Review the running OSPF configuration and the summary LSA database.

Traffic to Some Addresses in the Summary Fails

• Compare the aggregate's complete address range with the networks that really exist.
• Test an address in an existing component subnet and another address in an unintended covered subnet.
• Check whether a component subnet is down, absent, or no longer advertised internally.
• Verify that the ABR has a route to the actual destination.
• Replace an overly broad summary with a precise, correctly aligned prefix.

An External-Route Summary Does Not Appear

• Verify that the routes were redistributed into OSPF.
• Confirm that the ASBR's summary-address matches the redistributed prefixes.
• Ensure that summary-address, rather than area range, is being used for external routes.
• Check receiving routers for O E1 or O E2 entries.
• Confirm that the summarizing router is functioning as an ASBR.

Exam-Ready Summary

• OSPF has no automatic route summarization.
• An ABR uses area AREA_ID range NETWORK_ADDRESS SUBNET_MASK for intra-area routes advertised into other areas.
• The area ID in area range is the source area containing the component routes.
• An ASBR uses summary-address NETWORK_ADDRESS SUBNET_MASK for redistributed external routes.
• O IA normally identifies an inter-area route; O E1 and O E2 identify external routes.
• A summary reduces advertised route information outside the source area but does not remove component routes from the originating area's topology database.
• Always check aggregate alignment and the complete covered address range.
• A summary that is too broad can advertise nonexistent reachability and cause blackholing.

For related study, review OSPF route summarization alongside multi-area OSPF, ABR and ASBR roles, LSA behavior, route redistribution, and IPv4 CIDR planning.