Route Summarization & Aggregation

1. What Is Route Summarization?

Route summarization (also called route aggregation or supernetting) is the process of combining multiple contiguous, specific routes into a single summary route that is then advertised in place of the individual entries. Instead of advertising four /24 networks separately, a router can advertise one /22 that covers all four — reducing the information that neighbouring routers and the entire routing domain must process and store.

Summarization is possible because IP addressing is hierarchical. When subnets share a common high-order bit pattern, a single shorter prefix can represent the entire group. The router performing summarization suppresses the specific routes and advertises only the aggregate — any destination that falls within the summary is reachable via that single entry.

Without Summarization With Summarization
192.168.0.0/24 via 10.0.0.1 192.168.0.0/22 via 10.0.0.1
(one entry replaces four)
192.168.1.0/24 via 10.0.0.1
192.168.2.0/24 via 10.0.0.1
192.168.3.0/24 via 10.0.0.1

Related pages: Wildcard Masks & CIDR | OSPF Overview | EIGRP Overview | EIGRP Configuration | Default Routes | Administrative Distance | Route Summarization Lab

2. Benefits of Route Summarization

Benefit Explanation
Smaller routing tables Routers store and process fewer entries, reducing memory consumption and speeding up longest-prefix-match lookups
Reduced routing protocol traffic Fewer routes are advertised across the network — link-state databases (OSPF) and update packets (EIGRP, RIP) are smaller, consuming less bandwidth
Topology change isolation When a specific subnet within a summary flaps, the summary route itself does not change — remote routers do not trigger a recalculation (SPF in OSPF, DUAL in EIGRP) for a change they cannot see
Faster convergence Smaller link-state databases and distance-vector tables converge faster after a topology change; SPF calculations are less CPU-intensive
Scalability Hierarchical addressing with summarization at area or AS boundaries allows networks to grow without routing table explosion
Cleaner design Forces IP address planning to be hierarchical and contiguous — a network that can be summarised is a network that was designed well
Prerequisite — contiguous addressing: Summarization only works cleanly when the subnets to be summarised are contiguous (numerically adjacent) and share a common higher-order bit pattern. Discontiguous subnets produce a summary that inadvertently covers address space not in use, potentially causing black holes.

3. How to Calculate a Summary Address – Step by Step

The process of finding the correct summary address and prefix length requires converting the network addresses to binary, identifying the common bit prefix, and reading the summary network address and mask from that prefix.

3.1 The Four-Step Method

  Step 1:  Write all network addresses to be summarised in binary
  Step 2:  Align the binary values and find the leftmost bit where they DIFFER
  Step 3:  Count the number of bits that are IDENTICAL from left to right
           — this count is the summary prefix length (the new subnet mask)
  Step 4:  Copy the common bits; set all remaining bits to 0
           — the result is the summary network address

3.2 Worked Example 1 — Four Contiguous /24 Networks

  Networks to summarise:
    192.168.0.0 /24
    192.168.1.0 /24
    192.168.2.0 /24
    192.168.3.0 /24

  Step 1 — Convert third octet to binary (first two octets are identical):
    192.168.  0  .0  →  0 0 0 0 0 0 0 0
    192.168.  1  .0  →  0 0 0 0 0 0 0 1
    192.168.  2  .0  →  0 0 0 0 0 0 1 0
    192.168.  3  .0  →  0 0 0 0 0 0 1 1
                        ─────────────────
  Step 2 — First differing bit is at position 7 from the left (bit 7 of octet 3)
  Step 3 — Matching bits: 16 (first two octets) + 6 (first 6 bits of third octet) = 22
           Summary prefix = /22

  Step 4 — Set differing bits to 0:
    Third octet common bits: 0 0 0 0 0 0 → decimal 0
    Summary address: 192.168.0.0 /22

  Verification — /22 covers:
    Network:           192.168.0.0
    Broadcast:         192.168.3.255
    Range:             192.168.0.0 – 192.168.3.255  ✓ (all four /24s fit inside)

3.3 Worked Example 2 — Eight Contiguous /24 Networks

  Networks to summarise:
    10.0.0.0 /24  through  10.0.7.0 /24   (8 networks)

  Third octet values: 0, 1, 2, 3, 4, 5, 6, 7

  Binary (third octet only):
    0  →  0 0 0 0 0 0 0 0
    1  →  0 0 0 0 0 0 0 1
    2  →  0 0 0 0 0 0 1 0
    3  →  0 0 0 0 0 0 1 1
    4  →  0 0 0 0 0 1 0 0
    5  →  0 0 0 0 0 1 0 1
    6  →  0 0 0 0 0 1 1 0
    7  →  0 0 0 0 0 1 1 1
         ──────────────────
  First differing bit: position 6 from the left (bit 6 of octet 3)
  Matching bits: 16 (first two octets) + 5 (first 5 bits of third octet) = 21
  Summary prefix = /21

  Set differing bits to 0 → third octet = 0 0 0 0 0 0 0 0 = 0
  Summary address: 10.0.0.0 /21

  Verification — /21 covers:
    Network:    10.0.0.0
    Broadcast:  10.0.7.255
    Range:      10.0.0.0 – 10.0.7.255  ✓ (all eight /24s fit)

3.4 Worked Example 3 — Non-Power-of-Two Count (Partial Overlap Warning)

  Networks to summarise:
    172.16.0.0 /24
    172.16.1.0 /24
    172.16.2.0 /24   (only 3 networks — not a power of two)

  Binary (third octet):
    0  →  0 0 0 0 0 0 0 0
    1  →  0 0 0 0 0 0 0 1
    2  →  0 0 0 0 0 0 1 0
         ──────────────────
  First differing bit: position 7 from left
  Matching bits: 16 + 6 = 22  →  Summary = 172.16.0.0 /22

  ⚠ WARNING — The /22 summary covers:
    172.16.0.0 – 172.16.3.255
    But 172.16.3.0/24 does NOT exist in our network!

  If 172.16.3.0/24 is reachable via a DIFFERENT path in the network,
  advertising 172.16.0.0/22 here creates a routing black hole for that subnet.

  Solution: Either extend the address block to include 172.16.3.0/24,
  or summarise only 172.16.0.0/23 (covering .0 and .1) and advertise
  172.16.2.0/24 separately.

3.5 Quick Reference — Block Sizes and Summary Prefixes

Number of /24s to Summarise Prefix Bits Borrowed Summary Prefix Length Example
2 1 /23 10.0.0.0/24 + 10.0.1.0/24 → 10.0.0.0/23
4 2 /22 10.0.0.0–10.0.3.0/24 → 10.0.0.0/22
8 3 /21 10.0.0.0–10.0.7.0/24 → 10.0.0.0/21
16 4 /20 10.0.0.0–10.0.15.0/24 → 10.0.0.0/20
32 5 /19 10.0.0.0–10.0.31.0/24 → 10.0.0.0/19
256 8 /16 10.0.0.0–10.0.255.0/24 → 10.0.0.0/16

4. The Discard Route (Null0)

When a router generates a summary route, it automatically installs a corresponding discard route (also called a null route) pointing to the Null0 interface for the summary prefix. This is a critical safety mechanism.

4.1 Why the Discard Route Exists

  Scenario — without a discard route:

  Router-A summarises 192.168.0.0/22 and advertises it to Router-B.
  A packet arrives at Router-A destined for 192.168.3.50.
  Router-A's routing table has: 192.168.0.0/22 → summary (local)
  But 192.168.3.0/24 does NOT exist — no specific route to it.

  Without discard route:
    Router-A looks up 192.168.3.50 → matches 192.168.0.0/22 (the summary)
    → forwards to itself → looks up again → matches summary → loop!
    Result: routing loop and TTL expiry (count-to-infinity for the packet)

  With the Null0 discard route:
    Router-A has: 192.168.0.0/22 via Null0  (automatically installed)
    Packet for 192.168.3.50 matches 192.168.0.0/22 → forwarded to Null0
    → packet silently dropped (ICMP "Destination Unreachable" sent to source)
    Result: loop prevented — clean discard

4.2 Discard Route in the Routing Table

  Router-A# show ip route
  ...
  O     192.168.0.0/22 is a summary, 00:05:23, Null0   ← discard route
  O     192.168.0.0/24 [110/2] via 10.1.1.2
  O     192.168.1.0/24 [110/2] via 10.1.1.2
  O     192.168.2.0/24 [110/2] via 10.1.1.2
  ...

  The summary via Null0 is always installed with a higher administrative distance
  than the specific routes. When a specific route exists, it wins (longest prefix
  match). The Null0 route only catches packets for the "gap" addresses in the range.
Exam tip: The discard route to Null0 is installed automatically by both OSPF and EIGRP when summarization is configured. It is not a mistake in the routing table — it is intentional loop prevention. Packets destined for addresses within the summary block that have no specific route are dropped at the summarising router.

5. Where to Apply Summarization

Summarization is most effective when applied at boundaries — points in the network where traffic transitions between areas, autonomous systems, or administrative domains. Applying it too early (deep inside an area) can hide topology detail needed for optimal routing; applying it at the boundary keeps specific detail local while presenting a clean summary to the rest of the network.

  Optimal Summarization Points:

  ┌──────────────────────────────────────────────────────────────────┐
  │  OSPF Multi-Area Network                                         │
  │                                                                  │
  │  Area 1           Area 0 (Backbone)        Area 2               │
  │  10.1.0.0/24  ─┐                       ┌─  10.2.0.0/24          │
  │  10.1.1.0/24  ─┤                       ├─  10.2.1.0/24          │
  │  10.1.2.0/24  ─┤  [ABR]────────[ABR]  ├─  10.2.2.0/24          │
  │  10.1.3.0/24  ─┘    ↑                ↑  └─  10.2.3.0/24         │
  │                      │                │                          │
  │            Summarise here          Summarise here               │
  │            10.1.0.0/22             10.2.0.0/22                  │
  │            advertised              advertised                    │
  │            into Area 0             into Area 0                   │
  └──────────────────────────────────────────────────────────────────┘

  EIGRP Autonomous System:
  ┌──────────────────────────────────────────────────────────────────┐
  │  Distribution Router                                             │
  │  (summarises access-layer subnets before advertising to core)   │
  │                                                                  │
  │  Access layer:   192.168.0.0/24, .1.0/24, .2.0/24, .3.0/24     │
  │  Summary sent:   192.168.0.0/22  ─────→  Core routers           │
  └──────────────────────────────────────────────────────────────────┘

6. Summarization in OSPF

In OSPF, summarization can only be performed at specific router roles — it cannot be done on internal routers within an area. The two points where OSPF summarization is configured are the Area Border Router (ABR) for inter-area summarization, and the Autonomous System Boundary Router (ASBR) for external route summarization.

6.1 Inter-Area Summarization — ABR

The area range command is configured on the ABR to summarise specific routes from a non-backbone area before advertising them into Area 0 (or between areas).

  ! ── OSPF Inter-Area Summarization on ABR ──

  ! Scenario: ABR connects Area 1 (10.1.0.0/24 through 10.1.3.0/24) to Area 0

  Router(config)# router ospf 1
  Router(config-router)# area 1 range 10.1.0.0 255.255.252.0
  !                         ↑       ↑           ↑
  !                      Area    Summary IP   Summary Mask (/22)

  ! Result: Instead of advertising four /24 LSAs into Area 0, the ABR
  ! advertises a single Type 3 Summary LSA: 10.1.0.0/22

  ! Optional — suppress the summary (advertise nothing, just drop the specifics):
  Router(config-router)# area 1 range 10.1.0.0 255.255.252.0 not-advertise

  ! Optional — set a specific cost for the summary LSA:
  Router(config-router)# area 1 range 10.1.0.0 255.255.252.0 cost 50

  Verify:
  Router# show ip ospf border-routers
  Router# show ip route ospf
  Router# show ip ospf database summary

6.2 External Route Summarization — ASBR

When OSPF redistributes routes from another routing protocol (e.g., EIGRP or static), the ASBR can summarise those external routes using summary-address before they are flooded as Type 5 (or Type 7) External LSAs across the OSPF domain.

  ! ── OSPF External Summarization on ASBR ──

  Router(config)# router ospf 1
  Router(config-router)# summary-address 172.16.0.0 255.255.240.0
  ! Summarises all redistributed external routes within 172.16.0.0/20

  ! This is used alongside redistribution:
  Router(config-router)# redistribute eigrp 100 subnets

6.3 OSPF Summarization — Key Rules

Rule Detail
Only on ABR or ASBR Internal OSPF routers cannot summarise — only routers that sit on an area boundary
area range — inter-area Summarises Type 1/2 LSAs from a specific area into a Type 3 Summary LSA advertised to other areas
summary-address — external Summarises Type 5 External LSAs generated by redistribution at the ASBR
Discard route installed A route to Null0 for the summary prefix is automatically added to the ABR/ASBR routing table
Specific routes remain locally The specific /24 routes still exist within their own area — summarization only affects what is advertised outside

7. Summarization in EIGRP

EIGRP supports summarization in two forms: manual summarization configured on any interface, and automatic summarization (legacy, classful behaviour). Manual summarization is the preferred and exam-tested method.

7.1 EIGRP Manual Summarization

EIGRP manual summarization is applied per interface using the ip summary-address eigrp command. When configured, the router suppresses the specific routes out that interface and advertises only the summary. The discard route to Null0 is automatically installed.

  ! ── EIGRP Manual Summarization ──

  ! Scenario: Distribution router advertising 192.168.0.0/24 – 192.168.3.0/24
  !           out its Gi0/0 interface toward the core

  Router(config)# interface GigabitEthernet0/0
  Router(config-if)# ip summary-address eigrp 100 192.168.0.0 255.255.252.0
  !                                          ↑        ↑              ↑
  !                                      AS number  Summary IP    Summary Mask

  ! Result:
  ! - Specific routes .0/24, .1/24, .2/24, .3/24 suppressed out Gi0/0
  ! - Single summary 192.168.0.0/22 advertised out Gi0/0
  ! - Null0 discard route added locally for 192.168.0.0/22

  Verify:
  Router# show ip eigrp topology
  Router# show ip route eigrp
  Router# show ip interface GigabitEthernet0/0

7.2 EIGRP Auto-Summary (Legacy — Default Off in Modern IOS)

EIGRP historically performed automatic summarization at classful network boundaries — a behaviour that caused serious routing problems in discontiguous networks. In IOS 15.x and later, auto-summary is disabled by default. It is important to understand it for the exam, but manual summarization is always preferred.

  ! ── Auto-Summary (legacy — understand for exam, disable in production) ──

  ! Check current state:
  Router# show ip protocols
  ! Look for: "Automatic Summarization: disabled" (good) or "enabled" (risky)

  ! Disable auto-summary explicitly (best practice):
  Router(config)# router eigrp 100
  Router(config-router)# no auto-summary

  ! What auto-summary does when enabled:
  ! If a router has 10.1.0.0/24 and 10.1.1.0/24, and the interface
  ! toward the core crosses a classful boundary (e.g., from Class A to Class B),
  ! auto-summary advertises 10.0.0.0/8 (the Class A summary) — hiding
  ! the specific subnets and causing black holes in discontiguous designs.

  ! Manual summary is always more precise and predictable.

7.3 EIGRP vs OSPF Summarization — Key Differences

Aspect EIGRP OSPF
Where configured On any interface (per-interface command) Under the OSPF process on ABR (area range) or ASBR (summary-address)
Which routers can summarise Any EIGRP router Only ABR (inter-area) or ASBR (external)
Command syntax ip summary-address eigrp <AS> <network> <mask> area <id> range <network> <mask>
Auto-summary Exists (legacy, disabled by default in IOS 15+) No equivalent — OSPF is classless by design
Discard route Null0 route installed automatically Null0 route installed automatically
Scope of suppression Specific routes suppressed out the configured interface only Specific LSAs suppressed from being flooded outside the area

8. Summarization Pitfalls and Best Practices

Pitfall What Goes Wrong How to Avoid It
Summary covers unused address space Packets for non-existent subnets within the summary are dropped at the summarising router (Null0) — black hole for valid destinations elsewhere Plan address space so the entire summary block is in use, or advertise the unused portion separately via a more specific route if needed
Discontiguous networks with auto-summary EIGRP auto-summary advertises a classful summary at major network boundaries, hiding specific subnets and causing routing asymmetry or loops Always disable auto-summary with no auto-summary in EIGRP; use manual summarization only
Over-summarization A summary that is too broad (e.g., /16 instead of /22) hides too much topology detail and can mask routing problems Summarise at the most specific level that achieves the desired reduction without covering unrelated address space
Summarizing at the wrong point Summarising inside an OSPF area (on an internal router) is not possible; attempting it has no effect In OSPF, summarization must be on the ABR or ASBR — verify router role with show ip ospf
Forgetting the discard route implication If the Null0 discard route has a lower AD than a default route, traffic to unknown destinations in the summary is dropped rather than forwarded to the default gateway Be aware of the AD of the discard route; use ip route 0.0.0.0 0.0.0.0 with a lower AD than the discard route where needed

See also: Route Summarization & Aggregation Lab | OSPF Multi-Area Lab | EIGRP Configuration Lab | Default Route Redistribution in OSPF | show ip route | show ip protocols

9. Key Terms Quick Reference

Term Definition
Route Summarization Combining multiple specific routes into a single aggregate route advertised in their place; reduces routing table size and protocol overhead
Supernetting Another name for route summarization/aggregation — using a shorter prefix to represent a block of more-specific networks
Summary Address The aggregate network address and prefix length that represents all the specific subnets being summarised
Contiguous Subnets Subnets that are numerically adjacent and share a common bit prefix — the prerequisite for clean summarization
Discard Route (Null0) A route automatically installed by the summarising router for the summary prefix, pointing to Null0 — prevents routing loops for destinations within the summary that have no specific route
ABR (Area Border Router) An OSPF router connected to two or more areas; the only router that can perform inter-area route summarization using area range
ASBR (Autonomous System Boundary Router) An OSPF router that redistributes routes from outside the OSPF domain; can summarise external routes using summary-address
area range The OSPF ABR command to summarise routes from a specific area before advertising them to other areas
ip summary-address eigrp The EIGRP per-interface command to advertise a summary route and suppress more-specific routes out that interface
Auto-Summary Legacy EIGRP behaviour that automatically summarises to classful boundaries; disabled by default in IOS 15.x and later; can cause black holes in discontiguous designs
Black Hole A routing condition where packets are dropped because a summary covers address space for which no specific route exists at the summarising router

10. Route Summarization – Practice Quiz

1. What is the correct summary address for the following four networks? 172.16.8.0/24, 172.16.9.0/24, 172.16.10.0/24, 172.16.11.0/24

Correct answer is C. Convert the third octet to binary: 8 = 00001000, 9 = 00001001, 10 = 00001010, 11 = 00001011. The first six bits (000010) are identical across all four values. The 16 bits of the first two octets (172.16) plus 6 matching bits = prefix length 22. The common bits (000010 + 00) = 00001000 = 8, so the summary network address is 172.16.8.0/22, covering 172.16.8.0 through 172.16.11.255.

2. Why is a discard route to Null0 automatically installed when a router creates a summary route?

Correct answer is B. When a router advertises a summary, it claims reachability for the entire summary block. If a packet arrives destined for an address within the summary that has no specific route locally, the router would match the summary and try to forward — potentially back toward the source and into a loop. The Null0 discard route catches these packets and drops them cleanly with an ICMP unreachable, preventing TTL-expiry loops.

3. In OSPF, which router type is responsible for inter-area route summarization, and which command is used?

Correct answer is A. In OSPF, inter-area summarization can only be performed on the ABR — the router that sits on the boundary between a non-backbone area and Area 0. The command area <id> range is configured under the OSPF routing process and instructs the ABR to generate a single Type 3 Summary LSA for the specified range instead of individual Type 3 LSAs for each specific network. Internal routers have no summarization capability in OSPF.

4. How does EIGRP manual summarization differ from OSPF inter-area summarization in terms of where it is configured?

Correct answer is D. This is a key distinction for the CCNA exam. EIGRP gives every router the ability to summarise on any interface — you enter interface configuration mode and apply ip summary-address eigrp <AS> <network> <mask>. OSPF is more restrictive: summarization is a process-level command (area range) and is limited to routers that are ABRs. Internal OSPF routers simply cannot summarise routes.

5. A network has subnets 10.4.0.0/24 through 10.4.7.0/24 (eight subnets). What is the most efficient summary address?

Correct answer is B. Third octet values 0–7 in binary: 000, 001, 010, 011, 100, 101, 110, 111. The first 5 bits of the third octet are identical (00000). Total matching bits: 16 + 5 = 21. Summary = 10.4.0.0/21. A /22 only covers four /24s (.0–.3); a /20 covers sixteen /24s (.0–.15) — too broad. The /21 is the most efficient (tightest) fit for exactly eight contiguous /24s.

6. What is the main risk of summarising three non-power-of-two subnets (e.g., 10.0.0.0/24, 10.0.1.0/24, 10.0.2.0/24) into a single /22?

Correct answer is C. The binary calculation for three subnets (.0, .1, .2) still yields a /22 summary — but that /22 covers four /24s, including 10.0.3.0/24 which does not exist locally. If 10.0.3.0/24 is reachable elsewhere and another router forwards traffic for it to the summarising router, that router's Null0 discard route drops the packet — a black hole. Always verify that the entire range covered by the summary is either in use locally or truly unreachable elsewhere.

7. Why should EIGRP auto-summary be disabled in most modern networks?

Correct answer is A. EIGRP auto-summary triggers when the routing table contains subnets of the same classful major network on both sides of the router (discontiguous subnets). When it summarises 10.1.0.0/24 and 10.2.0.0/24 to 10.0.0.0/8 at the boundary, the other side of the network receives a single classful route with no way to distinguish which side has which subnet — causing routing loops or black holes. The command no auto-summary prevents this. In IOS 15.x and later, auto-summary is off by default.

8. A router's routing table contains the entry: D 192.168.0.0/22 is a summary, 00:10:00, Null0. What does this entry indicate?

Correct answer is D. The "D" code indicates EIGRP, and "is a summary" confirms this is an automatically generated discard route produced by EIGRP manual summarization. The router is advertising 192.168.0.0/22 to its neighbours and has installed this Null0 route locally to drop any packets for addresses within /22 that lack a more specific matching route. This entry is expected and correct — not an error.

9. An OSPF engineer wants to summarise routes 10.2.0.0/24, 10.2.1.0/24, 10.2.2.0/24, and 10.2.3.0/24 from Area 2 into Area 0. Which command achieves this on the ABR?

Correct answer is B. The area range command is the OSPF inter-area summarization command, configured under router ospf <process-id> on the ABR. The area number specified (2) is the source area — the area whose routes are being summarised. The mask 255.255.252.0 = /22, which covers 10.2.0.0 through 10.2.3.255 — exactly the four /24 networks. Option A uses incorrect OSPF syntax; option C is EIGRP syntax; option D is a network statement, not a summarization command.

10. A network engineer summarises 10.10.0.0/22 on a distribution router and advertises it to the core. Hosts in 10.10.3.0/24 report that they cannot reach servers in the data centre, even though the data centre router shows a valid route to 10.10.0.0/22. Hosts in 10.10.0.0/24, 10.10.1.0/24, and 10.10.2.0/24 work fine. What is the most likely cause?

Correct answer is C. The /22 does cover 10.10.3.0/24 (10.10.0.0–10.10.3.255), so the data centre router correctly forwards return traffic to the distribution router. However, the distribution router itself does not have a specific route to 10.10.3.0/24 — when return packets arrive, the distribution router matches its own Null0 discard route (10.10.0.0/22 → Null0) and drops them. The three other subnets work because specific routes for them exist in the distribution router's table and win via longest-prefix match over the Null0 summary. Fix: add the missing 10.10.3.0/24 route to the distribution router.

← Back to Home