WEBVTT

0:00:08.380000 --> 0:00:13.140000
 So here we are at the last video for
 this particular CCNA-EI-JRP lab where

0:00:13.140000 --> 0:00:15.960000
 we're going to do some
 path manipulation.

0:00:15.960000 --> 0:00:22.120000
 So at present when router one is pinging
 the loop back of router four,

0:00:22.120000 --> 0:00:25.140000
 I can expect that's going to
 take this fast ethernet link.

0:00:25.140000 --> 0:00:27.260000
 How would I actually prove that?

0:00:27.260000 --> 0:00:28.560000
 Well, here's what
 we're going to do.

0:00:28.560000 --> 0:00:30.860000
 Let's go ahead and start
 the routers up.

0:00:30.860000 --> 0:00:32.340000
 And let's go into router one.

0:00:32.340000 --> 0:00:34.340000
 And what we're going to do is we're
 going to look at his routing table.

0:00:34.340000 --> 0:00:36.940000
 And we're going to see, according to
 his routing table, if he was going

0:00:36.940000 --> 0:00:42.840000
 to route packets to the 44, 44, 44 network,
 what would his egress interface

0:00:42.840000 --> 0:00:50.620000
 be? Where would he
 send those packets?

0:00:50.620000 --> 0:00:58.120000
 Show IP route. And we can see he's learned
 of that network and he would

0:00:58.120000 --> 0:01:02.180000
 route them out the fast ethernet
 link, just like we thought.

0:01:02.180000 --> 0:01:07.440000
 Okay, now we also saw previously if we
 did show IP, egress, rp, topology,

0:01:07.440000 --> 0:01:12.680000
 all dash links, we did see that he had
 learned about that route via the

0:01:12.680000 --> 0:01:14.140000
 slow speed serial.

0:01:14.140000 --> 0:01:21.160000
 So what we need to do is we need to
 ultimately make eirp follow the top

0:01:21.160000 --> 0:01:26.240000
 link. We have to trick it or fool it
 into thinking that the top link is

0:01:26.240000 --> 0:01:28.680000
 actually the better path.

0:01:28.680000 --> 0:01:30.680000
 Well let me ask you a question.

0:01:30.680000 --> 0:01:34.680000
 By default, when eirp is coming up with
 its metric, that big long number

0:01:34.680000 --> 0:01:39.260000
 that we call distance, what are the variables
 that it plugs into the formula

0:01:39.260000 --> 0:01:41.900000
 to come up with its
 distance value?

0:01:41.900000 --> 0:01:46.220000
 What are the default variables otherwise
 known as vector metrics?

0:01:46.220000 --> 0:01:49.460000
 Well hopefully you quickly answered
 bandwidth and delay.

0:01:49.460000 --> 0:01:52.760000
 Bandwidth and delay are part of that
 formula, the default formula.

0:01:52.760000 --> 0:01:56.780000
 Now it's recommended that you do not
 touch the bandwidth on an interface

0:01:56.780000 --> 0:02:00.080000
 because bandwidth is used
 by other things as well.

0:02:00.080000 --> 0:02:03.560000
 So ideally if you want to manipulate
 eirp, you're going to manipulate

0:02:03.560000 --> 0:02:05.180000
 the delay variable.

0:02:05.180000 --> 0:02:08.420000
 So let's go ahead and
 start by doing this.

0:02:08.420000 --> 0:02:15.620000
 Let's go ahead and in here, let's try
 to take this interface right here,

0:02:15.620000 --> 0:02:19.100000
 serial 2 slash 0, and
 let's lower the delay.

0:02:19.100000 --> 0:02:24.040000
 Actually let's lower it to the minimum
 value and see if that works to

0:02:24.040000 --> 0:02:27.180000
 get our desired result.

0:02:27.180000 --> 0:02:30.100000
 Alright so let's go into router 1.


0:02:30.100000 --> 0:02:34.580000
 Actually I'm not sure if when I took
 my last snapshot I had the routers

0:02:34.580000 --> 0:02:36.020000
 turned off or not.

0:02:36.020000 --> 0:02:40.360000
 So I'm going to go ahead and retake
 that snapshot because I suspect I

0:02:40.360000 --> 0:02:56.160000
 did not. Okay so now let's
 turn them all back on.

0:02:56.160000 --> 0:03:02.740000
 And let's go into router 1 and go onto
 a serial 2 slash 0 and reduce the

0:03:02.740000 --> 0:03:05.740000
 delay to the minimum possible value
 to make it look like there's hardly

0:03:05.740000 --> 0:03:12.920000
 any delay on that
 interface at all.

0:03:12.920000 --> 0:03:19.480000
 Interface serial 2 slash 0 and we'll
 say delay and the lowest number I

0:03:19.480000 --> 0:03:23.520000
 can select is 1, which actually because
 it's tens of microseconds means

0:03:23.520000 --> 0:03:28.940000
 I'm telling him the delay on that
 interface is 10 microseconds.

0:03:28.940000 --> 0:03:37.360000
 Save my config, show
 IP, EIJRP, topology.

0:03:37.360000 --> 0:03:42.960000
 And remember the way this works is that
 after your prefix or your network

0:03:42.960000 --> 0:03:48.760000
 what you'll see first in this output
 is the successor or if you have more

0:03:48.760000 --> 0:03:54.120000
 than one successor the successors followed
 by the feasible successors.

0:03:54.120000 --> 0:03:58.500000
 Okay so in this particular case it's
 still using fast ethernet 00 nothing

0:03:58.500000 --> 0:04:03.140000
 has changed. Okay that being the case
 let's go back to our topology now

0:04:03.140000 --> 0:04:10.120000
 and try lowering the delay on this
 upstream interface and see if that

0:04:10.120000 --> 0:04:13.680000
 will also work. So that
 is what is that?

0:04:13.680000 --> 0:04:20.880000
 That is serial 2 slash
 1 on router 2.

0:04:20.880000 --> 0:04:26.940000
 We'll minimize this, actually we'll maximize
 it and let's go back to router

0:04:26.940000 --> 0:04:38.480000
 2. Interface serial 2
 slash 1 delay of 1.

0:04:38.480000 --> 0:04:44.540000
 Save that, we're not going to need
 router 2 anymore, close him down.

0:04:44.540000 --> 0:04:48.040000
 Alright did that make
 router 1 switch over?

0:04:48.040000 --> 0:04:54.280000
 Nope, still using
 the fast ethernet.

0:04:54.280000 --> 0:04:58.860000
 Okay now before we resort to modifying
 bandwidth values is there anything

0:04:58.860000 --> 0:05:00.880000
 else we can do with delay?

0:05:00.880000 --> 0:05:05.900000
 Well in our topology here we lower
 the delay of these as far as we can

0:05:05.900000 --> 0:05:11.060000
 possibly go. Why don't we take the
 reverse approach now and why don't

0:05:11.060000 --> 0:05:17.460000
 we go to router 1's upstream interface
 and increase the delay to some

0:05:17.460000 --> 0:05:19.400000
 really horrible number.

0:05:19.400000 --> 0:05:22.800000
 So he thinks that anything going out
 that interface will experience a

0:05:22.800000 --> 0:05:29.800000
 lot of delay. So let's go back
 to router 1, we're still there.

0:05:29.800000 --> 0:05:34.980000
 Interface fast ethernet 0 slash 0,
 delay and let's give him some delay

0:05:34.980000 --> 0:05:41.560000
 of like 55, 555, so that's tens of
 microseconds so that'll actually be

0:05:41.560000 --> 0:05:53.500000
 555,550. Okay did that
 make him change?

0:05:53.500000 --> 0:05:58.820000
 Nope, still using that
 fast ethernet.

0:05:58.820000 --> 0:06:01.400000
 He hasn't switched over yet.

0:06:01.400000 --> 0:06:03.680000
 Oh there we go, it did work.

0:06:03.680000 --> 0:06:08.200000
 Look at that. Now the 44 network, the
 next line which is the successor

0:06:08.200000 --> 0:06:10.720000
 is showing as serial 2 slash 0.

0:06:10.720000 --> 0:06:17.460000
 If we do show IP route we can now see
 that the 44 network is indeed going

0:06:17.460000 --> 0:06:20.800000
 across the top path,
 the serial link.

0:06:20.800000 --> 0:06:29.140000
 And I can verify that by doing
 trace, 44, 44, 44.4.

0:06:29.140000 --> 0:06:39.440000
 And we can see the first hop was 1
.2.1.2 which was right here router 2

0:06:39.440000 --> 0:06:48.060000
 and then the next hop was 2.4.2.4
 which was this address right here.

0:06:48.060000 --> 0:06:51.280000
 Now as of this point, I'm going to
 go ahead and stop the video at this

0:06:51.280000 --> 0:06:54.900000
 point, we're not entirely done so if
 you're doing this on your own you're

0:06:54.900000 --> 0:07:00.440000
 almost there. We've got packets from
 router 1 going to router 4 taking

0:07:00.440000 --> 0:07:05.780000
 the top link but that's not going
 to affect the return traffic.

0:07:05.780000 --> 0:07:10.100000
 Router 4 is still going to believe that
 to get back to router 1 he should

0:07:10.100000 --> 0:07:11.680000
 go across this bottom path.

0:07:11.680000 --> 0:07:15.320000
 So right now what we have is what's called
 asymmetric routing where packets

0:07:15.320000 --> 0:07:19.900000
 going in one direction take one path
 and the reply packets take another.

0:07:19.900000 --> 0:07:21.240000
 How can we verify that?

0:07:21.240000 --> 0:07:28.920000
 Well let's go to router 4 and let's
 see if he was to ping back to the

0:07:28.920000 --> 0:07:33.380000
 11 network what path
 would he take?

0:07:33.380000 --> 0:07:37.420000
 And we can see that right now he's
 still taking the lower link.

0:07:37.420000 --> 0:07:40.460000
 So in order to complete this lab you're
 going to have to continue manipulating

0:07:40.460000 --> 0:07:46.400000
 metrics until router 4 also believes
 that he should take the upstream

0:07:46.400000 --> 0:07:52.300000
 serial link. And just in case you get
 stuck with that what you're going

0:07:52.300000 --> 0:07:57.520000
 to do is sort of the reverse of what
 we just did so you're going to on

0:07:57.520000 --> 0:08:04.820000
 router 4 decrease minimize the delay
 on this interface down to 1, minimize

0:08:04.820000 --> 0:08:09.940000
 the delay on this interface down to
 1 and then you're going to want to

0:08:09.940000 --> 0:08:15.160000
 maximize or really increase the delay
 on the fast ethernet interface to

0:08:15.160000 --> 0:08:19.300000
 make it look like it's just horrible and
 you don't want to go that direction.

0:08:19.300000 --> 0:08:23.200000
 And that will allow router
 4 to take the top link.

0:08:23.200000 --> 0:08:30.400000
 And that concludes this video series
 on our CCNA EIJRP lab using GNS3.

