Before Upgrading to This Release

Due to underlying changes of the database in this release, data will be dropped during the upgrade. It is recommended that you read the following content carefully before upgrading to this release.

Important: Data migration from SmartZone (SZ) 5.0 to 5.1 is supported.
CAUTION: Data migration is not supported if system upgrades from release 3.6.0 or 3.6.1 or 3.6.2 to release 5.0 or to release 5.1 by SmartZone (SZ) release 5.0 and 5.1 upgrade. 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. [SCG-73771]
Attention:

If you are upgrading with a three or four nodes cluster running on version 5.0.0.0.676 with 22500 APs and above refer to caveat [SCG-97442].

  • The upgrade path is changed and is now limited to N-2 support. Only 3.6.0 or 3.6.1 or 3.6.2 or 5.0 releases can be upgraded to 5.1.
  • When upgrading to the release 5.1 image from release 3.6.0 or 3.6.1 or 3.6.2, the system displays the following warning message about not supporting data migration (statistics, events, administrator logs) during the upgrade process.


Data Migration Recommendations

If you need to preserve your data or reports, consider the following recommended options before upgrading:

  • Leverage an existing SCI platform to send statistics and reports to SCI before the upgrade.
    Note: SCI comes with a free 90-day evaluation.
  • Backup and export existing statistics and reports using Export tools or Streaming API before the upgrade.
  • Ruckus will be able to provide the Data Migration Tool to interested customers (only available to Essential controllers), and the Data Migration Tool Guide is downloadable from the support site.
    Note: Use of the Data Migration Tool is not recommended for high-scale users running SZ300 or vSZ-H.

Upgrade Considerations

Before upgrading, consider these additional points.

  • Before uploading a new AP patch, Ruckus strongly recommends that you save a cluster backup, in case you want to restore the previous AP patch.

  • Before upgrading the controller, Ruckus strongly recommends that you back up the entire cluster. In case the upgrade fails, you can use the cluster backup to roll back the cluster to its previous state.

  • 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 be unable to perform the upgrade. On the other hand, if the new VM instance has insufficient hard disk space, a warning message appears after you upload the upgrade image, but you will still be able to perform the upgrade.