EIGRP Auto-Summary: Behavior, Configuration, and Verification

Learn how EIGRP auto-summary creates classful routes, affects VLSM and discontiguous networks, and how to configure, verify, and troubleshoot it on Cisco routers.

EIGRP auto-summary is a routing behavior that can advertise several subnet routes as one classful summary route. Understanding it is important when troubleshooting missing subnet routes, unexpected broad routes, and reachability problems in VLSM or discontiguous network designs.

EIGRP, or Enhanced Interior Gateway Routing Protocol, exchanges reachability information between routers. Auto-summary changes the prefix information EIGRP advertises when routes cross a classful major-network boundary.

Why Route Summarization Is Used

Route summarization combines multiple specific routes into one shorter, less-specific prefix. For example, four contiguous /24 networks can be represented by one /22 summary:

10.20.0.0/24
10.20.1.0/24
10.20.2.0/24
10.20.3.0/24

Summary: 10.20.0.0/22

Summarization can provide several benefits:

Smaller routing tables.
Fewer routing updates when an individual subnet changes.
Lower processing and memory requirements on routers.
A more hierarchical and manageable routing design.

There are two important types of EIGRP summarization:

Automatic summarization: EIGRP chooses the historical classful major-network prefix. The administrator does not choose the summary length.
Manual summarization: The administrator chooses a suitable prefix and configures it on an interface. This allows the summary to match the addressing design.

Classful Major-Network Boundaries

A classful network uses the historical Class A, B, or C default mask. A major network is the classful parent network containing one or more subnets. Modern routing is classless, but these historical boundaries still matter to legacy behaviors such as EIGRP auto-summary.

Historical class	First-octet range	Default mask	Default prefix length	Example major network
Class A	1–126	255.0.0.0	/8	10.0.0.0/8
Class B	128–191	255.255.0.0	/16	172.16.0.0/16
Class C	192–223	255.255.255.0	/24	192.168.1.0/24

For example, 172.16.10.0/24 and 172.16.20.0/24 are both subnets of the Class B major network 172.16.0.0/16. EIGRP auto-summary uses that /16 boundary, not the actual /24 masks, when it summarizes across another major network.

Classless routing carries and evaluates prefix lengths. It supports subnet masks and VLSM, or Variable Length Subnet Masking, in which different prefix lengths are used within one addressing plan. Auto-summary can hide those useful prefix lengths.

How EIGRP Auto-Summary Works

When automatic summarization is active, EIGRP advertises a subnet using its classful major-network mask if the advertisement crosses a different major-network boundary.

Consider this example:

Router A owns:
  172.16.10.0/24
  172.16.20.0/24

Router A to Router B transit link:
  10.0.0.0/24

The 172.16.x.x subnets belong to the 172.16.0.0/16 major network. The transit network belongs to the different 10.0.0.0/8 major network. With auto-summary enabled, Router A can advertise 172.16.0.0/16 toward Router B instead of advertising the two /24 routes.

The receiving router may therefore install one broad route rather than the individual subnet routes. This reduces route detail, but it can also remove information needed for correct forwarding.

Local Summary Routes and Null0

A router that originates a summary commonly installs a local route for that summary pointing to Null0. Null0 is a discard interface. It prevents packets that match the summary but do not match any valid more-specific route from being forwarded indefinitely or causing a routing loop.

172.16.0.0/16 is a summary, Null0

A valid more-specific route takes precedence over the summary. For example, if the routing table contains both 172.16.10.0/24 and 172.16.0.0/16 toward Null0, traffic destined for 172.16.10.25 uses the /24 route because of longest-prefix match. Traffic for an unknown 172.16.x.x subnet may match only the /16 and be discarded at Null0.

Effects on Routing and Reachability

Reduced Route Detail

With auto-summary enabled, several routes within one major network can appear to the rest of the EIGRP domain as one classful route. The routing table becomes smaller, but routers lose the individual subnet information.

Condition	Advertised route information	Subnet mask preservation	Suitability for VLSM	Risk in discontiguous networks
Auto-summary enabled	Classful major-network summary across a boundary	Specific subnet masks may be hidden	Often unsuitable when subnet detail must cross boundaries	High if the same major network exists in separated locations
Auto-summary disabled	Specific classless prefixes, unless manually summarized	Subnet masks are preserved	Suitable for VLSM-aware designs	Lower, because individual prefixes remain visible

Discontiguous Networks

A discontiguous network is a major network separated into portions by another major network. For example, one site may use 172.16.10.0/24, while another site uses 172.16.20.0/24, with a 10.0.0.0/24 transit network between them.

If both edge routers summarize their local 172.16.x.x routes to 172.16.0.0/16, another router may see identical broad routes from different directions. It cannot use the hidden /24 information to select the correct site. Traffic may be sent toward the wrong router, loop between routers, or be discarded.

This is a common reason to disable auto-summary in modern EIGRP configurations. Disabling it allows 172.16.10.0/24 and 172.16.20.0/24 to remain distinguishable.

Longest-Prefix Match and Summary Routes

Routers use longest-prefix match when selecting among routes that match a destination. The route with the greatest number of matching prefix bits wins.

172.16.10.0/24 is more specific than 172.16.0.0/16.
If both routes are available, traffic for 172.16.10.25 uses the /24.
If the /24 is missing, the /16 summary may attract the traffic.
If that summary points to Null0, the packet is discarded.

Administrative distance is different from longest-prefix match. Administrative distance compares the trustworthiness of different route sources for the same destination prefix. It does not make a less-specific route beat an available more-specific route.

Default Behavior and IOS Considerations

Auto-summary behavior depends on the Cisco IOS platform, EIGRP implementation, and software release. Do not assume the setting from memory or from a different lab image. Inspect the active configuration and routing table.

Modern CCNA-style configurations commonly use no auto-summary when subnet and VLSM information must be preserved across major-network boundaries. The correct choice still depends on the addressing plan and the requirements of the network.

Configuring EIGRP Auto-Summary

Entering the EIGRP Routing Process

The setting is configured under the EIGRP router configuration mode. The autonomous system number must match the EIGRP process used by the participating routers.

Router(config)# router eigrp <autonomous-system-number>

Disabling Automatic Summarization

Use this command when individual subnet prefixes must be advertised across major-network boundaries:

Router(config)# router eigrp <autonomous-system-number>
Router(config-router)# no auto-summary

This does not remove EIGRP. It changes how EIGRP advertises subnet routes. It also does not prevent deliberate manual summarization.

Enabling Automatic Summarization

Enable the behavior only when a controlled lab or a carefully designed network requires classful summarization:

Router(config)# router eigrp <autonomous-system-number>
Router(config-router)# auto-summary

After changing the setting, allow EIGRP to reconverge or use a planned route refresh. Clearing neighbors or routes can interrupt forwarding and should be used cautiously.

Automatic Versus Manual EIGRP Summarization

Manual EIGRP summarization is configured on an interface. The administrator chooses the summary prefix instead of accepting a historical classful boundary.

Router(config)# interface <interface-id>
Router(config-if)# ip summary-address eigrp <autonomous-system-number> <summary-network> <summary-mask>

For example, four contiguous /24 networks can be summarized precisely as 10.20.0.0/22 rather than being represented by the much broader 10.0.0.0/8 classful summary.

Characteristic	Automatic summary	Manual interface summary
Prefix selection	Chosen from the historical classful major-network boundary	Chosen by the administrator
Configuration location	EIGRP router configuration mode	Interface configuration mode
Design precision	May be much broader than intended	Can match contiguous address blocks
Effect of disabling auto-summary	Automatic behavior stops	Manual summaries can still be configured
VLSM and discontiguous networks	Can hide important subnet information	Can be designed to preserve required reachability

Verification Commands

Use several views together. The configuration shows the setting, the protocol output describes active EIGRP behavior, and the routing and topology tables show what was learned and installed.

Command	What to inspect	Expected indication	Potential problem indication
`show running-config \| section router eigrp`	EIGRP process configuration	`no auto-summary` is present when specific routes are required	`auto-summary` is present or the intended setting is absent
`show ip protocols`	Active routing protocols and EIGRP settings	Correct EIGRP process and summary behavior	Unexpected process, AS number, or summarization state
`show ip route`	All installed IPv4 routes	Expected specific prefixes are present	Unexpected broad classful route or a Null0 summary
`show ip route eigrp`	Routes learned through EIGRP	Expected EIGRP prefixes and next hops	Missing /24 routes or only a classful summary
`show ip eigrp topology`	EIGRP topology entries and learned prefixes	Specific prefixes appear with expected neighbors	Topology contains only a summary or lacks the destination prefix

Exact output wording and supported commands can vary by IOS platform and release. Check both the local router and the neighboring router across the suspected major-network boundary.

Troubleshooting Workflow

Identify the missing destination. Determine the expected subnet and prefix length, such as 172.16.20.0/24.
Map the path. Find where the route crosses from one major network to another, such as from 172.16.0.0/16 to 10.0.0.0/8.
Inspect the EIGRP configuration. Use show running-config | section router eigrp and show ip protocols.
Confirm the installed route. Use show ip route and show ip route eigrp to look for a broad classful route or a summary pointing to Null0.
Inspect the topology information. Use show ip eigrp topology to determine whether the specific prefix was learned or hidden.
Disable auto-summary if subnet detail is required. Configure no auto-summary under the correct EIGRP process.
Allow convergence. Wait for normal EIGRP reconvergence, or use clearing commands only in a controlled maintenance or lab setting.
Recheck every router. Confirm that the individual prefixes appear and that the next hops point in the intended direction.

Common Symptoms

A broad route such as 172.16.0.0/16 exists, but expected /24 routes are absent.
Traffic to a subnet is sent toward the wrong site.
Traffic is dropped by a Null0 summary because the required more-specific route is unavailable.
Two separated sites advertise the same classful summary.

! Refresh commands for a controlled lab only
Router# clear ip eigrp neighbors
Router# clear ip route *

Worked Examples

Example 1: Automatic Classful Summary Across a Boundary

One router has 172.16.10.0/24 and 172.16.20.0/24. It connects to another router through 10.0.0.0/24.

Both 172.16 subnets belong to the Class B major network 172.16.0.0/16.
The transit network belongs to a different major network.
With auto-summary enabled, the remote advertisement can be 172.16.0.0/16.
With auto-summary disabled, the /24 prefixes can be advertised and learned individually.

Example 2: Discontiguous Addressing Failure

One side of a 10.0.0.0/24 transit network uses 172.16.10.0/24, and the other side uses 172.16.20.0/24.

Both edge routers can advertise 172.16.0.0/16 when auto-summary is active.
A middle router may not know which direction contains a particular /24.
The result can be incorrect forwarding, a routing loop, or a black hole.
Disabling auto-summary restores the specific prefixes needed for path selection.

Example 3: Summary Route to Null0

A router owns several more-specific routes within 192.168.0.0/16 and originates a summary. Its routing table may contain a 192.168.0.0/16 route to Null0.

Traffic matching a valid learned subnet uses that more-specific route.
Traffic for an unknown subnet within the /16 matches the summary.
The Null0 route discards that traffic locally, preventing a loop.

Exam-Relevant Notes

Auto-summary uses classful major-network boundaries, not the actual subnet mask of each route.
A different major-network boundary is the key condition for automatic summarization.
172.16.10.0/24 and 172.16.20.0/24 can be summarized as 172.16.0.0/16.
Discontiguous use of the same major network is a classic auto-summary problem.
Longest-prefix match makes a valid /24 preferable to a covering /16 summary.
A Null0 summary route can be normal and intentional; it is not automatically an interface failure.
no auto-summary is configured under router eigrp, not under an interface.
Disabling auto-summary does not disable manual interface-level summarization.
Verify behavior on the actual IOS release instead of assuming a universal default.

Summary

EIGRP auto-summary compresses subnet advertisements to classful major-network prefixes when they cross a different major-network boundary. This can reduce routing information, but it may hide VLSM details and create incorrect forwarding in discontiguous networks. Inspect the EIGRP process, protocol state, routing table, and topology table. When specific subnet reachability is required, configure no auto-summary, allow the network to reconverge, and verify that the individual prefixes are present. Use manual summaries when a deliberate, appropriately sized aggregation is needed.