Feature Compatibility

RUCKUS One checks feature compatibility by identifying devices that are compatible and incompatible with specific Wi-Fi features.
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 Compatibility 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.)

Feature Compatibility is a new, always-on functionality that alerts users when access points are not compatible with certain Wi-Fi features. Incompatibility may occur due to the use of legacy APs, or APs running older firmware versions, that do not support newer features.

RUCKUS One ensures that AP compatibility issues are easily and quickly identifiable at the venue and Wi-Fi network levels:

  • Displays an informational icon in the Devices and APs columns on Venue and Wi-Fi Network pages, respectively.
  • Displays an interactive banner message alerting you to the number of APs with feature incompatibility and allowing you to view the incompatibility details in a sidebar.
  • Displays a Feature Compatibility column (which you can enable or disable) in the list of APs for a specific venue or Wi-Fi network, reflecting the compatibility status for each AP. Status values are Fully compatible, Partially compatible, or Unknown. Partially incompatible is interactive; clicking this value opens an Incompatibility Details sidebar.

    The Incompatibility Details sidebar contains the AP model, the current AP firmware version, feature name for which AP incompatibility exists, and the minimum AP firmware requirements. In the Min. Required Versions column, pause the pointer on the firmware version to view the AP model families (denoted by their applicable IEEE 802.11 standard) that support the specific Wi-Fi feature.

    ACX-67432

Feature Compatibility provides the following benefits:

  • User Experience: Requires minimum customer actions to support End of Life (EOL) AP models when compared to alternative solutions such as splitting the venue to handle EOL devices.
  • Flexibility: Allows maximum flexibility for customers in terms of upgrading or downgrading device firmware versions.

Requirements

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

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

The following Wi-Fi features are supported for feature compatibility:

  • BSS Coloring
  • QoS Mirroring
  • Dynamic Simultaneous Authentication of Equals (SAE)
  • Automatic Frequency Coordination (AFC)
  • Switchable Radio Frequency (RF) support
  • 6G Outdoor (or Indoor) Channel Range Separation
  • Sticky Client Steering
  • Location Based Service (LBS)

Refer https://jira-wiki.ruckuswireless.com/pages/viewpage.action?spaceKey=ACX&title=%28ACX%29+Feature+Requirement to update this section.
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

RUCKUS One automatically checks AP compatibilities whenever a venue or network configuration is modified. While device-to-feature incompatibility will not result in a configuration change failure, legacy AP models and older AP firmware versions cannot support the latest Wi-Fi technologies and features. You should view the administration Activity Details associated with any venue or network configuration change to see a report listing every incompatible device and the feature with which it is incompatible.

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

This feature has no prerequisites to feature enablement or usage.

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: Viewing Existing Venues