APs registering to anchor controller

[root_taker]

What would make some of our APs register with the anchor controller rather than the primary? All APs are getting DHCP information pointing them to the primary controller, they are all in the same VLAN, etc but for whatever reason some register with the anchor controller. I’m not sure how this is even possible to be honest…

Any thoughts?

[Stephen Rodriguez · Accepted solution]

So, is your anchor controller in the same mobility group as the 'internal'?

And to explain.

DHCP option 43, DNS, L2 broadcast etc.  Are simply Discovery Mechanisms for an AP.

When the AP sends the Discovery Request to a WLC, the WLC responds with a Discovery Reply.  In the Discovery Reply, is a list of all the WLC in the mobility group, their current AP count, their max AP count, and their excess availability.

Using this information the AP will join the WLC with the Greatest Excess Availability.

So DHCP Option 43 points to WLCA.  In the Mobility group are WLCA(100), WLCB(100), WLCC(50).

WLCA has 53 AP

WLCB has 51 AP

WLCC has 0 AP.

Which WLC will the next AP join.  It will join WLCC, as WLCC has the Greatest Excess Availability.

Make Sense?

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

[root_taker]

Thanks Steve. 

I beleive this is whats happening.   I guess the mobility paradime is something I don't really understand.  My end goal is all APs to register with the primary controller.  Then, the guest wireless will be tunneled out to the anchor while the corprate wireless terminates on the primary controller.

Is the solution simply to create a seperate mobility group on the anchor controller?  Would this break the tunnel between the two?

[Stephen Rodriguez]

yes and no.

So log inot your 'anchor' and set the primary WLC to be the 'internal'.  Once all of your AP have moved.  Change teh default mobitlity group on the anchor to something different.  Then change it on the internal as well in teh mobility group configuration.

The reason anchoring works to a different mobility group name, is that you are hard coding the anchoring.

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

[root_taker]

Thanks Steve. 

I'm sorry, when you say set to "internal" where is that setting exactly?

[Stephen Rodriguez]

For the primary?  In the AP configuration.

so Wireless > pick your AP > High Availablity

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

[root_taker]

Awesome,

I was making that harder than it really was.  That takes care of it! 

[Reginald Pugh]

FYI : In the past if we never wanted an  AP to register to "Anchor Controller" we just went into ::

Security > AAA > AP Policies : to open the AP Policies page, and checked everything to include : Authorize MIC APs against auth-list or AAA. Saved the Configurations: even if APs tried to join they couldn't.

[Stephen Rodriguez]

That would work as well.  But as it was an anchor it was easier and makes better sense to change the mobility group.

now, if they all had to be in the same mob group, then AP security would work.

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

[Vinay Sharma · Accepted solution]

This document is generated from the following discussion: APs registering to anchor controller.