WEBVTT

1
00:00.000 --> 00:05.630
When we think about the management of our wireless networks, things are a

2
00:05.630 --> 00:06.360
little bit different

3
00:06.360 --> 00:10.390
than when we're managing our switches and our routers, primarily because of the

4
00:10.390 --> 00:10.760
sheer

5
00:10.760 --> 00:13.640
number of access points.

6
00:13.640 --> 00:15.500
We're talking about wireless communications.

7
00:15.500 --> 00:19.890
We usually have an access point, which is our network device that maintains a

8
00:19.890 --> 00:20.880
wired connection

9
00:20.880 --> 00:23.240
to the switched infrastructure.

10
00:23.240 --> 00:28.590
And then we're wirelessly communicating to devices that are referred to as

11
00:28.590 --> 00:29.600
stations.

12
00:29.600 --> 00:33.720
And abbreviated like so with STA capitalized.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:29.600 --> 00:33.720
And abbreviated like so with STA capitalized.

13
00:33.720 --> 00:37.530
So sometimes I'll refer to these as clients as well, but either way we have

14
00:37.530 --> 00:38.180
devices that

15
00:38.180 --> 00:41.720
are wirelessly communicating to these access points.

16
00:41.720 --> 00:46.430
And I know that back in the day when I was first just very young and entering

17
00:46.430 --> 00:47.600
into the industry

18
00:47.600 --> 00:52.860
I was responsible for largely just physical layer things like hanging access

19
00:52.860 --> 00:53.720
points.

20
00:53.720 --> 00:56.400
And eventually I learned how to do site surveys.

21
00:56.400 --> 01:00.860
And I would go into a school and this is like in the mid 2000s and I could do a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:56.400 --> 01:00.860
And I would go into a school and this is like in the mid 2000s and I could do a

22
01:00.860 --> 01:01.480
wireless

23
01:01.480 --> 01:05.850
site survey and for the entirety of this building we just need to have six

24
01:05.850 --> 01:07.040
access points.

25
01:07.040 --> 01:11.360
And the reason for that was because six access points would get the job done.

26
01:11.360 --> 01:15.840
We were using 2.4 gigahertz which could go a lot further.

27
01:15.840 --> 01:20.640
We had lower client density and so we didn't need a lot of AAPs.

28
01:20.640 --> 01:24.830
And so we might go into a school system and across many different schools maybe

29
01:24.830 --> 01:25.320
in total

30
01:25.320 --> 01:29.040
we had 50 or 60 access points.

31
01:29.040 --> 01:34.450
So still a lot of AAPs but it was at least somewhat manageable to manage every
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:29.040 --> 01:34.450
So still a lot of AAPs but it was at least somewhat manageable to manage every

32
01:34.450 --> 01:35.920
single AP on its

33
01:35.920 --> 01:36.920
own.

34
01:36.920 --> 01:42.950
But even 60 was a lot and as we've had to get into more modern applications and

35
01:42.950 --> 01:43.560
modern

36
01:43.560 --> 01:47.880
wireless devices we've seen the number of AAPs increased dramatically.

37
01:47.880 --> 01:53.600
That same school system that maybe needed 60 access points today might need 300

38
01:53.600 --> 01:55.200
or 600.

39
01:55.200 --> 02:01.780
And so we needed a better way even in the mid 2000s and late 2000s to manage
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:55.200 --> 02:01.780
And so we needed a better way even in the mid 2000s and late 2000s to manage

40
02:01.780 --> 02:02.760
these access

41
02:02.760 --> 02:03.760
points.

42
02:03.760 --> 02:11.880
And that led to the creation of the lightweight architecture.

43
02:11.880 --> 02:16.570
In a lot of ways lightweight wireless was sort of a first step into the world

44
02:16.570 --> 02:17.440
of software

45
02:17.440 --> 02:19.400
defined networking.

46
02:19.400 --> 02:24.070
Because what we did was we said that the amount of intelligence that's required

47
02:24.070 --> 02:24.520
on this

48
02:24.520 --> 02:27.720
access point here could be lowered.

49
02:27.720 --> 02:29.040
I didn't write that very well.

50
02:29.040 --> 02:30.720
So let's try that again.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
02:29.040 --> 02:30.720
So let's try that again.

51
02:30.720 --> 02:37.040
We could lower the intelligence level and ultimately the functions of the

52
02:37.040 --> 02:38.200
software that's

53
02:38.200 --> 02:40.280
running on this access point.

54
02:40.280 --> 02:44.720
So it's a more lightweight software image which is where the name comes from.

55
02:44.720 --> 02:50.720
And then we are connecting back to a wireless LAN controller.

56
02:50.720 --> 02:57.110
This wireless LAN controller is responsible for maintaining the management of

57
02:57.110 --> 02:58.200
that device.

58
02:58.200 --> 03:02.110
And so we could have again lots and lots of access points all communicating
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
02:58.200 --> 03:02.110
And so we could have again lots and lots of access points all communicating

59
03:02.110 --> 03:02.640
back to the

60
03:02.640 --> 03:04.280
wireless LAN controller.

61
03:04.280 --> 03:08.070
And I don't have to manage each one of these access points individually, which

62
03:08.070 --> 03:08.400
is what

63
03:08.400 --> 03:12.890
I had to do before a lightweight came around back when it was what we refer to

64
03:12.890 --> 03:14.240
as an autonomous

65
03:14.240 --> 03:15.640
architecture.

66
03:15.640 --> 03:20.090
So lightweight does a lot of good for us and a lot of times it's commonly

67
03:20.090 --> 03:21.280
centered around

68
03:21.280 --> 03:26.480
the idea of deploying wireless LAN controllers into our environment.

69
03:26.480 --> 03:30.000
And this is a beautiful thing because if I were to deploy let's say another
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:30.000 --> 03:30.680
access point

71
03:30.680 --> 03:38.400
into the environment, it will automatically find the wireless LAN controller.

72
03:38.400 --> 03:40.880
And there's a lot of ways that we can help it discover it.

73
03:40.880 --> 03:43.000
We'll talk about that momentarily.

74
03:43.000 --> 03:47.680
And the wireless LAN controller is going to push configuration down.

75
03:47.680 --> 03:51.480
Furthermore, as these access points are nearby each other, we might have one

76
03:51.480 --> 03:52.200
access point

77
03:52.200 --> 03:55.240
on channel 40 in the 5 gigahertz space.

78
03:55.240 --> 04:00.450
And therefore we wouldn't want this wireless or access point to be on channel
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
03:55.240 --> 04:00.450
And therefore we wouldn't want this wireless or access point to be on channel

79
04:00.450 --> 04:01.560
40 instead.

80
04:01.560 --> 04:05.660
The wireless LAN controller would say, all right, we're detecting channel 40 in

81
04:05.660 --> 04:06.520
the area.

82
04:06.520 --> 04:08.680
Maybe we're detecting a bunch of other channels.

83
04:08.680 --> 04:12.880
We think you should deploy on channel 60.

84
04:12.880 --> 04:14.760
And this might change over time.

85
04:14.760 --> 04:20.120
But in the end, we're trying to dynamically manage a wireless environment that

86
04:20.120 --> 04:21.400
isn't static.

87
04:21.400 --> 04:25.440
Wireless needs change dramatically even within the course of a day.

88
04:25.440 --> 04:29.990
The amount of interference and the amount of other wireless activities could

89
04:29.990 --> 04:30.560
prompt us
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
04:29.990 --> 04:30.560
prompt us

90
04:30.560 --> 04:35.640
to change not only the channel, but also the transmit power level.

91
04:35.640 --> 04:40.380
And so the wireless LAN controller is capable of monitoring the wireless

92
04:40.380 --> 04:42.120
environment and adjusting

93
04:42.120 --> 04:45.040
it on an as needed basis.

94
04:45.040 --> 04:50.530
From a, again, management perspective, me as the admin, I don't have to go out

95
04:50.530 --> 04:51.200
and manage

96
04:51.200 --> 04:52.920
all of these access points.

97
04:52.920 --> 04:56.240
Instead, I manage them all through one device.

98
04:56.240 --> 04:59.200
That's the wireless LAN controller.

99
04:59.200 --> 05:02.960
So what exactly is this wireless LAN controller?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

99
04:59.200 --> 05:02.960
So what exactly is this wireless LAN controller?

100
05:02.960 --> 05:08.260
Well, for the most part, a wireless LAN controller is going to be a physical

101
05:08.260 --> 05:10.480
device or appliance

102
05:10.480 --> 05:15.280
that's going to live on the network somewhere.

103
05:15.280 --> 05:16.800
And where it lives is very important.

104
05:16.800 --> 05:19.320
And we'll talk about that later on.

105
05:19.320 --> 05:22.120
Now they can also take different forms as well these days.

106
05:22.120 --> 05:26.200
For example, we could deploy it as a virtual appliance.

107
05:26.200 --> 05:30.500
And a virtual appliance just means that it has to live on one of my virtual
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

107
05:26.200 --> 05:30.500
And a virtual appliance just means that it has to live on one of my virtual

108
05:30.500 --> 05:31.400
hosts inside

109
05:31.400 --> 05:34.040
my data center.

110
05:34.040 --> 05:37.510
We don't often want our wireless LAN controllers to live inside of our data

111
05:37.510 --> 05:38.080
center.

112
05:38.080 --> 05:41.510
And so we could deploy this on a virtual host that connects in at a

113
05:41.510 --> 05:43.600
distribution layer somewhere.

114
05:43.600 --> 05:46.520
But either way, we could deploy the Cisco makes it available.

115
05:46.520 --> 05:52.200
First is download the software for a wireless LAN controller.

116
05:52.200 --> 05:57.420
And rather than purchase an appliance that is a physical set of hardware like

117
05:57.420 --> 05:58.240
CPU and memory

118
05:58.240 --> 06:02.420
and all of these things, I can create my own server and deploy the software
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
05:58.240 --> 06:02.420
and all of these things, I can create my own server and deploy the software

119
06:02.420 --> 06:03.480
onto that.

120
06:03.480 --> 06:07.440
So that's the concept of deploying it as a virtual appliance.

121
06:07.440 --> 06:11.880
We can also deploy it into the cloud as a virtual appliance.

122
06:11.880 --> 06:14.720
Now there's two different aspects to the cloud.

123
06:14.720 --> 06:19.750
So first of all, I could deploy this concept here, but rather than deploying it

124
06:19.750 --> 06:20.600
onto my own

125
06:20.600 --> 06:27.410
physical host, I just deploy the virtual appliance into a cloud space known as

126
06:27.410 --> 06:28.920
infrastructure

127
06:28.920 --> 06:30.040
as a service.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

127
06:28.920 --> 06:30.040
as a service.

128
06:30.040 --> 06:33.320
It's basically me saying I'm going to spin up a virtual machine in the cloud

129
06:33.320 --> 06:34.160
and run it

130
06:34.160 --> 06:35.160
there.

131
06:35.160 --> 06:40.160
And I could also run this as a controllerless environment.

132
06:40.160 --> 06:46.560
The best example of this from a Cisco perspective would be Miraki.

133
06:46.560 --> 06:50.400
Miraki is a product line that originally was a competitor to the Cisco.

134
06:50.400 --> 06:54.640
Cisco acquired them quite a long time ago at this point.

135
06:54.640 --> 06:59.160
And I connected an access point to my network and it goes out to the cloud and

136
06:59.160 --> 07:00.120
just finds
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

136
06:59.160 --> 07:00.120
just finds

137
07:00.120 --> 07:04.000
the controller that exists out in Miraki's space.

138
07:04.000 --> 07:06.800
So that means that I don't have to deploy anything here.

139
07:06.800 --> 07:09.200
I have to deploy something myself here.

140
07:09.200 --> 07:11.960
I don't have to deploy anything.

141
07:11.960 --> 07:17.920
And either way, the controller and the management functions exist in a cloud

142
07:17.920 --> 07:18.760
space.

143
07:18.760 --> 07:21.360
So both of those might be something we'd consider.

144
07:21.360 --> 07:25.480
Now the other thing is in smaller environments, we might even see this showing

145
07:25.480 --> 07:26.360
up inside of

146
07:26.360 --> 07:28.000
other devices.

147
07:28.000 --> 07:37.040
For example, we could see this embedded either in switches.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

147
07:28.000 --> 07:37.040
For example, we could see this embedded either in switches.

148
07:37.040 --> 07:41.240
Cisco has switches that allow you to embed a wireless LAN controller in there.

149
07:41.240 --> 07:45.880
And then we also have the ability to convert an access point into a very

150
07:45.880 --> 07:47.000
lightweight type

151
07:47.000 --> 07:50.320
of controller, which can be very useful for small locations.

152
07:50.320 --> 07:53.080
I take a bunch of access points that are in an area.

153
07:53.080 --> 07:56.820
I turn one of them into the wireless LAN controller from a functionality

154
07:56.820 --> 07:57.980
perspective.

155
07:57.980 --> 08:02.880
And that way I can manage this very small space without having to purchase a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

155
07:57.980 --> 08:02.880
And that way I can manage this very small space without having to purchase a

156
08:02.880 --> 08:03.720
larger than

157
08:03.720 --> 08:07.720
needed wireless LAN controller set of hardware.

158
08:07.720 --> 08:13.380
And so this is known as the embedded wireless controller, EWC solution when we

159
08:13.380 --> 08:14.540
're deploying

160
08:14.540 --> 08:17.260
it onto an access point.

161
08:17.260 --> 08:23.330
Now it's worth noting that Cisco actually had two different products and they

162
08:23.330 --> 08:24.260
're trying

163
08:24.260 --> 08:26.420
to migrate towards one of those.

164
08:26.420 --> 08:31.970
So originally when I talk about the mid-2000s Cisco made an acquisition of a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

164
08:26.420 --> 08:31.970
So originally when I talk about the mid-2000s Cisco made an acquisition of a

165
08:31.970 --> 08:32.820
company called

166
08:32.820 --> 08:35.740
Airspace.

167
08:35.740 --> 08:41.460
And previously they had acquired an access point company called Aeronet.

168
08:41.460 --> 08:45.020
So quite a few different products here that they purchased.

169
08:45.020 --> 08:49.520
And the funny thing about this is that this architecture existed for a very

170
08:49.520 --> 08:50.420
long time.

171
08:50.420 --> 08:54.340
It survived a couple of decades and probably even longer than that.

172
08:54.340 --> 08:59.250
And when we look at these products together this is at this point considered to

173
08:59.250 --> 09:00.140
be a legacy
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

173
08:59.250 --> 09:00.140
be a legacy

174
09:00.140 --> 09:01.140
product line.

175
09:01.140 --> 09:06.520
If I were to go out and purchase for example a 5500 controller or an 8500

176
09:06.520 --> 09:07.660
controller or

177
09:07.660 --> 09:11.100
a 3500, these are the old Aero-S.

178
09:11.100 --> 09:16.180
So running the operating system from Airspace, Aero-S as we called it.

179
09:16.180 --> 09:19.220
Those are a more legacy product line.

180
09:19.220 --> 09:22.020
And Cisco isn't actively selling these anymore.

181
09:22.020 --> 09:25.070
And the configuration of these was quite different thanks to the underlying

182
09:25.070 --> 09:26.940
operating system.

183
09:26.940 --> 09:33.510
These days Cisco has an iOS Xe platform that they put underneath the catalyst
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

183
09:26.940 --> 09:33.510
These days Cisco has an iOS Xe platform that they put underneath the catalyst

184
09:33.510 --> 09:35.580
product umbrella.

185
09:35.580 --> 09:39.420
Meaning that we used to refer to catalyst as just switches.

186
09:39.420 --> 09:43.420
Nowadays it can apply to routers and it can apply to access points and it can

187
09:43.420 --> 09:44.020
apply to

188
09:44.020 --> 09:45.780
wireless LAN controllers.

189
09:45.780 --> 09:50.740
For example they have the catalyst 9100 access point line and they have the

190
09:50.740 --> 09:52.580
catalyst 9800 wireless

191
09:52.580 --> 09:54.620
LAN controllers.

192
09:54.620 --> 09:57.940
And if I want to configure these again they are running iOS Xe.

193
09:57.940 --> 10:03.980
It feels a whole lot like I'm logged into a Cisco switch from a CLI perspective
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

193
09:57.940 --> 10:03.980
It feels a whole lot like I'm logged into a Cisco switch from a CLI perspective

194
10:03.980 --> 10:04.060
.

195
10:04.060 --> 10:09.260
Whereas the CLI for these legacy products it required studying because it was

196
10:09.260 --> 10:10.140
very different

197
10:10.140 --> 10:13.380
than anything else that Cisco had.

198
10:13.380 --> 10:17.590
Now we mentioned that when we come online the access points are automatically

199
10:17.590 --> 10:19.620
able to discover

200
10:19.620 --> 10:21.460
the wireless LAN controller.

201
10:21.460 --> 10:25.300
So they perform this WLC discovery process.

202
10:25.300 --> 10:31.260
They're going to start by performing a broadcast to find out if the wireless
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

202
10:25.300 --> 10:31.260
They're going to start by performing a broadcast to find out if the wireless

203
10:31.260 --> 10:32.340
LAN controller

204
10:32.340 --> 10:34.340
is on the same subnet as me.

205
10:34.340 --> 10:36.300
In larger networks this is rarely the case.

206
10:36.300 --> 10:39.600
Usually the wireless LAN controller lives out in the middle of the network

207
10:39.600 --> 10:40.460
somewhere and

208
10:40.460 --> 10:44.820
we have access points all over the place on all kinds of different subnets.

209
10:44.820 --> 10:49.500
So this is only going to work in lab environments in very small spaces.

210
10:49.500 --> 10:54.140
The most common way that we perform discovery is via DHCP.

211
10:54.140 --> 10:57.370
One of the cool things about migrating to a lightweight architecture back in

212
10:57.370 --> 10:58.340
the day was

213
10:58.340 --> 11:02.420
we were able to leverage DHCP for our access points.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

213
10:58.340 --> 11:02.420
we were able to leverage DHCP for our access points.

214
11:02.420 --> 11:05.800
When it was autonomous I had to manually configure all of these access points

215
11:05.800 --> 11:06.460
while I needed

216
11:06.460 --> 11:11.140
to track their IP addresses.

217
11:11.140 --> 11:17.440
With lightweight I can perform DHCP and DHCP by default doesn't include

218
11:17.440 --> 11:17.940
wireless LAN

219
11:17.940 --> 11:23.510
controller information but it can provide lots of other information via options

220
11:23.510 --> 11:23.780
.

221
11:23.780 --> 11:29.050
So I can use DHCP option 43 which is a configuration on pretty much every DHCP

222
11:29.050 --> 11:30.180
server these days.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

222
11:29.050 --> 11:30.180
server these days.

223
11:30.180 --> 11:35.160
I can tell that server hey you need to pass a particular IP address via this

224
11:35.160 --> 11:35.900
option.

225
11:35.900 --> 11:39.140
So when I receive the IP address I'm going to receive the IP address and the

226
11:39.140 --> 11:39.780
gateway and

227
11:39.780 --> 11:43.020
the subnet mask and all these things but I'll also receive a wireless LAN

228
11:43.020 --> 11:45.260
controller IP address.

229
11:45.260 --> 11:50.030
So that's the value of using DHCP and again it's the most common option in my

230
11:50.030 --> 11:50.980
experience

231
11:50.980 --> 11:55.260
for locating a wireless LAN controller that's remote.

232
11:55.260 --> 12:01.220
Nesisco does give us a DNS option when we come online we'll get as part of DHCP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

232
11:55.260 --> 12:01.220
Nesisco does give us a DNS option when we come online we'll get as part of DHCP

233
12:01.220 --> 12:01.260
we're

234
12:01.260 --> 12:07.740
also given DNS servers so if I don't get an IP address via this DHCP process I

235
12:07.740 --> 12:08.940
can instead

236
12:08.940 --> 12:13.660
get the DNS entry or the DNS server rather and then I can perform a name

237
12:13.660 --> 12:15.100
resolution of

238
12:15.100 --> 12:23.700
sysco capwapcontroller.local.

239
12:23.700 --> 12:29.580
And so this is actually dot local dash domain.

240
12:29.580 --> 12:33.810
So this is an option that we can use if we for whatever reason aren't able to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

240
12:29.580 --> 12:33.810
So this is an option that we can use if we for whatever reason aren't able to

241
12:33.810 --> 12:34.580
use DHCP

242
12:34.580 --> 12:40.220
option 43 then we can certainly perform this DNS look up.

243
12:40.220 --> 12:46.300
And lastly we can actually perform this as a or perform a manual operation.

244
12:46.300 --> 12:51.510
I can log into the access point I could console into it for example and I could

245
12:51.510 --> 12:52.300
tell it

246
12:52.300 --> 12:55.660
the IP address of the wireless LAN controller.

247
12:55.660 --> 13:00.520
So regardless we have lots of options and lots of ways for our access points to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

247
12:55.660 --> 13:00.520
So regardless we have lots of options and lots of ways for our access points to

248
13:00.520 --> 13:01.060
figure

249
13:01.060 --> 13:04.620
out where in the network the wireless LAN controller is.

250
13:04.620 --> 13:10.570
Now once an access point comes online and performs this discovery it's going to

251
13:10.570 --> 13:11.380
maintain

252
13:11.380 --> 13:18.740
a list of all of the wireless LAN controllers that it becomes aware of.

253
13:18.740 --> 13:21.940
This way when it reloads it doesn't have to go through this discovery process

254
13:21.940 --> 13:22.420
again it

255
13:22.420 --> 13:26.510
can just immediately go out to its list of known controllers and if it can't

256
13:26.510 --> 13:27.260
find a wireless

257
13:27.260 --> 13:32.000
LAN controller maybe that WLC is down it can then perform this discovery
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

257
13:27.260 --> 13:32.000
LAN controller maybe that WLC is down it can then perform this discovery

258
13:32.000 --> 13:33.100
process again.

259
13:33.100 --> 13:36.940
But ideally we only have to do this for initial discovery because for the most

260
13:36.940 --> 13:37.740
part our wireless

261
13:37.740 --> 13:41.380
LAN controller configurations are going to be relatively static and they're not

262
13:41.380 --> 13:41.740
going

263
13:41.740 --> 13:43.580
to be moving around.

264
13:43.580 --> 13:49.480
Now we do have a lot of design considerations to make when it comes to our

265
13:49.480 --> 13:50.260
wireless LAN

266
13:50.260 --> 13:54.990
controllers and that's going to be the focus of this part of this course is to

267
13:54.990 --> 13:55.820
be drilling

268
13:55.820 --> 14:00.520
into the idea of how do we deploy a wireless architecture what is going to be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

268
13:55.820 --> 14:00.520
into the idea of how do we deploy a wireless architecture what is going to be

269
14:00.520 --> 14:01.380
required from

270
14:01.380 --> 14:02.980
a design perspective.

271
14:02.980 --> 14:08.370
I've got to think about things such as licensing to make sure that I have

272
14:08.370 --> 14:09.780
wireless LAN controllers

273
14:09.780 --> 14:13.690
that are large enough and licensed enough for the number of access points in my

274
14:13.690 --> 14:14.500
environment.

275
14:14.500 --> 14:19.340
So I do need to consider the hardware sizing of my wireless LAN controllers.

276
14:19.340 --> 14:24.030
We have small, medium, large wireless LAN controllers for example we've got to

277
14:24.030 --> 14:25.980
consider failover

278
14:25.980 --> 14:30.490
because if a wireless LAN controller goes down we don't want to lose access to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

278
14:25.980 --> 14:30.490
because if a wireless LAN controller goes down we don't want to lose access to

279
14:30.490 --> 14:31.060
our wireless

280
14:31.060 --> 14:32.060
network.

281
14:32.060 --> 14:36.750
They rely on the wireless LAN controller because the APs are lightweight and

282
14:36.750 --> 14:37.740
they aren't functioning

283
14:37.740 --> 14:39.620
fully on their own.

284
14:39.620 --> 14:43.250
And lastly we mentioned it earlier we do need to worry about the wireless LAN

285
14:43.250 --> 14:43.980
controller

286
14:43.980 --> 14:50.800
location. This is a critical part of a wireless architecture design and we'll

287
14:50.800 --> 14:51.020
talk about the

288
14:51.020 --> 14:52.580
reasons for that here shortly.

289
14:52.580 --> 15:02.580
[BLANK_AUDIO]