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.
OK.. Management has released an employee with an oeap. they desire to block said oeap until its return. How do we do that before it connects to the wlc? the system has client tracking, not ap tracking/reporting. the device has to b...
FYI.. not very experienced but trying to setup AIR-AP1562I-B-K9 to connect to Cisco Controller 2504getting the following error: 02/18/2020 05:30:49.0500] wired0: link up[02/18/2020 05:30:49.1000] wired0: started[*02/18/2020 05:30:49.1563] aptrace_reg...
I am looking to implement interface groups in our wireless environments. We are currently running into issues with exhausting our DHCP pools and are looking to establish a second interface on one interface. I have a few questions in regards to this featur...
I try to put new image from 18.104.22.168 to 22.214.171.124 on AP but for 4 AP of 86 I couldn't.
Here is log from AP
UK-AP07#Jun 16 14:35:42 kernel: [*06/16/2022 14:35:13.6832] ....Re-Tx Count=1, Max Re-Tx Value=8, SendSeqNum=32, NumofPendingMsgs=2Jun 16 14:35:42...
In the course of studying the generated events in Cisco PI for Rogue AP, it turned out that there is no working link to the map of location of access points.Can you tell me how to fix this? Does this functionality require any additional license?