WEBVTT

1
00:00.000 --> 00:04.900
To appreciate configuring EIGRP is probably best to do it. So in this video, I

2
00:04.900 --> 00:05.440
'm going to walk you

3
00:05.440 --> 00:08.820
through the steps of implementing the traditional flavor or traditional

4
00:08.820 --> 00:10.800
configuration for EIGRP.

5
00:10.800 --> 00:14.080
And also the tail end of the set of videos, I'll give the opportunity to do so.

6
00:14.080 --> 00:14.400
Also,

7
00:14.400 --> 00:18.040
if you'd like to, you can actually scroll down to the very end, click on the

8
00:18.040 --> 00:19.040
link for the lab

9
00:19.040 --> 00:22.130
if you want to walk through it with me step by step right now. So whether you

10
00:22.130 --> 00:22.960
want to do it now,

11
00:22.960 --> 00:26.400
or later when I assign the lab, either way is great. So this is our virtualized

12
00:26.400 --> 00:26.880
environment

13
00:26.880 --> 00:30.000
to starting up. Also, while this is booting up, let me point out this button
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:30.000 --> 00:30.400
over here on the

15
00:30.400 --> 00:33.880
right, the reset button. If you are working a lab and you do a few things and

16
00:33.880 --> 00:34.560
go sideways,

17
00:34.560 --> 00:38.720
whatever, and you want to start over from scratch, just open the lab up again,

18
00:38.720 --> 00:39.760
click on reset here

19
00:39.760 --> 00:43.140
in a few minutes. It'll reset the lab and you can restart the machines and just

20
00:43.140 --> 00:44.000
go at it again.

21
00:44.000 --> 00:47.070
So feel free to get some hands on practice because that's a big part of the

22
00:47.070 --> 00:48.000
learning experience

23
00:48.000 --> 00:52.070
to reinforce what we're talking about regarding EIGRP. And although this may

24
00:52.070 --> 00:53.120
not be the first time you

25
00:53.120 --> 00:56.040
used our virtual lab environment, it may be the first time that I've walked you

26
00:56.040 --> 00:57.440
through using one.

27
00:57.440 --> 00:59.740
So let me take a moment and give you the lay of the land regarding the lab

28
00:59.740 --> 01:00.880
environment. So over here,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
00:59.740 --> 01:00.880
environment. So over here,

29
01:00.880 --> 01:04.140
we have lab controls. If you want to launch RDP in a separate application and

30
01:04.140 --> 01:04.960
connect to the lab

31
01:04.960 --> 01:09.250
environment, you can do so using that for the address right there. And then the

32
01:09.250 --> 01:10.320
username is learner.

33
01:10.320 --> 01:13.760
And then this dynamic password will be generated for you and it'll be different

34
01:13.760 --> 01:14.240
for each of your

35
01:14.240 --> 01:17.060
lab environments. But if you want to copy and paste those into RDP, if you want

36
01:17.060 --> 01:18.000
to use that instead,

37
01:18.000 --> 01:21.330
you can't or if you want to use the web interface, that's great too. So to

38
01:21.330 --> 01:22.240
begin with,

39
01:22.240 --> 01:25.630
we have server one nug here and that is going to be the VM that we're going to

40
01:25.630 --> 01:26.800
launch. And it has

41
01:26.800 --> 01:31.220
multi tab putty running and ready to go. So you can work with all of the rout
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
01:26.800 --> 01:31.220
multi tab putty running and ready to go. So you can work with all of the rout

42
01:31.220 --> 01:32.640
ers in the topology.

43
01:32.640 --> 01:37.120
And just to confirm that, I'm going to go ahead and highlight server one here.

44
01:37.120 --> 01:38.080
In fact, I need to double

45
01:38.080 --> 01:41.550
click on server one and go ahead and give that just a moment to launch. So

46
01:41.550 --> 01:42.640
there it goes. That was

47
01:42.640 --> 01:46.720
about 15 to 20 seconds of real time. So this is server one that we're looking

48
01:46.720 --> 01:47.680
at right here. And it

49
01:47.680 --> 01:53.380
has multi tab putty open. So here's R1, here's R2, R3, etc. There's also tab

50
01:53.380 --> 01:55.200
for PC. It's the virtual

51
01:55.200 --> 02:00.850
PC and PC7 and PC8. And then for convenience, I have in the skill, I've got the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
01:55.200 --> 02:00.850
PC and PC7 and PC8. And then for convenience, I have in the skill, I've got the

52
02:00.850 --> 02:01.760
lab topology, but I

53
02:01.760 --> 02:06.100
also put it right here as well. So here's an icon for the lab topology. If we

54
02:06.100 --> 02:07.680
double click on that here

55
02:07.680 --> 02:11.550
on server one, that's going to open that up so we can reference it here as well

56
02:11.550 --> 02:12.400
. And what a lot of

57
02:12.400 --> 02:16.250
people will do, they'll go ahead and download the topology right from the skill

58
02:16.250 --> 02:17.200
. And then if you have a

59
02:17.200 --> 02:20.190
second screen, it's really handy to put down the second screen. So you can see

60
02:20.190 --> 02:21.280
your command line,

61
02:21.280 --> 02:24.130
you can see the topology without having to go back and forth. But either way,

62
02:24.130 --> 02:25.040
it's great. So there's

63
02:25.040 --> 02:28.660
R2, I'm going to minimize that. And then here for this lab, I've got a notepad

64
02:28.660 --> 02:29.520
document sitting on

65
02:29.520 --> 02:35.210
the desktop. And that notepad document is called EIGRP configs right there. I
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
02:29.520 --> 02:35.210
the desktop. And that notepad document is called EIGRP configs right there. I

66
02:35.210 --> 02:36.240
also have it open by

67
02:36.240 --> 02:39.690
default. So it's already open in the taskbar. And there it is. And that way it

68
02:39.690 --> 02:40.320
's not a typing

69
02:40.320 --> 02:44.610
exercise for you, but rather just a way to see the config, put it in, and then

70
02:44.610 --> 02:45.760
also remove it as

71
02:45.760 --> 02:50.160
needed. So this first section here is going to first I'll go through and remove

72
02:50.160 --> 02:51.920
various versions of

73
02:51.920 --> 02:55.890
EIGRP and OSPF, whether they're there or not. This is going to get rid of those

74
02:55.890 --> 02:57.920
. And then to implement EIGRP,

75
02:57.920 --> 03:00.610
we're simply going to do this. In fact, let me make this a bit bigger. Let me
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
02:57.920 --> 03:00.610
we're simply going to do this. In fact, let me make this a bit bigger. Let me

76
03:00.610 --> 03:01.920
go to format and font.

77
03:01.920 --> 03:05.870
And I'll make this a little bigger for the recording. So let me go ahead and go

78
03:05.870 --> 03:07.680
to 20 and click on OK.

79
03:07.680 --> 03:12.040
That's better. All right. So the actual configuration for EIGRP is from

80
03:12.040 --> 03:13.440
configuration mode. You just

81
03:13.440 --> 03:18.260
go into router EIGRP, give it an autonomous system number. And then this

82
03:18.260 --> 03:20.720
network statement effectively says

83
03:20.720 --> 03:25.670
any interfaces that have an IPv4 address, you're in. That's it. So that's what

84
03:25.670 --> 03:26.480
I'm going to do on all

85
03:26.480 --> 03:30.060
the routers. I'm going to go ahead and copy that little piece right there.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
03:26.480 --> 03:30.060
the routers. I'm going to go ahead and copy that little piece right there.

86
03:30.060 --> 03:31.520
Right click. I'll copy that's

87
03:31.520 --> 03:35.190
my buffer. And then I have the tab open for multi tab putty right here. So we

88
03:35.190 --> 03:36.320
'll go back to multi tab

89
03:36.320 --> 03:40.230
putty. And then this is really fun and cool. And I want to share it with you

90
03:40.230 --> 03:42.160
right now. This icon

91
03:42.160 --> 03:46.180
right there. If we click on that, we can actually choose to send the commands

92
03:46.180 --> 03:48.000
to multiple devices at

93
03:48.000 --> 03:51.890
the same time. So if we have configuration, which we're about to do and you

94
03:51.890 --> 03:52.640
want to do it on all

95
03:52.640 --> 03:56.790
devices, you just copy paste it in, you know, tab by tab by tab or we could use

96
03:56.790 --> 03:58.160
this option as well.

97
03:58.160 --> 04:01.970
So let's go ahead and click on that. And then from my clipboard, I'm going to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

97
03:58.160 --> 04:01.970
So let's go ahead and click on that. And then from my clipboard, I'm going to

98
04:01.970 --> 04:02.480
click here in this

99
04:02.480 --> 04:05.890
space, type your script right click and click on paste. And that puts in that

100
04:05.890 --> 04:07.200
same configuration. So

101
04:07.200 --> 04:11.950
it's going to wipe out any possible earlier versions of EIDR, PROSPFI may have

102
04:11.950 --> 04:12.880
had. And then it's

103
04:12.880 --> 04:16.260
going to implement router EIDR P18 and a network statement of all zeros

104
04:16.260 --> 04:17.680
effectively saying any

105
04:17.680 --> 04:21.030
interface that have an IPV4 address, bring them in. And then I'm going to go

106
04:21.030 --> 04:22.560
ahead and have it say

107
04:22.560 --> 04:26.260
end. And then I click here on select all. But I don't want to send this to the

108
04:26.260 --> 04:26.960
PCs because I'm not

109
04:26.960 --> 04:30.650
going to know what to do with those commands. So I'm simply going to remove PC
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
04:26.960 --> 04:30.650
going to know what to do with those commands. So I'm simply going to remove PC

110
04:30.650 --> 04:31.840
one PC seven PC eight

111
04:31.840 --> 04:36.690
and send those commands to all of the eight routers. So if that in place, I'll

112
04:36.690 --> 04:38.160
click send script.

113
04:38.160 --> 04:43.830
And now it's done that for all eight routers. And because EIDR P is so quick,

114
04:43.830 --> 04:45.280
it's already negotiated

115
04:45.280 --> 04:49.110
neighborships, it's already converged. And each of the routers in the topology,

116
04:49.110 --> 04:49.600
let me bring up the

117
04:49.600 --> 04:54.250
topology again. They should now know how to reach every single IPV4 network in

118
04:54.250 --> 04:55.440
this topology.

119
04:55.440 --> 05:00.510
So as a quick test, let's go to R1. So R1 is at the top left hand corner of our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

119
04:55.440 --> 05:00.510
So as a quick test, let's go to R1. So R1 is at the top left hand corner of our

120
05:00.510 --> 05:01.440
topology. And let's

121
05:01.440 --> 05:05.950
start off the show IP protocols. We'll see what IPV4 protocols are running. So

122
05:05.950 --> 05:06.800
here it's showing us,

123
05:06.800 --> 05:10.610
I'll scroll up a little bit here. Here's showing us the EIDR P, autonomous

124
05:10.610 --> 05:11.920
system 18 is running.

125
05:11.920 --> 05:15.870
And here's showing us the metric weights that are being used. So K1 is the

126
05:15.870 --> 05:17.440
minimum bandwidth in the

127
05:17.440 --> 05:22.970
path. And K3 is the sum of the delays, meaning the delays added up. And the

128
05:22.970 --> 05:23.840
other values, the other

129
05:23.840 --> 05:30.050
K values, which represent things such as load and reliability and M2U. Those
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

129
05:23.840 --> 05:30.050
K values, which represent things such as load and reliability and M2U. Those

130
05:30.050 --> 05:30.800
are not being used for

131
05:30.800 --> 05:33.860
the metric calculation. It's also showing us here, let me bring up the topology

132
05:33.860 --> 05:35.120
once again for this.

133
05:35.120 --> 05:39.100
And I'll just move it a little bit over to the right. Here it's also showing us

134
05:39.100 --> 05:40.080
that router 1, the

135
05:40.080 --> 05:43.220
current router that we're sitting at, is learning routing updates and routing

136
05:43.220 --> 05:44.800
information from R3,

137
05:44.800 --> 05:49.710
based on that last octet of dot 3. And also from dot 2, based on the last octet

138
05:49.710 --> 05:50.560
ending in dot 2.

139
05:50.560 --> 05:54.140
That's another thing I did in the topology is to make it easy, I just used the

140
05:54.140 --> 05:55.200
router number for

141
05:55.200 --> 05:59.360
the final octet for each of the interface IP addresses. So here on R1, we have

142
05:59.360 --> 06:00.720
to show IPEIDR
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

142
05:59.360 --> 06:00.720
to show IPEIDR

143
06:00.720 --> 06:05.310
ERP neighbors. It'll show us who our neighbors are. There's R2 and R3, off of

144
06:05.310 --> 06:06.720
the respective interfaces.

145
06:06.720 --> 06:10.730
And then we do a show IPEIDGRP interface. It'll show us which interfaces are

146
06:10.730 --> 06:12.320
enabled for EIDGRP,

147
06:12.320 --> 06:18.010
which are all the interfaces that are using IPV4 on router 1. We can also show

148
06:18.010 --> 06:20.080
IPEIDGRP topology.

149
06:20.080 --> 06:24.220
Now before I press enter on this one, there's a lot of output that's going to

150
06:24.220 --> 06:25.280
be shown. So let's

151
06:25.280 --> 06:30.460
just focus on, for example, one route. Let's go ahead and choose the 888 route
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

151
06:25.280 --> 06:30.460
just focus on, for example, one route. Let's go ahead and choose the 888 route

152
06:30.460 --> 06:31.920
right here. I'll highlight

153
06:31.920 --> 06:36.990
it. So for the 888 route, that 32-bit network, it has one successor. That means

154
06:36.990 --> 06:38.000
one winning route in

155
06:38.000 --> 06:41.680
the routing table. The feasible distance, which is the effective metric for

156
06:41.680 --> 06:42.880
that route, is,

157
06:42.880 --> 06:46.170
looks like 40 million in change. Let me do a quick check. That's three

158
06:46.170 --> 06:47.280
characters and three more.

159
06:47.280 --> 06:51.340
Now depending on the flavor and implementation of EIDGRP, it may be using mic

160
06:51.340 --> 06:52.160
roseconds or

161
06:52.160 --> 06:56.290
picoseconds as part of the calculation. So that is going to be a 40 there, and

162
06:56.290 --> 06:57.280
that's 40 million.

163
06:57.280 --> 07:00.530
So this feasible distance for the successor route, effectively, that's the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

163
06:57.280 --> 07:00.530
So this feasible distance for the successor route, effectively, that's the

164
07:00.530 --> 07:01.360
metric further out.

165
07:01.360 --> 07:06.500
It's once again shown right here. It's also showing us the reported distance

166
07:06.500 --> 07:07.120
that's coming in from

167
07:07.120 --> 07:11.380
the neighbor. And based on the router it came from, the .3 there, that's R3

168
07:11.380 --> 07:12.000
that has this

169
07:12.000 --> 07:16.180
advertised distance. Now the fact of the matter is, R3 really isn't sending

170
07:16.180 --> 07:17.680
this number. R3 is

171
07:17.680 --> 07:21.210
setting information, including the sum of the delays and the slowest link in

172
07:21.210 --> 07:22.400
the path. And then it's

173
07:22.400 --> 07:26.460
actually R1 is calculating this number based on those considerations, based on

174
07:26.460 --> 07:27.120
the reported

175
07:27.120 --> 07:31.080
distance. So again, this first number here is the full metric or feasible
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

175
07:27.120 --> 07:31.080
distance. So again, this first number here is the full metric or feasible

176
07:31.080 --> 07:32.480
distance from the perspective

177
07:32.480 --> 07:37.230
of R1 to get to 8888. And the second part here is the reported distance that

178
07:37.230 --> 07:38.480
was coming in from

179
07:38.480 --> 07:42.440
R3. Or at least the values such as the sum of the delays and the slowest link

180
07:42.440 --> 07:43.600
in the path that

181
07:43.600 --> 07:47.680
were advertised by R3. And if you want to see the routing table, we can do a

182
07:47.680 --> 07:48.640
show IP route.

183
07:48.640 --> 07:51.920
And that shows all routes. Or if you want to see the EIGRP learned routes only,

184
07:51.920 --> 07:52.960
we do a show IP

185
07:52.960 --> 07:58.610
route, EIGRP, press center. And there once again is our 8888 route. And right

186
07:58.610 --> 07:59.440
there is the metric

187
07:59.440 --> 08:02.970
war in the world of EIGRP. We could call it the feasible distance. Or we could
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

187
07:59.440 --> 08:02.970
war in the world of EIGRP. We could call it the feasible distance. Or we could

188
08:02.970 --> 08:04.000
call it the composite

189
08:04.000 --> 08:06.590
metric. That's the metric for that winning route. And here is the

190
08:06.590 --> 08:08.400
administrative distance of 90 for

191
08:08.400 --> 08:11.650
an internally learned EIGRP route. And if we wanted to verify the path, we

192
08:11.650 --> 08:12.560
could do things like

193
08:12.560 --> 08:17.280
trace. So we can do a trace. And we'll go ahead and trace down to 8888. Press

194
08:17.280 --> 08:17.920
center. And that's

195
08:17.920 --> 08:20.890
showing us that it's taking the first top and then bring up the topology. So

196
08:20.890 --> 08:22.000
here based on our trace,

197
08:22.000 --> 08:26.910
R1 is forwarding it over to R3 based on that 3 there. And then our 3 is using

198
08:26.910 --> 08:27.920
this path to go

199
08:27.920 --> 08:32.780
ahead and send it down to R8. And R8 is the owner of that local loopback of 888
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

199
08:27.920 --> 08:32.780
ahead and send it down to R8. And R8 is the owner of that local loopback of 888

200
08:32.780 --> 08:33.920
8. And if you want to see

201
08:33.920 --> 08:38.340
the router config again, we do a show, run, flip pipe section. And let's go

202
08:38.340 --> 08:39.440
ahead and type in

203
08:39.440 --> 08:42.950
router. Give that a minute to process. And there is our full routing config

204
08:42.950 --> 08:45.520
right there. Router EIGRP 18.

205
08:45.520 --> 08:49.490
And please include any interfaces if they have an IPv4 address of any type

206
08:49.490 --> 08:50.720
associated with them.

207
08:50.720 --> 08:55.670
And very similar to OSPF, we could also specify certain ranges of interfaces

208
08:55.670 --> 08:56.640
based on IP addresses

209
08:56.640 --> 09:00.980
by using a network statement in combination with a wildcard mask. As an example
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

209
08:56.640 --> 09:00.980
by using a network statement in combination with a wildcard mask. As an example

210
09:00.980 --> 09:01.760
of that, let's go

211
09:01.760 --> 09:06.550
ahead and do a no. And then simply get a copy paste router EIGRP 18. Paste that

212
09:06.550 --> 09:08.080
in. Do a do show

213
09:08.080 --> 09:13.600
IP EIGRP interface. So no interfaces are participating at the moment in EIGRP.

214
09:13.600 --> 09:14.160
So we'll go ahead and do

215
09:14.160 --> 09:18.690
router EIGRP. And we'll set the same time system 18. And how about anything it

216
09:18.690 --> 09:19.840
starts with 10. So

217
09:19.840 --> 09:25.030
we're going to do 10.0.0.0. And then a wildcard mask of 0. And then if we don't

218
09:25.030 --> 09:26.480
care about the second,

219
09:26.480 --> 09:30.640
third and fourth octet, we do 255 for wildcard bits there, 255 for wildcard
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

219
09:26.480 --> 09:30.640
third and fourth octet, we do 255 for wildcard bits there, 255 for wildcard

220
09:30.640 --> 09:31.920
bits there, and 255

221
09:31.920 --> 09:36.950
and press enter. And then if we hit the up here a few times, and today show IP

222
09:36.950 --> 09:38.160
EIGRP interface,

223
09:38.160 --> 09:41.930
we'd only get those interfaces that start with a 10. And that does not include

224
09:41.930 --> 09:42.560
the loopback

225
09:42.560 --> 09:46.000
interface because the interface loopback in our one starts with a 1 and not a

226
09:46.000 --> 09:47.040
10. But if we want

227
09:47.040 --> 09:52.450
to add that also, we could do a network 1.1.1.1. Press enter, it's assuming the

228
09:52.450 --> 09:53.360
exact address. If you don't

229
09:53.360 --> 09:58.450
use wildcard bits, now if we do a show IP EIGRP interface, it now includes loop

230
09:58.450 --> 09:59.920
back 0 as well. If we do

231
09:59.920 --> 10:04.680
a do show IP interface brief, and say please exclude unassigned, that will also
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

231
09:59.920 --> 10:04.680
a do show IP interface brief, and say please exclude unassigned, that will also

232
10:04.680 --> 10:06.000
show us the associate

233
10:06.000 --> 10:10.030
IP addresses on those interfaces. So it's like an end there. So that's an

234
10:10.030 --> 10:11.840
example of how we can configure

235
10:11.840 --> 10:15.280
EIGRP using the traditional method. And once again, if you don't want to wait

236
10:15.280 --> 10:16.160
till the end, the

237
10:16.160 --> 10:19.720
lab assignment, if you want to launch that lab now, you can actually do this

238
10:19.720 --> 10:20.560
right now, and then

239
10:20.560 --> 10:23.750
join me in the next video as we continue because the next step is we're going

240
10:23.750 --> 10:24.960
to remove this configuration

241
10:24.960 --> 10:30.400
of traditional EIGRP and I like to walk you through implementing EIGRP using
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

241
10:24.960 --> 10:30.400
of traditional EIGRP and I like to walk you through implementing EIGRP using

242
10:30.400 --> 10:32.160
named EIGRP. So also,

243
10:32.160 --> 10:34.960
you my friend in the next video for exactly that.