Controller Discovery Process
The Cisco AP must join a controller to function as an AP and start serving clients. Cisco uses a process called controller discovery process to join a controller. The devices use Lightweight Access Point Protocol (LWAPP) to communicate with each other. The AP can be plugged associated to a controller regardless of the physical location or logical location in the network. A new AP, out of the box, can be plugged in anywhere regardless of the subnet. After it is plugged in, it locates the controller, receives the controller version of the software image and configuration. After this is sent to the AP, it can start serving clients.
Guidelines and Limitations
-
You cannot edit or query any AP using the controller CLI if the AP's name contains a space.
-
Make sure that the controller is set to the current time. If the controller is set to a time that has already occurred, the AP might not join the controller because its certificate might not be valid for that time.
The controller must discover AP before it can become an active part of the network. The AP supports the following controller discovery processes:
-
Locally stored controller IP address discovery: If the AP was previously joined to a controller, the primary, secondary, and tertiary controllers' IP addresses are stored in the AP's non-volatile memory. This process of storing controller IP addresses on an AP for later deployment is called priming the AP. For more information about priming, see Performing a Preinstallation Configuration (Optional).
-
DHCP server discovery: This feature uses DHCP option 43 to provide controller IP address to the AP. Cisco switches support a DHCP server option that is typically used for this capability. For more information about DHCP option 43, see Configuring DHCP Option 43.
-
DNS discovery: The AP can discover controllers through your domain name server (DNS). For the AP to do so, you must configure your DNS to return controller IP addresses in response to CISCO-CAPWAP-CONTROLLER.localdomain, where localdomain is the AP domain name. Configuring the CISCO-CAPWAP-CONTROLLER provides backward compatibility in an existing customer deployment. When an AP receives an IP address and DNS information from a DHCP server, it contacts the DNS to resolve CISCO-CAPWAP-CONTROLLER.localdomain. When the DNS sends a list of controller IP addresses, the AP sends discovery requests to the controllers.