Wireless Channels and Band Steering

Wireless channels are defined frequency ranges within the 2.4 GHz and 5 GHz ISM (Industrial, Scientific, and Medical) bands that Wi-Fi uses to transmit data. They exist because the radio frequency spectrum is a shared medium; dividing it into channels allows multiple devices to communicate simultaneously without interfering with each other, as long as they use different channels. In the 2.4 GHz band (2.400–2.4835 GHz), there are 14 channels defined by the IEEE 802.11 standard, each 22 MHz wide (though the channel spacing is 5 MHz, leading to overlap). In the 5 GHz band (5.150–5.825 GHz in the US), channels are 20 MHz wide, and many do not overlap because of larger spacing. The exam expects you to know the non-overlapping channels: for 2.4 GHz, channels 1, 6, and 11 (in the US) are the only non-overlapping ones. For 5 GHz, the non-overlapping channels are numerous — any 20 MHz channel is non-overlapping if adjacent channels are not used (e.g., 36, 40, 44, 48 are all non-overlapping if used with 20 MHz bandwidth).

Channel bonding, defined in 802.11n, allows an access point to combine two adjacent 20 MHz channels into a single 40 MHz channel, doubling the theoretical throughput. In 5 GHz, this is straightforward because there are many non-overlapping channels. In 2.4 GHz, bonding is problematic because only three non-overlapping channels exist; bonding channels 1+5 (40 MHz) would overlap with channel 6. The 802.11n standard allows 40 MHz in 2.4 GHz only if no other APs are detected on the secondary channel (a mechanism called "40 MHz intolerance"). The exam tests that 40 MHz is discouraged in 2.4 GHz due to interference.

802.11ac introduced 80 MHz and 160 MHz channels by bonding more 20 MHz channels. An 80 MHz channel bonds four 20 MHz channels (e.g., 36, 40, 44, 48). A 160 MHz channel bonds eight 20 MHz channels (e.g., 36-48 and 52-64). The practical throughput gain diminishes with more bonding because of increased interference and fewer available channels in dense deployments. The exam expects you to know that 80 MHz is common for 802.11ac, and 160 MHz is available but rarely used due to DFS (Dynamic Frequency Selection) restrictions and interference.

Band steering is a feature on dual-band access points (2.4 GHz and 5 GHz) that encourages client devices to connect to the less congested 5 GHz band instead of the overcrowded 2.4 GHz band. The 2.4 GHz band has only three non-overlapping channels, is shared with Bluetooth and other devices, and suffers from more interference. The 5 GHz band offers more channels, higher throughput, and less interference, but has shorter range. Band steering improves overall network performance by balancing clients across bands.

The mechanism relies on the client's scanning and association process. When a client scans for networks, it sends Probe Requests on both bands. The AP responds with Probe Responses. Band steering works by manipulating these responses:

On Cisco AireOS WLCs, band steering is configured under the WLAN advanced settings:

config wlan band-select allow <wlan-id>
config wlan band-select cycle-threshold <wlan-id> <seconds>
config wlan band-select expire <wlan-id> <seconds>

On Cisco IOS XE (Catalyst 9800), use:

wlan <profile-name>
 band-select
 client load balancing

Verification:

show wlan <wlan-id> band-select
show ap client summary | include <client-mac>

On standalone APs (e.g., Ubiquiti UniFi), band steering is a toggle with options like "Prefer 5G" or "Band Steering: Active".

A financial firm deploys 200 dual-band APs (2.4/5 GHz) across a 10-story building. Each floor has 50-100 employees with laptops and smartphones. The 2.4 GHz band is heavily congested due to neighboring offices and Bluetooth devices. Band steering is configured to prefer 5 GHz for all clients that support it. The network team sets an RSSI threshold of -72 dBm for steering to avoid clients at the edge of coverage. They also enable load balancing across APs. During a typical workday, 80% of clients connect on 5 GHz, reducing channel utilization on 2.4 GHz by 40%. 2.4 GHz is reserved for legacy devices (barcode scanners, older printers) that only support 2.4 GHz. The team monitors client distribution using a wireless controller dashboard. A common issue is that some users' personal smartphones (e.g., older models) ignore band steering and stay on 2.4 GHz, causing poor performance. The team mitigates this by creating a separate SSID for 2.4 GHz-only devices and applying band steering only to the primary SSID.

A university uses 802.11ac wave 2 APs with 80 MHz channels on 5 GHz and 20 MHz on 2.4 GHz. Band steering is enabled but with a per-client exception list for IoT sensors (temperature, door locks) that are 2.4 GHz only. The network team configures band steering with a blacklist timeout of 90 seconds to give clients more time to switch. During peak hours (lecture changes), thousands of clients roam simultaneously. Band steering must work with fast roaming (802.11r) to ensure seamless transitions. A misconfiguration causes some clients to be steered to DFS channels that are not yet available (radar detection), resulting in connection failures. The team adjusts the channel plan to avoid DFS channels for the primary SSID. They also discover that some laptop drivers do not handle probe response suppression well, causing them to disconnect and reconnect repeatedly. The solution is to disable band steering for those specific device types using MAC OUI-based policies.

A large retail chain provides free guest Wi-Fi. The network uses dual-band APs with band steering to push most guest traffic to 5 GHz, leaving 2.4 GHz for point-of-sale (POS) systems and inventory scanners that require 2.4 GHz reliability. Band steering is configured aggressively: probe response suppression on 2.4 GHz for all dual-band clients, with a short blacklist timeout of 30 seconds. However, guests with older phones (e.g., iPhone 5) that only support 2.4 GHz cannot connect because they are misidentified as dual-band (some older devices incorrectly advertise 5 GHz support). The helpdesk receives complaints. The team adds a whitelist for known 5 GHz-capable clients and disables band steering for the guest SSID. They also implement a captive portal that checks client capabilities and redirects 2.4 GHz-only clients to a separate SSID. Performance improves, but band steering is eventually disabled for the guest network because of too many compatibility issues.