Note: Users running SmartZone Releases 6.1.0, 6.1.1, and 6.1.2
(including patches), 7.0.0 (including patches), 7.1.0, and 7.1.1 (including
patches), are eligible to upgrade to Release 7.2.0. Releases earlier than 6.1.0 are
not supported. For more information, refer to the Release Compatibility.
Caution: Beginning with SmartZone 6.1, when
using three interfaces, the
vSZ-H platform does not support network configuration with the Control, Cluster, and
Management interfaces in the same subnet or VLAN. As a workaround, separate the
controller Control, Cluster, and Management interfaces to different subnets or VLANs
before upgrading.
Note: Effective with the 7.2.0
release, the SmartZone 300 physical appliance and associated accessories are
no longer supported. You can provision a virtual machine and deploy the
Virtual SmartZone (vSZ) software.
SmartZone Licensing and Support
Compliance
Software upgrades and support require
active licenses, one for each AP capacity license on your controllers and one for
each controller node. This ensures complete RUCKUS support, troubleshooting, and
access to the latest SmartZone features and security updates. On the RUCKUS Support
Portal, under your account, you can find the most up‑to‑date compliance information.
For more information, refer to SmartZone Licensing and Support
Compliance.
The following SmartZone versions
require full support compliance:
Upgrading from any earlier
version to SmartZone 6.1.2.0.487 (R6.1.2 P3) or later.
Upgrading from any earlier
version to SmartZone 7.1.x or 7.2.x.
Note: The compliance is enforced at the account level across all
SmartZones, not at the individual appliance level.
Caution: Before upgrading to 7.2.0 or
later, log in to the RUCKUS Support Portal and verify AP Support License status
is Compliant. For more information, refer to the RUCKUS SmartZone Software
Licensing Guide.
Caution: Data migration is
not supported if system upgrades from release 3.6.x. Existing system and network
configuration is preserved, but data such as status and statistics, alarms or
events, administrator logs, and mesh uplink history is not migrated to the new
release. Contact RUCKUS Support for concerns or additional clarifications.
Caution: SmartZone users upgrading from
R6.1.2.0 Patch 3 should be aware that applying this patch restricts the upgrade path
to R7.1.1 and above only. Directly upgrading to R7.0.0 Patch 6 or R7.1.0 is strongly
discouraged, as it may result in the loss of certain functionalities. Refer to the
Technical Support
Bulletin for details regarding the upgrade limitation - https://support.ruckuswireless.com/technical_support_bulletins/642.
Caution: When the controller
meets the following conditions before upgrading:
Access & core separation
feature is enabled
UDI interface exists
There are static routes for
UDI interface
Then, after upgrading to release 6.1.0, static routes for the UDI interface
will be placed in an incorrect routing table so these destinations will not be
reachable.
Due to a change in the EAP
supplicant timeout from default 12 seconds to 60 seconds, the client
fails to get an IP address when the RADIUS proxy switches to the
secondary server.
It is recommended to
change the Radius Option values in WLAN before upgrading the controller
or AP to SmartZone Release 6.1.
Following are values
recommended under Radius option in WLAN configuration:
NAS Request
Timeout = 5
NAS Max Number of
Retries = 6
DP Zone Affinity is renamed
to DP Group and DP Group is renamed as Internal DP Group. Please refer to
the Admin Guide for DP Group details on this feature.
It is recommended to upgrade
the controller Virtual SmartZone (vSZ) before updating the data plane
version because if the data plane version is higher than controller vSZ
version then data plane cannot be managed by vSZ platform.
When upgrading vSZ-E/vSZ-H, if the
memory/CPU allocation of the current VM instance does not match the lowest resource
level of the new VM instance to which the new vSZ-E/vSZ-H version will be installed,
you will lose the capacity for APs. On the other hand, if the new VM instance has
insufficient hard disk space, a warning message is displayed after you upload the
upgrade image, but you will still be able to perform the upgrade.