In this video lab, we're going to do three basic things.
Number one, we're going to identify how we
could do manual summarization.
Two, we'll implement the commands to do it,
and third, we'll then verify that our manual summarization
at interface boundaries with EIGRP is working.
Let's begin.
So let's devise a plan together, and here's
what I propose we do.
Down here in this--
I'm going to ignore that link for a little bit--
down here in this part of the network, it is all 10.1.x.x.
So it starts with 10.1, and over here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So it starts with 10.1, and over here
on this leg of the network--
over here is 10.2.x.x, with the first two octets being 10.2.
So this-- if we laid EIGRP on top of this,
which I propose we do--
so we could summarize all the routes down here that
begin with 10.1, out gig 1/0 and also fa 4/0,
and we could also tell R4 to summarize any routes that
start with 10.2--
summarize them to a 16-bit boundary out here.
What would be happening is, initially, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
What would be happening is, initially,
once EIGRP is in place and before we do the manual
summarization, R1 would have all the detailed routes
for 10.1-everything and 10.2-everything.
And after a summarization they would have a 16-bit route
for 10.1-everything and 10.2-everything,
and they wouldn't have the detailed routes.
That's the game plan.
Now the syntax to do this is interface configuration,
and the command is ip summary address.
What I'd like to do is walk you through implementing WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
What I'd like to do is walk you through implementing
traditional IPv4 EIGRP.
In the next video, we'll do named EIGRP, but this
will be the traditional EIGRP for IP version 4,
then we'll verify the routes to begin with,
then we'll implement the summarizations
and verify that they work.
And when it doesn't work, or if it doesn't work in the lab,
that's an opportunity for troubleshooting as well.
So here in the lab let's open up a new notepad document.
And we can use that for the base config that we're
going to use everywhere.
And I would recommend you follow these instructions,
as well, as we implement EIGRP across the network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
as well, as we implement EIGRP across the network.
So we'll will go into configuration mode
and, to get all the interfaces that we want to, here's
what I do.
Let's do router eigrp autonomous system 1,
and let's use network 10.0, and I'm
going to copy that twice more--
copy it once and paste it twice more, I should say.
And let's do 10.1 and also 10.2.
And that way we're just going to involve the interfaces WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that way we're just going to involve the interfaces
that we want to.
Otherwise, you could do everything and then go back
in and do passive interface, but let's do this
so we can focus on our summarization tasks
in this lab.
So looking at that, that looks good.
And auto summarization is off by default.
So let's do a Control-8 to select all that text.
We'll do a Control-C to copy it, and then we'll just paste it
onto each of our routers.
There's 2, 3, and 4, and 5, and 6, and 7, and 8.
It still cracks me up how darn fast convergence is with EIGRP. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
It still cracks me up how darn fast convergence is with EIGRP.
I mean, R8 knows everything.
"I know everything!"
No IP route for EIGRP learned routes-- it's just done.
And if we go to R1 and ask about the routes, so ip route eigrp,
it knows about the detailed routes of 10.1.5, 10.1.7,
10.1.35, 10.1.57, and so forth for the 10.2s--
lots of networks down there.
So what we'll do--
I'm going to bring you back to the topology
so we're on the same sheet of music.
On R3 we'll create summaries.
We'll do it on two interfaces, because if we don't do WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We'll do it on two interfaces, because if we don't do
summaries on both interfaces, then we'll be advertising
the detailed routes over here, and our [INAUDIBLE]---- anyway,
so long story short, we're going to advertise those summaries
on gig 1/0 and fa 4/0 on R3.
We'll start there.
So we'll go to the right device-- always important,
and we'll go to configuration mode.
And I'm going to do this in Range Config,
because that way we can do the command once
and it'll apply to both interfaces.
So Interface Range, and let's go to gig 1/0, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So Interface Range, and let's go to gig 1/0,
and also fast ethernet 4/0--
so far, so good.
Here's the syntax for our manual summary for our EIGRP.
It's ip summary-address-- we're going
to specify it's for EIGRP because we're not running RIP.
Now we're going to specify the autonomous system
number in a peak up here.
Looks like autonomous system number 1 we used-- great,
and then we're going to put it in the summary.
So in R3 we'll say, we want you to summarize 10.1,
and then we'll use a /16, and that's our summary.
Ta-da! WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Ta-da!
Now check this out.
If we do a show ip route for EIGRP-learned routes and press
Enter there--
I want to point out something really important,
and that's this bad boy right here, this discard route.
Because we created a summary this router also--
bada bing-- via the same front running protocol
created this summary route that goes to null zero.
And here's the reason that route's important.
Let's imagine that a packet to 10.1.90.5 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's imagine that a packet to 10.1.90.5
gets sent in this route or receives it.
Well, it looks at this routing table for the longest match.
And if we didn't have this route that put it in the bit bucket,
and if this router had a default route, it's possible--
not possible-- this route router would,
without this route going to null 0 would forward that
to the default route, and then that would be cycled through--
we could have a loop.
This just basically tells the router,
listen, you know summary you advertised?
You don't have a more detailed route in your routing table
for the packets to come in?
Boom.
Kill it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Kill it.
And that's what this does right here.
So let's go ahead on R4, getting back to our topology,
and on R4 we'll create a summary on gig 2/0
and fa 4/1 that advertise these networks down here
on the bottom right, which is the 10.2 networks that it knows
about.
So let's do that on R4.
So here on R4, let's go ahead do a show ip int brief--
I want to make sure I'm on the right device-- good enough.
Then we'll go to configuration mode, and interface range,
and we want gig 2/0. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and we want gig 2/0.
I want to make sure it's right on my topology as well.
Yeah, gig 2/0 and fa 4/1--
so gig 2/0 and fa 4/1--
and we're going to do an ip summary-address,
and we'll specify eigrp autonomous system 1.
What we're summarizing is the 10.2s.
We'll go ahead and put 10.2.0.0 with a 16-bit mask, and boom.
Boom, our summary's created.
We do a show ip route eigrp.
There's our discard route right there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
There's our discard route right there.
And as a result of those two summaries,
if we go back here to R1 or R2 and we'd say,
show us the routes, they're going to have,
instead of more detailed rules for 10.1
and a whole bunch of detailed routes,
they'll just have 10.1 with the 16-bit route and a 16-bit mask,
and then 10.2.
And everything else will be suppressed or hidden
by those routers that are advertising the summaries.
So here we are at R1.
So this is the routing table from a few minutes
ago, before we had the summaries.
We have some routes for 10.1, et cetera, down here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We have some routes for 10.1, et cetera, down here
and we have routes for 10.2, et cetera,
and those 24-bit routes should all be gone.
You should just have the 10.1.16 and 10.2.16.
Let's verify that with show ip route or EIGRP-learned rules,
and survey says boom--
we have a 10.1.16 and a 10.2.16, and that's it,
because of the summary that we're
doing manually on those interfaces on R3 and R4
respectively.
So this is an opportunity. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So this is an opportunity.
If you'd like to practice with this, I encourage you to do so.
And in the next video, we're going
to do manual summarization again,
but we're going to do it with named EIGRP, which may
be fairly newer to many of you.
So I'll see you in that next video and lab in just a moment.
Meanwhile, I hope this has been informative for you,
and I'd like to thank you for viewing.