Now for the CCNA exam, you really need to know how to configure a wireless LAN controller.
You need to know the menu options in a wireless LAN controller.
So I'm going to show you multiple demonstrations and also test your knowledge of the Cisco Wireless
LAN controller.
In this first demonstration, we're going to build a brand new network consisting of lightweight wireless
access points, wireless LAN controller, switch, DHCP server and obviously clients.
This will give you a good understanding of how to build a network using the Cisco Wireless LAN controller.
I strongly suggest that you follow me.
So while I'm building this, follow what I'm doing and see if you can get it right in the next few labs.
I'm going to test your knowledge and see if you can actually build your own wireless LAN controller
network.
Remember that we're using a lightweight access point share and autonomous access point is an access
point that you configure and manage directly.
Here we're using a lightweight access points which require a wireless LAN controller to work.
Okay, so let's get started.
In this example, I'm controlling that Windows computer from my Mac.
You could run packet tracer directly on your Mac or Linux computer.
I have found however, that I have issues with packet tracer on my Mac.
So I've found that Windows is the most stable using the latest release of packet tracer.
So that's what I'm going to use for this demonstration.
Okay, so let's build a network.
First thing I need is a switch.
So I'm going to get a 3560 switch and add that to the topology.
The switch will simply be a layer two switch.
In this topology, we're going to start with a simple topology, and then in subsequent videos and labs,
we'll build more complex topologies.
But let's start simple to make sure that you can get a network working.
Okay, so we've got a switch.
Next device I need is a PC.
I'm going to use the PC to manage the wireless LAN controller.
I also need a server.
The server will act as a DHCP server to allocate IP addresses to the wireless access points.
We also need a wireless LAN controller.
I'm going to get a 3504 wireless LAN controller.
We also need some lightweight access points.
I'll grab two of those.
So 3702 wireless access points.
So they are our devices.
Let's name this access point one.
We'll name this access point to.
I'll name this w one.
This will be switch one.
I'll leave the rest of the devices as they are.
So next thing is, let's cable up the network.
I'll connect the first Ethernet interface of the PC.
To the first Frost Ethernet interface on the switch.
DHCP server to the second interface.
Wireless LAN controller gigabit one to the third physical interface, and then I'll connect the access
points to the switch.
So there's a basic topology.
It's not very pretty, but that's all we need to get started.
You could make this look better if you wanted to.
I'm not too concerned about that.
One of the things you could do if you don't like the labels is go to options, preferences and uncheck
this option so that the interface labels are removed.
But I prefer having those so that I know how the devices are connected.
Okay, so let's now configure the devices.
The first thing is the wireless access point by default uses an IP address of 1921681.1.
With this subnet mask, I'm going to change that to a slash 24 mask.
I'm going to set the default gateway to 1921681254 and the DNS server.
21921681 253.
So you might want to add a note to your topology so that you know what IP addresses the devices are
using default gateways.
That DHCP server DNS server will be 1921681253.
That will be the server up here and then the wireless LAN controller will be 1921681.1.
I'll leave it at the default for the moment.
Now, in the real world, you probably going to want to change that.
You're going to want to put your access points on a different VLAN to your client devices.
But I'm going to keep it simple.
I always like to keep things simple when we start start from the basics and then bold or iterate on
that and make it more complex.
Okay.
So all I've done is specify the IP addresses of the wireless LAN controller.
We've got its name.
Once again, management information.
Is that on the PC?
We're going to configure it with an IP address in the same subnet.
So let's say 19216815 slash 24 mask.
If you buy a physical access point, it by default will have an IP address of one on 216811.
So you just put your PC in the same subnet and then you can browse to the controller and configure it.
So that's what we're doing here.
So on the PC, I've got my IP address configured, go to desktop.
I'll make this a bit bigger, go to web browser.
And in this example, we're using HTTP and we're going to browse to the IP address of the controller.
Now I have found that this is very slow in packet tracer.
You can see the icons here flickering a lot.
Just be patient.
It might be very slow with this controller.
If you think there's a problem, you could ping from your PC to the controller.
But as you can see here, we've now been prompted with a wizard.
This is something important to remember.
Use HTTP to the IP address of the controller initially.
Then once you've done some initial configuration, it will reboot and you have to use HTTPS to configure
the controller.
So what is the admin name that I'm going to use?
I'm going to use admin password is going to be Cisco.
Now it might complain about that password.
Click start now notice it's complaining about the passwords.
So I'm going to say Cisco one, two, three, Cisco, one, two, three.
Obviously, in the real world, you're going to want to use a better password than that, but that's
fine for this demonstration.
So uppercase C for Cisco.
One, two, three.
Now we need to give it a name.
I'm going to call it wc1.
It's picked up that I'm in the United Kingdom.
Your packet tracer should pick up where you are.
In the real world, you need to specify the right country.
You don't want to use Germany or say Russia in the UK to be legally compliant.
Use the correct country code.
So GB is UK date and time is here.
timeZone is that we can specify http server if we want to.
We're going to specify the management IP address.
I'll keep that the same if you want to change it.
This is where you can change it.
Default gateway to five four.
In the real world, you typically once again want to use VLANs.
You want to separate your AP IP addressing from your clients.
We're not going to worry about that here.
We want to get started.
Somebody click next.
Now we told that we can create a wireless network and employee network, so let's create a staff network.
What security are we going to use?
Make sure you know this.
Pzc WPA two Pzc means we're not using a radius server enterprise means we're going to use a radius server
better for authentication.
Typically at home you're going to use pzc appreciate key.
In other words, the same key or the same password is used on your PC as well as your wireless network.
You're just authenticating use using a preset key.
But if you're using enterprise, you integrate with a radius or tax server.
So I'm simply going to use preset key.
What's the passphrase?
I'm going to use Cisco, one, two, three to keep it simple so that I don't forget my passwords.
You might want to write that down.
Keep it somewhere.
The VLAN that I'm going to use is the management VLAN.
Not great practice for the real world, but we'll leave that for the moment.
We could set up a guest network if we wanted to, but I'm going to show you how to do that manually,
so I'm going to leave that as it is and click next.
Now, a virtual IP address is required by the controller.
In many past implementations they used 1.1.1, but that's now a very important IP address for DNS resolution.
So you don't want to use that Cisco using 192021 by default now.
So that's the virtual IP address default mobility group, which can be used if clients are roaming from
one access point to another is default.
We'll leave that as it is and click next.
Okay.
So now we asked to confirm our settings and click apply.
So there is my controller settings.
Here is my network settings.
I'm using the default virtual IP address and default mobility group.
I'm going to click Apply and notice what we told system will reboot.
After these settings are applied, click okay to apply these configurations or cancel to return to the
wizard.
I'm going to click.
Okay.
The configuration is now saved and I can connect back to the controller, but I need to use HTTPS to
connect to the controller.
So what I could do is on the client, close this down and make sure that I can ping the controller.
So this is one way to check whether it's come back again.
Making sure that the pings actually succeed.
So I'm going to pause the video at this point, wait for this to start working, and then I'll connect
back to the controller using HTTPS.
How are you doing?
Are you able to follow me at this pace?
Are you able to configure your controller?
Try this yourself.
That's the best way to learn.