VMware ESXi and vSphere Cluster Management
EIGRP Auto-Summary and Classful Route Summarization
Learn how EIGRP auto-summary creates classful routes, why it causes problems in discontiguous networks, and how to disable and verify it.
EIGRP (Enhanced Interior Gateway Routing Protocol) exchanges reachability information between neighboring Cisco routers. One important EIGRP behavior is auto-summary: the automatic conversion of subnet routes into classful major-network routes when they are advertised across a different major network boundary.
This lesson explains route summarization, classful and classless routing, discontiguous networks, EIGRP verification commands, and the safer use of deliberate manual summaries.
Route Summarization Basics
Route summarization combines multiple more-specific routes into one less-specific prefix. For example, several subnet routes can be represented by one aggregate route. A routing table using a summary needs fewer entries, and routers may advertise fewer routes to their neighbors.
A summary is less specific than the routes it represents. For example, 10.0.0.0/8 is less specific than 10.5.10.0/24. The number after the slash is the prefix length; a smaller prefix length covers a larger address range.
- Automatic summarization: the routing protocol chooses a classful boundary and advertises the resulting major-network route.
- Manual summarization: an administrator explicitly selects the summary prefix, mask, and interface where it is advertised.
Summarization can reduce routing-table size and update traffic, but an incorrect summary can claim reachability for addresses that are not actually reachable. A summary must therefore be planned around the topology.
Classful IPv4 Boundaries
Traditional IPv4 addressing divided addresses into classes. Although modern networks use classless addressing and CIDR, the old class boundaries remain important for understanding EIGRP auto-summary.
- Class A: the traditional major-network prefix is
/8. The private major network10.0.0.0/8is an example. - Class B: the traditional major-network prefix is
/16. The private network172.16.0.0/16is an example. - Class C: the traditional major-network prefix is
/24. The private subnet192.168.1.0/24illustrates a classful boundary.
A major network is the classful network portion of an IPv4 address. A subnet is a more-specific network carved from that major network. For example, 10.5.10.0/24 is a subnet inside the Class A major network 10.0.0.0/8.
| Traditional class | Example major network | Classful prefix length | Example subnet | Auto-summary result |
|---|---|---|---|---|
| Class A | 10.0.0.0 | /8 | 10.5.10.0/24 | 10.0.0.0/8 |
| Class B | 172.16.0.0 | /16 | 172.16.20.0/24 | 172.16.0.0/16 |
| Class C | 192.168.1.0 | /24 | 192.168.1.64/26 | 192.168.1.0/24 |
How EIGRP Auto-Summary Works
EIGRP auto-summary advertises subnet routes at their classful major-network boundaries. When a subnet is advertised across an interface that belongs to a different major network, EIGRP can replace the subnet prefix with the classful summary.
For example, suppose R1 owns the connected subnet 10.5.10.0/24. R1 and R2 form an EIGRP neighbor relationship across a transit link whose addresses are outside the 10.0.0.0/8 major network. With auto-summary active, R1 can advertise 10.0.0.0/8 to R2 instead of 10.5.10.0/24.
Classful Versus Classless Routing
Classful routing relies on the traditional major-network boundary and does not preserve the complete subnet mask in every routing decision. Classless routing carries a prefix length with the route, such as 10.5.10.0/24, so routers know exactly which addresses are reachable.
Converting 10.5.10.0/24 into 10.0.0.0/8 loses subnet-level precision. The /8 route matches every address from 10.0.0.0 through 10.255.255.255, not only the addresses in the /24 subnet.
Modern designs generally preserve classless prefixes. When aggregation is useful, administrators normally configure a deliberate manual summary that covers only the correct, reachable address space.
Topology Example: R1 and R2
Consider this two-router topology:
R1 LAN: 10.5.10.0/24
|
R1 ===== EIGRP transit link ===== R2
transit network is not 10.0.0.0/8
R1 advertises the LAN route toward R2.
With auto-summary enabled, R2 may receive the following route:
10.0.0.0/8 via R1
R2 then considers every destination matching 10.0.0.0/8 to be reachable through R1. Traffic for 10.5.10.25 correctly goes toward R1, but traffic for an unrelated or unreachable address such as 10.200.1.10 may also be sent toward R1. R1 cannot deliver that traffic merely because it owns one subnet inside the /8.
After auto-summary is disabled and EIGRP reconverges, R2 should receive the specific route:
10.5.10.0/24 via R1
R2 then forwards only destinations in that /24 toward R1. An address such as 10.200.1.10 is no longer treated as reachable through R1 unless another route matches it.
| Configuration state | Route advertised by R1 | Route installed on R2 | Forwarding consequence |
|---|---|---|---|
| Auto-summary enabled | 10.0.0.0/8 | EIGRP route to 10.0.0.0/8 via R1 | All 10.x destinations can be sent toward R1 |
| Auto-summary disabled | 10.5.10.0/24 | EIGRP route to 10.5.10.0/24 via R1 | Only the advertised /24 is sent toward R1 |
Discontiguous Networks
A discontiguous network has separated portions of the same major classful network with one or more different major networks between them. For example, one site may use 10.1.1.0/24, another site may use 10.5.10.0/24, and a non-10 major network may lie between those sites.
10.1.1.0/24 -- R1 -- 172.16.0.0/16 transit -- R2 -- 10.5.10.0/24
With automatic classful summarization, routers may advertise both separated portions as 10.0.0.0/8. The summary does not identify which specific 10.x subnets exist or where they are located.
This can produce incorrect forwarding. A router may install a broad 10.0.0.0/8 route through one neighbor and send traffic for a different, unreachable portion of the 10.x range toward that neighbor. The result can be a routing loop, a dropped packet, or a black hole.
Disabling auto-summary allows EIGRP to advertise the actual subnet prefixes. Routers can then distinguish 10.1.1.0/24 from 10.5.10.0/24 and select the appropriate next hop.
Longest-Prefix Match and Summaries
Longest-prefix match is the forwarding rule that prefers the most-specific route matching a destination. If a router has both 10.0.0.0/8 and 10.5.10.0/24, traffic for 10.5.10.25 uses the /24 because /24 is more specific than /8.
Accurate prefix advertisements give longest-prefix match the information it needs. An incorrect broad summary can still be selected for destinations that have no more-specific route, which is why summaries must not include unreachable address space.
Disabling EIGRP Auto-Summary
In classic EIGRP configuration, the setting is applied in router EIGRP configuration mode:
Router(config)# router eigrp <autonomous-system-number>
Router(config-router)# no auto-summary
Apply the change on routers that advertise affected routes. Use the appropriate EIGRP process or address-family context for the platform and software syntax in use.
Changing the setting affects route advertisements. Existing neighbor and topology state may need time to refresh before the expected /24 appears. In a controlled lab, you can reset the EIGRP adjacencies:
Router# clear ip eigrp neighbors
Safe Verification Workflow
- Record the current routing table, EIGRP neighbors, and relevant configuration before changing anything.
- Confirm that the EIGRP neighbor relationship is established.
- Inspect the EIGRP protocol settings to determine whether auto-summary is active.
- Inspect the learned route and verify its prefix length and next hop.
- Change the configuration, allow convergence, and repeat the checks.
- Test valid destinations and test an address that should not be reachable through the advertising router.
show ip eigrp neighbors
show ip protocols
show running-config | section router eigrp
show ip route eigrp
show ip route <destination-network>
show ip eigrp topology
show ip eigrp neighbors confirms the EIGRP adjacency. show ip protocols displays protocol settings and commonly identifies whether automatic summarization is enabled. The running configuration shows the configured EIGRP commands.
show ip route eigrp lists EIGRP-installed routes. Use show ip route <destination-network> to inspect a particular prefix, including its next hop and prefix length. show ip eigrp topology provides EIGRP topology information, including learned route details used by DUAL.
Troubleshooting Auto-Summary Problems
Unexpected 10.0.0.0/8 Route
If a router has an EIGRP route for 10.0.0.0/8 when only one 10.x subnet should be reachable through its next hop, check:
show ip route 10.0.0.0
show ip protocols
show running-config | section router eigrp
The likely cause is active automatic classful summarization on the advertising router. Disable it, confirm the neighbor relationship, allow route exchange to refresh, and verify that the specific subnet prefix is installed.
Traffic Sent to the Wrong Router
Compare routing tables along the path. Look for overlapping classful summaries and the next hops selected for the affected destinations. Confirm whether separated portions of the same major network exist. Remove inappropriate auto-summary behavior or redesign the addressing and summaries.
The /24 Does Not Appear Immediately
Check the neighbor and topology state:
show ip eigrp neighbors
show ip eigrp topology
show ip route eigrp
Wait for normal convergence. In a controlled lab, reset the neighbor relationship and recheck the route. If the command syntax differs or no auto-summary is unavailable, use context-sensitive help and verify the operational result with show ip protocols and routing-table commands.
Manual EIGRP Summarization
Automatic summarization is not the same as intentional aggregation. Manual EIGRP summarization is configured on an interface and uses a prefix selected by the administrator.
interface <interface-id>
ip summary-address eigrp <autonomous-system-number> <summary-network> <summary-mask>
| Characteristic | Auto-summary | Manual summarization |
|---|---|---|
| Trigger | Classful boundary behavior during advertisement | Explicit interface configuration |
| Prefix selection | Class A, B, or C major-network boundary | Administrator-selected prefix and mask |
| Control | Broad and topology-dependent | Limited to the configured interface and summary |
| Typical use | Legacy classful designs | Planned aggregation in classless designs |
| Risk | Can hide discontiguous subnet locations | Can create a black hole if it covers unreachable space |
Only use a manual summary when the summarized destinations are reachable through the interface where the summary is advertised. Summaries should cover appropriate, preferably contiguous address space. A discard or null route may sometimes be used as part of a deliberate design, but it must be planned to prevent loops and unintended black holes.
DUAL and Route Information
DUAL (Diffusing Update Algorithm) is the EIGRP algorithm that calculates loop-free routes and reacts to topology changes. DUAL operates on the route information EIGRP has learned. If auto-summary hides subnet-level information, the protocol and forwarding table have less precise information to use. Disabling auto-summary lets EIGRP exchange the actual classless prefixes, improving route selection in discontiguous designs.
Exam-Relevant Points
- Auto-summary advertises subnet routes at classful major-network boundaries.
10.5.10.0/24can be advertised as10.0.0.0/8when it crosses a different major-network boundary and auto-summary is active.- A discontiguous network contains separated subnets from the same major network.
- The configuration command to disable classic EIGRP auto-summary is
no auto-summaryunderrouter eigrp. - Always verify neighbors, protocol settings, topology information, route prefix length, and next hop after a change.
- Manual summarization is explicit and preferred when aggregation is required in a modern classless design.
- Longest-prefix match prefers a specific subnet route over a broader summary when both are present.
Summary
EIGRP route summarization can reduce routing-table size and advertisement volume, but auto-summary uses traditional classful boundaries rather than the actual subnet structure. In a discontiguous network, this can cause a router to advertise or install an overly broad route such as 10.0.0.0/8, sending traffic for unrelated 10.x destinations toward the wrong router.
For modern classless IPv4 networks, disable inappropriate auto-summary with no auto-summary, allow EIGRP to reconverge, and verify that specific routes such as 10.5.10.0/24 are installed. When aggregation is desirable, use carefully planned manual summaries that include only reachable address space.
Continue with EIGRP auto-summary configuration and verification.