WEBVTT

1
00:00.000 --> 00:02.200
All right, it's time to have some fun.

2
00:02.200 --> 00:03.600
We're gonna get into the lab here

3
00:03.600 --> 00:07.520
and configure my 25.04 wireless lane controller.

4
00:07.520 --> 00:09.360
This is running aero S.

5
00:09.360 --> 00:14.440
And it's connected to my layer two lab network.

6
00:14.440 --> 00:17.760
And so I've got an access point here.

7
00:17.760 --> 00:19.400
It's not going to be the same access point

8
00:19.400 --> 00:20.800
I used to demo earlier.

9
00:20.800 --> 00:22.600
And the reason for that is because

10
00:22.600 --> 00:25.240
an aero S controller will find

11
00:25.240 --> 00:30.240
cannot run 802.11AX, which is known as Wi-Fi 6,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:25.240 --> 00:30.240
cannot run 802.11AX, which is known as Wi-Fi 6,

12
00:30.240 --> 00:34.040
nor can it run the six gigahertz space,

13
00:34.040 --> 00:38.800
which is the six E spec there that we have as well.

14
00:38.800 --> 00:41.800
So we can't run either one of these with aero S

15
00:41.800 --> 00:43.800
and that access point that I showed off

16
00:43.800 --> 00:46.160
was an 802.11AX access point.

17
00:46.160 --> 00:48.440
And so it was never added to aero S.

18
00:48.440 --> 00:51.400
Instead, what I have is I've got a,

19
00:51.400 --> 00:52.240
what is this again?

20
00:52.240 --> 00:56.000
This is a 35.02 internal antenna.

21
00:56.000 --> 00:59.320
So a 35.02 I cap wipe access point.

22
00:59.320 --> 01:02.960
So what we've got here is if we can see the,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:59.320 --> 01:02.960
So what we've got here is if we can see the,

23
01:02.960 --> 01:04.680
I guess so quickly it should go like that

24
01:04.680 --> 01:07.720
with the logo there, but it is alternating in colors.

25
01:07.720 --> 01:10.440
It's going from, well, it's hard to see on the video,

26
01:10.440 --> 01:11.800
especially with my green screen,

27
01:11.800 --> 01:13.880
blotting out the green LED,

28
01:13.880 --> 01:16.920
but essentially it's looking for a controller.

29
01:16.920 --> 01:21.840
The colors are going from green to red to amber.

30
01:22.240 --> 01:24.640
The green to red.

31
01:24.640 --> 01:28.360
And so what we're you need to do now is find out,

32
01:28.360 --> 01:30.640
what do we need to do to make this access point
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:28.360 --> 01:30.640
what do we need to do to make this access point

33
01:30.640 --> 01:32.320
connect to the controller?

34
01:32.320 --> 01:34.720
Because they're already in the same layer to network.

35
01:34.720 --> 01:37.680
I mean, the access point is sending broadcast messages out

36
01:37.680 --> 01:39.720
and the controller is receiving it

37
01:39.720 --> 01:41.480
and yet it's ignoring it.

38
01:41.480 --> 01:42.960
So what exactly is going on?

39
01:42.960 --> 01:44.520
Well, this is a very important part

40
01:44.520 --> 01:47.120
of our aero S controller configuration.

41
01:47.120 --> 01:49.920
Again, what we have here, if we use a dotted line

42
01:49.920 --> 01:53.080
to represent the fact that we've got a logical interface

43
01:53.080 --> 01:55.880
in here and this logical interface

44
01:55.880 --> 02:00.040
is going to be the management interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
01:55.880 --> 02:00.040
is going to be the management interface.

45
02:00.040 --> 02:04.360
The management interface is currently on my lab network.

46
02:04.360 --> 02:07.880
It's got the .14 IP address.

47
02:07.880 --> 02:11.280
And again, it is receiving those broadcasts.

48
02:11.280 --> 02:15.360
However, what we don't have is we have yet to check the box

49
02:15.360 --> 02:19.640
that allows for dynamic AP management.

50
02:20.200 --> 02:23.200
Until it's enabled for this,

51
02:23.200 --> 02:25.120
it's not going to allow access points

52
02:25.120 --> 02:27.320
to form cap web tunnels here.

53
02:27.320 --> 02:29.920
So we're going to have to go in here and check that box

54
02:29.920 --> 02:33.120
and make sure that we support access points.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
02:29.920 --> 02:33.120
and make sure that we support access points.

55
02:33.120 --> 02:36.960
So that'll be step number one is to go and check that box.

56
02:36.960 --> 02:39.560
Once that's up, we should see that the access point

57
02:39.560 --> 02:40.800
gets discovered.

58
02:40.800 --> 02:45.440
We're also going to go ahead and configure a dynamic interface

59
02:45.440 --> 02:49.160
which would be associated with a different VLAN ID.

60
02:49.160 --> 02:51.840
Now, I've got the management interface configured

61
02:51.840 --> 02:54.480
to use the native VLAN.

62
02:54.480 --> 02:59.560
And so actually in ARA-S, it refers to that as zero untagged.

63
02:59.560 --> 03:02.280
And as a result, in a production environment,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:59.560 --> 03:02.280
And as a result, in a production environment,

64
03:02.280 --> 03:05.400
as you can imagine, this is going to need to be a trunk link.

65
03:05.400 --> 03:08.560
And very likely, we would have multiple links

66
03:08.560 --> 03:10.800
all bundled together in production.

67
03:10.800 --> 03:14.680
So this becomes known as a lag, a link aggregation.

68
03:14.680 --> 03:17.040
And that would again be what we'd expect to see

69
03:17.040 --> 03:20.280
in production, but in my lab environment, I don't have that.

70
03:20.280 --> 03:22.760
I just have a single link to keep things simple.

71
03:22.760 --> 03:26.240
And also because my upstream switch is just a home switch

72
03:26.240 --> 03:28.600
and doesn't actually support port channels.

73
03:28.600 --> 03:30.680
But if we wanted to configure a port channel,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
03:28.600 --> 03:30.680
But if we wanted to configure a port channel,

74
03:30.680 --> 03:33.080
we could configure a static port channel there

75
03:33.080 --> 03:35.520
using a Cisco switch.

76
03:35.520 --> 03:37.400
Now, the last thing we'll do in this video

77
03:37.400 --> 03:43.240
is take this access point and add it into an AP group.

78
03:43.240 --> 03:46.760
And so we're going to go and create an access point group

79
03:46.760 --> 03:49.720
and we'll add the AP into that group.

80
03:49.720 --> 03:51.480
Now notice by the end of this video,

81
03:51.480 --> 03:53.840
we will not have configured an SSID.

82
03:53.840 --> 03:56.520
There's no broadcasting of signals yet.

83
03:56.520 --> 03:58.960
We haven't configured a WLAN yet.

84
03:58.960 --> 04:00.840
So we've got to get all of this knocked out
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:58.960 --> 04:00.840
So we've got to get all of this knocked out

85
04:00.840 --> 04:04.600
before we can even start to configure our SSIDs and WLANs,

86
04:04.600 --> 04:07.880
which will come up in the next video.

87
04:07.880 --> 04:10.720
So once again, let's flip over to the controllers

88
04:10.720 --> 04:12.520
graphical user interface.

89
04:12.520 --> 04:15.280
And we're going to start off by going and taking a look

90
04:15.280 --> 04:16.200
at those interfaces.

91
04:16.200 --> 04:17.960
I'm going to come over to the controller

92
04:17.960 --> 04:19.880
and then the interface is on the left.

93
04:19.880 --> 04:23.360
And we see that it comes with a management and virtual interface,

94
04:23.360 --> 04:26.160
which have IP addresses that were given to it

95
04:26.160 --> 04:29.080
by the admin during initial setup.

96
04:29.080 --> 04:32.040
In other words, me at that point.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
04:29.080 --> 04:32.040
In other words, me at that point.

97
04:32.040 --> 04:34.200
Now, again, we mentioned that we're not covering

98
04:34.200 --> 04:37.240
all of the interfaces because that's prerequisite knowledge.

99
04:37.240 --> 04:40.160
But we should remember that there's a virtual interface.

100
04:40.160 --> 04:44.400
And usually we're going to give it the 192.0.2.1 address.

101
04:44.400 --> 04:47.480
Once upon a time, Cisco recommended 1.1.1.1 here

102
04:47.480 --> 04:53.120
because that was a very easy IP address that was not in use.

103
04:53.120 --> 04:54.200
Well, go figure.

104
04:54.200 --> 04:55.080
Now it's in use.

105
04:55.080 --> 04:59.120
It's a DNS server that's available on the public internet.

106
04:59.120 --> 05:01.400
And so Cisco changed the recommendation to say,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

106
04:59.120 --> 05:01.400
And so Cisco changed the recommendation to say,

107
05:01.400 --> 05:03.520
you know, we should probably never have used a public IP

108
05:03.520 --> 05:04.200
address.

109
05:04.200 --> 05:06.640
Let's use a range that was actually set aside

110
05:06.640 --> 05:08.600
and dedicated for lab purposes.

111
05:08.600 --> 05:13.960
And so 192.0.2 as a slash 24 was set aside for that reason.

112
05:13.960 --> 05:15.680
And so we can use the .1 address there.

113
05:15.680 --> 05:18.840
And that should be an IP address that is not used anywhere else

114
05:18.840 --> 05:21.440
in our local network or on the internet.

115
05:21.440 --> 05:24.280
So that's what we want to place on the virtual IP address.

116
05:24.280 --> 05:26.800
And that would be the same IP address

117
05:26.800 --> 05:28.880
on all of our wireless LAN controllers.

118
05:28.880 --> 05:31.840
It's not something we need to worry about duplicating
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
05:28.880 --> 05:31.840
It's not something we need to worry about duplicating

119
05:31.840 --> 05:32.640
or anything like that.

120
05:32.640 --> 05:36.160
We will duplicate that IP address among all of our controllers.

121
05:36.160 --> 05:40.120
So that's a very brief touching on the virtual interface.

122
05:40.120 --> 05:41.800
Let's focus on the management interface.

123
05:41.800 --> 05:45.240
So once again, this is using the untagged VLAN.

124
05:45.240 --> 05:48.800
So we don't actually define what that VLAN is

125
05:48.800 --> 05:50.680
because it's irrelevant to the controller.

126
05:50.680 --> 05:53.640
It just knows that it's not going to tag it.

127
05:53.640 --> 05:57.000
So this has to match up with whatever the native VLAN is

128
05:57.000 --> 05:59.040
on the upstream switch.

129
05:59.040 --> 06:01.520
But if I click on this, we'll see some configuration
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

129
05:59.040 --> 06:01.520
But if I click on this, we'll see some configuration

130
06:01.520 --> 06:02.320
information.

131
06:02.320 --> 06:05.400
Again, 0 here means that we're not tagging it.

132
06:05.400 --> 06:08.240
I've got the IP address here as well as the gateway.

133
06:08.240 --> 06:11.080
I can tell it which port number and backup port to use.

134
06:11.080 --> 06:13.600
So again, I'm only using a single interface.

135
06:13.600 --> 06:16.360
So I said use port number one, backup port number two.

136
06:16.360 --> 06:19.680
And if we're using lag, then we don't need to worry about this

137
06:19.680 --> 06:22.040
because we have one logical port.

138
06:22.040 --> 06:26.560
And it's going to automatically handle physical failovers for us.

139
06:26.560 --> 06:28.280
Here's the big thing we need to worry about.

140
06:28.280 --> 06:31.360
Enable Dynamic AP Management.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

140
06:28.280 --> 06:31.360
Enable Dynamic AP Management.

141
06:31.360 --> 06:33.400
Like I said, this is unchecked.

142
06:33.400 --> 06:37.840
And I'm going to check this and then come up here and apply.

143
06:37.840 --> 06:42.160
This should make it so that this address is discoverable now

144
06:42.160 --> 06:43.840
by access points.

145
06:43.840 --> 06:45.240
So I'm going to say OK.

146
06:45.240 --> 06:47.600
And yes, it's going to cause a little bit of a reset

147
06:47.600 --> 06:48.720
for existing networks.

148
06:48.720 --> 06:50.600
We don't need to worry too much about that

149
06:50.600 --> 06:54.320
because we are bringing in that work up fresh.

150
06:54.320 --> 06:57.400
So I'm going to come back over to the Monitor tab,

151
06:57.400 --> 06:59.680
click on Access Points over here.

152
06:59.680 --> 07:01.240
And we'll go take a look at radio.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

152
06:59.680 --> 07:01.240
And we'll go take a look at radio.

153
07:01.240 --> 07:02.800
So we're expecting--

154
07:02.800 --> 07:04.080
I can click on either one of these

155
07:04.080 --> 07:07.400
because this is a dual band radio or access point.

156
07:07.400 --> 07:11.760
But we are expecting that the radios should start to show up.

157
07:11.760 --> 07:14.080
I'm looking over here at my access point.

158
07:14.080 --> 07:16.640
And we do see now it-- well, again,

159
07:16.640 --> 07:18.720
because of the green screen, can't really see it

160
07:18.720 --> 07:20.640
because it's just see-through there.

161
07:20.640 --> 07:23.200
But there's a green LED.

162
07:23.200 --> 07:26.040
And so the green LED means that it

163
07:26.040 --> 07:28.120
has associated with the controller.

164
07:28.120 --> 07:29.640
So give it a few moments here.

165
07:29.640 --> 07:33.600
And hopefully, our controller will sync up pretty up.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

165
07:29.640 --> 07:33.600
And hopefully, our controller will sync up pretty up.

166
07:33.600 --> 07:34.280
It's already there.

167
07:34.280 --> 07:34.800
Look at that.

168
07:34.800 --> 07:36.520
Didn't even have to pause the video.

169
07:36.520 --> 07:39.080
So we do see that we've got one up here, one up here.

170
07:39.080 --> 07:41.880
If I click over here now, we do see that it's there.

171
07:41.880 --> 07:45.400
So a little bit of this legacy interface issue

172
07:45.400 --> 07:47.120
doesn't automatically refresh.

173
07:47.120 --> 07:49.640
And so we just have to click around until things

174
07:49.640 --> 07:50.720
start to show up.

175
07:50.720 --> 07:54.120
But we do see that I've got, again, a dual radio access

176
07:54.120 --> 07:54.880
point.

177
07:54.880 --> 07:59.640
So it's got a 5 gigahertz radio that supports 802.11AN and AC

178
07:59.640 --> 08:02.280
and a 2.4, which is BG and N.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

178
07:59.640 --> 08:02.280
and a 2.4, which is BG and N.

179
08:02.280 --> 08:06.960
So from here, we can start to do some more configurations.

180
08:06.960 --> 08:09.280
Now, even though we're not going to use it in the lab demo,

181
08:09.280 --> 08:12.080
I do want to demonstrate creating a dynamic interface.

182
08:12.080 --> 08:15.280
So we go to controller, interfaces, and look over here,

183
08:15.280 --> 08:16.760
I can just click new.

184
08:16.760 --> 08:19.000
Let's create a new interface.

185
08:19.000 --> 08:22.800
So let's just call this test for the sake of something

186
08:22.800 --> 08:23.720
we're not going to use.

187
08:23.720 --> 08:26.720
And we see I can associate a VLAN ID here.

188
08:26.720 --> 08:29.000
And this is going to have to be something unique relative

189
08:29.000 --> 08:29.640
to the controller.

190
08:29.640 --> 08:32.840
I can't create multiple interfaces with the same VLAN ID.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

190
08:29.640 --> 08:32.840
I can't create multiple interfaces with the same VLAN ID.

191
08:32.840 --> 08:34.960
So let's just say this is VLAN 10.

192
08:34.960 --> 08:36.040
So we're going to click apply.

193
08:36.040 --> 08:37.960
And now we see a lot of the same information that's

194
08:37.960 --> 08:39.320
on that management interface.

195
08:39.320 --> 08:43.480
So I can set the port number and the backup port number.

196
08:43.480 --> 08:47.040
So which of these interfaces will this--

197
08:47.040 --> 08:49.160
well, again, think of it almost like an SVI.

198
08:49.160 --> 08:50.920
It's a logical interface.

199
08:50.920 --> 08:52.600
And it's getting mapped to a port.

200
08:52.600 --> 08:55.800
One interesting thing about AROS is they are always

201
08:55.800 --> 08:58.400
very consistent about the use of the words interface

202
08:58.400 --> 08:59.240
and port.

203
08:59.240 --> 09:01.760
Cisco can sometimes go back and forth on this.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

203
08:59.240 --> 09:01.760
Cisco can sometimes go back and forth on this.

204
09:01.760 --> 09:05.120
But with the wireless LAN controller with AROS,

205
09:05.120 --> 09:09.320
interface means a logical point.

206
09:09.320 --> 09:11.120
And a port is physical.

207
09:11.120 --> 09:13.160
So interface logical, port physical.

208
09:13.160 --> 09:15.680
If I see port, it's talking about a physical port

209
09:15.680 --> 09:17.400
on the wireless LAN controller.

210
09:17.400 --> 09:18.720
If we're talking about an interface,

211
09:18.720 --> 09:21.840
it's logical, again, thinking like an SVI.

212
09:21.840 --> 09:23.480
So either way, we see that I could

213
09:23.480 --> 09:25.080
enable dynamic AP management.

214
09:25.080 --> 09:27.120
I don't have to do this, by the way.

215
09:27.120 --> 09:30.280
I can still map this interface to SSID's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

215
09:27.120 --> 09:30.280
I can still map this interface to SSID's

216
09:30.280 --> 09:33.320
for the sake of mapping them to VLAN 10 in this case.

217
09:33.320 --> 09:36.240
But if I do want them to be able to form capwap tunnels,

218
09:36.240 --> 09:37.920
then I can enable this.

219
09:37.920 --> 09:39.960
And there are limits to how many capwap tunnels

220
09:39.960 --> 09:41.560
can form on each interface.

221
09:41.560 --> 09:43.280
And so I might need to load balance this

222
09:43.280 --> 09:44.840
in a real world network.

223
09:44.840 --> 09:47.480
From here, I could enter some kind of dummy IP address

224
09:47.480 --> 09:50.320
for my lab environment, like 10.0.10.

225
09:50.320 --> 09:53.480
And then we'll just say the .2 interface.

226
09:53.480 --> 09:56.160
So NetMask, actually, that would be a slash 24.

227
09:56.160 --> 09:59.000
And then the gateway could be 10.1.

228
09:59.000 --> 10:01.120
So now, when I click Apply, we're going to find
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

228
09:59.000 --> 10:01.120
So now, when I click Apply, we're going to find

229
10:01.120 --> 10:03.360
that there are some normal warnings here about,

230
10:03.360 --> 10:05.200
and it's going to cause some issues.

231
10:05.200 --> 10:08.560
But we're also going to find that it's going to fail to add.

232
10:08.560 --> 10:12.000
The reason for that is because we can only actually apply

233
10:12.000 --> 10:16.840
one of these dynamic AP manager interfaces

234
10:16.840 --> 10:18.320
per physical port.

235
10:18.320 --> 10:20.000
Now with a lag, this looks a little different.

236
10:20.000 --> 10:22.480
But with physical ports like this,

237
10:22.480 --> 10:23.880
we can't actually apply this.

238
10:23.880 --> 10:26.000
So I'm going to go and enter all of the information

239
10:26.000 --> 10:27.000
in again.

240
10:27.000 --> 10:31.040
And at this point, I'm going to leave the dynamic AP manager
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

240
10:27.000 --> 10:31.040
And at this point, I'm going to leave the dynamic AP manager

241
10:31.040 --> 10:32.320
option off.

242
10:32.320 --> 10:34.600
And that's going to make sure that I can, in fact,

243
10:34.600 --> 10:37.080
save this dynamic interface to the same port

244
10:37.080 --> 10:39.160
as my management interface.

245
10:39.160 --> 10:40.200
OK, cool.

246
10:40.200 --> 10:42.520
So we go back to the interfaces.

247
10:42.520 --> 10:45.520
And we do see that this test interface shows up

248
10:45.520 --> 10:46.920
as VLAN10.

249
10:46.920 --> 10:50.240
With this IP address, it calls it a dynamic interface here.

250
10:50.240 --> 10:54.000
And we left dynamic AP management disabled.

251
10:54.000 --> 10:56.000
So this is very useful information.

252
10:56.000 --> 10:58.720
And as I keep saying, in a production environment,

253
10:58.720 --> 10:59.760
things will look different.

254
10:59.760 --> 11:02.160
For example, we would expect to see
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

254
10:59.760 --> 11:02.160
For example, we would expect to see

255
11:02.160 --> 11:05.560
many different dynamic interfaces listed here.

256
11:05.560 --> 11:07.480
We need one for every single VLAN

257
11:07.480 --> 11:10.960
that we're using on our SSIDs.

258
11:10.960 --> 11:12.600
So the last thing we said we're going to do

259
11:12.600 --> 11:15.200
is to go take a look at our access points.

260
11:15.200 --> 11:18.360
So once again, I've got this access point down here.

261
11:18.360 --> 11:20.200
If I go over to Wireless, I can actually

262
11:20.200 --> 11:22.120
see more details on the access point.

263
11:22.120 --> 11:25.000
It actually defaults to this all APs option.

264
11:25.000 --> 11:27.520
And I can see the 3502i listed here.

265
11:27.520 --> 11:28.800
So I can click on it.

266
11:28.800 --> 11:30.440
I can see the name.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

266
11:28.800 --> 11:30.440
I can see the name.

267
11:30.440 --> 11:32.480
I could actually name it if I wanted to.

268
11:32.480 --> 11:34.720
And a network with dozens or hundreds of APs.

269
11:34.720 --> 11:38.200
I probably don't want to name every single one.

270
11:38.200 --> 11:39.480
Yeah.

271
11:39.480 --> 11:40.720
Reminds me of playing Pokemon.

272
11:40.720 --> 11:42.560
I don't want to name all of my Pokemon.

273
11:42.560 --> 11:44.240
I just want to name the special ones.

274
11:44.240 --> 11:47.040
So same thing with the access points, I suppose.

275
11:47.040 --> 11:48.760
Maybe that is neither here nor there.

276
11:48.760 --> 11:53.200
But either way, if I go over to some of these different options,

277
11:53.200 --> 11:55.920
we can see that we can do individual configurations,

278
11:55.920 --> 11:58.480
such as whether we're supporting CDP,

279
11:58.480 --> 12:01.680
the list of controllers, primary, secondary, and tertiary.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

279
11:58.480 --> 12:01.680
the list of controllers, primary, secondary, and tertiary.

280
12:01.680 --> 12:05.400
If I want to override that, I can see critical information,

281
12:05.400 --> 12:08.280
like the product ID and the serial number and all

282
12:08.280 --> 12:09.360
of these things.

283
12:09.360 --> 12:13.040
And so lots of information just by clicking on the AP.

284
12:13.040 --> 12:14.720
Now, the last goal that we had was

285
12:14.720 --> 12:18.040
to add this access point into the AP group that we created.

286
12:18.040 --> 12:22.120
And we can do that by going over here to the Advanced tab.

287
12:22.120 --> 12:25.080
And this AP group name is a dropdown,

288
12:25.080 --> 12:27.680
and I can select CBTN group.

289
12:27.680 --> 12:30.320
So this is how I apply it to the group.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

289
12:27.680 --> 12:30.320
So this is how I apply it to the group.

290
12:30.320 --> 12:33.160
I can click Apply here and say, OK.

291
12:33.160 --> 12:36.880
And now this is going to be part of that AP group.

292
12:36.880 --> 12:39.000
So this is something we're going to want

293
12:39.000 --> 12:40.840
to make sure that we do intentionally.

294
12:40.840 --> 12:43.760
We're setting our access points into the appropriate group

295
12:43.760 --> 12:47.760
based on their location that they're being deployed into

296
12:47.760 --> 12:50.320
in the network.