WEBVTT

0:00:08.000000 --> 0:00:14.340000
 In the last video, I introduced you
 to the concept of VLAN Trunks, which

0:00:14.340000 --> 0:00:19.560000
 was really just on a switch, a formal
 way of identifying different broadcast

0:00:19.560000 --> 0:00:23.460000
 domains that that one switch is keeping
 track of and keeping isolated

0:00:23.460000 --> 0:00:24.940000
 from each other.

0:00:24.940000 --> 0:00:29.180000
 In the context of VLANs, we also learned
 that all the devices that are

0:00:29.180000 --> 0:00:33.960000
 in one VLAN are also at layer
 three in the same IP subnet.

0:00:33.960000 --> 0:00:35.600000
 Now, the switch is
 not aware of that.

0:00:35.600000 --> 0:00:38.260000
 If we're talking about us a regular
 layer two switch, the switch does

0:00:38.260000 --> 0:00:41.080000
 not really know anything
 about IP and subnetting.

0:00:41.080000 --> 0:00:45.240000
 All it knows is that this group of ports
 here is contained in one broadcast

0:00:45.240000 --> 0:00:49.460000
 domain. This group of ports is in a
 different broadcast domain, and the

0:00:49.460000 --> 0:00:51.740000
 two are now allowed to talk.

0:00:51.740000 --> 0:00:56.660000
 Now, that being the case, what if
 you have a situation like this?

0:00:56.660000 --> 0:01:01.420000
 And I have worked this up here in GNS3,
 so you could replicate this if

0:01:01.420000 --> 0:01:10.120000
 you want. Where I have two VLANs, so
 in this particular case, I have VLAN1

0:01:10.120000 --> 0:01:16.220000
 here and here, and it's separated
 between two different switches.

0:01:16.220000 --> 0:01:22.240000
 So if all I had was VLAN1, then this
 connection between the switches could

0:01:22.240000 --> 0:01:27.280000
 also be placed in VLAN1, and these
 guys would be able to communicate.

0:01:27.280000 --> 0:01:31.440000
 And in order to make this more of a real
 world scenario, I've also incorporated

0:01:31.440000 --> 0:01:34.960000
 DHCP server, which in this
 case is my router.

0:01:34.960000 --> 0:01:37.760000
 Later on in some of the later videos, when
 we talk a little bit more extensively

0:01:37.760000 --> 0:01:41.900000
 about DHCP, you'll actually learn how
 to configure a router or a switch

0:01:41.900000 --> 0:01:43.860000
 as a DHCP server.

0:01:43.860000 --> 0:01:47.820000
 The configuration is pretty easy, and
 it's the same whether you're on

0:01:47.820000 --> 0:01:52.860000
 a switch. Usually in real life, you
 would have in a regular network a

0:01:52.860000 --> 0:01:56.660000
 real server, like a Windows server
 or a Linux server or something like

0:01:56.660000 --> 0:01:59.320000
 that, acting as your DHCP server.

0:01:59.320000 --> 0:02:03.240000
 But in some smaller networks, you can
 get away with just having your router

0:02:03.240000 --> 0:02:06.220000
 or your switch double
 up as a DHCP server.

0:02:06.220000 --> 0:02:08.440000
 So that's what I'm doing
 here to make this simple.

0:02:08.440000 --> 0:02:13.580000
 So these two PCs here are going to have
 to get their IP information from

0:02:13.580000 --> 0:02:14.780000
 the DHCP server.

0:02:14.780000 --> 0:02:18.960000
 You can see that they are going
 to be in the 1,1,1 network.

0:02:18.960000 --> 0:02:23.180000
 And the server itself,
 the router, is 1,1,1,1.

0:02:23.180000 --> 0:02:26.880000
 Now to make things a little bit more
 interesting, I also incorporated

0:02:26.880000 --> 0:02:30.300000
 a second VLAN, VLAN2, as
 you can see right here.

0:02:30.300000 --> 0:02:32.740000
 And that's also split
 across the switches.

0:02:32.740000 --> 0:02:38.580000
 Now that poses an interesting dilemma,
 because I only have a single connection

0:02:38.580000 --> 0:02:40.800000
 here between these switches.

0:02:40.800000 --> 0:02:45.520000
 If I put that connection into VLAN1, and
 I put this connection here between

0:02:45.520000 --> 0:02:49.960000
 the switch and the router and VLAN1,
 then these two PCs will be happy.

0:02:49.960000 --> 0:02:53.860000
 We'll have one big broadcast domain that
 will, they'll be able to communicate

0:02:53.860000 --> 0:02:55.880000
 with each other via ARP.

0:02:55.880000 --> 0:02:59.120000
 Their DHCP broadcast will be able to go
 down here to the router and they'll

0:02:59.120000 --> 0:03:01.180000
 get their DHCP information.

0:03:01.180000 --> 0:03:04.840000
 But that will leave the people
 in VLAN2 out in the cold.

0:03:04.840000 --> 0:03:10.200000
 So for VLAN2, one option I could do is
 I could connect another connection

0:03:10.200000 --> 0:03:14.920000
 between these switches, put that in
 VLAN2, connect another connection

0:03:14.920000 --> 0:03:19.600000
 from the switch to the router, put that
 also in the two subnet, and then

0:03:19.600000 --> 0:03:21.500000
 our VLAN2 people would be happy.

0:03:21.500000 --> 0:03:23.960000
 They could communicate
 across the second link.

0:03:23.960000 --> 0:03:26.860000
 They could get to their DHCP
 server across this link.

0:03:26.860000 --> 0:03:31.240000
 Now that might be okay if we're
 only talking about two VLANs.

0:03:31.240000 --> 0:03:35.160000
 But in a real network, most likely
 you're going to have dozens, if not

0:03:35.160000 --> 0:03:44.580000
 hundreds, of VLANs, depending
 on how large your network is.

0:03:44.580000 --> 0:03:46.620000
 For something like this.

0:03:46.620000 --> 0:03:50.120000
 So in this particular case, it's
 a more scalable solution.

0:03:50.120000 --> 0:03:53.020000
 And when if you haven't heard that term
 scalable before, what I'm talking

0:03:53.020000 --> 0:03:57.640000
 about is designing your network in such
 a way that it has room for future

0:03:57.640000 --> 0:04:02.680000
 growth. It has room to add more subnets
 in the future, or room to add

0:04:02.680000 --> 0:04:03.700000
 more VLANs in the future.

0:04:03.700000 --> 0:04:07.600000
 So you're thinking about what features
 can I use, how can I configure

0:04:07.600000 --> 0:04:11.400000
 things that will allow me to grow
 in the future more easily?

0:04:11.400000 --> 0:04:13.760000
 That's what we mean
 by scalability.

0:04:13.760000 --> 0:04:17.400000
 So in this particular case, adding some
 extra links isn't really an option

0:04:17.400000 --> 0:04:22.300000
 for me. So what we need to do is we need
 to figure out some way that this

0:04:22.300000 --> 0:04:27.280000
 one link here between the two switches
 is actually capable of being in

0:04:27.280000 --> 0:04:30.660000
 more than one broadcast domain.

0:04:30.660000 --> 0:04:35.800000
 You see these access ports going to
 the hosts, well, an access port by

0:04:35.800000 --> 0:04:38.660000
 definition is only in
 one broadcast domain.

0:04:38.660000 --> 0:04:43.000000
 This access port right here is in the
 broadcast domain known as VLAN2.

0:04:43.000000 --> 0:04:47.860000
 And this access port up here is in the
 broadcast domain known as VLAN1.

0:04:47.860000 --> 0:04:51.100000
 But in the middle here between the
 switches and from the switch to the

0:04:51.100000 --> 0:04:56.340000
 router, I have a need to actually put
 those links into multiple VLANs.

0:04:56.340000 --> 0:05:01.760000
 And this is where the concept of
 VLAN trunks comes into play.

0:05:01.760000 --> 0:05:09.140000
 So a VLAN trunk port has two
 or more VLANs across it.

0:05:09.140000 --> 0:05:13.800000
 So as look at the last bullet point here,
 by default, all the VLAN traffic

0:05:13.800000 --> 0:05:16.580000
 is allowed from a trunk port.

0:05:16.580000 --> 0:05:20.000000
 Now we know that on a switch, let me
 ask you a review question, what was

0:05:20.000000 --> 0:05:21.880000
 the default VLAN?

0:05:21.880000 --> 0:05:24.540000
 VLAN number what is
 the default VLAN?

0:05:24.540000 --> 0:05:27.940000
 Hopefully you said VLAN1.

0:05:27.940000 --> 0:05:33.880000
 That's right. Now what is the highest
 numbered VLAN that you could create?

0:05:33.880000 --> 0:05:37.480000
 That was VLAN 4094.

0:05:37.480000 --> 0:05:40.840000
 So you had from VLAN1
 to VLAN 4094.

0:05:40.840000 --> 0:05:45.860000
 Now all those VLANs don't exist
 by default on a switch.

0:05:45.860000 --> 0:05:49.700000
 The only ones that exist by default are
 VLAN1 and then those sort of VLANs

0:05:49.700000 --> 0:05:52.860000
 in the middle like 10002
 through 10005.

0:05:52.860000 --> 0:05:59.440000
 And that's it. So what trunk ports do
 is as you create a new VLAN, let's

0:05:59.440000 --> 0:06:06.560000
 see before you even apply
 it to any access ports.

0:06:06.560000 --> 0:06:10.720000
 Because remember, using a VLAN
 is a two-step process.

0:06:10.720000 --> 0:06:16.380000
 You create the VLAN globally, config
 T and then VLAN 25, VLAN 17.

0:06:16.380000 --> 0:06:20.140000
 And then if you actually have any ports
 on the switch connecting to hosts,

0:06:20.140000 --> 0:06:25.440000
 you have to go to that port and say
 switch port access VLAN 25 or switch

0:06:25.440000 --> 0:06:29.580000
 port access VLAN 333.

0:06:29.580000 --> 0:06:34.100000
 But even before you apply the VLAN to
 an access port, the moment you type

0:06:34.100000 --> 0:06:40.200000
 in VLAN 5 or VLAN 99 and that becomes
 a VLAN in the switch, if that switch

0:06:40.200000 --> 0:06:43.500000
 has any functional VLAN trunks, so
 now we're talking about a different

0:06:43.500000 --> 0:06:48.120000
 mode now. Previously we talked
 about switch port mode access.

0:06:48.120000 --> 0:06:52.260000
 Now we're talking about a different
 mode, switch port mode trunk.

0:06:52.260000 --> 0:06:55.980000
 And when an interface is configured
 as a trunk, whatever VLANs are on

0:06:55.980000 --> 0:06:59.360000
 that switch are automatically allowed
 to go across that trunk.

0:06:59.360000 --> 0:07:04.560000
 So if I've got five broadcast domains,
 VLANs 1, 2, 3, 4 and 5, all five

0:07:04.560000 --> 0:07:08.180000
 of them will automatically
 be carried by that trunk.

0:07:08.180000 --> 0:07:09.800000
 Now that raises an interesting
 question.

0:07:09.800000 --> 0:07:21.340000
 If we go back to our diagram right here,
 if this PC, PC1 generates a frame,

0:07:21.340000 --> 0:07:25.960000
 actually let's forget about PC1 for
 a second, let's take a look at PC2.

0:07:25.960000 --> 0:07:32.200000
 If PC2 generates a frame that needs
 to go across this trunk and then go

0:07:32.200000 --> 0:07:36.700000
 down here to PC4, let's say it's a broadcast,
 maybe he is sending an art

0:07:36.700000 --> 0:07:41.600000
 request saying, hey PC4, I need
 to know what your Mac is.

0:07:41.600000 --> 0:07:47.440000
 Once that ethernet frame arrives here
 on fast ethernet 0 slash 15 of ether

0:07:47.440000 --> 0:07:52.300000
 switch 2, and let me go ahead and zoom
 in on that a little bit, right

0:07:52.300000 --> 0:07:55.100000
 there, okay, let's move
 this guy out of the way.

0:07:55.100000 --> 0:07:59.420000
 Once it comes in right here, switch
 2 has to have some way of knowing,

0:07:59.420000 --> 0:08:04.480000
 okay, this is a broadcast that just came
 in and I have actually two broadcast

0:08:04.480000 --> 0:08:10.920000
 domains I'm aware of, VLAN 1 and VLAN
 2, which broadcast domain am I allowed

0:08:10.920000 --> 0:08:13.300000
 to put this broadcast into?

0:08:13.300000 --> 0:08:16.740000
 Because when the broadcast comes across
 here, this art request, we don't

0:08:16.740000 --> 0:08:21.100000
 want him to flood it into VLAN 1 because
 it originated over here in VLAN

0:08:21.100000 --> 0:08:25.040000
 2, so it has to be flooded
 into VLAN 2.

0:08:25.040000 --> 0:08:29.060000
 So that means that as frames go back
 and forth across this trunk, there

0:08:29.060000 --> 0:08:35.800000
 has to be some way of identifying which
 broadcast domain they belong to.

0:08:35.800000 --> 0:08:40.040000
 And 802.1Q has a very creative
 way of doing this.

0:08:40.040000 --> 0:08:51.580000
 802.1Q applies an extra field to the
 layer 2 header called an 802.1Q tag.

0:08:51.580000 --> 0:08:54.900000
 Sometimes they just shorten
 it as a .1Q tag.

0:08:54.900000 --> 0:08:59.220000
 So if we were actually to look at what
 this looks like, if this was my

0:08:59.220000 --> 0:09:07.180000
 IP packet here, so from the perspective
 of Ethernet, that's just the data.

0:09:07.180000 --> 0:09:22.700000
 And we know that Ethernet adds a trailer,
 we call it an FCS to the front

0:09:22.700000 --> 0:09:25.820000
 end. Review question.

0:09:25.820000 --> 0:09:28.680000
 Very first field of
 an Ethernet header.

0:09:28.680000 --> 0:09:30.920000
 What do we call that field?

0:09:30.920000 --> 0:09:32.440000
 That is the preamble.

0:09:32.440000 --> 0:09:34.780000
 I'll just put P-R-E.

0:09:34.780000 --> 0:09:36.120000
 That's the preamble.

0:09:36.120000 --> 0:09:37.720000
 What follows the preamble?

0:09:37.720000 --> 0:09:41.640000
 That is the destination Mac.

0:09:41.640000 --> 0:09:44.180000
 What follows the destination Mac?

0:09:44.180000 --> 0:09:47.500000
 That is the source Mac.

0:09:47.500000 --> 0:09:52.660000
 Now, in a regular Ethernet frame, what
 typically follows the source Mac?

0:09:52.660000 --> 0:09:57.120000
 That would be the type
 code, the type field.

0:09:57.120000 --> 0:10:01.400000
 So there would be a number that we would
 put in here if this is IP version

0:10:01.400000 --> 0:10:05.100000
 4. There would be a different number
 we'd put in here if it's IP version

0:10:05.100000 --> 0:10:10.680000
 6. Well, if this Ethernet frame is going
 across a VLAN trunk, and it has

0:10:10.680000 --> 0:10:14.740000
 to be identified as belonging to a particular
 VLAN, we actually put our

0:10:14.740000 --> 0:10:22.040000
 tag right here. So the type field
 actually contains the tag.

0:10:22.040000 --> 0:10:28.720000
 So now here, we have a special number,
 a type number that says this is

0:10:28.720000 --> 0:10:35.020000
 802.1q. So instead of the type field
 saying, oh, I'm carrying IP version

0:10:35.020000 --> 0:10:39.940000
 4, or I'm carrying IP version 6, there's
 actually another reserve number

0:10:39.940000 --> 0:10:42.980000
 that says this is a .1q tag.

0:10:42.980000 --> 0:10:45.460000
 Then there's a couple of other fields
 in here that we don't really care

0:10:45.460000 --> 0:10:46.780000
 about all that much.

0:10:46.780000 --> 0:10:50.460000
 And then here is where
 we put the VLAN.

0:10:50.460000 --> 0:10:56.580000
 So if this frame belongs to VLAN 55,
 you would see the number 55 in here.

0:10:56.580000 --> 0:11:01.820000
 If it belongs to VLAN 6, you would
 see the number 6 in here.

0:11:01.820000 --> 0:11:05.980000
 Now, you might, if I just left it that
 way, I would be doing you a disservice

0:11:05.980000 --> 0:11:10.000000
 because I'd be letting you think, okay,
 every frame that goes across the

0:11:10.000000 --> 0:11:14.380000
 VLAN trunk has a special tag with that
 actually indicates the number of

0:11:14.380000 --> 0:11:18.260000
 the VLAN. And that is
 true 99% of the time.

0:11:18.260000 --> 0:11:20.320000
 But take a look at the
 second bullet here.

0:11:20.320000 --> 0:11:25.160000
 It says, all traffic except the native
 VLAN is inserted with an 802.1q

0:11:25.160000 --> 0:11:32.760000
 tag. By default, the native VLAN is
 VLAN 1, which means that when, if

0:11:32.760000 --> 0:11:37.140000
 I'm a switch, and let's say I just
 got a frame on VLAN 1, I say, okay,

0:11:37.140000 --> 0:11:42.000000
 I need to send it to you, you're another
 switch, and we have a 802.1q

0:11:42.000000 --> 0:11:48.240000
 tag between us. I'm sorry, we have
 an 802.1q VLAN trunk between us.

0:11:48.240000 --> 0:11:52.480000
 Well, if I can put a VLAN 1 frame
 on here, I'm not going to tag it.

0:11:52.480000 --> 0:11:56.080000
 So when you receive it, it's just going
 to look like any other Ethernet

0:11:56.080000 --> 0:11:59.880000
 frame. You'll have some Typecode in there
 that says IP version 4, or maybe

0:11:59.880000 --> 0:12:04.140000
 a Typecode that says IP version 6, but
 it'll just look like a normal Ethernet

0:12:04.140000 --> 0:12:10.840000
 frame to you. Now, if I receive a frame
 on VLAN 7, as an example, then

0:12:10.840000 --> 0:12:15.440000
 before I put on this wire, I'm going
 to modify the Typecode to say, this

0:12:15.440000 --> 0:12:19.800000
 is 802.1q, and this frame
 belongs to VLAN 7.

0:12:19.800000 --> 0:12:28.780000
 So when you get it, you'll actually see
 that in this VLAN trunk will have

0:12:28.780000 --> 0:12:34.600000
 a tag unless it belongs to the broadcast
 domain known as VLAN 1.

0:12:34.600000 --> 0:12:36.100000
 Those frames are untouched.

0:12:36.100000 --> 0:12:38.820000
 They go across the trunk
 in their native format.

0:12:38.820000 --> 0:12:40.140000
 They are untouched.

0:12:40.140000 --> 0:12:42.220000
 That's why we call
 it the native VLAN.

0:12:42.220000 --> 0:12:46.800000
 Now, as with pretty much everything
 else, if you have a desire to do so,

0:12:46.800000 --> 0:12:49.360000
 you can change the native
 VLAN to something else.

0:12:49.360000 --> 0:12:53.640000
 But the main thing is, if we change
 it, you and I both have to agree.

0:12:53.640000 --> 0:12:57.040000
 If I decide that, okay, the frames
 I put on this trunk are going to be

0:12:57.040000 --> 0:13:01.800000
 untagged, just regular frames that
 belong to VLAN 99, you need to know

0:13:01.800000 --> 0:13:06.760000
 that. You need to have that configured
 because how else would you know?

0:13:06.760000 --> 0:13:09.560000
 Like, let's say that I
 kept that as a secret.

0:13:09.560000 --> 0:13:13.800000
 Let's say on my switch, I decided, okay,
 I'm not going to use VLAN 1 as

0:13:13.800000 --> 0:13:14.660000
 the native VLAN.

0:13:14.660000 --> 0:13:17.260000
 I'm going to use VLAN
 99 as a native VLAN.

0:13:17.260000 --> 0:13:21.660000
 So whenever I get a frame here from
 VLAN 99, when I put on this trunk,

0:13:21.660000 --> 0:13:23.060000
 I'm going to leave it alone.

0:13:23.060000 --> 0:13:25.000000
 I'm not going to tag it at all.

0:13:25.000000 --> 0:13:29.680000
 Well, if you didn't know that, and you
 still thought that VLAN 1 was the

0:13:29.680000 --> 0:13:33.700000
 native VLAN, once you received that
 plain old Ethernet frame without a

0:13:33.700000 --> 0:13:38.920000
 tag, what broadcast domain do you think
 you would assume it belongs to?

0:13:38.920000 --> 0:13:44.100000
 You would assume it belongs to VLAN
 1 because you didn't know what I was

0:13:44.100000 --> 0:13:46.340000
 thinking. You didn't know
 what I had configured.

0:13:46.340000 --> 0:13:50.580000
 That's why if you change the native
 VLAN on one side of the trunk, you

0:13:50.580000 --> 0:13:53.240000
 have to make sure it matches on
 the other side of the trunk.

0:13:53.240000 --> 0:13:57.300000
 If it doesn't, like in that example,
 where I think VLAN 99 is the native

0:13:57.300000 --> 0:14:00.540000
 VLAN, you think VLAN
 1 is the native VLAN?

0:14:00.540000 --> 0:14:01.700000
 Guess what's going to happen?

0:14:01.700000 --> 0:14:05.500000
 Here comes in a broadcast
 on VLAN 99.

0:14:05.500000 --> 0:14:11.420000
 I put on that trunk, untagged regular
 Ethernet frame, and guess what?

0:14:11.420000 --> 0:14:16.860000
 When it comes to you, you dump that
 broadcast into VLAN 1 because you

0:14:16.860000 --> 0:14:18.480000
 didn't know it came from VLAN 99.

0:14:18.480000 --> 0:14:22.740000
 Here's a broadcast that started in VLAN
 99, and on your side is now being

0:14:22.740000 --> 0:14:24.560000
 dumped into VLAN 1.

0:14:24.560000 --> 0:14:26.980000
 That is a bad situation.

0:14:26.980000 --> 0:14:30.360000
 That's why the native
 VLAN has to match.

0:14:30.360000 --> 0:14:33.060000
 In just a second, one of the reasons
 why I created this whole thing in

0:14:33.060000 --> 0:14:37.400000
 GNS3 is because, like I said in some
 of the earlier videos, GNS3 has wire

0:14:37.400000 --> 0:14:38.960000
 shark built into it.

0:14:38.960000 --> 0:14:42.300000
 So, we'll actually do a packet capture
 of some packets going across a

0:14:42.300000 --> 0:14:46.060000
 trunk so I can show you what
 that tag actually looks like.

0:14:46.060000 --> 0:14:49.680000
 So, 802.1Q, as you can see, just by
 the fact that it was created by the

0:14:49.680000 --> 0:14:52.580000
 IEEE, is a standard VLAN trunking.


0:14:52.580000 --> 0:14:58.080000
 This is not a Cisco proprietary method,
 so any switch should be able to

0:14:58.080000 --> 0:15:01.960000
 support 802.1Q trunking.

0:15:01.960000 --> 0:15:04.860000
 And we've talked about all this.

0:15:04.860000 --> 0:15:08.840000
 If you want to change the native
 VLAN, it is an interface command.

0:15:08.840000 --> 0:15:11.780000
 So, you would go into the interface
 as your trunk, whatever interface

0:15:11.780000 --> 0:15:16.460000
 fast ethernet 0 slash 7 or whatever it
 is, and then you'd say switch port

0:15:16.460000 --> 0:15:22.060000
 trunk native VLAN 99, like in my example,
 and both of us would have to

0:15:22.060000 --> 0:15:25.180000
 have that in these interfaces that
 were connected to each other.

0:15:25.180000 --> 0:15:32.560000
 Okay, so the simplest way to configure
 trunking is to go into the interface

0:15:32.560000 --> 0:15:38.700000
 and then say switch port trunk
 encapsulation dot 1Q.

0:15:38.700000 --> 0:15:43.940000
 Now, you might be wondering, well,
 why do I need that if 802.1Q is the

0:15:43.940000 --> 0:15:48.700000
 way of adding tags, why do
 I have to specify that?

0:15:48.700000 --> 0:15:54.360000
 The reason for that is Cisco a while
 ago, many, many years ago, actually

0:15:54.360000 --> 0:15:59.320000
 came up with this idea of trunking before
 the IEEE did, and they had their

0:15:59.320000 --> 0:16:02.480000
 own proprietary way of doing
 trunking called ISL.

0:16:02.480000 --> 0:16:05.920000
 It stood for inter
 switch link, ISL.

0:16:05.920000 --> 0:16:10.780000
 And then the IEEE came up
 with later on 802.1Q.

0:16:10.780000 --> 0:16:14.880000
 So, there's some Cisco switches out
 there today, still quite a few of

0:16:14.880000 --> 0:16:19.620000
 them, that support either
 ISL or 802.1Q.

0:16:19.620000 --> 0:16:23.220000
 And so, if you're on a switch like that,
 you have to specify this command

0:16:23.220000 --> 0:16:27.780000
 to let it know, I want you to do
 the IEEE way of doing 802.1Q.

0:16:27.780000 --> 0:16:30.780000
 Now, if you're on a switch that does
 not support that command, let's say

0:16:30.780000 --> 0:16:37.920000
 you're on a switch and unrecognized,
 well, then you don't have to worry

0:16:37.920000 --> 0:16:41.780000
 about it. That is a switch
 that's only doing 802.1Q.

0:16:41.780000 --> 0:16:43.260000
 It doesn't even do ISL.

0:16:43.260000 --> 0:16:45.820000
 So, it's not even giving
 you that command.

0:16:45.820000 --> 0:16:48.700000
 But it's just sort of like I've saying,
 you know, there's certain things

0:16:48.700000 --> 0:16:49.540000
 that you should do in networking.

0:16:49.540000 --> 0:16:52.580000
 It's just like a knee jerk reaction,
 like right memory.

0:16:52.580000 --> 0:16:55.940000
 Every single time I make a change to
 my configuration, right memory, save

0:16:55.940000 --> 0:16:59.540000
 it, just getting the habit of doing
 that, going on to an interface.

0:16:59.540000 --> 0:17:03.280000
 And before you leave it, doing no shutdown,
 just doing that by habit,

0:17:03.280000 --> 0:17:05.000000
 you should do this also.

0:17:05.000000 --> 0:17:08.240000
 Whenever you're configuring a trunk,
 just by habit, you should type in

0:17:08.240000 --> 0:17:11.280000
 switchport trunk encapsulation.1Q.


0:17:11.280000 --> 0:17:15.720000
 If it doesn't recognize the command,
 nothing lost, no worries.

0:17:15.720000 --> 0:17:18.180000
 It's just a good habit
 to get into.

0:17:18.180000 --> 0:17:20.300000
 But then we have to
 change the mode.

0:17:20.300000 --> 0:17:23.320000
 Here we type switchport
 mode trunk.

0:17:23.320000 --> 0:17:29.360000
 And now that makes sure that this
 is operating as a VLAN trunk.

0:17:29.360000 --> 0:17:31.160000
 Probably should do no shutdown.

0:17:31.160000 --> 0:17:32.340000
 That's not in the slide here.

0:17:32.340000 --> 0:17:36.500000
 But once again, just as a habit, you
 should type no shutdown before you

0:17:36.500000 --> 0:17:38.040000
 leave the interface.

0:17:38.040000 --> 0:17:43.120000
 And there's a couple of ways
 that we can verify trunking.

0:17:43.120000 --> 0:17:47.680000
 Show VLAN actually doesn't show
 you if an interface is a trunk.

0:17:47.680000 --> 0:17:49.840000
 It just shows you what
 VLANs that you've got.

0:17:49.840000 --> 0:17:52.080000
 We looked at that in
 the previous video.

0:17:52.080000 --> 0:17:56.080000
 The command that I use the most often
 to see, do I have any interfaces

0:17:56.080000 --> 0:18:00.620000
 that are trunking and what interfaces
 are they, is show interface trunk.

0:18:00.620000 --> 0:18:02.020000
 That's the command I use a lot.

0:18:02.020000 --> 0:18:06.080000
 You can also use show interface status
 or show interface switchport.

