All right, let's go ahead and answer these challenge questions.
They're really designed to make us think about the architecture and make sure
we understand
that architecture, but also start to think about how we'd go about making
configuration
changes on the graphical user interface.
The first question, if we're lying on layer two broadcasts for the wireless LAN
controller
discovery of AP1, what VLAN must be enabled on this interface?
Well, ideally this interface is going to be a trunk.
And so the question is, how many VLANs need to be added?
Well, within the context of this question, we really only need one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Well, within the context of this question, we really only need one.
We need VLAN 100 because VLAN 100 is what AP1 is on.
And therefore we need to make sure AP1 can send a broadcast message and land on
the
SVI that's responsible for Capwep termination.
Now we immediately are going to be left wondering about AP2, which is running
on VLAN 200.
And that's what the next question asks is, how can AP2 then find a connection
to the
wireless LAN controller?
Well, we don't want to just rely on layer two broadcasts. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Well, we don't want to just rely on layer two broadcasts.
Remember, we also have that DHCP option 43.
And we also have the potential to use DNS or manual entries.
As we've mentioned in the real world, the DHCP option 43 is very simple to
include.
A lot of our access points tend to use DHCP.
And therefore we would just want to add it into our DHCP server and pass the IP
address
of this SVI to the access point during DHCP. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of this SVI to the access point during DHCP.
But if we listed out any of those methods, then that would be perfectly viable.
Next up AP1 appears to have connected, but its LED is flashing blue.
And so what's going on?
Well, we saw this when we first connected our access point.
This means that it is receiving a software upgrade.
So when the access point first connects to the wireless LAN controller, it's
going to
receive a software update if it's required because they really need to be
running the
same software version.
We don't want to be running incompatible software versions between the wireless WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We don't want to be running incompatible software versions between the wireless
LAN controller
and the access point.
And so blue, blue light flashing means that it's upgrading, whereas eventually
we saw
that it was solid green and that meant that it was fully connected.
And always keep in mind that if the color is cycling, especially red to amber
to green,
or possibly red and green alternating, either way that implies that we're still
looking
for that wireless LAN controller when you have to come back here and think
about our
methods if we can't find one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
methods if we can't find one.
Lastly, which configuration must be deployed on a multiple wireless LAN
controllers?
So radio resource management can be unified among many APs in the same area.
Well, now we're talking about wireless LAN controller to wireless LAN
controller communications.
And specifically, this is going to be an RF group configuration.
It's not to be confused with mobility groups.
Remember, RF groups are focused on that radio resource management.
The idea is we've got other APs in the area.
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
They're connected to this wireless LAN controller, but they can all hear each
other speaking
wirelessly.
And therefore, we need to consider one another when it comes to channel
selection as well
as how much the power, which we're transmitting and so on and so forth.
So now we have to wonder about how do we go about configuring that in the UI.
So let's go ahead and flip over to that.
And so remember that everything within our configuration sets going to be under
configuration
here and we looked at several things. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
here and we looked at several things.
Remember, VLAN interfaces are weirdly under layer two, but it's under VLANs.
That part makes sense at least.
We've got physical interface configurations up here.
So adding VLAN 100 to a trunk link would have happened here, either on the port
channel
for which is logical or the physical interface with his ether channel.
And then if we scroll down under wireless, we saw mobility.
That's where we configure mobility groups.
And right here, wireless global, this is where we can configure the RF group
name, changing
it away from the default setting. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it away from the default setting.
So as we've said before, if you don't have access to your own 9800, then be
sure to kind
of watch these demos and think through and just sort of close your eyes and
visualize
if we have to, just to make sure we know where to configure some of these key
constructs.
If you do have access to an 9800, I encourage you to log in and play around
with these configurations,
especially if you can get to the point where you can add an access point.
And that's going to be very useful to us as we move forward.
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
But once again, it's all about what we have in our lab environment and what we
can do
with what we are given.
I hope this has been informative for you and I'd like to thank you for viewing.