In the previous video, we looked at the classics with EIGRP
for IPv4 and IPv6.
In this video and hands-on lab, we're
going to focus on address families
as part of named EIGRP configuration.
[MUSIC PLAYING]
So this is the topology where we're
going to implement IPv4 and IPv6 with named EIGRP configuration
using address families.
I thought to make this a little more fun
and also to give us more hands-on practice and diving WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and also to give us more hands-on practice and diving
into the individual containers for address
families and their properties, let's also do this.
Let's specify that on R1 that the loopback
0 will be a passive interface.
Now to do that, it is going to require us
to go into the address family.
And I want that passive for IPv4 and IPv6
so we can experience that both ways.
So on R1, loopback 0 should be passive,
and, and here's what I see.
I noticed that-- let me get a little different color here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I noticed that-- let me get a little different color here.
Fantastic.
I noticed that on R8, when we were doing the show commands,
or when I did the show commands earlier for routes,
I saw that it had two successor routes.
And I can't remember which ones they were.
So we have three possibilities here, A, B, and C.
And I recall for IPv4 and IPv6 regarding this network up here,
the 10.01 or the 2001:DB8:6783:1 for IPv6 that it had two
successor routes and it had one that wasn't being used.
So here's what I'd like to do.
On R8, regarding this network up here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
On R8, regarding this network up here,
we'll call it target network x, x marks the spot,
I'd like us to play with the variance for both IPv4 and IPv6
so that R8 will use all three routes.
Now if we set the variance-- and also, if the feasibility
condition has been met, which means the advertised
distance for a route is lower than our current feasible
distance.
So assuming that's all proper and all met,
I would love to have all three interfaces participate. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I would love to have all three interfaces participate.
And at that point, if the variance is high enough
and we meet the feasibility condition,
we are going to have proportional load balancing up
to this network up here for IPv4 and IPv6.
And that's going to give us an opportunity on R8--
most important part here--
of going into the address families
and sorting out where do we configure the variance?
It's going to be somewhere under the address family.
So we use some context-sensitive help to get there.
So if you're for challenge, you're
welcome to right now go ahead and launch this lab WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
welcome to right now go ahead and launch this lab
and go for it for IPv4 and IPv6 with the loopback 0
on R1 being passive and R8 eight using all three routes,
proportionately, by modifying variance.
And you're ready-- so go ahead and pause me
if want to do that.
Work on the lab.
And then when you're ready, go ahead and click on resume.
And what we'll do together is we'll
walk through this solution with named EIGRP configuration model
so either way is great.
And I'll see you in just a moment for the walkthrough.
WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
All right.
So here we go.
So here's our named configuration.
It hasn't changed from previous.
So we can use it again.
I don't have any routing protocols running.
Let's just do a quick check.
Show IP protocols for IPv4, show IPv6 protocols.
Great.
So we have a starting point with no dynamic routing protocols.
Fabulous.
So let's do this whole thing.
We don't really need to remove the older ones.
They're gone.
But IPv6 unicast routing, we'll do a EIGRP Our-Named-EIGRP. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But IPv6 unicast routing, we'll do a EIGRP Our-Named-EIGRP.
Autonomous system 4, all networks.
And then we'll bring in all the IPv6 interfaces, as well.
Right click on that.
Copy.
And then let's go to R1 and--
hold on a second.
Let me make sure I have everything.
Let me also go to end here.
Yup.
And that way I can go to out of configuration mode.
And then we'll do our tweaks.
So copy R1.
Boom.
R2, R3, R4.
And when you do this lab, you're welcome to do it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And when you do this lab, you're welcome to do it
all manually if you want to.
Perfectly fine.
And we should have adjacencies for IPv4 and IPv6 everywhere.
And that looks great.
So I've got three neighbors with IPv4 on R8,
and three neighbors for IPv6.
Sounds great.
And we do a show IP EIGRP neighbors for IPv4 and show
IPv6 EIGRP neighbors.
Now what we can do also, and this is also WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now what we can do also, and this is also
reminiscent of OSPF v3 with its address families,
we can also do a show EIGRP space.
And then we can specify the address family.
And then IPv4.
And then continue it on with interface.
And what that does, that gives the same output
as this command, show IP EIGRP interface.
So the output is the same.
So it's just two different ways of issuing the same request.
So for IPv6, it'd be show IPv6 EIGRP interfaces, like that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So for IPv6, it'd be show IPv6 EIGRP interfaces, like that.
Or we could also do show EIGRP address family IPv6 interfaces.
The output is going to be the same.
So it's important to realize that, like in OSPF version 3,
some of the IPv4 commands no longer worked.
But here, with address families currently with EIGRP,
both sets of commands for IP and IPv6 work,
as well as the new ones that invoke the actual address
family itself. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
family itself.
All right.
So let's tackle the question or the problem
of a passive interface up on R1's loopback 0.
To do that, we'll go up to R1.
Get on the right router.
That always helps.
And lets just verify our tables.
Show IP route or EIGRP learned routes.
Lots of routes there.
And show IPv6 route for EIGRP learned routes.
All right.
Fantastic.
So let's do this.
Let's do a show run section router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's do a show run section router.
And let's decode this together.
So here is our named configuration for EIGRP.
And then here we have the subsection four unicast
IPv4 for autonomous system 4.
And then we have this thing called topology base.
There's nothing in it.
That's why this exit is right after.
And then we have a network statement that says,
which interfaces are going to come in?
In this case all, IPv4 interfaces.
And then we have this exit address family,
indicating we're stepping out.
And then we have this next one here,
address family IPv6, which implies
we're now going into that section WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we're now going into that section
of the config for IPv6 traffic using autonomous system 6.
And then topology base and out because currently empty.
We'll fix that here in just a moment.
And then exit out.
So if we wanted to do a passive interface,
we would want to do it under the IPv4 section
and also under the IPv6.
But we'd also want to go to the correct subcategory.
So we'll go into configuration mode.
And I'm just going to copy, paste this router
EIGRP named EIGRP.
That will save us some typing.
I'm then going to go into the address family, or IPv4, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'm then going to go into the address family, or IPv4,
by copy, pasting that.
And then, let's go ahead and do a question mark.
Now the way we do a passive interface is we're
going to go into another subcompartment.
And that is the af-interface.
"Enter Address Family interface config."
So we type in af-interface.
And then it says, OK, great, af interface, which interface?
And if we want to work with loopback 0,
we'll say loopback 0.
Press Enter.
So if we do a question mark here,
here's where we have passive interface. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
here's where we have passive interface.
We'll do a passive interface.
Press Enter.
And now that interface is a passive interface within EIGRP
for autonomous system number 4.
And notice this says it's going to suppress updates
on the interface.
There's also an option for shutdown.
So if we didn't want that interface
to participate at all, including its directly connected network
as part of the EIGRP routing process,
we could use a shutdown option.
And it's not going to shut down the physical interface.
It's just going to shut down the EIGRP processing
for IPv4 on that interface. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for IPv4 on that interface.
All right.
So there is the change that we just made.
Fantastic.
And we also want to go ahead and do a passive interface
on the IPv6 side of the house.
So I'm going to go ahead and copy this line right here.
And we'll do a question mark.
And here we're also going to type in af-interface.
Again, we're going to go work with loopback 0.
And now we'll do a question mark.
And here we have passive interface or shutdown.
So if you didn't want that network on that interface
to be part of IPv6 because they're all enabled by default,
that would do it.
So we do a shutdown there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we do a shutdown there.
And in fact, let me do a do show run interface for a loopback 0.
[LAUGHTER]
Well, it was a good exercise.
We don't have an IPv6 address on that interface to begin with.
We only have an IPv4 address.
So as far as being passive, there's
not too much of a chance the loopback interface is
going to get a neighbor.
And doing a shutdown loopback that
doesn't have an IPv6 address isn't
going to get us too far anyway.
However, it did give us practice doing the commands.
Let's take a look real quick.
And let's do a do show run section router, once again, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's do a do show run section router, once again,
just to make sure it all took.
All right.
So there's our named configuration.
There's our passive interface for version 4.
There's our shutdown for loopback 0 for version 6,
although it doesn't have an IPv6 address yet.
And we are good to go.
All right.
The other task I want to-- and we could do
is show IP protocols.
And here it's showing EIGRP 4.
Its showing part of our named configuration,
where it came from. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
where it came from.
And it's also showing us that we have
a passive interface of loopback 0, which is fantastic.
Now the other task I wanted us to do was on R8.
I'd like to use all three routes.
And as we're forwarding traffic up here
to 10.0.1, or to the IPv6 equivalent of 10.0.1
up on the top left.
So to do that, we are going to have to first of all,
see if we have a feasible successor who meets
the feasibility condition.
And then secondly, we're going to have
to tweak the variance enough so that it can go ahead and start WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to tweak the variance enough so that it can go ahead and start
using that lesser route in its routing table.
So let's go to R8 and we'll check that out.
This will be a good rehearsal and reinforcement
for EIGRP concepts.
So R8 we go.
So to R8 we go.
And let's do a show IP EIGRP topology.
We're going to have a very similar experience with IPv6,
as well.
So you can choose your protocol and then focus on that.
So 10-- let's see here.
I'm looking for 10.0.1.
There it is right there.
And here's the feasible distance. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And here's the feasible distance.
We got a comma there and a comma there.
1.7 million.
Awesome.
OK.
So there's our feasible distance.
That's the metric.
If we looked at the routing table,
that's what it would show.
And it currently says we have two successors,
meaning we have two routes that are currently
in the routing table.
And it's these two routes based on both of them
having that feasible distance.
And then over here, we have the advertised distance.
So the reason that this third route with the next hop of .3
is not being used is because it has a worse metric effect. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is not being used is because it has a worse metric effect.
There's a comma, comma, 11.
Yeah.
Its metric is 11 million versus 1.7 million.
And so it's not being used.
But right here, the advertised distance
that's coming in from R3, based on that IP
address, the advertised distance is less than
the current feasible distance.
That means that this route right here meets
the feasibility condition.
It can be used if variance is set high enough. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
It can be used if variance is set high enough.
So if we take a look at--
wow.
So I guess the question is, how many times does this number go
into that one?
We'll tend to it.
Yeah.
If we take this number out here and we just say times 10,
it's going to be 11,743,000, which will just barely include
that third route there that's not quite in.
So we need to set the variance for 10
in order for that route to be included in the routing table.
And let's also while, we're at it, let's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's also while, we're at it, let's
verify that for IPv6 as well.
Let's do a show IPv6 EIGRP topology.
And the other command, as a reminder,
we can do a show EIGRP for the address family IPv6.
And then topology.
And that will give us the same output.
So you can run it either way you want.
Both commands currently work, which is great news.
So we're looking for the 1 network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we're looking for the 1 network.
And that's this bad boy right here.
So it has two successors.
And, wow, 1.7.
Is that the exact same metric as it was for IPv4?
I'm going to go check real quick.
Let me just scroll up.
So ending in 638.
Look at that.
All right.
Same exact metrics.
We the same exact scenario but for IPv6 regarding this network
right here.
So we have two successor routes.
And then we have these guys.
Then the third one right here is not being used. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Then the third one right here is not being used.
And it is off by about 10 would do it.
So if we set the variance to 10, or EIGRP for version 4,
for that address family and also for IPv6, both of those, IPv4
and IPv6, that third route should show up and be
placed in the routing table.
Let's verify those real quick.
Let's show IP route 10.0.1.0.
And there's our two winning routes.
Great.
And then if we do a show IPv6 route,
press Enter, there we go. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
press Enter, there we go.
So we have two paths there, as well.
OK.
So let's do a show run section router.
And let's go tweak the variance and set the variance to 10
or higher on both of them.
So to do that, we'll going into configuration mode.
And we'll go into named configuration mode for EIGRP.
We'll go into the autonomous system 4.
And now the question is, where exactly do we
go in to do the variance?
One option would be a question mark.
No variance here.
But it's the topology option that we want, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But it's the topology option that we want,
where we can set the variance.
So we're going to type in topology and question mark.
I pressed Enter.
And we're going to use the base topology.
So if we go back and look at our router config,
it was topology base.
So that's the compartment or container
in this address family where we're
going to set the variance.
So we'll hit Tab.
And now we're in topology base.
And from here, we have several options,
including commands regarding auto-summary
and default-information.
And what we want is the one that starts with v, variance. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And what we want is the one that starts with v, variance.
And we are going to set the variance to at least 10
to make sure that third route which meets the feasibility
condition can actually be placed in the routing table.
So we'll do a variance of 10.
And then we'll type in exit.
Exit.
And then we'll go into the address family or IPv6.
I'm going to use a gun.
So IPv6, unicast, and autonomous system.
I think we were using 6 for that.
You don't have to, but I used 4 for IPv4 and 6 for IPv6 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
You don't have to, but I used 4 for IPv4 and 6 for IPv6
to help me remember.
That just came in helpful.
And press Enter.
And then from here, we'll do topology base.
And then from here, we'll do variance.
And set it to 10, as well.
All right.
So now that we've done that, if we
do a show IP route or 10.1.1.0, which is the IPv4 route
the top left-hand side of our network, check it out.
Now we have three routes that all made it
in the routing table.
Our next hop of .7 and next hop of .3, and the next hop of .6. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Our next hop of .7 and next hop of .3, and the next hop of .6.
and if we look at the traffic share count,
these are our two winners.
They're going to be proportionally load balanced.
We have more traffic sent on those two links
compared to this one.
So about seven times three.
Each of these links is going to have about seven times as much
as this link right here based on the ratio of their traffic
share count All right.
So let's verify this.
Let's verify the actual proportional load balancing.
Let's do a trace. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's do a trace.
I'm going to press Enter.
If you'll all follow along in the lab, that's great.
And by doing this, we can display a large number
of probe numbers.
So target IP address is going to be 10.0.1.1.
That's router 1 gig 00 address.
And I don't care about the source.
My source.
Display numeric rate.
Timeout 3 seconds.
That's great.
Probe count.
Let's do 100.
And then away we go.
So the goal here is, I want to see .3
as a rarely used next hop that's in this path. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
as a rarely used next hop that's in this path.
Where .6 and .7, if you look at the topology here--
and I'll let that complete.
So most of the traffic should go through .6 as the next hop,
or .7 as the next hop, and occasionally, .3.
So .3 should be seen a lot less than .6 and .7.
So let's take a look.
So here we go.
If we circle--
I'm going to use this color and circle the threes.
There's three, there's three, there's three.
OK.
Great.
And all the others are seven and six and seven and six WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And all the others are seven and six and seven and six
and seven and--
oh, and then we're off to the next hop.
OK.
So everything past this point is the next hop in the path.
But look at all the packets that were involved.
So for the .3, it got these and it got these and it got these.
But for the .7, it had all these packets.
And for .6, it had all these packets.
And actually, it extends to the line below it as well.
So the key here is that the load balancing proportional load WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So the key here is that the load balancing proportional load
balancing is happening as we expected it to,
giving a lion's share .7 and .6, as those next hops, and dot
three, now a very small portion of that.
So thanks for joining me in this hands-on lab, where
we had the opportunity to configure and verify
named EIGRP configuration for the address families
of IPv4 and IPv6.
I'll see you in the next set of videos.
Meanwhile, I hope this has been informative for you.
And I'd like to thank you for viewing.