#REJOIN AAA HOW TO#

Note: If you use CAPWAP, make sure that there is a DNS entry for cisco-capwap-controller. Essentially, the LAP learns as many management interface addresses for the controller list as possible via:ĭHCP option 43 (good for global companies where offices and controllers are on different continents)ĭNS entry for cisco-capwap-controller (good for local businesses - can also be used to find where brand new APs join) The LAP sends discovery requests to controllers through the various discovery algorithms and builds a controller list. The LAP boots and DHCPs an IP address if it was not previously assigned a static IP address. The AP goes through this process on startup: The controller then tells the LAP the Layer 3 AP-manager interface (which can also be the management by default)IP address so the LAP can send a join request to the AP-manager interface next. The LAPs always connect to the management interface address of the controller first with a discovery request. Therefore, Cisco recommends using the DHCP option 43 or DNS methods. This does not help find the controller if you replace a LAP later on. Therefore, if you put the LAP first on the local subnet of the management interface, it will find the controller's management interface and remember the address. Also, the LAP remembers the management IP address of any controller it joins across reboots. In addition to these methods, the LAP does automatically look on the local subnet for controllers with a 255.255.255.255 local broadcast. If you do not tell the LAP where the controller is via DHCP option 43, DNS resolution of 'Cisco-capwap-controller.local_domain', or statically configure it, the LAP does not know where in the network to find the management interface of the controller. However, this presents a question: how did the LAPs find the management IP address of the controller when it is on a different subnet? In a Cisco Unified Wireless network, the LAPs must first discover and join a WLC before they can service wireless clients. Overview of the Wireless LAN Controller (WLC) Discovery and Join Process Refer to Cisco Technical Tips Conventions for more information on document conventions.

#REJOIN AAA HOW TO#

This document also provides information on some of the reasons why a Lightweight Access Point (LAP) fails to join a WLC and describes how to troubleshoot the issues.Ĭisco recommends that you have knowledge of these topics:īasic knowledge of the configuration of LAPs and Cisco WLCsīasic knowledge of Lightweight Access Point Protocol (CAPWAP) This document gives an overview of the Wireless LAN Controller (WLC) Discovery and Join Process.

Rejoin aaa