VMware ESXi and vSphere Cluster Management

EIGRP Manual Route Summarization

Learn how EIGRP manual route summarization works, calculate safe summary prefixes, configure Cisco IOS interfaces, verify results, and troubleshoot routing risks.

EIGRP (Enhanced Interior Gateway Routing Protocol) is an interior gateway routing protocol that supports route aggregation. Manual summarization is the administrator-configured process of advertising one aggregate prefix instead of several more-specific routes.

This lesson covers how to calculate a correct summary, configure it on a Cisco IOS interface, verify the route-table changes, and evaluate risks such as overly broad summaries and black holes.

Why use EIGRP manual summarization?

A component route is a specific subnet included within a summary. A summary route is an aggregate prefix representing a contiguous range of destination addresses. For example, 172.16.8.0/24 and 172.16.9.0/24 can be represented by 172.16.8.0/23.

Summarization can reduce the number of entries in a remote routing table, reduce the amount of routing information that must be advertised, and make the addressing design easier to manage. Instead of maintaining many individual prefixes at every downstream router, a downstream router can use one aggregate where that level of detail is unnecessary.

A summary represents an address range, not merely a list of the component routes currently known by the summarizing router. Therefore, a router receiving 10.0.0.0/8 treats that prefix as a route to the entire range from 10.0.0.0 through 10.255.255.255 unless a more-specific route is available.

How manual summarization behaves in EIGRP

EIGRP manual summarization is not limited to major network boundaries. It can be configured on routers throughout an EIGRP domain wherever an aggregate is useful.

Configuration is per interface. The summary affects EIGRP advertisements leaving the selected interface. This allows a router to advertise a summary toward one neighbor or network segment without automatically advertising the same summary through every interface.

The EIGRP autonomous system number (ASN) is the process identifier used by participating routers. The ASN in the summary command must match the EIGRP process configured on the router.

Manual versus automatic summarization

Auto-summary is legacy EIGRP behavior that summarizes routes at classful network boundaries. Manual summarization lets the administrator choose the exact prefix and the exact outbound interface. In discontiguous or VLSM environments, disabling auto-summary is commonly necessary so that unexpected classful summaries are not advertised.

Calculate a correct summary prefix

1. List the network address and mask for every component subnet.
2. Write the network addresses in binary.
3. Compare the bits from left to right and find the longest common prefix.
4. Use the common bits to derive the summary network address and prefix length.
5. Convert the prefix length to a dotted-decimal subnet mask.
6. Calculate the complete address range covered by the summary.
7. Check whether unused or unrelated address space has been included.

Example: summarizing adjacent /24 networks

Consider 172.16.8.0/24 and 172.16.9.0/24. Their third octets are 8 and 9:

The two networks share the first 23 bits, so the tight aggregate is 172.16.8.0/23, with mask 255.255.254.0. It covers exactly the two adjacent /24 ranges and does not include the neighboring 172.16.10.0/24 network.

Example: an overly broad aggregate

Suppose R1 owns 10.5.10.0/24 and 10.20.15.0/24 and advertises 10.0.0.0/8. The /8 covers every address from 10.0.0.0 through 10.255.255.255. Most of that range is unused by R1.

This summary may reduce routing information, but it is not a tight mathematical summary of only those two /24 networks. If another valid 10.x.x.x network exists through a different path, or if a destination in the range does not exist, the broad aggregate can attract traffic toward R1. The result can be a route black hole or suboptimal routing.

Configure an EIGRP interface summary

The summary command is entered under the interface through which the aggregate should be advertised. In this example, R1 sends the summary toward R2 through FastEthernet0/1.

R1(config)# router eigrp 1
R1(config-router)# no auto-summary
R1(config-router)# interface FastEthernet0/1
R1(config-if)# ip summary-address eigrp 1 10.0.0.0 255.0.0.0

The command format is:

ip summary-address eigrp <ASN> <summary-address> <subnet-mask>

For a tighter design, the summary could instead be configured as follows:

R1(config)# interface FastEthernet0/1
R1(config-if)# ip summary-address eigrp 1 172.16.8.0 255.255.254.0

To remove a manual summary, use the negated form on the same outbound interface:

R1(config)# interface FastEthernet0/1
R1(config-if)# no ip summary-address eigrp 1 10.0.0.0 255.0.0.0

Disabling auto-summary is especially important when the addressing plan uses VLSM or discontiguous networks. It prevents legacy classful behavior from creating summaries that do not match the intended classless design.

Route-table effects

Assume R1 owns 10.5.10.0/24 and 10.20.15.0/24, and R2 learns routes from R1.

On R1, EIGRP commonly installs a local summary route toward Null0, a discard interface. This route acts as a safety mechanism: traffic matching the summary but lacking a more-specific component route is discarded locally instead of being forwarded indefinitely and creating a routing loop.

The Null0 route does not prevent a more-specific route from being used. Forwarding uses longest-prefix match, meaning the most specific matching prefix wins. For example, if a router has 10.0.0.0/8 and 10.20.15.0/24, traffic for 10.20.15.0 uses the /24 route. Other 10.x.x.x traffic may match only the /8 and follow the summary path.

Verify the configuration and operation

Use these commands on the summarizing router and the receiving router:

show ip route
show ip route eigrp
show ip eigrp neighbors
show ip eigrp topology
show running-config | section router eigrp
show running-config interface FastEthernet0/1

• show ip route displays the complete routing table, including a local summary and possible Null0 discard entry.
• show ip route eigrp focuses on EIGRP-learned routes and helps compare individual routes with the aggregate.
• show ip eigrp neighbors confirms that the intended adjacency is established.
• show ip eigrp topology shows EIGRP topology information and can help determine whether component paths are available.
• show running-config | section router eigrp verifies the ASN and whether no auto-summary is present.
• show running-config interface FastEthernet0/1 confirms that the summary is configured on the correct outbound interface.

Verification should include traffic tests to every intended component subnet. Confirm that all of them follow the summarized path and that destinations outside the intended address plan are not incorrectly attracted by the aggregate.

Summary safety and design considerations

Choose the most specific valid aggregate

A good summary includes every intended component route while excluding reachable networks that belong elsewhere. Calculate the full range, not just the first and last listed subnet. A summary that includes unrelated address space can advertise reachability the router cannot actually provide.

If another part of the network uses addresses inside the aggregate, a broad summary can compete with the correct path. A more-specific route normally wins through longest-prefix match, but if that more-specific route is missing, the broad summary may send packets to the wrong router.

Understand the local discard route

The local Null0 summary route catches traffic that matches the aggregate but has no available more-specific route. This helps prevent loops caused by forwarding unknown destinations back toward other routers. It also means that a missing component route can result in a deliberate discard at the summarizing router rather than successful delivery.

Troubleshooting

Individual routes remain on the receiving router

• Confirm that the summary command is configured on the interface facing the intended neighbor.
• Check that the interface direction is correct; summaries affect advertisements leaving the configured interface.
• Verify that the ASN in the command matches the active EIGRP process.
• Use show ip eigrp neighbors to confirm that the adjacency is up.
• Inspect the receiving router with show ip route eigrp.

Unrelated traffic is sent toward the summarizing router

• Calculate the complete address range of the aggregate.
• Look for overlapping networks or missing more-specific routes in the routing tables.
• Replace the broad summary with a tighter valid aggregate where possible.

Routes are unexpectedly summarized at classful boundaries

Auto-summary may still be enabled. Review the EIGRP process configuration and use no auto-summary when classless advertisements are required.

Some intended subnets are unreachable

• Recalculate the common prefix and verify the summary address and mask.
• Confirm that every component route exists locally and that its interface is operational.
• Inspect the routing table for the summary and its local discard route.
• Check whether traffic is matching the Null0 summary because the required more-specific route is absent.

Exam-relevant notes

• Manual EIGRP summarization is configured under an interface, not only under the EIGRP routing process.
• The summary command uses the EIGRP ASN, summary network address, and dotted-decimal subnet mask.
• A summary is advertised out of the interface where it is configured; it is not automatically sent through every interface.
• Disable legacy auto-summary for many VLSM and discontiguous-network designs.
• Always calculate the entire aggregate range and check for unintended address space.
• Longest-prefix match allows a valid more-specific route to override a broader summary.
• A local Null0 summary route helps prevent routing loops but can discard traffic for missing component routes.

For continued study, review EIGRP manual summarization alongside EIGRP route filtering, metrics, redistribution, and longest-prefix-match forwarding.