Migrating RUCKUS IoT Controller 1.8.2.0 MR to 2.0.x

You can only migrate from RUCKUS IoT Controller 1.8.2.0 MR to 2.0.x and not directly from a prior version.
Caution: The AP-based licensing scheme is no longer supported beginning with RUCKUS IoT Controller 2.0.x.

Prerequisites

Before migrating to RUCKUS IoT Controller 2.0.x, back up RUCKUS IoT Controller 1.8.2.0 MR and obtain a new license for RUCKUS IoT Controller 2.0.x.

Backing Up RUCKUS IoT Controller 1.8.2.0 MR

To back up RUCKUS IoT Controller 1.8.2.0 MR, complete the following steps.

  1. Log in to RUCKUS IoT Controller 1.8.2.0 MR.
  2. Navigate to Admin > Backup.
  3. Click Create Backup.
  4. Click Dowload.

    Creating a Backup

Obtaining a New License

To obtain a new license for RUCKUS IoT Controller 2.0.x, complete the following steps.

  1. Deploy RUCKUS IoT Controller 2.0.x
  2. Obtain the controller serial number.
  3. Contact RUCKUS support for a new device license, refer to https://support.ruckuswireless.com/articles/000012195.

Migrating to RUCKUS IoT Controller 2.0.x

Complete the following steps to migrate from RUCKUS IoT Controller 1.8.2.0 MR to 2.0.x

Note: Do NOT upload the new license before doing the 1.8.2. DB restore. Doing so will lead to devices being onboarded in decommissioned state.

  1. Deploy RUCKUS IoT Controller 2.0.x
  2. Prestart RUCKUS IoT Controller 2.0.x. Configure the Hostname and TimeZone as configured in the 1.8.2 controller.
  3. Log in to RUCKUS IoT Controller 2.0.x.
  4. Navigate to Admin > Backup.
  5. Click Upload Backup > Confirm.
  6. Select No and click Update to retain the current configuration.

    Uploading a Backup

    The controller uploads the file to its database. After the upload process is complete, the RUCKUS IoT Controller logs out of the web interface automatically. When the controller login page displays again, you have completed upgrading the controller.

    Note: Ensure that the database upload process is completed correctly before you proceed.
  7. Shut down RUCKUS IoT Controller 1.8.2.0 MR.
  8. Log in to RUCKUS IoT Controller 2.0.x.
  9. Navigate to Admin > VM Configurations.
  10. Either update the RUCKUS IoT Controller 1.8.2.0 MR configuration network settings to configure RUCKUS IoT Controller 2.0.x similar to the existing configuration, or update the new configuration network settings to configure RUCKUS IoT Controller 2.0.x to a new network.
    Note: RUCKUS highly recommends that you stop using the older instance to configure the network after the migration to RUCKUS IoT Controller 2.0.x is complete, and you shut down or delete RUCKUS IoT Controller 1.8.2.0 MR.
    Note: If the RUCKUS IoT Controller IP address is changed, update the IP address in the APs using Option 43 or the vSZ AP CLI.
    Note: Because the RUCKUS IoT Controller 2.0.x license is not part of the database backup, you must contact RUCKUS Support to obtain the license.
  11. Go to the RUCKUS IoT Controller UI, click Admin > Licenses and upload the new license.
Parent topic: RUCKUS IoT Controller 1.8.2.0 MR to 2.0.x Migration