Controller Assisted Mobility

[Gary_Hartstone]

Seeking any feedback on the "Controller Assisted Mobility" feature which can be enabled on WLAN>Client Settings.
I have a older Distribution Center site running 2 RFS7000s. Site has 3 buildings assigned to their own unique RF Domains. Building 1 has 60 AP621s, Building 3 has 30 AP621s and Building 3 has 20 AP6522s. All APs are configured for IPLayer3/MintLevel1 adoption. The main WLAN is tunnelled back to the controller and configured with a VLAN pool of 4 VLANs. Problems occur when forklifts move between RF domains, and on recent rare occasions MU disassociations result in MUs being assigned to a new VLAN. I've seen the following webpage https://extremeportal.force.com/ExtrArticleDetail?an=000064277 which recommends implementing Controller Assisted Mobility for these issues, but when implemented I can't see any difference in the GUI or way of confirming if a roaming database is being maintained by the controller. any feedback would be appreciated, thanks.

[Alona]

It works in 5.5.6. It was broken much later

[Shay_Weir]

The Smart-RF policy that manages this does not work. It is fixed though in WiNG 5.9. We tried the by floor, by area and Smart-RF did not do the proper calculation. Wait for 5.9. I would still enter the information into the device\AP level profile so that you have this in place for future use.

[Shay_Weir]

Is there a reason why you have 3 rf-domains for this location? Why not a single domain, 3 WLANs, use the extended vlan parameter in the controller profile? Each WLAN can have its own VLAN\DHCP scope, security settings, device specific settings, data rates. We have several large fulfillment centers (3million square feet) using this configuration. The clients range from tablets, to lifts, to wearable, handhelds and wireless printers. This design works well. All traffic is tunneled back to the controller to allow for roaming between areas. Just a thought for a simple configuration.

[Shay_Weir]

Makes sense. We moved from Cisco 1200's (and 5508 controllers) to ap7532 and ap7562 (nx7510 WiNG controllers) for several facilities. Each facility has about 200 APs. We started using the 8132 initially because of their industrial look and feel, but found out the ap7532 (which came out mid conversion) works just as well if not better and offered 802.11ac. Extreme has some newer models in the works that have more features to support these environments. Talk to your rep about what is coming up. You may be surprised.

[Gary_Hartstone]

Thanks for the feedback. At the time we were moving from L2 to L3 adoption and migrating from multiple RFS6000s. With the memory limitations of the AP621s it seemed easier to have each building have their own RF Domain.