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.
When connecting to the wireless network I have noticed that the clients will often skip an AP 10 feet away and connect to one two floors up and 100+ feet away. That doesn't sound very efficient and data rates are pretty poor.Can this be fixed?My test clie...
I recently installed vWLC release 8.5 in Hyper-V and referenced the hyper-v deployment guide. Once installed and configured, I could ping the management interface IP from the hyper-v host but couldn't load the web GUI from a browser on the host. After a l...
Hi, We have a remote site with FlexConnect and mainly Win7 devices. Last week we came across IP-adress conflicts for that scope. The Clients use the same Subnet for both NICs and they are active at the same time. As I could not find reliable inf...
WLC C9800-40-K9 on 16.12.1 We are seeing a lot of alarms in ISE for "12929 NAS sends RADIUS accounting update messages too frequently". The NAS is a 9800 WLC and the clients are mainly phones on our eduroam SSID. On the old 5508 controller there is n...
Hello Cisco members, I would like to ask if obtaining RSSI data from WLC controllers is possible, for associated and/or unassociated clients? I read some resources on the Internet which says it's doable via "Cisco Wireless Location Appliance", b...