WEBVTT

1
00:00.000 --> 00:05.400
Next up, we want to do some configuration around radio resource management as

2
00:05.400 --> 00:07.000
well as get our mobility groups configured.

3
00:07.000 --> 00:11.000
Well, the way we're going to do that is we're going to log into our controller

4
00:11.000 --> 00:13.000
here, go to configuration,

5
00:13.000 --> 00:16.490
and we're going to find radio configurations here, and then our R.M. is right

6
00:16.490 --> 00:17.000
there.

7
00:17.000 --> 00:21.350
So what we're going to find is we've got different elements of the radio space

8
00:21.350 --> 00:23.000
that we want to manage.

9
00:23.000 --> 00:27.040
And there are a few primary categories that we're going to want to especially

10
00:27.040 --> 00:28.000
pay attention to,

11
00:28.000 --> 00:30.000
but let's just go ahead and talk about all of the options.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:28.000 --> 00:30.000
but let's just go ahead and talk about all of the options.

12
00:30.000 --> 00:33.400
So first of all, when we go to radio resource management, we see that we can

13
00:33.400 --> 00:36.000
perform individual configurations based on the band,

14
00:36.000 --> 00:40.360
which is pretty cool. So if I go to the 5 gigahertz band, under general, I can

15
00:40.360 --> 00:44.000
see that we can define the different thresholds for clients to connect,

16
00:44.000 --> 00:47.770
as well as the number of clients. Coverage is interesting. We can also define

17
00:47.770 --> 00:49.000
some thresholds in here.

18
00:49.000 --> 00:55.000
We have to be very careful about changing things from the default,

19
00:55.000 --> 00:59.700
but this is where we could enable coverage hold detection. This is self-healing

20
00:59.700 --> 01:00.000
.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:59.700 --> 01:00.000
.

21
01:00.000 --> 01:03.960
The concept of one AP goes down, that other APs could boost their signal to try

22
01:03.960 --> 01:05.000
to cover that space.

23
01:05.000 --> 01:09.000
So if we do want to enable that, this is where we can, or I may as should say,

24
01:09.000 --> 01:11.000
disable it because it's enabled by default,

25
01:11.000 --> 01:15.000
then we can come here. We also have dynamic channel assignment.

26
01:15.000 --> 01:19.800
So DCA, this is where I can allow my wireless line controller to figure out

27
01:19.800 --> 01:22.000
what channel is going to be best.

28
01:22.000 --> 01:28.000
And I can scroll all the way down here and see which channels are eligible.

29
01:28.000 --> 01:32.810
So if I need to tweak this for any specific reason, maybe regulatory
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
01:28.000 --> 01:32.810
So if I need to tweak this for any specific reason, maybe regulatory

30
01:32.810 --> 01:37.000
requirements where I live is going to require me to not use specific channels,

31
01:37.000 --> 01:41.050
or maybe I just want to limit the channels in use for one reason or another. I

32
01:41.050 --> 01:42.000
can do that here.

33
01:42.000 --> 01:47.240
I can allow the wireless line controller to dynamically change my channel width

34
01:47.240 --> 01:49.000
s and so on and so forth.

35
01:49.000 --> 01:53.420
From here, we've got transmit power control, TPC. This allows me to control the

36
01:53.420 --> 01:55.000
power level of my access points,

37
01:55.000 --> 02:00.310
and I can make it so that maybe their maximum power level is like 24 dBm
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:55.000 --> 02:00.310
and I can make it so that maybe their maximum power level is like 24 dBm

38
02:00.310 --> 02:04.000
instead of 30 dBm, whatever makes sense for my environment.

39
02:04.000 --> 02:10.270
And then RF grouping here, this is where we can actually configure our RF group

40
02:10.270 --> 02:11.000
status.

41
02:11.000 --> 02:16.210
So again, we configured the group name of being CBTM, and we see the group

42
02:16.210 --> 02:18.000
leader that's been elected.

43
02:18.000 --> 02:22.000
Again, I only have one wireless line controller, so it's this controller, WLC1.

44
02:22.000 --> 02:24.000
However, we can say,

45
02:24.000 --> 02:28.000
"Hey, I want you to be the leader explicitly. I can check this box here."

46
02:28.000 --> 02:32.320
And that's pretty much where it comes down to. Here, I can see the list of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:28.000 --> 02:32.320
And that's pretty much where it comes down to. Here, I can see the list of

47
02:32.320 --> 02:35.000
controllers that would be in this RF group.

48
02:35.000 --> 02:39.300
And then spatial reuse is interesting. This is a Wi-Fi 6 enhancement that

49
02:39.300 --> 02:41.000
allows me to set BSS colors,

50
02:41.000 --> 02:45.610
and effectively allows me to be more efficient with my transmit in a high

51
02:45.610 --> 02:47.000
density network.

52
02:47.000 --> 02:51.060
So again, this isn't a wireless course. We don't need to drill into the nitty-

53
02:51.060 --> 02:53.000
gritty details of any one of these.

54
02:53.000 --> 02:56.440
Just generally speaking, understand that radio resource management controls the

55
02:56.440 --> 03:00.000
channels, controls the power, controls the RF.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:56.440 --> 03:00.000
channels, controls the power, controls the RF.

56
03:00.000 --> 03:03.940
Well, at least I have my option in here for RF groups, so I need to understand

57
03:03.940 --> 03:05.000
what the RF groups are.

58
03:05.000 --> 03:10.540
And then the self-healing here, the coverage hole detection is again a big part

59
03:10.540 --> 03:14.000
of the Cisco lightweight wireless solution.

60
03:14.000 --> 03:17.270
Now, lastly, we want to take a look at mobility groups. I can go to

61
03:17.270 --> 03:21.000
configuration here. Once again, go to the wireless section.

62
03:21.000 --> 03:25.280
And now we see a mobility area here. So I'm going to click on mobility, and

63
03:25.280 --> 03:28.000
this will allow me to change the mobility group name.

64
03:28.000 --> 03:32.700
If I want to use multicast, which is going to be advised, if I have a lot of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
03:28.000 --> 03:32.700
If I want to use multicast, which is going to be advised, if I have a lot of

65
03:32.700 --> 03:35.000
wireless lane controllers that are layer three separated,

66
03:35.000 --> 03:39.200
then I would probably want to use multicast because otherwise it's a full mesh

67
03:39.200 --> 03:41.000
of unicast configurations.

68
03:41.000 --> 03:46.160
Now, something to keep in mind with mobility groups is the fact that I do have

69
03:46.160 --> 03:48.000
to configure my peers.

70
03:48.000 --> 03:52.510
So I come to peer configuration, and I can add a mobility peer here. I've got

71
03:52.510 --> 03:56.000
to enter the MAC address and the IP address and the group name.

72
03:56.000 --> 04:01.370
And this is going to be an important part of configuring mobility groups, which
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
03:56.000 --> 04:01.370
And this is going to be an important part of configuring mobility groups, which

73
04:01.370 --> 04:06.000
leads to seamless roaming, potentially even across layer three boundaries.

74
04:06.000 --> 04:09.910
So we covered mobility groups in a lot of detail earlier on, but this is where

75
04:09.910 --> 04:13.000
we configure it. Again, it's under configuration, then wireless,

76
04:13.000 --> 04:18.790
and then mobility to configure my mobility group name, as well as my mobility

77
04:18.790 --> 04:20.000
group peers.