Looks like Cisco finally acknowledged that BYOD is part of “Voice over Wireless” solution which they have to support. In the past Cisco TAC only support if customer is using Cisco wireless phone (7925/7921) in their Voice over wireless deployment & not any BYOD as wireless client.
With Jabber client release for any BYOD, almost all customers want to use that as wireless end device to deliver voice/video services over wireless. This WLAN Best Practice for Apple Devices document guide you how to configure your Cisco WLAN to support Apple Devices.
I found this from the below blog you may want to go for further related information.
I wonder if you had an update on this since Fast Transition and everything has been released. I am struggling in a HealthCare/Hospital environment that I need to support iphones & ipads everywhere, and yet still have legacy devices that could possibly break. The only thing I can possibly do and hopefully with Security’s blessing is to create an additional SSID which I already have 3-4 for Guest, and some other sister company’s network support.
An additional question I am looking for information on Dual Band Neighbor List (802.11k). My thought is, if you have a device that roams off 5ghz and you don’t have Dual Band Neighbor List turned on, can it still get 5ghz? Many times I see in Catalyst Center that a device wants to remain on 2.4 even when 5ghz is available. So my thought is, it got off 2.4 and because Dual Band Neighbor list is not turned on then maybe it wont connect to 5ghz?
Hi Dave,
I understand it is a challenge to implement 802.11r in such an environment. Without having some control over the endpoints you bring into your Wi-Fi environment, it becomes a difficult task.
“Many times I see in Catalyst Center that a device wants to remain on 2.4 even when 5ghz is available” – It is purely client decision to stay on 2.4GHz or go to 5GHz based on its roaming algorithms configured. Having neigbour list via 11k or active scanning helps, but it does not enforce client to roam.
HTH
Rasika