WEBVTT

0:00:08.420000 --> 0:00:12.000000
 Okay, so here we are in part
 three of our CCNA switch lab.

0:00:12.000000 --> 0:00:15.180000
 And now we're finally going to start
 doing some switching stuff by jumping

0:00:15.180000 --> 0:00:19.240000
 over to those ether switch modules
 in our routers and configuring the

0:00:19.240000 --> 0:00:21.180000
 switching component of that.

0:00:21.180000 --> 0:00:25.380000
 So here we're going to configure
 VTP and VLANs on the routers.

0:00:25.380000 --> 0:00:29.840000
 And by the time we're done with this,
 we should have end-to-end connectivity

0:00:29.840000 --> 0:00:33.900000
 all the way across from one router
 to the other at the far side.

0:00:33.900000 --> 0:00:36.820000
 We won't be done yet because we'll still
 have to manipulate a little bit

0:00:36.820000 --> 0:00:38.000000
 of spanning tree.

0:00:38.000000 --> 0:00:41.260000
 We'll do that in the final video, but
 we should have end-to-end connectivity

0:00:41.260000 --> 0:00:44.940000
 by the time we're done with
 the required tasks here.

0:00:44.940000 --> 0:00:49.820000
 Okay, so looking at our topology diagram,
 we can see that right now what's

0:00:49.820000 --> 0:00:55.440000
 left for us is we have to do here.


0:00:55.440000 --> 0:00:59.360000
 We want to make sure that VTP is set
 up so this guy is a client and he

0:00:59.360000 --> 0:01:04.160000
 learns of the routes
 of the VLANs via VTP.

0:01:04.160000 --> 0:01:09.640000
 So let's start with VTP
 and then do the VLANs.

0:01:09.640000 --> 0:01:15.680000
 So I'm going to go on to the ether switch
 router two, which in this particular

0:01:15.680000 --> 0:01:19.820000
 case, now before I do this, I've been
 saving my configs all along the

0:01:19.820000 --> 0:01:22.620000
 way. So I'm going to
 take a snapshot.

0:01:22.620000 --> 0:01:28.280000
 I'm going to turn everybody off, take
 a snapshot right now, and we'll

0:01:28.280000 --> 0:01:38.940000
 call this no VLAN or STP.

0:01:38.940000 --> 0:01:45.400000
 Okay, close. Let's bring
 everything back online.

0:01:45.400000 --> 0:01:49.120000
 So the majority of the configuration
 for this is going to be between ether

0:01:49.120000 --> 0:01:50.940000
 switch one and ether switch two.

0:01:50.940000 --> 0:01:53.260000
 So let's just bring
 both of those up.

0:01:53.260000 --> 0:02:05.380000
 All right, let's put them
 in the correct order here.

0:02:05.380000 --> 0:02:12.720000
 Okay, ether switch one,
 which is the guy on top.

0:02:12.720000 --> 0:02:19.720000
 Let's start with ether switch
 two as the VTP client.

0:02:19.720000 --> 0:02:24.340000
 So here with VTP first, we have
 to create a VTP domain name.

0:02:24.340000 --> 0:02:27.280000
 And we'll just give it I and E.

0:02:27.280000 --> 0:02:32.700000
 And we'll make it the same here.

0:02:32.700000 --> 0:02:38.560000
 Okay, now the ether switch one is going
 to be a VTP server by default

0:02:38.560000 --> 0:02:40.900000
 because that's the
 way Cisco works it.

0:02:40.900000 --> 0:02:48.060000
 So we just have to configure
 ether switch two as a client.

0:02:48.060000 --> 0:02:52.580000
 Okay, great. Now in order for VTP to
 work, it has to work over functional

0:02:52.580000 --> 0:03:00.040000
 VLAN trunks. Now these ether switch modules,
 unlike real physical switches,

0:03:00.040000 --> 0:03:03.040000
 do not support the dynamic
 trunking protocol.

0:03:03.040000 --> 0:03:06.980000
 If these were real switches, the links
 between them quite possibly would

0:03:06.980000 --> 0:03:13.840000
 already be 802.1 because they'd probably
 dynamic and have exchanged DTP

0:03:13.840000 --> 0:03:18.480000
 or maybe not. But in this particular
 case, in order to form a trunk, we

0:03:18.480000 --> 0:03:20.980000
 have to manually do it on
 ether switch modules.

0:03:20.980000 --> 0:03:24.120000
 We cannot use dynamic desirable
 or dynamic auto.

0:03:24.120000 --> 0:03:26.620000
 Those keywords don't
 even exist for us.

0:03:26.620000 --> 0:03:30.940000
 So that being the case, if I go back
 to my topology diagram, we've got

0:03:30.940000 --> 0:03:34.460000
 one slash nine and
 one slash fifteen.

0:03:34.460000 --> 0:03:39.260000
 So I'll just go ahead and use the
 interface range command for that.

0:03:39.260000 --> 0:03:42.400000
 Interface range past ethernet
 one slash nine.

0:03:42.400000 --> 0:03:46.920000
 And because it's a non-continuous
 range, I have to use the comma.

0:03:46.920000 --> 0:03:51.740000
 And we'll just say switch
 port mode trunk.

0:03:51.740000 --> 0:03:54.840000
 No shut, just for good measure.

0:03:54.840000 --> 0:03:58.380000
 Save our configuration.

0:03:58.380000 --> 0:04:01.480000
 Okay, so that's ether switch two.

0:04:01.480000 --> 0:04:04.980000
 Now let's just do the same
 thing in ether switch one.

0:04:04.980000 --> 0:04:10.720000
 Interface range past ethernet one slash
 nine comma one slash fifteen.

0:04:10.720000 --> 0:04:16.480000
 Switch port mode trunk.

0:04:16.480000 --> 0:04:23.340000
 Save it. Okay, and for the CCNA routing
 and switching exam, you should

0:04:23.340000 --> 0:04:28.240000
 be aware of what command you would type
 to verify if the trunks are actually

0:04:28.240000 --> 0:04:31.300000
 functional. There's actually a couple
 of things you can do, but my favorite

0:04:31.300000 --> 0:04:34.680000
 command is show interfaces trunk.

0:04:34.680000 --> 0:04:39.100000
 And it shows us right here.

0:04:39.100000 --> 0:04:44.140000
 You can also do show interface, type in
 the interface name, and then switch

0:04:44.140000 --> 0:04:48.900000
 port. And what you're looking
 for is operational mode.

0:04:48.900000 --> 0:04:52.460000
 Administrative mode means what
 am I configured to do?

0:04:52.460000 --> 0:04:56.140000
 Operational mode means what
 am I actually doing?

0:04:56.140000 --> 0:04:58.780000
 And right now it says trunk.

0:04:58.780000 --> 0:04:59.920000
 So we're good to go there.

0:04:59.920000 --> 0:05:04.820000
 So now the last thing we should be able
 to do is here in our VTP server,

0:05:04.820000 --> 0:05:08.420000
 we should be able to create our two
 VLANs, VLANs four and five, and we

0:05:08.420000 --> 0:05:13.380000
 should see them propagated downstream
 to our VTP client.

0:05:13.380000 --> 0:05:18.240000
 VLAN four dash five.

0:05:18.240000 --> 0:05:23.460000
 That allows us to create multiple
 VLANs at the same time.

0:05:23.460000 --> 0:05:27.760000
 Save our configuration.

0:05:27.760000 --> 0:05:31.860000
 Now if we were in a regular switch, we
 could just do the show VLAN command

0:05:31.860000 --> 0:05:34.940000
 to see what VLANs are in here.

0:05:34.940000 --> 0:05:42.380000
 But in this particular case, we have
 to do show VLAN dash switch.

0:05:42.380000 --> 0:05:48.860000
 And we can see that VLANs four
 and five have been created.

0:05:48.860000 --> 0:05:52.020000
 Show interface trunk.

0:05:52.020000 --> 0:05:55.100000
 Verify is forced that those VLANs
 are allowed on the trunk.

0:05:55.100000 --> 0:05:57.240000
 They're actually right
 now, they are active.

0:05:57.240000 --> 0:05:58.900000
 We can see that.

0:05:58.900000 --> 0:06:04.000000
 And so now if we go down to switch two,
 hopefully it has learned of those

0:06:04.000000 --> 0:06:09.580000
 VLANs via VTP. Show
 VLAN dash switch.

0:06:09.580000 --> 0:06:14.440000
 And he has. He has
 learned of those.

0:06:14.440000 --> 0:06:17.000000
 Save our configuration.

0:06:17.000000 --> 0:06:21.920000
 So at this point now, our trunks are
 functional all the way across.

0:06:21.920000 --> 0:06:25.060000
 Whatever VLANs we're going to be using
 have been configured and have been

0:06:25.060000 --> 0:06:32.880000
 propagated. So if we go to our diagram,
 router one now should be able

0:06:32.880000 --> 0:06:38.340000
 to ping either one of these IP addresses
 on router three, and he should

0:06:38.340000 --> 0:06:40.180000
 be able to get a response back.

0:06:40.180000 --> 0:06:53.180000
 So let's see if that
 is indeed the case.

0:06:53.180000 --> 0:06:55.780000
 All right, let's bring
 up router one.

0:06:55.780000 --> 0:07:12.640000
 Here's the moment of truth.

0:07:12.640000 --> 0:07:14.940000
 This is good though, this is going to give
 us a little bit of troubleshooting

0:07:14.940000 --> 0:07:19.300000
 experience. Okay, so step number one,
 we previously configured some static

0:07:19.300000 --> 0:07:21.040000
 routes in here, but let's verify.

0:07:21.040000 --> 0:07:23.540000
 Does he actually have the routing
 information to get there?

0:07:23.540000 --> 0:07:29.820000
 Show IP route. Okay, so he
 does have a static route.

0:07:29.820000 --> 0:07:38.940000
 Can he ping his neighbor, his next
 hop neighbor, ping 1.2.4.2?

0:07:38.940000 --> 0:07:41.440000
 Okay, he is not pinging.

0:07:41.440000 --> 0:07:42.960000
 Ah, I think I know what
 the problem is.

0:07:42.960000 --> 0:07:45.600000
 We forgot one little
 step, I believe.

0:07:45.600000 --> 0:07:50.140000
 I think the problem is we forgot to
 configure this interface right here

0:07:50.140000 --> 0:07:54.060000
 on Ether Switch 2 as a trunk.

0:07:54.060000 --> 0:07:55.660000
 I think that's our problem.

0:07:55.660000 --> 0:07:58.800000
 So let's go back to
 Ether Switch 2.

0:07:58.800000 --> 0:08:02.580000
 Show run interface fast
 ethernet 1 slash zero.

0:08:02.580000 --> 0:08:06.600000
 And yes, it is not configured
 as a trunk.

0:08:06.600000 --> 0:08:13.440000
 Okay, so config T interface fast ethernet
 1 slash zero, switch port mode

0:08:13.440000 --> 0:08:18.460000
 trunk. And that should
 be all we have to do.

0:08:18.460000 --> 0:08:24.640000
 Now it's carrying all the VLANs.

0:08:24.640000 --> 0:08:28.320000
 So now we should be able to ping, router
 1 should be able to ping router

0:08:28.320000 --> 0:08:37.000000
 2. It might take a little bit of time
 because remember spanning tree has

0:08:37.000000 --> 0:08:40.360000
 to converge and go from listening
 to learning to forwarding.

0:08:40.360000 --> 0:08:51.400000
 And that takes a little
 bit of time.

0:08:51.400000 --> 0:08:55.580000
 Let's verify that spanning tree for
 VLANs 4 and 5 does have a forwarding

0:08:55.580000 --> 0:09:00.120000
 path. So what we should see, I don't
 know which one of these switches

0:09:00.120000 --> 0:09:01.780000
 is going to be the spanning
 tree root bridge.

0:09:01.780000 --> 0:09:04.440000
 We'll get into that in the very
 last video of this section.

0:09:04.440000 --> 0:09:08.480000
 But what we should see is that VLANs
 4 and 5 are both allowed on this

0:09:08.480000 --> 0:09:10.380000
 interface because it's trunking.

0:09:10.380000 --> 0:09:12.800000
 This interface should be
 in the forwarding state.

0:09:12.800000 --> 0:09:16.360000
 It should be designated
 for both VLANs 4 and 5.

0:09:16.360000 --> 0:09:17.600000
 Same thing over here.

0:09:17.600000 --> 0:09:19.220000
 Ah, I think that's
 the other problem.

0:09:19.220000 --> 0:09:22.680000
 I forgot to configure this
 as an 802.1Q trunk.

0:09:22.680000 --> 0:09:24.660000
 That's probably what's
 the problem.

0:09:24.660000 --> 0:09:30.700000
 So let's go over to my diagram here,
 my GNS3, and I need to configure

0:09:30.700000 --> 0:09:37.440000
 fast ethernet 1, 0
 on Ether Switch 1.

0:09:37.440000 --> 0:09:44.100000
 Switch port mode trunk.

0:09:44.100000 --> 0:09:47.400000
 All right, let's wait for it to
 go into the forwarding state.

0:09:47.400000 --> 0:09:51.920000
 Show spanning-tree interface
 fast ethernet 1, 0.

0:09:51.920000 --> 0:09:57.760000
 Right now, it says that
 it is listening.

0:09:57.760000 --> 0:10:01.980000
 So we have to wait until
 it goes forwarding.

0:10:01.980000 --> 0:10:05.420000
 And now it is learning.

0:10:05.420000 --> 0:10:13.640000
 And now it is forwarding.

0:10:13.640000 --> 0:10:19.000000
 All right, so now we should have
 end-to-end connectivity.

0:10:19.000000 --> 0:10:28.660000
 First of all, it can router
 1, ping router 2.

0:10:28.660000 --> 0:10:36.100000
 Now we might need a little bit
 more troubleshooting here.

0:10:36.100000 --> 0:10:47.520000
 All right, let's see if we
 can troubleshoot this.

0:10:47.520000 --> 0:10:48.720000
 Starting with the physical layer.

0:10:48.720000 --> 0:10:53.380000
 Show IP interface brief.

0:10:53.380000 --> 0:10:57.200000
 And fast ethernet 0, 0 is
 what we're looking for.

0:10:57.200000 --> 0:11:01.480000
 It is up. The various
 subinterfaces are up.

0:11:01.480000 --> 0:11:05.660000
 And the various subinterfaces have
 been allocated that IP addresses in

0:11:05.660000 --> 0:11:09.120000
 the correct VLANs and subnets.

0:11:09.120000 --> 0:11:10.280000
 So that looks right.

0:11:10.280000 --> 0:11:17.960000
 We already confirmed that he has
 the correct static routes.

0:11:17.960000 --> 0:11:21.160000
 Okay, so there's nothing
 wrong on router 1.

0:11:21.160000 --> 0:11:25.440000
 Okay, let's move down
 the chain now.

0:11:25.440000 --> 0:11:27.920000
 Let's go over to ether switch 2.

0:11:27.920000 --> 0:11:33.780000
 Ether switch 2. Let's make sure the
 fast ethernet 1, 0 is trunking.

0:11:33.780000 --> 0:11:39.460000
 Show interface fast ethernet
 1, 0 switch port.

0:11:39.460000 --> 0:11:42.260000
 Operational mode is trunk.

0:11:42.260000 --> 0:11:45.240000
 Show interface trunk.

0:11:45.240000 --> 0:11:50.560000
 1 size 0 is on and it is
 allowing VLANs 4 and 5.

0:11:50.560000 --> 0:11:52.140000
 Okay, that's good.

0:11:52.140000 --> 0:11:56.120000
 We also see that these other two interfaces
 leading upstream to ether

0:11:56.120000 --> 0:11:57.900000
 switch 1 are on.

0:11:57.900000 --> 0:12:00.820000
 Also allowing VLANs 4 and 5.

0:12:00.820000 --> 0:12:06.560000
 Let's look at the spanning
 tree state of VLAN 4.

0:12:06.560000 --> 0:12:10.400000
 VLAN 4 is executing
 basically 802.1d.

0:12:10.400000 --> 0:12:17.000000
 And what we're looking for here is
 it says that 1 slash 0, which goes

0:12:17.000000 --> 0:12:19.300000
 down to router 1, is forwarding.

0:12:19.300000 --> 0:12:26.560000
 1 slash 9, which goes upstream to
 ether switch 1 is forwarding.

0:12:26.560000 --> 0:12:28.440000
 And 1 slash 15 is blocking.

0:12:28.440000 --> 0:12:31.020000
 That's fine. We just need one
 of those upstream interfaces.

0:12:31.020000 --> 0:12:34.680000
 So right now the one here on the left
 is the one that's in the forwarding

0:12:34.680000 --> 0:12:38.440000
 state. That's for VLAN
 4, about VLAN 5.

0:12:38.440000 --> 0:12:42.400000
 I would expect VLAN 5 to
 look exactly the same.

0:12:42.400000 --> 0:12:46.760000
 Yep, the port going to the router is
 forwarding and the lower numbered

0:12:46.760000 --> 0:12:49.400000
 port is forwarding going upstream.


0:12:49.400000 --> 0:12:54.780000
 Everything looks fine
 on ether switch 2.

0:12:54.780000 --> 0:12:57.880000
 Now let's go over
 to ether switch 1.

0:12:57.880000 --> 0:13:07.140000
 Show spanning dash tree VLAN 4.

0:13:07.140000 --> 0:13:12.440000
 Okay, so 1 slash 0, which goes across
 to router 2, is forwarding.

0:13:12.440000 --> 0:13:15.740000
 1 slash 9 is forwarding.

0:13:15.740000 --> 0:13:17.080000
 1 slash 15 is forwarding.

0:13:17.080000 --> 0:13:19.800000
 Okay, so this guy is probably
 the root bridge.

0:13:19.800000 --> 0:13:25.820000
 Okay, so so far everything
 looks fine.

0:13:25.820000 --> 0:13:30.060000
 Now let's go across to router 2.

0:13:30.060000 --> 0:13:35.600000
 Last thing to check here.

0:13:35.600000 --> 0:13:44.440000
 Show run. Let's take a look
 at his fast ethernet 00.

0:13:44.440000 --> 0:13:46.860000
 Okay, up. Here's our problem.

0:13:46.860000 --> 0:13:49.360000
 Fast ethernet 00, I forgot
 to bring it up.

0:13:49.360000 --> 0:13:59.880000
 It's shut down. That could
 explain our problem.

0:13:59.880000 --> 0:14:03.220000
 Show IP interface brief.

0:14:03.220000 --> 0:14:07.060000
 All right, fast ethernet 00, which is
 trunking, is up, and the other two

0:14:07.060000 --> 0:14:09.720000
 interfaces are up.

0:14:09.720000 --> 0:14:14.680000
 Okay, so now, which was a good troubleshooting
 exercise, we should be

0:14:14.680000 --> 0:14:17.820000
 able to ping end to end from R1.

0:14:17.820000 --> 0:14:20.580000
 Ping 1, no, 2.3.2.3.

0:14:20.580000 --> 0:14:21.620000
 Let's go for the gold here.

0:14:21.620000 --> 0:14:23.600000
 Let's try to ping all the way.

0:14:23.600000 --> 0:14:27.120000
 Come on, you can do it.

0:14:27.120000 --> 0:14:30.120000
 There we go. Fantastic.

0:14:30.120000 --> 0:14:32.940000
 And ping the other side, 3.2.3.3.

0:14:32.940000 --> 0:14:37.620000
 He has to arp for it.

0:14:37.620000 --> 0:14:40.360000
 Actually, he doesn't have to arp for
 it, but he does have to arp for his

0:14:40.360000 --> 0:14:44.220000
 next hop. And then
 we have success.

0:14:44.220000 --> 0:14:48.820000
 Okay, so at this point, let me
 bring the diagram over here.

0:14:48.820000 --> 0:14:51.580000
 Let me just renumber these interfaces
 for a second because these are not

0:14:51.580000 --> 0:15:05.960000
 correct. Okay, so we have 1 slash 9,
 1 slash 15, 1 slash 9, 1 slash 15.

0:15:05.960000 --> 0:15:09.060000
 And this over here, I
 believe, is 1 slash 0.

0:15:09.060000 --> 0:15:13.820000
 Okay, so right now, because of the
 way spanning tree is configured, or

0:15:13.820000 --> 0:15:18.200000
 by the way, it just ended up, we didn't
 configure it this way, what we've

0:15:18.200000 --> 0:15:24.840000
 got is this right here is
 in the blocking state.

0:15:24.840000 --> 0:15:34.120000
 The remaining three interfaces
 are forwarding.

0:15:34.120000 --> 0:15:41.160000
 And so when router one pings anything
 over here, everything he pings is

0:15:41.160000 --> 0:15:43.160000
 going to have to take
 the forwarding path.

0:15:43.160000 --> 0:15:46.900000
 It's going to go this way, both
 the pings and the reply packets.

0:15:46.900000 --> 0:15:54.600000
 However, if you remember, if we go right
 back to our original lab specifications,

0:15:54.600000 --> 0:16:02.200000
 our objectives, it said, as we can
 see here, ensure that packets sent

0:16:02.200000 --> 0:16:06.960000
 between router one and router two traverse
 across the highest numbered

0:16:06.960000 --> 0:16:11.300000
 ports. So right now, it's going across
 the lowest numbered ports, 1 slash

0:16:11.300000 --> 0:16:15.500000
 9. But in reality, we're supposed to
 be having it go across the highest

0:16:15.500000 --> 0:16:20.880000
 numbered ports, which in this case means
 we need to somehow get this path

0:16:20.880000 --> 0:16:24.300000
 forwarding and this path blocking.


0:16:24.300000 --> 0:16:29.620000
 And that's the last thing we're going
 to do in the very next video.

0:16:29.620000 --> 0:16:30.400000
 Thanks for watching!

