WEBVTT

0:00:03.100000 --> 0:00:07.060000
 Hello and welcome to this video which
 wraps up our QOS section review

0:00:07.060000 --> 0:00:11.500000
 for the CCNA 200-301 bootcamp.

0:00:11.500000 --> 0:00:14.340000
 So in this one we're going to finish
 up by now focusing on some of the

0:00:14.340000 --> 0:00:19.680000
 aspects of Wi-Fi QOS, how you can apply
 it to your access point to affect

0:00:19.680000 --> 0:00:21.220000
 your wireless LANs.

0:00:21.220000 --> 0:00:27.740000
 So I'm going to give you a brief
 review of Wi-Fi frame delivery.

0:00:27.740000 --> 0:00:30.540000
 And then we're going to talk about something
 that's unique to Wi-Fi which

0:00:30.540000 --> 0:00:36.260000
 is CSMA CA. You don't have to know the
 gory details of how CSMA CA works,

0:00:36.260000 --> 0:00:42.280000
 but if you're going to implement QOS
 in Wi-Fi, it does affect CSMA CA,

0:00:42.280000 --> 0:00:45.080000
 and so you have to know what's
 happening at a high level.

0:00:45.080000 --> 0:00:51.140000
 And then we're going to look at Wi-Fi
 QOS 802.11e and access classes and

0:00:51.140000 --> 0:00:59.280000
 something called precious
 metal policies.

0:00:59.280000 --> 0:01:06.060000
 Okay, so in a wired LAN where a host
 would be typically connected directly

0:01:06.060000 --> 0:01:11.400000
 to a physical switch port, that host
 would have dedicated access to that

0:01:11.400000 --> 0:01:15.800000
 switch port. No other host can use it,
 but your laptop or PC that's connected

0:01:15.800000 --> 0:01:19.620000
 to there. And that one switch port would
 have some transmit and receive

0:01:19.620000 --> 0:01:25.180000
 cues for receiving frames from
 you and sending frames to you.

0:01:25.180000 --> 0:01:28.140000
 Wireless LANs and access points,
 they don't have that.

0:01:28.140000 --> 0:01:31.220000
 It's a totally different
 structure.

0:01:31.220000 --> 0:01:37.460000
 So most Wi-Fi IEEE protocols, we're talking
 about like 802.11n, 802.11ac,

0:01:37.460000 --> 0:01:43.400000
 802.11b and so forth, provide a shared
 contention-based network that's

0:01:43.400000 --> 0:01:46.740000
 our BSS for Wi-Fi stations.

0:01:46.740000 --> 0:01:52.600000
 So that means that, as I've mentioned
 some Wi-Fi material, that of all

0:01:52.600000 --> 0:01:56.180000
 the devices that are associated in using
 this access point that's on the

0:01:56.180000 --> 0:02:01.100000
 ceiling or on the wall, typically only
 one person can talk at a time.

0:02:01.100000 --> 0:02:04.320000
 If more than, if two or more people talk
 at the same time, that's considered

0:02:04.320000 --> 0:02:06.760000
 a collision, that is contention.

0:02:06.760000 --> 0:02:13.360000
 So in both the upstream direction to
 the access point and downstream from

0:02:13.360000 --> 0:02:17.580000
 the access point to your client, Wi
-Fi frames are largely delivered as

0:02:17.580000 --> 0:02:19.620000
 first in, first out.

0:02:19.620000 --> 0:02:23.120000
 There's really no consideration as to
 the type of data, the priority of

0:02:23.120000 --> 0:02:25.520000
 the packet, or anything like that.


0:02:25.520000 --> 0:02:31.000000
 So in the world of wired Ethernet,
 back when we were dealing with hubs

0:02:31.000000 --> 0:02:36.660000
 and things were half duplex, you had
 to learn something called CSMA CD,

0:02:36.660000 --> 0:02:39.940000
 carrier sense, multiple access
 with collision detect.

0:02:39.940000 --> 0:02:43.480000
 And you had to know how that worked
 in the world of wired LANs.

0:02:43.480000 --> 0:02:50.440000
 Well, Wi-Fi uses something very,
 very different called CSMA CA.

0:02:50.440000 --> 0:02:54.440000
 And this is a channel access method
 that's used by Wi-Fi to try to avoid

0:02:54.440000 --> 0:02:59.100000
 collisions and do something about
 collisions when they occur.

0:02:59.100000 --> 0:03:06.580000
 So CSMA CA stands for carrier sense, multiple
 access with collision avoidance.

0:03:06.580000 --> 0:03:09.540000
 Collision avoidance.

0:03:09.540000 --> 0:03:12.900000
 And it uses different
 types of time slots.

0:03:12.900000 --> 0:03:17.580000
 Each time slot has a name to dictate
 when you can transmit.

0:03:17.580000 --> 0:03:22.240000
 And by inducing some variation and some
 randomness into the time slots,

0:03:22.240000 --> 0:03:31.660000
 that's what hopefully
 avoids contention.

0:03:31.660000 --> 0:03:37.400000
 So CSMA CA ultimately at its heart
 uses a fairly complex algorithm or

0:03:37.400000 --> 0:03:42.820000
 protocol called DCF, the distributed
 coordinated function.

0:03:42.820000 --> 0:03:46.100000
 So I'm just going to go into a real
 high level of it right here.

0:03:46.100000 --> 0:03:50.880000
 But if you want a little bit more details,
 just Google CSMA CA and distributed

0:03:50.880000 --> 0:03:53.740000
 coordinated function and you'll
 find everything that you need.

0:03:53.740000 --> 0:03:56.960000
 All right, so let's do a quick
 overview of CSMA CA.

0:03:56.960000 --> 0:04:00.720000
 So I just mentioned it's carrier sense,
 multiple access with collision

0:04:00.720000 --> 0:04:04.640000
 avoidance. So here's how it works.


0:04:04.640000 --> 0:04:09.720000
 Your Wi-Fi net card
 wants to transmit.

0:04:09.720000 --> 0:04:13.740000
 So the first thing that's going to
 happen is your Wi-Fi net card, just

0:04:13.740000 --> 0:04:18.240000
 like in regular wired LANs, right, in
 wired ethernet, you would do carrier

0:04:18.240000 --> 0:04:21.980000
 sense. Now in a wired LAN, you would listen
 for the presence of an electrical

0:04:21.980000 --> 0:04:25.200000
 signal, a carrier on
 your ethernet cable.

0:04:25.200000 --> 0:04:28.800000
 And if you didn't hear anything, you
 say, okay, it must be free, I can

0:04:28.800000 --> 0:04:33.980000
 go. In Wi-Fi, right, it's not electro,
 it's electromagnetic radiation,

0:04:33.980000 --> 0:04:35.560000
 it's radio frequencies.

0:04:35.560000 --> 0:04:38.700000
 So your net card already knows
 what channel it's on.

0:04:38.700000 --> 0:04:42.280000
 It already knows what, you know, tiny slice
 of radio frequency it's transmitting

0:04:42.280000 --> 0:04:43.500000
 and listening to.

0:04:43.500000 --> 0:04:46.560000
 So if it needs to transmit something,
 or if the access point needs to

0:04:46.560000 --> 0:04:50.260000
 transmit something to you,
 it operates the same way.

0:04:50.260000 --> 0:04:55.040000
 It listens for activity
 on that radio frequency.

0:04:55.040000 --> 0:05:00.980000
 Now, if it says, oh, nobody's transmitting
 right now, well, unlike wired

0:05:00.980000 --> 0:05:07.440000
 LANs that say, okay, I can go in wireless
 in 802.11, you know, 802.11

0:05:07.440000 --> 0:05:12.680000
 Wi-Fi, if it's free, if nobody seems
 to be talking right now, then we

0:05:12.680000 --> 0:05:21.360000
 wait a predefined amount of time to
 release, not the lever be tested on

0:05:21.360000 --> 0:05:25.940000
 that diffs. Very short, you
 can see 34 microseconds.

0:05:25.940000 --> 0:05:27.540000
 So you wait 34 microseconds.

0:05:27.540000 --> 0:05:32.040000
 Now, imagine this for a moment, imagine
 that two Wi-Fi NIC cards on two

0:05:32.040000 --> 0:05:36.420000
 different laptops associated to the
 same access point, they both have

0:05:36.420000 --> 0:05:38.100000
 something they want to transmit.

0:05:38.100000 --> 0:05:40.900000
 They both listen at the same
 time, oh, it's free.

0:05:40.900000 --> 0:05:44.340000
 Okay, so now they both wait
 diffs, 34 microseconds.

0:05:44.340000 --> 0:05:46.740000
 You might think, oh, well, they're going
 to run into each other, right?

0:05:46.740000 --> 0:05:48.660000
 Because their diffs
 interval is done.

0:05:48.660000 --> 0:05:51.600000
 Well, hold on, they can't
 transmit just yet.

0:05:51.600000 --> 0:05:57.120000
 Once the diffs interval is done, then we
 generate a random back-off contention

0:05:57.120000 --> 0:05:59.640000
 window of time slots.

0:05:59.640000 --> 0:06:03.860000
 Each time slot is 20 microseconds.


0:06:03.860000 --> 0:06:09.520000
 And this is where we're trying to avoid
 collisions because this is randomized.

0:06:09.520000 --> 0:06:14.940000
 So PC number one might decide, oh, I'm
 going to randomly select a contention

0:06:14.940000 --> 0:06:17.620000
 window of four time slots.

0:06:17.620000 --> 0:06:21.880000
 And PC number two might say, I'm going
 to randomly generate a contention

0:06:21.880000 --> 0:06:24.300000
 window of seven time slots.

0:06:24.300000 --> 0:06:25.880000
 And so PC number one will win.

0:06:25.880000 --> 0:06:30.400000
 Once his four time slots are done waiting
 20 microseconds, 20 microseconds,

0:06:30.400000 --> 0:06:34.400000
 20 microseconds, 20 microseconds is
 done, nobody's been talking yet, I

0:06:34.400000 --> 0:06:36.900000
 can go transmit it free.

0:06:36.900000 --> 0:06:42.260000
 Now, imagine this other guy over here,
 he's only four time slots into

0:06:42.260000 --> 0:06:45.880000
 a seven. All of a sudden, he starts
 hearing radio frequencies, he says,

0:06:45.880000 --> 0:06:49.320000
 oh, man, somebody is
 talking right now.

0:06:49.320000 --> 0:06:55.000000
 So if the medium is busy, then he's
 going to generate a different amount

0:06:55.000000 --> 0:06:57.820000
 of what's called back-off slots.

0:06:57.820000 --> 0:07:00.580000
 These are also 20
 microseconds each.

0:07:00.580000 --> 0:07:04.740000
 It's going to be a minimum
 of 15, a maximum of 1,023.

0:07:04.740000 --> 0:07:06.440000
 He's going to count down.

0:07:06.440000 --> 0:07:11.300000
 So count down slots as long
 as the medium is not busy.

0:07:11.300000 --> 0:07:13.580000
 Okay, so he's going
 to be listening.

0:07:13.580000 --> 0:07:16.580000
 He's listening for PC number one,
 PC number one is transmitting.

0:07:16.580000 --> 0:07:20.040000
 At some point, PC number one is going
 to stop transmitting and the RF

0:07:20.040000 --> 0:07:21.800000
 is going to be free.

0:07:21.800000 --> 0:07:24.880000
 Now, this guy's going to say, okay,
 I'm going to take these time slots

0:07:24.880000 --> 0:07:28.640000
 that I just randomly generated
 as part of my back-off.

0:07:28.640000 --> 0:07:30.940000
 And I'm going to decrement those.

0:07:30.940000 --> 0:07:34.640000
 And then hopefully during all this time,
 if nobody talks by the time that's

0:07:34.640000 --> 0:07:41.620000
 done, then I can transmit.

0:07:41.620000 --> 0:07:45.040000
 Now, another thing about Wi-Fi that
 I don't have here in the slides is

0:07:45.040000 --> 0:07:49.940000
 that every data frame that's transmitted,
 either from the access point

0:07:49.940000 --> 0:07:54.900000
 to you or from you to the access
 point is actually acknowledged.

0:07:54.900000 --> 0:07:57.420000
 Just like we talked about in some of
 the previous slides, how there were

0:07:57.420000 --> 0:08:00.740000
 some Wi-Fi frames that were unique
 to just Wi-Fi, like beacons.

0:08:00.740000 --> 0:08:05.260000
 I mentioned that the access point 10
 times every second sends out a beacon

0:08:05.260000 --> 0:08:06.720000
 saying, hey, here I am.

0:08:06.720000 --> 0:08:09.760000
 Here's my SSID. Here's the wireless
 LAN you can connect to.

0:08:09.760000 --> 0:08:13.180000
 Well, there's another Wi-Fi frame
 type called an acknowledgment.

0:08:13.180000 --> 0:08:16.620000
 So whether I'm transmitting to the access
 point or he's transmitting to

0:08:16.620000 --> 0:08:22.040000
 me, whoever transmits, once transmit
 is done, remember how we just talked

0:08:22.040000 --> 0:08:25.500000
 about the diffs interval, which was,
 okay, when I want to transmit a data

0:08:25.500000 --> 0:08:27.040000
 frame, I'm going to wait.

0:08:27.040000 --> 0:08:27.800000
 It was up here at the top.

0:08:27.800000 --> 0:08:30.560000
 I'm going to wait 34 microseconds
 of diffs.

0:08:30.560000 --> 0:08:35.840000
 Well, there's a shorter interval called
 SIFs, which stands for short interframe

0:08:35.840000 --> 0:08:40.900000
 space. Don't have to memorize that,
 but that is for acknowledgments.

0:08:40.900000 --> 0:08:46.280000
 So if I transmit my frame, I'm going
 to wait the SIFs interval, and when

0:08:46.280000 --> 0:08:52.840000
 SIFs interval is over, I should get
 an 802.11 acknowledgment frame back.

0:08:52.840000 --> 0:08:55.640000
 Because you see, this is one thing that
 makes Wi-Fi very different than

0:08:55.640000 --> 0:08:59.920000
 wired LANs. Back in the world of wired
 Ethernet, back when you used to

0:08:59.920000 --> 0:09:04.180000
 do half duplex, an Ethernet cable in
 the NIC card it was connected to,

0:09:04.180000 --> 0:09:09.640000
 that NIC card was actually capable of
 transmitting and listening at the

0:09:09.640000 --> 0:09:13.000000
 same time. And so the way it detected collisions
 is said, okay, I'm transmitting

0:09:13.000000 --> 0:09:15.040000
 on my receive pins.

0:09:15.040000 --> 0:09:16.440000
 I shouldn't be getting anything.

0:09:16.440000 --> 0:09:19.760000
 But if while I'm transmitting on my
 transmit pins, all of a sudden some

0:09:19.760000 --> 0:09:23.920000
 electrical energy came in on my receive
 pin, that I knew a collision had

0:09:23.920000 --> 0:09:28.900000
 happened. But with Wi-Fi, you
 can only do one or the other.

0:09:28.900000 --> 0:09:32.000000
 Your transceiver can only transmit
 or it can receive.

0:09:32.000000 --> 0:09:33.940000
 It can't do both at the same time.


0:09:33.940000 --> 0:09:36.600000
 So while you're transmitting, it's like
 you're like this with your hands

0:09:36.600000 --> 0:09:38.340000
 up to your ears and you
 can't hear anything.

0:09:38.340000 --> 0:09:41.560000
 So if a collision happened,
 you wouldn't know.

0:09:41.560000 --> 0:09:43.920000
 This is why we need
 the acknowledgment.

0:09:43.920000 --> 0:09:47.220000
 Because if while I'm transmitting somebody
 else transmits the receiver

0:09:47.220000 --> 0:09:50.500000
 of that transmission, he's not
 going to acknowledge me.

0:09:50.500000 --> 0:09:54.420000
 Because my Wi-Fi frame was garbled, it
 was mixed up, he can't acknowledge

0:09:54.420000 --> 0:09:58.100000
 me. So once I'm done transmitting,
 I listen.

0:09:58.100000 --> 0:10:02.800000
 If I don't get my acknowledgment, now
 I know there's been a collision.

0:10:02.800000 --> 0:10:07.080000
 And like it says right here, now
 I have to retransmit again.

0:10:07.080000 --> 0:10:10.860000
 So what does all this have
 to do with Wi-Fi QOS?

0:10:10.860000 --> 0:10:17.820000
 Well, Wi-Fi QOS, when you enable QOS, it
 modifies a couple of two fundamental

0:10:17.820000 --> 0:10:22.040000
 elements. Number one, it plays
 around with those timers.

0:10:22.040000 --> 0:10:25.100000
 Now you don't have to know the details
 of what it does or how it shrinks

0:10:25.100000 --> 0:10:30.460000
 them, but just know that certain Wi-Fi
 policies will increase or decrease

0:10:30.460000 --> 0:10:34.780000
 the amount of time we have to
 wait to transmit something.

0:10:34.780000 --> 0:10:38.800000
 That's one way that we can give preferred
 traffic preferential treatment.

0:10:38.800000 --> 0:10:42.740000
 We can say, okay, for voice traffic,
 I'm not going to wait diffs.

0:10:42.740000 --> 0:10:48.240000
 I'm going to wait less
 time than that.

0:10:48.240000 --> 0:10:53.380000
 So by giving certain types of traffic,
 a greater probability of getting

0:10:53.380000 --> 0:10:57.500000
 into the airwaves, because you're waiting
 less time, we're giving it quality

0:10:57.500000 --> 0:11:04.440000
 of service. Also, Wi-Fi QOS can mark
 frames prior to transmitting those

0:11:04.440000 --> 0:11:06.100000
 frames onto the wired LAN.

0:11:06.100000 --> 0:11:16.280000
 Now Wi-Fi QOS was very first introduced
 into the 802.11e standard.

0:11:16.280000 --> 0:11:19.400000
 And 802.11e said, here's
 what you should do.

0:11:19.400000 --> 0:11:23.840000
 You should sort all of your traffic
 into four different access classes

0:11:23.840000 --> 0:11:29.900000
 or ACs. And depending on which access
 class you fall into, we'll determine

0:11:29.900000 --> 0:11:34.020000
 how we're going to modify the distributed
 coordinated function.

0:11:34.020000 --> 0:11:37.040000
 Remember, that was the whole background
 thing about how long do I wait?

0:11:37.040000 --> 0:11:39.160000
 How much contention window I have?


0:11:39.160000 --> 0:11:40.280000
 How many times lost do I have?

0:11:40.280000 --> 0:11:43.700000
 Before I can even get this thing
 out and start transmitting it.

0:11:43.700000 --> 0:11:48.420000
 So the access classes you can see right
 here, it was based on the original

0:11:48.420000 --> 0:11:51.580000
 cost values of zero through seven.


0:11:51.580000 --> 0:11:54.880000
 So you can see that one and two were
 given background, which is kind of

0:11:54.880000 --> 0:11:55.580000
 interesting, right?

0:11:55.580000 --> 0:11:59.200000
 You would think that zero would be on
 the bottom, but zero and three were

0:11:59.200000 --> 0:12:04.460000
 best effort. Cost or IP precedence
 values of four and five were given

0:12:04.460000 --> 0:12:08.900000
 video and six and seven
 were given voice.

0:12:08.900000 --> 0:12:16.120000
 All right, so many Wi-Fi vendors decided
 that we're going to give each

0:12:16.120000 --> 0:12:19.200000
 class the name of
 a precious metal.

0:12:19.200000 --> 0:12:24.280000
 In other words, voice traffic, the best
 of all, we're going to call that

0:12:24.280000 --> 0:12:29.020000
 platinum. So if you go into a Wi-Fi
 access point or a controller and you

0:12:29.020000 --> 0:12:34.060000
 say, hey, I'm going to apply platinum
 QOS to this particular wireless

0:12:34.060000 --> 0:12:38.760000
 land. You are applying that
 particular access class.

0:12:38.760000 --> 0:12:41.040000
 Video is given gold.

0:12:41.040000 --> 0:12:46.680000
 Best effort is given silver and
 background is given bronze.

0:12:46.680000 --> 0:12:49.000000
 This is something you should know.


0:12:49.000000 --> 0:12:54.560000
 You should memorize that bronze is background,
 that silver is best effort.

0:12:54.560000 --> 0:12:58.320000
 You don't have to memorize it as access
 class zero or access class one,

0:12:58.320000 --> 0:13:01.780000
 but going into any certification exam,
 you should make flashcards for

0:13:01.780000 --> 0:13:06.220000
 yourself and memorize what the name
 of the precious metal is and what

0:13:06.220000 --> 0:13:07.520000
 the designation is.

0:13:07.520000 --> 0:13:14.280000
 Is that precious mezel designated for voice,
 video, best effort or background?

0:13:14.280000 --> 0:13:18.260000
 And depending on the platform, depending
 on the controller, depending

0:13:18.260000 --> 0:13:24.920000
 on the access point, sometimes you
 will apply this bronze or platinum

0:13:24.920000 --> 0:13:28.240000
 or gold policy to an
 entire wireless land.

0:13:28.240000 --> 0:13:36.060000
 Sometimes you can do it
 on a per user basis.

0:13:36.060000 --> 0:13:41.460000
 Also, as I mentioned, that when you
 apply a precious metal policy, it

0:13:41.460000 --> 0:13:46.680000
 does affect the DSCP or the IP precedence
 bits of packets as they're transmitted

0:13:46.680000 --> 0:13:51.040000
 from the access point
 onto the wired land.

0:13:51.040000 --> 0:13:56.680000
 And you can see right here what
 those settings will be.

0:13:56.680000 --> 0:14:00.940000
 Okay, so I'm going to show
 you two different gooies.

0:14:00.940000 --> 0:14:04.320000
 I just have screenshots here that I'm
 going to use two different gooies

0:14:04.320000 --> 0:14:07.740000
 of two different wireless land controllers
 and older one that Cisco used

0:14:07.740000 --> 0:14:10.440000
 to use it. I'm sure they still
 have out to this day.

0:14:10.440000 --> 0:14:14.520000
 And Cisco's newest latest and greatest
 wireless land controller, the 9800.

0:14:14.520000 --> 0:14:18.800000
 Now I'm going to show you how to apply
 these precious metal policies to

0:14:18.800000 --> 0:14:26.220000
 wireless lands. Okay, so let's start with
 Cisco's 5500 wireless land controller.

0:14:26.220000 --> 0:14:29.720000
 So we can see here, this is all happening
 after you've already created

0:14:29.720000 --> 0:14:32.480000
 your wireless land after you've
 already created your SSID.

0:14:32.480000 --> 0:14:37.160000
 So here we've got an SSID called engineering,
 a wireless land called engineering,

0:14:37.160000 --> 0:14:40.160000
 and we're going to the
 edit settings for that.

0:14:40.160000 --> 0:14:54.080000
 And notice that there's a
 tab up at the top for QOS.

0:14:54.080000 --> 0:14:59.140000
 Okay, and here within the QOS tab,
 it's pretty easy right here.

0:14:59.140000 --> 0:15:02.720000
 The very first drop down window is where
 you get to select your precious

0:15:02.720000 --> 0:15:08.060000
 metal policy. So that's and then
 you would click the apply button.

0:15:08.060000 --> 0:15:10.020000
 Pretty simple right there.

0:15:10.020000 --> 0:15:15.460000
 Now for the 9800 series.

0:15:15.460000 --> 0:15:18.540000
 They've taken a little bit of a
 different approach with this.

0:15:18.540000 --> 0:15:23.580000
 The 9800 series in general breaks the configuration
 up into several different

0:15:23.580000 --> 0:15:28.820000
 steps. You have to configure policies,
 apply policies to tags, and then

0:15:28.820000 --> 0:15:31.520000
 apply your tags to your
 wireless lands.

0:15:31.520000 --> 0:15:35.120000
 Let's just walk through
 the process for that.

0:15:35.120000 --> 0:15:39.700000
 So number one, we're going to create
 a new policy that specifies the metal

0:15:39.700000 --> 0:15:43.880000
 we desire. We're going to create a
 new tag that references that policy

0:15:43.880000 --> 0:15:47.320000
 and then we're going to apply a
 wireless land against that tag.

0:15:47.320000 --> 0:15:48.740000
 One other difference.

0:15:48.740000 --> 0:15:53.520000
 In the 9800 series wireless land
 controller, you have a choice.

0:15:53.520000 --> 0:15:58.060000
 You see for the longest time, if you want
 to do Wi-Fi QOS, your only options

0:15:58.060000 --> 0:16:01.720000
 were to select one of these metals gold,
 platinum, bronze, silver, right?

0:16:01.720000 --> 0:16:02.620000
 And that was it.

0:16:02.620000 --> 0:16:06.840000
 And then when you selected that, you couldn't
 really modify the DCF behavior

0:16:06.840000 --> 0:16:08.820000
 or the QS marking settings.

0:16:08.820000 --> 0:16:11.320000
 It was what it was.

0:16:11.320000 --> 0:16:15.640000
 Now, with like for example this newer
 controller, you can still do that.

0:16:15.640000 --> 0:16:17.800000
 And I'm going to show you how to
 walk through how to do that.

0:16:17.800000 --> 0:16:21.500000
 Or you can actually set a lot
 of these settings yourself.

0:16:21.500000 --> 0:16:25.580000
 You can apply policing against individual
 users or wireless lands.

0:16:25.580000 --> 0:16:27.860000
 You can set the markings yourself.


0:16:27.860000 --> 0:16:29.100000
 Not going to go into that.

0:16:29.100000 --> 0:16:31.940000
 Just know that on the 9800 wireless
 land controllers, if you want to do

0:16:31.940000 --> 0:16:36.160000
 QOS, you're not just stuck with one of
 these four precious metal policies.

0:16:36.160000 --> 0:16:38.300000
 There's a lot more granularity
 you can get into.

0:16:38.300000 --> 0:16:43.220000
 If you want to. Alright, so step number
 one, we're going to go into the

0:16:43.220000 --> 0:16:44.940000
 configuration section
 in the dashboard.

0:16:44.940000 --> 0:16:49.800000
 And you can see we're going to select
 policy under configuration.

0:16:49.800000 --> 0:16:54.560000
 After that, we're going
 to add a new policy.

0:16:54.560000 --> 0:17:00.680000
 And then we're just going to give that
 policy a name and description.

0:17:00.680000 --> 0:17:07.620000
 We want to enable that policy
 so we can actually use it.

0:17:07.620000 --> 0:17:12.460000
 So notice here we were in as we add
 the policy, we were in the general

0:17:12.460000 --> 0:17:16.960000
 tab. Okay, once you've done this stuff,
 then we're going to move over

0:17:16.960000 --> 0:17:20.280000
 to the QOS and ABC tab.

0:17:20.280000 --> 0:17:21.980000
 And that's what we see next.

0:17:21.980000 --> 0:17:26.080000
 So now we click on the QS
 ABC tab and we see this.

0:17:26.080000 --> 0:17:33.300000
 And this is where you can select
 your precious metal policy.

0:17:33.300000 --> 0:17:42.440000
 So you can select ingress or egress
 ingress is from the clients to you.

0:17:42.440000 --> 0:17:44.920000
 And then what you're going to do when
 you put your stuff, when what the

0:17:44.920000 --> 0:17:48.480000
 access point is going to do when it
 puts the stuff onto the wired land.

0:17:48.480000 --> 0:17:52.520000
 egress is from the access
 point down to the client.

0:17:52.520000 --> 0:17:58.760000
 So you're going to select one or both
 of these and select your policy.

0:17:58.760000 --> 0:18:02.460000
 Okay, now right here we can view so
 knows we're under configuration tags

0:18:02.460000 --> 0:18:03.460000
 and profiles policy.

0:18:03.460000 --> 0:18:04.440000
 We're just viewing it.

0:18:04.440000 --> 0:18:05.380000
 Yep, there it is.

0:18:05.380000 --> 0:18:06.400000
 We just configured that.

0:18:06.400000 --> 0:18:07.660000
 So it is showing up.

0:18:07.660000 --> 0:18:12.300000
 So now we need to apply this policy
 against something called a tag.

0:18:12.300000 --> 0:18:14.840000
 So now we go back
 to the dashboard.

0:18:14.840000 --> 0:18:18.220000
 But this time we do
 configuration tags.

0:18:18.220000 --> 0:18:22.760000
 All right, so we're
 going to add again.

0:18:22.760000 --> 0:18:25.660000
 We're going to give a name
 and description to the tag.

0:18:25.660000 --> 0:18:31.480000
 And now here what we're doing is we're
 saying, okay, what policy do I

0:18:31.480000 --> 0:18:33.500000
 want this tag to apply to.

0:18:33.500000 --> 0:18:37.540000
 And we're going to select the policy
 we just configured to do this.

0:18:37.540000 --> 0:18:45.000000
 So on this page here, we're actually
 doing two things at once with the

0:18:45.000000 --> 0:18:48.480000
 tag. We're telling the tag.

0:18:48.480000 --> 0:18:50.300000
 Which policy we want.

0:18:50.300000 --> 0:18:54.600000
 Right, and we just configured, you know,
 a particular policy right here.

0:18:54.600000 --> 0:19:01.400000
 And we're telling it which wireless
 LAN we want that to apply against.

0:19:01.400000 --> 0:19:03.140000
 So two things at once.

0:19:03.140000 --> 0:19:07.240000
 And then we hit the check
 button to apply it.

0:19:07.240000 --> 0:19:12.680000
 And now we see the tag
 that we just did.

0:19:12.680000 --> 0:19:19.520000
 So that's basically the steps of applying
 a precious metal Wi-Fi QS policy

0:19:19.520000 --> 0:19:22.160000
 to one of your wireless LANs.

0:19:22.160000 --> 0:19:23.420000
 Thank you for watching this video.