Okay.
So that last ping succeeded.
I'll ping the controller again.
And as you can see, the pings are now succeeding.
So I'll close this command prompt and go back to my browser and use HTTPS and browse to the IP address
of the controller.
If I used http, I get server reset connection needs to be https and now I can log in using my username
of admin password of Cisco 1 to 3 click login.
Again, it may be a bit slow.
You need to be patient with us.
If you go back to your packet tracer topology, you might see lots of traffic between the PC and the
controller.
Just wait for things to happen.
Okay.
So we can see the IP address of the controller IP version four IP version, six software version.
We can see that it's been up for 2 minutes and 6 seconds.
We can see other information about the controller.
This is a very good representation of a real physical controller.
Packet trace is great and once again is all you need for the CCNA exam.
Spend time with the wireless LAN controller looking at the menu options for the exam, specifically
under wireless LANs.
So make sure that you understand, for instance, that when I click on w lan id one or wireless lan
one, I can see the configuration of this wireless LAN controller.
Now again, mine's running very slowly.
You have to be patient with this program.
So under general we can see profile name is staff, SSID is staff.
It's enabled.
We can see that radius policy is all management interfaces management spend time especially here under
security.
So layer two securities, WPA and WPA two.
We're using a U.S. encryption.
We're not using Ed or one X, we're using preset key.
And here's our preset key if you need to change it.
Under Layer three, no layer three security is enabled.
And no triple-A servers are being used.
We are not using Triple A in this example.
We simply using preset keys.
We can also see quality of service, staff, policy mapping and advanced settings.
But now let's get the access points to register with the wireless LAN controller.
Because at the moment under monitor, you'll notice that no access points have registered, no controllers
have registered with the controller.
And that's because we either need to configure them manually or we need to use a DHCP server.
They have different options.
You can use manual configuration on your access points to point them to the controller or use a DHCP
server or use DNS to get them to learn about the controller.
In this example, we'll use DHCP.
So on the DHCP server, I'll click on the server and go to services.
DHCP, we want to enable DHCP with the default gateway in this example being the switch.
So I haven't configured the switch.
So let's configure that right now.
Otherwise you may keep wondering where is the default gateway?
So I'll bypass the initial configuration on the switch.
Give it a hostname of SSE one.
Go on to interface VLAN one.
No, shut it.
IP address
19216812542552450.
So slash 24 mask and I'll save the config show IP interface brief scrolling all the way down.
We can see the IP address is up up and we should be able to ping the controller from the switch assuming
that everything is working.
It took it a while, but there you go, switch keeping the controller.
So the switch in this example is the default gateway.
So back on the TFTP server, DNS server is going to be the local device 1921681253.
So under config, we should probably configure the server with an IP address.
So 1921681253 is going to be the IP address of this server and it's going to be configured with this
DHCP information start IP address will be 1921681 100.
I'll start the pool at 100 because the control is using one.
So let's leave the lower IP addresses for the controller.
Now, in a good deployment, you probably want to move your controller to the high end IP addresses
in sort of the same range as the other network devices.
But for the moment, again, I'm just wanting to keep it simple, so I'm going to leave it as that subnet
mask is going to be 2552552550.
Maximum number of IP addresses that will allocate is 50.
This is really important.
Make sure that you configure the wireless LAN controller IP address here.
So 19216811 will be the wireless LAN controllers IP address and make sure that you click save to save
that information.
So I've just maximized the page.
Here's a summary of what we've done.
Server pool I left at default services enabled default gateways.
The switch DNS server is the local server.
Start IP address for the pool is 1921681 150 IP addresses will be allocated wireless LAN Controller
IP address is 1921681.1.
Okay.
So that's the server configuration.
Let's make sure that it can ping the wireless LAN controller.
Basically, just want to test IP connectivity to make sure that things are working properly.
And there you go so it can ping the wireless LAN controller.
Okay.
So on these access points, go to config.
I don't want to use static.
I want to use DHCP.
I want it to get an IP address from the DHCP server and you can see it's already been given gateway
information and DNS server information.
So under wireless LAN controller, we have learnt who the primary wireless LAN controller is through
DHCP.
So it's 1921681.1.
We can see other information about the app such as its IP address allocated once again using DHCP.
We can see the radio information.
I'm just going to leave that at default.
Second access point makes sure that it's been given an IP address.
So click on DHCP.
There we go.
Wireless LAN controller.
It's learnt that IP address has been learnt.
It's 19216811.
So back on the PC, I'll make this bigger.
I'll refresh monitor.
Notice we've now learnt about two access points.
Two apps have been discovered.
If I click on detail, I can see access point one and access point two.
Here the IP addresses.
Here are the models of the access point.
So the access points picked up the information through DHCP.
They've got an IP address, they learnt about the controller and they've registered with the controller.
So that's great.
Go to monitor once again.
IP address of controller.
It's been up for 10 minutes scrolling down.
We have got a 2.11 A and AC radios.
We've also got BG and N radios.
So two access points have been registered, but we have no clients at the moment.
So let's go to Wireless LANs and let's add a new wireless LAN or wireless local area network.
And I'm going to call this guest.
And click apply.
We've already got a staff or corporate.
Network.
So let's create a guest network.
I'll enable this.
Everything else is a default.
Go to security.
Layer two Security will be none.
In this example, I want this to be an open guest network now again in the real world and in subsequent
examples, I'll show you this.
We definitely don't want the guest network in the same VLAN as the corporate network.
We'd want to put that in a separate subnet.
So we we'd want guests in a separate subnet to corporate network make sense for security reasons.
But for the moment, we just want to get it started.
I want to show you how to get an access point.
Working with a wireless LAN controller.
What's important is that you understand these options.
So notice layer two, there's no security here.
Layer three, no security, no triple A service.
All I did was create a guest network and enable it and set the security to nothing.
And I've clicked apply now, so we should have two wireless networks.
I'll click back to go back.
We should have two wireless networks.
And there you go.
Both of them are enabled.
One is using WPA two authentication pre shared key.
One of them is using no security.
Both are enabled.
So we've got our network, but we haven't got clients.
So next step is let's get some clients into this network.
So I'll move this up a little bit.
Let's get two laptops into the network.
So laptop one, laptop two, first laptop.
Let's configure the laptop to use the guest network just so that we can start with something very basic.
Now, at the moment, we haven't got a wireless network adapter in this laptop.
If I go to config, I've got fast Ethernet zero and Bluetooth.
What I want is a wireless network adapter in this laptop.
This is an old laptop, so I'm going to swap out the Ethernet module for a wireless module.
You have to turn the laptop off and then turn it on to insert that wireless network interface card.
Now today in modern laptops, we generally have wireless, not physical Ethernet.
But this shows you nicely how we replace a network interface card that's physical wired Ethernet with
a wireless network interface card.
So now under config notice, we have wireless on the other laptop, which I haven't made that change
on notice under config.
We still have fast ethernet, but this laptop now has wireless is zero.
We don't want to use any authentication.
We want to join the guest network and we want to use DHCP.
Notice the IP address at the moment is 169.
But if that's configured right and I've just moved out of that tab, you'll notice it's now connected
to the wireless network and IP address has changed to one on 21681 104, which means that if I open
up a command prompt, I should I'll make this bigger.
I should be able to ping 1921681254, which is the switch.
And I can.
So I've now got a client connected to the network using the guest ssid let's get this guy connected
to the corporate network.
So first thing is under physical.
I've got to turn the laptop off.
Notice what happens when I try and take this.
When it's turned on, I get an error.
So I've got to turn it off, drag this network interface card out, put a wireless network interface
card into the laptop, go to config.
Well got it.
Powered on first, then go to config.
And now under wireless zero, I can specify what I'm using.
I'm not using WPA k.
I need to use WPA to ask why.
Jumping back to the wireless LAN controller, we're using WPA two.
So back on that laptop key is Cisco.
One, two, three.
I want to join.
What did I call it?
Stuff.
I want to join the staff network.
IP addresses this.
Just want to show you the diagram.
As soon as I make that change.
So it's really actually picked it up.
Notice it's now connected to the wireless network.
It's been given this IP address.
So under desktop command, prompt paying 192168254.
That works.
Can I ping the other laptop?
104.
That works.
So this device has an IP address of 121681 105 on the other laptop.
IP config has IP address 192168114.
It should be able to ping 105 and it can.
Now, in the real world, you don't want to do that.
You don't want your well, generally, you don't want your guests having access to your corporate network,
as I explained.
But I wanted to show you how easy it is to get a network working in packet tracer with a controller
with two access points with.
PCs.