Route summarization is one of the most effective tuning tools available in EIGRP. Instead of advertising every individual subnet to a neighbor, a router can group several subnets together and advertise them as one summarized route. That single change cuts the number of entries in every downstream routing table and shrinks the size of routing updates flowing across the network.
EIGRP supports two ways to summarize routes: automatic summarization, which happens at classful network boundaries with no manual configuration, and manual summarization, which lets an administrator define an exact summary boundary on a specific interface. This guide focuses on automatic summarization — how it behaves, why Cisco turned it off by default, and how to configure, verify, and troubleshoot it.
What Automatic Summarization Actually Does
When automatic summarization is enabled, EIGRP checks every subnet configured under a network command. If it finds subnets that belong to the same classful network, it advertises a single classful A, B, or C route to neighbors instead of the individual subnets. Critically, this only applies to subnets directly connected to the router’s own interfaces — routes learned from other EIGRP neighbors are never re-summarized this way.
Consider a router, R1, with four locally connected subnets: 10.10.10.0/30, 10.10.11.0/24, 10.10.12.0/24, and 10.10.13.0/24. All four subnets fall inside the same class A network, 10.0.0.0/8. With automatic summarization enabled, R1 collapses all four into a single advertisement of 10.0.0.0/8 sent to its neighbor, R2. Traffic destined for 10.10.11.0/24, 10.10.12.0/24, and 10.10.13.0/24 all travels across that one summarized path from R2’s perspective — R2 never sees the individual subnets and never carries separate routing table entries for them.
This is exactly why summarization matters at scale: a network with hundreds of subnets inside a handful of major networks can collapse its routing tables down to a handful of summary routes, cutting both memory usage and the CPU cost of processing routing updates.
Why Automatic Summarization Is Disabled by Default Today
Automatic summarization used to be the default EIGRP behavior on every Cisco IOS release. That changed starting with Cisco IOS Release 15.0(1)M and 12.2(33): from those releases forward, automatic summarization ships disabled by default, and administrators who want it must explicitly turn it on.
The reason is simple: classful network boundaries stopped being a reliable design assumption once Classless Inter-Domain Routing (CIDR) became standard. Modern networks routinely split a single classful network across multiple, non-adjacent locations — a condition known as a discontiguous network. Automatic summarization at classful boundaries can cause serious routing problems in a discontiguous network, because two different routers can end up advertising the same summarized classful route while the specific subnets behind each one are unreachable from the other side. That is exactly the kind of routing black hole that CIDR-aware manual summarization avoids, which is why Cisco defaults to leaving auto-summary off on any device running a modern IOS release.
Configuring EIGRP Automatic Summarization
On an IOS release where auto-summary is off by default, turning it on takes two commands in router configuration mode:
R1(config)# router eigrp 100
R1(config-router)# auto-summaryThe number 100 is the EIGRP autonomous system number, and it must match on every router in the same EIGRP domain. Apply the identical auto-summary command on every router that should participate in automatic summarization — R1 alone summarizing its routes has no effect on how R2 or R3 behave.
To disable it again, use the negated form of the same command:
R1(config-router)# no auto-summaryVerifying Auto-Summary Configuration
The show ip protocols command confirms whether automatic summarization is active on a given router. The output includes a line explicitly stating whether “automatic network summarization” is in effect. A router running a modern IOS release will show it disabled until the auto-summary command has been entered manually.
Once auto-summary is enabled and verified with show ip protocols, the next step is confirming the actual effect on a neighboring router’s routing table. Using show ip route eigrp on R2 shows whether R2 now carries a single summarized entry instead of the individual subnets. For example, if R1 has the subnets 192.168.10.4/30 and 192.168.10.8/30 connected locally, enabling auto-summary causes R1 to advertise a single 192.168.10.0/24 route to its neighbors instead of the two /30 subnets individually.
If R1 has EIGRP neighbors on more than one interface, the summarized route goes out every interface where an EIGRP adjacency exists — an interface with no EIGRP neighbor never receives the update at all, since there’s no one on the other end to send it to.
Verifying Auto-Summary from the Topology Table
The routing table only shows the single best route, so confirming a summary route was actually received — not just installed — sometimes requires looking at the topology table directly. Suppose R1 sends R2 a summarized advertisement of 172.16.0.0/16. Both R2 and R3 should now show that summary in their topology tables if the network is configured correctly across every router in the path.
Running show ip eigrp topology with the all-links keyword displays every update a router has received, including summary routes and any subnet-level updates that were filtered out by summarization elsewhere in the network. This is the most reliable way to confirm a summarized route was actually propagated correctly across multiple hops, rather than only checking the final routing table entry on one router.
The Null0 Summary Route
Every time EIGRP creates an automatic summary route, it also installs a second, hidden route pointing to interface Null0 — a virtual IOS interface sometimes called “the bit bucket.” Any packet that matches a route pointing to Null0 is silently discarded.
This Null0 route exists to prevent routing loops. When a router advertises a summary like 10.0.0.0/8, it is implicitly claiming it can reach every address inside that range. If a packet arrives destined for an address inside 10.0.0.0/8 that isn’t actually covered by one of the real, more-specific routes, the Null0 summary route catches it and drops it instead of forwarding it toward a neighbor that might bounce it right back — the classic signature of a routing loop.
EIGRP automatically installs a Null0 summary route under any of these conditions:
- A single subnet was learned via EIGRP that falls under a classful network the router is also summarizing.
- Two or more
networkcommands are configured under the EIGRP router configuration mode. - Automatic summarization is enabled and at least one subnet exists within the summarized classful network.
How to Identify the Classful Boundary Yourself
Before enabling automatic summarization on any router, it helps to work out exactly what the summary will look like, rather than relying on the router to tell you afterward. The process is the same every time:
- List every subnet directly connected to the router’s interfaces. For R1 in the earlier example, that’s 10.10.10.0/30, 10.10.11.0/24, 10.10.12.0/24, and 10.10.13.0/24.
- Identify the first octet of each address to determine its class. Any address starting with 1–126 is Class A, 128–191 is Class B, and 192–223 is Class C. All four subnets above start with 10, placing them firmly in Class A.
- Apply the classful default mask for that class. Class A uses a default /8 mask, Class B uses /16, and Class C uses /24.
- Combine the network portion with the classful mask. For the 10.x.x.x subnets, the classful summary is 10.0.0.0/8 — every one of the four subnets falls inside that range.
The same logic explains why 192.168.10.4/30 and 192.168.10.8/30 summarize to 192.168.10.0/24 rather than something broader: both addresses start with 192, placing them in Class C, and the classful default mask for Class C is /24. Working through these four steps by hand before enabling auto-summary is the fastest way to predict exactly what a router will advertise — and to catch a discontiguous-network problem before it becomes an outage.
Automatic Summarization vs. Manual Summarization
| Attribute | Automatic Summarization | Manual Summarization |
|---|---|---|
| Boundary | Fixed at classful A/B/C network edges | Any prefix length the administrator chooses |
| Configuration | auto-summary under router eigrp | ip summary-address eigrp on a specific interface |
| IPv6 support | Not available — no classful addressing in IPv6 | Fully supported |
| Discontiguous network risk | High — can cause routing black holes | Low — administrator controls exactly where the boundary sits |
| Default state (modern IOS) | Disabled | N/A — configured only when needed |
| Scope | Applies to every classful boundary the router crosses | Applies only to the interface it’s configured on |
Why Automatic Summarization Doesn’t Exist for IPv6
IPv6 has no concept of classful addressing — there is no equivalent of a class A, B, or C network boundary for EIGRP to summarize at automatically. Every IPv6 summarization decision in EIGRP for IPv6 has to be manual, using summary-address under the IPv6 address-family configuration. This is one of the clearest structural differences between EIGRP for IPv4 and EIGRP for IPv6 for anyone studying both address families for certification.
Troubleshooting Automatic Summarization
- A remote router is missing routes it should have — check whether the network is discontiguous. If two separate parts of the same classful network are separated by a different major network in between, automatic summarization can cause one side to become unreachable from the other, since both sides advertise the same summary and neither has the specific subnet routes anymore.
- Traffic is being silently dropped — this is often the Null0 route working as intended. Confirm with
show ip routewhether a Null0 entry exists for the classful network in question, and verify the destination address actually corresponds to a real, advertised subnet. auto-summaryis configured but neighbors still see individual subnets — confirm the command was applied on the originating router, not just the router receiving the update. Automatic summarization only summarizes routes for subnets directly connected to the advertising router’s own interfaces.- Auto-summary won’t take effect on IPv6 networks — this is expected behavior, not a bug. Use manual summary-address configuration instead, since IPv6 has no classful network concept for EIGRP to summarize against.
Frequently Asked Questions
Is EIGRP automatic summarization enabled by default? No, not on any modern IOS release. It was enabled by default before Cisco IOS Release 15.0(1)M and 12.2(33); every release since then ships with it disabled.
What command enables automatic summarization? auto-summary, entered in router configuration mode under the EIGRP process (for example, router eigrp 100 followed by auto-summary).
What command verifies whether automatic summarization is active? show ip protocols displays the current auto-summary state on a router. Following up with show ip route eigrp confirms whether summarized routes actually appear in a neighbor’s routing table.
Why does EIGRP install a route to Null0 when summarization is enabled? To prevent routing loops. The Null0 route silently drops any packet destined for an address inside the summarized range that doesn’t correspond to a real, more-specific route.
Does automatic summarization work with IPv6? No. IPv6 has no classful addressing, so there is no automatic classful boundary for EIGRP to summarize at. IPv6 summarization must always be configured manually.
Why would enabling automatic summarization break a network instead of improving it? Discontiguous networks are the most common cause. If subnets from the same classful network exist on both sides of a different major network, automatic summarization can hide the specific routes each side needs, creating unreachable destinations instead of a cleaner routing table.
Key Takeaways
Automatic summarization collapses subnets into classful A, B, or C routes at network boundaries with zero manual configuration, but it comes with real risk in any network where a classful boundary doesn’t cleanly separate every part of the topology. That’s exactly why Cisco flipped the default to off starting with IOS 15.0(1)M and 12.2(33). Manual summarization, configured with ip summary-address eigrp on a specific interface, gives an administrator precise control over exactly where a summary boundary sits — which is why it has become the standard approach in nearly every modern EIGRP deployment.
