What can a company that completes migration to 802.11n do to avoid coexistence problems with neighboring businesses...
that still use 802.11g (for example, in multi-tenant office buildings)?
The 802.11n high throughput (HT) standard defines three modes of operation: a legacy (non-HT) mode, a greenfield (HT-only) mode, and a mixed mode where HT protection mechanisms ensure that transmissions can be detected by both old 802.11a/g/b devices and new 802.11n devices.
In mixed mode, HT protection requires that 802.11n devices send a legacy preamble, followed by an HT preamble. The legacy preamble lets 802.11a/b/g devices to avoid transmitting over HT frames sent by 802.11n devices. 802.11n devices must also, to announce their intent to transmit using legacy format CTS-to-Self or Request to Send/Clear to Send (RTS/CTS) frames that let nearby 802.11a/b/g devices sense when the channel is in use.
These HT protection mechanisms significantly reduce an 802.11n WLAN's throughput, but they are necessary to avoid collisions between older 802.11a/b/g devices and newer 802.11n devices. If you knew that no legacy devices were present, you could configure your access point (AP) to operate in greenfield (HT-only) mode, eliminating this overhead. However, in highly-congested areas, neighboring WLANs may use 802.11a/b/g long after your own clients have been upgraded to 802.11n. In such situations, operating in greenfield mode not only makes you a bad neighbor -- it can cause numerous collisions that degrade the performance of your own WLAN.
The best way to avoid this problem is to assign your own APs to use different channel(s) than neighboring legacy APs. This is relatively easy when your neighbors use 802.11b/g in the 2.4 GHz ISM band -- just make sure that your own greenfield 802.11n APs use only channels in the 5 GHz UNII band. In other words, reserve 2.4 GHz channels for legacy coexistence only, in mixed mode. However, if your neighbors also use 802.11a in the 5 GHz band, you'll want to assign your greenfield 802.11n APs to unused channels -- for example, the recently-added UNII-2e section of the 5 GHz band. Furthermore, you should avoid using 40 MHz wide channels unless you've found an unused area of the 5 GHz band in which to operate. Finally, you may want to let your 802.11n APs use dynamic frequency selection (DFS) within the range of channels that you've selected, so that they can automatically detect and try to avoid new sources of co-channel interference.
Related Q&A from Lisa Phifer
Need to send an email, check your flight's status or get ready for a presentation? You can do it all on your smartwatch, thanks to a slew of Apple ...continue reading
New and improved management features have made Android devices more suitable for enterprise use, and API and EMM tools can streamline the device ...continue reading
Whether you need a basic open source mobile device management tool for your company's Apple or Android devices, or something more customized, you ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.