01-26-2018 07:51 AM - edited 07-05-2021 08:10 AM
I have a pair of WLCs, both with APs on, both serving Clients within the same, quite large, coverage area. Both WLCs are connected to all of the same VLANs, both are in the same Mobility Group, etc. The SSID we have uses WPA2-AES (802.1X) and we use Interface Groups (which are identical across both WLCs).
I have noticed that when people roam from one WLC to the other, they often do a L3 roam instead of a L2. Given that both WLCs are connected to all the same Subnets, why is an Inter-Controller L3 roam happening? It should do an Inter-Controller L2 roam and the Client's session should be transferred to the new WLC...
Anybody else got this problem? Or any insights on how to troubleshoot?
Cheers,
Richard
01-26-2018 07:54 AM
What you should be seeing is the the client is mobile. Meaning that the original controller the client was on will anchor the traffic to the other controller. As long as the interface names and interface group names are identical, the client should roam and keep the same IP address and be placed on the same interface within the interface group.
01-26-2018 07:56 AM
01-26-2018 08:23 AM
01-26-2018 08:32 AM
01-26-2018 10:00 AM
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