ZD to vSZ Migration

  • 1
  • Question
  • Updated 10 months ago
  • Answered

I have two controllers. One of them is ZD 1200 and another one is vSZ configured as an Essentials with one interface (the location is really small and we don't need to separate traffic)

Controllers have to serve different sub-networks. Let’s say ZD: and SZ Each sub-network has your own DHCP server.

In the beginning all AP were connected to ZD. After vSZ installation I switched some of APs to the new controller (vSZ). My problem is the APs still have old IP addresses from first the network (

How can I migrate APs to the new sub-network?

Photo of Igor Tunakin

Igor Tunakin

  • 42 Posts
  • 15 Reply Likes

Posted 2 years ago

  • 1
Photo of Vivek Gupta

Vivek Gupta, Employee

  • 16 Posts
  • 5 Reply Likes
Hi Igor,

May I know the software version running on the vSZ-E and the Zone director.

Starting from 3.5 vSZ release, we introduced an option of ZD migration under Administration --> ZD Migration. You can configure the Zone director IP address with the username and password and click Connect. It will list all the the AP's under the ZD and you can select AP's that you want to migrate.

Note : ZD versions 9.13, 9.13.1, 9.13.2 and 9.13.3 are supported

Vivek Gupta
Photo of Igor Tunakin

Igor Tunakin

  • 42 Posts
  • 15 Reply Likes
Hi Vivek,

thanks for the answer. I did the migration successfully. It is not a problem. But i didn't understand why APs got IP addresses from the first DHCP.
Ok. I think it because of DHCP-server settings.
Photo of Dionis

Dionis, AlphaDog

  • 80 Posts
  • 48 Reply Likes
Hi Igor, 

The IP of the AP doesn't have much to do with the controllers that manage it.  That is a management network configuration on your switches.  If you want APs to be on the same network, just simply change the VLAN on the switch that is configured for the APs you want so that they go to the network IP that you want them to be in.  From the controller perspective, they don't care what the IP of the AP is as long as they can talk to them.  

Simply change the access VLAN on the switch to correspond to the VLAN you want the AP management space to be in.  Hope this helps.
Photo of Joe Kelly

Joe Kelly

  • 8 Posts
  • 2 Reply Likes
1. Set up a DHCP server with the OPT 43 information and the subnet you want the APs to have -
2. download the CSV file from vSZ, populate AP info in .csv then upload to the Zone you wan the AP to reside.
3.  in the vSZ configure the zone that is replacing the ZD be sure to include the subnet from step one
3. migrate APs from ZD to vSZ, when they reboot they will look for the DHCP sever in step one.  The OPT 43 will point them to the vSZ the vSZ will see their subnet as Zone you configured in step 3 and the APs will find a home in the default AP group.
Making them work is like the ZD
Photo of M


  • 37 Posts
  • 5 Reply Likes
Can you clear to me if the ZD/APs are running 9.12 and below, a factory reset of the AP is needed but not when APs are running 9.13 and above? Since we experience failed migration of APs from ZD 9.12 to vSZ 3.6.2, I read that resetting the APs to factory defaults will allow the AP to migrate to vSZ successfully. But is it still the same for 9.13? I'm having difficulty securing another ZD to test this so if someone had experienced this scenario, I'd appreciate the feedback.
Photo of M


  • 37 Posts
  • 5 Reply Likes
Photo of Michael Brado

Michael Brado, Official Rep

  • 3298 Posts
  • 523 Reply Likes
Just factory defaulting APs that have been running ZD controller code, will not be enough if the SZ isn't running an LWAPP2SCG process/script.

Please see the details for ZD to SZ 3.5+ migration, that's documented in this knowledge base article:

Photo of M


  • 37 Posts
  • 5 Reply Likes
I did enable LWAPP2SCG but the AP failed to complete migration. So I am wondering if factory reset is necessary if ZD/AP is running 9.12 or not necessary if running 9.13 already.
Photo of do394jg37


  • 1 Post
  • 1 Reply Like
same issue here, but with aps at 9.13 zd fw and trying to do them one at a time via ssh.   its really as if ruckus does not want people to upgrade to vsz.  not 1 of our 500+ aps has been a clean move to vsz,  bottom line-  manually upgrade each AP to standalone FW 104 +  then manually add them to the vSZ (3.6 in our case).

its really a sad scenario on ruckus' part.
Photo of Eizens Putnins

Eizens Putnins

  • 125 Posts
  • 53 Reply Likes
Hope my very late reply will help somebody who has same problem now and IS searching for answers.
Actually, Ruckus is not guilty there --  reason is not reading manuals.  vSZ manual clearly states that reset to factory default is mandatory after installing vSZ firmware on  AP to get AP working. Newer vSZ versions (3.5+) can do it for you automatically and very conveniently in AP migration tab.
When this reset is not done, migration fails -- in the best case you get AP, which is managed by vSZ, but does not transmit any WLAN.
This applies to any AP ever connected to ZD, even if it was reset to factory later. Only APs in real factory default status -- which have never been connected to ZD, can be connected to vSZ without reset.
I see it again and again -- and people don't do reset even when I say them to do it, because it looks contr-intuitive. Just do it!
I got through this stage with version 3.1, when there was not enough manuals, but now it is well documented and even automated.