The following section provides information on the new features and enhancements in this release.

• ZoneDirector Migration Tool: Make it easy to upgrade from your existing infrastructure! RUCKUS One now supports the import of ZD configuration files. RUCKUS One will build a new venue based on your imported ZD configuration, reconnect and reimage all supported access points, and provide great visibility into the process.
• Sticky Client Steering: Many times, wireless clients suffer from poor roaming experience, stubbornly remaining attached to a faraway access point while a nearer, stronger signal goes unused. Sticky client steering takes advantage of SmartRoam, the RUCKUS patented wireless roaming technology, and interoperation with IEEE standards to drive clients to connect to the best RF signal available. Sticky Client Steering is configured at the venue level and offers great support for connected sticky clients while gently directing them to use a better signal.
• Mesh Enhancements: Mesh operation in RUCKUS One now includes support for a custom SSID/PSK for mesh, as well as support for both 2.4 GHz and 5 GHz/6 GHz operation. Specific APs can now be manually configured as root nodes, mesh nodes, or to not participate in a venue's mesh configuration. This allows the operator to deploy and fine-tune the exact mesh configuration needed for their environment.
• New Admin role: DPSK Manager: We continue to expand role and responsibility delegation in RUCKUS One. The latest addition is the DPSK Manager, an administrative user whose sole responsibility is creating, disseminating, and managing Dynamic Pre-Shared Keys. Similar to a guest manager role, this user can only interact with DPSK related services. Additional Admin roles will be available in upcoming releases.
• Upcoming change to API rate-limiting: Starting next month, the RUCKUS One APIs will include rate limiting to several of the APIs. A rate limit is the number of API calls an App or user can make within a given time period. If this limit is exceeded, the App or user may be throttled. API request made by a throttled user or App will fail. The API will return a 429 to indicate rate limiting has been encountered. Each set of APIs which have rate limiting will identify the limits for those APIs in the API information included with each API section. The rate limit is determined by the following three key aspects:
  • The key that is used. For RUCKUS One, the key is the tenant ID.
  • How many calls are permitted per minute for each tenant.
  • How fast the number of calls allowed is restored. To prevent a flood of API requests, the rate limiting only allows a fixed number of APIs to be restored after the limit is encountered.