Sticky Client Steering

Sticky Client Steering improves Wi-Fi performance by redirecting clients with poor Signal-to-Noise Ratio (SNR) to more optimal APs.
This topic is reused between RUCKUS One and Unleashed. Pls use conditions as required.
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 WLAN level (disabled by default)
  • Enables you to configure Sticky Client Steering and configures the SNR Threshold and Neighbor AP fields at the WLAN 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

Make sure to upgrade to the supported Unleashed firmware.

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

Consider the following when configuring and using this feature:
  • The Sticky Client Steering setting is not visible unless Load Balancing is enabled.
  • Each radio type is separately migrated per the following rules and can be migrated mixedly. Following are the system behavior changes for Background Scanning after the firmware is upgraded to Unleashed 200.18:
    • Client Load Balancing: If Client Load Balancing is enabled, the setting is retained as is after the migration.
    • Background Scanning:
      • If one of the radio type that performed Background Scanning is disabled and Client Load Balancing is disabled, Background Scanning is migrated as enabled and the interval is set to 60/60/20 for the 2.4, 5, and 6 GHz radios, respectively.
      • If one of the radio type that performed Background Scanning is disabled and Client Load Balancing is enabled, Background Scanning is migrated as enabled and the interval is set to 20/20/10 for the 2.4, 5, and 6 GHz radios, respectively.
  • Sticky Client Steering and SmartRoam features are mutully exclusive. Enabling Sticky Client Steering from the web interface or AP CLI takes precedence over SmartRoam, preventing SmartRoam from disconnecting clients. When Sticky Client Steering is disabled, SmartRoam automatically resumes its client steering operations.
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

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

Consider the following best practices when implementing 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

Following are the prerequisites:

  • Upgrade Unleashed to release 200.18 to configure Sticky Client Steering.
  • Load Balancing must be enabled before the Sticky Client Steering setting can be accessed and configured.
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: Client Load Balancing