Sticky Client Steering

Sticky Client Steering improves Wi-Fi performance by redirecting clients with poor Signal-to-Noise Ratio (SNR) to more optimal APs.
To provide an overview of a feature and its benefits. May require several Concept topics to keep content in short, manageable, and reusable chunks of content.

The intention of this new template is to outline the information that you will need to collect from SMEs and provide to readers.

NOTE: Feature Configuration / Troubleshooting are *not* part of the Feature Concept template. These templates are likely to be part of seperate task/reference templates (to be developed).

General Notes for Concept Topics:
  • Optional sections are to be used with discretion based on the feature characteristics.

Feature Overview

This section is required. Providing detailed and accurate information in the feature overview is crucial as it helps users understand the functionality, benefits, and usage of the feature. Moreover, it ensures consistency in communication across all platforms, enhancing user experience and product perception.
  • What is the name of the feature? (What do users call the feature? If the feature is referred to by an acronym, what is the acronym expansion? What is the formal name to be used in documentation?)
    Note: Typically, the name is used as part of the section titles, such as the overview title and the configuration section titles.
  • Where does the feature fit within our taxonomy? (What are the taxonomy group and sub-group? This information is important for categorizing the feature documentation and incorporating it into the existing document sets.)
  • What standard or standards govern the feature? (Sometimes needed.)
  • Is the feature a new feature or an enhancement to an existing feature?
  • Does the feature replace another feature?
  • What does the feature do? (General description)
  • How does the feature benefit the user?
  • What set of terms do the writer and reader need to know to understand the feature and its use?
  • How does the feature work? (Detailed description, if needed.)

The Sticky Client Steering Configuration feature uses Adaptive Client Load Balancing (ACLB) that collects statistics from the client and neighboring APs to make an informed decision to direct the client to roam to a better AP in the following manner:

  • Enables you to configure Load Balancing at the venue level (disabled by default)
  • Enables you to configure Sticky Client Steering and configures the SNR Threshold and Neighbor AP fields at the venue and AP levels

The purpose of the Sticky Client Steering is to identify the sticky clients and assist them in transitioning to a better AP. The Sticky Client Steering algorithm monitors the received SNR from the client. When the SNR drops below the configured threshold value, the client steering process scans the neighboring APs that can provide better service to the client. A BSS Transition Management (BTM) Request frame is sent to the clients that support BTM. Depending on each client's response, the algorithm will take additional steps to transition the client, which may include disconnecting any client that does not support BTM and reinforcing scanning and finding a neighboring AP with a better service potential.

Based on IEEE 802.11k, the AP uses the beacon report response to check the SNR of the servicing AP as seen by the client. If the SNR of an AP exceeds the threshold set, then the AP is classified as a Neighbor AP.

Following are the benefits:

  • Enhanced user experience and dynamic adjustments: Automatically steers clients to APs with better SNR based on real-time conditions.
  • Optimized network performance: Ensures a balanced load across APs, preventing any single AP from becoming overloaded.

Requirements

  • Sticky Client Steering configuration at the AP level is supported only for AP firmware 7.0.0.300 and later versions.
  • Ensure that Load Balancing is enabled at the venue level to configure Sticky Client Steering at the venue and AP levels.
  • Ensure Background Scanning is enabled to maintain accurate data on neighboring APs and their available capacities.
This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

If there are no requirements, use the following default wording:

This feature has no special hardware or software requirements for feature enablement or usage.

If there are requirements, include the applicable below points (depending on product line):

  • What releases support the feature?
    Note: Typically, this is not documented in the configuration guides; however, we need to know where to include the information.
  • What hardware models support the feature?
  • Does the feature require specific modules?
  • Does the feature run only on certain ports?
  • Does the feature have special memory requirements?
  • In an integrated system, can the feature be managed or configured from another device? What are the related release and system requirements?
  • Does the feature introduce new user requirements?
  • Does the feature introduce physical or location-based requirements?

Considerations

  • By default, the AP-level Sticky Client Steering setting uses the venue-level configuration. You can customize the Sticky Client Steering setting per AP if Load Balancing is enabled at the venue level.
  • If Sticky Client Steering is enabled at the venue and AP levels, the SmartRoam feature (can only be configured using AP CLI) is disabled.
  • If the AP does not support the required firmware version to configure AP Sticky Client Steering, RUCKUS One returns an error and the preconfigured venue-level settings are retained.
  • At the venue level, the Sticky Client Steering setting is not visible unless Load Balancing is enabled.
  • If the AP does not support the Sticky Client Steering feature, then this setting is greyed out and disabled in the AP-level setting.
  • If you disable Load Balancing at the venue level, the AP Sticky Client Steering configured at the AP level under that venue will be disabled.
  • When an AP is moved to another venue, the AP-level Sticky Client Steering configuration will reset to venue-level settings.
This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

If there are no considerations, use the following default wording:

This feature has no special considerations or limitations pertaining to feature enablement or usage.

If there are considerations, include the applicable below points (depending on product line).

Note: A separate section on Limitations may sometimes be needed.
  • Does the feature replace an existing feature?
  • Does the feature work only with a certain protocol or with a limited set of protocols?
  • Is the feature meant to be used in combination with another feature or a set of features?
  • Is the feature incompatible with any features?
  • What happens when the feature is enabled?
  • What happens when the feature is disabled?
  • Does enabling/disabling the feature enable/disable another feature?
  • What system behavior changes, if any, does the feature introduce?
  • Are performance issues associated with the feature? How can these be mitigated?

Best Practices

Updating Best Practices as per Orlando's feedback. Approved by SMEs Weiguo Xie and ChiaWei Chou.

Consider the following best practices to configure Sticky Client Steering:

  • Set Appropriate Signal Thresholds: Start with the default SNR threshold values. In environments with high interference or dense AP deployments, you might need to increase the SNR threshold.
  • Monitor Client Device Behavior: Regularly monitor the behavior of client devices to understand their roaming patterns and adjust the steering settings accordingly. This can help in fine-tuning the settings to match the specific environment and client device types.
  • Adjust AP Power Levels: Ensure that the transmit power levels of APs are set appropriately. Too high-power levels can cause client devices to stick to an AP even when a better option is available. Balancing the power levels can encourage smoother transitions between APs.
  • Test and Optimize: Start with conservative settings for steering thresholds and gradually adjust them based on observed performance. Testing in a controlled environment can help identify the optimal settings before deploying them network-wide.
  • Consider Client Device Capabilities: Be aware of the capabilities and limitations of the client devices in your network. Some devices may not support certain steering mechanisms, so it’s important to configure settings that are compatible with most devices.
This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

If there are no best practices (recommendations), use the following default wording:

This feature has no special recommendations for feature enablement or usage.

If there are considerations, include the applicable below points (depending on product line).

  • Brief list of RUCKUS recommendations on product use to optimize performance.

Prerequisites

  • Enable Load Balancing at the venue level
  • Upgrade the AP to the supported firmware version to configure AP Sticky Client Steering
This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

If there are no prerequisites, use the following default wording:

This feature has no prerequisites to feature enablement or usage.

If there are prerequisites, include the applicable below points (depending on product line).

Note: This section is sometimes part of a general overview and sometimes part of a configuration overview.
  • What are the task prerequisites that the user must ensure are met,for configuration? (For example, must you be running certain protocols, or must you configure other features first?)
Parent topic: Radio Settings