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.
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.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...