All right, it's time to have some fun.
We're gonna get into the lab here
and configure my 25.04 wireless lane controller.
This is running aero S.
And it's connected to my layer two lab network.
And so I've got an access point here.
It's not going to be the same access point
I used to demo earlier.
And the reason for that is because
an aero S controller will find
cannot run 802.11AX, which is known as Wi-Fi 6, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
cannot run 802.11AX, which is known as Wi-Fi 6,
nor can it run the six gigahertz space,
which is the six E spec there that we have as well.
So we can't run either one of these with aero S
and that access point that I showed off
was an 802.11AX access point.
And so it was never added to aero S.
Instead, what I have is I've got a,
what is this again?
This is a 35.02 internal antenna.
So a 35.02 I cap wipe access point.
So what we've got here is if we can see the, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So what we've got here is if we can see the,
I guess so quickly it should go like that
with the logo there, but it is alternating in colors.
It's going from, well, it's hard to see on the video,
especially with my green screen,
blotting out the green LED,
but essentially it's looking for a controller.
The colors are going from green to red to amber.
The green to red.
And so what we're you need to do now is find out,
what do we need to do to make this access point WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
what do we need to do to make this access point
connect to the controller?
Because they're already in the same layer to network.
I mean, the access point is sending broadcast messages out
and the controller is receiving it
and yet it's ignoring it.
So what exactly is going on?
Well, this is a very important part
of our aero S controller configuration.
Again, what we have here, if we use a dotted line
to represent the fact that we've got a logical interface
in here and this logical interface
is going to be the management interface. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is going to be the management interface.
The management interface is currently on my lab network.
It's got the .14 IP address.
And again, it is receiving those broadcasts.
However, what we don't have is we have yet to check the box
that allows for dynamic AP management.
Until it's enabled for this,
it's not going to allow access points
to form cap web tunnels here.
So we're going to have to go in here and check that box
and make sure that we support access points. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and make sure that we support access points.
So that'll be step number one is to go and check that box.
Once that's up, we should see that the access point
gets discovered.
We're also going to go ahead and configure a dynamic interface
which would be associated with a different VLAN ID.
Now, I've got the management interface configured
to use the native VLAN.
And so actually in ARA-S, it refers to that as zero untagged.
And as a result, in a production environment, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And as a result, in a production environment,
as you can imagine, this is going to need to be a trunk link.
And very likely, we would have multiple links
all bundled together in production.
So this becomes known as a lag, a link aggregation.
And that would again be what we'd expect to see
in production, but in my lab environment, I don't have that.
I just have a single link to keep things simple.
And also because my upstream switch is just a home switch
and doesn't actually support port channels.
But if we wanted to configure a port channel, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But if we wanted to configure a port channel,
we could configure a static port channel there
using a Cisco switch.
Now, the last thing we'll do in this video
is take this access point and add it into an AP group.
And so we're going to go and create an access point group
and we'll add the AP into that group.
Now notice by the end of this video,
we will not have configured an SSID.
There's no broadcasting of signals yet.
We haven't configured a WLAN yet.
So we've got to get all of this knocked out WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we've got to get all of this knocked out
before we can even start to configure our SSIDs and WLANs,
which will come up in the next video.
So once again, let's flip over to the controllers
graphical user interface.
And we're going to start off by going and taking a look
at those interfaces.
I'm going to come over to the controller
and then the interface is on the left.
And we see that it comes with a management and virtual interface,
which have IP addresses that were given to it
by the admin during initial setup.
In other words, me at that point. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
In other words, me at that point.
Now, again, we mentioned that we're not covering
all of the interfaces because that's prerequisite knowledge.
But we should remember that there's a virtual interface.
And usually we're going to give it the 192.0.2.1 address.
Once upon a time, Cisco recommended 1.1.1.1 here
because that was a very easy IP address that was not in use.
Well, go figure.
Now it's in use.
It's a DNS server that's available on the public internet.
And so Cisco changed the recommendation to say, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And so Cisco changed the recommendation to say,
you know, we should probably never have used a public IP
address.
Let's use a range that was actually set aside
and dedicated for lab purposes.
And so 192.0.2 as a slash 24 was set aside for that reason.
And so we can use the .1 address there.
And that should be an IP address that is not used anywhere else
in our local network or on the internet.
So that's what we want to place on the virtual IP address.
And that would be the same IP address
on all of our wireless LAN controllers.
It's not something we need to worry about duplicating WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
It's not something we need to worry about duplicating
or anything like that.
We will duplicate that IP address among all of our controllers.
So that's a very brief touching on the virtual interface.
Let's focus on the management interface.
So once again, this is using the untagged VLAN.
So we don't actually define what that VLAN is
because it's irrelevant to the controller.
It just knows that it's not going to tag it.
So this has to match up with whatever the native VLAN is
on the upstream switch.
But if I click on this, we'll see some configuration WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But if I click on this, we'll see some configuration
information.
Again, 0 here means that we're not tagging it.
I've got the IP address here as well as the gateway.
I can tell it which port number and backup port to use.
So again, I'm only using a single interface.
So I said use port number one, backup port number two.
And if we're using lag, then we don't need to worry about this
because we have one logical port.
And it's going to automatically handle physical failovers for us.
Here's the big thing we need to worry about.
Enable Dynamic AP Management. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Enable Dynamic AP Management.
Like I said, this is unchecked.
And I'm going to check this and then come up here and apply.
This should make it so that this address is discoverable now
by access points.
So I'm going to say OK.
And yes, it's going to cause a little bit of a reset
for existing networks.
We don't need to worry too much about that
because we are bringing in that work up fresh.
So I'm going to come back over to the Monitor tab,
click on Access Points over here.
And we'll go take a look at radio. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we'll go take a look at radio.
So we're expecting--
I can click on either one of these
because this is a dual band radio or access point.
But we are expecting that the radios should start to show up.
I'm looking over here at my access point.
And we do see now it-- well, again,
because of the green screen, can't really see it
because it's just see-through there.
But there's a green LED.
And so the green LED means that it
has associated with the controller.
So give it a few moments here.
And hopefully, our controller will sync up pretty up. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And hopefully, our controller will sync up pretty up.
It's already there.
Look at that.
Didn't even have to pause the video.
So we do see that we've got one up here, one up here.
If I click over here now, we do see that it's there.
So a little bit of this legacy interface issue
doesn't automatically refresh.
And so we just have to click around until things
start to show up.
But we do see that I've got, again, a dual radio access
point.
So it's got a 5 gigahertz radio that supports 802.11AN and AC
and a 2.4, which is BG and N. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and a 2.4, which is BG and N.
So from here, we can start to do some more configurations.
Now, even though we're not going to use it in the lab demo,
I do want to demonstrate creating a dynamic interface.
So we go to controller, interfaces, and look over here,
I can just click new.
Let's create a new interface.
So let's just call this test for the sake of something
we're not going to use.
And we see I can associate a VLAN ID here.
And this is going to have to be something unique relative
to the controller.
I can't create multiple interfaces with the same VLAN ID. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I can't create multiple interfaces with the same VLAN ID.
So let's just say this is VLAN 10.
So we're going to click apply.
And now we see a lot of the same information that's
on that management interface.
So I can set the port number and the backup port number.
So which of these interfaces will this--
well, again, think of it almost like an SVI.
It's a logical interface.
And it's getting mapped to a port.
One interesting thing about AROS is they are always
very consistent about the use of the words interface
and port.
Cisco can sometimes go back and forth on this. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Cisco can sometimes go back and forth on this.
But with the wireless LAN controller with AROS,
interface means a logical point.
And a port is physical.
So interface logical, port physical.
If I see port, it's talking about a physical port
on the wireless LAN controller.
If we're talking about an interface,
it's logical, again, thinking like an SVI.
So either way, we see that I could
enable dynamic AP management.
I don't have to do this, by the way.
I can still map this interface to SSID's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I can still map this interface to SSID's
for the sake of mapping them to VLAN 10 in this case.
But if I do want them to be able to form capwap tunnels,
then I can enable this.
And there are limits to how many capwap tunnels
can form on each interface.
And so I might need to load balance this
in a real world network.
From here, I could enter some kind of dummy IP address
for my lab environment, like 10.0.10.
And then we'll just say the .2 interface.
So NetMask, actually, that would be a slash 24.
And then the gateway could be 10.1.
So now, when I click Apply, we're going to find WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So now, when I click Apply, we're going to find
that there are some normal warnings here about,
and it's going to cause some issues.
But we're also going to find that it's going to fail to add.
The reason for that is because we can only actually apply
one of these dynamic AP manager interfaces
per physical port.
Now with a lag, this looks a little different.
But with physical ports like this,
we can't actually apply this.
So I'm going to go and enter all of the information
in again.
And at this point, I'm going to leave the dynamic AP manager WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And at this point, I'm going to leave the dynamic AP manager
option off.
And that's going to make sure that I can, in fact,
save this dynamic interface to the same port
as my management interface.
OK, cool.
So we go back to the interfaces.
And we do see that this test interface shows up
as VLAN10.
With this IP address, it calls it a dynamic interface here.
And we left dynamic AP management disabled.
So this is very useful information.
And as I keep saying, in a production environment,
things will look different.
For example, we would expect to see WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
For example, we would expect to see
many different dynamic interfaces listed here.
We need one for every single VLAN
that we're using on our SSIDs.
So the last thing we said we're going to do
is to go take a look at our access points.
So once again, I've got this access point down here.
If I go over to Wireless, I can actually
see more details on the access point.
It actually defaults to this all APs option.
And I can see the 3502i listed here.
So I can click on it.
I can see the name. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I can see the name.
I could actually name it if I wanted to.
And a network with dozens or hundreds of APs.
I probably don't want to name every single one.
Yeah.
Reminds me of playing Pokemon.
I don't want to name all of my Pokemon.
I just want to name the special ones.
So same thing with the access points, I suppose.
Maybe that is neither here nor there.
But either way, if I go over to some of these different options,
we can see that we can do individual configurations,
such as whether we're supporting CDP,
the list of controllers, primary, secondary, and tertiary. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the list of controllers, primary, secondary, and tertiary.
If I want to override that, I can see critical information,
like the product ID and the serial number and all
of these things.
And so lots of information just by clicking on the AP.
Now, the last goal that we had was
to add this access point into the AP group that we created.
And we can do that by going over here to the Advanced tab.
And this AP group name is a dropdown,
and I can select CBTN group.
So this is how I apply it to the group. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So this is how I apply it to the group.
I can click Apply here and say, OK.
And now this is going to be part of that AP group.
So this is something we're going to want
to make sure that we do intentionally.
We're setting our access points into the appropriate group
based on their location that they're being deployed into
in the network.