WLC limit

[vishalpatil86]

HI,

I am using cisco WLC 4404 and has 48 1242 series APs registered with it.

When i tried to connect another AP, it did not get registered, but when removed one of the registered AP and then connected, it got registered

moral of the story is i cannot register more than 48 APs

Help me on this.

[Nicolas Darchis]

The documentation clearly states that if you want to connect more than 48 APs, you need to connect several ports of the WLC either through LAG and an etherchannel on switch or without LAG but you need one ap manager interface per port then.

[vishalpatil86]

hi,

can u pls provide me the documentation?

[Nicolas Darchis]

http://www.cisco.com/en/US/docs/wireless/technology/controller/deployment/guide/dep.html#wp1061736

a simple search on the forum for "WLC 48 APs" also works 😛

[Leo Laohoo]

Hi Nico,

Doubt if you'll get anything from the thread owner so can I give you the +5 instead? 

[Nicolas Darchis]

We have a deal. Thanks 😄

[vishalpatil86]

hi,

I have created interfaces as per the documentation.

But when I assign controller to cisco AP, its not working.

I have attached config screen shots.

Kindly suggest on this.

[dmantill]

is the switch properly configured for that vlan?

if you do a show arp from the switch or wired network, can you see that mac being map to that IP and passing traffic thru that port?

please provide us moredetails...

show arp from the switch

is it i connected to the same switch?

switchports configuration from switch

frm WLC

show interface summary and detailed..

show port summary

[weterry]

If you are having trouble getting a 2nd interface functional, and you only had a single interface connected originally, my suggestion is you go back to that setup and you just enable LAG and reboot the WLC.

You can only have 48 APs assigned to a single AP-Manager, unless LAG is enabled.

But having LAG Enabled doesn't not mean you have to have more than 1 interface connected.

If you have LAG enabled, and only 1 physical interface connected, then you don't really have to do any port-channel config on the switch side either...

Other than that, if you want to go with two ap-managers and two different physical ports, then generally speaking the primary reason it would fail was if your switchport was not configured correctly for the 2nd interface.....

[vishalpatil86]

hi,

required config is attached

[vishalpatil86]

hi,

can anyone help me on this?

[dmantill]

Config on the WLC looks OK but from the switch side it doesnt make sense , how isnt it possible to see themac address on its table :-s

Is it the direct switch where the WLC is connected? check the mac-address table per port on theones you think it is connected.

I would save the configuration and reload the WLC :-s

[vishalpatil86]

hi,

if i want to enable LAG for this purpose, then do i have to create ap manager and assign IP to it?

[weterry]

No... as a matter of fact you'd probably want to remove the newly created AP-Manager.

In theory, if everything is functional on your WLC and you enabled LAG, I wouldn't expect anything to change (except that you'd be able to get more than 48 APs connected via a single interface).

LAG Requires a reboot though, so be prepared for that.

I suppose if something goes wrong (which I doubt), then you could always just disable lag and reboot again.

Now none of this fixes why your second ap-manager isn't working, as clearly something is going wrong there but LAG I think will make it easier if you're just trying to get your last few APs connected.

[dmantill]

I think if you enable LAG and you do a reboot rhat interface should automatically be removed from configuration, however for best practice please remove the interface manually and use LAG, LAG is always the way to go, multiple ap-manager interfaces is like a workaround...

Let us know how did you go and remember to use the right algorith for loadbalancing the ether channel on the switch side.