WEBVTT

0:00:08.400000 --> 0:00:12.300000
 So let's talk a little bit more about
 broadcast domains and how we can

0:00:12.300000 --> 0:00:15.500000
 manipulate them and control
 them on switches.

0:00:15.500000 --> 0:00:18.740000
 Because after all, this is one of the
 big benefits of switches is it gives

0:00:18.740000 --> 0:00:23.700000
 us the ability to control and configure
 something called virtual LAN.

0:00:23.700000 --> 0:00:27.220000
 So here we're going to talk about what
 are virtual LANs, why do we need

0:00:27.220000 --> 0:00:31.740000
 them, and how we can address them.


0:00:31.740000 --> 0:00:36.760000
 Alright so in this particular picture
 right here we have two physically

0:00:36.760000 --> 0:00:40.300000
 distinct separate local
 area networks.

0:00:40.300000 --> 0:00:45.460000
 We have a local area network for sales
 and a local area network for marketing.

0:00:45.460000 --> 0:00:48.700000
 They're completely separate, they're
 not connected in any way.

0:00:48.700000 --> 0:00:51.960000
 Maybe we did that intentionally because
 we have security reasons.

0:00:51.960000 --> 0:00:54.720000
 You know those people in sales, you know
 sometimes they get a little funny

0:00:54.720000 --> 0:00:57.960000
 and we don't want them sending information
 on those people in marketing

0:00:57.960000 --> 0:01:01.800000
 so we want to keep them completely
 separate and distinct.

0:01:01.800000 --> 0:01:07.640000
 So we look at this and we say okay this
 is great but wouldn't it be better

0:01:07.640000 --> 0:01:13.300000
 if instead of having two separate networking
 devices, two bridges, wouldn't

0:01:13.300000 --> 0:01:17.860000
 it be great if we could just have one
 device, both departments are connected

0:01:17.860000 --> 0:01:22.360000
 to that one device but we're still able
 to keep them separated from each

0:01:22.360000 --> 0:01:27.780000
 other. Because right now sales is
 in their own broadcast domain.

0:01:27.780000 --> 0:01:33.520000
 Because we know that bridges and switches
 when they receive in a frame,

0:01:33.520000 --> 0:01:37.660000
 if the destination address of that frame
 is unknown, the switch does not

0:01:37.660000 --> 0:01:43.000000
 have that in its table like a broadcast,
 like a multicast, or like a unicast

0:01:43.000000 --> 0:01:46.900000
 MAC address that just has never been
 learned, the switch or the bridge

0:01:46.900000 --> 0:01:48.880000
 will flood that frame.

0:01:48.880000 --> 0:01:51.620000
 It will send it out all the other ports
 other than the one where it came

0:01:51.620000 --> 0:01:55.780000
 in. So on the left we have a broadcast
 domain and on the right we have

0:01:55.780000 --> 0:01:56.580000
 a broadcast domain.

0:01:56.580000 --> 0:02:00.440000
 Wouldn't it be nice if we could get
 rid of those two bridges and replace

0:02:00.440000 --> 0:02:05.100000
 them with just a single device that
 still everybody could connect to but

0:02:05.100000 --> 0:02:10.500000
 could maintain our isolation and separation
 of different broadcast domains.

0:02:10.500000 --> 0:02:15.100000
 And that's exactly what
 virtual lands are.

0:02:15.100000 --> 0:02:20.220000
 So now we have a switch and we have
 configured our virtual lands and we

0:02:20.220000 --> 0:02:25.280000
 put the ports into those virtual lands
 and now it separates out our broadcast

0:02:25.280000 --> 0:02:30.920000
 domains. So a virtual land that is the
 purpose of it, it separates broadcast

0:02:30.920000 --> 0:02:34.560000
 domains, it gives you a little
 bit of flexibility and control.

0:02:34.560000 --> 0:02:37.920000
 Now you might be wondering well why would
 I want to separate out my broadcast

0:02:37.920000 --> 0:02:40.820000
 domains? A variety of reasons.

0:02:40.820000 --> 0:02:47.800000
 Number one, every time an actual broadcast,
 an ethernet frame with a destination

0:02:47.800000 --> 0:02:53.320000
 MAC address of FFFFFFF or all ones in
 binary, every time an ethernet frame

0:02:53.320000 --> 0:02:58.640000
 with a destination of a broadcast hits
 your net card, your net card has

0:02:58.640000 --> 0:03:03.520000
 to take that in, send it up to the
 CPU of your laptop and your laptop

0:03:03.520000 --> 0:03:05.120000
 has to inspect it.

0:03:05.120000 --> 0:03:08.940000
 Now if it's just one broadcast,
 not a big deal.

0:03:08.940000 --> 0:03:12.380000
 But as the broadcast domain gets bigger
 and bigger and bigger, if I go

0:03:12.380000 --> 0:03:18.900000
 from having four devices to 14 devices
 to 400 devices all in one broadcast

0:03:18.900000 --> 0:03:21.860000
 domain, you're going to
 see a lot of broadcasts.

0:03:21.860000 --> 0:03:26.660000
 Broadcast are used by a lot of legitimate
 protocols, ARP uses broadcasts,

0:03:26.660000 --> 0:03:28.620000
 DHCP uses broadcast.

0:03:28.620000 --> 0:03:30.700000
 There's a lot of things
 that use broadcasts.

0:03:30.700000 --> 0:03:34.420000
 You would be surprised at how frequently
 your laptop is sending out broadcasts

0:03:34.420000 --> 0:03:38.700000
 without you even touching it, without
 you even touching the keyboard.

0:03:38.700000 --> 0:03:43.440000
 So if you can imagine your CPU is getting
 busier and busier and busier,

0:03:43.440000 --> 0:03:47.560000
 processing all these broadcasts that
 are coming in, that's going to have

0:03:47.560000 --> 0:03:51.660000
 effect on you. Your websites are going
 to seem to load slower, your email

0:03:51.660000 --> 0:03:54.880000
 is going to load slower, anything that
 has to do with networking on your

0:03:54.880000 --> 0:03:58.140000
 laptop is going to start
 grinding to a halt.

0:03:58.140000 --> 0:04:00.980000
 So that's one reason why we might want
 to take a rather large network

0:04:00.980000 --> 0:04:06.040000
 and partition it into different VLANs,
 into different broadcast domains.

0:04:06.040000 --> 0:04:08.820000
 Also for security restrictions.

0:04:08.820000 --> 0:04:12.880000
 So from a layer three perspective,
 an IP perspective, all the devices

0:04:12.880000 --> 0:04:15.860000
 in one broadcast domain
 are in the same subnet.

0:04:15.860000 --> 0:04:18.060000
 They're in the same IP network.

0:04:18.060000 --> 0:04:23.820000
 Well, when it comes to doing security
 like say, okay, I want Joe to be

0:04:23.820000 --> 0:04:28.040000
 able to get to this server over here,
 but I don't want Sally to be able

0:04:28.040000 --> 0:04:29.060000
 to get to the server.

0:04:29.060000 --> 0:04:33.200000
 If everybody's in the same subnet in
 the same broadcast domain, that's

0:04:33.200000 --> 0:04:35.420000
 possible, but it's hard.

0:04:35.420000 --> 0:04:38.440000
 As a matter of fact, at the CCNA level,
 you don't even learn how to do

0:04:38.440000 --> 0:04:41.520000
 that. Once you go to the CCNP level
 and you're starting for your CCNP

0:04:41.520000 --> 0:04:44.920000
 switch exam, then you'll
 learn of ways to do that.

0:04:44.920000 --> 0:04:46.660000
 But it's difficult.

0:04:46.660000 --> 0:04:51.820000
 It's a lot easier if I can separate people
 into different broadcast domains,

0:04:51.820000 --> 0:04:53.560000
 different subnets.

0:04:53.560000 --> 0:04:58.360000
 There's a lot of other ways, a lot of
 easier ways to prevent devices from

0:04:58.360000 --> 0:05:01.000000
 one subnet from talking
 to another subnet.

0:05:01.000000 --> 0:05:04.080000
 But we're all in the same
 subnet on the same VLAN.

0:05:04.080000 --> 0:05:05.540000
 That gets kind of tricky.

0:05:05.540000 --> 0:05:08.660000
 So from a security perspective, you
 might want to break up your network

0:05:08.660000 --> 0:05:11.340000
 into different partitions
 or different VLANs.

0:05:11.340000 --> 0:05:17.160000
 So provides better security, controls
 broadcast like ARP, and provides

0:05:17.160000 --> 0:05:20.160000
 hierarchical subnet usage.

0:05:20.160000 --> 0:05:22.980000
 Not really going to expand
 on that one all that much.

0:05:22.980000 --> 0:05:28.820000
 So as far as VLANs are concerned, then
 this is the way it's been for decades,

0:05:28.820000 --> 0:05:32.820000
 the VLAN range is from 1 to 4,094.


0:05:32.820000 --> 0:05:34.960000
 So that's the VLANs you
 have available to you.

0:05:34.960000 --> 0:05:40.300000
 Now there are some VLANs that are what
 are called normal range VLANs,

0:05:40.300000 --> 0:05:42.340000
 1 through 1,001.

0:05:42.340000 --> 0:05:46.860000
 And usually people just stick with VLANs
 in that number, in that range.

0:05:46.860000 --> 0:05:48.320000
 Now it's completely up to you.

0:05:48.320000 --> 0:05:51.540000
 You say, okay, so I've decided that
 I want payroll, all of the people

0:05:51.540000 --> 0:05:55.740000
 in payroll to be in one IP subnet,
 and I'll put them in a VLAN.

0:05:55.740000 --> 0:05:57.200000
 Which VLAN should it be?

0:05:57.200000 --> 0:06:00.480000
 It's up to you. You could
 select VLAN 2 for them.

0:06:00.480000 --> 0:06:06.240000
 You could select VLAN 359 completely
 up to you, completely up to you.

0:06:06.240000 --> 0:06:10.480000
 It's just the main thing to remember
 is that one IP subnet has to be in

0:06:10.480000 --> 0:06:15.600000
 its own unique VLAN number, and another
 IP subnet has to be in a different

0:06:15.600000 --> 0:06:21.680000
 VLAN number. You can't have two different
 subnets at layer 3 sharing the

0:06:21.680000 --> 0:06:26.300000
 same VLAN. Because if you do that, now
 they're seeing each other's broadcasts.

0:06:26.300000 --> 0:06:29.580000
 And that's exactly what
 we wanted to avoid.

0:06:29.580000 --> 0:06:31.820000
 Also just the reverse is true.

0:06:31.820000 --> 0:06:36.060000
 I can't have a user over here who's in
 one subnet, a user over here who's

0:06:36.060000 --> 0:06:41.200000
 in the exact same subnet, same network,
 but they're in two different VLANs.

0:06:41.200000 --> 0:06:45.240000
 If they're in two different VLANs,
 they're not sharing broadcasts.

0:06:45.240000 --> 0:06:49.060000
 At layer 3, they think they're
 in the same broadcast domain.

0:06:49.060000 --> 0:06:51.300000
 They say, oh, I'm in the
 same subnet as that guy.

0:06:51.300000 --> 0:06:53.180000
 I can ARP for him.

0:06:53.180000 --> 0:06:54.800000
 But ARP is a broadcast.

0:06:54.800000 --> 0:06:58.520000
 When you send out an ARP request for
 something that you think is in your

0:06:58.520000 --> 0:07:02.840000
 network, that's making the assumption
 that that broadcast can get to that

0:07:02.840000 --> 0:07:07.560000
 guy. But if in reality, he's in a different
 VLAN, even if at layer 3,

0:07:07.560000 --> 0:07:09.180000
 he's in the same subnet as you.

0:07:09.180000 --> 0:07:13.220000
 But if he's in a different broadcast domain,
 a different VLAN, your broadcasts

0:07:13.220000 --> 0:07:15.480000
 will not reach him.

0:07:15.480000 --> 0:07:18.840000
 And I'm going to demonstrate
 that here in just a moment.

0:07:18.840000 --> 0:07:22.640000
 So some of the VLANs right there in
 the middle, 1,000, 2 through 1,000,

0:07:22.640000 --> 0:07:26.920000
 5 are reserved. I don't think you're ever
 going to be tested on that they're

0:07:26.920000 --> 0:07:29.400000
 reserved for token
 ring, necessarily.

0:07:29.400000 --> 0:07:32.200000
 But you should remember that those ones
 there in the middle are reserved.

0:07:32.200000 --> 0:07:33.160000
 You cannot use them.

0:07:33.160000 --> 0:07:34.200000
 They're unusable.

0:07:34.200000 --> 0:07:38.980000
 So you should probably remember that 1
,000, 2 through 1,000, 5 are unusable.

0:07:38.980000 --> 0:07:44.100000
 And then the higher numbers, 1,000,
 6 through 4,094, are extended range

0:07:44.100000 --> 0:07:49.120000
 VLANs. Once again, once you get to
 the CCNP switch exam, we learn more

0:07:49.120000 --> 0:07:53.160000
 about those. And there's some caveats
 and gotchs as far as if you want

0:07:53.160000 --> 0:07:57.400000
 to use those. There's certain other
 things you have to do first.

0:07:57.400000 --> 0:08:00.900000
 At the CCNA level, though, we
 don't really get into that.

0:08:00.900000 --> 0:08:04.000000
 Okay, so how do I
 configure a VLAN?

0:08:04.000000 --> 0:08:09.900000
 So remember that initially when you
 turn on a switch, review question,

0:08:09.900000 --> 0:08:16.460000
 when you turn on a switch, are the ports
 on the switch by default administratively

0:08:16.460000 --> 0:08:20.740000
 down or administratively enabled?

0:08:20.740000 --> 0:08:25.100000
 They are administratively enabled.


0:08:25.100000 --> 0:08:29.080000
 Routers, their interfaces are administratively
 shut down by default.

0:08:29.080000 --> 0:08:33.160000
 But by default, switch ports are up
 as soon as you plug something in.

0:08:33.160000 --> 0:08:37.500000
 Now, when you get a switch, whether
 it's got 8 ports or whether it's got

0:08:37.500000 --> 0:08:43.380000
 200 ports, the default behavior is that
 all those interfaces are in VLAN

0:08:43.380000 --> 0:08:45.640000
 1, the default VLAN.

0:08:45.640000 --> 0:08:47.840000
 You should remember that
 VLAN 1 is already there.

0:08:47.840000 --> 0:08:49.140000
 You don't have to configure it.

0:08:49.140000 --> 0:08:53.060000
 It is the default VLAN and all
 the interfaces are in it.

0:08:53.060000 --> 0:08:56.600000
 Now, if you say, oh, okay, well, that's
 cool because that one switch is

0:08:56.600000 --> 0:08:58.060000
 going to be connected to payroll.

0:08:58.060000 --> 0:09:01.420000
 Nobody but payroll is going to
 be connected to that switch.

0:09:01.420000 --> 0:09:03.860000
 And everybody in payroll is going
 to be in the same subnet.

0:09:03.860000 --> 0:09:06.320000
 So they're going to be in
 the same broadcast domain.

0:09:06.320000 --> 0:09:07.200000
 No problem then.

0:09:07.200000 --> 0:09:08.800000
 You don't have to
 create any VLANs.

0:09:08.800000 --> 0:09:10.380000
 You don't have to
 change any VLANs.

0:09:10.380000 --> 0:09:15.040000
 But if you do want to go on a switch and
 you want to create some new VLANs,

0:09:15.040000 --> 0:09:17.020000
 it's a two-step process.

0:09:17.020000 --> 0:09:24.640000
 Step number one is just creating it
 and naming it like VLAN 2, VLAN 9,

0:09:24.640000 --> 0:09:29.300000
 just basically telling the switch,
 I'm creating a new VLAN on you.

0:09:29.300000 --> 0:09:34.320000
 VLAN 200, VLAN 300, that's
 literally the command.

0:09:34.320000 --> 0:09:36.040000
 VLAN and the VLAN ID.

0:09:36.040000 --> 0:09:37.880000
 Don't even worry about
 the legacy way.

0:09:37.880000 --> 0:09:39.300000
 Nobody does that.

0:09:39.300000 --> 0:09:40.940000
 This is the way you're
 going to do it.

0:09:40.940000 --> 0:09:42.160000
 That's the way you're
 going to do it.

0:09:42.160000 --> 0:09:46.560000
 Config T, go into global config mode,
 and then just type VLAN and the

0:09:46.560000 --> 0:09:50.420000
 number, like VLAN 5, VLAN 7.

0:09:50.420000 --> 0:09:54.920000
 Optionally, if you want to, this is
 optional, you can provide it a name.

0:09:54.920000 --> 0:09:57.780000
 And this kind of helps if you're looking
 at the running config and it

0:09:57.780000 --> 0:10:00.940000
 says VLAN 2 and then underneath
 it it says engineering VLAN.

0:10:00.940000 --> 0:10:03.240000
 And then VLAN 3, marketing VLAN.

0:10:03.240000 --> 0:10:06.880000
 Now you know, oh okay, I know
 why these VLANs were created.

0:10:06.880000 --> 0:10:09.780000
 Don't have to give it a name, but it's
 just kind of nice, a descriptive

0:10:09.780000 --> 0:10:13.940000
 characteristic. Now, that's
 step number one.

0:10:13.940000 --> 0:10:19.540000
 Just because I created VLAN 5,
 the switch can't read my mind.

0:10:19.540000 --> 0:10:20.880000
 It doesn't have telepathy.

0:10:20.880000 --> 0:10:26.040000
 It doesn't know which interfaces I want
 to put into that broadcast domain.

0:10:26.040000 --> 0:10:27.420000
 So that's the second step.

0:10:27.420000 --> 0:10:30.000000
 Now we have to go into
 the interfaces, right?

0:10:30.000000 --> 0:10:36.600000
 Interface, Fast Ethernet, whatever, and
 apply that VLAN to the interface.

0:10:36.600000 --> 0:10:38.840000
 And here's how we do that.

0:10:38.840000 --> 0:10:41.260000
 We type switch port mode access.

0:10:41.260000 --> 0:10:42.800000
 We saw that in the
 last slide, right?

0:10:42.800000 --> 0:10:46.940000
 In the last video, that's saying this
 interface is in one broadcast domain

0:10:46.940000 --> 0:10:52.040000
 only. Now if all I did was type that,
 it would still be in VLAN 1.

0:10:52.040000 --> 0:10:53.860000
 I really wouldn't have done much.

0:10:53.860000 --> 0:10:58.620000
 But then I type switch port
 access VLAN whatever.

0:10:58.620000 --> 0:11:02.340000
 Switch port access VLAN 2 if I want
 it to be in that broadcast domain.

0:11:02.340000 --> 0:11:06.540000
 Switch port access VLAN 99 if I want
 to be in that broadcast domain.

0:11:06.540000 --> 0:11:11.160000
 So critical thing I want you
 to take away from this.

0:11:11.160000 --> 0:11:19.420000
 On switch ports, the mode dictates
 what the interface is doing.

0:11:19.420000 --> 0:11:24.380000
 The main mode we've really focused
 on so far is just access mode.

0:11:24.380000 --> 0:11:27.280000
 There are other modes as well.

0:11:27.280000 --> 0:11:29.900000
 When we talk about trunking in the next
 section, we're going to get into

0:11:29.900000 --> 0:11:35.100000
 that. So, but why I'm saying that is
 because if you look at the running

0:11:35.100000 --> 0:11:39.740000
 config of a switch and you see on a
 particular interface, it says switch

0:11:39.740000 --> 0:11:42.760000
 port access VLAN 20.

0:11:42.760000 --> 0:11:48.500000
 You can't automatically assume that
 that interface is just in VLAN 20

0:11:48.500000 --> 0:11:51.520000
 and it's providing access
 to some device.

0:11:51.520000 --> 0:11:55.300000
 You can't assume that just from
 this command right here.

0:11:55.300000 --> 0:12:00.560000
 This command does not tell you how this
 interface is operating right now.

0:12:00.560000 --> 0:12:06.540000
 All that all that command says is if
 this interface ever becomes an access

0:12:06.540000 --> 0:12:12.040000
 port, if it's ever in that mode, then
 while it's an access port, it's

0:12:12.040000 --> 0:12:14.420000
 going to be in this
 VLAN right here.

0:12:14.420000 --> 0:12:18.140000
 But we don't know from this
 command what the mode is.

0:12:18.140000 --> 0:12:21.760000
 That's where this command
 is critical.

0:12:21.760000 --> 0:12:25.520000
 So, if this interface was in some other
 kind of mode, you might think,

0:12:25.520000 --> 0:12:29.060000
 oh, okay, well, if I put in some other
 mode, this right here will just

0:12:29.060000 --> 0:12:31.480000
 vanish from the configuration,
 right?

0:12:31.480000 --> 0:12:36.060000
 Nope. This could be in another mode
 and you would still see this in your

0:12:36.060000 --> 0:12:41.460000
 running config. So, the point I'm trying
 to make to you is step number

0:12:41.460000 --> 0:12:46.020000
 one when doing any kind of troubleshooting
 is identify what mode is my

0:12:46.020000 --> 0:12:49.220000
 interface in. Because then you can
 look at the running config and you

0:12:49.220000 --> 0:12:52.980000
 can say, oh, okay, well, these commands
 I can ignore because they don't

0:12:52.980000 --> 0:12:57.540000
 apply to the particular mode that
 I'm operating in right now.

0:12:57.540000 --> 0:13:02.240000
 And some verification commands show
 VLAN is probably the command you're

0:13:02.240000 --> 0:13:03.780000
 going to use the most often.

0:13:03.780000 --> 0:13:07.420000
 Shows you the VLANs that you've got
 and what interfaces are applied to

0:13:07.420000 --> 0:13:16.560000
 those VLANs. And then the keyword
 of switch port at the end.

0:13:16.560000 --> 0:13:18.960000
 Let's do some demonstrations
 of this.

0:13:18.960000 --> 0:13:23.060000
 So, for this demonstration, I've created
 this topology here, which I'm

0:13:23.060000 --> 0:13:23.840000
 going to be using.

0:13:23.840000 --> 0:13:29.720000
 So, I've got switch two and in my particular
 lab, which is a real, I'm

0:13:29.720000 --> 0:13:31.020000
 using I-neas rack.

0:13:31.020000 --> 0:13:32.480000
 So, I-neas rack rentals.

0:13:32.480000 --> 0:13:37.180000
 So, if you ever buy some tokens and
 you do some rack rental time on our

0:13:37.180000 --> 0:13:41.060000
 CCNA, CCNP racks, that's exactly what
 I'm going to be using here in this

0:13:41.060000 --> 0:13:44.360000
 demonstration and most of our
 demonstrations coming up.

0:13:44.360000 --> 0:13:47.440000
 So, I've got to switch, but in our racks,
 we don't actually have any real

0:13:47.440000 --> 0:13:51.120000
 hosts. There's no laptops
 or PCs in the racks.

0:13:51.120000 --> 0:13:53.720000
 So, I'm actually using routers.

0:13:53.720000 --> 0:13:56.940000
 This is actually router one,
 router two and router three.

0:13:56.940000 --> 0:14:00.020000
 But I'm going to pretend
 that they're hosts.

0:14:00.020000 --> 0:14:03.240000
 I've just given them IP addresses and
 we're just going to be using them

0:14:03.240000 --> 0:14:04.780000
 to initiate pings.

0:14:04.780000 --> 0:14:06.600000
 So, they're not going to be doing
 any fancy routing stuff.

0:14:06.600000 --> 0:14:10.520000
 Let's just pretend that they're hosts
 and I changed their names, their

0:14:10.520000 --> 0:14:16.000000
 host name to host one, host two, host three,
 just for demonstration purposes.

0:14:16.000000 --> 0:14:21.520000
 Okay. So, let's go on to
 switch two to begin with.

0:14:21.520000 --> 0:14:24.800000
 And what I recommend that you might want
 to do is right now, if you haven't

0:14:24.800000 --> 0:14:28.120000
 already done this, take a
 screenshot of this image.

0:14:28.120000 --> 0:14:32.400000
 That way, when I log into the devices,
 you can be looking at the screenshot

0:14:32.400000 --> 0:14:36.780000
 while I'm showing you the command line
 and you won't get confused as to

0:14:36.780000 --> 0:14:40.820000
 which device I'm in and port numbers
 and all that kind of stuff.

0:14:40.820000 --> 0:14:43.700000
 Okay. So, hopefully you've had enough
 time or you've paused the video

0:14:43.700000 --> 0:14:46.060000
 and you've taken that screenshot.

0:14:46.060000 --> 0:14:48.840000
 So, let's go over here.

0:14:48.840000 --> 0:14:53.860000
 So, first of all, I'm going to go
 ahead and I am in switch two.

0:14:53.860000 --> 0:14:56.920000
 Remember, user exec mode can't
 really do anything from here.

0:14:56.920000 --> 0:14:58.540000
 So, I want to type enable.

0:14:58.540000 --> 0:15:03.220000
 So, the first thing I want to see
 is what VLANs are in this switch.

0:15:03.220000 --> 0:15:06.760000
 Honestly, I don't know if this switch
 has just the default VLANs.

0:15:06.760000 --> 0:15:09.720000
 There might be some other VLANs in
 here from some previous labs that I

0:15:09.720000 --> 0:15:12.580000
 did. So, I'm just going
 to type show VLAN.

0:15:12.580000 --> 0:15:16.400000
 Okay. It just has
 the default VLAN.

0:15:16.400000 --> 0:15:22.820000
 So, we see here, VLAN one, there
 has been no name configured.

0:15:22.820000 --> 0:15:27.140000
 So, the name is just default
 and it's active.

0:15:27.140000 --> 0:15:32.240000
 And you can see these are all the
 ports that are in that VLAN.

0:15:32.240000 --> 0:15:37.280000
 Now, if a port, if you know there's
 a port on the switch but it does not

0:15:37.280000 --> 0:15:42.000000
 show up here, but you know that port is
 actually up and connected to something,

0:15:42.000000 --> 0:15:47.080000
 if it's not anywhere in this output,
 that means that port is not an access

0:15:47.080000 --> 0:15:52.780000
 port. Only ports that are in the switch
 port mode access will show up

0:15:52.780000 --> 0:15:56.920000
 here as access ports in the various
 VLANs that you've got.

0:15:56.920000 --> 0:16:00.820000
 If it's not here, then that means it's
 in some other mode, probably what

0:16:00.820000 --> 0:16:04.940000
 we call trunking mode that we'll
 talk about in another video.

0:16:04.940000 --> 0:16:06.220000
 So, right now we have this.

0:16:06.220000 --> 0:16:09.760000
 And so, if we look at that, that means
 all three of these interfaces are

0:16:09.760000 --> 0:16:10.980000
 in the same VLAN.

0:16:10.980000 --> 0:16:16.040000
 Let me go ahead and bring them up.


0:16:16.040000 --> 0:16:20.400000
 By the way, this command I'm doing right
 here, this is a useful command

0:16:20.400000 --> 0:16:22.760000
 on switch's interface range.

0:16:22.760000 --> 0:16:27.640000
 This way you can group a bunch of interfaces
 together and now the configuration

0:16:27.640000 --> 0:16:31.240000
 command I apply is going to apply across
 all of them at the same time.

0:16:31.240000 --> 0:16:34.660000
 So, I don't have to get into each
 interface one at a time at a time.

0:16:34.660000 --> 0:16:36.920000
 So, I'll just do no shutdown.

0:16:36.920000 --> 0:16:42.580000
 I disabled them purposely before
 this lab just to demonstrate.

0:16:42.580000 --> 0:16:50.560000
 Okay, so I'm going to go into host
 one and we can see that host one in

0:16:50.560000 --> 0:16:54.220000
 his ARP table, all he knows
 about is himself.

0:16:54.220000 --> 0:16:59.120000
 Now, because they are all three in the
 same subnet, you can see they're

0:16:59.120000 --> 0:17:04.640000
 all three in the one to three network
 and I'll put a circle here.

0:17:04.640000 --> 0:17:11.500000
 They're all three in the same
 VLAN, which is VLAN 1.

0:17:11.500000 --> 0:17:16.000000
 They should be able to
 exchange broadcasts.

0:17:16.000000 --> 0:17:21.260000
 So, if on PC1 I ping PC2, first thing
 he's going to do is he's going to

0:17:21.260000 --> 0:17:22.860000
 send out an ARP request.

0:17:22.860000 --> 0:17:25.000000
 So, my first ping will
 probably fail.

0:17:25.000000 --> 0:17:27.280000
 That ARP request will
 be a broadcast.

0:17:27.280000 --> 0:17:32.880000
 So, when it's broadcast
 PC2 and PC3 will see it.

0:17:32.880000 --> 0:17:36.760000
 And then PC2 will respond back to that
 with an ARP reply and then the

0:17:36.760000 --> 0:17:38.260000
 ping should go through.

0:17:38.260000 --> 0:17:42.700000
 So, if PC1 can actually ping PC2, that
 will prove the broadcast works.

0:17:42.700000 --> 0:17:45.500000
 And actually, because this is a router,
 I have the ability to turn on

0:17:45.500000 --> 0:17:49.880000
 a debug to actually watch the ARP
 go out and I'm going to do that.

0:17:49.880000 --> 0:18:00.600000
 So, debug ARP. So, here
 we go, ping 1.2.3.2.

0:18:00.600000 --> 0:18:05.000000
 All right, on debug all
 turns off the debug.

0:18:05.000000 --> 0:18:12.980000
 So, we can see here, as soon as I did
 the ping, we see IP ARP sent request.

0:18:12.980000 --> 0:18:14.620000
 So, he sent an ARP request.

0:18:14.620000 --> 0:18:20.280000
 He says, this is me, this is my Mac,
 and I'm looking for 1, 2, 3, 2.

0:18:20.280000 --> 0:18:22.940000
 I don't know his Mac.

0:18:22.940000 --> 0:18:26.800000
 And because they are in the same broadcast
 domain, we received an ARP

0:18:26.800000 --> 0:18:30.900000
 response, received reply.

0:18:30.900000 --> 0:18:32.980000
 And now we can see here
 at the Mac address.

0:18:32.980000 --> 0:18:35.640000
 And then the pings were
 successful after that.

0:18:35.640000 --> 0:18:38.860000
 Now, I'm also going to
 do the same thing.

0:18:38.860000 --> 0:18:42.740000
 I'm going to ping 1, 2, 3, 3.

0:18:42.740000 --> 0:18:44.100000
 He's arping for him right now.

0:18:44.100000 --> 0:18:45.700000
 I turned off the debug.

0:18:45.700000 --> 0:18:49.220000
 And now when I do show ARP, we can see
 he's learned about everything in

0:18:49.220000 --> 0:18:53.700000
 his ARP table. So, all three of these
 guys know about each other.

0:18:53.700000 --> 0:18:56.700000
 Now, look what happens
 if I do this.

0:18:56.700000 --> 0:19:05.680000
 I'm going to leave these two ports in
 VLAN 1, but I'm going to take this

0:19:05.680000 --> 0:19:12.280000
 port right here, and I'm going to
 create a new VLAN called VLAN 2.

0:19:12.280000 --> 0:19:16.640000
 And I'm going to put this
 interface in that port.

0:19:16.640000 --> 0:19:17.700000
 So, that's step number one.

0:19:17.700000 --> 0:19:24.840000
 Let's do that. So, the first
 step is to create the VLAN.

0:19:24.840000 --> 0:19:27.960000
 So, I have to go into global configuration
 mode to do that.

0:19:27.960000 --> 0:19:30.720000
 And I just type VLAN 2.

0:19:30.720000 --> 0:19:33.040000
 And I could give it
 a name if I want.

0:19:33.040000 --> 0:19:36.620000
 Name, let's just say, engineering.


0:19:36.620000 --> 0:19:41.460000
 Okay. And now, I haven't done, I haven't
 applied the VLAN to an interface

0:19:41.460000 --> 0:19:54.880000
 yet. So, now when I do this, I need
 to go to interface fast, and it's

0:19:54.880000 --> 0:19:59.760000
 at zero slash three, and apply
 VLAN 2 to that interface.

0:19:59.760000 --> 0:20:04.220000
 And that is the switch port.

0:20:04.220000 --> 0:20:06.820000
 We want to do switch
 port mode access.

0:20:06.820000 --> 0:20:12.680000
 And then switch port
 access VLAN 2.

0:20:12.680000 --> 0:20:16.720000
 That's the command that moves it from
 VLAN 1, which is what it was in

0:20:16.720000 --> 0:20:19.700000
 now into VLAN 2.

0:20:19.700000 --> 0:20:25.140000
 And now if I do the show VLAN command,
 now we see that interface is in

0:20:25.140000 --> 0:20:32.860000
 VLAN 2. Okay. Now, here's
 an interesting question.

0:20:32.860000 --> 0:20:40.760000
 If we go over to host 1, show ARP.


0:20:40.760000 --> 0:20:48.200000
 Okay. He thinks that 1, 2, 3, 3
 is this MAC address right here.

0:20:48.200000 --> 0:20:49.080000
 I can't memorize.

0:20:49.080000 --> 0:20:49.660000
 Oh, let's see here.

0:20:49.660000 --> 0:20:50.500000
 Well, here's what I could.

0:20:50.500000 --> 0:20:51.680000
 No, I can't memorize that.

0:20:51.680000 --> 0:20:54.240000
 So I'm just going to remember
 the last four characters.

0:20:54.240000 --> 0:21:04.680000
 6DD8. 6DD8. So this is 6D8.

0:21:04.680000 --> 0:21:20.960000
 That's him. And router 1 says in his
 ARP table, 1.2.3.3 equals MAC 6DD8.

0:21:20.960000 --> 0:21:25.580000
 Make this a little
 bit bigger here.

0:21:25.580000 --> 0:21:33.920000
 Okay. But this MAC address, back when
 router 1, 1, 1 host 1, ARPed, the

0:21:33.920000 --> 0:21:37.180000
 ARP was successful back when
 PC3 was in the same VLAN.

0:21:37.180000 --> 0:21:38.780000
 When he was in VLAN 1.

0:21:38.780000 --> 0:21:43.560000
 And 6D8 was originally
 learned in VLAN 1.

0:21:43.560000 --> 0:21:46.000000
 Is it still in VLAN 1?

0:21:46.000000 --> 0:21:48.940000
 Well, let's take a look at
 the MAC address table.

0:21:48.940000 --> 0:21:54.040000
 Show MAC address-table.

0:21:54.040000 --> 0:21:57.360000
 And we're looking for an
 address ending with 6D8.

0:21:57.360000 --> 0:22:04.220000
 Look at this. 6D8
 is now in VLAN 2.

0:22:04.220000 --> 0:22:13.040000
 In VLAN 2. So what's going
 to happen if PC1 pings?

0:22:13.040000 --> 0:22:14.780000
 Because he already has
 an ARP entry, right?

0:22:14.780000 --> 0:22:16.660000
 He already thinks, hey, I
 don't have to ARP anymore.

0:22:16.660000 --> 0:22:18.320000
 I know the guy's MAC address.

0:22:18.320000 --> 0:22:20.440000
 Let's think about what's
 going to happen here.

0:22:20.440000 --> 0:22:23.820000
 So it's going to come in this way.


0:22:23.820000 --> 0:22:28.360000
 And I'm going to draw it over
 here because I have more room.

0:22:28.360000 --> 0:22:33.360000
 So the IP source will
 be 10.0, not 10.

0:22:33.360000 --> 0:22:39.960000
 1.2.3.1. The IP destination
 will be 1.2.3.3.

0:22:39.960000 --> 0:22:45.860000
 The MAC source will
 be whatever PC1 is.

0:22:45.860000 --> 0:22:53.240000
 And the MAC destination
 is going to be xxxx6D8.

0:22:53.240000 --> 0:22:58.280000
 Now, when that comes into this port,
 what's that switch going to do?

0:22:58.280000 --> 0:23:01.240000
 You might think, oh,
 well, no problem.

0:23:01.240000 --> 0:23:03.300000
 I mean, he's going to look at
 his MAC address table, right?

0:23:03.300000 --> 0:23:05.680000
 And he's going to find 6D8.

0:23:05.680000 --> 0:23:08.860000
 And he's going to find this
 associate to port 0 slash 3.

0:23:08.860000 --> 0:23:10.660000
 I mean, after all, that's what
 we see right here, right?

0:23:10.660000 --> 0:23:13.160000
 There it is. Here's the problem.

0:23:13.160000 --> 0:23:17.100000
 Look at this. The MAC address table
 does not just store the MAC address

0:23:17.100000 --> 0:23:30.080000
 and the port. It also stores
 what VLAN it belongs to.

0:23:30.080000 --> 0:23:34.840000
 The switch is going to say, oh, it
 came in on a port that's in VLAN 1.

0:23:34.840000 --> 0:23:40.560000
 In my MAC address table, I
 need to find 6D8 in VLAN 1.

0:23:40.560000 --> 0:23:43.980000
 And he's not going to find it
 because it's not in VLAN 1.

0:23:43.980000 --> 0:23:47.000000
 It's in VLAN 2. And so guess what?


0:23:47.000000 --> 0:23:48.520000
 Our ping is going to fail.

0:23:48.520000 --> 0:23:50.820000
 The switch is not going to say, oh,
 OK, well, I'm just going to allow

0:23:50.820000 --> 0:23:54.900000
 this frame to jump from one broadcast
 domain to another broadcast domain.

0:23:54.900000 --> 0:23:56.260000
 The switch is not
 going to do that.

0:23:56.260000 --> 0:23:59.320000
 Remember, this is a virtual LAN.

0:23:59.320000 --> 0:24:04.220000
 In a real LAN, in a real LAN, when you
 put an ethernet frame on the wire,

0:24:04.220000 --> 0:24:09.180000
 the destination MAC address of that frame
 has to be somebody on your wire.

0:24:09.180000 --> 0:24:11.060000
 That is the rules of ethernet.

0:24:11.060000 --> 0:24:13.400000
 When you put an ethernet frame on the
 wire, it's destined for somebody

0:24:13.400000 --> 0:24:17.620000
 on your wire. Now, if you're trying
 to get your packet, if you're trying

0:24:17.620000 --> 0:24:21.060000
 to get your data to somebody on another
 wire, the destination MAC address

0:24:21.060000 --> 0:24:24.340000
 has to be a router that's
 on your wire.

0:24:24.340000 --> 0:24:27.860000
 So you can get that frame to the router
 who's on your wire, and then he

0:24:27.860000 --> 0:24:30.060000
 can route it to another subnet.

0:24:30.060000 --> 0:24:33.420000
 But this is not going to work here,
 because this would be breaking the

0:24:33.420000 --> 0:24:34.180000
 rules of ethernet.

0:24:34.180000 --> 0:24:38.100000
 If this ping actually worked, that
 would mean that PC1 was putting an

0:24:38.100000 --> 0:24:42.100000
 ethernet frame on his wire with a destination
 MAC address of something

0:24:42.100000 --> 0:24:47.320000
 that was not on his wire, and just somehow
 magically hopped from one wire

0:24:47.320000 --> 0:24:50.700000
 to the other, from one
 LAN to the other.

0:24:50.700000 --> 0:24:55.120000
 But the whole reason we create virtual
 LANs is to separate them.

0:24:55.120000 --> 0:24:59.880000
 So PC1 should not be
 able to ping PC3.

0:24:59.880000 --> 0:25:03.300000
 Now, this is all in theory here, because
 they're on two separate broadcast

0:25:03.300000 --> 0:25:05.660000
 domains, even though he
 has the MAC address.

0:25:05.660000 --> 0:25:10.460000
 Let's see what happens.

0:25:10.460000 --> 0:25:16.800000
 Show ARP. Okay, ping 1.2.3.3.

0:25:16.800000 --> 0:25:18.280000
 Ah, there we go.

0:25:18.280000 --> 0:25:20.520000
 See, I'm just getting dots.

0:25:20.520000 --> 0:25:26.560000
 So the ping is not working, even
 though he has a MAC entry.

0:25:26.560000 --> 0:25:30.480000
 It's not working because they're
 on different broadcast domains.

0:25:30.480000 --> 0:25:33.160000
 Now watch this, I'm going to
 clear out his ARP table.

0:25:33.160000 --> 0:25:44.620000
 Clear ARP. So now when I do
 show ARP, let's say 1.2.3.3.

0:25:44.620000 --> 0:25:51.340000
 Okay, so 1.2.3.3 is gone.

0:25:51.340000 --> 0:25:55.960000
 Debug ARP. Now let's ping 1.2.3.3.


0:25:55.960000 --> 0:26:01.700000
 Sending a request, sending a
 request, sending a request.

0:26:01.700000 --> 0:26:05.780000
 He's not getting any responses,
 because these are broadcasts.

0:26:05.780000 --> 0:26:09.940000
 So he sent all these requests, but
 he didn't get any ARP reply.

0:26:09.940000 --> 0:26:13.440000
 Even though this guy is in the same
 subnet as him, he was in a different

0:26:13.440000 --> 0:26:19.340000
 virtual LAN. And broadcasts from this
 virtual LAN, ARP requests, were

0:26:19.340000 --> 0:26:21.620000
 not allowed to go into
 this virtual LAN.

0:26:21.620000 --> 0:26:28.040000
 Even when PC1 knew what the MAC address
 of PC3 was, it still couldn't

0:26:28.040000 --> 0:26:34.820000
 get over here, because the rules of ethernet
 say, when you put an ethernet

0:26:34.820000 --> 0:26:40.000000
 in your broadcast domain, in your LAN,
 in this case, they're not in the

0:26:40.000000 --> 0:26:43.940000
 same LAN, they're in separate
 virtual LANs.

0:26:43.940000 --> 0:26:46.600000
 One other thing I want to show you
 is the output of that other command

0:26:46.600000 --> 0:26:51.460000
 that we saw. So we already looked at
 show VLAN, and you're going to use

0:26:51.460000 --> 0:26:54.360000
 that command a lot in your
 networking career.

0:26:54.360000 --> 0:26:59.880000
 You can also do show interface, fast
 ethernet, and then whatever it is,

0:26:59.880000 --> 0:27:10.620000
 and the number one, it shows you what
 is my operational mode, static access.

0:27:10.620000 --> 0:27:15.640000
 So administrative mode means,
 what am I configured to do?

0:27:15.640000 --> 0:27:19.600000
 Operational mode means, what
 am I actually doing?

0:27:19.600000 --> 0:27:23.040000
 Sometimes what you're configured to
 do doesn't work, because it relies

0:27:23.040000 --> 0:27:26.780000
 on things that aren't turned on
 or aren't working properly.

0:27:26.780000 --> 0:27:29.620000
 And so your operational mode will be
 different, but right now we're the

0:27:29.620000 --> 0:27:36.200000
 same. But look down here, access
 mode VLAN, VLAN 2 engineering.

0:27:36.200000 --> 0:27:41.680000
 So that says, if this is operationally
 an access port, which it is, if

0:27:41.680000 --> 0:27:46.060000
 that's true, then this
 will be in VLAN 2.

0:27:46.060000 --> 0:27:50.120000
 And that concludes this
 video on virtual LANs.

