Pervasive Wireless for BYOD Webinar: Q&A Session
We recently recorded a webinar on Pervasive Wireless for BYOD. If you missed the webinar, you can find a recording of it here. During the session there were a number of great questions that came up and we felt it would be good to post them on the Cisco Mobility Blog. Here is a selection of the most informative questions from the session:
1) Non-overlapping channels in 802.11 are always an issue. How many non-overlapping channels will there be in 802.11ac?
That depends on the deployment strategy and the benefit of the extended channels. Initial increases in efficiency with new modulation are expected to be the biggest impact initially. However it is likely that we will see a lot of devices being released with 1 spatial stream supporting only 20 or 40 MHz. For more information on the channel breakout of 802.11ac, we have written an 802.11ac technical white paper.
2) What is the best way to handle the “hotspot” functionality built into many of these smart phones? I regularly see them show up as rogues, but I don’t know how much I should concern myself with tracking them down.
This is a general concern for smartphones and tablets that can operate as a local hotspot. Tethering can also be a security concern. The companies we work with are dealing with them in different ways.
One way is to have an IT policy that lets employees know your business policy and if it is permitted or not. If you want more IT control, you will likely need to look into a device client such as an MDM to be able to enforce a policy on the device.
In practical deployments like high density deployments for instance, it is important to have a policy that provides easy access to a managed network which will greatly reduce incidences like this.
3) Is the recommended “probe cycle count” for Bandselect on the WLC 2? It’s the default but wondering if I should modify the default Bandselect settings to get a few more clients into the 5GHz space.
Yes, you certainly can. Initially the default was 3 when we introduced it. However, it caused problems with some legacy 2.4 GHz only devices. So there is no reason not to try 3 now. Also, it is good to change the default level from -90 to something more appropriate for the designed cell.
4) We are in the midst of expanding the number of our Access Points; we have far too few for the demand in our large hospital setting.
This is a common issue these days. Take a look at the HD Design guide that we have written; specifically the principles that apply to all HD environments which is what hospitals are.
5) Is there an upgrade path from ACS (Access Control Server) to ISE (Identity Service Engine)?
Yes. You can substitute ISE for ACS as a first step, handling the Authorization functions and being BYOD ready. Take a look at our ACS Migration At-A-Glance for more information.
Stay tuned for our next webinar: High Density Wireless Networks for Higher Education which is on Sept. 27th at 8: AM PDT.Tags: