03-21-2012 05:44 AM - edited 07-03-2021 09:50 PM
Wanted to poll any expert here for an issue I encountered.
We have existing AP 1132 with WLC 4404 controller implemented in a site. We started add on new AP 3502 with WLC 5508.
Our customer has existing 10 of 4404 controllers and configured in the same mobility group, and the roaming is working fine(ap are 1131).
Curently we deployed 2 new 5508 controllers and replaced some 1131 AP to 3500 AP. And the controller created new IP scheme for the wireless client. But after migrate 2 APs, we found that the roaming is not working when the wireless client move from new AP to old AP.
When moving from new AP to old AP, the ip address for the client is unchange, but the ping will be droped, and will never come back. Until we do a ipconfig flush, and reconnect, the connection can back to normal, but the ip address als changed to the old IP scheme.
Anyone can share any similar experience or advice?
TIA
03-21-2012 06:25 AM
Seems like mobility is not working correctly. There are few things... are you seeing this in one direction... Old to new or new to old? WLC code the same? WLANs setup the same? What do you see when the client roams under monitor client.
Thanks,
Scott Fella
Sent from my iPhone
03-21-2012 08:00 PM
Just confirmed that we have the necessary L3 roaming configuration in – same WLC code, same mobility group, etc.
Per wlan roaming, we should not be seeing client changing IP address and having ping drops. Any advice would be appreciated.
Sent from Cisco Technical Support iPad App
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide