Access points (APs) must discover a controller before they can become an active part of the network. The lightweight APs support the controller discovery processes.
These are the methods by which the AP discovers one or more controllers:
The AP issues a DHCP DISCOVER message in order to obtain an address.
attempts Lightweight Access Point Protocol (LWAPP) wireless LAN (WLAN) controller discovery and Ethernet broadcast. This method is deprecated and supported only on older Cisco AP1000 series. Current Cisco Aironet APs and wireless LAN controllers (WLCs) do not support Layer 2.
Layer 3 attempts LWAPP WLAN controller discovery
LWAPP discovery broadcast on local subnet: This can be assisted across Layer 3-routed boundaries with Cisco IOS commands:
ip forward-protocol udp 12223 (LWAPP) or 5246 (Control and Provisioning of Wireless Access Points [CAPWAP] as of version 5.2)
Over-the-air provisioning (OTAP)
If this feature is enabled on the controller (Controller >General), all associated AP's transmit wireless CAPWAP or LWAPP neighbor messages, and
the new APs receive the controller IP address from these messages. This feature is disabled by default due to possible security issues and should be enabled only during deployment. Locally stored controller IP address: This includes IP addresses of the controller that were learned from a previously joined mobility group.
DHCP server discovery with option 43: This feature uses DHCP to provide controller IP addresses to the AP. Cisco switches and routers support a DHCP server option that is typically used for this capability. However, currently (as of version 5.2) controllers cannot support this option.
The AP can discover controllers through your Domain Name System (DNS) server. The DNS server must be configured to return controller IP addresses in response to CISCO-LWAPP-CONTROLLER.local domain.
4. Once the APs join the controller, the primary, secondary, and tertiary controllers of the AP can be manually configured to join upon the next boot up, unless the master controller is chosen (Controller > Advanced > Master Controller Mode).
Note that the AP will cycle through all discovery methods to compile a complete list of controllers before selecting a WLC for joining. Also note that WLC version 5.2 changes the default tunnel protocol from LWAPP to CAPWAP.
Hello, I am in a situation where I need to rename a huge number of APs which wouldn't be feasible from the GUI. I spent a lot of time trying and searching for a how-to but to no avail!The commands listed under 'ap' don't include a rename! Is the...
I work for an MSP and also do sales into some enterprise clients, I have a client with 4x 3602 APs and another 17x 3702 APs ready to be installed.A colleague of his told him he needs a wireless controller now, he wants to know if that is a requirement, or...
Hello everyone! I'm a beginner in the Wireless world and I want to change most AP names in my topoloogy while using Cisco Prime 3.3 (100+ devices). To achieve this I believe I need to: 1) Export a csv with the APs I want to modify.2) Modify thei...
Hi All- A colleague of mine grabbed a 3702i that I have configured as a workgroup bridge and hung it in the ceiling. I can get to it via ssh / http. Any chance I can convert it to capwap in place. Advice on the procedure.would be a...