WEBVTT

1
00:00.000 --> 00:03.160
All right, let's go ahead and answer these challenge questions.

2
00:03.160 --> 00:06.320
They're really designed to make us think about the architecture and make sure

3
00:06.320 --> 00:06.800
we understand

4
00:06.800 --> 00:10.420
that architecture, but also start to think about how we'd go about making

5
00:10.420 --> 00:11.200
configuration

6
00:11.200 --> 00:14.200
changes on the graphical user interface.

7
00:14.200 --> 00:17.550
The first question, if we're lying on layer two broadcasts for the wireless LAN

8
00:17.550 --> 00:18.080
controller

9
00:18.080 --> 00:23.120
discovery of AP1, what VLAN must be enabled on this interface?

10
00:23.120 --> 00:26.440
Well, ideally this interface is going to be a trunk.

11
00:26.440 --> 00:29.280
And so the question is, how many VLANs need to be added?

12
00:29.280 --> 00:32.480
Well, within the context of this question, we really only need one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:29.280 --> 00:32.480
Well, within the context of this question, we really only need one.

13
00:32.480 --> 00:37.920
We need VLAN 100 because VLAN 100 is what AP1 is on.

14
00:37.920 --> 00:43.640
And therefore we need to make sure AP1 can send a broadcast message and land on

15
00:43.640 --> 00:43.960
the

16
00:43.960 --> 00:47.600
SVI that's responsible for Capwep termination.

17
00:47.600 --> 00:52.990
Now we immediately are going to be left wondering about AP2, which is running

18
00:52.990 --> 00:54.520
on VLAN 200.

19
00:54.520 --> 00:57.920
And that's what the next question asks is, how can AP2 then find a connection

20
00:57.920 --> 00:58.080
to the

21
00:58.080 --> 00:59.080
wireless LAN controller?

22
00:59.080 --> 01:02.160
Well, we don't want to just rely on layer two broadcasts.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:59.080 --> 01:02.160
Well, we don't want to just rely on layer two broadcasts.

23
01:02.160 --> 01:06.440
Remember, we also have that DHCP option 43.

24
01:06.440 --> 01:12.520
And we also have the potential to use DNS or manual entries.

25
01:12.520 --> 01:17.310
As we've mentioned in the real world, the DHCP option 43 is very simple to

26
01:17.310 --> 01:18.040
include.

27
01:18.040 --> 01:21.080
A lot of our access points tend to use DHCP.

28
01:21.080 --> 01:25.240
And therefore we would just want to add it into our DHCP server and pass the IP

29
01:25.240 --> 01:25.760
address

30
01:25.760 --> 01:30.520
of this SVI to the access point during DHCP.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:25.760 --> 01:30.520
of this SVI to the access point during DHCP.

31
01:30.520 --> 01:35.040
But if we listed out any of those methods, then that would be perfectly viable.

32
01:35.040 --> 01:39.960
Next up AP1 appears to have connected, but its LED is flashing blue.

33
01:39.960 --> 01:41.120
And so what's going on?

34
01:41.120 --> 01:44.400
Well, we saw this when we first connected our access point.

35
01:44.400 --> 01:49.360
This means that it is receiving a software upgrade.

36
01:49.360 --> 01:52.640
So when the access point first connects to the wireless LAN controller, it's

37
01:52.640 --> 01:53.120
going to

38
01:53.120 --> 01:57.090
receive a software update if it's required because they really need to be

39
01:57.090 --> 01:57.720
running the

40
01:57.720 --> 01:58.960
same software version.

41
01:58.960 --> 02:02.850
We don't want to be running incompatible software versions between the wireless
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
01:58.960 --> 02:02.850
We don't want to be running incompatible software versions between the wireless

42
02:02.850 --> 02:03.800
LAN controller

43
02:03.800 --> 02:05.280
and the access point.

44
02:05.280 --> 02:09.940
And so blue, blue light flashing means that it's upgrading, whereas eventually

45
02:09.940 --> 02:10.360
we saw

46
02:10.360 --> 02:13.680
that it was solid green and that meant that it was fully connected.

47
02:13.680 --> 02:19.170
And always keep in mind that if the color is cycling, especially red to amber

48
02:19.170 --> 02:20.040
to green,

49
02:20.040 --> 02:24.410
or possibly red and green alternating, either way that implies that we're still

50
02:24.410 --> 02:24.920
looking

51
02:24.920 --> 02:27.780
for that wireless LAN controller when you have to come back here and think

52
02:27.780 --> 02:28.200
about our

53
02:28.200 --> 02:30.360
methods if we can't find one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:28.200 --> 02:30.360
methods if we can't find one.

54
02:30.360 --> 02:34.080
Lastly, which configuration must be deployed on a multiple wireless LAN

55
02:34.080 --> 02:34.960
controllers?

56
02:34.960 --> 02:39.480
So radio resource management can be unified among many APs in the same area.

57
02:39.480 --> 02:43.440
Well, now we're talking about wireless LAN controller to wireless LAN

58
02:43.440 --> 02:45.360
controller communications.

59
02:45.360 --> 02:50.000
And specifically, this is going to be an RF group configuration.

60
02:50.000 --> 02:52.400
It's not to be confused with mobility groups.

61
02:52.400 --> 02:57.040
Remember, RF groups are focused on that radio resource management.

62
02:57.040 --> 02:59.960
The idea is we've got other APs in the area.

63
02:59.960 --> 03:03.470
They're connected to this wireless LAN controller, but they can all hear each
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:59.960 --> 03:03.470
They're connected to this wireless LAN controller, but they can all hear each

64
03:03.470 --> 03:04.280
other speaking

65
03:04.280 --> 03:05.840
wirelessly.

66
03:05.840 --> 03:09.880
And therefore, we need to consider one another when it comes to channel

67
03:09.880 --> 03:11.000
selection as well

68
03:11.000 --> 03:16.760
as how much the power, which we're transmitting and so on and so forth.

69
03:16.760 --> 03:21.120
So now we have to wonder about how do we go about configuring that in the UI.

70
03:21.120 --> 03:23.560
So let's go ahead and flip over to that.

71
03:23.560 --> 03:27.690
And so remember that everything within our configuration sets going to be under

72
03:27.690 --> 03:28.560
configuration

73
03:28.560 --> 03:30.520
here and we looked at several things.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
03:28.560 --> 03:30.520
here and we looked at several things.

74
03:30.520 --> 03:34.720
Remember, VLAN interfaces are weirdly under layer two, but it's under VLANs.

75
03:34.720 --> 03:36.320
That part makes sense at least.

76
03:36.320 --> 03:39.040
We've got physical interface configurations up here.

77
03:39.040 --> 03:44.020
So adding VLAN 100 to a trunk link would have happened here, either on the port

78
03:44.020 --> 03:44.600
channel

79
03:44.600 --> 03:48.760
for which is logical or the physical interface with his ether channel.

80
03:48.760 --> 03:51.800
And then if we scroll down under wireless, we saw mobility.

81
03:51.800 --> 03:53.760
That's where we configure mobility groups.

82
03:53.760 --> 03:59.130
And right here, wireless global, this is where we can configure the RF group

83
03:59.130 --> 03:59.640
name, changing

84
03:59.640 --> 04:01.800
it away from the default setting.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:59.640 --> 04:01.800
it away from the default setting.

85
04:01.800 --> 04:07.190
So as we've said before, if you don't have access to your own 9800, then be

86
04:07.190 --> 04:08.000
sure to kind

87
04:08.000 --> 04:11.520
of watch these demos and think through and just sort of close your eyes and

88
04:11.520 --> 04:12.160
visualize

89
04:12.160 --> 04:15.840
if we have to, just to make sure we know where to configure some of these key

90
04:15.840 --> 04:16.560
constructs.

91
04:16.560 --> 04:20.130
If you do have access to an 9800, I encourage you to log in and play around

92
04:20.130 --> 04:21.520
with these configurations,

93
04:21.520 --> 04:24.920
especially if you can get to the point where you can add an access point.

94
04:24.920 --> 04:27.320
And that's going to be very useful to us as we move forward.

95
04:27.320 --> 04:31.810
But once again, it's all about what we have in our lab environment and what we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
04:27.320 --> 04:31.810
But once again, it's all about what we have in our lab environment and what we

96
04:31.810 --> 04:32.280
can do

97
04:32.280 --> 04:33.480
with what we are given.

98
04:33.480 --> 04:36.200
I hope this has been informative for you and I'd like to thank you for viewing.