We are seeing evidence of "sticky clients", clients that remain associated to access points that are far away, when a user moves between floors of a building.
I admit to being new to supporting optimized roaming on Cisco controllers (after having easily supported this on Aruba controllers for the past several years, by using Client Match.) What are the pros/cons of implementing Optimized Roaming on Cisco Controllers? We don't currently have it enabled here, and it may never have been before. One of the caveats before enabling it is "Disable 802.11a / 802.11b network before changing Optimized Roaming Interval value" ... this means I have to disable the 802.11a and 802.11b/g networks on the controller, enable Optimized Roaming, tune the interval value, re-enable the 802.11a and 802.11b/g networks ... this sounds like an outage, yes ? -- Will Dawes - Aruba ACMA Network Engineering and Architecture University Networking and Infrastructure Louisiana State University 200 Frey Computing Services Center, Baton Rouge, LA 70803 office 225.578.5926 wda...@lsu.edu<mailto:wda...@lsu.edu> ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
