Known Issues and Limitations
This release includes the following known issues and limitations.
Description |
---|
Symptom: When configuring VLANs in a network, you can only manage the VLANs for individual switches using venue-level configuration profiles. It’s not possible to configure VLANs for all switches simultaneously within the network. Workaround: Access the switch CLI to make changes. |
Symptom: When using a Chrome-based browser with SAML2 Single Sign-On (SSO), users might be redirected back to the login page. Workaround: Use another browser. |
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. |
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> |
Symptom: MacOS Monterey and BigSur version STA can connect on a PSK WLAN but STA ping is lost after some time. Workaround: None. |
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, etc.),
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. |
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. |
Symptom: DPSK deletion is not
included with activities associated with unit deletion. Workaround: During a unit deletion failure event, make sure to delete the associated DPSK passphrase manually. |
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. |
Symptom: When creating identities
or units from identities or venues, if DPSK creation fails (such as due
to duplicate passphrases, etc.), 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. |
Symptom: A connected client (with
the unit's DPSK passphrase) details is not displayed in the
Identity page. Workaround: None. |
Symptom: After the ZoneDirector
configuration is migrated to RUCKUS One, some of AP-related information
cannot be viewed until the AP comes online. Workaround: None. |
Symptom UE cannot roam across
different venues. Workaround: None. |
Symptom: R760
or R560 cannot be added to customer migrated from RUCKUS Cloud. Workaround: Minimum firmware version to support R560, R760 is 6.2.1.x. Some migrated Cloud customers may have 6.2.0.x. Ensure Venue firmware is updated to the latest firmware version. |
Symptom:
Service validation test cannot be edited by an admin account. Workaround: Only the owner of the test can edit the service validation test. |
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. |
Symptom: Historical connected
clients in the AI Assurance tab will be delayed for
~ 30 minutes. Workaround: Wait for 30 minutes for the AI Assurance health tabs to display the connected client's data. |
Symptom: A
newly added venue, AP, or network might take 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. |
Symptom: Service validation
virtual wireless clients: In certain cases, getting PSK Failure with
reason "STA Disassoc" when station and target APs operate in different
channel. Workaround: None. |
Symptom: When
you create or edit a Rogue AP Policy with new venue, the venue count is
not refreshed automatically. Workaround: Refresh the browser UI. |
Symptom:
Traffic information reported under the Wireless
Clients tab and Applications tab do
not match. Workaround: None. |
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. |
Symptom: Select All DPSK
passphrases check box selects all passphrases for the current page
only. Workaround: Change the pagination count to 100/page and then select the passphrase per page. |
Symptom: The Firmware
Version Management page lists even the deleted
venue. Workaround: None. |
Symptom: Download admin logs
venue name is not shown properly in description field. Workaround: Venue name is shown as a separate field in the .CSV file adjacent to the description column. |
Symptom: Server error message is
displayed when browser session times out though the active session is
not idle. The JWT default session time is 60 minutes. Workaround: Re-log in after the session expires. |
Symptom: Activities, Events and Admin logs are limited to 100 pages only, irrespective of time period selected. Workaround: None. |
Symptom: Sometimes alarm counts are not aligned with change to
calendar time on the
Dashboard. Workaround: None. |
Symptom: The search results for events do not match the search keyword entered. Sometimes, produces unwanted search results. Workaround: Concentrate only on the search results where the results are highlighted. |
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. |
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. |