WEBVTT

0:00:08.520000 --> 0:00:11.480000
 So, let me go back to GNS3 here.

0:00:11.480000 --> 0:00:14.340000
 So, I've already pre-configured
 all of this stuff.

0:00:14.340000 --> 0:00:17.900000
 Let me go in and a couple
 of things here.

0:00:17.900000 --> 0:00:23.720000
 If you're using GNS3 like I am,
 GNS3 is great for routing stuff.

0:00:23.720000 --> 0:00:26.180000
 Pretty much anything you'd ever need
 to do with routers all the way up

0:00:26.180000 --> 0:00:30.100000
 to pretty much the CCIE level
 you could do in GNS3.

0:00:30.100000 --> 0:00:32.520000
 Switching is kind of weak.

0:00:32.520000 --> 0:00:36.540000
 There's a lot of switching
 features that you can't do.

0:00:36.540000 --> 0:00:40.520000
 Most of what you need to know at the
 CCNA level, you can do with switches

0:00:40.520000 --> 0:00:44.640000
 on GNS3, not everything,
 but most everything.

0:00:44.640000 --> 0:00:49.340000
 But once you get to the CCMP level, that's
 where GNS3 switching is really

0:00:49.340000 --> 0:00:51.460000
 subpar. And it's not their fault.

0:00:51.460000 --> 0:00:57.080000
 It's really the fault of what software
 images are available to put into

0:00:57.080000 --> 0:01:02.900000
 this program. But that being said, I'm
 not going to really show you the

0:01:02.900000 --> 0:01:04.120000
 routers configuration.

0:01:04.120000 --> 0:01:05.160000
 I'll show you that in a second.

0:01:05.160000 --> 0:01:07.260000
 Let me just start with a
 switches configuration.

0:01:07.260000 --> 0:01:10.280000
 Let's go here to Ether Switch 1.

0:01:10.280000 --> 0:01:12.960000
 Let me get rid of some
 of this other stuff.

0:01:12.960000 --> 0:01:17.860000
 These are the hosts.

0:01:17.860000 --> 0:01:24.280000
 Okay, so here in Ether Switch 1, because
 this is what this really is,

0:01:24.280000 --> 0:01:26.260000
 just so you know, because you're going
 to see a different command here

0:01:26.260000 --> 0:01:31.460000
 that you don't normally use,
 Cisco sells some routers.

0:01:31.460000 --> 0:01:35.260000
 And when it comes to routers
 and switches, this is common.

0:01:35.260000 --> 0:01:39.460000
 When you're buying a router switch at
 a very high level, you have a choice.

0:01:39.460000 --> 0:01:43.480000
 You can buy what's called a
 fixed configuration chassis.

0:01:43.480000 --> 0:01:46.680000
 What that means is you're
 buying one box.

0:01:46.680000 --> 0:01:51.020000
 All the interfaces or all the ports
 are on that box and that's what you

0:01:51.020000 --> 0:01:55.900000
 get. So for example, let's say you bought
 a switch that's a fixed configuration

0:01:55.900000 --> 0:01:59.060000
 chassis that has 24 ports.

0:01:59.060000 --> 0:02:03.120000
 Well let's say later on as your network
 grows, all of a sudden you've

0:02:03.120000 --> 0:02:05.980000
 used up all those 24 ports.

0:02:05.980000 --> 0:02:07.340000
 You don't have any options.

0:02:07.340000 --> 0:02:09.080000
 You've got to go buy
 another switch.

0:02:09.080000 --> 0:02:12.360000
 There's nothing you can do to that
 switch to give it more ports.

0:02:12.360000 --> 0:02:14.280000
 You've used up everything.

0:02:14.280000 --> 0:02:19.800000
 Whereas in a modular chassis, whether
 it be a router or a switch, basically

0:02:19.800000 --> 0:02:23.600000
 what you're buying is the box and then
 you get to choose what sort of

0:02:23.600000 --> 0:02:26.720000
 modules you want to plug in there.


0:02:26.720000 --> 0:02:30.760000
 Like maybe on a modular switch you say,
 okay, this switch could technically

0:02:30.760000 --> 0:02:33.340000
 have five modules inside of it.

0:02:33.340000 --> 0:02:36.520000
 Right now I'm only going to spend money
 to buy one module that's a 24

0:02:36.520000 --> 0:02:38.200000
 port switching module.

0:02:38.200000 --> 0:02:42.840000
 And then if I run out of ports, I'll
 order from Cisco another module and

0:02:42.840000 --> 0:02:47.760000
 in that same chassis I'll slide in
 another 24 port switching module.

0:02:47.760000 --> 0:02:51.540000
 Or in the case of a router, you can
 say, well right now all I need are

0:02:51.540000 --> 0:02:55.160000
 LAN modules. But later on I'm going
 to pull out one of those LAN modules

0:02:55.160000 --> 0:02:58.560000
 and I'm going to put a wide area networking
 module in there or a firewall

0:02:58.560000 --> 0:03:00.900000
 module or something like that.

0:03:00.900000 --> 0:03:06.000000
 So modular switches and routers are better
 from the standpoint of scalability.

0:03:06.000000 --> 0:03:09.740000
 You can start small and then purchase
 more things that you can plug in

0:03:09.740000 --> 0:03:11.820000
 there. Sort of like
 your laptop, right?

0:03:11.820000 --> 0:03:14.980000
 When you buy your laptop it's got additional
 ports in it that are probably

0:03:14.980000 --> 0:03:16.460000
 not used for something.

0:03:16.460000 --> 0:03:20.060000
 But later on you can stick a DVD drive
 in there, maybe stick in another

0:03:20.060000 --> 0:03:21.960000
 ethernet card if you wanted to.

0:03:21.960000 --> 0:03:23.720000
 Same thing with modular chassis.

0:03:23.720000 --> 0:03:27.700000
 Of course the downside is the modular
 chassis are typically more expensive

0:03:27.700000 --> 0:03:29.620000
 for that very reason.

0:03:29.620000 --> 0:03:31.780000
 What does that have
 to do with this?

0:03:31.780000 --> 0:03:36.940000
 Well, Cisco sells some routers, they're
 modular routers and some of the

0:03:36.940000 --> 0:03:40.700000
 modules you can put in there if you
 want to are switching modules.

0:03:40.700000 --> 0:03:44.580000
 It's actually a little module you can
 slide in that's got like 16 ports

0:03:44.580000 --> 0:03:49.620000
 or 8 ports and it's like a little self
-contained switch that's inside

0:03:49.620000 --> 0:03:53.200000
 the router. And that's what
 this is right here.

0:03:53.200000 --> 0:03:57.360000
 This ether switch is actually a router
 that's got a switching module inside

0:03:57.360000 --> 0:03:59.680000
 of it. Why is that important?

0:03:59.680000 --> 0:04:03.600000
 Because it doesn't really support all
 the commands that real switches

0:04:03.600000 --> 0:04:06.680000
 do, that just something that
 was built as a switch.

0:04:06.680000 --> 0:04:08.320000
 It doesn't support
 all the commands.

0:04:08.320000 --> 0:04:11.500000
 And some of the commands that you would
 use for like configuring or showing

0:04:11.500000 --> 0:04:15.900000
 things are a little bit different
 than if I was on a real switch.

0:04:15.900000 --> 0:04:18.820000
 So for example, review question.

0:04:18.820000 --> 0:04:24.920000
 What command would I type in a normal
 switch to see what VLANs I've got?

0:04:24.920000 --> 0:04:29.520000
 Well, hopefully you said show VLAN
 and you'd be absolutely right.

0:04:29.520000 --> 0:04:33.340000
 But in this particular switch because
 it's really a router with a switch

0:04:33.340000 --> 0:04:37.620000
 module inside of it, the show
 VLAN command doesn't work.

0:04:37.620000 --> 0:04:41.780000
 That is a valid command on a real switch
 and on the CCNA exam, that's

0:04:41.780000 --> 0:04:44.360000
 what they expect you to know,
 the show VLAN command.

0:04:44.360000 --> 0:04:52.480000
 But on this, it's actually
 show VLAN dash switch.

0:04:52.480000 --> 0:04:55.020000
 It's a little bit different.

0:04:55.020000 --> 0:04:57.660000
 So you can see here, here's
 my default VLAN.

0:04:57.660000 --> 0:05:02.700000
 And according to my diagram, I'm on
 switch one, so fast ethernet one one

0:05:02.700000 --> 0:05:04.380000
 should be in there.

0:05:04.380000 --> 0:05:10.660000
 And it is. And here's VLAN
 two that I configured.

0:05:10.660000 --> 0:05:13.900000
 And fast ethernet one
 two is in that.

0:05:13.900000 --> 0:05:17.280000
 And you can see right
 here, that is correct.

0:05:17.280000 --> 0:05:20.860000
 Now what about one three
 and one fifteen?

0:05:20.860000 --> 0:05:25.980000
 Both of these are configured as VLAN trunks,
 so they are in multiple VLANs.

0:05:25.980000 --> 0:05:29.700000
 So let's just take a look at
 one fifteen as an example.

0:05:29.700000 --> 0:05:34.020000
 If you look through here, one fifteen
 doesn't show up anywhere in this

0:05:34.020000 --> 0:05:36.440000
 output. It's not here.

0:05:36.440000 --> 0:05:41.420000
 Because this only shows you ports that
 are configured as access ports

0:05:41.420000 --> 0:05:44.240000
 that are in one VLAN
 and one VLAN only.

0:05:44.240000 --> 0:05:49.080000
 That's why one slash fifteen and one
 slash three don't show up here.

0:05:49.080000 --> 0:05:51.580000
 Because those interfaces
 are trunks.

0:05:51.580000 --> 0:05:56.960000
 So to verify that, show
 interface trunk.

0:05:56.960000 --> 0:06:01.940000
 And now you can verify, okay one slash
 three, I use the switch port mode

0:06:01.940000 --> 0:06:05.200000
 trunk command which forced the
 interface to become a trunk.

0:06:05.200000 --> 0:06:06.880000
 It didn't have a choice
 in the matter.

0:06:06.880000 --> 0:06:09.380000
 That's why the same mode is on.

0:06:09.380000 --> 0:06:13.140000
 And later I will see that there are
 other ways you can tell a port to

0:06:13.140000 --> 0:06:17.360000
 dynamically become a trunk if certain
 parameters are exchanged between

0:06:17.360000 --> 0:06:19.940000
 switches. But that's
 not what I did here.

0:06:19.940000 --> 0:06:24.240000
 And you can see it's using 802.1q encapsulation
 and the native VLAN is

0:06:24.240000 --> 0:06:28.180000
 one. Let's take a look
 at the configuration.

0:06:28.180000 --> 0:06:33.500000
 How would I look at the configuration
 of a router or a switch?

0:06:33.500000 --> 0:06:36.300000
 What would be the command
 I should type in?

0:06:36.300000 --> 0:06:45.720000
 Show run or the long command
 is show running-config.

0:06:45.720000 --> 0:06:51.420000
 Just keep hitting my space bar
 to get to the next level.

0:06:51.420000 --> 0:06:55.540000
 And here we see here's
 my first trunk.

0:06:55.540000 --> 0:06:59.180000
 All I typed in was switch
 port mode trunk.

0:06:59.180000 --> 0:07:02.920000
 As a matter of fact this Ether switch
 module does support the switch port

0:07:02.920000 --> 0:07:05.900000
 trunk encapsulation.1q command.

0:07:05.900000 --> 0:07:07.500000
 It let me type that in.

0:07:07.500000 --> 0:07:09.060000
 But it defaulted to that.

0:07:09.060000 --> 0:07:12.080000
 It doesn't even support ISL so that's
 why we don't even see it here in

0:07:12.080000 --> 0:07:14.980000
 the output. Switch port mode
 trunk is all I had to do.

0:07:14.980000 --> 0:07:18.700000
 And I had to make sure that
 the interface was up.

0:07:18.700000 --> 0:07:19.840000
 And I did no shut.

0:07:19.840000 --> 0:07:21.280000
 Which was also the default.

0:07:21.280000 --> 0:07:22.580000
 That's why we don't see that here.


0:07:22.580000 --> 0:07:24.540000
 And that's one thing
 about Cisco iOS.

0:07:24.540000 --> 0:07:28.700000
 If you type in a command that's already
 the default behavior most of the

0:07:28.700000 --> 0:07:31.740000
 time, you won't see it
 in the running-config.

0:07:31.740000 --> 0:07:36.420000
 Mostly what you see in the running
-config is non-default commands.

0:07:36.420000 --> 0:07:40.880000
 Not always. Okay.

0:07:40.880000 --> 0:07:43.720000
 And so that's how we
 configure the switch.

0:07:43.720000 --> 0:07:47.200000
 If you are trunking to a router,
 it's a little bit different.

0:07:47.200000 --> 0:07:49.720000
 Now the configuration on the switch
 side is still the same.

0:07:49.720000 --> 0:07:54.200000
 On Fast Ethan at 1.3 it's switch
 port mode trunk on 1.15.

0:07:54.200000 --> 0:07:58.660000
 No different. Let me show you
 a little shortcut here.

0:07:58.660000 --> 0:08:03.760000
 Instead of doing show run, I
 can say show run interface.

0:08:03.760000 --> 0:08:06.120000
 Fast Ethan at 1.15.

0:08:06.120000 --> 0:08:09.620000
 And it only shows me that portion
 of the configuration.

0:08:09.620000 --> 0:08:10.400000
 Just that interface.

0:08:10.400000 --> 0:08:11.860000
 I don't have to scroll
 through everything.

0:08:11.860000 --> 0:08:14.040000
 So that's a nice little shortcut.

0:08:14.040000 --> 0:08:17.600000
 So you can see that's configured
 exactly the same way.

0:08:17.600000 --> 0:08:22.200000
 And the other side of the link, the
 switch on the other side, switch to,

0:08:22.200000 --> 0:08:24.180000
 he's also configured that way.

0:08:24.180000 --> 0:08:26.980000
 Now for router, it's a
 little bit different.

0:08:26.980000 --> 0:08:35.600000
 I'll just show you real quickly
 here the router's configuration.

0:08:35.600000 --> 0:08:40.100000
 So in the router's configuration, I didn't
 really do anything on his main

0:08:40.100000 --> 0:08:44.060000
 interface. Remember how I talked about
 when we were talking about Telnet

0:08:44.060000 --> 0:08:46.580000
 and we were talking
 about VTY lines?

0:08:46.580000 --> 0:08:50.140000
 I said how on routers and switches
 sometimes they create these sort of

0:08:50.140000 --> 0:08:54.960000
 imaginary logical interfaces as
 like placeholders for things.

0:08:54.960000 --> 0:08:58.120000
 We also talked about that when we did
 our switched virtual interface,

0:08:58.120000 --> 0:09:04.100000
 our interface VLAN1 in the last video
 I believe when we said okay, where

0:09:04.100000 --> 0:09:06.240000
 do I put an IP address
 on a switch?

0:09:06.240000 --> 0:09:08.140000
 Oh, interface VLAN1.

0:09:08.140000 --> 0:09:12.400000
 Well, here are a couple of additional
 logical interfaces.

0:09:12.400000 --> 0:09:18.120000
 These are called sub interfaces where
 you have some interface number and

0:09:18.120000 --> 0:09:21.600000
 then a dot and then
 some other number.

0:09:21.600000 --> 0:09:23.080000
 So I made these up from scratch.

0:09:23.080000 --> 0:09:25.020000
 These did not exist before.

0:09:25.020000 --> 0:09:27.920000
 And on a router, this is how you take
 a router because if we look at our

0:09:27.920000 --> 0:09:32.580000
 topology diagram, where is it?

0:09:32.580000 --> 0:09:40.040000
 Right here. Just like this interface
 here, this interface here has to

0:09:40.040000 --> 0:09:43.420000
 carry multiple broadcast domains.

0:09:43.420000 --> 0:09:47.620000
 Well, this link has to carry
 multiple broadcast domains.

0:09:47.620000 --> 0:09:51.700000
 Now the switches, they don't really
 care about layer three.

0:09:51.700000 --> 0:09:53.800000
 All they care about is layer two.

0:09:53.800000 --> 0:09:57.340000
 But the router, he does
 care about layer three.

0:09:57.340000 --> 0:10:01.740000
 He is a host, remember the router's interface
 is a host just like a laptop

0:10:01.740000 --> 0:10:03.620000
 is in a network.

0:10:03.620000 --> 0:10:06.660000
 And he has to have an IP
 address in a network.

0:10:06.660000 --> 0:10:09.920000
 But here we have sort of an interesting
 challenge because we actually

0:10:09.920000 --> 0:10:15.400000
 need this one interface to participate
 in two networks.

0:10:15.400000 --> 0:10:19.340000
 The 111 and the 222.

0:10:19.340000 --> 0:10:23.660000
 And normally an interface can
 only be in one network.

0:10:23.660000 --> 0:10:28.400000
 So how do we assign more than
 one subnet to one interface?

0:10:28.400000 --> 0:10:30.160000
 Well, what we can do is
 we can trick the router.

0:10:30.160000 --> 0:10:34.020000
 We can say, hey router, I want you
 to make believe that you have more

0:10:34.020000 --> 0:10:35.780000
 than one interface here.

0:10:35.780000 --> 0:10:40.600000
 And that is what sub
 interfaces are.

0:10:40.600000 --> 0:10:44.880000
 So by creating this interface out of
 thin air, I've said, okay, on fast

0:10:44.880000 --> 0:10:49.520000
 int, zero slash one, I'm actually going
 to divide you up into two interfaces.

0:10:49.520000 --> 0:10:54.920000
 Zero slash one dot one and
 zero slash one dot two.

0:10:54.920000 --> 0:10:58.760000
 Now the number after the dot
 could have been anything.

0:10:58.760000 --> 0:11:02.580000
 I could have said zero slash one dot
 fifty five and zero slash one dot

0:11:02.580000 --> 0:11:08.840000
 nineteen. It's just the fact that there's
 a dot followed by a number that

0:11:08.840000 --> 0:11:13.000000
 tells the operating system, okay, this
 is a new logical interface that's

0:11:13.000000 --> 0:11:19.140000
 being created and it's associated
 with this physical interface.

0:11:19.140000 --> 0:11:22.940000
 I just chose to use dot one because to
 me it made sense that this interface

0:11:22.940000 --> 0:11:28.260000
 would be used for VLAN one and this
 dot two interface would be used for

0:11:28.260000 --> 0:11:33.860000
 VLAN two. And then once I made my sub
 interfaces, the router didn't know

0:11:33.860000 --> 0:11:36.320000
 what I wanted to do with
 these sub interfaces.

0:11:36.320000 --> 0:11:39.340000
 It knew I was going to put different
 subnets on there, which I did with

0:11:39.340000 --> 0:11:40.960000
 my IP addressing.

0:11:40.960000 --> 0:11:46.040000
 But I had to tell the router, hey,
 this sub interface right here, you

0:11:46.040000 --> 0:11:49.840000
 need to be able to process
 tags, 802 dot one q tags.

0:11:49.840000 --> 0:11:54.320000
 And so when an ethernet frame comes
 in with an 802 dot one q tag and the

0:11:54.320000 --> 0:11:59.320000
 VLAN number inside there says VLAN two,
 the router says, oh, okay, this

0:11:59.320000 --> 0:12:01.860000
 is a sub interface, it's
 going to deal with that.

0:12:01.860000 --> 0:12:06.460000
 And when an ethernet frame comes in
 with no tag, which is on the native

0:12:06.460000 --> 0:12:11.080000
 VLAN, this sub interface is
 going to deal with that.

0:12:11.080000 --> 0:12:14.280000
 So you see this extra work you
 don't have to do on switches.

0:12:14.280000 --> 0:12:17.980000
 Switches automatically know they know
 what VLANs they've got and they

0:12:17.980000 --> 0:12:21.020000
 know whatever VLAN you configured is
 going to be traveling across that

0:12:21.020000 --> 0:12:25.580000
 trunk. But the router, he doesn't
 know what VLANs exist.

0:12:25.580000 --> 0:12:30.200000
 So I actually have to tell him with this
 encapsulation dot one q command.

0:12:30.200000 --> 0:12:35.180000
 So that being the case, let's finish
 up here with taking a look at some

0:12:35.180000 --> 0:12:42.940000
 of these tags. So let's start with,
 let's open up some sessions with my

0:12:42.940000 --> 0:12:56.580000
 PCs. Okay, so PC one, I'm going
 to have him ping PC three.

0:12:56.580000 --> 0:13:00.720000
 Now PC three here show IP.

0:13:00.720000 --> 0:13:05.820000
 So in the context of GNS three, I'm
 using something called the virtual

0:13:05.820000 --> 0:13:08.960000
 PC simulator VPCS.

0:13:08.960000 --> 0:13:11.360000
 And that's actually something
 that's built into GNS three.

0:13:11.360000 --> 0:13:13.640000
 It comes with it by default.

0:13:13.640000 --> 0:13:18.560000
 And like it looks like it's a great little
 tool for a simulated host here.

0:13:18.560000 --> 0:13:20.620000
 It's sort of like a virtual PC.

0:13:20.620000 --> 0:13:26.180000
 So PC three is, let's see
 here, one one one three.

0:13:26.180000 --> 0:13:29.180000
 And from PC one, I should
 be able to ping that.

0:13:29.180000 --> 0:13:32.000000
 Yep, I can ping it.

0:13:32.000000 --> 0:13:37.080000
 Now let's go ahead and
 start a sniffer trace.

0:13:37.080000 --> 0:13:41.360000
 And the way I did this in GNS three
 is I just right clicked on the link

0:13:41.360000 --> 0:13:44.460000
 and then I click start capture.

0:13:44.460000 --> 0:13:53.280000
 And yes, I want to use fast ethernet
 one slash 15 on ether switch one.

0:13:53.280000 --> 0:13:56.120000
 Okay, so wire shark is
 starting up right here.

0:13:56.120000 --> 0:13:57.660000
 Okay, there it goes.

0:13:57.660000 --> 0:14:01.400000
 So while it's doing its thing,
 let's do that ping again.

0:14:01.400000 --> 0:14:04.740000
 All right, so there goes my ping.

0:14:04.740000 --> 0:14:10.460000
 And PC four is two,
 two, two, three.

0:14:10.460000 --> 0:14:12.900000
 So I'll ping that from here.

0:14:12.900000 --> 0:14:17.160000
 That ping was successful.

0:14:17.160000 --> 0:14:21.320000
 Okay, let's stop our
 sniffer trace.

0:14:21.320000 --> 0:14:24.580000
 And in wire, you can see here in wire
 shark, I'm getting a lot of stuff.

0:14:24.580000 --> 0:14:26.100000
 We haven't talked about
 spanning tree.

0:14:26.100000 --> 0:14:30.500000
 Spinning tree is actually a protocol
 you learn at the IC indeed to level.

0:14:30.500000 --> 0:14:33.680000
 So I'm not going to be talking about
 it in this series of videos.

0:14:33.680000 --> 0:14:37.520000
 But in wire shark, if you want to filter
 something out, you say, okay,

0:14:37.520000 --> 0:14:38.540000
 I want to filter out
 of this garbage.

0:14:38.540000 --> 0:14:39.920000
 I don't want to see this.

0:14:39.920000 --> 0:14:42.260000
 Just click on the frame.

0:14:42.260000 --> 0:14:45.360000
 And in this particular case, I'll click
 on where it says spanning tree,

0:14:45.360000 --> 0:14:51.140000
 I right click. And then as I right
 click, I'll do apply as filter.

0:14:51.140000 --> 0:14:52.580000
 And I'll say not.

0:14:52.580000 --> 0:14:55.860000
 In other words, I don't want to
 see stuff that matches this.

0:14:55.860000 --> 0:14:59.360000
 And it filters it out.

0:14:59.360000 --> 0:15:02.120000
 Okay, so before we take
 a look at that in depth.

0:15:02.120000 --> 0:15:08.460000
 So when VLAN one, when PC one pinged
 PC three, that was going across VLAN

0:15:08.460000 --> 0:15:11.340000
 one. And that's the native
 VLAN by default.

0:15:11.340000 --> 0:15:16.840000
 So we should not see any 802
.1Q tags in those pings.

0:15:16.840000 --> 0:15:19.400000
 So here we go, I'll click on it.

0:15:19.400000 --> 0:15:25.220000
 And you can see if I expand the Ethernet
 header, you can see it's a regular

0:15:25.220000 --> 0:15:26.120000
 Ethernet header.

0:15:26.120000 --> 0:15:30.880000
 You've got the destination Mac, source
 Mac, and then the type code.

0:15:30.880000 --> 0:15:35.140000
 And this particular type code is carrying
 the number for IP version four.

0:15:35.140000 --> 0:15:37.680000
 That is the reserve
 number for IPv4.

0:15:37.680000 --> 0:15:40.980000
 That probably is something
 you should memorize.

0:15:40.980000 --> 0:15:47.660000
 That in an Ethernet frame, the ether type
 value of 0x0800 is for IP version

0:15:47.660000 --> 0:15:52.100000
 four. So no mention here of any kind
 of a tag, which is what we would

0:15:52.100000 --> 0:16:00.040000
 expect. Now if I go back, when I ping
 from PC two to PC four, that ping

0:16:00.040000 --> 0:16:02.360000
 came in on VLAN two.

0:16:02.360000 --> 0:16:05.380000
 And so the switch said, okay, in order
 for me to put that across the trunk,

0:16:05.380000 --> 0:16:10.540000
 I have to apply an 802.1Q tag to that,
 indicating that this frame belongs

0:16:10.540000 --> 0:16:14.480000
 to VLAN two. And we will
 see that in here.

0:16:14.480000 --> 0:16:16.860000
 I'll just click on one of those.

0:16:16.860000 --> 0:16:19.700000
 And there you can see it.

0:16:19.700000 --> 0:16:25.760000
 Ethernet two, look, the
 type code is now 0x8100.

0:16:25.760000 --> 0:16:30.300000
 That is the reserve value
 for an 802.1Q tag.

0:16:30.300000 --> 0:16:31.660000
 And here is the tag right here.

0:16:31.660000 --> 0:16:35.340000
 If I open it up, you
 can see the fields.

0:16:35.340000 --> 0:16:36.740000
 There is a priority field.

0:16:36.740000 --> 0:16:40.460000
 If you want to do quality of service,
 not something you really learn about

0:16:40.460000 --> 0:16:42.500000
 at the ICND one level.

0:16:42.500000 --> 0:16:45.860000
 Canonical and format identifier,
 don't worry about that.

0:16:45.860000 --> 0:16:48.100000
 No one's ever going to ask
 you what that field is.

0:16:48.100000 --> 0:16:52.380000
 And then here, you can see
 is our VLAN identifier.

0:16:52.380000 --> 0:16:56.600000
 VLAN two, it contains
 the number two.

0:16:56.600000 --> 0:17:01.660000
 So that concludes this
 section on VLAN trunks.

