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, Rogue detection on AP can do that on the wireless scope. Now, about the wired scope.Is the only way to detect/alert unauthorized AP on the wired network through network vulnerability scanning tools or Cisco ISE could also do that ? T...
Guys, Did anyone integrate mobility express solution with LDAP server before? As i already found the below link that contains the attached info: https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-5/b_cisco_mobility_expres...
Hi all, We currently have 9120AX access points deployed managed by a 9800L controller. Could anyone tell me if it is possible to 'schedule' the availability of a particular SSID? We want to broadcast a SSID (and allow users to connect) between c...
My school got an old school building that has a AIR LAP1252AG-A-K9 in it.I know it is old, however, what do we need to use it?I was told something like an AIR-RM1552A-A-K9.If that is it, can that be made with a virtual build and not a physical one?I...
We have a 3355 MSE appliance, and we do not have the admin password for the web. I have tried just about anything (even re-running the startup wizard and redoing the password for Admin, which for some reason wouldn't take. We are at our wits e...