Route summarization, also known as route aggregation or prefix aggregation, is a fundamental technique for reducing the size of routing tables and controlling routing update traffic. On the CCNA 200-301 exam (Objective 3.3), you must understand how to configure and verify manual and automatic summarization in both RIPv2 and EIGRP, and how it affects routing behavior. Mastering this topic is essential for building efficient, scalable networks and avoiding common exam traps.
Jump to a section
Imagine a massive library with millions of books. Each book has a unique call number (like a specific IP address). Without any organization, the librarian would have to list every single book's call number on a giant map to find anything—this is like a flat routing table with every /32 host route. That's overwhelming and slow. Instead, the library uses a hierarchical system: books are grouped by subject (e.g., 500s for Science, 600s for Technology). The librarian can say, 'All books starting with 5 are in the west wing,' and 'All books starting with 6 are in the east wing.' This is like a summary route: 5.0.0.0/8 or 6.0.0.0/8. Now, if someone asks for a specific book like 523.1, the librarian knows it's in the west wing (the summary route). But here's the catch: if a book with call number 523.1 is actually in the east wing (a more specific route), the librarian needs a more detailed map for that exception—just like a routing table needs a specific route (longest match) to override the summary. In networking, routers advertise summary routes to neighbors, reducing the number of prefixes exchanged. The neighbors install the summary, but if they have a more specific route, they use that instead. This mirrors how the library's general map (summary) works, but a detailed map (specific route) overrides it for particular items. The library also uses 'automatic summarization' when grouping books by the first digit of the call number—RIPv2 and EIGRP do this at classful boundaries by default. But just as a library might have a book that doesn't fit its subject category (like a science book in the arts section), you need manual summarization to create custom groupings that match your network topology.
What is Route Summarization?
Route summarization is the process of combining multiple contiguous network prefixes into a single, less specific prefix that represents all of them. For example, instead of advertising four /24 subnets (192.168.1.0/24, 192.168.2.0/24, 192.168.3.0/24, 192.168.4.0/24), a router can advertise a single /22 prefix: 192.168.0.0/22. This reduces the number of entries in routing tables, decreases routing update traffic, and improves convergence time.
Why It Exists
Routing Table Size: Without summarization, every subnet in a large network appears in every router's table. For an enterprise with thousands of subnets, this can exhaust memory and CPU on older routers.
Update Efficiency: Dynamic routing protocols send updates periodically (RIPv2: 30 seconds) or on change (EIGRP, OSPF). Fewer prefixes mean smaller update packets and less bandwidth consumption.
Faster Convergence: With fewer routes to process, routers can recalculate paths more quickly after a topology change.
Stability: A summary route hides flapping specific subnets from upstream routers, preventing unnecessary routing updates.
How It Works – Step by Step
Identify contiguous subnets: The subnets must be consecutive in the address space and share a common prefix length. For example, 10.1.0.0/24, 10.1.1.0/24, 10.1.2.0/24, 10.1.3.0/24 are contiguous and can be summarized as 10.1.0.0/22.
Calculate the summary prefix: Write the network addresses in binary and find the common bits from left to right. The summary prefix is the common bits followed by zeros, with a prefix length equal to the number of common bits. Example:
10.1.0.0/24 = 00001010.00000001.00000000.00000000
10.1.1.0/24 = 00001010.00000001.00000001.00000000
10.1.2.0/24 = 00001010.00000001.00000010.00000000
10.1.3.0/24 = 00001010.00000001.00000011.00000000
Common bits: 00001010.00000001.000000xx = 22 bits
Summary: 10.1.0.0/22Configure summarization on the router: Depending on the routing protocol, you either enable automatic summarization (default in RIPv2 and EIGRP for classful networks) or configure manual summarization on an interface.
Router advertises the summary: The router sends the summary prefix to neighbors instead of the individual subnets. Neighbors install the summary route in their routing table, with a metric derived from the component routes (e.g., the best metric among them for EIGRP).
Longest match wins: If a more specific route exists (e.g., a /24 for a particular subnet), it is preferred over the summary. This allows routers to have both a summary for general traffic and specific routes for exceptions.
Automatic vs. Manual Summarization
Automatic Summarization: In RIPv2 and EIGRP (but not OSPF), routers automatically summarize networks at classful boundaries (e.g., 10.0.0.0/8) when advertising out an interface that is not in the same major network. This is enabled by default but often causes problems in discontiguous networks (where subnets of the same major network are separated by another major network). For CCNA, you must know how to disable it with no auto-summary.
Manual Summarization: Supported by RIPv2, EIGRP, OSPF, and BGP. You configure a specific summary prefix on an interface. This gives you control over what is advertised and avoids issues like discontiguous networks.
IOS CLI Configuration Examples
RIPv2 Manual Summarization:
router rip
version 2
no auto-summary
!
interface GigabitEthernet0/0
ip summary-address rip 10.1.0.0 255.255.252.0EIGRP Manual Summarization:
router eigrp 100
no auto-summary
!
interface GigabitEthernet0/0
ip summary-address eigrp 100 10.1.0.0 255.255.252.0OSPF Manual Summarization (on ABR or ASBR):
router ospf 1
area 0 range 10.1.0.0 255.255.252.0Verification Commands
show ip route – Look for the summary route; note the prefix length and the fact that it is a candidate default or summary route.
show ip protocols – Check if auto-summary is enabled or disabled.
show ip rip database – For RIPv2, see the summary entry.
show ip eigrp topology – For EIGRP, see the summary route as an internal route with a metric.
debug ip rip or debug eigrp packets – Observe the update packets to see that only the summary is sent.
Example output for show ip route on a router receiving a summary:
10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
C 10.1.0.0/22 is directly connected, GigabitEthernet0/0Interaction with Other Protocols
RIPv2: Manual summarization works on a per-interface basis. Automatic summarization is enabled by default but should be disabled in discontiguous networks.
EIGRP: Similar to RIPv2, but EIGRP also supports summarization on any interface. The summary route is advertised with the metric equal to the best metric among the component routes. By default, EIGRP installs a null0 route for the summary to prevent loops.
OSPF: Summarization is configured on ABRs (for inter-area routes) and ASBRs (for external routes). OSPF does not support automatic summarization. The area range command summarizes routes from one area into another.
BGP: Summarization is configured with aggregate-address command. BGP can suppress more specific routes.
Exam Traps
Automatic summarization is enabled by default in RIPv2 and EIGRP – Many candidates forget to disable it, leading to routing loops in discontiguous networks.
Summary routes include a null0 route – In EIGRP, when you configure a summary, the router creates a local route to null0 for the summary prefix to prevent loops. This is often tested.
Manual summarization overrides automatic – If both are configured, manual summary takes precedence.
Summarization does not affect directly connected networks – You cannot summarize a directly connected interface's own network; summarization only affects routes being advertised.
OSPF does not support automatic summarization – Candidates sometimes confuse OSPF with RIPv2/EIGRP.
Key Values and Defaults
Default auto-summary: enabled in RIPv2 and EIGRP (IOS versions before 15.0(1)M – in later versions, it may be disabled by default). Always verify with show ip protocols.
Manual summary metric: For EIGRP, the metric is the best metric of the component routes.
Null0 route: EIGRP installs a null0 route for the summary with administrative distance 5 (or 2 for summary routes).
OSPF area range does not create a null0 route; it simply summarizes between areas.
Calculation Traps
When asked to find the best summary for a set of subnets, ensure they are contiguous. If they are not, you cannot summarize them into a single prefix (you may need multiple summaries).
The summary prefix length must be less than or equal to the shortest component prefix length. For /24 subnets, the summary can be /23 or shorter, but not /25.
Watch for powers of two: the number of subnets being summarized must be a power of two if you want a single summary. For example, 5 subnets cannot be summarized into one prefix; you might need two summaries.
The summary network address must align with the prefix length. For a /22, the third octet must be a multiple of 4 (e.g., 0, 4, 8, 12...).
Identify contiguous subnets to summarize
Start by listing the subnets you want to summarize. They must be contiguous in the IP address space. For example, if you have 192.168.0.0/24, 192.168.1.0/24, 192.168.2.0/24, and 192.168.3.0/24, they are contiguous because they increment by one in the third octet. If you had 192.168.0.0/24 and 192.168.2.0/24 (skipping 1), they are not contiguous and cannot be summarized into a single prefix. Also, ensure that the subnets belong to the same major network (e.g., all are 192.168.x.x). If they are from different major networks, automatic summarization might cause issues, but manual summarization can still be used if the resulting prefix is valid.
Calculate the summary prefix and mask
Convert the subnet addresses to binary and find the common bits from left to right. For the example above: 192.168.0.0 = 11000000.10101000.00000000.00000000, 192.168.1.0 = 11000000.10101000.00000001.00000000, 192.168.2.0 = 11000000.10101000.00000010.00000000, 192.168.3.0 = 11000000.10101000.00000011.00000000. The first 22 bits are common (11000000.10101000.000000xx). So the summary prefix is 192.168.0.0/22. The mask in dotted decimal is 255.255.252.0. For exam questions, practice this calculation quickly. Remember that the number of subnets must be a power of two for a single summary; if not, you may need multiple summaries or a different approach.
Disable automatic summarization if needed
On RIPv2 and EIGRP, automatic summarization is enabled by default. This can cause routing loops in discontiguous networks. To disable it, use the `no auto-summary` command under the routing process. For example: `router rip` then `no auto-summary`. Verify with `show ip protocols`. On newer IOS versions (15.x), auto-summary may be disabled by default, but always check. For OSPF, there is no automatic summarization, so this step is skipped.
Configure manual summarization on the interface
For RIPv2 and EIGRP, manual summarization is configured on the outgoing interface. Enter interface configuration mode and use the `ip summary-address` command. For RIPv2: `ip summary-address rip 192.168.0.0 255.255.252.0`. For EIGRP: `ip summary-address eigrp 100 192.168.0.0 255.255.252.0`. The summary will be advertised out that interface to neighbors. Note that the interface must be in the same major network as the summary? Actually, no – the summary can be any prefix, but the interface must have an IP address that is within the summary range? Not necessarily; the summary is just advertised out the interface. For OSPF, summarization is configured under the router OSPF process with the `area range` command, not on an interface.
Verify the summary route is installed and advertised
Use `show ip route` to see if the summary route appears in the routing table. For EIGRP, you'll also see a null0 route for the summary (e.g., `192.168.0.0/22 is a summary, Null0`). Use `show ip protocols` to confirm auto-summary is disabled. On the neighbor router, use `show ip route` to see the summary route received. You can also use `debug ip rip` or `debug eigrp packets` to see the actual update packets containing the summary. For OSPF, use `show ip ospf database summary` to see the summary LSA.
Troubleshoot common summarization issues
Common issues include: (1) Discontiguous networks – if subnets of the same major network are separated by another major network, automatic summarization causes incorrect routing. Fix by disabling auto-summary and using manual summaries. (2) Missing null0 route – in EIGRP, if the null0 route is missing (e.g., due to a bug or misconfiguration), routing loops can occur. Check with `show ip route` for the null0 entry. (3) Summary not being advertised – ensure the interface is up and the routing protocol is enabled on it. Use `show ip interface brief` and `show ip protocols`. (4) Incorrect summary calculation – verify the prefix length and network address. Use `show ip route` on the advertising router to see if the component routes are present.
In a large enterprise network with hundreds of branch offices, route summarization is critical for keeping the core routing table manageable. For example, consider a company with a /16 address space (10.0.0.0/16) divided into /24 subnets for each branch. Without summarization, the core routers would need to know about every single /24, potentially thousands of routes. By summarizing at the distribution layer into /20 or /18 prefixes, the core only sees a handful of routes.
Scenario 1: Summarization at the Distribution Layer A typical design has access switches in each building with /24 VLANs. The distribution layer router (or multilayer switch) connects to the core. On the distribution router, you configure manual summarization for the building's subnets. For example, building A uses 10.1.0.0/21 (8 subnets), building B uses 10.1.8.0/21, etc. The distribution router advertises only the /21 to the core. If a new /24 is added within the /21, the core does not need to learn about it – the summary already covers it. This reduces routing updates and improves stability.
Scenario 2: Avoiding Discontiguous Network Problems A company acquires another company and merges networks. The original network uses 172.16.0.0/16 subnetted into /24s, but the new company uses 172.16.0.0/16 as well, but with different subnets. Without careful planning, automatic summarization could cause routers to think all 172.16.x.x is reachable via one path when it is actually split. The solution is to disable auto-summary and configure manual summaries that accurately reflect the topology, possibly using different major networks or more specific summaries.
Performance Considerations Summarization reduces CPU load on routers because fewer routes are processed. However, the router must still compute the summary route's metric (e.g., best metric among component routes in EIGRP) and install a null0 route. On very large networks, the number of summaries can still be high, but it is far less than the number of individual subnets. Bandwidth savings are significant: a RIPv2 update with 1000 routes is about 30KB; with summarization to 10 routes, it's 300 bytes.
Misconfiguration Consequences If you misconfigure a summary (e.g., too broad a prefix), traffic may be black-holed. For instance, if you summarize 10.0.0.0/8 but have subnets that are not actually reachable via that router, packets to those subnets will be forwarded to the summarizing router, which then drops them (or sends them to null0 if the null0 route exists). This is a common cause of connectivity issues. Also, if you forget to disable auto-summary in a discontiguous network, routing loops occur because routers receive a summary that points to the wrong location for some subnets.
Scale In service provider networks, summarization is essential for Internet routing. The global BGP table has over 900,000 routes; without summarization by ISPs, it would be unmanageable. Enterprises typically summarize at the WAN edge to reduce the number of routes advertised to the provider.
The CCNA 200-301 exam objective 3.3 covers route summarization within the context of IP connectivity. Expect questions on both theory and configuration, particularly for RIPv2 and EIGRP. The exam tests your ability to:
Calculate the best summary prefix given a set of subnets.
Identify when automatic summarization causes problems (discontiguous networks).
Configure manual summarization on a router interface.
Verify summarization using show commands.
Understand the behavior of null0 routes in EIGRP.
Common Wrong Answers and Why Candidates Choose Them
Choosing a summary that is too specific (e.g., /24 instead of /22): Candidates often forget that the summary must cover all subnets. They might pick the first subnet's prefix length instead of calculating the common bits. Trap: They see 192.168.1.0/24 and think the summary is 192.168.1.0/24, but that only covers one subnet.
Selecting a summary with the wrong network address (e.g., 192.168.2.0/22): The summary network address must align with the prefix length. For a /22, the third octet must be a multiple of 4. 192.168.2.0/22 is invalid because 2 is not a multiple of 4. Candidates often forget this alignment rule.
Thinking OSPF supports automatic summarization: This is a classic trap. OSPF does not do automatic summarization; only RIPv2 and EIGRP do. Candidates who study RIPv2 and EIGRP first may incorrectly apply the same behavior to OSPF.
Believing that summarization reduces the number of routes in the local routing table: Actually, the summarizing router still has the individual component routes in its table (unless they are from a different source). Summarization only affects what is advertised to neighbors. The local router's table may also include a null0 route for the summary, but the component routes remain. Candidates confuse local table with advertised routes.
Specific Values and Commands
Default auto-summary: enabled (RIPv2, EIGRP) – but verify with show ip protocols.
Command to disable: no auto-summary under router config.
Manual summary command: ip summary-address rip|eigrp <as> <network> <mask>.
For OSPF: area <area-id> range <network> <mask>.
Null0 route: In EIGRP, show ip route includes a summary route with next-hop Null0 and AD 5 (or 2 for summary).
Calculation Traps
Ensure subnets are contiguous and the number of subnets is a power of two for a single summary. If you have 3 subnets, you cannot summarize into one prefix; you might need two summaries (e.g., /23 and /24).
The summary prefix length is found by counting common bits. Practice binary conversion.
Watch for questions that ask for the summary that includes a specific set of subnets but also excludes others. You may need to choose a prefix that covers all given but not extra unwanted subnets.
Decision Rule for Scenario Questions
Read the question: Are the subnets in the same major network? If not, automatic summarization will cause issues.
Is the network discontiguous? If yes, disable auto-summary and use manual summaries.
To find the best summary, list the subnets in binary, find common bits, and determine the prefix. Check alignment.
Verify that the summary does not include unintended subnets (e.g., if you have 10.1.0.0/24 and 10.1.1.0/24, a /22 would include 10.1.2.0 and 10.1.3.0, which might not be desired).
Route summarization reduces routing table size and update traffic by advertising a single prefix for multiple contiguous subnets.
Manual summarization is configured on interfaces for RIPv2 and EIGRP using `ip summary-address`; for OSPF, use `area range`.
Automatic summarization is enabled by default in RIPv2 and EIGRP but must be disabled in discontiguous networks with `no auto-summary`.
The summary prefix must have a network address that aligns with the prefix length (e.g., /22 requires third octet multiple of 4).
EIGRP installs a null0 route for manual summaries to prevent routing loops (AD 5).
OSPF does not support automatic summarization; only manual summarization on ABRs/ASBRs.
When calculating a summary, ensure subnets are contiguous and the count is a power of two for a single prefix.
These come up on the exam all the time. Here's how to tell them apart.
Automatic Summarization
Enabled by default in RIPv2 and EIGRP
Summarizes at classful boundaries only (e.g., /8, /16, /24)
Can cause routing loops in discontiguous networks
No configuration required, but must be disabled if unwanted
Does not create a null0 route in RIPv2; EIGRP may create a summary route to null0
Manual Summarization
Configured explicitly on an interface or area
Can summarize to any prefix length
Prevents discontiguous network issues
Requires configuration but gives full control
EIGRP always creates a null0 route; RIPv2 does not
Mistake
Route summarization reduces the number of routes in the local router's routing table.
Correct
Summarization only affects what is advertised to neighbors. The local router still has the component routes (unless they are suppressed) and may add a null0 route for the summary. The routing table size on the local router does not decrease significantly.
Candidates think summarization compresses the local table, but it actually only compresses updates sent to others.
Mistake
OSPF supports automatic summarization like RIPv2 and EIGRP.
Correct
OSPF does not support automatic summarization. Summarization in OSPF is always manual and configured on ABRs or ASBRs using the `area range` command.
Candidates generalize from RIPv2/EIGRP behavior to OSPF without reading the specifics.
Mistake
You can summarize any set of subnets into one prefix regardless of contiguity.
Correct
Subnets must be contiguous (consecutive addresses) and the number of subnets must be a power of two for a single summary. Non-contiguous subnets require multiple summaries or a different approach.
Candidates often ignore the binary alignment requirement and pick a prefix that doesn't cover all subnets or includes unwanted ones.
Mistake
Manual summarization in EIGRP does not create a null0 route.
Correct
EIGRP always installs a null0 route for manually configured summaries to prevent routing loops. This route has an administrative distance of 5 (or 2 for summary routes) and appears in `show ip route`.
Candidates may not read the output carefully or confuse EIGRP with RIPv2, which does not create a null0 route.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Automatic summarization is a feature of RIPv2 and EIGRP where routers automatically summarize networks at classful boundaries (e.g., /8, /16, /24) when advertising out an interface that belongs to a different major network. It is enabled by default but can cause routing loops in discontiguous networks. Manual summarization is configured by the network engineer on a specific interface (RIPv2, EIGRP) or area (OSPF) and allows summarization to any prefix length, giving full control. For the exam, remember that automatic summarization must be disabled with `no auto-summary` in discontiguous networks, and manual summarization is done with `ip summary-address` or `area range`.
No, route summarization only affects routes that are being advertised to neighbors. Directly connected networks are not summarized; they are advertised individually. However, when you configure manual summarization on an interface, the router will advertise the summary prefix instead of the component routes that are learned via the routing protocol. Directly connected routes are not affected. For example, if you have a directly connected /24, you cannot summarize it into a /23 because it's not a learned route. The summary command only applies to routes that are being redistributed or advertised.
EIGRP creates a null0 route for the summary prefix to prevent routing loops. When a router advertises a summary, it is telling neighbors that it knows how to reach all subnets within that summary. However, if the router receives a packet destined for a subnet within the summary that it does not actually have a component route for (e.g., because that subnet doesn't exist), the router would normally drop the packet. But without the null0 route, the router might forward the packet back out the same interface it came from, creating a loop. The null0 route ensures that any traffic for subnets not explicitly in the routing table is discarded. The null0 route has an administrative distance of 5 (or 2 for summary routes) and is visible in `show ip route`.
Yes, you can manually summarize routes from different major networks into a single prefix, as long as the resulting prefix is valid. For example, you could summarize 10.0.0.0/8 and 11.0.0.0/8 into 8.0.0.0/5? No, that would be incorrect because the common bits are only the first 5 bits? Actually, 10.0.0.0/8 and 11.0.0.0/8 have first octets 10 (00001010) and 11 (00001011). Common bits: first 6 bits are 000010, so the summary would be 8.0.0.0/6? That includes 8.0.0.0/6 which covers 8.0.0.0 to 11.255.255.255, so it would include 10.0.0.0/8 and 11.0.0.0/8 but also 8.0.0.0/8 and 9.0.0.0/8, which may not be desired. So technically possible but usually not recommended because it includes unintended networks. Automatic summarization only works within the same major network.
Use `show ip route` on the summarizing router to see if the summary route appears. For EIGRP, you will see a null0 route for the summary. For RIPv2, the summary may appear as a route with the next-hop of the interface. On the neighbor router, use `show ip route` to see the summary route received. Also use `show ip protocols` to confirm auto-summary is disabled. For OSPF, use `show ip ospf database summary` to see the summary LSA. Debug commands like `debug ip rip` or `debug eigrp packets` can show the actual updates containing the summary.
The longest match rule states that when a router has multiple routes to the same destination, it uses the route with the longest prefix length (most specific). Summarization creates a less specific route (shorter prefix). So if a router has both a summary route (e.g., 10.1.0.0/22) and a more specific route (e.g., 10.1.1.0/24), the router will use the /24 for traffic to 10.1.1.x. This allows you to have a general summary for most subnets while having specific routes for exceptions. For example, if a particular subnet is reachable via a different path, you can advertise a specific route for it, and it will override the summary. This is a key concept for exam questions.
Yes, especially with automatic summarization in discontiguous networks. If a router summarizes a major network and sends the summary to a neighbor that also has subnets of that major network, the neighbor might send traffic for those subnets back to the summarizing router, creating a loop. Manual summarization can also cause loops if the summary is too broad and the router does not have a null0 route (in protocols like RIPv2). EIGRP prevents this by installing a null0 route. Always ensure that the summarizing router has a path to all subnets within the summary, or use a null0 route to drop traffic for missing subnets.
You've just covered Route Summarization — now see how well it sticks with free CCNA 200-301 practice questions. Full explanations included, no account needed.
Done with this chapter?