Wireless AP - WLC Discovery

[mirkobrodersen]

Hello all,

I have a question regarding WLC discovery.

Now I've read the Chapter for that in the ENCOR OCG (2), and the order is as follows:

Step 1. The AP broadcasts a CAPWAP Discovery Request on its local wired subnet.

Step 2. An AP can be “primed” with up to three controllers—a primary, a second-
ary, and a tertiary.

Step 3. The DHCP server that supplies the AP with an IP address can also send DHCP
option 43 to suggest a list of WLC addresses.

Step 4. The AP attempts to resolve the name CISCO-CAPWAP-CONTROLLER.
localdomain with a DNS request

Step 5. If none of the steps have been successful, the AP resets itself and starts the
discovery process all over again.

So my thought process was, that this is the actual order in which the AP attempts to discover a WLC.

However in the following whitepaper: https://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/119286-lap-notjoin-wlc-tshoot.html

The order is this:

The AP goes through this process on startup:

1. The LAP boots and DHCPs an IP address if it was not previously assigned a static IP address.
2. The LAP sends discovery requests to controllers through the various discovery algorithms and builds a controller list. Essentially, the LAP learns as many management interface addresses for the controller list as possible via:
   1. DHCP option 43 (good for global companies where offices and controllers are on different continents).
   2. DNS entry for cisco-capwap-controller (good for local businesses - can also be used to find where brand new APs join) If you use CAPWAP, make sure there is a DNS entry for cisco-capwap-controller.
   3. Management IP addresses of controllers the LAP remembers previously.
   4. A Layer 3 broadcast on the subnet.
   5. Statically configured information.
   6. Controllers present in the mobility group of the WLC the AP last joined.

So therefore I'm a bit confused what I should think about that. Since I would go with the official Whitepaper, but I'm not sure. Can someone verify and help me with this?

Thanks in advance!

Kind regards,

Mirko

[pieterh]

read this carefully
The LAP sends discovery requests to controllers through the various discovery algorithms and builds a controller list. Essentially, the LAP learns as many management interface addresses for the controller list as possible via:

this does not describe the priority, it describes what items are contained in the list
after the full list is built then a controller is selected through preference rules

[nachoGrande]

setup dhcp option 43 in your DHCP server.  Or better yet, but the AP on the same vlan as the WLC and it will find it through a broadcast packet. Once it has discovered and join, move it to another network if needed.

but to directly answer your question, i have never had an issue (and do a packet capture to check).

The AP goes through this process on startup:

1. The LAP boots and DHCPs an IP address if it was not previously assigned a static IP address.
2. The LAP sends discovery requests to controllers through the various discovery algorithms and builds a controller list. Essentially, the LAP learns as many management interface addresses for the controller list as possible via:
   1. DHCP option 43 (good for global companies where offices and controllers are on different continents).
   2. DNS entry for cisco-capwap-controller (good for local businesses - can also be used to find where brand new APs join) If you use CAPWAP, make sure there is a DNS entry for cisco-capwap-controller.
   3. Management IP addresses of controllers the LAP remembers previously.
   4. A Layer 3 broadcast on the subnet.
   5. Statically configured information.
   6. Controllers present in the mobility group of the WLC the AP last joined.
      
      Do you have DHCP helper address setup.  What do you see on the conroller or on the AP logs?
   7.  

[nachoGrande]

what model and code is the Access point?

Also, if you don't have a static IP, the first step that happens is DHCP, so option 43 would be the first step.

[Rich R]

Option 43 is the recommended method.

Setting the static Primary/Secondary/Tertiary HA config on the AP will allow it to deterministically join them in that order otherwise it will simply join the first one it gets a reply from.  You will always see it sending discovery requests to every WLC it knows about too, including any WLC it has joined before or learned about from WLC mobility (basically it checks that list it compiled to see which ones it could join if needed).

Also note a fact often missed by people who like to try using static IP addresses for their APs instead of DHCP.  If, for any reason, an AP with static IP is not able to join a WLC it will automatically fall-back to using DHCP (override the static IP config) as a method of recovery to try to find a working WLC.  So it's best to just design for DHCP with option 43.

[mirkobrodersen]

Hello @Rich R,

thanks for the reply. Tough my problem is, that I expect questions on exams like "If the AP couldn't discover a WLC via DHCP option 43 or via DNS, what is the next method which it is going to use". So I assume there has to be an order.

And because those two sources mentioning different orders, I'm not sure which order to learn.

Kind regards,

Mirko

[MHM Cisco World]

when I read this order first time I also confuse 
but I will clear it to you 
the AP will collect WLC IP from all discover method, the order here is which one of discover come first and so on 
the order not meaning that if AP detect WLC via DHCP then it stop and not check the WLC via DNS. 
so the AP collect all WLC IP and select one of them. 
if the WLC not in same subnet of AP then the first discovery method have no WLC IP 
if the DHCP op43 not correct or not send by DHCP then no WLC IP
if the DNS can not resolve the WLC IP then  no WLC IP 
here the AP will use last WLC use or use primary/secondary WLC IP save in runing ( also here the cisco have some note to prefer the WLC primary/secondary than the WLC learn from DHCP/DNS)

MHM

[pieterh]

separate the discovery process from the controller selection
maybe the document below answers your question sufficiently
I read it as primed controllers first,
next any of the discovered controllers with the most "free capacity" to service access points
when multiple controllers with equal capacity, then the first controller that has responded.

Understand the AP Join Process with the Catalyst 9800 WLC - Cisco

Note: The WLC Discovery methods listed do not have any precedence order.

Wireless LAN Controller Election

Once the AP has received a Discovery Response from any WLC using any of the WLC discovery methods, it selects one controller to join with this criteria:

1. Primary Controller (Configured with the capwap ap primary-base <wlc-hostname> <wlc-IP-address> command)
2. Secondary Controller (Configured with the capwap ap secondary-base <wlc-hostname> <wlc-IP-address> command) 
3. Tertiary Controller (Configured with the capwap ap tertiary-base <wlc-hostname> <wlc-IP-address> command)
4. If no Primary, Secondary or Tertiary WLC were previously configured, then the AP attempts to join the first WLC that responded to the Discovery Request with its own Discovery Response that has the maximum capacity of available APs (that is, the WLC that can support the most APs at a given time).

and this document
Joining Process of an Cisco Access Point - Cisco Community
mentions you have some influence on the selection process (where the default-logic is described as above)

• (Once the LAP has list of all those WLCs to which it can join, the LAP can decide the WLC , it will like to join.
• The logic for that decision can either be customized by the user or can be left to the default-logic).
• The order of execution of logic is preferred with the customized logic first, else with default-logic.

all this results in that broadcast on the local network can be  preferred over configuring DHCP-43 and DNS,
because this always results in selecting  a controller on the same lan/subnet
depending on your own demands can result in priming the controller address as the preferred method.
this way YOU are in control, 
the other discovery methods are still executed, to build the list of candidates to use when ALL primed controllers do not respond

[Rich R]

If you want a definitive answer for the preferred order then you'll have to test it yourself and observe but you can't be sure it will always be the same on every AP type and software version.