Question

Customer Environment

Symptoms

A vSZ migration may be needed when:

Changing or upgrading hypervisor platforms
Refreshing underlying hardware
Consolidating virtualization environments
Correcting stability or performance concerns
Retiring older or unsupported hypervisors

Root Cause

Troubleshooting Steps

NA

Workaround

NA

Resolution

Step 1 — Collect Cluster and Configuration Backups
Export the following from the existing vSZ:

Cluster Backup
Configuration Backup

Important Note About Backups

Configuration Backup contains only configuration.
Cluster Backup can also be used but contains:

Old controller IP address
Full cluster metadata
Certificates
Node information

If restoring a Cluster Backup, the OLD vSZ must be completely shut down before restoration
to prevent an immediate IP conflict, since the restored system will assume the same IP.

RUCKUS best practice: Use Configuration Backup for hypervisor migration unless cluster?level metadata is required.

Step 2 — Deploy a New vSZ on the Target Hypervisor
Deploy a new vSZ instance with:

Correct RUCKUS?recommended CPU, RAM, and storage
A new unique IP address

**Using the old IP while the old vSZ is still online will cause a network?wide IP conflict.**

Step 3 — Temporary Licenses (vSZ RTU and AP/Switch Capacity)
To migrate devices to the new vSZ, temporary licenses may be required.
Provide the following information to the RUCKUS Licensing Team and System Engineering Team:

Serial Number of the old vSZ
Serial Number of the new vSZ
Old and new hypervisor details
Number of Access Points and ICX switches being migrated
Current AP and Switch license usage

Verify:

vSZ RTU entitlement
AP capacity licenses
Switch capacity licenses

Temporary licenses will be issued to support migration.

Step 4 — Activate the temporary licenses 

Apply licenses to the new vSZ
Confirm capacity under Administration ? Licenses

Step 5 — Restore the Configuration Backup
On the new vSZ:

Navigate to Administration ? System ? Backup & Restore
Restore the Configuration Backup
Allow the system to reboot

Only restore Cluster Backup if the old vSZ is fully powered off due to IP reuse.

Step 6 — Migrate Access Points and Switches

After restoring configuration, APs and switches must be redirected to the new controller.

In case of cluster backup the AP and Switch will communicate with the old IP. 

Customers may choose based on environment design and operational preference.

Option A — DHCP Option 43 (APs and Switches)
Configure DHCP Option 43 to point both:

RUCKUS Access Points
RUCKUS ICX Switches

to the new vSZ IP address.
Devices will automatically discover and adopt the new controller using DHCP.

In case of cluster backup the AP and Switch will communicate with the old IP. 

Option B — Switchover Cluster (APs and Switches)
Use the following option:

Administration ? Cluster ? Settings ? Switchover Cluster

This triggers:

AP migration
ICX switch migration

to the new vSZ.

Step 7 — Transfer Permanent Licenses
After all devices have successfully moved to the new vSZ:

Contact the RUCKUS Licensing Team
Request permanent license transfer from the old vSZ to the new vSZ
Verify the updated license allocation under Administration ? Licenses