WEBVTT 1 00:00.000 --> 00:03.360 Alright, we're going to wrap up here by taking a look at where we configure 2 00:03.360 --> 00:04.200 certain elements 3 00:04.200 --> 00:08.470 that we took a look at with iOS Xe and where we configure those with arrow s, 4 00:08.470 --> 00:08.880 especially 5 00:08.880 --> 00:13.000 things like our mobility group and our f group and so on and so forth. 6 00:13.000 --> 00:14.720 So we'll start with mobility here. 7 00:14.720 --> 00:18.060 We're going to go over to controller and here on the general tab, we're going 8 00:18.060 --> 00:18.560 to find that 9 00:18.560 --> 00:22.320 we're part of this default mobility domain name. 10 00:22.320 --> 00:26.850 Now, interestingly, Cisco's calling this the mobility domain name, but this is 11 00:26.850 --> 00:27.440 actually 12 00:27.440 --> 00:29.160 the mobility group. 13 00:29.160 --> 00:33.110 So if I want to change the mobility group name from home to home one or WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:29.160 --> 00:33.110 So if I want to change the mobility group name from home to home one or 14 00:33.110 --> 00:34.160 something like 15 00:34.160 --> 00:35.440 that, I could do that. 16 00:35.440 --> 00:39.960 I could click apply here and then we'll see where that name changes. 17 00:39.960 --> 00:44.260 Specifically, if I look over here on the left under mobility management, I go 18 00:44.260 --> 00:44.920 to mobility 19 00:44.920 --> 00:49.430 groups and we'll see now that my local mobility group is home one, I go back to 20 00:49.430 --> 00:50.200 general, put 21 00:50.200 --> 00:54.900 it back to home, apply mobility groups, and now we're back to being part of the 22 00:54.900 --> 00:56.160 home group. 23 00:56.160 --> 00:59.360 Importantly, here's where we add all of our mobility group peers. 24 00:59.360 --> 01:01.320 Remember, we have to add these individually. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 00:59.360 --> 01:01.320 Remember, we have to add these individually. 25 01:01.320 --> 01:02.800 There's two ways we can add them. 26 01:02.800 --> 01:06.120 I can click new and add the member IP and MAC address. 27 01:06.120 --> 01:11.300 So something like 1.2.3.4 and the MAC address could be, I don't know, 0, 0, 0, 28 01:11.300 --> 01:11.800 0. 29 01:11.800 --> 01:14.520 You got to add in the whole thing here. 30 01:14.520 --> 01:16.280 There we go. 31 01:16.280 --> 01:17.440 There's a MAC address. 32 01:17.440 --> 01:20.240 As part of the same group name, click apply and there we go. 33 01:20.240 --> 01:24.020 It is listed now as a peer and it's trying to reach out, find the control and 34 01:24.020 --> 01:24.640 data path 35 01:24.640 --> 01:27.720 or down because that peer doesn't actually exist. 36 01:27.720 --> 01:31.100 The other thing we can do, whoops, I have to scroll over now, is to click this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 01:27.720 --> 01:31.100 The other thing we can do, whoops, I have to scroll over now, is to click this 37 01:31.100 --> 01:31.640 edit all 38 01:31.640 --> 01:32.640 button. 39 01:32.640 --> 01:37.230 If I do that, it turns it into more or less a text document and I could paste 40 01:37.230 --> 01:37.920 in all of 41 01:37.920 --> 01:41.800 my mobility group peers, maybe in a much more efficient fashion. 42 01:41.800 --> 01:43.080 So this is just an option we have. 43 01:43.080 --> 01:46.440 We can also edit these if we had a typo with one of the MAC addresses. 44 01:46.440 --> 01:52.080 I could just come in here rather than removing it and trying to re-add it. 45 01:52.080 --> 01:55.720 As well, we also have the concept of multi-cast messaging in here. 46 01:55.720 --> 01:59.560 We mentioned that mobility groups as they grow should be converted over to 47 01:59.560 --> 02:00.240 multi-cast WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 47 01:59.560 --> 02:00.240 multi-cast 48 02:00.240 --> 02:01.240 communication. 49 02:01.240 --> 02:06.220 I can enable it here, enter the group address, whatever maybe 239.something 50 02:06.220 --> 02:06.960 that I'm using 51 02:06.960 --> 02:09.600 for the sake of multi-cast messaging. 52 02:09.600 --> 02:13.120 So that is our multi- or our mobility groups. 53 02:13.120 --> 02:16.360 Next is our, has to do with RF configurations. 54 02:16.360 --> 02:20.330 So coming back to the general tab here, we do see that we have an RF group name 55 02:20.330 --> 02:20.640 . 56 02:20.640 --> 02:25.190 So remember, RF groups are supposed to define when we have controllers that 57 02:25.190 --> 02:26.120 should expect 58 02:26.120 --> 02:29.280 to work together from an RF perspective. 59 02:29.280 --> 02:33.070 It makes it so that we can work together to manage our radio resource WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 59 02:29.280 --> 02:33.070 It makes it so that we can work together to manage our radio resource 60 02:33.070 --> 02:33.720 management, our 61 02:33.720 --> 02:34.960 RRM. 62 02:34.960 --> 02:39.120 And so this is also called home, just something that is created during setup. 63 02:39.120 --> 02:41.600 We can change it here if we so desire. 64 02:41.600 --> 02:45.030 Meanwhile I can go over to the wireless tab and this is where most of our RF 65 02:45.030 --> 02:45.840 configuration 66 02:45.840 --> 02:47.080 is done. 67 02:47.080 --> 02:52.480 And so importantly, notice that we've got 802.11a and an AC here, as well as BG 68 02:52.480 --> 02:54.040 and N. If I expand 69 02:54.040 --> 02:58.040 one of these at the very top of both of them, by the way, will be the network 70 02:58.040 --> 02:58.720 option. 71 02:58.720 --> 03:01.240 If I click this, I can see whether or not it's enabled. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 71 02:58.720 --> 03:01.240 If I click this, I can see whether or not it's enabled. 72 03:01.240 --> 03:04.840 Now be careful here because again, it's a little bit legacy. 73 03:04.840 --> 03:09.220 We're talking about this being the five gigahertz side of things versus the 2.4 74 03:09.220 --> 03:09.960 gigahertz. 75 03:09.960 --> 03:14.240 And sometimes it just refers to it at 802.11a and so on and so forth. 76 03:14.240 --> 03:17.700 Although these are a lot of 802.11a settings, for example, we have the legacy 77 03:17.700 --> 03:18.440 data rate sitting 78 03:18.440 --> 03:22.080 over here, we can disable or enable it here. 79 03:22.080 --> 03:27.040 Meanwhile if I want to do something with our, our N or AC, I can come all the 80 03:27.040 --> 03:27.840 way down here 81 03:27.840 --> 03:28.920 to high throughput. 82 03:28.920 --> 03:34.500 And this is where we see an AC enablement, as well as all the individual MCS WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 82 03:28.920 --> 03:34.500 And this is where we see an AC enablement, as well as all the individual MCS 83 03:34.500 --> 03:35.440 indices. 84 03:35.440 --> 03:38.960 So that would be also true for BGN network. 85 03:38.960 --> 03:44.600 This is more of a BG concept, whereas high throughput here would be 802.11N, 86 03:44.600 --> 03:44.680 keeping 87 03:44.680 --> 03:50.720 in mind that 802.11AC didn't actually support the 2.4 gigahertz band. 88 03:50.720 --> 03:53.120 Furthermore, we can see that there's RRM here. 89 03:53.120 --> 03:55.560 So RRM is split up by band. 90 03:55.560 --> 03:58.680 So again, this is referring to the five gigahertz band. 91 03:58.680 --> 04:03.750 I can look at my RF grouping here is where we can set, again, whether we want WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 91 03:58.680 --> 04:03.750 I can look at my RF grouping here is where we can set, again, whether we want 92 04:03.750 --> 04:04.440 to elect 93 04:04.440 --> 04:08.690 a leader, if I want specific controllers to be the leader, I've got my transmit 94 04:08.690 --> 04:08.840 power 95 04:08.840 --> 04:13.520 control, my dynamic channel assignment options, which channels are eligible. 96 04:13.520 --> 04:17.350 I can change my coverage hold detection here or at least disable it, change the 97 04:17.350 --> 04:18.000 thresholds 98 04:18.000 --> 04:19.040 and so on and so forth. 99 04:19.040 --> 04:23.320 So we have all of the same options that we covered with iOS XE. 100 04:23.320 --> 04:27.160 And again, in AROS, a lot of them are going to be under wireless. 101 04:27.160 --> 04:29.880 Lastly, we do have the concept of the RF profile. 102 04:29.880 --> 04:32.120 Scroll up here, we see RF profiles. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 102 04:29.880 --> 04:32.120 Scroll up here, we see RF profiles. 103 04:32.120 --> 04:38.260 A lot of our iOS XE constructs didn't exist with AROS, but hey, RF profiles did 104 04:38.260 --> 04:38.360 . 105 04:38.360 --> 04:40.360 And it's basically the same thing. 106 04:40.360 --> 04:44.800 I can click new here, create a profile name CBTN. 107 04:44.800 --> 04:49.760 And I do have to decide whether this is a five gigahertz or 2.4 gigahertz 108 04:49.760 --> 04:50.640 policy. 109 04:50.640 --> 04:54.560 But when I click apply here, I can see that I can come over to RRM. 110 04:54.560 --> 04:56.800 I can change the thresholds. 111 04:56.800 --> 05:02.370 Just like with iOS XE, this is a way that I can override whether or not, or WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 111 04:56.800 --> 05:02.370 Just like with iOS XE, this is a way that I can override whether or not, or 112 05:02.370 --> 05:03.120 like the 113 05:03.120 --> 05:05.440 global RRM settings. 114 05:05.440 --> 05:09.240 So if I want specific access points to behave differently, then I can override 115 05:09.240 --> 05:09.800 them with 116 05:09.800 --> 05:13.960 an RF profile as it relates to radio resource management. 117 05:13.960 --> 05:16.360 So for example, I'm just going to click apply here. 118 05:16.360 --> 05:18.720 I've got my RF profile. 119 05:18.720 --> 05:24.640 Now I can go over to WLANs, look at my AP group, and then click on my group. 120 05:24.640 --> 05:26.280 And we see an RF profile tab here. 121 05:26.280 --> 05:31.240 I can simply select CBTN in the 802.11a drop down. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 121 05:26.280 --> 05:31.240 I can simply select CBTN in the 802.11a drop down. 122 05:31.240 --> 05:36.300 So again, just some things to cover as far as mobility groups and RF groups, RF 123 05:36.300 --> 05:37.040 profiles 124 05:37.040 --> 05:38.280 and so on and so forth. 125 05:38.280 --> 05:41.720 There's certainly some controller level configurations we should be aware of 126 05:41.720 --> 05:42.600 and how we go about 127 05:42.600 --> 05:44.200 doing that in AroS.