ChannelFly and Background Scanning

The controller offers the ChannelFly and Background Scanning automatic channel selection methods for spectrum utilization and performance optimization.

ChannelFly has undergone significant changes in SmartZone 5.2.1 release, combining the benefits of the Background Scanning method and the original Legacy ChannelFly. ChannelFly is the recommended method for all deployments.

Channel Selection Methods

Channel Selection Method When to Use
ChannelFly Recommended method for most deployments.
Background Scanning For existing deployments that currently use Background Scanning

Legacy ChannelFly (Accessible only from AP CLI)

When Background Scan is not allowed ‒ Legacy ChannelFly excels at avoiding excessive interference without the need of Background Scan
Note: Both channel selection methods require Background Scan, ideally with the default 20 second scan interval.

Background Scan is accessible from the zone configuration, advanced settings.

Background Scan

ChannelFly

ChannelFly uses Background Scan to collect information on the presence of neighboring APs and to assess how busy the channel is. The algorithm focuses on placing neighboring APs on different channels and avoiding busy channels. A Background Scan interval of 20 seconds is recommended for most deployments. In deployments where a larger interval is necessary, ChannelFly will still work but will take longer to settle upon a channel plan and may be less responsive to interference.

ChannelFly uses 802.11h channel change announcements to minimize the impact of channel changes on the wireless client. Despite 802.11h, channel changes still run the risk of disrupting wireless clients, and ChannelFly takes into the account the impact on associated clients.

The Channel Change Frequency (CCF) configuration allows the user to specify the responsive of ChannelFly to interference with consideration for the impact on associated clients. ChannelFly will avoid performing channel changes when a certain number of clients are associated to the AP on a per-radio basis. This threshold is defined by the CCF. With the default CCF of 33, channel changes may occur only when there are 3 or fewer associated clients. The CCF also affects the probability that a channel change occurs when a better channel is found. However, a channel change will only occur when the number of associate clients is below the client threshold as defined in Client Threshold Table.

Change Change Frequency Configuration

The following table details the threshold for each CCF. It provides the number of associated clients that would bar ChannelFly from performing a channel change.

Client Threshold Table

CCF 100 90 80 70 60 50 40 30 20 10 1
Client Threshold 10 9 8 7 6 5 4 3 2 1 0

For deployments where impact on the clients is less of a consideration and avoiding interference is paramount, higher values of CCF are recommended.

For deployments with low client counts, two or fewer associated clients per AP on average, a CCF of 10 or 20 is recommended. For deployments where channel changes are not allowed to impact any associate client, a CCF of 0 is recommended.

The Full Optimization Period configuration specifies a period of time where ChannelFly is allowed to ignore the impact of channel changes on associated clients. During this time, preferably when the wireless network is not expected to be actively servicing clients such as the middle of the night, ChannelFly will be free to full optimize the channel plan. A higher number of channel changes may be observed during this time.

The Full Optimization Period can be specified by clicking specific hours or by clicking-and-dragging across the time bar to affect multiple hours. The time periods can be non-contiguous, and the period can be disabled entirely by clicking the blue box under Time.

Configuring Full Optimization Period

For the first hour following the reboot of an AP, ChannelFly may perform up to six channel changes in order to quickly settle upon a channel plan. During this period, ChannelFly will ignore the impact of channel changes on associated clients.

The table below summarizes the channel change behavior for each of the ChannelFly states.

ChannelFly State and its Behavior

State Behavior
AP reboot Channel changes may occur at higher frequency for the first hour
Normal operation Channel changes may occur only when the number of associated clients is lower than the client threshold based on the Channel Change Frequency
Full Optimization Period Channel changes may occur at higher frequency

ChannelFly can be enabled/disabled per band. If there are 2.4 GHz clients do not support 802.11h on the wireless network, RUCKUS recommends disabling ChannelFly for 2.4 GHz but leaving it enabled for the 5 GHz band.

To revert to Legacy ChannelFly, first select ChannelFly from the controller, then from AP CLI:

rkscli: set channselectmode wifi<0/1> <mode>
   wifi0 - 2.4 GHz
   wifi1 - 5 GHz
  <mode> - 1: ChannelFly
           0: Legacy ChannelFly

Background Scanning

Background Scanning is a channel selection method, and Background Scan is the AP functionality where the AP briefly leaves the home channel to scan another channel.

Background Scanning uses Background Scan to collect information on the presence of neighboring APs. Background Scanning focuses on finding a channel with the fewest number of neighbors.

When the AP is rebooted, Background Scanning will enter a training period where the number of channel changes may be elevated in the first hour.

Background Scan is required, with the recommended default scan interval of 20 seconds. In situations where a larger scan interval is necessary, Background Scan will require a longer training period.

Note: In order to detect rogue APs on the network, you must enable Background Scan on the controller.

Note: ChannelFly Overview. This video provides a brief overview of ChannelFly.

Click to play video in full screen mode.