RF Optimisation in dense Lab deployments 8.0.1

1. With so many AP's so close together, its best to disable your 2.4 GHz radios.

When AP's are too many and too close together as often happens in LAB situations, it's best to not use your 2.4 GHz radio in ap-mode. One nice option is to change the mode of your g radio to am-mode.

2. Disabling channel bonding on your controller's APs and interfering APs.

Configure your AP's to disable channel bonding on your 5 GHz radios, this make more channels free for you and your classmates AP's to choose from.

Note: it is a good idea to keep a minimum distance of at least 10 feet between APs. There is a certain amount of interference between radios even if they are running on 5GHz but different channels.

you can copy and paste this into your Mobility Master console:

cd /md configure terminal rf dot11a-radio-profile "default" cell-size-reduction 55 no very-high-throughput-enable no high-throughput-enable max-channel-bandwidth 20MHz eirp-min 6 eirp-max 9 rf arm-profile "default-a" no 80MHz-support 40MHz-allowed-bands None min-tx-power 6 max-tx-power 9 rf dot11g-radio-profile "default" mode am-mode rf ht-radio-profile "default-a" 40MHz-intolerance exit write memory

After you have applied these changes, your WLAN Client will still not connect reliably to your WLAN service

The windows drivers degrade while facing such serious interference issues so it helps quite a bit to disable then reenable the WLAN drivers. Some times that is not good enough though and rebooting the PC client is required. To do that type the following in a command console: shutdown /r /t 0