RUCKUS AI Release Notes

Introduction

This document provides RUCKUS AI software release information, including new features and enhancements, along with known issues, resolved issues, prerequisites, and support information for this release.

How Do I Get Support?

For product support information and details on contacting the Support Team, go directly to the RUCKUS Support Portal using https://support.ruckuswireless.com, or go to https://www.ruckusnetworks.com and select Support.

RUCKUS AI Updates

This section outlines the changes introduced in RUCKUS AI over time.

January 2025

  • The Health page includes new KPI metrics for wired networks, such as Multicast Traffic Compliance, Interface Health Compliance, and DHCP. These metrics enable you to measure network compliance against SLA goals and provide the ability to drill down by network segment and time for detailed analysis.

    As part of this update, all existing and newly added wired KPI metrics now require switches to run FastIron firmware version 10.0.10f or later as a minimum prerequisite.

  • A new Wired AI Security category has been introduced to include TCP SYN DDoS incident detection. This feature detects TCP SYN attack incidents, provides notifications to users, and recommends appropriate remediation actions to mitigate potential threats. This functionality requires switches to run FastIron firmware version 10.0.10f or later as a minimum prerequisite.
  • The incident previously labeled as 'Sub-optimal WAN throughput' has been renamed to 'Physical link speed/duplex mismatch between AP and upstream device' with its severity level adjusted to P4 for better alignment with the behavior. It is reported as a single Zone-level incident, reducing the number of individual incidents in the Incidents table and simplifying incident management. Additionally, the updated incident includes detailed information about affected APs, providing greater clarity and actionable insights to streamline troubleshooting processes.
  • Client Troubleshooting workflows have been enhanced with:
    • The inclusion of Roam Type in the connection event details pop-up.
    • The addition of BTM sent and received request details.
  • Enhancements have been introduced to enable AP filtering by MAC address across multiple AI feature sets. This ensures accurate identification of APs in environments with large sets of devices sharing similar names.

Prerequisites

This section describes the prerequisites for the product.

  • When there are more than one node in an SZ cluster, AI Driven Cloud RRM needs SZ firmware 5.2.2.0.1563 with KSP (ER-11990_FixRAServiceValidation_5_2_2_0_1563-v1_863521.ksp)/ 6.1.1/ 6.1.2/ 7.0 and later for it to work.
  • Before logging in to RUCKUS AI, ensure that you have configured the Northbound Data Streaming to enable data transfer from the controller, and configure the controller to enable historical connection failures and client events.
  • AI-Driven RRM is supported only in SmartZone controller 5.2.1 and later.
  • AI-Driven RRM is supported only in zones without mesh configurations.
  • AI-Driven RRM is supported only if all APs in the zone are fully licensed, and you should not add unlicensed APs to the zone at a later stage.
  • AI-Driven RRM works only if the zone APs transmit enough traffic data.
  • If you experience a SZ issue in a cluster with more than one node, that will be fixed only with 6.1.1. Then you must provide three days of AP peer data (surrounding AP or neighbor data) for RRM to compute and display the recommendation patterns.
  • In the Overview and Wired tabs of the Health page, data is displayed only for switches running FastIron firmware version 10.0.10d or later.

Known Issues

This section describes the known caveats and limitations of the product.

Known caveats describe unexpected actions within a product. The following are the current active caveats that may have been applicable in previous releases. A caveat that remains unresolved from a previous release will have an impact on all future releases until it is resolved.

General
  • RUCKUS AI requires at least one AP to be connected to the SZ/vSZ.
  • PCAPs are displayed within 15 minutes of the failure time.
  • WPA2-PSK authentication failure is displayed as EAP failure.
Network Health
  • The aggregate metrics panel in the Wired tab of the Health page remains independent of the custom SLA defined in the KPI charts; instead, it follows the default thresholds.
  • The Health page includes stack ports in the total port count calculation.
  • The aggregate value displayed in the DHCP Success metrics panel on the Wired tab of the Health page may not be consistent with the underlying DHCP failure counts associated with the switches.
Report and Data Studio
  • Report generation (database) timeouts may occur for data older than one month or report periods exceeding 2 weeks, depending on the data volume. The problem can be alleviated by shortening report periods, scheduling reports to run during off-peak hours, or generating reports during off-peak hours of the region.
  • In Data Studio, native filter has no effect for schedule reports and dashboard export csv.
  • In Data Studio, the filter applied on the Schedules page resets when you toggle between Admin and Brand modes. You have to apply the filter again.
  • If Data Studio is opened in two different tabs or windows, toggling between Admin and Brand modes in a window will impact the other window or tab.
  • Reports on new RUCKUS AI UI do not support multiple AP selection.
  • For scheduled reports and dashboards, if the query times out, no reports or dashboards will be sent.
Service Validation
  • Service Validation uses SpeedTestC which has limitation and shows lower speedTest results than the normal clients test.
  • Service Validation for WLAN will fail if Guest Access Portal is enabled with Always Accept authentication mode.
  • Service Validation does not work for APs that are configured with DHCP/NAT.
  • In Service Validation, Ping/Tracert/Speedtest uses the station AP DNS instead of the client subnet DNS.
  • Mesh APs cannot operate as station APs in Service Validation with virtual wireless client.
  • For new SSIDs, Service Validation tests with virtual wireless client may take up to 24 hours after the SSID is created.
Video Call QoE
  • RUCKUS AI may take up to 30 minutes to display detailed Wi-Fi data of zoom call participants.
  • If the Zoom call participants are connected through the VPN, then the Zoom server reports the clients as "wired" though they are connected to RUCKUS Wi-Fi.
IntentAI
  • In AI-Driven RRM with Automated Frequency Coordination (AFC), the Opclass parameter is not considered along with the AP channel width, which prevents the AP from operating in Standard Power (SP) mode.
  • If a non-default DP group is being used, SmartZone's zone version and DP group version must be identical for the RUCKUS AI recommendations to function properly.
  • AI-Driven RRM does not operate when zone has active mesh APs.
  • When there are more than one node in a SZ cluster, AI Driven RRM needs SZ firmware 5.2.2.0.1563 with KSP (ER-11990_FixRAServiceValidation_5_2_2_0_1563-v1_863521.ksp)/ 6.1.1/ 6.1.2/ 7.0 and later for it to work.
  • In cases where the number of APs is increased by a large percentage or the channel range is greatly reduced after the AI-Driven RRM recommendation is applied, the number of interfering links may show an increase over the original value (before the network changes). This indicates that the network conditions had changed and interference cannot be driven to zero. However, AI-Driven RRM still runs in the background and provides the best possible channel plan given the new network conditions.
Configuration Change feature
  • Firmware changes in SmartZone are not recorded as a configuration change.
  • SmartZone controller configuration changes at system level, domain level, profile configuration, creating and deleting zone, WLAN, WLAN group, AP group, AP and those related to moving APs between zones, and AP groups are not supported.
  • Some configuration values such as Channel fly optimization period and AP time zone are not displayed in user-friendly format.
  • Multi-level configuration for parameters such as SNMP v2/v3 agent information and AP model specific configurations are not displayed.
  • Configuration change entries are not displayed when WLAN QosMapSet state is changed from disable to enable, after editing Internal DPSK WLAN, after changing RGRE to SGRE in CCM GBP, and for QinQ.
Wireless Clients
  • On the Client Troubleshooting page, the radio information for BTM events associated with the upper 5 GHz radio in APs operating in 2-5-5 mode is currently displayed as '5 GHz.' The radio information for connection and disconnection events is displayed accurately as '6(5) GHz.'

A few features are available in the new RUCKUS AI web UI, but when you click on these features, you will be redirected to the old RUCKUS Analytics web UI. You can use the old RUCKUS Analytics web UI to access features that are not visible in the new RUCKUS AI web UI.

Resolved Issues

This section describes resolved issues in the release.

November 2024

  • Resolved an issue where the Top AP Reboot Reasons widget in the AP Report displayed incorrect data. (ER-13131)
  • Resolved an issue where email alerts for P1 incidents were not sent to the configured recipient address, and a major P1-level event was incorrectly classified as a P4. (ER-13927)
  • Resolved an issue where client load balancing recommendation showed wrong details. (ER-13775)
  • Resolved an issue where a user was labeled as 'internal user' in two different RUCKUS AI accounts. (ER-14000)
  • Resolved an issue that caused the service validation test to fail. (ER-12927)
  • Resolved an issue where changes to the account name were not reflected in RUCKUS AI. (ER-14046)

August 2024

  • Resolved an issue where the onboarded vSZ and any related data were not available in RUCKUS AI. (ER-13870)
  • Resolved an issue where the AI-Driven RRM recommendations for rogue APs affected radio settings. (ER-13864)
  • Resolved an issue where the invited third-party user could not access AI-Driven RRM and AI Operations. (ER-13845)
  • Resolved an issue where enabling and disabling of band balancing were misrepresented in the Configuration Change page. (ER-13789)
  • Resolved an issue where the Service Validation tests failed to complete and the report was not generated due to a timeout. (ER-11990)
  • Resolved an issue where the SmartZone controller onboarding process was stuck in queued status. (ER-13661)
  • Resolved an issue where Data Studio dashboard could not be imported into other RAI accounts. (ER-13809, ER-13581)
  • Resolved an issue where Webhook URLs containing authentication information were not supported. (ER-13766)
  • Resolved an issue where Onboarded Systems and Licenses page failed when too many tenants enabled support access. (ER-13716)
  • Resolved an issue where Incident analytics did not provide root cause analysis and recommended actions for P4 incidents. (ER-13549)
  • Resolved an issue where email notifications for incidents were not sent to the configured email addresses. (ER-13656, ER-13641)
  • Resolved an issue where service validation profiles could not be edited. (ER-13514)
  • Resolved an issue where Peer data was not sent to RUCKUS AI. This data is required in order to have AI recommendations. (ER-13529, ER-13324)
  • AP patches are delivered in R6.2.1, R6.1.2 to distinguish Captive Portal self-sign from Radius failures in RUCKUS AI. (ER-12188)
  • Resolved an issue where client or wireless related incidents or data could not be traced on Ruckus Analytics. (ER-12736)
  • Resolved an issue where an internal server error occurred when attempting to view a chart in the Data Studio dashboard using the View chart in Explore option. (ER-13548)
  • RUCKUS AI has a fix to handle situation when SZ does not handle 6G radio. (ER-13453)
  • Resolved an issue where some users did not receive third-party invitation. (ER-13509)
  • Resolved an issue where DHCP failed during service validation when the WLAN was hidden. (ER-11372)
  • Resolved an issue where the SmartZone controller onboarding process was stuck in 'Create Streaming Profiles' status. (ER-13477)
  • Resolved an issue where the Data Studio report for wireless clients was throwing timeout errors when polling old data. (ER-13387)