How does Aruba address it? Well, it’s pretty complicated. The Aruba APs collect all the “beacon reports” from the clients in the network and forwards them to the “report process” (in their controller). This information contains SNR, MAC, RF band, and possibility other information about the client. All this information is processed to identify “unhealthy” clients; clients with low data rates or high SNR values. Their solution also takes in consideration of access points that may be “congested”. All this information is then processed and a roam strategy is developed for each selected client. An ideal access point(s) is selected for the client and the “guided” roam preparation begins. Client blacklists or white lists are generated for a set of APs to reduce the number of acceptable APs to the desired client. Once in place, the client is disassociated and put on a temporary blacklist for the current access point. The client’s roaming mechanism is then invoked and it attempts to find a new access point with which to associate. Whew! As a mobile user continues to move throughout a facility, the sequence is repeated multiple times. While AP chatter to the controller is on the Ethernet backplane, it is easy to see that the traffic load might quickly escalate to erode total network throughput within large, highly mobile networks.
Meru, dedicated to fully supporting mobility since its founding in 2002 has always addressed this issue and our customers know and love it. Meru’s Air Traffic Control and Virtual Cell, clients are seamlessly moved from AP to AP to optimize the client’s experience and to minimize network congestion. This has always been the case. For more information, just go here: http://www.merunetworks.com/products/system-director-os/virtual-cell/index.html.
Looks like others in the market are finally catching up to Meru.