Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

WLC - Stopping broadcast response to LAP

Hi,

I'm currently in the process of migrating my wireless infrastructure.

I presently have a 4404 (10.6.100.5) and 5508 (10.6.100.6) with some LAP 1131;

I installed a new cluster of 5760 (10.6.100.8) and purchased some LAP 3702;

All my WLCs and LAPs are in the same subnet.

I configured a DNS entry for cisco-capwap-controller.domain.com with the IP 10.6.100.8 which is my new 5760 cluster.

 

Now, here is the issue:

When I boot a new LAP 3702, I would like it to join my new 5760 controller (10.6.100.8).  Hence, why I added the DNS entry.  But, the LAP 3702 joins the 5508 (10.6.100.6) instead .

When I connect to my AP with a console cable, I see the controller trying to connect to 10.6.100.5, but it says that the controller does not have the right code (which I expected because the code is not supported with the 3702), then it tries to connect to the 5508 (10.6.100.6) and it connects to it.

Is there a way to stop the 5508 of answering to broadcast requests from LAPs?

It looks like the LAP is sending a broadcast, but receiving answers from WLCs in IP order....10.6.100.5 and then10.6.100.6 without going to 10.6.100.7.

 

Thanks for your help.

 

 

2 REPLIES

Are all the WLC in the same

Are all the WLC in the same mobility group as well as the same subnet?

Is the 5760 .7 or .8?

 

If you can put the new 3702 on their own subnet you can use an ACL to block UDP 5246 from going to the .5 and .6 WLC

 

HTH,

Steve

HTH, Steve ------------------------------------------------------------------------------------------------ Please remember to rate useful posts, and mark questions as answered
VIP Purple

Hi,You cannot have 4404,5508

Hi,

You cannot have 4404,5508 & 5760 in same mobility group (as 4400 not supported "new mobility"). You can make 5508 & 5760 in same mobility group as long as your 5508 configured for this feature. I believe you do not want that & you are phasing out 4404 after migration. Here is what you want to do if you require roaming clients between 5508 & 5760.

http://mrncciew.com/2014/05/06/configuring-new-mobility/

What you should do is once 3700 AP register to your 5508, change the primary controller (AP High Availabiity tab) name & IP to 5760 details. Keep the 5508 as secondary & see how that goes.

 

Also keep in mind all AP models are not supported in IOS-XE (5760,3850,3650 etc) specially non 802.11n AP (1131 in your case)

http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html

 

HTH

Rasika

**** Pls rate all useful responses ****

 

27
Views
0
Helpful
2
Replies
CreatePlease to create content