EIGRP Summarization and Default Routing

Summarization at a Glance

Summarization lets one prefix represent several smaller networks. It reduces routing information, hides unnecessary topology changes, and can stop EIGRP Queries at a useful boundary.

Configured onOutbound interface

Local safety routeSummary to Null0

Default summary AD5

Default prefix0.0.0.0/0

Simple meaning: Tell the neighbor, “All of these smaller networks are behind me.” The summarizing router must still know how to reach every component network it represents.

1. Build the Summary Mental Model

Imagine that R1 owns four branch LANs and sends them toward R2. Without summarization, R2 learns four routes. With summarization, R2 learns one route that covers the complete address block.

Branch LANs10.20.0.0/2410.20.1.0/2410.20.2.0/2410.20.3.0/24

R1Summary boundarySends 10.20.0.0/22

R2One EIGRP routeForwards the /22 toward R1

R1 hides the four component prefixes from R2, but R1 keeps the detailed routes needed to forward real traffic.

Key responsibility: R2 trusts R1 for every address inside the summary. If the summary covers a missing network, traffic can reach R1 and then be discarded.

2. Calculate a Safe Summary

Write the changing octet in binary and find the bits shared by every component network. Stop at the first bit that changes. The shared bits become the summary prefix.

Network	Third octet	Shared bits
10.20.0.0/24	`00000000`	`000000`
10.20.1.0/24	`00000001`	`000000`
10.20.2.0/24	`00000010`	`000000`
10.20.3.0/24	`00000011`	`000000`

1

Order the prefixes

Confirm the lowest and highest network.

2

Find shared bits

The first 22 bits match.

3

Check the range

10.20.0.0/22 covers .0 through .3.

The answer is 10.20.0.0/22 with mask 255.255.252.0. Before configuring it, list every /24 inside the range and identify any unused space.

3. Choose the Correct Summary Interface

EIGRP manual summarization is an outbound interface policy. Apply it where advertisements leave the summarizing router toward the neighbor that should receive the shorter route.

Question	Answer in this lab	Reason
Who owns the detailed routes?	R1	R1 has the real component paths.
Who should learn only the /22?	R2	R2 does not need branch detail.
Where do updates leave R1 for R2?	Gi0/0	The summary belongs on this interface.
Must every neighbor receive it?	No	Each outbound interface can use different policy.

Quick rule: Stand on the summarizing router and look toward the neighbor that should receive the summary. Configure the exit interface in that direction.

4. Configure a Summary in Classic Mode

First prove that the component routes exist. Then apply the summary on the R1 interface facing R2.

Configure R1

router eigrp 100
 network 10.20.0.0 0.0.3.255
!
interface GigabitEthernet0/0
 ip summary-address eigrp 100 10.20.0.0 255.255.252.0

Verify R1

show ip route 10.20.0.0 255.255.252.0
show ip eigrp topology 10.20.0.0/22
show running-config interface GigabitEthernet0/0

R2 should learn one internal EIGRP route for 10.20.0.0/22. R1 keeps the component routes locally but suppresses those specifics when sending updates through Gi0/0.

5. Configure a Summary in Named Mode

Named EIGRP organizes the same interface policy under the IPv4 address family.

R1 named-mode configuration

router eigrp ENTERPRISE
 address-family ipv4 unicast autonomous-system 100
  af-interface GigabitEthernet0/0
   summary-address 10.20.0.0 255.255.252.0
  exit-af-interface
 exit-address-family

Confirm the address family

show running-config | section router eigrp
show ip eigrp interfaces detail
show ip eigrp topology 10.20.0.0/22
show ip route 10.20.0.0 255.255.252.0

The forwarding result should match classic mode. During migration, compare neighbor, topology, and route output rather than assuming that valid syntax means equivalent behavior.

6. Understand the Null0 Safety Route

While at least one matching component route supports the summary, EIGRP normally installs a local summary toward Null0 with administrative distance 5. This protects against a forwarding loop.

1

Specific route exists

10.20.2.25 matches its /24 and reaches the LAN.

2

Unknown address arrives

10.20.3.200 has no component route but matches the /22.

3

Null0 discards it

The packet stops instead of following a less-specific route.

Inspect the local summary

R1# show ip route 10.20.0.0 255.255.252.0
D   10.20.0.0/22 is a summary, 00:12:41, Null0

Compare a component route

R1# show ip route 10.20.2.0
D   10.20.2.0/24 via 10.12.0.2

R1# show ip route 10.20.3.200
Routing entry for 10.20.0.0/22, Null0

Normal behavior: Null0 does not discard valid component traffic. Longest-prefix matching chooses the more-specific route before the /22 summary.

7. Leak One Approved Specific Route

A neighbor may need the summary plus one specific route, perhaps to prefer a direct path to an important service subnet. A leak map creates that controlled exception.

Select the exception

ip prefix-list LEAK-SERVICE permit 10.20.2.0/24
route-map LEAK-SERVICE permit 10
 match ip address prefix-list LEAK-SERVICE

Attach it

interface GigabitEthernet0/0
 ip summary-address eigrp 100 10.20.0.0 255.255.252.0 leak-map LEAK-SERVICE

R2 should receive the /22 plus 10.20.2.0/24. The /24 wins for matching traffic because it is more specific.

Keep exceptions rare: Leaking many routes removes the operational value of summarization. Document the reason for every leaked prefix.

8. Advertise a Default Route Safely

A default route tells a branch where to send traffic when no more-specific route matches. Tie its advertisement to real upstream reachability and use restrictive policy.

Method	Best use	Main caution
Redistribute a static default	Policy-controlled injection	Permit only 0.0.0.0/0.
Advertise a 0.0.0.0/0 summary	Default-only view on one interface	It suppresses EIGRP specifics there.

Method A: Redistribute only the static default

ip route 0.0.0.0 0.0.0.0 192.0.2.1
ip prefix-list DEFAULT-ONLY permit 0.0.0.0/0
route-map DEFAULT-ONLY permit 10
 match ip address prefix-list DEFAULT-ONLY
!
router eigrp 100
 redistribute static metric 100000 10 255 1 1500 route-map DEFAULT-ONLY

Method B: Advertise a default summary

interface GigabitEthernet0/0
 ip summary-address eigrp 100 0.0.0.0 0.0.0.0

Choose one method deliberately. Redistribution creates an external D EX default and the route map prevents unrelated static routes from entering EIGRP. The interface summary instead gives that neighbor a default-only EIGRP view.

Practical rule: A default in the branch table proves only the first routing decision. Verify the upstream next hop, security or NAT policy, and return path too.

9. Verify the Complete Forwarding Path

Start with the source of truth and move toward the receiver. This identifies exactly where a route disappeared or changed.

1

Components

Confirm R1 knows each real subnet.

2

Local summary

Confirm the /22 through Null0.

3

Receiver

Confirm R2 learns the intended route.

4

Traffic

Test valid, missing, and return paths.

On R1

show ip route 10.20.0.0 255.255.252.0
show ip route 10.20.2.0
show ip eigrp topology 10.20.0.0/22
show running-config interface GigabitEthernet0/0

On R2 or branch

show ip route eigrp
show ip route 10.20.0.0
show ip route 0.0.0.0
traceroute 10.20.2.25
ping 10.20.2.25 source Loopback0

Success criteria: Intended prefixes work, unused summary space follows the expected Null0 behavior, next hops are correct, and return traffic reaches the test source.

10. Test What Happens When a Component Fails

A summary can remain advertised while only one matching component survives. This stabilizes the upstream table, but it can hide a partial failure.

1

A /24 disappears

R1 loses 10.20.2.0/24 but retains other components.

2

The /22 stays

R2 may not see any route change.

3

Traffic hits Null0

R1 discards traffic for the failed component.

This is the tradeoff of hiding detail, not automatically a design error. Monitoring must detect component failures on the summarizer because the upstream summary can remain healthy.

11. Troubleshoot Common Problems

Symptom	Likely cause	First check
Summary absent	No component route or wrong interface	Local RIB and outbound interface.
Specifics still advertised	Wrong direction or leak-map match	Interface and route-map counters.
Valid subnet unreachable	Component route disappeared	Exact longer prefix on R1.
Unexpected Null0 drop	Summary is broader than the address plan	Compare range with allocated subnets.
Too many static routes imported	Broad redistribution policy	Prefix list and route map.
Default exists but internet fails	Next hop, NAT, ACL, DNS, or return path	Trace beyond the EIGRP route.

Write the exact destination and expected prefix length.
Find the component route on the summarizer first.
Confirm the real outbound interface and policy.
Verify the receiver route, next hop, and packet path.

12. Apply Practical Design Rules

A good summary follows the address plan. It should not be invented after deployment only to make a routing table look smaller.

Use a clear boundary

Summarize where one router owns stable paths to the components.

Choose a narrow block

Avoid including unused or differently routed space.

Monitor hidden detail

The aggregate can stay present during a component failure.

Align addressing: Use contiguous site prefixes where possible.
Document exceptions: Record every leaked route and its purpose.
Test both directions: A forward route does not guarantee a return path.
Save evidence: Compare routes and traffic before and after the change.

Continue with EIGRP stub routing to contain Queries at branches, or study EIGRP filtering and redistribution for more detailed route policy.

13. Guided Summarization and Default-Route Lab

Use an isolated three-router lab. R1 owns the components, R2 is the transit router, and R3 represents a branch.

Task 1: Build the Baseline

Create four /24 loopbacks on R1.
Advertise them in AS 100.
Confirm R2 learns all four.
Save route and topology output.

Expected result: R2 has four internal D routes.

Task 2: Add the /22

Calculate the summary.
Apply it toward R2.
Verify Null0 on R1.
Confirm one /22 on R2.

Expected result: Specifics disappear only across the selected interface.

Task 3: Fail a Component

Shut one R1 loopback.
Confirm the /22 remains on R2.
Test working and failed components.
Explain the Null0 result.
Restore the route.

Expected result: You observe stability and the hidden-failure tradeoff.

Task 4: Send a Default

Create a valid static default on R2.
Select only 0.0.0.0/0 with policy.
Redistribute it with a metric.
Confirm D EX on R3.
Test forward and return traffic.

Expected result: R3 receives one default without unrelated statics.

14. Frequently Asked Questions

Why does EIGRP create a Null0 summary route?

It prevents an unknown address inside the summary from following a less-specific route and looping. More-specific component routes still win.

When does the Null0 summary disappear?

It normally remains while at least one component route supports the summary. When all support disappears, the summary can be withdrawn.

Does a summary hide routes from every neighbor?

No. Manual summarization is attached to an outbound interface, so other interfaces can advertise different detail.

Why is the summary administrative distance 5?

The low distance keeps the local protective Null0 route installed. Longer component prefixes still win before administrative distance is compared.

Does summarization reduce Queries?

Yes. It can create a Query boundary because the neighbor sees the aggregate instead of internal components.

Should I redistribute all static routes to send a default?

No. Match only 0.0.0.0/0 unless the design explicitly requires other static routes.

What is risky about a 0.0.0.0/0 summary?

It represents every IPv4 destination and suppresses more-specific EIGRP advertisements on that interface.

When should I use a leak map?

Use it for a small, documented set of more-specific exceptions. If many routes must be leaked, redesign the summary.