Performing the Upgrade

RUCKUS strongly recommends backing up the controller cluster before performing the upgrade. If the system crashes for any reason, you can use the latest backup file to restore the controller cluster.
Always back up the controller before attempting a software upgrade. If you are managing a multi-node cluster, back up the entire cluster, and then verify that the backup process completes successfully.

If you have an FTP server, back up the entire cluster and upload the backup files from all the nodes in a cluster to a remote FTP server.

Before starting this procedure, you should have already obtained a valid controller software upgrade file from RUCKUS Support Team or an authorized reseller.
  1. Copy the software upgrade file that you received from RUCKUS to the computer where you are accessing the controller web interface or to any location on the network that is accessible from the web interface.
  2. Go to Administration > Administration > Upgrade.
  3. Select the Upgrade tab.
    In Current System Information, the controller version information is displayed.
    Note: The Upgrade History tab displays information about previous cluster upgrades.
  4. In Upload, select the Run Pre-Upgrade Validations check box to verify if the data migration was successful. This option allows you to verify data migration errors before performing the upgrade.
  5. Click Browse to select the patch file.
  6. Click Upload to upload the controller configuration to the one in the patch file.
    The controller uploads the file to its database, and then performs file verification. After the file is verified, the Patch for Pending Upgrade section is populated with information about the upgrade file. If data migration was unsuccessful, the following error is displayed: Exception occurred during the validation of data migration. Please apply the system configuration backup and contact system administrator.
  7. Click Backup & Upgrade to perform the upgrade. The backup operation is done before the system upgrade flow starts. The backup file will be used to restore cluster automatically while the upgrade process fails. Refer to Creating a Cluster Backup for more information.
When the forced backup-and-upgrade process is complete, the controller logs you off the web interface automatically. When the controller log on page appears again, you have completed upgrading the controller.

In the Current System Information section, check the value for controller version. If the firmware version is newer than the firmware version that controller was using before you started the upgrade process, then the upgrade process was completed successfully.

Note: APs periodically send scheduled configuration requests to the controller, including the firmware version. Therefore, when an AP joins a zone for the first time, the firmware version is verified by the controller. If the firmware version is different from that which is configured for the zone, the controller responds with a request to upgrade it, after which the AP initiates a request to upgrade the firmware using HTTP.