Cisco Controller 2100/Aironet 1200 AP

Hello
I have to setup a Cisco controller 2100 in an infrastructure that already has 5 Aironet series 1200 access points setup. All the users used to connect to the Acess points directly using WEP but we now have to unify all the APs and configure them on the controller.

I found some instructions and I configured the Management and AP manager's port, plugged the Aironet APs ot the controller but I am not able to get the controller to recognize them as Access points even when I do Search by MAC AP using the controller's web GUI. I can see the Access points listed in Interface Neighbors under the CDP category but I cannot connect to to them wirelessly or connect to them like I used through the web as long as they are directly connected to the controller. Any ideas of what I am not doing or doing wrong?
Maximus54Asked:
Who is Participating?
 
HodepineCommented:
The search by mac address is just to find a specific AP from already discovered APs.

The 2100 controller can only run in Layer 3 mode (opposed to the larger controllers that can run both layer 2 and layer 3), which isn't a problem, since you'll want to run layer 3 anyway. When running layer 3 the APs find the controller based on information it can get from a number of sources. The two most common are either by options set in DHCP or by DNS. If you set up a host called CISCO-CAPWAP-CONTROLLER and CISCO-LWAPP-CONTROLLER on your DNS server pointing to the AP-MANAGER ip of the controller, the AP will find this if it's DHCP settings are correct (doman and DNS server needs to be included in the DHCP information).

If that is in place, you can connect your AP to any port in your network where it receives a DHCP address, and it'll look up the IP-address of the controller and connect to it.

The controller has to be reachable, so you need to connect it to the network so the AP-manager interface can be reached. I've never set up the 2100, only the larger 440x and 5508, but I believe you need to "link" the AP-manager interface to one of the physical ports on the controller, so have a look at the settings on the AP-manager and confirm if there are any settings like this and if so, that they're right. A bit complex? Maybe. There's a reason there are consultants out there. ;)

0
 
HodepineCommented:
Sounds like you need to convert your stand-alone access points to lightweight.

The controller "speaks" LWAPP/CAPWAP with the access points, and the stand alone accesspoints don't understand what it's talking about.

Follow this guide to convert:

http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html

0
 
Maximus54Author Commented:
Thank you Hodepine, I read something similar in another blog but I ignored it as it did not make any sense then so I will try it right now and get back to you.
0
WEBINAR: 10 Easy Ways to Lose a Password

Join us on June 27th at 8 am PDT to learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees. We'll cover the importance of multi-factor authentication and how these solutions can better protect your business!

 
Maximus54Author Commented:
Sorry but I followed that link and upgraded the access point but still the controller is not detecting it. I do a search with its MAC address and it is still not finding it.
0
 
Maximus54Author Commented:
Hodepine
Thank you so much for getting back to me so soon, I just had a couple of questing before I do the additional steps that you sent me. First, after I upgraded the AP, should I hook it up to our network switch or should I hook the AP directly into the controller, 2nd even though the upgrade process said that it was complete, is there anyway I can check whether that AP has actually been upgraded to a Lightweight AP.
And last, from the new steps that you sent, should I create both the CISCO-CAPWAP-CONTROLLER and the CISCO-LWAPP-CONTROLLER or just one of them pointing to the AP-Manager interface IP address? Thanks again
0
 
HodepineCommented:
As long as it is in a network that can reach the AP-manager interface, it doesn't matter where it's connected. It's not common to connect it directly to the controller. Doesn't scale well if there are many aps or the aps are on remote locations.

You should create both domain names, just to be safe. Depending on the version of software it will query for one of them. Both should point to the AP-manager address.

You can connect to the ap with the console to confirm if the upgrade is done, or just try to run the upgrade process again.

0
 
Maximus54Author Commented:
No you do know that the management port is the only port that is pingable, right! Anyway, it does not work. When I telnet to the AP and tried debug lwapp, I get an "%Invalid input detected at '^' marker" and the ^ points to lwapp. It is like it does not understand it. I will try some more so unless you can think of anythign else then thanks a lot for all of your help.
0
 
HodepineCommented:
Yeah, by reach I mean reach with lwapp or capwap traffic, not ICMP.

The fact that you can telnet to the ap is a bit troubling. If a lightweight  boots up and can't find a controller it will reboot and search for a controller again. I'd try the upgrade process again.
0
 
Maximus54Author Commented:
Just in case it was the one AP that I was working with, I upgraded another one and the same problem occurs. At this point, I am giving up at least until Monday. Thanks for all of your help Hopedine. I will leave the question open in the hopes that someone else has also experienced the same difficulty.
0
 
Maximus54Author Commented:
Hodepine:
I redid the same thing as last time and this time it worked so your solution worked. Thanks a lot and I am awarding you the points.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.