WEBVTT

1
00:00.000 --> 00:04.540
Well, as mentioned, wireless stations are able to roam between our wireless

2
00:04.540 --> 00:06.320
lane controllers

3
00:06.320 --> 00:10.120
if access points are connected to different ones.

4
00:10.120 --> 00:14.750
But in order for us to support this, the wireless lane controllers must be in

5
00:14.750 --> 00:16.040
the same mobility

6
00:16.040 --> 00:17.400
group.

7
00:17.400 --> 00:21.390
The mobility group is a configuration that we're going to place onto the

8
00:21.390 --> 00:22.220
wireless lane

9
00:22.220 --> 00:26.020
controllers and it's going to alert them to other wireless lane controllers

10
00:26.020 --> 00:26.480
that are

11
00:26.480 --> 00:31.680
responsible for access points that will allow roaming.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:26.480 --> 00:31.680
responsible for access points that will allow roaming.

12
00:31.680 --> 00:35.380
Now we have to evaluate our wireless network and decide which access points we

13
00:35.380 --> 00:35.800
want to

14
00:35.800 --> 00:37.400
support roaming between.

15
00:37.400 --> 00:41.020
For example, if we have a headquarters location, we probably want all of the

16
00:41.020 --> 00:41.880
access points,

17
00:41.880 --> 00:46.000
regardless of their wireless lane controller attachment, to allow for roaming

18
00:46.000 --> 00:46.800
because people

19
00:46.800 --> 00:49.600
can walk from one access point to the other.

20
00:49.600 --> 00:53.880
But if this is a campus environment and maybe we've got buildings throughout,

21
00:53.880 --> 00:54.360
yeah, these

22
00:54.360 --> 00:59.230
are buildings from above here, buildings throughout the campus, are we going to

23
00:59.230 --> 01:00.000
want people to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:59.230 --> 01:00.000
want people to

24
01:00.000 --> 01:02.560
be able to roam from one building to another?

25
01:02.560 --> 01:06.440
And for that matter, is there enough wireless signal to make it from one

26
01:06.440 --> 01:07.800
building to another?

27
01:07.800 --> 01:11.650
And so if all the access points here are attached to one wireless lane

28
01:11.650 --> 01:12.720
controller, all

29
01:12.720 --> 01:16.740
the access points over here are attached to a different one, do we want these

30
01:16.740 --> 01:17.380
wireless

31
01:17.380 --> 01:20.560
lane controllers to be part of the same mobility group?

32
01:20.560 --> 01:24.960
That's part of our wireless design, it's a little bit outside the scope of an

33
01:24.960 --> 01:25.880
exam and

34
01:25.880 --> 01:29.840
a course such as this, but we do need to be aware of what we're configuring

35
01:29.840 --> 01:30.440
when we do
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:29.840 --> 01:30.440
when we do

36
01:30.440 --> 01:33.080
configure the mobility group.

37
01:33.080 --> 01:37.470
Now the mobility group is going to consist of certain parameters that we're

38
01:37.470 --> 01:37.960
going to

39
01:37.960 --> 01:39.360
have to configure.

40
01:39.360 --> 01:42.360
For example, we're going to have to give it a name.

41
01:42.360 --> 01:45.180
And this name is going to have to be consistent among the different wireless

42
01:45.180 --> 01:45.920
lane controllers

43
01:45.920 --> 01:47.640
as we might imagine.

44
01:47.640 --> 01:53.140
We can also, by the way, have up to, let's see, it says 24 wireless lane

45
01:53.140 --> 01:54.400
controllers in a

46
01:54.400 --> 01:56.000
single mobility group.

47
01:56.000 --> 01:57.600
So that's per group.

48
01:57.600 --> 01:59.960
That feels like a whole lot of wireless lane controllers.

49
01:59.960 --> 02:03.600
I'm going to guess that we're not going to hit this limit anytime soon, because
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
01:59.960 --> 02:03.600
I'm going to guess that we're not going to hit this limit anytime soon, because

50
02:03.600 --> 02:03.880
by the

51
02:03.880 --> 02:06.980
time we're talking about that many wireless lane controllers, we're probably

52
02:06.980 --> 02:07.520
talking about

53
02:07.520 --> 02:12.680
access points that there's really no physical way to roam between the two.

54
02:12.680 --> 02:15.710
So we're naturally talking about a very large set of wireless lane controllers

55
02:15.710 --> 02:17.320
at that point.

56
02:17.320 --> 02:23.780
They are also going to have to know the IPs and the MAC addresses of the other

57
02:23.780 --> 02:24.680
wireless

58
02:24.680 --> 02:27.720
lane controllers.

59
02:27.720 --> 02:31.200
We're going to have to get in there and let the wireless lane controllers know
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

59
02:27.720 --> 02:31.200
We're going to have to get in there and let the wireless lane controllers know

60
02:31.200 --> 02:31.600
where the

61
02:31.600 --> 02:36.640
other controllers are so they can begin their communications.

62
02:36.640 --> 02:40.600
And furthermore, an interesting part of all of this is as we've said, Cisco has

63
02:40.600 --> 02:41.280
two different

64
02:41.280 --> 02:43.280
types of wireless lane controllers.

65
02:43.280 --> 02:47.040
They have the AOS, legacy type of controllers.

66
02:47.040 --> 02:51.560
They also have the iOS XE, catalyst 9800 wireless lane controllers.

67
02:51.560 --> 02:53.160
These are the modern ones.

68
02:53.160 --> 02:56.800
And both of these can be in the same mobility group.

69
02:56.800 --> 03:01.700
Cisco has done as much as possible to make the migration from the older
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
02:56.800 --> 03:01.700
Cisco has done as much as possible to make the migration from the older

70
03:01.700 --> 03:02.720
platform to the

71
03:02.720 --> 03:05.280
modern platform as seamless as possible.

72
03:05.280 --> 03:08.880
And one of the ways they did this is by including both of them from a

73
03:08.880 --> 03:10.480
capabilities perspective

74
03:10.480 --> 03:13.560
within a mobility group.

75
03:13.560 --> 03:17.260
Now something we'll have to consider from a configuration perspective is by

76
03:17.260 --> 03:18.040
default as

77
03:18.040 --> 03:22.760
these communications happen, it's going to default to unicast communications.

78
03:22.760 --> 03:27.940
So if we have three, four, five, six wireless lane controllers, we should know

79
03:27.940 --> 03:28.600
that it's

80
03:28.600 --> 03:30.000
going to just use unicast.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
03:28.600 --> 03:30.000
going to just use unicast.

81
03:30.000 --> 03:34.130
We don't need to worry about a multicast infrastructure supporting the mobility

82
03:34.130 --> 03:34.520
group

83
03:34.520 --> 03:35.520
configuration.

84
03:35.520 --> 03:41.040
But as that number increases, we're going to see that we're going to switch to

85
03:41.040 --> 03:41.920
multicast.

86
03:41.920 --> 03:45.840
And so at this point, we will need a multicast architecture, which makes sense.

87
03:45.840 --> 03:49.920
We don't want a full mesh of communications happening leveraging unicast.

88
03:49.920 --> 03:52.560
It's going to be very inefficient.

89
03:52.560 --> 03:56.580
So keep in mind from the previous video, what it is we're trying to accomplish

90
03:56.580 --> 03:57.120
here.

91
03:57.120 --> 04:00.000
We have these three different types of roams.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
03:57.120 --> 04:00.000
We have these three different types of roams.

92
04:00.000 --> 04:05.280
And the first one is that intra controller layer two Rome.

93
04:05.280 --> 04:08.940
This happens within a wireless lane controller, meaning that we've got two

94
04:08.940 --> 04:09.720
access points

95
04:09.720 --> 04:13.200
here and we're roaming between the two.

96
04:13.200 --> 04:16.520
We might argue that we don't need to let anybody else know about this.

97
04:16.520 --> 04:22.460
And yet Cisco has it in the architecture such that I'm going to alert all of

98
04:22.460 --> 04:23.080
the other

99
04:23.080 --> 04:29.280
wireless lane controllers in my mobility group that this Rome occurred.

100
04:29.280 --> 04:32.640
So we're all tracking where all of the stations are.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

100
04:29.280 --> 04:32.640
So we're all tracking where all of the stations are.

101
04:32.640 --> 04:36.310
That way, if we do Rome to another one of these wireless lane controllers and

102
04:36.310 --> 04:36.840
perform

103
04:36.840 --> 04:42.000
an inter layer three Rome, well, at that point, we can make that happen.

104
04:42.000 --> 04:45.630
And the mobility group wireless lane controllers already know a little bit

105
04:45.630 --> 04:46.720
about that station.

106
04:46.720 --> 04:49.680
Now we do have those other two as well.

107
04:49.680 --> 04:52.120
And the other two are going to come with different implications.

108
04:52.120 --> 04:56.350
The inter layer three, as we said, this is when we go from one wireless lane

109
04:56.350 --> 04:57.120
controller

110
04:57.120 --> 04:59.440
to the other.

111
04:59.440 --> 05:01.920
We're going to need to establish the anchor controller.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
04:59.440 --> 05:01.920
We're going to need to establish the anchor controller.

112
05:01.920 --> 05:03.240
So that's the first one.

113
05:03.240 --> 05:06.320
And then the foreign controller is the second one.

114
05:06.320 --> 05:10.120
And that's going to be a little bit arguably the more complex situation.

115
05:10.120 --> 05:13.120
But the idea is simply that we have layer three segmentation between the

116
05:13.120 --> 05:13.680
wireless lane

117
05:13.680 --> 05:14.760
controllers.

118
05:14.760 --> 05:19.160
Very likely they're in different locations and different buildings.

119
05:19.160 --> 05:23.520
Or we simply have the inter layer two, which is a little simpler.

120
05:23.520 --> 05:26.580
It usually means that they're in the same building because they're on the same

121
05:26.580 --> 05:26.920
layer

122
05:26.920 --> 05:28.080
two network.

123
05:28.080 --> 05:32.920
And at this point, this is a simple handoff between wireless lane controllers.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

123
05:28.080 --> 05:32.920
And at this point, this is a simple handoff between wireless lane controllers.

124
05:32.920 --> 05:36.980
But again, those communications have to happen and in all of these scenarios,

125
05:36.980 --> 05:37.680
we are going

126
05:37.680 --> 05:40.920
to require mobility group configuration.

127
05:40.920 --> 05:46.640
Now lastly, we have one interesting topic of conversation, which is the

128
05:46.640 --> 05:48.600
mobility domain.

129
05:48.600 --> 05:54.470
Embrability domain is going to be a set of wireless lane controllers in which

130
05:54.470 --> 05:55.120
we have

131
05:55.120 --> 05:59.680
up to three mobility groups.

132
05:59.680 --> 06:04.880
Now we might think that the way this works is we configure a mobility domain.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

132
05:59.680 --> 06:04.880
Now we might think that the way this works is we configure a mobility domain.

133
06:04.880 --> 06:09.000
And hierarchically speaking, we create the domain and then we create the three

134
06:09.000 --> 06:09.680
different

135
06:09.680 --> 06:12.240
groups within it and we can manage this.

136
06:12.240 --> 06:14.480
But this isn't exactly how it comes together.

137
06:14.480 --> 06:18.080
It's kind of interesting how this gets configured.

138
06:18.080 --> 06:22.220
We're doing mostly as we're relaxing requirements around mobility group

139
06:22.220 --> 06:23.360
configuration.

140
06:23.360 --> 06:27.200
Because what happens is when I log into one wireless lane controller and I let

141
06:27.200 --> 06:27.600
it know

142
06:27.600 --> 06:32.310
about another wireless lane controller's IP and MAC address, I'm going to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

142
06:27.600 --> 06:32.310
about another wireless lane controller's IP and MAC address, I'm going to

143
06:32.310 --> 06:32.960
specify the

144
06:32.960 --> 06:35.200
group that it's a part of.

145
06:35.200 --> 06:38.640
Now this group is in most cases going to be the same group.

146
06:38.640 --> 06:43.520
Maybe this is group CBT and so I'm going to specify this as group CBT.

147
06:43.520 --> 06:47.920
But Cisco does allow me to specify up to two other mobility groups as part of

148
06:47.920 --> 06:48.440
this.

149
06:48.440 --> 06:53.150
And this collection of configurations as I add them together, this is the

150
06:53.150 --> 06:55.200
mobility domain.

151
06:55.200 --> 06:58.080
It's interesting because I never actually define the domain.

152
06:58.080 --> 07:00.240
I never name the domain.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

152
06:58.080 --> 07:00.240
I never name the domain.

153
07:00.240 --> 07:03.460
It's a strange methodology relative to what we might expect with having a

154
07:03.460 --> 07:04.080
little more

155
07:04.080 --> 07:05.920
concrete architecture.

156
07:05.920 --> 07:09.850
But it does come together in such a way that we can support multiple mobility

157
07:09.850 --> 07:10.840
groups on

158
07:10.840 --> 07:12.560
wireless lane controllers.

159
07:12.560 --> 07:16.350
Now as we might imagine needing to support this many mobility groups, we can

160
07:16.350 --> 07:16.800
already

161
07:16.800 --> 07:21.430
support up to 24 wireless lane controllers per group would pretty well imply

162
07:21.430 --> 07:22.000
that we're

163
07:22.000 --> 07:24.520
talking about very large deployments.

164
07:24.520 --> 07:27.810
And at the same time, it's just something to be aware of, especially around the

165
07:27.810 --> 07:28.200
concept

166
07:28.200 --> 07:34.000
of how many mobility groups can be configured per mobility domain.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

166
07:28.200 --> 07:34.000
of how many mobility groups can be configured per mobility domain.

167
07:34.000 --> 07:38.400
And that's going to more or less map out to large organizations across multiple

168
07:38.400 --> 07:39.120
locations.