In the previous video, we walked through the implementation of EIGRP using the
traditional method.
So in this video, we're going to remove that config and then walk through the
implementation of EIGRP.
But this time, use named EIGRP.
So if you brought the lab up in the previous video or if you're bringing it now
and you want to do this along with me
or if you want to wait to the end, it's all good either way you want to do it,
but please get the hands on practice.
So to remove the current EIGRP and put the new named EIGRP, what I'm going to
do is go back to this text document.
So this is on server one nug and this is the document called EIGRP configs WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So this is on server one nug and this is the document called EIGRP configs
sitting on the desktop just to confirm that where it's at.
We'll minimize that, minimize that.
It's this little document right there EIGRP configs.
So with that open, let's go down a little bit and this part right here, the
second part is going to remove all the routing protocols, including EIGRP.
And then walk through the implementation of using EIGRP with address families.
So this part right here is all about getting rid of anything that might have
been there previously starting off fresh. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
been there previously starting off fresh.
And then here is how we're going to configure named EIGRP.
We start off with the name router EIGRP space and then you give it a name that
you want to use.
And then once you're there inside named EIGRP, it can support both IPv4 as well
as IPv6.
So because we're focusing on IPv4, the first thing we'd want to do is specify
okay for address family IPv4.
I want to use the autonomous system number of 100 and then you would use
network statements once you're in this address family for IPv4 just like you WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
network statements once you're in this address family for IPv4 just like you
would with the traditional flavor.
So whether you want to use every interface with network 0, 0, 0, 0 or network
10 and these wild card bits either way is great.
And then once you're done, boom, we now have EIGRP running.
But this time we're using our named EIGRP.
And within the address family for IPv4, we're using AS100.
So I'm going to go ahead and scroll up a little bit. I'm going to go ahead and
copy that entire section.
So this is what I currently have. I'll right click. I'll copy that and then I
'll go back to multi tab buddy. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
'll go back to multi tab buddy.
So I'll click on the icon in the taskbar to get there. And then I'm going to
use this option once again.
So I'll click here for send script and then I'll go ahead and right click.
I'll paste in all those commands. I'll click on select all and then I'll go
ahead and scroll down and say, you know what?
We don't want to send that to PC 7 or 8 or PC 1 because they're not routers.
They won't know what to do with it.
And so with router 1 through 8 selected and the script input here will go ahead
and click on send script.
And that's going to remove any routing that may have been there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that's going to remove any routing that may have been there.
And it's going to implement named EIGRP. And then it looks like I didn't have a
carriage return up from my end.
So I'm going to go back here and press enter here in the script section. Select
all send it and little PCs won't care if they get it enter.
So once again now that we have it configured we can do those same types of
commands. So if we go to our four, it's good our four.
So here in our four we do a show IP protocols in press center. It'll show us
our protocols that are running for IPv4.
So here's showing us EIGRP 100 is showing us the K values that is using again WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here's showing us EIGRP 100 is showing us the K values that is using again
the K1 represents the minimum bandwidth in the path and K3 reports to some of
the delays.
And another way of seeing some of those values that are being used is spring
back to topology for a moment.
So we're looking at the loop back down R8. If we did a show IP route for 8.8.8.
8.8 and press enter.
Here's the routing information for that route. It was learned via EIGRP 100.
Here's the current metric for that route. And another name for that metric
would be the feasible distance.
That's the calculation involving the sum of the delays and the lowest link in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
That's the calculation involving the sum of the delays and the lowest link in
the path.
And if you're wondering, well, what is the total delay and what is the minimum
bandwidth in the path right here showing us in the show output for the show IP
route showing us the total delay is looks like 20,000 and 32 microseconds.
And the minimum bandwidth in the path is 64. And if we looked at that route for
8.8.8.8 and we looked at it from R1's perspective, even though R1 isn't
directly connected to any 64K links, that information would have been reported WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
directly connected to any 64K links, that information would have been reported
regarding the worst link in the path.
It would have been reported by R2 or R3 because that's also what they believe
the worst link in the path is because that's what they were told or in the case
of R3, it's directly connected and learning the route on that 64 bit network.
And to verify that, let's just go ahead over to R2 and R3. So we'll go to the
tab for R2 and R2. Let's do a show.
Back here, check this out. We need this to. Let's go ahead for all the routers
and I click up here again. And let's do a show IP route for 8.8.8.8.
And press enter a couple times and let's send that to everybody except for the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And press enter a couple times and let's send that to everybody except for the
PCs because they're not routers. They want to do it with it.
But we'll send that command to all of them at once. Do send script and then we
'll look at R2.
So here on R2 with the R2 tab selected, we can see the minimum bandwidth is 64K
. The other router was R3. So if we go to R3 and we look at the minimum link in
the path is 64 bits, again, it's because that has been advertised as the worst
path from their neighbors if they weren't directly connected to those networks.
Also, over here, R3 is reporting a total delay of 20,000 and two microseconds. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Also, over here, R3 is reporting a total delay of 20,000 and two microseconds.
And if we go to R2, R2 is reporting a delay of 20,000 and 22 microseconds.
So the delay that goes into the calculation is less from R3. So if we go to R1
and look at the route, that's why it's using .3 as the next hop because after
the calculation was all done, that had the lowest metric.
We can verify that with a show, IP, EIGRP, topology, press enter, and I'm going
to hit space bar. So here is our route. Now this P on the far left, that means WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to hit space bar. So here is our route. Now this P on the far left, that means
it's passive.
I mean, it's not actively trying to learn where that route is. It's pretty
stable in the routing table. And that's why there's a P there for passive. It's
saying there's one winning route. And the final metric is this one right here.
So if we count all the characters there, 11 billion, 551. So there's the
feasible distance right there again. And the reported distance that came in
from R3, the reported distance based on the sum of the delays and the worst
link.
When R1 calculated that based on the reported information, it came up with that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
When R1 calculated that based on the reported information, it came up with that
metric. So that's the advertised distance or reported distance that R1 is
receiving from R3 regarding that route to 8888.
And the cool thing is most of the show commands are going the same regarding IP
v4, EIGRP, whether or not we implemented it as traditional EIGRP or whether we
used named EIGRP.
So as a reminder, if you do a show run, pipe section router, press enter and
give that a moment to process that'll show us the running config regarding our
router configuration. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
router configuration.
So all we typed in was our named EIGRP. We went to address family for IPv4 Unic
ast for a time system 100. And then we did nothing with the topology base. We
left it as default. And then all we did was specify network 0, 0, 0, 0. And
everything else you see here is based on the defaults.
So again, the commands can be show IP EIGRP interface and also in the notepad
document. If you're doing this lab with me, if you scroll the bottom, I have a
whole bunch of relevant show commands you might want to play with.
So we could just show IP EIGRP interface. We're going to show IP EIGRP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we could just show IP EIGRP interface. We're going to show IP EIGRP
neighbors to see who our neighbors are.
Another cool option is show IP EIGRP topology all links now by default there is
something called a feasibility condition. In fact, let's find a router and let
me tell you about that right now. Let's go to R4.
And here on R4, let me bring up the topology. Let's look at it real quick. So
here on R4, it is learning about the 8888 network from R2 and from R3 and also WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
here on R4, it is learning about the 8888 network from R2 and from R3 and also
from R6.
So if we did a show IP EIGRP topology and press down or and I'm going to go
down a little bit and take a look at 8888 and I'll just go ahead and do Q for
quit.
So here knows about that route. There is the metric for it, which is like 11
billion 552. And that is the winning route right there.
So that feasible distance for the successor out is the metric that it has for
this route that it learned based on that last octet coming from R2.
So this is the feasible distance for the successor out. There's the effective WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So this is the feasible distance for the successor out. There's the effective
result of the details from the reported distance coming in from R2.
And we have two feasible successors. These two routes did not make it into the
routing table because they didn't have a better or lower final metric or
feasible distance than the prior route.
So let me tell you about these two feasible successors that could if the
primary successor out goes way that they could be installed in the routing
table.
The reason these two routes are here and being shown even though they're not
the winning routes or feasible successors, they could be winning routes if the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the winning routes or feasible successors, they could be winning routes if the
primary route goes way is because they meet something called the feasibility
condition.
And here's what the feasibility condition means. So we're focusing on R4. So
far four has three potential paths that it can forward to get to 8888. One has
a better metric and that's going to R2.
So I'm going to put R2 here as the successor out. That's the winner route. So
our four of these four of the packet is going to forward to R2.
But where are the other two potential paths are dot six and that's our six
based on that last octet and R3. So I'll draw the 8888 network down here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
based on that last octet and R3. So I'll draw the 8888 network down here.
So in these three routes are reporting that information. They're all reporting
the sum of the delays. That's the K3 aspect regarding the metric calculation.
And they're also reporting the minimum bandwidth in the path and that's the K1.
So as R6 and R3 are reporting that information if and only if the result of the
calculation that R4 is doing based on the reported distance coming from R6 and
R3.
Only if that information the reported distance and I'll go ahead and get arrows
here as well. That reported distance is right here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
here as well. That reported distance is right here.
So there's a reported distance coming in from R6 and here is the reported
distance coming in from R3 based on those last two octets.
So the feasibility condition says I will consider them as usable routes if
these advertised distances here also known as reported distances are lower than
the current feasible distance or the current metric for the successor route.
So we look at this number here 11 billion 552 here we have 11 billion 550. So
that reported distance coming in from R3 is lower than the current final metric WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that reported distance coming in from R3 is lower than the current final metric
for the winning route.
And the route being advertised without six is significantly lower than the
final metric. So as a result these two routes are considered feasible success
ors because they meet the feasibility condition that is the reported information
coming from R3 and R6 when R4 to the calculation based on that reported
distance their reported distance is lower than the value of the metric for the
winning route.
So this is the feasible distance right here for the winning route and these two
right here are the reported distances and the calculation based on that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
right here are the reported distances and the calculation based on that
reported distance information coming in from R6 and R3.
And that's going to be true for all the feasible successor shown. So here we
have one successor for the 1001 network. There's the feasible distance.
Here is that winning route right there feasible distance again on the right we
have the advertised or reported distance that's coming in from the neighbor.
And this metric right here which is way higher than the successor metric and
that's why it's not in the routing table. The reason is here is because this
advertised distance the reported distance if you will coming in from R3 is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
advertised distance the reported distance if you will coming in from R3 is
still lower than the final metric for the winning route.
So because it's lower they reported distance coming in from R3 it is considered
a feasible successor. So if we had another route that came in and the reported
distance was higher than our current metric for the winning route we wouldn't
even show it here by default because it doesn't meet the feasibility condition.
Now there is one other command let me go ahead and create a screen. There is
one other command we could do if you want to see the additional routes that don
't meet the feasibility condition.
You could go into a show IP EADGRP topology and then a question mark and the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
You could go into a show IP EADGRP topology and then a question mark and the
option is right there all links. So I could type in all dash links press enter
and that's going to show us every single route the successor routes and
feasible successors.
It's also going to show us routes that are not feasible successors. So just to
compare and contrast that real quick we do a show IP EADGRP topology press
enter and let's take just look at the first five or six routes there.
And we do it again with the all links press enter and there is a difference. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we do it again with the all links press enter and there is a difference.
Let's just scroll up and see where that difference is without the all links.
Let's take a look at the 1017 network. We have a successor route and that's
this one right here.
And then we have a feasible successor right here and that's because this value
right here the report distance is lower than our current final metric and this
is making it in. However, when we did the show IP EADGRP topology and we use
the option of all links we take the same network look at this is now showing us
three.
So we solve one successor that's this route right here coming in for two and we
saw the feasible successor right here but look at this one this route which is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
saw the feasible successor right here but look at this one this route which is
advertised by our six based on that last octet of dot six right there it's
reported distance it looks like 11 billion 557 which is way the heck higher
than the current metric for the winning route and as a result this route right
here is not a feasible successor and that's why it wouldn't show it to us by
default.
We did the command again with show IP EADGRP topology and no all links option
press dinner and then we look at that 10.17 route it's showing us the successor WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
press dinner and then we look at that 10.17 route it's showing us the successor
route which is through dot two and the feasible successor which is dot three
but it's no longer showing us we scroll up it's not showing us the non feasible
successor here going through dot six.
We've got all these commands you want to practice and play with them in the lab
assignment I put all them right here as well so we did a show IP EADGRP top
ology from our four and let's take a look at our topology once again so from our
four let's look at the details for network eight eight eight eight which is
loop back down on our eight.
We just show EADGRP topology until we get the eight eight eight network here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We just show EADGRP topology until we get the eight eight eight network here
showing us that we have one successor one winning route there's its feasible
distance or metric and then we have two feasible successors that could be used
in the event that primary route goes way so based on the metric we're looking
at that's the successor route and then our six and our three both meet the feas
ibility condition and that's why those routes are also showing up here with the
command show IP EADGRP topology however if we did a trace to and let's go ahead
and do it long hand here.
We'll go to eight eight eight eight and we'll go ahead and say please repeat WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We'll go to eight eight eight eight and we'll go ahead and say please repeat
the probe count let's do ten times and press enter and then we'll press enter
all the way through notice that it's taking the same first hop every single
time through dot two and then for the second hop our two is in 14 and over to R
1 and R1 is in R3 and then R3 is sitting down to R8 based on the last octets as
shown right here and that's because we did a show IP route for eight eight
eight eight and we could put the final eight there there's our next hop.
And for the calculation for the final metric there is the total delay and there WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And for the calculation for the final metric there is the total delay and there
is the minimum bandwidth in the path that we're used as part of the calculation
to get that final metric and that final metric is right here we can all see
that metric in the routing table with the show IP route press enter and go up
to the eight eight eight network right here and there's that metric once again
for that route.
So currently our four only has one path for the eight eight eight network that
's using the feasible successor the winning route and that's setting it up to R2
it's not considering other feasible successors for example our three going over WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it's not considering other feasible successors for example our three going over
the left or our six going straight down it's only using the best route in the
path.
However with eagrp if we want to say you know what if you've got some
additional feasible successors go ahead and start using them we can do that as
well so the next video I'll walk you through both options for doing one for
traditional eagrp and another for named eagrp and it's using the feature of
variance inside the routing protocol so I'll see you in the next video for
exactly that.