EIGRP Floating Summarization

When you create summaries in EIGRP, the router automatically creates a route that points to a Null 0 interface.

This Null 0 interface serves as a bit bucket to prevent the router from forwarding traffic for destinations inside the summary address that it doesn’t have a longer match for. This is also known as Null routed.

This is true for OSPF and BGP summarization as well..

The administrative distance for summary routes have an AD of 5 by default. Knowing this we can configure a route with an AD of 1-4 to take precedence over our summary route.

Here is what I mean.

A simple EIGRP topology with R4, R5, and R8. Full EIGRP connectivity between nodes.

eigrp.summary0.PNG

Note: Lo1 has been created on R4 and R5 and advertised into the EIGRP process.

Lets configure a default route on R4 Ethernet segment towards R5.

eigrp.summary

On R5, let’s check for the route to R4 Lo1 – 160.1.4.4. R5s CEF table matches our summary route to reach 160.1.4.4

eigrp.summary1

Let’s check on R8. R8 just like R5 has a CEF entry for 160.1.4.4 that matches the summary route 0.0.0.0/0 that R4 generated. R8 and R5 don’t have a specific route for 160.1.4.4 because the summary route it suppressing the more specific route from being install into their routing tables, which is why we need to consult the CEF for the route.

eigrp.summary2.PNG

R8 can pint 160.1.4.4 as of now.

Let’s configure a summary address for the Lo1 prefix’s on R5 for R8 on the shared Ethernet segment between them.

eigrp.summary3.PNG

Below you can see that R8 received our new summary address for the Lo1 prefixes. We can see this in the out put 160.1.4.0/23. Lets try to ping 160.1.4.4 – R4s Lo1.

eigrp.summary4.PNG

eigrp.summary7

Pings to R4 – 160.1.4.4 fail. Pings to R5 – 160.1.5.5 are successful because R5 has this address locally configured.

Lets see what R5 has to say about the route to 160.1.4.4.

eigrp.summary5

We can see that R5 can reach 160.1.4.4 via Null 0. Lets ping 160.1.4.4.

eigrp.summary6.PNG

This can’t work! Our packets are Null routed!

So to get around this lets configure a static route on R5 to R4 for 160.1.4.4.

eigrp.summary8.PNG

R5 now knows about 160.1.4.4 with a AD of 1. Let’s see if this fixes R8s reachability.

eigrp.summary9.PNG

R8 can reach 160.1.4.4!

This could have also been solved by poisoning the Null 0 interface from R5s RIB with an AD of 255.

eigrp.summary10.PNG

The difference here is that the Null 0 interface found on R5 is completely removed from the routing table.

Credit: INE

Mike

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s