1
00:00:02,645 --> 00:00:04,645
(music)

2
00:00:08,920 --> 00:00:11,703
- Alright so here we are
zipping along now in part three

3
00:00:11,703 --> 00:00:14,962
and now we're gonna add EIGRP
to what we've already done

4
00:00:14,962 --> 00:00:17,712
so far in parts one and part two.

5
00:00:19,092 --> 00:00:23,259
So let's go back to our
original requirements here.

6
00:00:24,635 --> 00:00:27,133
I'll put my topology back in here.

7
00:00:27,133 --> 00:00:28,470
So we know that everything's
supposed to be in

8
00:00:28,470 --> 00:00:29,670
one autonomous system.

9
00:00:29,670 --> 00:00:33,170
It was not specified what that
autonomous system should be

10
00:00:33,170 --> 00:00:35,265
so it's up to you, I'm just gonna use

11
00:00:35,265 --> 00:00:38,138
EIGRP autonomous system 100,

12
00:00:38,138 --> 00:00:40,462
but you can choose any
number that you wish.

13
00:00:40,462 --> 00:00:42,994
And we also know that EIGRP
is supposed to be configured

14
00:00:42,994 --> 00:00:46,163
on all of these devices,
adding every single link

15
00:00:46,163 --> 00:00:47,580
into the process.

16
00:00:50,126 --> 00:00:53,863
Okay, so let's go ahead and do that.

17
00:00:53,863 --> 00:00:56,280
So let's start up everything,

18
00:00:58,149 --> 00:01:02,316
let's open it up once again SecureCRT.

19
00:01:04,249 --> 00:01:07,332
Alright, let's start with router one.

20
00:01:14,800 --> 00:01:18,619
conf t, router eigrp 100.

21
00:01:18,619 --> 00:01:20,151
Now this point, here's a little shortcut,

22
00:01:20,151 --> 00:01:21,972
the CCNA doesn't necessarily expect you to

23
00:01:21,972 --> 00:01:23,834
know how to do this and
they probably wouldn't

24
00:01:23,834 --> 00:01:25,657
want you to do this on any simulations

25
00:01:25,657 --> 00:01:28,711
but if you do desire to
have every single interface

26
00:01:28,711 --> 00:01:31,521
in your router in the EIGRP protocol,

27
00:01:31,521 --> 00:01:35,602
you can simply type network 0.0.0.0

28
00:01:35,602 --> 00:01:37,765
and that covers all of them at once.

29
00:01:37,765 --> 00:01:40,095
But for the purposes of the
CCNA Routing & Switching Exam,

30
00:01:40,095 --> 00:01:41,982
they're gonna want you to be
a little bit more specific

31
00:01:41,982 --> 00:01:43,899
than that.

32
00:01:45,098 --> 00:01:47,373
So we're gonna use the
actual explicit networks

33
00:01:47,373 --> 00:01:49,652
along with wildcard masks.

34
00:01:49,652 --> 00:01:52,152
(key strokes)

35
00:02:00,906 --> 00:02:03,045
Alright and that completes
our EIGRP configuration

36
00:02:03,045 --> 00:02:05,045
in router one.

37
00:02:07,383 --> 00:02:10,360
Alright, so we've saved
our configuration there

38
00:02:10,360 --> 00:02:12,454
so we can go ahead and
get rid of that guy,

39
00:02:12,454 --> 00:02:15,405
get rid of his window.

40
00:02:15,405 --> 00:02:16,500
Now where are we right here?

41
00:02:16,500 --> 00:02:17,905
Which router is this?

42
00:02:17,905 --> 00:02:19,348
This is router four, okay,

43
00:02:19,348 --> 00:02:20,653
so we'll go ahead and do the same thing,

44
00:02:20,653 --> 00:02:24,480
router eigrp 100,

45
00:02:24,480 --> 00:02:28,859
network 44.44.44.0,

46
00:02:28,859 --> 00:02:31,333
that covers our loopback.

47
00:02:31,333 --> 00:02:35,500
network 2.4.2.0

48
00:02:36,716 --> 00:02:40,883
and network 3.4.3.0

49
00:02:43,721 --> 00:02:45,971
and save our configuration.

50
00:02:50,461 --> 00:02:55,296
And show ip protocol can
verify the EIGRPs configured

51
00:02:55,296 --> 00:02:58,285
and that has been configured
on the correct networks

52
00:02:58,285 --> 00:03:01,169
for this particular device.

53
00:03:01,169 --> 00:03:04,669
Alright so save it, get rid of router four

54
00:03:06,629 --> 00:03:09,126
and now who do we have?

55
00:03:09,126 --> 00:03:13,293
Router three, okay, router eigrp 100.

56
00:03:14,889 --> 00:03:17,351
Now in this particular
router, one of the things

57
00:03:17,351 --> 00:03:19,437
that we were asked to do was to use

58
00:03:19,437 --> 00:03:22,987
the built in capabilities
of Wireshark built into GNS3

59
00:03:22,987 --> 00:03:25,026
so we could actually capture some packets

60
00:03:25,026 --> 00:03:26,517
and see what's going on

61
00:03:26,517 --> 00:03:28,018
and I would prefer to do that

62
00:03:28,018 --> 00:03:29,706
across the Fast Ethernet links.

63
00:03:29,706 --> 00:03:31,885
That way we can also see
the multicast addresses

64
00:03:31,885 --> 00:03:34,847
that are used and the MAC
addresses and all that good stuff.

65
00:03:34,847 --> 00:03:37,116
And we wouldn't see that stuff
if we do our packet captures

66
00:03:37,116 --> 00:03:38,735
on the serial interfaces.

67
00:03:38,735 --> 00:03:41,250
So in this particular case
here's what I'm gonna do,

68
00:03:41,250 --> 00:03:43,250
I'm gonna go ahead and
complete the configuration

69
00:03:43,250 --> 00:03:44,944
between router one and router three,

70
00:03:44,944 --> 00:03:48,182
I'll enable this link in
EIGRP so the neighborship

71
00:03:48,182 --> 00:03:52,327
will come up, but before I add this link

72
00:03:52,327 --> 00:03:53,324
into this,

73
00:03:53,324 --> 00:03:55,674
I'm gonna go ahead and turn on Wireshark

74
00:03:55,674 --> 00:03:59,001
on this interface which I
think is Fast Ethernet 0/1

75
00:03:59,001 --> 00:04:01,581
in router three and then we'll see that

76
00:04:01,581 --> 00:04:04,882
when I add EIGRP to this
link, we'll actually be able

77
00:04:04,882 --> 00:04:07,011
to capture the packets as the
whole neighbor relationship

78
00:04:07,011 --> 00:04:11,179
is built and as the EIGRP
updates are exchanged.

79
00:04:11,179 --> 00:04:14,686
So, let's go ahead on router three here

80
00:04:14,686 --> 00:04:17,603
and add in the command to...

81
00:04:19,186 --> 00:04:20,908
add EIGRP into the link connecting

82
00:04:20,908 --> 00:04:22,075
to router one.

83
00:04:23,690 --> 00:04:24,922
Alright, we should see that neighborship

84
00:04:24,922 --> 00:04:26,243
come up pretty quickly.

85
00:04:26,243 --> 00:04:27,420
There we go.

86
00:04:27,420 --> 00:04:29,573
Alright, and now before I
do the final stage of this,

87
00:04:29,573 --> 00:04:32,979
let's go back to our GNS3 topology...

88
00:04:32,979 --> 00:04:36,353
and I'm going to right-click

89
00:04:36,353 --> 00:04:38,486
and select capture

90
00:04:38,486 --> 00:04:40,417
and that will enable
me to start Wireshark.

91
00:04:40,417 --> 00:04:41,640
Now when I do that, it's gonna ask me

92
00:04:41,640 --> 00:04:43,370
"Which interface do you
want to capture on?"

93
00:04:43,370 --> 00:04:45,658
In this particular case
it's defaulting to the one

94
00:04:45,658 --> 00:04:49,294
I actually did want, Fast
Ethernet 0/1, that's good.

95
00:04:49,294 --> 00:04:50,944
So now just hit okay

96
00:04:50,944 --> 00:04:53,910
and Wireshark will come up immediately

97
00:04:53,910 --> 00:04:56,557
and start capturing packets.

98
00:04:56,557 --> 00:04:59,356
Alright so let's go to router three

99
00:04:59,356 --> 00:05:01,477
and finish off our configuration.

100
00:05:01,477 --> 00:05:05,644
network 3.4.3.0.0.0.0.255

101
00:05:09,370 --> 00:05:13,752
save our memory and we
can see that already

102
00:05:13,752 --> 00:05:16,529
the EIGRP neighbor relationship was built.

103
00:05:16,529 --> 00:05:20,696
So we can go ahead and
go back to Wireshark

104
00:05:21,573 --> 00:05:25,099
and stop capturing, so
we don't need to anymore.

105
00:05:25,099 --> 00:05:26,099
There we go.

106
00:05:27,320 --> 00:05:30,669
Now, if there were other
routers on this link

107
00:05:30,669 --> 00:05:32,991
for example if there were three
or four routers or something

108
00:05:32,991 --> 00:05:37,852
I might say well, "I only
wanna see the EIGRP packets

109
00:05:37,852 --> 00:05:42,021
"that were either transmitted
from or received by

110
00:05:42,021 --> 00:05:43,424
"router three."

111
00:05:43,424 --> 00:05:45,527
So let's imaging there
were two or three other,

112
00:05:45,527 --> 00:05:47,824
maybe this link is connected
to a hub or a switch

113
00:05:47,824 --> 00:05:48,657
or something, I'd say.

114
00:05:48,657 --> 00:05:50,760
"Oh, I don't wanna see all
their packets going back

115
00:05:50,760 --> 00:05:52,803
"and forth, I just want
to see the ones going to

116
00:05:52,803 --> 00:05:55,091
"or coming from router three."

117
00:05:55,091 --> 00:05:59,162
So that involves creating
actually a Wireshark filter.

118
00:05:59,162 --> 00:06:01,334
So here within the upper
left corner of Wireshark

119
00:06:01,334 --> 00:06:02,576
is where I'm gonna create that filter.

120
00:06:02,576 --> 00:06:06,743
It's just ip.addr and then ==

121
00:06:08,385 --> 00:06:10,066
and then the IP address,

122
00:06:10,066 --> 00:06:12,899
in this case 3.4.3.3.

123
00:06:15,022 --> 00:06:17,118
Alright and so now this will show me,

124
00:06:17,118 --> 00:06:20,275
this will filter out everything
and only show me packets

125
00:06:20,275 --> 00:06:24,054
where 3.4.3.3 was either in the source

126
00:06:24,054 --> 00:06:28,113
or the destination, since
I didn't specify that.

127
00:06:28,113 --> 00:06:30,955
And so we can see, here's
the exchange of hellos

128
00:06:30,955 --> 00:06:34,792
between router three, router three,

129
00:06:34,792 --> 00:06:37,324
and now once the link comes up

130
00:06:37,324 --> 00:06:39,788
here is an update that goes across.

131
00:06:39,788 --> 00:06:41,051
So let's go back to the hello first.

132
00:06:41,051 --> 00:06:45,218
We can open that up and
see some pretty good stuff.

133
00:06:46,122 --> 00:06:48,678
You can see here that it's using

134
00:06:48,678 --> 00:06:51,985
the 224.0.0.10 as the destination

135
00:06:51,985 --> 00:06:55,669
and its own IP address as the source

136
00:06:55,669 --> 00:06:57,370
and if we scroll and also we can see

137
00:06:57,370 --> 00:07:00,027
that the IP protocol is Protocol 88,

138
00:07:00,027 --> 00:07:01,888
that's the protocol reserved for EIGRP.

139
00:07:01,888 --> 00:07:04,372
This is all stuff you could
be potentially tested on

140
00:07:04,372 --> 00:07:06,538
for the CCNA.

141
00:07:06,538 --> 00:07:09,510
And if we scroll down to the
actual body of the EIGRP packet

142
00:07:09,510 --> 00:07:13,327
right behind the IP header we can see

143
00:07:13,327 --> 00:07:14,790
all this good stuff.

144
00:07:14,790 --> 00:07:18,807
So we can see the operational
code is Hello, this is a Hello

145
00:07:18,807 --> 00:07:21,457
and in the Hello the CCNA
is gonna expect you to know

146
00:07:21,457 --> 00:07:24,980
what is in the Hello and
what parameters have to match

147
00:07:24,980 --> 00:07:27,524
and what parameters don't
necessarily have to match.

148
00:07:27,524 --> 00:07:29,934
Well we know the autonomous
system numbers in there,

149
00:07:29,934 --> 00:07:33,591
that has to match and we also know that

150
00:07:33,591 --> 00:07:38,141
under the parameters field,
what's called the K Values

151
00:07:38,141 --> 00:07:39,308
have to match,

152
00:07:40,929 --> 00:07:43,512
And we see all that right here.

153
00:07:45,306 --> 00:07:47,416
Alright so let's go ahead
and shut down Wireshark,

154
00:07:47,416 --> 00:07:48,984
we don't need that anymore

155
00:07:48,984 --> 00:07:50,985
and before we exit out of this video.

156
00:07:50,985 --> 00:07:53,652
Let's make sure at this point...

157
00:07:54,701 --> 00:07:58,465
router one should know
about, actually router three,

158
00:07:58,465 --> 00:07:59,921
router three should know about everything.

159
00:07:59,921 --> 00:08:02,177
He should know about the
loopback of router one

160
00:08:02,177 --> 00:08:04,228
and the loopback of router four,

161
00:08:04,228 --> 00:08:06,395
sho ip route.

162
00:08:07,940 --> 00:08:09,940
And we can see, he does.

163
00:08:12,054 --> 00:08:14,028
And further more at this
point we should have

164
00:08:14,028 --> 00:08:15,348
end to end reach-ability.

165
00:08:15,348 --> 00:08:19,764
So if I close out this and now here we are

166
00:08:19,764 --> 00:08:22,676
at router two, well we
don't really care about

167
00:08:22,676 --> 00:08:26,713
router two anymore, he
should be all good to go.

168
00:08:26,713 --> 00:08:30,880
Let's just make sure that
he's configured appropriately.

169
00:08:34,542 --> 00:08:36,010
Nope, router two doesn't
have any configuration

170
00:08:36,010 --> 00:08:36,929
for EIGRP.

171
00:08:36,929 --> 00:08:39,429
(key strokes)

172
00:08:53,533 --> 00:08:55,304
Okay, so router two is done.

173
00:08:55,304 --> 00:08:58,624
So now at this point ,
if we go into router one,

174
00:08:58,624 --> 00:09:00,948
just double-clicking on him

175
00:09:00,948 --> 00:09:02,781
and do sho ip route...

176
00:09:04,661 --> 00:09:06,411
issue that command...

177
00:09:08,680 --> 00:09:12,847
we can see that router
one has learned about

178
00:09:13,881 --> 00:09:15,402
router four's loopback.

179
00:09:15,402 --> 00:09:18,699
And we should be able to ping it,

180
00:09:18,699 --> 00:09:20,203
and we can.

181
00:09:20,203 --> 00:09:21,614
And we can also see that
as far as that loopback

182
00:09:21,614 --> 00:09:25,436
is concerned, the path
that's been learned,

183
00:09:25,436 --> 00:09:27,864
or I should say the preferred path

184
00:09:27,864 --> 00:09:30,337
is Fast Ethernet 0/0

185
00:09:30,337 --> 00:09:32,981
which makes sense because
that path is faster than

186
00:09:32,981 --> 00:09:34,932
the serial link on top.

187
00:09:34,932 --> 00:09:36,203
Now that leads us to ask the question

188
00:09:36,203 --> 00:09:38,140
you might be asked in the CCNA,

189
00:09:38,140 --> 00:09:41,934
how would you discover
all of the possible paths

190
00:09:41,934 --> 00:09:43,426
that a router has learned

191
00:09:43,426 --> 00:09:45,631
to a particular destination network?

192
00:09:45,631 --> 00:09:50,299
Well you should know the
command sho ip eigrp topology

193
00:09:50,299 --> 00:09:52,908
which gives you a high-level
sort of summary view.

194
00:09:52,908 --> 00:09:55,092
And looking at this you
might initially think,

195
00:09:55,092 --> 00:09:58,428
"Oh, well router one only
has learned about the

196
00:09:58,428 --> 00:10:00,764
"44 network via the Fast Ethernet path,

197
00:10:00,764 --> 00:10:03,500
"something must be wrong
because why didn't he also

198
00:10:03,500 --> 00:10:05,633
"learn about the serial link, even though

199
00:10:05,633 --> 00:10:07,422
"that might not be the
link he's actually using

200
00:10:07,422 --> 00:10:10,882
"in his routing table, it
should still be in here right?"

201
00:10:10,882 --> 00:10:14,284
Remember, this particular
command, only shows you

202
00:10:14,284 --> 00:10:17,388
your successors and feasible successors.

203
00:10:17,388 --> 00:10:18,749
Now if you don't know
what those terms are,

204
00:10:18,749 --> 00:10:20,836
better go look 'em up
because that's something

205
00:10:20,836 --> 00:10:23,442
the CCNA Routing & Switching
Exam is gonna expect

206
00:10:23,442 --> 00:10:25,530
you to know what those terms are.

207
00:10:25,530 --> 00:10:29,449
So this only shows you successor
and feasible successors.

208
00:10:29,449 --> 00:10:32,537
There's a possibility that you
could learn of an alternate

209
00:10:32,537 --> 00:10:35,763
path to route that doesn't
meet either one of those

210
00:10:35,763 --> 00:10:36,934
conditions.

211
00:10:36,934 --> 00:10:40,894
It's not a successor or a
feasible successor, why?

212
00:10:40,894 --> 00:10:43,280
Well, if an incoming route comes to you

213
00:10:43,280 --> 00:10:46,668
and it does not meet the
"feasibility condition"

214
00:10:46,668 --> 00:10:48,837
which is the condition that EIGRP uses

215
00:10:48,837 --> 00:10:51,121
to try to detect routing loops.

216
00:10:51,121 --> 00:10:53,235
If it does not meet the
feasibility condition,

217
00:10:53,235 --> 00:10:56,151
it will not be classified
as either a successor

218
00:10:56,151 --> 00:10:57,996
or a feasible successor.

219
00:10:57,996 --> 00:11:00,556
So how can we tell in our topology table

220
00:11:00,556 --> 00:11:02,992
if we actually have
learned about this route

221
00:11:02,992 --> 00:11:05,756
via the serial link but because it came in

222
00:11:05,756 --> 00:11:08,763
and the metric was so
horrible, it was considered

223
00:11:08,763 --> 00:11:10,927
as a possible loop and it did not meet

224
00:11:10,927 --> 00:11:12,596
the feasibility condition.

225
00:11:12,596 --> 00:11:13,813
Well here's how we can tell,

226
00:11:13,813 --> 00:11:15,832
we can use that exact same we just used,

227
00:11:15,832 --> 00:11:19,999
but with a keyword of all-links.

228
00:11:21,504 --> 00:11:24,188
And now we can see as far as
the 44 network is concerned,

229
00:11:24,188 --> 00:11:27,449
yes the Fast Ethernet 0/0 is the successor

230
00:11:27,449 --> 00:11:31,241
but here it is down here
and wow, why didn't this

231
00:11:31,241 --> 00:11:34,357
be considered?

232
00:11:34,357 --> 00:11:37,134
Well look at this, right
now our feasible distance,

233
00:11:37,134 --> 00:11:40,995
our total distance for
the best, fastest path

234
00:11:40,995 --> 00:11:44,995
is 435,200.

235
00:11:46,370 --> 00:11:49,553
Well our neighbor downstairs
on the serial link,

236
00:11:49,553 --> 00:11:54,381
he advertised a path of
little bit of over two million

237
00:11:54,381 --> 00:11:55,782
as the metric.

238
00:11:55,782 --> 00:11:59,075
That does not meet the
feasibility condition.

239
00:11:59,075 --> 00:12:01,489
And if you wanna know more
about the feasibility condition,

240
00:12:01,489 --> 00:12:03,223
you definitely wanna research that,

241
00:12:03,223 --> 00:12:07,390
because that is also CCNA
Routing & Switching level topic.

242
00:12:09,583 --> 00:12:12,195
So at this point,

243
00:12:12,195 --> 00:12:14,629
that concludes this particular section

244
00:12:14,629 --> 00:12:18,758
of the video where we've done
our basic EIGRP configuration.

245
00:12:18,758 --> 00:12:20,835
So stay tuned for the
next videos coming up

246
00:12:20,835 --> 00:12:23,696
to add the authentication
element into this

247
00:12:23,696 --> 00:12:26,954
and then lastly we're
gonna manipulate EIGRP

248
00:12:26,954 --> 00:12:30,967
so it actually prefers that
slower path on the top.

249
00:12:30,967 --> 00:12:33,050
(music)