WEBVTT

1
00:00.000 --> 00:03.680
Yes, it's time to talk about the more legacy,

2
00:03.680 --> 00:06.080
Arrow-esque wireless LAN controllers.

3
00:06.080 --> 00:10.160
Why are we still talking about these even though Cisco no longer sells them?

4
00:10.160 --> 00:11.820
Well, there's two primary reasons.

5
00:11.820 --> 00:17.720
First of all, the reality is that there are still probably hundreds of

6
00:17.720 --> 00:18.560
thousands of these

7
00:18.560 --> 00:21.080
things in production that works around the globe.

8
00:21.080 --> 00:24.890
So you're very likely to run into this at some point if you don't already

9
00:24.890 --> 00:25.520
actively

10
00:25.520 --> 00:26.520
manage one.

11
00:26.520 --> 00:31.520
However, the other reason is simply because Cisco wants us to be sure that we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:26.520 --> 00:31.520
However, the other reason is simply because Cisco wants us to be sure that we

12
00:31.520 --> 00:32.240
can support

13
00:32.240 --> 00:38.840
them and therefore it's within scope of this exam and therefore of this course.

14
00:38.840 --> 00:43.080
And so whether it's a situation of, hey, we need to manage one of these in

15
00:43.080 --> 00:43.920
production,

16
00:43.920 --> 00:48.350
or simply I need to make sure that I understand all of the topics within the

17
00:48.350 --> 00:49.320
blueprint, either

18
00:49.320 --> 00:52.120
way, it's a pretty good reason to go ahead and study it.

19
00:52.120 --> 00:57.560
So as we know, iOS XE is the modern platform for wireless LAN controllers.

20
00:57.560 --> 01:00.920
This is what runs on our catalyst, 9800s.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:57.560 --> 01:00.920
This is what runs on our catalyst, 9800s.

21
01:00.920 --> 01:05.750
Again, catalyst now can mean pretty much anything Cisco has decided and

22
01:05.750 --> 01:06.920
therefore we're going

23
01:06.920 --> 01:11.560
to see it running our wireless LAN controller architecture now.

24
01:11.560 --> 01:16.820
However, before this, we had the old Air OS.

25
01:16.820 --> 01:20.510
This came from an acquisition that Cisco made right around the time I entered

26
01:20.510 --> 01:21.560
into the industry.

27
01:21.560 --> 01:24.400
So it's been a couple of years to say the least.

28
01:24.400 --> 01:30.110
They acquired a company called AirSpace spelled like this and AirSpace had
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:24.400 --> 01:30.110
They acquired a company called AirSpace spelled like this and AirSpace had

29
01:30.110 --> 01:31.560
created the concept

30
01:31.560 --> 01:35.520
of lightweight architecture along with the tunneling mechanism that eventually

31
01:35.520 --> 01:35.920
became

32
01:35.920 --> 01:37.520
CapWap.

33
01:37.520 --> 01:41.800
And so these ran on more legacy wireless LAN controller hardware, including

34
01:41.800 --> 01:42.520
things like

35
01:42.520 --> 01:50.440
the 5500s and the 3500s and even going back a little bit further, the 2500s.

36
01:50.440 --> 01:55.040
And this is the wireless LAN controller that I'm going to be using to demo Air

37
01:55.040 --> 01:55.800
OS in our

38
01:55.800 --> 01:57.760
lab today.

39
01:57.760 --> 02:03.880
Now by and large, when Cisco developed iOS XE architecture, they borrowed most
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:57.760 --> 02:03.880
Now by and large, when Cisco developed iOS XE architecture, they borrowed most

40
02:03.880 --> 02:04.440
of what

41
02:04.440 --> 02:06.920
happens on the AirOS side.

42
02:06.920 --> 02:11.160
However, they still changed the way that we do the configuration.

43
02:11.160 --> 02:14.720
And so it's important for us to still figure out exactly how we can do the same

44
02:14.720 --> 02:15.360
things in

45
02:15.360 --> 02:16.800
AirOS.

46
02:16.800 --> 02:22.680
One of the biggest differences is that Cisco created the concept of tags for

47
02:22.680 --> 02:23.520
iOS XE and

48
02:23.520 --> 02:28.600
we just don't have tags on the AirOS side.

49
02:28.600 --> 02:33.620
And another major difference is that while we use SVIs on the iOS XE side,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:28.600 --> 02:33.620
And another major difference is that while we use SVIs on the iOS XE side,

50
02:33.620 --> 02:35.000
because it's

51
02:35.000 --> 02:41.800
an iOS XE device, it's basically a catalyst switch we can use VLAN interfaces.

52
02:41.800 --> 02:44.880
Well on the AirOS side, we're not going to use that either.

53
02:44.880 --> 02:46.040
So what do we use over here?

54
02:46.040 --> 02:50.880
Well instead of tags, we're going to use the concept of AP groups.

55
02:50.880 --> 02:55.520
AP groups are going to allow us to take a collection of APs and group them

56
02:55.520 --> 02:56.400
together,

57
02:56.400 --> 03:01.930
as the name implies, and take a configuration and apply it to all of the APs in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:56.400 --> 03:01.930
as the name implies, and take a configuration and apply it to all of the APs in

58
03:01.930 --> 03:02.640
a single

59
03:02.640 --> 03:04.320
group.

60
03:04.320 --> 03:07.730
So we'll use those instead of tags in order to bring our configuration together

61
03:07.730 --> 03:08.080
on the

62
03:08.080 --> 03:09.760
AirOS side.

63
03:09.760 --> 03:16.440
And instead of using SVIs, we're going to use the concept of dynamic interfaces

64
03:16.440 --> 03:16.480
.

65
03:16.480 --> 03:20.800
The whole conversation about interfaces on AirOS is very, very important.

66
03:20.800 --> 03:25.280
We have virtual interfaces, management interfaces, redundancy interfaces.

67
03:25.280 --> 03:28.960
And so this is a conversation that showed up in our CCNA course.

68
03:28.960 --> 03:33.200
If you need to refresher on how interfaces come together on AirOS, I highly
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
03:28.960 --> 03:33.200
If you need to refresher on how interfaces come together on AirOS, I highly

69
03:33.200 --> 03:33.960
recommend

70
03:33.960 --> 03:37.200
taking a look at those topics within CCNA.

71
03:37.200 --> 03:40.480
However, we are going to need to rely on these.

72
03:40.480 --> 03:43.720
And so we'll take a look at the configuration of dynamic interfaces and

73
03:43.720 --> 03:44.760
management interfaces

74
03:44.760 --> 03:47.560
here on AirOS.

75
03:47.560 --> 03:52.720
So as we explore the similarities now, we're going to still find that Cisco

76
03:52.720 --> 03:53.640
likes to use

77
03:53.640 --> 03:55.040
WLANs.

78
03:55.040 --> 04:02.280
This concept of wireless LANs or WLANs is a combination of our SSID and our SS
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
03:55.040 --> 04:02.280
This concept of wireless LANs or WLANs is a combination of our SSID and our SS

79
04:02.280 --> 04:04.560
ID configurations.

80
04:04.560 --> 04:10.600
And so this is going to remain the same between iOSXE and AirOS.

81
04:10.600 --> 04:16.650
But there is a little bit of a nuanced difference between how we do it on AirOS

82
04:16.650 --> 04:18.080
versus iOSXE.

83
04:18.080 --> 04:27.050
Specifically on iOSXE, I'm going to apply my WLAN via the policy tag and the

84
04:27.050 --> 04:28.000
policy

85
04:28.000 --> 04:30.360
profile.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
04:28.000 --> 04:30.360
profile.

86
04:30.360 --> 04:35.230
And so this is an important part of how we bring the configuration together on

87
04:35.230 --> 04:35.960
iOSXE.

88
04:35.960 --> 04:41.610
And this is how we ultimately apply the VLAN because we're going to map it to

89
04:41.610 --> 04:42.840
an SVI,

90
04:42.840 --> 04:45.600
which directly maps it to a VLAN on iOSXE.

91
04:45.600 --> 04:50.950
Well, we've already said on AirOS that we don't have the ability to create SVIs

92
04:50.950 --> 04:51.320
and

93
04:51.320 --> 04:52.640
we're not using tags.

94
04:52.640 --> 04:57.130
So instead, what we're going to find is that we're going to take a WLAN and we

95
04:57.130 --> 04:57.440
're just

96
04:57.440 --> 05:02.920
going to directly map it to one of those interfaces.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
04:57.440 --> 05:02.920
going to directly map it to one of those interfaces.

97
05:02.920 --> 05:07.420
In production networks, for the most part, we're going to map this to a dynamic

98
05:07.420 --> 05:08.400
interface.

99
05:08.400 --> 05:12.480
The dynamic interface is going to have a VLAN associated with it.

100
05:12.480 --> 05:16.610
However, in smaller environments, especially remote sites and, hey, lab

101
05:16.610 --> 05:17.560
environments such

102
05:17.560 --> 05:21.640
as mine, we can also apply this to the management interface.

103
05:21.640 --> 05:24.480
And oftentimes this is going to be an untagged VLAN.

104
05:24.480 --> 05:28.520
It doesn't have to be, but we at least have that choice.

105
05:28.520 --> 05:31.040
We'll say one or the other.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
05:28.520 --> 05:31.040
We'll say one or the other.

106
05:31.040 --> 05:35.680
But this, in this way, we're going to take the SSID and get it to a VLAN.

107
05:35.680 --> 05:36.880
So we see that either way.

108
05:36.880 --> 05:42.160
We get it to a VLAN on iOSXE via the policy tag and the policy profile, whereas

109
05:42.160 --> 05:43.280
in AirOS,

110
05:43.280 --> 05:49.240
we're going to do it via our dynamic, really, either one, our dynamic interface

111
05:49.240 --> 05:49.920
mapping

112
05:49.920 --> 05:52.920
or our management interface mapping.

113
05:52.920 --> 05:57.960
Now, let's have a quick note on this concept of dynamic interfaces.

114
05:57.960 --> 06:02.640
So a dynamic interface we're going to find is very similar to an SVI.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

114
05:57.960 --> 06:02.640
So a dynamic interface we're going to find is very similar to an SVI.

115
06:02.640 --> 06:06.880
In that, we're going to have to provide it with a VLAN ID.

116
06:06.880 --> 06:11.330
And this VLAN ID is going to get mapped to the trunk that connects to the

117
06:11.330 --> 06:12.240
wireless LAN

118
06:12.240 --> 06:13.240
controller.

119
06:13.240 --> 06:14.760
So that's pretty handy.

120
06:14.760 --> 06:17.880
It's also going to have IP address information.

121
06:17.880 --> 06:19.480
So it's going to have an IP address.

122
06:19.480 --> 06:21.600
It's going to have a mask.

123
06:21.600 --> 06:25.680
But interestingly, it's also going to have a gateway address.

124
06:25.680 --> 06:30.390
So we need to create this dynamic interface almost as if we're creating a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
06:25.680 --> 06:30.390
So we need to create this dynamic interface almost as if we're creating a

125
06:30.390 --> 06:31.200
little subnet,

126
06:31.200 --> 06:33.720
a little network of our own.

127
06:33.720 --> 06:38.470
And so once again, for the most part, our AirOS, WLANs end up getting mapped to

128
06:38.470 --> 06:38.680
one

129
06:38.680 --> 06:39.680
of these.

130
06:39.680 --> 06:43.240
And that is ultimately how we get mapped to our VLAN ID.

131
06:43.240 --> 06:46.960
So I want to point this out because it is just a little bit different from an S

132
06:46.960 --> 06:47.240
VI, but

133
06:47.240 --> 06:52.850
it will end up feeling very similar to how we bring that configuration together

134
06:52.850 --> 06:53.160
on the

135
06:53.160 --> 06:56.360
iOS XE side.

136
06:56.360 --> 07:01.560
Now furthermore, we have to worry about our CAPWAP termination.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

136
06:56.360 --> 07:01.560
Now furthermore, we have to worry about our CAPWAP termination.

137
07:01.560 --> 07:06.870
And our CAPWAP tunnels are going to get terminated onto the wireless LAN

138
07:06.870 --> 07:08.080
controller.

139
07:08.080 --> 07:12.840
So our APs are going to form CAPWAP here to the wireless LAN controller.

140
07:12.840 --> 07:16.680
But the question is, what are we landing on with the wireless LAN controller

141
07:16.680 --> 07:17.160
here?

142
07:17.160 --> 07:22.520
How exactly are we going to allow CAPWAP termination to happen?

143
07:22.520 --> 07:26.640
Well with our iOS XE, we allowed this to happen on an SVI.

144
07:26.640 --> 07:31.360
With our wireless LAN controller, we're going to also allow this to happen on a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

144
07:26.640 --> 07:31.360
With our wireless LAN controller, we're going to also allow this to happen on a

145
07:31.360 --> 07:31.960
dynamic

146
07:31.960 --> 07:33.360
interface.

147
07:33.360 --> 07:36.680
So this is a dynamic interface.

148
07:36.680 --> 07:41.590
And once again, we can either discover this via broadcast or via some kind of

149
07:41.590 --> 07:42.280
layer three

150
07:42.280 --> 07:46.360
mechanism, either DHCP option 43 or DNS.

151
07:46.360 --> 07:49.600
So either way, we'd be connecting to an IP address.

152
07:49.600 --> 07:53.240
And the dynamic interface does have an IP address.

153
07:53.240 --> 07:57.440
But again, broadcast will work in a small environment or lab environment.

154
07:57.440 --> 08:00.320
And we are also bound to a VLAN.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

154
07:57.440 --> 08:00.320
And we are also bound to a VLAN.

155
08:00.320 --> 08:04.470
And so we just need to think through how those access points are going to land

156
08:04.470 --> 08:04.920
on one

157
08:04.920 --> 08:06.600
of those dynamic interfaces.

158
08:06.600 --> 08:10.880
However, we also need to make sure that we have an option enabled on the

159
08:10.880 --> 08:12.600
dynamic interface.

160
08:12.600 --> 08:20.520
And that option is going to be known as dynamic AP management.

161
08:20.520 --> 08:26.200
We'll see that we have to enable this in order to allow for CAPWAP termination.

162
08:26.200 --> 08:29.760
If we don't have that enabled, the access points will not be able to attach on

163
08:29.760 --> 08:30.040
that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

163
08:29.760 --> 08:30.040
that

164
08:30.040 --> 08:33.160
interface, even if they try to do so.

165
08:33.160 --> 08:38.200
Now even though we can do this on the dynamic interface, we can also do this on

166
08:38.200 --> 08:39.040
the management

167
08:39.040 --> 08:40.840
interface.

168
08:40.840 --> 08:44.560
The only difference between the dynamic and management interface is that the

169
08:44.560 --> 08:45.040
management

170
08:45.040 --> 08:48.680
interface is how I access the graphical user interface.

171
08:48.680 --> 08:53.560
And generally speaking, how I SSH or otherwise interface with the wireless LAN

172
08:53.560 --> 08:54.560
controller.

173
08:54.560 --> 08:57.990
And so do we want to use the management interface to also terminate access

174
08:57.990 --> 08:58.560
points?

175
08:58.560 --> 08:59.560
Usually not.

176
08:59.560 --> 09:03.640
Again, not in large scale production networks, but in small environments like
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

176
08:59.560 --> 09:03.640
Again, not in large scale production networks, but in small environments like

177
09:03.640 --> 09:05.080
the lab environment,

178
09:05.080 --> 09:09.580
that is exactly what we're going to probably end up doing in a lot of

179
09:09.580 --> 09:10.560
situations.

180
09:10.560 --> 09:15.440
But with all that said, let's take a quick tour, I suppose, of the wireless LAN

181
09:15.440 --> 09:16.320
controller

182
09:16.320 --> 09:17.960
interface for AROS.

183
09:17.960 --> 09:19.960
As we see, it's very, very different.

184
09:19.960 --> 09:25.200
And it definitely starts to feel a little bit legacy with the configuration

185
09:25.200 --> 09:26.120
here, with

186
09:26.120 --> 09:27.120
the interface.

187
09:27.120 --> 09:31.000
It feels like a graphical user interface from 10 or 15 years ago.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

187
09:27.120 --> 09:31.000
It feels like a graphical user interface from 10 or 15 years ago.

188
09:31.000 --> 09:34.840
And that's how it should feel because that's how long ago it was created.

189
09:34.840 --> 09:39.470
So as far as navigating the user interface, for the most part, we're going to

190
09:39.470 --> 09:40.440
pay attention

191
09:40.440 --> 09:43.240
to all of these different tabs at the top.

192
09:43.240 --> 09:45.560
For example, the monitor tab is the default tab.

193
09:45.560 --> 09:48.830
It's going to allow us to look and see, hey, what's the IP address of the

194
09:48.830 --> 09:49.640
controller?

195
09:49.640 --> 09:51.440
What's the current situation?

196
09:51.440 --> 09:55.080
Number of rogues out there, number of access points that are up right now.

197
09:55.080 --> 09:58.280
We don't have anything online and so on and so forth.

198
09:58.280 --> 10:01.420
I can look at my access points over here and drill into some other
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

198
09:58.280 --> 10:01.420
I can look at my access points over here and drill into some other

199
10:01.420 --> 10:02.480
configurations.

200
10:02.480 --> 10:07.120
But for the most part, this landing dashboard page is going to give us a lot of

201
10:07.120 --> 10:08.040
information.

202
10:08.040 --> 10:12.070
I can also click on WLANs here and then see my list of WLANs, which is

203
10:12.070 --> 10:13.440
currently empty.

204
10:13.440 --> 10:17.310
We're going to fill that by the end of this skill and we can just create a new

205
10:17.310 --> 10:17.920
one right

206
10:17.920 --> 10:18.920
here.

207
10:18.920 --> 10:20.600
Controller is an interesting tab.

208
10:20.600 --> 10:24.000
This is where we're going to be able to configure our interfaces, which will be

209
10:24.000 --> 10:25.280
very important,

210
10:25.280 --> 10:26.800
as we've mentioned a few times.

211
10:26.800 --> 10:31.280
We can figure our mobility group and RF group here as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

211
10:26.800 --> 10:31.280
We can figure our mobility group and RF group here as well.

212
10:31.280 --> 10:34.710
And generally speaking, we're going to see things like our ability to deploy

213
10:34.710 --> 10:35.320
lag, which

214
10:35.320 --> 10:37.640
is port channeling or link aggregating.

215
10:37.640 --> 10:39.400
That's what lag stands for.

216
10:39.400 --> 10:42.000
The front facing ports on our wireless LAN controller.

217
10:42.000 --> 10:44.720
That's an important configuration as well there.

218
10:44.720 --> 10:48.680
And then wireless is going to allow us to configure our individual band

219
10:48.680 --> 10:49.520
networks as well

220
10:49.520 --> 10:51.280
as radio resource management.

221
10:51.280 --> 10:57.100
We've got the ability to do a lot of network configuration for 5 GHz and 2.4

222
10:57.100 --> 10:58.360
GHz in here.

223
10:58.360 --> 11:02.250
Lots to do on the wireless tab, as we might imagine, on a wireless LAN
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

223
10:58.360 --> 11:02.250
Lots to do on the wireless tab, as we might imagine, on a wireless LAN

224
11:02.250 --> 11:02.680
controller.

225
11:02.680 --> 11:07.650
We is not where we decide how to encrypt or authenticate individual wireless

226
11:07.650 --> 11:08.600
networks.

227
11:08.600 --> 11:11.240
Instead, it's where we perform our AAA configuration.

228
11:11.240 --> 11:13.820
So setting up a radius or tacac server.

229
11:13.820 --> 11:17.920
That is where we would perform that configuration.

230
11:17.920 --> 11:22.030
And then management is where we can set up individual users, allow for telnet

231
11:22.030 --> 11:22.600
and SSH,

232
11:22.600 --> 11:27.280
as well as HTTP/HETPS, into the controller itself.

233
11:27.280 --> 11:28.780
Lastly commands.

234
11:28.780 --> 11:32.730
This is where we can perform a software upgrade or for that matter just to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

234
11:28.780 --> 11:32.730
This is where we can perform a software upgrade or for that matter just to

235
11:32.730 --> 11:34.300
reboot the controller.

236
11:34.300 --> 11:39.220
So there's a little bit of a flyover as far as the configuration is concerned.

237
11:39.220 --> 11:43.490
But as we go into individual components like the WLANs tab here when we're

238
11:43.490 --> 11:44.260
coming in here

239
11:44.260 --> 11:47.360
to do the configuration, we'll start to get a sense of how all of this

240
11:47.360 --> 11:48.420
configuration comes

241
11:48.420 --> 11:49.620
together.

242
11:49.620 --> 11:53.610
Most of our configuration time will be spent on WLANs controller and a little

243
11:53.610 --> 11:55.020
bit of wireless.

244
11:55.020 --> 11:59.740
But even then mostly wireless LANs and controller, especially those interfaces,

245
11:59.740 --> 12:00.060
is where we're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

245
11:59.740 --> 12:00.060
is where we're

246
12:00.060 --> 12:01.380
going to spend a lot of our time.