ZoneDirector to SmartZone Migration

SmartZone controllers are better equipped to handle large WiFi deployments such as within campuses and when customers are vastly distributed; therefore, RUCKUS recommends that you migrate existing ZoneDirector deployments to SmartZone controller deployments. The SmartZone controller has an option to automatically migrate ZoneDirector AP configuration information to SmartZone controllers from the controller itself, using a migration tool.
The AP models must be supported by the SmartZone controller.
Note: Each migration batch can support a maximum of 50 APs.

Migration Support Matrix

SmartZone Version ZoneDirector Version
3.5.x 9.13x
3.6.x 9.13.x, 10.0.x, 10.1.x
5.0.x 9.13.x, 10.0.x, 10.1.x
5.1.x 9.13.x, 10.0.x, 10.1.x, 10.2.x
5.2.x 9.13.x, 10.0.x, 10.1.x, 10.2.x, 10.3.x, 10.4.x
6.x 9.13.x, 10.0.x, 10.1.x, 10.2.x, 10.3.x, 10.4.x, 10.5.x

Caution: Do not power off the AP during the migration process.
  1. Go to Administration > Administration > ZD Migration.
    The ZoneDirector Migration page appears.
  2. Configure the following:
    1. ZoneDirector IP Address: Type the IP address of the ZD that you want to migrate.
    2. Admin Credentials: Enter the username and password details to access/login to ZD.
    3. Click Connect. Lists of APs connected to the ZD deployment are displayed.
    4. Click Select AP to choose the AP information that you want to migrate from ZD.
    5. Click Migrate to migrate the AP. The controller imports the ZD configuration and applies it to the selected AP.

    The ZoneDirector Migration Status section displays the status of the migration. When completed successfully, a success message is displayed. If migration fails, a failure message is displayed and you can attempt the migration process again.

    Note: To migrate ZoneDirector Mesh APs to SmartZone, upgrade ZoneDirector to its supported version. For information on the supported versions, refer to the release notes.

    Consider these for ZoneDirector Migration:

    • Zone Director, vSZ and APs all must be in the same subnet.
    • Admin login credentials must be local, not radius.
    • Go to ZD > System Settings > Login Warning and make sure it is disabled.
    • Make sure there are no Management access rules/ACLs configured in ZD that can block the vSZ's IP address.
    • When you run the migration process, it imports the ZD configuration, and creates a basic Zone Configuration automatically in vSZ.
    • Only basic configurations are migrated to vSZ.

Parent topic: ZD Migration