WEBVTT

0:00:08.600000 --> 0:00:12.540000
 So here we are zipping along now in
 part three and now we're going to

0:00:12.540000 --> 0:00:17.640000
 add EIJRP to what we've already done
 so far in parts one and part two.

0:00:17.640000 --> 0:00:22.880000
 So let's go back to our original
 requirements here.

0:00:22.880000 --> 0:00:26.740000
 I'll draw my put my topology
 back here and here.

0:00:26.740000 --> 0:00:29.900000
 So we know that everything's supposed
 to be in one autonomous system.

0:00:29.900000 --> 0:00:33.960000
 It was not specified what that autonomous
 system should be so it's up

0:00:33.960000 --> 0:00:38.460000
 to you. I'm just going to use EIJRP
 Autonomous System 100 but you can

0:00:38.460000 --> 0:00:40.380000
 choose any number that you wish.

0:00:40.380000 --> 0:00:43.720000
 And we also know that EIJRP is supposed
 to be configured on all of these

0:00:43.720000 --> 0:00:48.880000
 devices adding every single
 link into the process.

0:00:48.880000 --> 0:00:53.840000
 Okay, so let's go ahead and
 go ahead and do that.

0:00:53.840000 --> 0:00:57.760000
 So let's start up everything.

0:00:57.760000 --> 0:01:02.480000
 Let's open it up once
 again in secure CRT.

0:01:02.480000 --> 0:01:13.480000
 Alright, let's start
 with router one.

0:01:13.480000 --> 0:01:18.500000
 Config T, router EIJRP 100.

0:01:18.500000 --> 0:01:20.180000
 Now at this point here's
 a little shortcut.

0:01:20.180000 --> 0:01:23.040000
 The CCNA doesn't necessarily expect
 you to know how to do this and they

0:01:23.040000 --> 0:01:25.740000
 probably wouldn't want you to
 do this on any simulations.

0:01:25.740000 --> 0:01:30.400000
 But if you desire to have every single
 interface in your router in the

0:01:30.400000 --> 0:01:36.500000
 EIJRP protocol, you can simply type
 network 000 and that covers all of

0:01:36.500000 --> 0:01:40.200000
 them at once. But for the purposes of
 the CCNA routing and switching exam,

0:01:40.200000 --> 0:01:43.120000
 they're going to want you to be a little
 bit more specific than that.

0:01:43.120000 --> 0:01:48.160000
 So we're going to use the actual explicit
 networks along with wildcard

0:01:48.160000 --> 0:02:05.640000
 masks. Alright, and that completes our
 EIJRP configuration in router one.

0:02:05.640000 --> 0:02:11.020000
 Alright, so we've saved our configuration
 there so we can go ahead and

0:02:11.020000 --> 0:02:15.280000
 get rid of that guy, get
 rid of his window.

0:02:15.280000 --> 0:02:16.480000
 Now where are we right here?

0:02:16.480000 --> 0:02:17.680000
 Which router is this?

0:02:17.680000 --> 0:02:19.360000
 This is router four, okay.

0:02:19.360000 --> 0:02:25.300000
 So we'll go ahead and
 do the same thing.

0:02:25.300000 --> 0:02:38.440000
 44, 44, 44.0, that covers our loopback,
 network 2.4.2.0, and network 3

0:02:38.440000 --> 0:02:50.080000
.4.3.0, and save our configuration.


0:02:50.080000 --> 0:02:55.660000
 And show IP protocol can verify that
 EIJRP is configured and that has

0:02:55.660000 --> 0:03:00.900000
 been configured on the correct networks
 for this particular device.

0:03:00.900000 --> 0:03:08.640000
 Alright, so save it, get rid of router
 four, and now who do we have?

0:03:08.640000 --> 0:03:11.540000
 Router three, okay.

0:03:11.540000 --> 0:03:14.140000
 Router EIJRP 100.

0:03:14.140000 --> 0:03:18.340000
 Now in this particular router, one
 of the things that we were asked to

0:03:18.340000 --> 0:03:23.300000
 do was to use the built-in capabilities
 of Wireshark built into GNS3 so

0:03:23.300000 --> 0:03:26.420000
 we could actually capture some packets
 and see what's going on.

0:03:26.420000 --> 0:03:29.660000
 And I would prefer to do that across
 the fast Ethernet links.

0:03:29.660000 --> 0:03:32.920000
 That way we can also see the multicast
 addresses that are used and the

0:03:32.920000 --> 0:03:34.600000
 MAC addresses and all
 that good stuff.

0:03:34.600000 --> 0:03:37.560000
 And we wouldn't see that stuff if we
 do our packet captures on the serial

0:03:37.560000 --> 0:03:41.040000
 interfaces. So in this particular
 case, here's what I'm going to do.

0:03:41.040000 --> 0:03:44.040000
 I'm going to go ahead and complete the
 configuration between router one

0:03:44.040000 --> 0:03:44.680000
 and router three.

0:03:44.680000 --> 0:03:48.940000
 I will enable this link in EIJRP
 so the neighborship will come up.

0:03:48.940000 --> 0:03:54.300000
 But before I add this link into that,
 I'm going to go ahead and turn on

0:03:54.300000 --> 0:03:58.200000
 Wireshark on this interface, which I
 think is fast Ethernet at zero slash

0:03:58.200000 --> 0:03:59.880000
 one in router three.

0:03:59.880000 --> 0:04:04.460000
 And then we'll see that when I add
 EIJRP to this link, we'll actually

0:04:04.460000 --> 0:04:07.440000
 be able to capture the packets as the
 whole neighbor relationship is built

0:04:07.440000 --> 0:04:10.820000
 and as the EIJRP updates
 are exchanged.

0:04:10.820000 --> 0:04:19.840000
 So let's go ahead on router three here
 and add in the command to add EIJRP

0:04:19.840000 --> 0:04:22.260000
 into the link connecting
 to router one.

0:04:22.260000 --> 0:04:26.180000
 All right, we should see that neighborship
 come up pretty quickly.

0:04:26.180000 --> 0:04:29.720000
 There we go. All right, and now before
 I do the final stage of this, let's

0:04:29.720000 --> 0:04:32.300000
 go back to our GNS3 topology.

0:04:32.300000 --> 0:04:38.300000
 And I'm going to right click
 and select capture.

0:04:38.300000 --> 0:04:40.460000
 And that will enable me
 to start Wireshark.

0:04:40.460000 --> 0:04:42.620000
 Now when I do that, it's going to ask
 me, which interface do you want

0:04:42.620000 --> 0:04:46.140000
 to capture on? In this particular case,
 it's defaulting to the one I actually

0:04:46.140000 --> 0:04:49.380000
 did want. Fast Ethernet zero
 slash one, that's good.

0:04:49.380000 --> 0:04:54.780000
 So now just hit OK and Wireshark will come
 up immediately and start capturing

0:04:54.780000 --> 0:05:00.200000
 packets. All right, so now let's go
 to router three and finish off our

0:05:00.200000 --> 0:05:05.140000
 configuration. Network three dot four
 dot three dot zero zero zero zero

0:05:05.140000 --> 0:05:07.240000
 dot two fifty five.

0:05:07.240000 --> 0:05:11.820000
 Save our memory.

0:05:11.820000 --> 0:05:16.520000
 And we can see that already the EIJRP
 neighbor relationship was built.

0:05:16.520000 --> 0:05:22.640000
 So we can go ahead and go back to
 Wireshark and stop capturing.

0:05:22.640000 --> 0:05:24.500000
 So we don't need to anymore.

0:05:24.500000 --> 0:05:31.080000
 There we go. Now if there were other
 routers on this link, for example,

0:05:31.080000 --> 0:05:33.960000
 if there were three or four routers
 or something, I might say, well, I

0:05:33.960000 --> 0:05:40.460000
 only want to see the EIJRP packets that
 were either transmitted from or

0:05:40.460000 --> 0:05:43.160000
 received by router three.

0:05:43.160000 --> 0:05:46.520000
 So let's imagine there were two or three
 other, maybe this link is connected

0:05:46.520000 --> 0:05:48.200000
 to a hub or a switch or something.


0:05:48.200000 --> 0:05:51.280000
 I say, oh, I don't want to see all
 their packets going back and forth.

0:05:51.280000 --> 0:05:55.000000
 I just want to see the ones going
 to or coming from router three.

0:05:55.000000 --> 0:05:59.040000
 So that involves creating actually
 a Wireshark filter.

0:05:59.040000 --> 0:06:01.720000
 So here within the upper left corner
 of Wireshark is where I'm going to

0:06:01.720000 --> 0:06:02.540000
 create that filter.

0:06:02.540000 --> 0:06:09.920000
 It's just IP dot ADDR and then equals
 equals and then the IP address.

0:06:09.920000 --> 0:06:14.820000
 When this case is three dot
 four dot three dot three.

0:06:14.820000 --> 0:06:19.060000
 All right. And so now this will show
 me, this will filter out everything

0:06:19.060000 --> 0:06:22.660000
 and only show me packets where three
 dot four dot three dot three was

0:06:22.660000 --> 0:06:27.100000
 either in the source or the destination
 since I didn't specify that.

0:06:27.100000 --> 0:06:32.800000
 And so we can see here's the exchange
 of hellos between router three,

0:06:32.800000 --> 0:06:39.260000
 router three. And now once the link comes
 up, here is an update that goes

0:06:39.260000 --> 0:06:41.100000
 across. So let's go back
 to the hello first.

0:06:41.100000 --> 0:06:44.640000
 We can open that up and see
 some pretty good stuff.

0:06:44.640000 --> 0:06:52.200000
 You can see here that it's using the
 2240010 as the destination and its

0:06:52.200000 --> 0:06:55.740000
 own IP address as the source.

0:06:55.740000 --> 0:06:58.840000
 And if we scroll and also we can see
 that the IP protocol is protocol

0:06:58.840000 --> 0:07:02.020000
 88. That's the protocol
 reserved for EIGRP.

0:07:02.020000 --> 0:07:06.200000
 This is all stuff you could be potentially
 tested on for the CCNA.

0:07:06.200000 --> 0:07:09.880000
 And then if we scroll down to the actual
 body of the EIGRP packet right

0:07:09.880000 --> 0:07:14.740000
 behind the IP header, we can
 see all this good stuff.

0:07:14.740000 --> 0:07:17.880000
 So we can see the operational
 code is hello.

0:07:17.880000 --> 0:07:18.860000
 This is a hello.

0:07:18.860000 --> 0:07:22.800000
 And in the hello, the CCNA is going
 to expect you to know what is in the

0:07:22.800000 --> 0:07:26.740000
 hello and what parameters have to match
 and what parameters don't necessarily

0:07:26.740000 --> 0:07:30.020000
 have to match. Well, we know the autonomous
 system numbers in there, that

0:07:30.020000 --> 0:07:36.300000
 has to match. And we also know that
 under the parameters field, what's

0:07:36.300000 --> 0:07:40.240000
 called the K values have to match.


0:07:40.240000 --> 0:07:43.180000
 And we see all that right here.

0:07:43.180000 --> 0:07:47.440000
 All right, so let's go ahead
 and shut down wire shark.

0:07:47.440000 --> 0:07:48.960000
 We don't need that anymore.

0:07:48.960000 --> 0:07:54.860000
 And before we exit out of this video,
 let's make sure at this point, router

0:07:54.860000 --> 0:07:58.920000
 one should know about,
 actually router three.

0:07:58.920000 --> 0:07:59.680000
 Or you should know
 about everything.

0:07:59.680000 --> 0:08:03.080000
 He should know about the loop back
 of router one and the loop back of

0:08:03.080000 --> 0:08:06.440000
 router four. Show IP route.

0:08:06.440000 --> 0:08:11.920000
 And we can see he does.

0:08:11.920000 --> 0:08:15.500000
 And furthermore, at this point, we should
 have end to end reachability.

0:08:15.500000 --> 0:08:22.180000
 So if I close out this, and now here
 we are at router two, well, we don't

0:08:22.180000 --> 0:08:24.540000
 really care about router
 two anymore.

0:08:24.540000 --> 0:08:28.900000
 He should be all good to go.

0:08:28.900000 --> 0:08:31.640000
 So, appropriately.

0:08:31.640000 --> 0:08:39.080000
 Nope, router two doesn't have
 any configuration for EIGRP.

0:08:39.080000 --> 0:08:55.200000
 Okay, so router two is done.

0:08:55.200000 --> 0:08:59.540000
 So now at this point, if we go into
 router one, just double clicking on

0:08:59.540000 --> 0:09:03.320000
 him. And do show IP route.

0:09:03.320000 --> 0:09:06.940000
 Issue that command.

0:09:06.940000 --> 0:09:15.280000
 We can see that router one has learned
 about router four's loop back.

0:09:15.280000 --> 0:09:16.960000
 And we should be able to ping it.

0:09:16.960000 --> 0:09:23.180000
 And we can. And we can also see that as
 far as that loop back is concerned,

0:09:23.180000 --> 0:09:28.680000
 the path that's been learned, or I should
 say the preferred path, is fast

0:09:28.680000 --> 0:09:30.500000
 ethernet zero slash zero.

0:09:30.500000 --> 0:09:33.940000
 Which makes sense, because that path
 is faster than the serial link on

0:09:33.940000 --> 0:09:36.340000
 top. Now that leads us
 to ask the question.

0:09:36.340000 --> 0:09:40.780000
 You might be asked in the CCNA, how would
 you discover all of the possible

0:09:40.780000 --> 0:09:45.540000
 paths that a router has learned to
 a particular destination network?

0:09:45.540000 --> 0:09:49.980000
 Well, you should know the command
 show IP, EIGRP topology.

0:09:49.980000 --> 0:09:52.760000
 Which gives you a high level
 sort of summary view.

0:09:52.760000 --> 0:09:57.460000
 And looking at this, you might initially
 think, oh, well, router one has

0:09:57.460000 --> 0:10:00.580000
 only learned about the 44 network
 via the fast ethernet path.

0:10:00.580000 --> 0:10:04.160000
 Something must be wrong, because why
 didn't he also learn it about the

0:10:04.160000 --> 0:10:07.280000
 serial link? Even though that might
 not be the link he's actually using

0:10:07.280000 --> 0:10:10.720000
 in his routing table, it should
 still be in here, right?

0:10:10.720000 --> 0:10:16.280000
 Remember, this particular command only
 shows you your successors and feasible

0:10:16.280000 --> 0:10:19.640000
 successors. Now, if you don't know what
 those terms are, better go look

0:10:19.640000 --> 0:10:22.540000
 them up, because that's something the
 CCNA routing and switching exam

0:10:22.540000 --> 0:10:25.360000
 is going to expect you to
 know what those terms are.

0:10:25.360000 --> 0:10:29.000000
 So this only shows you successors
 and feasible successors.

0:10:29.000000 --> 0:10:33.420000
 There's a possibility that you could
 learn of an alternate path to a route

0:10:33.420000 --> 0:10:36.720000
 that doesn't meet either
 one of those conditions.

0:10:36.720000 --> 0:10:39.800000
 It's not a successor or
 a feasible successor.

0:10:39.800000 --> 0:10:44.360000
 Why? Well, if an incoming route comes
 into you and it does not meet the

0:10:44.360000 --> 0:10:49.340000
 feasibility condition, which is the
 condition that EIGRP uses to try to

0:10:49.340000 --> 0:10:50.960000
 detect routing loops.

0:10:50.960000 --> 0:10:54.460000
 If it does not meet the feasibility
 condition, it will not be classified

0:10:54.460000 --> 0:10:58.120000
 as either a successor or
 a feasible successor.

0:10:58.120000 --> 0:11:02.160000
 So how can we tell in our topology
 table, if we actually have learned

0:11:02.160000 --> 0:11:06.300000
 about this route via the serial link,
 but because it came in and the metric

0:11:06.300000 --> 0:11:09.780000
 was so horrible, it was considered
 as a possible loop.

0:11:09.780000 --> 0:11:12.420000
 And it did not meet the
 feasibility condition.

0:11:12.420000 --> 0:11:13.740000
 Well, here's how we can tell.

0:11:13.740000 --> 0:11:16.860000
 We can use that exact same command
 we just used, but with the keyword

0:11:16.860000 --> 0:11:21.260000
 of all dash links.

0:11:21.260000 --> 0:11:25.320000
 And now we can see, as far as the 44
 network is concerned, yes, the fast

0:11:25.320000 --> 0:11:29.780000
 e-thon at 00 is the successor,
 but here it is down here.

0:11:29.780000 --> 0:11:34.420000
 And wow, why didn't
 this be considered?

0:11:34.420000 --> 0:11:35.340000
 Well, look at this.

0:11:35.340000 --> 0:11:40.280000
 Right now, our feasible distance, our
 total distance for the best fastest

0:11:40.280000 --> 0:11:45.160000
 path is 435,200.

0:11:45.160000 --> 0:11:51.120000
 Well, our neighbor downstairs on the
 serial link, he advertised a path

0:11:51.120000 --> 0:11:55.680000
 of a little bit of over
 2 million as the metric.

0:11:55.680000 --> 0:11:59.040000
 That does not meet the
 feasibility condition.

0:11:59.040000 --> 0:12:01.720000
 And if you want to know more about the
 feasibility condition, you definitely

0:12:01.720000 --> 0:12:04.920000
 want to research that because
 that is also a solution.

0:12:04.920000 --> 0:12:09.120000
 So, we have a CCNA routing
 and switching level topic.

0:12:09.120000 --> 0:12:15.120000
 So, at this point, that concludes this
 particular section of the video

0:12:15.120000 --> 0:12:18.800000
 where we've done our basic
 EIGRP configuration.

0:12:18.800000 --> 0:12:22.000000
 So, stay tuned for the next videos
 coming up to add the authentication

0:12:22.000000 --> 0:12:23.580000
 element into this.

0:12:23.580000 --> 0:12:27.740000
 And then lastly, we're going to manipulate
 EIGRP so it actually prefers

0:12:27.740000 --> 0:12:34.920000
 that slower path on the top.

