WEBVTT

1
00:00.000 --> 00:05.840
So, now we have our AP connected and we also have our global configurations in

2
00:05.840 --> 00:06.280
place.

3
00:06.280 --> 00:08.160
So the question is what's next?

4
00:08.160 --> 00:10.960
What do we have to do to get our wireless networks online because my access

5
00:10.960 --> 00:11.600
point sitting

6
00:11.600 --> 00:15.000
right here still isn't broadcasting any SSID's?

7
00:15.000 --> 00:21.180
Well, this configuration that Cisco has put together for us on the 9800s via

8
00:21.180 --> 00:22.080
iOSXE is

9
00:22.080 --> 00:26.600
a little bit of a system that we have to study and understand how it all comes

10
00:26.600 --> 00:27.520
together.

11
00:27.520 --> 00:32.500
There's a lot of modular components that bring the configuration together in a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:27.520 --> 00:32.500
There's a lot of modular components that bring the configuration together in a

12
00:32.500 --> 00:33.440
way that we

13
00:33.440 --> 00:36.280
didn't have with the old iOS system.

14
00:36.280 --> 00:40.740
And so we do need to document this out and diagram this because, again, there's

15
00:40.740 --> 00:41.080
a lot

16
00:41.080 --> 00:42.800
of modular components.

17
00:42.800 --> 00:46.730
And if we have a good map that we can have as a reference, then we can very

18
00:46.730 --> 00:47.360
easily get

19
00:47.360 --> 00:51.120
into the configuration and start making changes because we might think, hey, I

20
00:51.120 --> 00:51.800
just want to

21
00:51.800 --> 00:56.410
create a WLAN, which is how Cisco is always defined as SSID's, and apply it to

22
00:56.410 --> 00:56.960
a bunch

23
00:56.960 --> 00:58.560
of access points.

24
00:58.560 --> 00:59.800
And that sounds great.

25
00:59.800 --> 01:04.850
It certainly would get us started on getting wireless networks advertised and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
00:59.800 --> 01:04.850
It certainly would get us started on getting wireless networks advertised and

26
01:04.850 --> 01:05.600
broadcast

27
01:05.600 --> 01:09.880
from our APs, but it's not going to be quite that simple.

28
01:09.880 --> 01:14.630
But what we'll find just for consistency's sake is that what Cisco is really

29
01:14.630 --> 01:15.320
focusing

30
01:15.320 --> 01:19.040
in on is the AP configuration.

31
01:19.040 --> 01:23.840
What we want to do is we want to bring in a bunch of information that lands on

32
01:23.840 --> 01:24.640
the access

33
01:24.640 --> 01:28.680
point and gives us the wireless network that we're looking for.

34
01:28.680 --> 01:32.030
But in order to do that, rather than going around and individually configuring
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:28.680 --> 01:32.030
But in order to do that, rather than going around and individually configuring

35
01:32.030 --> 01:32.360
access

36
01:32.360 --> 01:36.780
points or trying to manage groups of access points and apply policies here and

37
01:36.780 --> 01:37.000
there,

38
01:37.000 --> 01:41.250
instead, we're going to have this modular policy that scales a whole lot better

39
01:41.250 --> 01:42.000
to enterprise

40
01:42.000 --> 01:43.520
level networks.

41
01:43.520 --> 01:47.560
So this AP configuration's at the heart of our new architecture that we're

42
01:47.560 --> 01:48.160
building

43
01:48.160 --> 01:49.160
out here.

44
01:49.160 --> 01:53.120
But again, we're not just going to get onto APs and start configuring things.

45
01:53.120 --> 01:58.160
Instead, we're going to find that there are three primary constructs that we're

46
01:58.160 --> 01:58.600
going

47
01:58.600 --> 02:03.400
to configure in order to bring the config together.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
01:58.600 --> 02:03.400
to configure in order to bring the config together.

48
02:03.400 --> 02:06.440
And these are known as tags.

49
02:06.440 --> 02:11.290
So there's three different tags that are going to feed into our AP

50
02:11.290 --> 02:12.640
configurations.

51
02:12.640 --> 02:22.200
And those three tags are known as a site tag, an RF tag, and a policy tag.

52
02:22.200 --> 02:27.060
So if we have any takeaway from this, it's to know that there's these three

53
02:27.060 --> 02:27.680
tags.

54
02:27.680 --> 02:31.880
And when we create these three tags and apply them to our access points, that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
02:27.680 --> 02:31.880
And when we create these three tags and apply them to our access points, that

55
02:31.880 --> 02:32.480
it really

56
02:32.480 --> 02:34.880
brings all of the configuration together.

57
02:34.880 --> 02:39.230
And from there, it's just a matter of knowing which tag is responsible for

58
02:39.230 --> 02:40.800
which configuration.

59
02:40.800 --> 02:43.160
Let's start over here with the policy tag.

60
02:43.160 --> 02:48.760
Policy tags are going to be where we apply our wireless lands or our W lands.

61
02:48.760 --> 02:54.870
Once again, the W lands are how we configure our SSIDs and get those mapped

62
02:54.870 --> 02:55.680
into the wireless

63
02:55.680 --> 02:56.680
space.

64
02:56.680 --> 02:59.040
So remember, an SSID is that network name.

65
02:59.040 --> 03:04.390
When I go to a place of a place of work or a cafe or something, I want to log
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
02:59.040 --> 03:04.390
When I go to a place of a place of work or a cafe or something, I want to log

66
03:04.390 --> 03:04.960
in.

67
03:04.960 --> 03:06.640
I see a wireless network.

68
03:06.640 --> 03:09.320
That's an SSID that's being broadcast.

69
03:09.320 --> 03:14.090
Cisco created the concept of the W land to include SSIDs plus all of the

70
03:14.090 --> 03:15.320
configurations

71
03:15.320 --> 03:18.680
that get associated with our SSIDs.

72
03:18.680 --> 03:21.440
This is going to include security.

73
03:21.440 --> 03:25.260
And so more or less, what we're saying here is it's not just a matter of

74
03:25.260 --> 03:26.280
creating a network

75
03:26.280 --> 03:30.440
name because even though that's important, if I could show up at CBT now gets
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
03:26.280 --> 03:30.440
name because even though that's important, if I could show up at CBT now gets

76
03:30.440 --> 03:31.560
headquarters,

77
03:31.560 --> 03:35.430
maybe we have a wireless network that's called CBTN and we know what we're

78
03:35.430 --> 03:36.640
associating ourselves

79
03:36.640 --> 03:37.640
with.

80
03:37.640 --> 03:41.230
So the name is important, but more importantly, it would be all the

81
03:41.230 --> 03:42.880
configuration and security

82
03:42.880 --> 03:43.920
settings.

83
03:43.920 --> 03:49.840
And that is what all comes into the concept of the W land.

84
03:49.840 --> 03:54.640
Now in iOS XC, we're actually going to find that these are known as W land

85
03:54.640 --> 03:55.680
profiles when

86
03:55.680 --> 03:57.600
we configure them.

87
03:57.600 --> 04:03.720
And these W land profiles are going to get mapped inside of our policy tags.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
03:57.600 --> 04:03.720
And these W land profiles are going to get mapped inside of our policy tags.

88
04:03.720 --> 04:07.910
So I'm going to create a W land and I'm going to place it inside the policy tag

89
04:07.910 --> 04:08.240
.

90
04:08.240 --> 04:10.160
Now what if I want multiple W lands?

91
04:10.160 --> 04:13.880
What if I have two or three SSIDs that I want to advertise?

92
04:13.880 --> 04:18.490
Which one of those is going to require being mapped into the policy tag that

93
04:18.490 --> 04:19.320
inevitably

94
04:19.320 --> 04:21.440
gets placed onto our access points.

95
04:21.440 --> 04:26.760
But we do start to see now how, yeah, I create all of this information to

96
04:26.760 --> 04:27.840
create a network

97
04:27.840 --> 04:31.080
name and an SSID and all of its configuration.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

97
04:27.840 --> 04:31.080
name and an SSID and all of its configuration.

98
04:31.080 --> 04:35.160
Well now I see modularly how I'm kind of applying these different W lands and

99
04:35.160 --> 04:35.800
how those

100
04:35.800 --> 04:41.320
ultimately end up on my access point as it gets there via the policy tag.

101
04:41.320 --> 04:44.640
However, we're not quite done with the policy tag.

102
04:44.640 --> 04:49.080
We also have to create a policy profile.

103
04:49.080 --> 04:52.680
So we must we'll get used to the concept of tags and profiles.

104
04:52.680 --> 04:56.930
Again the tags, the three tags are the ones that directly get referenced by our

105
04:56.930 --> 04:57.920
configuration.

106
04:57.920 --> 05:02.970
The profiles are going to be how we define configuration oftentimes within a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

106
04:57.920 --> 05:02.970
The profiles are going to be how we define configuration oftentimes within a

107
05:02.970 --> 05:03.600
tag like

108
05:03.600 --> 05:05.000
the W land profile.

109
05:05.000 --> 05:07.120
Now like the policy profile.

110
05:07.120 --> 05:10.440
That's how Cisco architected this.

111
05:10.440 --> 05:15.320
Policy profiles are where we're going to perform the other side of our W land

112
05:15.320 --> 05:17.120
configuration.

113
05:17.120 --> 05:21.100
Specifically we need to map our SSIDs to a specific V land and that's going to

114
05:21.100 --> 05:21.560
be part

115
05:21.560 --> 05:23.640
of a policy profile.

116
05:23.640 --> 05:29.320
And so we're also going to see that I can map quality of service configurations

117
05:29.320 --> 05:29.320
here

118
05:29.320 --> 05:33.480
as well as any kind of anchoring config.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
05:29.320 --> 05:33.480
as well as any kind of anchoring config.

119
05:33.480 --> 05:39.090
So this is going to go into a policy profile and then I get to map the policy

120
05:39.090 --> 05:39.920
profile to

121
05:39.920 --> 05:42.840
a W land here inside the policy tag.

122
05:42.840 --> 05:48.860
So maybe I map policy profile one to W land one here and then policy profile

123
05:48.860 --> 05:49.840
two to W

124
05:49.840 --> 05:51.440
land two.

125
05:51.440 --> 05:55.180
But the reason we're doing it this way is because maybe I just still want to

126
05:55.180 --> 05:55.840
use policy

127
05:55.840 --> 06:00.120
profile one to map to wireless land three.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

127
05:55.840 --> 06:00.120
profile one to map to wireless land three.

128
06:00.120 --> 06:02.960
And so we see that this is again a modular concept.

129
06:02.960 --> 06:08.110
I can have multiple policy profiles that get mapped to different W lands and

130
06:08.110 --> 06:09.080
potentially

131
06:09.080 --> 06:10.960
in an overlapping fashion.

132
06:10.960 --> 06:14.000
This is why Cisco's creating this the way they are.

133
06:14.000 --> 06:19.380
So again as we apply this policy tag to access points what we're really

134
06:19.380 --> 06:22.000
bringing is SSIDs

135
06:22.000 --> 06:26.150
and all of their configurations and all of their security settings mapped to V

136
06:26.150 --> 06:26.600
land and

137
06:26.600 --> 06:30.280
quality of service and anchoring configurations as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

137
06:26.600 --> 06:30.280
quality of service and anchoring configurations as well.

138
06:30.280 --> 06:33.840
So all of that gets defined by the policy tag.

139
06:33.840 --> 06:39.720
Now that is the vast majority of our configuration from a policy perspective.

140
06:39.720 --> 06:44.170
That's why Cisco calls it that if we want to talk about how we should attach to

141
06:44.170 --> 06:44.360
the

142
06:44.360 --> 06:48.040
network and the names and all these things that would be all part of the policy

143
06:48.040 --> 06:48.480
tag.

144
06:48.480 --> 06:50.920
But we do still have two other tags to talk about.

145
06:50.920 --> 06:53.000
Let's talk about the site tag next.

146
06:53.000 --> 06:58.510
The site tag is going to hold configurations that should apply to the entire

147
06:58.510 --> 06:59.240
site.

148
06:59.240 --> 07:02.270
So when I bring an access point online it's going to belong to a site and it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

148
06:59.240 --> 07:02.270
So when I bring an access point online it's going to belong to a site and it

149
07:02.270 --> 07:03.160
will be given

150
07:03.160 --> 07:08.560
the same site tag that all of the other access points at that location are

151
07:08.560 --> 07:08.880
given.

152
07:08.880 --> 07:14.860
There are two primary configurations specifically two primary profiles that get

153
07:14.860 --> 07:15.760
mapped through

154
07:15.760 --> 07:17.080
the site tag.

155
07:17.080 --> 07:26.310
We have the AP join profile and if we're going to run a site in FlexConnect

156
07:26.310 --> 07:27.320
then we also have

157
07:27.320 --> 07:30.720
the flex profile.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
07:27.320 --> 07:30.720
the flex profile.

158
07:30.720 --> 07:35.460
As we've mentioned if we're going to run FlexConnect, FlexConnect should be

159
07:35.460 --> 07:35.760
deployed

160
07:35.760 --> 07:37.320
on a site basis.

161
07:37.320 --> 07:42.460
Not just a few access points but all of the APs at a site should be running in

162
07:42.460 --> 07:43.480
FlexConnect

163
07:43.480 --> 07:45.360
if we're going to convert them.

164
07:45.360 --> 07:49.630
And so that makes sense to include it as part of a site tag where all the APs

165
07:49.630 --> 07:50.560
at a site

166
07:50.560 --> 07:53.000
have the exact same tag.

167
07:53.000 --> 07:58.080
Now the AP join profile is all about wireless land controller attachment.

168
07:58.080 --> 08:01.510
And I know we just spent a bunch of time attaching our access point to this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

168
07:58.080 --> 08:01.510
And I know we just spent a bunch of time attaching our access point to this

169
08:01.510 --> 08:02.080
wireless

170
08:02.080 --> 08:03.280
land controller.

171
08:03.280 --> 08:06.000
But there's more to it than simply attachment.

172
08:06.000 --> 08:10.600
We also have to worry about the configuration of backup controllers.

173
08:10.600 --> 08:14.320
Which controller should I fail over to if my primary goes down?

174
08:14.320 --> 08:18.600
And as part of that how am I going to handle failback?

175
08:18.600 --> 08:21.900
Because if we have two controllers and I have a bunch of access points

176
08:21.900 --> 08:22.960
associated with

177
08:22.960 --> 08:26.660
this controller and it goes down, well sure they could fail over but then if

178
08:26.660 --> 08:27.560
this controller

179
08:27.560 --> 08:30.640
comes back up, should I immediately fail back?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

179
08:27.560 --> 08:30.640
comes back up, should I immediately fail back?

180
08:30.640 --> 08:33.950
Should I wait a while because maybe that controller isn't stable and it's going

181
08:33.950 --> 08:35.960
to keep reloading.

182
08:35.960 --> 08:39.310
Especially if there's a network related issue that's actually causing me to not

183
08:39.310 --> 08:39.720
be able

184
08:39.720 --> 08:41.000
to reach it.

185
08:41.000 --> 08:44.200
And so these configurations are going to be part of the join profile again

186
08:44.200 --> 08:44.840
anything that

187
08:44.840 --> 08:50.100
has to do with how the access point handles its connections to wireless land

188
08:50.100 --> 08:51.640
controllers.

189
08:51.640 --> 08:55.720
Now as mentioned Flex Profile, this is going to be all about FlexConnect.

190
08:55.720 --> 09:00.060
It's going to define for example how exactly we configure the access points to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

190
08:55.720 --> 09:00.060
It's going to define for example how exactly we configure the access points to

191
09:00.060 --> 09:00.640
operate

192
09:00.640 --> 09:02.200
in FlexConnect mode.

193
09:02.200 --> 09:04.320
There's a whole lot to consider there.

194
09:04.320 --> 09:09.160
And furthermore within the site tag down here, we're going to have a check box

195
09:09.160 --> 09:09.880
that defines

196
09:09.880 --> 09:11.760
whether or not it's a local site.

197
09:11.760 --> 09:16.160
So it says enable local site.

198
09:16.160 --> 09:19.640
And this is going to be enabled by default.

199
09:19.640 --> 09:20.720
So it'll be checked.

200
09:20.720 --> 09:23.760
So again remember local mode is the opposite of FlexConnect mode.

201
09:23.760 --> 09:27.000
If it's a local site, then we're not running FlexConnect.

202
09:27.000 --> 09:32.360
So if I want to run FlexConnect, I would need to make sure that I uncheck this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

202
09:27.000 --> 09:32.360
So if I want to run FlexConnect, I would need to make sure that I uncheck this

203
09:32.360 --> 09:33.600
box and then

204
09:33.600 --> 09:38.420
my Flex Profile configuration will be applied such that all of my access points

205
09:38.420 --> 09:39.280
at the site

206
09:39.280 --> 09:42.360
are running in FlexConnect operation.

207
09:42.360 --> 09:44.200
Now lastly we have the RF tag.

208
09:44.200 --> 09:49.000
And as the name implies, this is going to be all about RF configuration.

209
09:49.000 --> 09:55.000
Now I know we've got our wireless LAN controller configured with global

210
09:55.000 --> 09:56.000
configurations for

211
09:56.000 --> 09:58.360
radio resource management.

212
09:58.360 --> 10:03.790
And this will be pushed automatically to access points that we don't do
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

212
09:58.360 --> 10:03.790
And this will be pushed automatically to access points that we don't do

213
10:03.790 --> 10:05.320
something otherwise

214
10:05.320 --> 10:06.320
with.

215
10:06.320 --> 10:10.280
But an RF tag actually allows us to override this.

216
10:10.280 --> 10:17.090
And so what I can do with an RF profile, which by the way, yes we have RF

217
10:17.090 --> 10:18.160
profiles

218
10:18.160 --> 10:22.850
that associate to the RF tag, just like with all of these other tags, they have

219
10:22.850 --> 10:23.520
profiles

220
10:23.520 --> 10:24.620
behind them.

221
10:24.620 --> 10:30.690
So this RF profile now is going to allow me to configure local R radio resource
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

221
10:24.620 --> 10:30.690
So this RF profile now is going to allow me to configure local R radio resource

222
10:30.690 --> 10:32.320
management

223
10:32.320 --> 10:34.640
RRM policies.

224
10:34.640 --> 10:39.800
So I can change configurations on the RF profile.

225
10:39.800 --> 10:43.360
And by the way, I can have one profile per band.

226
10:43.360 --> 10:46.720
So I can have this be my 2.4 GHz profile.

227
10:46.720 --> 10:48.720
I can create a 5 profile.

228
10:48.720 --> 10:51.680
I can create a 6 GHz profile.

229
10:51.680 --> 10:54.320
And I can set that to the RF tag.

230
10:54.320 --> 10:57.670
So if for example, I have a bunch of access points and I don't want them to run

231
10:57.670 --> 10:58.280
a specific

232
10:58.280 --> 11:04.000
channel, well I'd want to create a specific dynamic channel assignment or DCA
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

232
10:58.280 --> 11:04.000
channel, well I'd want to create a specific dynamic channel assignment or DCA

233
11:04.000 --> 11:04.840
policy that

234
11:04.840 --> 11:07.120
overrides the global policy.

235
11:07.120 --> 11:11.600
So the global policy says that I can use channel 36 for whatever reason.

236
11:11.600 --> 11:17.110
I don't want it to be at the site and so I disable channel 36 locally as part

237
11:17.110 --> 11:17.720
of this

238
11:17.720 --> 11:18.840
profile.

239
11:18.840 --> 11:25.260
And then that profile gets mapped via the 5 GHz RF profile that's part of the

240
11:25.260 --> 11:26.160
RF tag.

241
11:26.160 --> 11:30.390
So this architecture again starts with just the goal of creating a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

241
11:26.160 --> 11:30.390
So this architecture again starts with just the goal of creating a

242
11:30.390 --> 11:31.760
configuration that

243
11:31.760 --> 11:33.480
gets mapped to an access point.

244
11:33.480 --> 11:36.800
We're going to create three different tags to do so and those tags all have

245
11:36.800 --> 11:37.280
profiles

246
11:37.280 --> 11:38.440
behind them.

247
11:38.440 --> 11:42.450
For now, we just want to make sure that we understand this architecture and as

248
11:42.450 --> 11:43.160
we continue

249
11:43.160 --> 11:47.610
to dive further into configuration, we're going to see how we configure these

250
11:47.610 --> 11:48.240
profiles,

251
11:48.240 --> 11:52.120
associate them with tags and get those tags associated with our access points.