WEBVTT

0:00:08.200000 --> 0:00:12.220000
 In this video, I'd like to
 talk about voice VLANs.

0:00:12.220000 --> 0:00:16.000000
 So up until now, as you're watching
 this video, hopefully you've already

0:00:16.000000 --> 0:00:19.720000
 learned about the concept of just regular
 VLANs and you've learned about

0:00:19.720000 --> 0:00:23.340000
 the concept of what's called
 an access port on a switch.

0:00:23.340000 --> 0:00:28.500000
 So on a Cisco switch, when you type switch
 port mode access on an interface,

0:00:28.500000 --> 0:00:32.680000
 normally that tells the interface
 you are in one broadcast domain.

0:00:32.680000 --> 0:00:34.380000
 It doesn't know what
 broadcast domain.

0:00:34.380000 --> 0:00:36.780000
 It will assume VLAN
 one by default.

0:00:36.780000 --> 0:00:39.700000
 And then you have to pair that up with
 the additional command of switch

0:00:39.700000 --> 0:00:45.240000
 port access VLAN and then some number,
 like switch port access VLAN 7

0:00:45.240000 --> 0:00:50.480000
 or VLAN 6, which says that any frame
 that comes in this interface that's

0:00:50.480000 --> 0:00:55.200000
 an untagged ethernet frame will be assigned
 to that broadcast domain of

0:00:55.200000 --> 0:00:59.060000
 VLAN 7 or VLAN 6, whatever
 you configured.

0:00:59.060000 --> 0:01:03.240000
 The other thing you've learned is this
 concept of trunks, VLAN trunks,

0:01:03.240000 --> 0:01:07.360000
 which can be formed either with switch
 port mode trunk or switch port

0:01:07.360000 --> 0:01:12.700000
 mode dynamic and then dynamic auto or
 dynamic desirable, which now means

0:01:12.700000 --> 0:01:16.220000
 all of the broadcast domains
 that you know about Mr.

0:01:16.220000 --> 0:01:21.740000
 Switch, VLAN 7, VLAN 9, VLAN 200, all
 of them are permissible on this

0:01:21.740000 --> 0:01:25.620000
 one interface. The native
 VLAN will be untagged.

0:01:25.620000 --> 0:01:30.060000
 All other ethernet frames will have
 an 802.1Q tag applied to indicate

0:01:30.060000 --> 0:01:32.140000
 what VLAN they belong to.

0:01:32.140000 --> 0:01:35.160000
 Voice VLANs is something
 like right in the middle.

0:01:35.160000 --> 0:01:38.280000
 So let's talk about
 what voice VLANs do.

0:01:38.280000 --> 0:01:41.520000
 So first of all, what problem
 is solved by voice VLANs?

0:01:41.520000 --> 0:01:43.220000
 Why did they create them?

0:01:43.220000 --> 0:01:52.420000
 So here we have your typical situation
 where you have an IP phone and

0:01:52.420000 --> 0:01:55.360000
 I'm just going to and then you also
 have connected to that phone some

0:01:55.360000 --> 0:01:59.660000
 sort of data device like
 a PC or a laptop.

0:01:59.660000 --> 0:02:04.420000
 And our challenge here is that this
 switch port right here is going to

0:02:04.420000 --> 0:02:08.080000
 be receiving frames that were sourced
 by the phone, which is carrying

0:02:08.080000 --> 0:02:09.460000
 your voice traffic.

0:02:09.460000 --> 0:02:12.760000
 It's also going to be receiving ingress
 frames that were sourced by the

0:02:12.760000 --> 0:02:14.940000
 laptop, which is your
 data traffic.

0:02:14.940000 --> 0:02:21.280000
 And ideally, we want some way for that switch
 to be able to tell the difference

0:02:21.280000 --> 0:02:28.300000
 between between frames that were sourced
 from the PC as data frames versus

0:02:28.300000 --> 0:02:33.260000
 frames that were sourced from
 the phone as voice frames.

0:02:33.260000 --> 0:02:36.780000
 And the reason we want to be able to
 differentiate them is maybe to apply

0:02:36.780000 --> 0:02:38.820000
 different policy levels to them.

0:02:38.820000 --> 0:02:41.080000
 We're talking about quality
 of service now.

0:02:41.080000 --> 0:02:46.580000
 So when the frames come in, we want
 to be able to treat the voice frames

0:02:46.580000 --> 0:02:50.960000
 with a higher level of priority, a higher
 level of service, then we treat

0:02:50.960000 --> 0:02:52.180000
 the data frames.

0:02:52.180000 --> 0:02:54.640000
 So we need to be able to tell
 the difference between them.

0:02:54.640000 --> 0:02:59.060000
 And here is where a voice
 VLAN comes into play.

0:02:59.060000 --> 0:03:03.620000
 So with voice VLANs, it gives us the ability
 to basically have two broadcast

0:03:03.620000 --> 0:03:07.040000
 domains assigned to this
 interface on the switch.

0:03:07.040000 --> 0:03:11.420000
 We have one broadcast domain, which
 will be for our access VLAN, which

0:03:11.420000 --> 0:03:16.220000
 is our data, our untagged Ethernet
 frames from the laptop.

0:03:16.220000 --> 0:03:20.100000
 And then we'll have another VLAN also
 on this interface, which will allow

0:03:20.100000 --> 0:03:24.860000
 802.1Q tags. And that will presumably
 be the traffic that's carrying our

0:03:24.860000 --> 0:03:29.020000
 voice inside of the
 Ethernet frames.

0:03:29.020000 --> 0:03:34.040000
 So you can sort of think of this as
 like a little mini 802.1Q trunk.

0:03:34.040000 --> 0:03:37.900000
 But unlike a normal 802.1Q trunk, which
 could be carrying potentially

0:03:37.900000 --> 0:03:44.120000
 hundreds of VLANs with hundreds of different
 802.1Q tag values, here we've

0:03:44.120000 --> 0:03:49.060000
 only got two broadcast domains, not
 all the broadcast domains that the

0:03:49.060000 --> 0:03:52.080000
 switch might be aware of.

0:03:52.080000 --> 0:03:56.200000
 And the way this works here is that
 inside the IP phone itself, there's

0:03:56.200000 --> 0:03:58.220000
 actually like a little
 mini switch.

0:03:58.220000 --> 0:04:00.660000
 They say it's like a
 three port switch.

0:04:00.660000 --> 0:04:05.620000
 So inside the IP phone, you have on
 its switch, you have one port, which

0:04:05.620000 --> 0:04:06.580000
 is the data port.

0:04:06.580000 --> 0:04:10.720000
 And usually if you turn the IP phone
 around, you'll see on the back of

0:04:10.720000 --> 0:04:14.660000
 it a little RJ45, it'll say 2PC.

0:04:14.660000 --> 0:04:19.960000
 So this will say here 2PC, typically,
 or something like that.

0:04:19.960000 --> 0:04:24.300000
 And then you'll see another RJ45 port,
 which will say something like 2

0:04:24.300000 --> 0:04:33.120000
 switch. Switch. And then what you don't
 realize is there's another sort

0:04:33.120000 --> 0:04:37.760000
 of third internal switch port, which
 goes to the actual CPU, the central

0:04:37.760000 --> 0:04:40.680000
 processing unit of
 the phone itself.

0:04:40.680000 --> 0:04:44.140000
 So that's why we say there's like a
 little three port mini switch inside

0:04:44.140000 --> 0:04:46.080000
 the phone itself.

0:04:46.080000 --> 0:04:51.900000
 And the voice VLAN feature on the Cisco
 switch allows us to program that

0:04:51.900000 --> 0:04:55.140000
 little mini switch
 inside the phone.

0:04:55.140000 --> 0:05:05.240000
 So it's useful for isolating user data and
 voice traffic in the same interface.

0:05:05.240000 --> 0:05:10.220000
 OK, so like I said, voice VLANs implies
 that there are two VLANs operating

0:05:10.220000 --> 0:05:15.320000
 on one switch port, your access VLAN,
 which is what your data traffic

0:05:15.320000 --> 0:05:17.860000
 will be using, and
 your voice VLAN.

0:05:17.860000 --> 0:05:21.380000
 And both must be explicitly
 configured.

0:05:21.380000 --> 0:05:26.040000
 Now the access VLAN, that's configured
 the same old way you've always

0:05:26.040000 --> 0:05:31.940000
 done it. Switch port, mode access,
 switch port access, VLAN, whatever.

0:05:31.940000 --> 0:05:33.520000
 So it's no different.

0:05:33.520000 --> 0:05:38.660000
 And notice your mode is still
 switch port mode access.

0:05:38.660000 --> 0:05:40.980000
 The only thing that's different is we're
 now going to have a new command

0:05:40.980000 --> 0:05:45.520000
 that you haven't seen before to
 define what the voice VLAN is.

0:05:45.520000 --> 0:05:51.340000
 Now that helps the switch, the Cisco
 switch, your 3560, your 6500.

0:05:51.340000 --> 0:05:55.660000
 That helps that switch to know, oh, OK,
 when I see an ingress frame coming

0:05:55.660000 --> 0:06:01.180000
 in, this got an 802.1Q tag that
 says this value may be 90.

0:06:01.180000 --> 0:06:03.360000
 I know that's my voice VLAN.

0:06:03.360000 --> 0:06:04.700000
 That's a separate VLAN.

0:06:04.700000 --> 0:06:06.640000
 I need to do something
 different with that.

0:06:06.640000 --> 0:06:08.880000
 But how do we tell the phone?

0:06:08.880000 --> 0:06:14.240000
 How do we tell the IP phone, hey, when
 you take that voice traffic and

0:06:14.240000 --> 0:06:18.780000
 you encapsulate it inside Ethernet
 frames, I want you to tag that with

0:06:18.780000 --> 0:06:21.420000
 an 802.1Q tag. And
 here's the value.

0:06:21.420000 --> 0:06:24.880000
 I want you to put the VLAN
 90 or VLAN 7 in there.

0:06:24.880000 --> 0:06:28.200000
 So how do we get that information
 to the phone?

0:06:28.200000 --> 0:06:30.080000
 Well, you can see here there's
 one of two ways.

0:06:30.080000 --> 0:06:34.840000
 If it's a Cisco IP phone, we can actually
 utilize the Cisco Discovery

0:06:34.840000 --> 0:06:40.360000
 protocol. CDP can push down to the
 phone how it should be reacting to

0:06:40.360000 --> 0:06:44.620000
 VLANs and how it should be tagging
 or potentially not tagging stuff.

0:06:44.620000 --> 0:06:49.140000
 If it's not a Cisco IP phone, well, then
 there is a specific option, option

0:06:49.140000 --> 0:06:52.160000
 156, that you can use in DHCP.

0:06:52.160000 --> 0:06:56.400000
 So the DHCP server itself can be pre
-configured to push that information

0:06:56.400000 --> 0:07:00.480000
 down to the IP phone.

0:07:00.480000 --> 0:07:03.880000
 So here's our command,
 switch port voice VLAN.

0:07:03.880000 --> 0:07:06.120000
 And you can see you've
 got four options here.

0:07:06.120000 --> 0:07:07.800000
 You can actually type a VLAN ID.

0:07:07.800000 --> 0:07:09.420000
 And this is what most people do.

0:07:09.420000 --> 0:07:13.920000
 Switch port voice VLAN
 7 or voice VLAN 90.

0:07:13.920000 --> 0:07:16.800000
 Most of the time, that's
 what people do.

0:07:16.800000 --> 0:07:19.240000
 But on this slide, I'm going to show
 you what all these various options

0:07:19.240000 --> 0:07:23.720000
 do so you can sort of get an idea as to
 how the Ethernet frames are manipulated

0:07:23.720000 --> 0:07:28.640000
 and what's actually being instructed to
 the IP phone based on these various

0:07:28.640000 --> 0:07:34.420000
 options here. So let's start where
 you say switch port voice VLAN and

0:07:34.420000 --> 0:07:38.320000
 then you say like the number
 7 as an example.

0:07:38.320000 --> 0:07:43.180000
 So let's put the number
 7 right here.

0:07:43.180000 --> 0:07:49.240000
 Okay, so what that would mean, I'm
 going to go ahead and expand this a

0:07:49.240000 --> 0:07:55.060000
 little bit. That means that when the
 IP phone sends its voice traffic

0:07:55.060000 --> 0:08:03.400000
 inside of an Ethernet frame, it would
 put an 802.1Q tag, a .1Q tag that

0:08:03.400000 --> 0:08:06.900000
 would say the VLAN is 7.

0:08:06.900000 --> 0:08:11.320000
 And inside that tag, remember, there's
 also what we call priority bits,

0:08:11.320000 --> 0:08:13.000000
 three bits for priority.

0:08:13.000000 --> 0:08:17.600000
 And the default behavior of the IP phone
 is to set that with the number

0:08:17.600000 --> 0:08:21.540000
 of five. So that's what the Ethernet
 frames would look like from the IP

0:08:21.540000 --> 0:08:27.300000
 phone. And then if there's a laptop
 connected to this, when it sends its

0:08:27.300000 --> 0:08:34.120000
 frame, will laptops and PCs by default,
 they don't do 802.1Q tagging.

0:08:34.120000 --> 0:08:37.000000
 So there would be no
 tag on here at all.

0:08:37.000000 --> 0:08:40.260000
 It would just be a regular
 old Ethernet frame.

0:08:40.260000 --> 0:08:46.060000
 So on the switch, when this red frame
 comes in without a tag, whatever

0:08:46.060000 --> 0:08:53.540000
 you've got configured here of switch
 port access VLAN, and I'll just put

0:08:53.540000 --> 0:08:54.320000
 some number in here.

0:08:54.320000 --> 0:08:58.360000
 Let's say it's VLAN 10, well, when this
 red frame comes in with no tag,

0:08:58.360000 --> 0:09:02.260000
 it will be assigned to the broadcast
 domain of VLAN 10.

0:09:02.260000 --> 0:09:06.540000
 And when the green frame comes in that
 is explicitly tagged with the number

0:09:06.540000 --> 0:09:11.260000
 seven, that will match up with our
 switch port voice VLAN command.

0:09:11.260000 --> 0:09:13.660000
 And the switch will say, oh,
 okay, I can allow that.

0:09:13.660000 --> 0:09:16.420000
 I know that VLAN 7
 is the voice VLAN.

0:09:16.420000 --> 0:09:20.160000
 So that's how people typically
 implement voice VLANs.

0:09:20.160000 --> 0:09:22.900000
 There's a couple of other options
 here, as you can see.

0:09:22.900000 --> 0:09:29.960000
 The next option is switch
 port voice VLAN dot 1P.

0:09:29.960000 --> 0:09:31.480000
 So what does that mean?

0:09:31.480000 --> 0:09:38.800000
 Okay. So in that particular case, when
 our phone sends its traffic, now

0:09:38.800000 --> 0:09:44.100000
 it has received a CDP message saying,
 when you send something, I do want

0:09:44.100000 --> 0:09:49.460000
 you to apply a tag and 802.1Q tag,
 but I want the VLAN ID to actually

0:09:49.460000 --> 0:09:53.140000
 be the number zero, to
 be the number zero.

0:09:53.140000 --> 0:09:56.740000
 And because you're putting that tag
 in there, you're still allowed to

0:09:56.740000 --> 0:10:00.740000
 set the priority bits in the tag, which
 by default will be the number

0:10:00.740000 --> 0:10:07.200000
 five. Now by also saying dot 1P, we're
 saying, hey, if you have a PC connected

0:10:07.200000 --> 0:10:16.100000
 to you, laptops, PCs, they do have the
 ability to send frames with tags.

0:10:16.100000 --> 0:10:18.260000
 And this is called 802.1P.

0:10:18.260000 --> 0:10:23.560000
 As a matter of fact, this priority
 section of the tag, that is called

0:10:23.560000 --> 0:10:29.160000
 802.1P. So if you go into the NIC card
 of your laptop per PC and you say,

0:10:29.160000 --> 0:10:31.380000
 I am enabling you for 802.1P.

0:10:31.380000 --> 0:10:39.900000
 That means that laptop will now send
 a tag also with a VLAN ID of zero.

0:10:39.900000 --> 0:10:42.860000
 It will actually populate
 the VLAN of all zeros.

0:10:42.860000 --> 0:10:48.320000
 And now from the laptop, you have the
 ability to set your priority bits.

0:10:48.320000 --> 0:10:52.900000
 Now hopefully, whatever that priority
 is will be something that's not

0:10:52.900000 --> 0:10:55.800000
 five. There will be something
 like maybe three.

0:10:55.800000 --> 0:11:01.660000
 Because at this point, the switch right
 here has no ability to, at layer

0:11:01.660000 --> 0:11:06.520000
 two, differentiate between the voice
 frames and the data frames, because

0:11:06.520000 --> 0:11:09.280000
 they're both coming in on
 what the native VLAN is.

0:11:09.280000 --> 0:11:15.800000
 So in this particular case, if you've
 said switch port, access, VLAN,

0:11:15.800000 --> 0:11:22.500000
 let's say five, then both of these
 frames, because they don't have an

0:11:22.500000 --> 0:11:26.640000
 explicit VLAN configured, both of them
 will go into the broadcast domain

0:11:26.640000 --> 0:11:31.900000
 of VLAN five. Now we don't have really
 a separate voice or data VLAN.

0:11:31.900000 --> 0:11:35.540000
 They're both being lumped together
 into whatever your access VLAN is.

0:11:35.540000 --> 0:11:40.120000
 And the only thing that makes them different
 is their layer two priority

0:11:40.120000 --> 0:11:42.640000
 within their dot one p header.

0:11:42.640000 --> 0:11:46.040000
 And also remember, there's a
 layer three priority as well.

0:11:46.040000 --> 0:11:51.120000
 In the IP header, there's the IP
 precedence bits or the DSCP bits.

0:11:51.120000 --> 0:11:55.640000
 So in that particular case, the
 phone will mark its DSCP.

0:11:55.640000 --> 0:12:01.380000
 This is layer three now in the IP header,
 as what's called expedited forwarding.

0:12:01.380000 --> 0:12:06.140000
 And we'll get into that some
 more when we look at QoS.

0:12:06.140000 --> 0:12:09.660000
 And the laptop, well, we don't
 know what it's going to do.

0:12:09.660000 --> 0:12:12.100000
 We have no idea what
 it's going to do.

0:12:12.100000 --> 0:12:17.560000
 But if the priority is three, then the
 DSCP will be something that matches

0:12:17.560000 --> 0:12:21.160000
 that. Something that matches
 this right here.

0:12:21.160000 --> 0:12:26.800000
 So hopefully at either layer two or layer
 three, we'll be able to differentiate

0:12:26.800000 --> 0:12:30.680000
 the traffic and apply different quality
 of service policies because at

0:12:30.680000 --> 0:12:34.100000
 layer two, they're both going to
 go into the same access VLAN.

0:12:34.100000 --> 0:12:38.680000
 So that's what happens when we use
 the dot one p option in our switch

0:12:38.680000 --> 0:12:42.300000
 port voice VLAN command.

0:12:42.300000 --> 0:12:47.820000
 We're basically telling the phone, put
 a tag with a value of zero in the

0:12:47.820000 --> 0:12:52.080000
 VLAN. Now what other
 options do we have?

0:12:52.080000 --> 0:12:57.380000
 Well, what if we do switch
 port voice VLAN untagged?

0:12:57.380000 --> 0:13:02.140000
 Okay, so now what's happening
 is we're telling the phone.

0:13:02.140000 --> 0:13:07.460000
 So via CDP, we're saying
 use VLAN 409695.

0:13:07.460000 --> 0:13:11.520000
 VLAN 409695 is actually
 a special VLAN number.

0:13:11.520000 --> 0:13:15.420000
 It's actually called the dead VLAN,
 kind of a weird thing, but it's a

0:13:15.420000 --> 0:13:17.540000
 reserved VLAN called
 the dead VLAN.

0:13:17.540000 --> 0:13:20.520000
 And it's a way of saying
 don't tag anything.

0:13:20.520000 --> 0:13:23.900000
 You are not allowed to
 use VLAN tags at all.

0:13:23.900000 --> 0:13:28.920000
 So my Cisco switch now is telling
 the phone, you can't do 802.1Q.

0:13:28.920000 --> 0:13:31.120000
 No tags allowed from you at all.

0:13:31.120000 --> 0:13:33.080000
 So what does that actually
 look like?

0:13:33.080000 --> 0:13:37.880000
 Well, in this particular case now, we
 would see the IP phone just sending

0:13:37.880000 --> 0:13:42.240000
 a regular Ethernet frame with,
 like I said, no tag.

0:13:42.240000 --> 0:13:50.100000
 No tag. But remember at layer three
 in the IP header, I'll just use IP

0:13:50.100000 --> 0:13:54.600000
 precedence because IP precedence is
 easier to understand than DSCP.

0:13:54.600000 --> 0:13:58.900000
 In layer three, we're going to have
 an IP precedence, which is in the

0:13:58.900000 --> 0:14:03.940000
 toss byte of the IP header, which
 is going to be equal to five.

0:14:03.940000 --> 0:14:07.820000
 That's the default value that
 phones give at layer three.

0:14:07.820000 --> 0:14:13.380000
 And if I have a laptop or PC here,
 well, once again, the assumption is

0:14:13.380000 --> 0:14:20.220000
 by default laptops and PCs don't do tags
 and they don't do IP precedence.

0:14:20.220000 --> 0:14:22.400000
 So there will be no tag.

0:14:22.400000 --> 0:14:25.460000
 Unless someone's really messed around
 with their NIC card, this will be

0:14:25.460000 --> 0:14:28.060000
 the default behavior of
 the laptop or the PC.

0:14:28.060000 --> 0:14:29.160000
 There will be no tag.

0:14:29.160000 --> 0:14:34.120000
 And at layer three, the default behavior
 of IP precedence in every single

0:14:34.120000 --> 0:14:39.100000
 frame that you send, whether it be
 web browsing or telnet or email, is

0:14:39.100000 --> 0:14:45.700000
 always zero. So once again, whatever
 the access VLAN is here, switch port

0:14:45.700000 --> 0:14:52.580000
 mode access, sorry for my sloppy writing
 here, access equals, let's say,

0:14:52.580000 --> 0:14:56.260000
 90. Well, then both of these frames
 will be assigned to the broadcast

0:14:56.260000 --> 0:14:58.740000
 domain of VLAN 90.

0:14:58.740000 --> 0:15:01.880000
 And the only way we'll be able to differentiate
 them, the only way we'll

0:15:01.880000 --> 0:15:05.580000
 be able to apply different policies
 will be based on what we see in the

0:15:05.580000 --> 0:15:07.800000
 layer three header, the IP header.


0:15:07.800000 --> 0:15:14.680000
 That'll be it. And then of course, your
 last option is switch port voice

0:15:14.680000 --> 0:15:22.420000
 VLAN none. And that means once again,
 there is no, I'm not giving you

0:15:22.420000 --> 0:15:24.840000
 any VLAN whatsoever.

0:15:24.840000 --> 0:15:31.220000
 So now the IP phone doesn't really
 know what to use for an 802.1Q tag.

0:15:31.220000 --> 0:15:35.280000
 So it'll probably try to get
 that information via DHCP.

0:15:35.280000 --> 0:15:39.720000
 But if DHCP doesn't give it a tag, well
 then at this point, it'll be exactly

0:15:39.720000 --> 0:15:42.660000
 the same as the previous scenario,
 as scenario three.

0:15:42.660000 --> 0:15:48.680000
 If this phone is not being given a voice
 VLAN from my switch, and if it's

0:15:48.680000 --> 0:15:54.080000
 not being given a voice VLAN via DHCP,
 then scenario four and scenario

0:15:54.080000 --> 0:15:58.440000
 three will end up being
 exactly the same thing.

0:15:58.440000 --> 0:16:04.100000
 So how do we verify if there's a voice
 VLAN and if there is what it is?

0:16:04.100000 --> 0:16:08.380000
 Well, we can do the command show interface
 switch port to see that.

0:16:08.380000 --> 0:16:14.600000
 For example, if I go on the switch
 right now, if I do show interface,

0:16:14.600000 --> 0:16:20.380000
 fast ethernet zero slash one switch port,
 I make this a little bit larger

0:16:20.380000 --> 0:16:21.960000
 here for you guys.

0:16:21.960000 --> 0:16:27.500000
 So right now, there is no
 voice VLAN right here.

0:16:27.500000 --> 0:16:29.240000
 I have not configured any.

0:16:29.240000 --> 0:16:32.880000
 And the default access
 VLAN is VLAN one.

0:16:32.880000 --> 0:16:38.580000
 So all I have to do is go into my interface
 and say switch port, voice

0:16:38.580000 --> 0:16:41.640000
 VLAN, and I'll use VLAN two.

0:16:41.640000 --> 0:16:45.400000
 Now in my case, VLAN two has not
 actually been created yet.

0:16:45.400000 --> 0:16:49.100000
 So this particular switch like many
 other Cisco switches will create the

0:16:49.100000 --> 0:16:52.320000
 VLAN since it doesn't
 already exist.

0:16:52.320000 --> 0:16:56.160000
 And now when I do that same show command,
 it'll explicitly say that my

0:16:56.160000 --> 0:16:58.300000
 voice VLAN is two.

0:16:58.300000 --> 0:17:03.120000
 And you can see how that's different
 than my access mode VLAN, which is

