cancel
Showing results for 
Search instead for 
Did you mean: 

vSZ to vSZ APs migration

dawidku
New Contributor III

Hello 

We have 2 vSZ-H controllers deployed (not clustered), secondary was only built temporarily to accomodate new client. We now want to migrate 200 access points from temporary vSZ02 controller onto our production vSZ01.

What would be the easiest way to achieve this with minimal downtime and minimal manual (AP CLI) job?

1 ACCEPTED SOLUTION

James
RUCKUS Team Member

Understood. Please try the following.

  • Login to temporary controller > Network > Access points > Choose an AP zone > Select one AP from the list, which you are planning to move to your main controller.
  • Clock "more" > "switch over cluster" > enter Control IP of your main controller. If main controller is behind a NAT service, enter the respective control NAT IP
  • Prior to moving an AP, try to ping the main controller's control interface IP from the AP.
  • It would be good, if the AP you selected is one you have physical access to, just in case it does not join the new controller, SSH access to the AP is needed to recover it.
  • Make sure the main cluster has sufficient AP capacity licenses to support the additional APs.

 

James_1-1683804817800.png

 

View solution in original post

5 REPLIES 5

James
RUCKUS Team Member

Hello,

We have am option called switch Cluster on vSZ. This could be used to move APs from one Cluster to another.

What is the current firmware version on the primary and backup controllers ?

dawidku
New Contributor III

James

Controllers are not clustered and running different versions of firmware (6.0 & 6.1)z

James
RUCKUS Team Member

Understood. Please try the following.

  • Login to temporary controller > Network > Access points > Choose an AP zone > Select one AP from the list, which you are planning to move to your main controller.
  • Clock "more" > "switch over cluster" > enter Control IP of your main controller. If main controller is behind a NAT service, enter the respective control NAT IP
  • Prior to moving an AP, try to ping the main controller's control interface IP from the AP.
  • It would be good, if the AP you selected is one you have physical access to, just in case it does not join the new controller, SSH access to the AP is needed to recover it.
  • Make sure the main cluster has sufficient AP capacity licenses to support the additional APs.

 

James_1-1683804817800.png

 

dawidku
New Contributor III

Hi James

This worked perfectly, what a brilliant feature!

Thank you so much for you assistance.