This release includes the following known issues
and limitations.
Note: Known issues and limitations for individual
device firmware versions are outside the scope of this document. Refer to
Supported Hardware and Software for links to the
Release Notes applicable to
RUCKUS One supported devices
(RUCKUS APs, RUCKUS ICX switches, and RUCKUS Edge devices).
| Issue |
ACX-94548 |
| Symptom |
RUCKUS DSE: Same prompt produces inconsistent results; data appears
for the last 3 hours but not for the last 24 hours. |
| Condition |
When the data volume is very large, the system currently applies a
limit of records to ensure the query can return results within the
specified time range. Removing this limit could, in the worst-case
scenario, exhaust all Druid resources and cause a Druid service
outage. |
| Workaround |
None. |
| Issue |
ACX-88468 |
| Symptom |
RUCKUS DSE: Querying AP and switch counts at the same time may fail
to return results or may display incorrect numbers. |
| Condition |
The system does not currently support querying multiple topics within
a single request. Each query should focus on only one topic to ensure
proper results. |
| Workaround |
None. |
| Issue |
ACX-89512 |
| Symptom |
RUCKUS DSE: The values shown in the table and line chart are
inconsistent. |
| Condition |
Values displayed in the table are closer to the expected numbers,
while the ones in the line chart may show discrepancies. |
| Workaround |
Refer to the table for the most accurate consumption values. |
| Issue |
ACX-89514 |
| Symptom |
RUCKUS DSE: Refining a report or continuing a prompt thread
fails. |
| Condition |
For example, when requesting data in a table first and then
attempting to switch two columns, the operation cannot be completed.
Previously, switching columns was possible, but the resulting table data
would appear blank or display incorrect values. |
| Workaround |
None. |
| Issue |
ACX-90101 |
| Symptom |
RUCKUS DSE: In some cases, the message Failed to get
response from AI… may appear. |
| Condition |
This can occur when requesting additional information, such as client
traffic data, after querying connected wireless clients at a specific
time. The follow-up request cannot be fulfilled, resulting in the error
message. |
| Workaround |
None. |
| Issue |
ACX-86635 |
| Symptom |
RUCKUS DSE: After multiple complex or unanswerable queries, even a
simple query may fail. |
| Condition |
Occurs when several complex or invalid network-related questions are
submitted in sequence. The system may then fail to process subsequent
simple queries. |
| Workaround |
Restarting the session may temporarily resolve the issue. |
| Issue |
ACX-85683, ACX-80311, ACX-98586 |
| Symptom |
RUCKUS DSE: Some queries result in the error message: I encountered an
error while processing your request. |
| Condition |
This issue may even
occur with different queries such as the following:
- Visualizing AP Count
Trend with a line chart (Offline, Online, Total
APs).
- Displaying Wireless
Traffic and Wireless
Applications using a table, where one column shows total
traffic and another shows the percentage of total traffic.
- How many APs
do I have online vs. offline?
|
| Workaround |
None. |
| Issue |
ACX-79914 |
| Symptom |
RUCKUS DSE: The displayed unit values may differ from the expected
scale. |
| Condition |
If no unit is specified, the system defaults to bytes or
seconds. |
| Workaround |
Include the desired unit (MB, GB, and Day) in the query. |
| Issue |
ACX-80116, ACX-80226, ACX-80232, ACX-98182 |
| Symptom |
RUCKUS DSE: Queries for certain data sources may display incorrect
information instead of displaying Not
Supported. |
| Condition |
Only Druid and partially Postgres data (Incident & Client
Experience) sources are supported. The following non-Druid sources are
not supported:
- Alarm
- (count)
- Venue
- RUCKUS Edge
- RWGs
- IoT
Controllers
|
| Workaround |
None. |
| Issue |
ACX-96832 |
| Symptom |
RUCKUS DSE: Selecting an option after entering a query fails to
return data or shows Failed to get
response from AI…. |
| Condition |
This issue is related to handling conversation history and context
during Large Language Model (LLM) calls. It occurs with follow-up
queries such as Display with GBytes and selecting Human-in-the-Loop (HITL)
options:
- No data returned
after selecting a HITL option.
- Failed response
after selecting a HITL option.
|
| Workaround |
None. |
| Issue |
ACX-96857 |
| Symptom |
RUCKUS DSE displays incorrect units such as B for Bytes, and
milliseconds when the value represents the number of
counts. |
| Condition |
RUCKUS DSE automatically assigns units based on data type rather than
metric context, causing mismatched labels. |
| Workaround |
None. |
| Issue |
ACX-98765 |
| Symptom |
RUCKUS DSE: The timestamps in AI query results do not match the
user's local time. |
| Condition |
AI query results use UTC+0, however, AI Assurance displays local
timezone such as UTC+8 causing discrepancies. |
| Workaround |
None. |
| Issue |
ACX-81595 |
| Symptom |
RUCKUS DSE: Labels on line charts or bar charts may overlap, making
them difficult to read. |
| Condition |
Occurs when displaying a large volume of data; high-density data
points cause label crowding even when zoomed in. |
| Workaround |
None. |
| Issue |
ACX-80308, ACX-80307 |
| Symptom |
RUCKUS DSE: Similar queries may return different
results. |
| Condition |
Variations in how a query is worded might yield inconsistent
responses, for example: Wireless Traffic Avg
Tx Rate vs Average Tx rate of
wireless radio traffic. |
| Workaround |
Use consistent query phrasing for accuracy. |
| Issue |
ACX-80651, ACX-80410, ACX-80401 |
| Symptom |
RUCKUS DSE: AI-generated charts are less refined compared to Dashboard or Business Insights
charts. |
| Condition |
For example, pie charts do not display segment details by default. Dashboard or Business Insights
charts are more interactive. |
| Workaround |
Hover over chart segments to view details. |
| Issue |
ACX-80615, ACX-80597, ACX-80504, ACX-89252 |
| Symptom |
RUCKUS DSE: Generated charts and tables do not support percentage (%)
format displays. |
| Condition |
Metrics like Airtime Utilization or Applications
display raw counts instead of percentages format. |
| Workaround |
None. |
| Issue |
ACX-79923 |
| Symptom |
RUCKUS DSE: Only one widget format can be generated for a
request. |
| Condition |
The system does not support multiple widget types in a single query
such as a table and line chart. |
| Workaround |
Submit separate queries for each widget format. |
| Issue |
ACX-79958 |
| Symptom |
RUCKUS DSE: Answer displays are presented without
pagination. |
| Condition |
Only a scrollbar is available; pagination is not supported. |
| Workaround |
Use the scrollbar to navigate content. |
| Issue |
ACX-81412, ACX-81100, ACX-80310 |
| Symptom |
RUCKUS DSE: Charts or tables may not match expectations when queries
are ambiguous. |
| Condition |
Precise questions are
needed. Example:
- Query 1
(Failed): Display Top SSIDs by Traffic with columns:
SSID, User Traffic (Downlink MB), User Traffic (Uplink MB), User
Traffic (Total MB), Unique Client MAC Count, AP Count over last
24 hours
- Query 2
(Successful): Display Top SSIDs by client
Traffic with columns: SSID, client traffic (Downlink MB), User
Traffic (Uplink MB), User Traffic (Total MB), Unique Client MAC
Count, AP Count over last 24 hours
|
| Workaround |
Specify the metric type clearly to ensure accurate chart or tables
are generated. |
| Issue |
ACX-37453 |
| Symptom |
When a property unit is deleted, the related DPSKs will remain
intact. Activities related to unit deletion do not include DPSK
deletion. |
| Workaround |
None. |
| Issue |
ACX-33829 |
| Symptom |
User equipment is unable to roam between APs in different venues. |
| Workaround |
None. |
| Issue |
ACX-32416 |
| Symptom |
Certain AP-related data is not visible until the AP is operational
following the migration of the ZoneDirector configuration to RUCKUS
One. |
| Workaround |
None. |
| Issue |
ACX-40890, ACX-34930 |
| Symptom |
STA can connect on a PSK WLAN with MacOS Monterey and BigSur
versions, however after a while, the STA ping disappears. |
| Workaround |
None. |
| Issue |
|
| Symptom |
When using a Chrome-based browser with SAML2 Single Sign-On (SSO), users might be
redirected back to the log in page. |
| Workaround |
Use another browser. |
| Issue |
|
| Symptom |
Regardless of whether properties are assigned or unassigned to an LSP
(which is the integrator), the Brand 360 aggregate view incorporates all
properties to display data for three metrics: Property Health, Guest
Experience, and Brand SSID Compliance. However, the tabular view in the
Brand 360 aggregate view is updated properly and displays the property
data only if the properties are assigned to the LSP. |
| Workaround |
None. |
| Issue |
|
| Symptom |
When creating a unit from the property service, if identity creation files are
duplicated (either due to a duplicate passphrase or duplicate LAN port,
and so on), RUCKUS One will not halt the creation of units. |
| Workaround |
Since Activity indicates the identity creation
failure, the user can change the configuration that resulted in the
failure, or the user can delete the unit that is not associated with the
identity. |
| Issue |
|
| Symptom |
Email is not tracked during creation of the identity; email or SMS is
not tracked when the unit is associated with the portal service using
the edit operation; email is not tracked during registration of MAC
addresses. |
| Workaround |
None. |
| Issue |
|
| Symptom |
If the same device is connected to multiple identities or units using
different DPSK passphrases at different points in time, the devices will
reflect both identities or units with the last seen date. |
| Workaround |
None. |
| Issue |
|
| Symptom |
When creating identities or units from identities or venues, if DPSK creation fails
(such as due to duplicate passphrases, and so on), the RUCKUS One system
will not halt the creation of identities. |
| Workaround |
Since Activity
indicates the identity's failure in identity activity, the user can go
ahead and change the configuration that resulted in failure, or the user
can go ahead and delete the identity or unit that is not associated with
DPSK. |
| Issue |
|
| Symptom |
A connected client (with the unit's DPSK passphrase) details is not
displayed in the Identity page. |
| Workaround |
None. |
| Issue |
CMS-1090 |
| Symptom |
From RUCKUS One, you cannot configure the port speed of an ICX
7850-48F switch. |
| Workaround |
Use the following
switch CLI commands to configure the port speed:
# configure terminal
# interface ethernet 1/1/1 to
1/1/4
# speed-duplex
<speed>
|
| Issue |
ACX-31477 |
| Symptom |
Service validation test cannot be edited by an admin account.
|
| Workaround |
Only the owner of the test can edit the service validation
test. |
| Issue |
ACX-31937 |
| Symptom |
Firmware Version Management: Changing the update
schedule without selecting an update time will result in an internal
server error. |
| Workaround |
Choose the time before clicking Update
Schedule. |
| Issue |
ACX-32365 |
| Symptom |
Historical connected clients in the AI Assurance tab will be
delayed for about ~ 30 minutes. |
| Workaround |
Wait for 30 minutes for the AI Assurance health
tabs to display the connected client's data. |
| Issue |
ACX-32368 |
| Symptom |
A newly added venue, AP, or network might take a longer time to appear while creating a
service validation test. |
| Workaround |
Wait for 24 hours before the newly added entities are listed in
Service validation test. |
| Issue |
ACX-26662 |
| Symptom |
Search filter for VLAN does not work as VLAN data can be a single
digit number. A minimum of two characters is required to trigger UI
search. |
| Workaround |
None. |
| Issue |
ACX-27662 |
| Symptom |
The Firmware Version Management page lists even
the deleted venue. |
| Workaround |
None. |
| Issue |
ACX-24450 |
| Symptom |
User is not able to see zones list for linking the Client Isolation
policy profile at the time of adding new wireless network. |
| Workaround |
Create the network without selecting policies and then edit the
network to enable venue for the Client Isolation policy. |
| Issue |
ACX-24998 |
| Symptom |
Switch incidents are not listed in specific switch filter or in the
Switch tab though switches are contributing to
the venue level incidents. |
| Workaround |
None. |