WEBVTT

1
00:00.000 --> 00:03.800
Alright, it is time to review our wireless.

2
00:03.800 --> 00:08.270
So we are going to combine both our architectural conversations and security

3
00:08.270 --> 00:09.320
conversations into

4
00:09.320 --> 00:10.320
this review.

5
00:10.320 --> 00:14.060
Meaning we not only need to understand the architecture of wireless as well as

6
00:14.060 --> 00:14.800
the security

7
00:14.800 --> 00:20.520
of wireless but also how to configure it all in iOS and iOS Xe.

8
00:20.520 --> 00:24.950
And so definitely bookmarked this skill for review later because this will be a

9
00:24.950 --> 00:25.360
great

10
00:25.360 --> 00:29.440
opportunity to come back before taking the exam to make sure that we understand

11
00:29.440 --> 00:30.040
all of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:29.440 --> 00:30.040
all of

12
00:30.040 --> 00:35.390
the foundational principles of wireless all the way up to the configuration of

13
00:35.390 --> 00:36.040
our SSID

14
00:36.040 --> 00:38.160
along with our security parameters.

15
00:38.160 --> 00:41.190
So as always as we are going through these quizzes make sure you pause the

16
00:41.190 --> 00:41.960
video to answer

17
00:41.960 --> 00:45.800
the question yourself and identify any areas of weakness.

18
00:45.800 --> 00:48.860
The source skill is at the bottom of each question so you can go back and

19
00:48.860 --> 00:49.880
review that skill as

20
00:49.880 --> 00:54.720
much as needed if we do identify areas that we maybe aren't as strong in.

21
00:54.720 --> 00:58.120
So let's go ahead and start off with 8 questions in this quiz.

22
00:58.120 --> 01:03.730
First up what AP mode of operation allows for scanning many channels for RF
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:58.120 --> 01:03.730
First up what AP mode of operation allows for scanning many channels for RF

23
01:03.730 --> 01:04.440
data.

24
01:04.440 --> 01:08.800
So this concept of AP modes this is very important in the Cisco lightweight

25
01:08.800 --> 01:09.760
architecture.

26
01:09.760 --> 01:14.580
Cisco allows for all 5 of these modes of operation as well as a bridge mode

27
01:14.580 --> 01:17.080
that includes mesh.

28
01:17.080 --> 01:20.710
But either way the answer to this question is simply going to be monitor mode

29
01:20.710 --> 01:21.400
right there

30
01:21.400 --> 01:22.840
in the middle.

31
01:22.840 --> 01:24.760
So what are these modes of operation?

32
01:24.760 --> 01:28.600
Well again we can go back and review if needed but just very quickly local mode

33
01:28.600 --> 01:29.400
of operation

34
01:29.400 --> 01:32.320
this is going to be our normal mode.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:29.400 --> 01:32.320
this is going to be our normal mode.

35
01:32.320 --> 01:37.580
Most of our APs should be in local mode it's referring to the fact that our APs

36
01:37.580 --> 01:38.520
are locally

37
01:38.520 --> 01:43.400
configured ideally connecting to a local wireless LAN controller.

38
01:43.400 --> 01:48.710
FlexConnect this is when we connect an access point remotely and we might worry

39
01:48.710 --> 01:49.280
about a

40
01:49.280 --> 01:55.680
flex connect AP losing its connection to the wireless LAN controller usually

41
01:55.680 --> 01:56.360
because there's

42
01:56.360 --> 02:01.000
a wide area network in the way that might not be fully stable or fully reliable
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:56.360 --> 02:01.000
a wide area network in the way that might not be fully stable or fully reliable

43
02:01.000 --> 02:01.320
and

44
02:01.320 --> 02:04.400
we just lack the redundancy as much as anything.

45
02:04.400 --> 02:08.100
So we've configured the access point for flex connect and if we do lose this

46
02:08.100 --> 02:08.680
connection

47
02:08.680 --> 02:13.240
to the wireless LAN controller then the access point stays online.

48
02:13.240 --> 02:16.860
Just keep in mind in the real world that this isn't particularly useful if the

49
02:16.860 --> 02:17.240
entire

50
02:17.240 --> 02:21.630
network is out here and we lost our connection anyways it's primarily going to

51
02:21.630 --> 02:22.280
be useful

52
02:22.280 --> 02:26.230
when we've got some kind of router at the site with a dedicated internet

53
02:26.230 --> 02:27.240
circuit because

54
02:27.240 --> 02:31.420
at that point wireless clients could still go through the flex connect AP and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
02:27.240 --> 02:31.420
at that point wireless clients could still go through the flex connect AP and

55
02:31.420 --> 02:31.800
get out

56
02:31.800 --> 02:33.480
to the internet.

57
02:33.480 --> 02:37.080
So it's just a matter of thinking through what exactly we're gaining.

58
02:37.080 --> 02:40.960
Monitor mode is the one we're talking about here the idea is that the access

59
02:40.960 --> 02:41.640
point will

60
02:41.640 --> 02:45.910
be able to sniff all of the well I shouldn't use the word sniff because that

61
02:45.910 --> 02:46.760
sniff remote

62
02:46.760 --> 02:50.840
but we can monitor and scan all of the different channels.

63
02:50.840 --> 02:55.640
So a access point that is servicing stations is locked to a single channel for

64
02:55.640 --> 02:56.240
the most

65
02:56.240 --> 02:57.240
part.

66
02:57.240 --> 03:01.050
I might choose channel 36 it's locked to that channel because all of these
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
02:57.240 --> 03:01.050
I might choose channel 36 it's locked to that channel because all of these

67
03:01.050 --> 03:02.120
wireless stations

68
03:02.120 --> 03:06.360
are trying to communicate on why on state channel 36.

69
03:06.360 --> 03:11.060
And so if there is a rogue device out here on channel 40 this access point is

70
03:11.060 --> 03:11.800
not really

71
03:11.800 --> 03:13.240
going to be able to see it.

72
03:13.240 --> 03:18.580
Now every now and again a local mode AP can switch channels and to listen for

73
03:18.580 --> 03:19.160
what's

74
03:19.160 --> 03:23.980
going on but again the focus is going to be over here on all of these channel

75
03:23.980 --> 03:25.200
36 clients.

76
03:25.200 --> 03:30.920
Whereas a monitor mode AP importantly does not service clients.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:25.200 --> 03:30.920
Whereas a monitor mode AP importantly does not service clients.

77
03:30.920 --> 03:34.470
These wireless stations are not going to connect for data instead I'm going to

78
03:34.470 --> 03:35.280
listen to channel

79
03:35.280 --> 03:40.360
36 and then listen to channel 40 and then listen to channel 44 and keep cycling

80
03:40.360 --> 03:40.880
all of

81
03:40.880 --> 03:45.680
these channels around and around and around to provide as much RF data as

82
03:45.680 --> 03:46.520
possible.

83
03:46.520 --> 03:51.040
But very importantly no clients are serviced on monitor mode sniff remote is

84
03:51.040 --> 03:51.800
sort of like

85
03:51.800 --> 03:59.120
monitor mode except importantly well how is it similar well there's no clients

86
03:59.120 --> 03:59.240
that's

87
03:59.240 --> 04:03.110
how it's similar otherwise it's pretty different it's going to be locked to a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
03:59.240 --> 04:03.110
how it's similar otherwise it's pretty different it's going to be locked to a

88
04:03.110 --> 04:03.840
specific channel

89
04:03.840 --> 04:11.030
so like channel 36 and we're going to be listening in specifically for packet

90
04:11.030 --> 04:11.920
captures.

91
04:11.920 --> 04:15.640
We have to lock to a channel because otherwise we're not going to hear all of

92
04:15.640 --> 04:16.320
the packets

93
04:16.320 --> 04:20.130
that are being exchanged and so this is usually not something we're going to

94
04:20.130 --> 04:21.040
install out into

95
04:21.040 --> 04:26.240
the network it's usually a little bit more intended for specific use cases and

96
04:26.240 --> 04:26.960
then bridge

97
04:26.960 --> 04:31.730
and mesh is going to be for connecting to our remote locations such as classic
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

97
04:26.960 --> 04:31.730
and mesh is going to be for connecting to our remote locations such as classic

98
04:31.730 --> 04:32.600
traditional

99
04:32.600 --> 04:36.700
wireless bridges so that was a very quick overview of the different modes of

100
04:36.700 --> 04:37.360
operation

101
04:37.360 --> 04:41.360
but this is a fundamental concept we must be comfortable with when it comes to

102
04:41.360 --> 04:41.800
Cisco's

103
04:41.800 --> 04:43.000
lightweight architecture.

104
04:43.000 --> 04:48.320
Alright question two what antenna type can be used to reach very long distances

105
04:48.320 --> 04:48.960
usually

106
04:48.960 --> 04:55.450
for connecting to towers so we're talking about maybe a pair of towers out here

107
04:55.450 --> 04:56.040
we're

108
04:56.040 --> 05:00.760
going to connect something that allows for long range communication well the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

108
04:56.040 --> 05:00.760
going to connect something that allows for long range communication well the

109
05:00.760 --> 05:01.160
answer to

110
05:01.160 --> 05:05.720
this question is going to be a grid antenna which is more or less a dish

111
05:05.720 --> 05:06.680
antenna the big

112
05:06.680 --> 05:12.350
difference is that a grid antenna looks something like this where it's a

113
05:12.350 --> 05:14.680
wireless grid that still

114
05:14.680 --> 05:19.090
catches wireless signals but allows for like wind to pass through it so it's

115
05:19.090 --> 05:19.720
less likely

116
05:19.720 --> 05:24.600
to get blown down or have problems getting pushed by the wind.

117
05:24.600 --> 05:28.930
So a grid and a dish these are our longest range antennas very quickly an omnid

118
05:28.930 --> 05:29.760
irectional

119
05:29.760 --> 05:33.890
is that circular overhead it looks like a circle at least from the side as we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

119
05:29.760 --> 05:33.890
is that circular overhead it looks like a circle at least from the side as we

120
05:33.890 --> 05:34.480
've talked

121
05:34.480 --> 05:38.160
about it looks a little bit more like that donut shape that's pretty poor

122
05:38.160 --> 05:38.960
representation

123
05:38.960 --> 05:43.050
there we go something along those lines but it's supposed to cover the area

124
05:43.050 --> 05:43.960
around evenly

125
05:43.960 --> 05:45.920
hence the word omnie there.

126
05:45.920 --> 05:49.890
Patch and panel these are parts are two different types of planar antennas

127
05:49.890 --> 05:51.680
these are semi directional

128
05:51.680 --> 05:56.490
usually intended for hallways where we're broadcasting out in a straight line

129
05:56.490 --> 05:57.000
and not

130
05:57.000 --> 06:01.400
so much worrying about the space behind the antenna and then a sector antenna
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
05:57.000 --> 06:01.400
so much worrying about the space behind the antenna and then a sector antenna

131
06:01.400 --> 06:02.520
this is

132
06:02.520 --> 06:07.070
we think about maybe cellular antennas naturally cellular and Wi-Fi are very

133
06:07.070 --> 06:07.920
different in a

134
06:07.920 --> 06:12.900
lot of ways but the concept here is that we cover client area from a tower by

135
06:12.900 --> 06:13.480
aiming

136
06:13.480 --> 06:17.900
down and so typically we're going to install an array of sector antennas but

137
06:17.900 --> 06:18.320
again that's

138
06:18.320 --> 06:23.480
not even though we might mount it on a pole or a small tower and in an area it

139
06:23.480 --> 06:24.280
's not going

140
06:24.280 --> 06:29.960
to service very long distances like great in dish antennas.

141
06:29.960 --> 06:32.740
Alright question number three place these options in the order used by
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

141
06:29.960 --> 06:32.740
Alright question number three place these options in the order used by

142
06:32.740 --> 06:33.600
lightweight APs

143
06:33.600 --> 06:38.320
to discover a wireless LAN controller so remember part of the lightweight

144
06:38.320 --> 06:39.640
architecture the idea

145
06:39.640 --> 06:43.210
here is we're going to have a centralized controller somewhere and I just want

146
06:43.210 --> 06:43.440
to be

147
06:43.440 --> 06:47.520
able to pull an access point out of a box and plug it into the network and have

148
06:47.520 --> 06:48.240
it find

149
06:48.240 --> 06:53.810
its wireless LAN controller and yeah I can manually configure it if I have to

150
06:53.810 --> 06:54.120
but for

151
06:54.120 --> 06:58.180
the most part we're trying to get away from unboxing a thousand access points

152
06:58.180 --> 06:58.640
configuring

153
06:58.640 --> 07:02.660
them and then deploying them I'd rather just pull them out of the box from
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

153
06:58.640 --> 07:02.660
them and then deploying them I'd rather just pull them out of the box from

154
07:02.660 --> 07:03.720
Cisco straight

155
07:03.720 --> 07:08.490
from the delivery person whatever the situation is there and plug it in and

156
07:08.490 --> 07:09.640
have it discover

157
07:09.640 --> 07:15.340
the wireless LAN controller so we are going to go through a specific order here

158
07:15.340 --> 07:15.960
but the

159
07:15.960 --> 07:21.340
goal again is to enable automated discovery that scales with the network so

160
07:21.340 --> 07:21.920
first of all

161
07:21.920 --> 07:25.850
we're going to start with a broadcast we're just going to do a layer to

162
07:25.850 --> 07:26.720
broadcast just

163
07:26.720 --> 07:30.330
in case this is a small site just in case the wireless LAN controller happens
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

163
07:26.720 --> 07:30.330
in case this is a small site just in case the wireless LAN controller happens

164
07:30.330 --> 07:30.640
to be

165
07:30.640 --> 07:34.690
on the same VLAN the advantage here is we're going to discover local wireless

166
07:34.690 --> 07:35.680
LAN controllers

167
07:35.680 --> 07:41.200
before we go discovering remote wireless LAN controllers but next we're going

168
07:41.200 --> 07:42.040
to attempt

169
07:42.040 --> 07:47.330
to use DHCP option 43 and as we said earlier on in the course this is the one

170
07:47.330 --> 07:48.360
that is highly

171
07:48.360 --> 07:53.360
used in production real world networks the reason for that is the AP is going

172
07:53.360 --> 07:53.880
to have

173
07:53.880 --> 07:59.080
to get an IP address via DHCP in all likelihood yeah if we pulled it out of the

174
07:59.080 --> 07:59.600
box we could

175
07:59.600 --> 08:03.440
give it a static IP but that doesn't scale particularly well so we're going to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

175
07:59.600 --> 08:03.440
give it a static IP but that doesn't scale particularly well so we're going to

176
08:03.440 --> 08:03.880
use DHCP

177
08:03.880 --> 08:08.920
in most cases anyways to get an address why not configure the DHCP server to

178
08:08.920 --> 08:09.840
also handle

179
08:09.840 --> 08:14.990
or hand the access point the wireless LAN controller address at the same time

180
08:14.990 --> 08:15.840
we're going to have

181
08:15.840 --> 08:20.980
to configure our DHCP server for this we get on here we configure option 43

182
08:20.980 --> 08:22.560
with an IP address

183
08:22.560 --> 08:26.950
that would be the wireless LAN controller address and as part of the DHCP

184
08:26.950 --> 08:27.840
negotiation

185
08:27.840 --> 08:32.910
the AP becomes aware of what that wireless LAN controller address is so it's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

185
08:27.840 --> 08:32.910
the AP becomes aware of what that wireless LAN controller address is so it's

186
08:32.910 --> 08:33.840
very flexible

187
08:33.840 --> 08:39.040
and very scalable now third we're going to attempt to use DNS we're going to

188
08:39.040 --> 08:39.560
resolve

189
08:39.560 --> 08:46.760
that name sisco-capwap-controller.local and from here we would well naturally

190
08:46.760 --> 08:47.480
as part

191
08:47.480 --> 08:52.110
of the address we get a DNS server we will perform a resolution of that which

192
08:52.110 --> 08:52.560
means

193
08:52.560 --> 08:58.880
I actually have to configure the DNS entry here on my DNS server so it goes out

194
08:58.880 --> 08:59.800
performs

195
08:59.800 --> 09:06.040
resolution and it gets the IP address of the wireless LAN controller now lastly
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

195
08:59.800 --> 09:06.040
resolution and it gets the IP address of the wireless LAN controller now lastly

196
09:06.040 --> 09:06.600
if we have

197
09:06.600 --> 09:11.970
to rely on manual configuration we can however again it doesn't scale very well

198
09:11.970 --> 09:12.280
but this

199
09:12.280 --> 09:17.090
is the order we want to start with broadcast go to DHCP then DNS then get to

200
09:17.090 --> 09:17.920
the manual

201
09:17.920 --> 09:21.920
configuration as a last resort.

202
09:21.920 --> 09:26.260
Alright next up which type of roaming makes use of an anchor controller so

203
09:26.260 --> 09:27.240
first and foremost

204
09:27.240 --> 09:32.690
there is no such thing as a layer 3 intra controller roam so hopefully we flag
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

204
09:27.240 --> 09:32.690
there is no such thing as a layer 3 intra controller roam so hopefully we flag

205
09:32.690 --> 09:33.200
that pretty

206
09:33.200 --> 09:37.860
quickly however let's walk through a couple of these other scenarios so

207
09:37.860 --> 09:38.920
remember the situation

208
09:38.920 --> 09:43.390
here we might have access points that are part of the same wireless LAN

209
09:43.390 --> 09:44.400
controller and

210
09:44.400 --> 09:49.380
then we might also have a different wireless LAN controller with an access

211
09:49.380 --> 09:50.360
point and this

212
09:50.360 --> 09:55.060
could be part of a layer 2 network so they're on the same VLANs but then we

213
09:55.060 --> 09:55.960
might also have

214
09:55.960 --> 10:01.020
a wireless LAN controller over here that has layer 3 segmentation so this is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

214
09:55.960 --> 10:01.020
a wireless LAN controller over here that has layer 3 segmentation so this is

215
10:01.020 --> 10:01.840
routed out

216
10:01.840 --> 10:06.940
to a different location potentially across the network core so to go through a

217
10:06.940 --> 10:07.240
layer

218
10:07.240 --> 10:14.030
3 network to another AP and our user here walking with their mobile device in

219
10:14.030 --> 10:14.840
hand might

220
10:14.840 --> 10:19.990
walk and roam across all of these access points so between these two access

221
10:19.990 --> 10:20.800
points this would

222
10:20.800 --> 10:25.200
be an intra layer 2 roam.

223
10:25.200 --> 10:30.920
intra is an English not a word but I guess a there's a word for it but it goes
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

223
10:25.200 --> 10:30.920
intra is an English not a word but I guess a there's a word for it but it goes

224
10:30.920 --> 10:31.680
in front

225
10:31.680 --> 10:38.790
of a word like a preface and prefix that's it and then it is intended to mean

226
10:38.790 --> 10:39.600
within

227
10:39.600 --> 10:45.650
so it's within the same controller here so intra layer 2 that is very seamless

228
10:45.650 --> 10:46.200
we don't

229
10:46.200 --> 10:50.940
need to worry about anchor controllers then if we go to another wireless LAN

230
10:50.940 --> 10:51.760
controller

231
10:51.760 --> 10:56.400
now we're talking about inter which is a prefix meaning different or between so

232
10:56.400 --> 10:56.640
now

233
10:56.640 --> 10:59.980
we're talking about between two different wireless LAN controllers but it's

234
10:59.980 --> 11:00.880
still layer
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

234
10:59.980 --> 11:00.880
still layer

235
11:00.880 --> 11:01.880
2.

236
11:01.880 --> 11:04.440
Well we don't need an anchor controller any error at this point we can just

237
11:04.440 --> 11:05.440
hand the information

238
11:05.440 --> 11:09.120
off because my IP address stays the same.

239
11:09.120 --> 11:14.200
The challenge is when we roam well say over here this is going to be an inter

240
11:14.200 --> 11:14.720
layer 3

241
11:14.720 --> 11:20.250
roam inter because it's between two wireless LAN controllers layer 3 because we

242
11:20.250 --> 11:20.800
have to

243
11:20.800 --> 11:27.310
pass this layer 3 boundary and now the problem is my IP address subnet lives

244
11:27.310 --> 11:29.240
over here and

245
11:29.240 --> 11:34.700
yet I am my wireless device M over here so any kind of packet coming in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

245
11:29.240 --> 11:34.700
yet I am my wireless device M over here so any kind of packet coming in

246
11:34.700 --> 11:35.920
destined for

247
11:35.920 --> 11:41.040
that IP address is going to get routed this way so now I need the anchor

248
11:41.040 --> 11:42.360
controller so

249
11:42.360 --> 11:46.050
my wireless LAN controller here will become an anchor controller it will

250
11:46.050 --> 11:46.800
receive that

251
11:46.800 --> 11:52.890
information or that packet and then send it over to my foreign controller so

252
11:52.890 --> 11:53.640
that is

253
11:53.640 --> 11:59.310
this whole concept so long story short what we need to do is take advantage of

254
11:59.310 --> 12:00.040
the layer
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

254
11:59.310 --> 12:00.040
the layer

255
12:00.040 --> 12:06.560
3 and that should say inter controller roam so there's a little bit of a test

256
12:06.560 --> 12:06.880
there to

257
12:06.880 --> 12:11.600
see if we're paying attention clearly I wasn't a little bit of copy paste error

258
12:11.600 --> 12:12.240
there but

259
12:12.240 --> 12:16.600
this should say inter controller roam and so yes there's no such thing as a

260
12:16.600 --> 12:17.640
layer 3 intro

261
12:17.640 --> 12:22.180
but there is such a thing as a layer 3 inter controller roam and that is going

262
12:22.180 --> 12:22.840
to require

263
12:22.840 --> 12:28.080
the use of an anchor controller so speaking of roaming we've got another

264
12:28.080 --> 12:28.640
question here

265
12:28.640 --> 12:32.450
about it wireless LAN controllers must be configured with what feature in order
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

265
12:28.640 --> 12:32.450
about it wireless LAN controllers must be configured with what feature in order

266
12:32.450 --> 12:33.000
to provide

267
12:33.000 --> 12:37.850
seamless roaming between WLCs well we just talked about anchor controllers but

268
12:37.850 --> 12:38.680
anchor controllers

269
12:38.680 --> 12:44.750
aren't required for seamless roaming because we might do an inter layer 2 roam

270
12:44.750 --> 12:45.360
and then

271
12:45.360 --> 12:50.110
anchor controllers aren't involved the answer here is be the mobility group

272
12:50.110 --> 12:50.720
those wireless

273
12:50.720 --> 12:54.660
LAN controllers that we drew out on the previous quiz question these are all

274
12:54.660 --> 12:55.600
going to be part

275
12:55.600 --> 13:00.360
of the same mobility group we must configure them to be part of the mobility
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

275
12:55.600 --> 13:00.360
of the same mobility group we must configure them to be part of the mobility

276
13:00.360 --> 13:01.200
group which

277
13:01.200 --> 13:06.460
allows them to hand off wireless clients from one AP to another when they

278
13:06.460 --> 13:07.440
belong to those

279
13:07.440 --> 13:12.860
different controllers alright we're over halfway done just three more questions

280
13:12.860 --> 13:13.920
to go what type

281
13:13.920 --> 13:18.840
of cap web tunnel is built from flex connect APs to the controller so remember

282
13:18.840 --> 13:19.840
when an access

283
13:19.840 --> 13:24.100
point comes online and let's say it's in local mode meaning that normal type of

284
13:24.100 --> 13:24.680
mode that we

285
13:24.680 --> 13:28.810
can expect to deploy for the most part the access point must form cap web

286
13:28.810 --> 13:30.240
tunnels it's going to form
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

286
13:28.810 --> 13:30.240
tunnels it's going to form

287
13:30.240 --> 13:34.980
a control plane connection and a data plane connection this is why if we lose

288
13:34.980 --> 13:36.040
connection to the

289
13:36.040 --> 13:41.800
wireless LAN controller we lose all sense of wireless connectivity for that AP

290
13:41.800 --> 13:43.800
however if we

291
13:43.800 --> 13:48.080
have a flex connect access point where again we run the risk of losing

292
13:48.080 --> 13:49.640
connection to the wireless

293
13:49.640 --> 13:55.160
LAN controller we're only going to run a control plane tunnel the data plane

294
13:55.160 --> 13:56.560
tunnel is not used in

295
13:56.560 --> 14:02.150
this case so recall that let's say this connection online is online over here
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

295
13:56.560 --> 14:02.150
this case so recall that let's say this connection online is online over here

296
14:02.150 --> 14:03.400
this client connecting

297
14:03.400 --> 14:09.500
to this AP gets tunneled to the wireless LAN controller and it has a trunk back

298
14:09.500 --> 14:11.000
to the rest of the

299
14:11.000 --> 14:14.800
network and so this client gets tunneled to the wireless LAN controller and

300
14:14.800 --> 14:15.960
placed back onto the

301
14:15.960 --> 14:21.220
network meaning this is its point of presence well over here this client isn't

302
14:21.220 --> 14:22.360
going to be forwarded

303
14:22.360 --> 14:26.720
through the data plane tunnel instead it's going to be dropped off here to the

304
14:26.720 --> 14:27.800
local switch or

305
14:27.800 --> 14:33.500
whatever this access point is plugged into via its trunk and it just changes
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

305
14:27.800 --> 14:33.500
whatever this access point is plugged into via its trunk and it just changes

306
14:33.500 --> 14:35.320
the way that the traffic

307
14:35.320 --> 14:39.660
is handed off which is why we can hand this off to maybe a local internet

308
14:39.660 --> 14:41.240
connection if the LAN

309
14:41.240 --> 14:45.630
circuit goes down so the answer here when it comes to flex connect APs it's

310
14:45.630 --> 14:47.000
going to form a control

311
14:47.000 --> 14:52.920
plane tunnel only all right little question here on configuration so what are

312
14:52.920 --> 14:54.360
the three primary

313
14:54.360 --> 15:00.520
configuration elements in iOSXE that provide APs with configuration the quick
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

313
14:54.360 --> 15:00.520
configuration elements in iOSXE that provide APs with configuration the quick

314
15:00.520 --> 15:01.880
answer here is when

315
15:01.880 --> 15:06.580
we're talking about our three primary configuration elements we're looking at

316
15:06.580 --> 15:07.720
tags and so we must

317
15:07.720 --> 15:13.770
configure a site tag and RF tag and a policy tag in order to fully configure an

318
15:13.770 --> 15:15.640
AP now that said

319
15:15.640 --> 15:20.460
the RF tag and the site tag these are optional there's nothing here that's

320
15:20.460 --> 15:22.120
required we can rely on

321
15:22.120 --> 15:27.900
default configuration settings but the policy tag is where we have our W-LAMs

322
15:27.900 --> 15:28.440
and so if I don't

323
15:28.440 --> 15:33.200
configure a policy tag I have no SSIDs so this part we're going to have to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

323
15:28.440 --> 15:33.200
configure a policy tag I have no SSIDs so this part we're going to have to

324
15:33.200 --> 15:34.440
configure and in a

325
15:34.440 --> 15:39.040
basic environment that might be the only tag we have to configure and yet all

326
15:39.040 --> 15:40.440
of the AP configurations

327
15:40.440 --> 15:46.600
are coming from these three tags all right last question here what aspect of

328
15:46.600 --> 15:48.120
configuration is

329
15:48.120 --> 15:53.460
unique to AROS controllers so we just said in iOSXE we're going to use all of

330
15:53.460 --> 15:55.880
these tags but on the

331
15:55.880 --> 16:01.740
on the AROS side of things we're going to use AP groups the site tags and AP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

331
15:55.880 --> 16:01.740
on the AROS side of things we're going to use AP groups the site tags and AP

332
16:01.740 --> 16:02.760
groups are sort of

333
16:02.760 --> 16:09.560
the same thing with site tags being used for iOSXE and AP groups being for AROS

334
16:09.560 --> 16:11.240
but that parallel

335
16:11.240 --> 16:15.250
can break down a couple of different ways so we just think of it as a sort of

336
16:15.250 --> 16:16.200
relationship

337
16:16.200 --> 16:22.440
either way what we find is I've got a bunch of APs and I'm using AROS I want to

338
16:22.440 --> 16:23.080
apply a

339
16:23.080 --> 16:28.800
configuration like my SSIDs to all of these APs how do I do that well I bundle

340
16:28.800 --> 16:30.040
all these together
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

340
16:28.800 --> 16:30.040
all these together

341
16:30.040 --> 16:37.470
in an AP group and I really map them to the AP group so at that point the APs

342
16:37.470 --> 16:38.840
are mapped to the

343
16:38.840 --> 16:44.460
AP group the W-LAMs and SSIDs are configured via the AP group and that brings

344
16:44.460 --> 16:45.960
our configuration

345
16:45.960 --> 16:51.240
into all of those APs so once again the goal of this quiz is to make sure that

346
16:51.240 --> 16:51.880
we identify

347
16:51.880 --> 16:55.900
areas of weakness if there's anything in here that caused any trip ups then be

348
16:55.900 --> 16:56.680
sure to go back

349
16:56.680 --> 16:59.870
and review the appropriate skill in order to make sure we've got it all down

350
16:59.870 --> 17:00.840
otherwise we can move
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

350
16:59.870 --> 17:00.840
otherwise we can move

351
17:00.840 --> 17:02.600
on to wireless security