topic Re: Current Migration Process from ZD 3000 to virtual Smartzone Essentials in Access Points - Indoor and Outdoor

Current Migration Process from ZD 3000 to virtual Smartzone Essentials

daniel_googe — Thu, 24 Mar 2016 16:40:03 GMT

I have decided to move to a virtual SmartZone controller because Ruckus informed me that the new SmartZones would allow autonomous WLANs to continue running on meshed APs if the controller isn't reachable and that the ZD was not capable of that. I have found a tech document titled "ZoneDirector to SCG/vSCG/SZ Access Point Migration Guide" that was published in November of 2014. This process is very involved and relatively a lot of work. Is there a newer procedure that I am missing? My searches haven't turned up anything if there is. How has your migration gone?

Re: Current Migration Process from ZD 3000 to virtual Smartzone Essentials

sid_sok — Thu, 24 Mar 2016 19:51:31 GMT

The migration process and doc you are referring to is old, it should still work but there are ways to get it done with out doing it that way.
With the new SZ code it might be easier, depending on your AP to controller topology. If all your APs are connected to a network where you have control over the DHCP server or local DNS server you can use DHCP option 43 to redirect the ZD AP to the vSCG and once in SCG mode, you will need a secondary Option43 (see KB article on how to set that up) to redirect the APs (which should have been converted and defaulted) again to the same vSCG IP.

When you bring up the new vSCG, make sure you enable LWAPP2SCG conversion and to have the process default the AP. This is one of the question that is asked during the cluster setup. I also recommend using a 1 interface vSCG-H for configuration simplicity, but any other flavor should work.

If possible I would do this:

Current setup:
ZD IP: 192.168.1.100

New setup:
vSZ-H (vSCG-H): 192.168.1.101

At AP network:
DHCP Option 43 sub option 3 > 192.168.1.101
DHCP Option 43 sub option 6 > 192.168.1.101

1. Sping up the vSZ-H, enable LWAPP2SCG conversion with the default AP as an option
2. At the AP locaiton setup the DHCP option 43
3. On the current ZD, set the Access Point Policy to limit the discover to the primary ZD and backup ZD.
4. put the Current ZD IP as the primary ZD, put the new vSZ-H IP as the secondary "ZD"
5. After 5-10 min, disconnect/shutdown the Primary ZD, let the AP connect to the Secondary "ZD", which should trigger the LWAPP AP to SCG AP conversion, which should default the AP.
6. The newly defaulted AP will look the vSZ-H base on the Option 43 sub option 6 and now should be able to join the vSZ-H.

The above steps will allow you to migtrate your ZD network to SCG (vSZ-(H or E)/SZ100/SCG200), You will then need to confgigure the vSZ's Zone/wlan/AP and move the AP from the staging zone to the final zone. In the case of vSZ-E/SZ100, the AP will br put in the default AP group using the default wlan group.

I hope this hleps.

Sid

Re: Current Migration Process from ZD 3000 to virtual Smartzone Essentials

brian_powers_51 — Wed, 04 May 2016 13:47:08 GMT

Sid,

Would this same process work if moving from one vSZ-H to another? Also is there a command that we can put directly into an AP that will point it to another vSZ-H?

Re: Current Migration Process from ZD 3000 to virtual Smartzone Essentials

eizens_putnins — Fri, 02 Dec 2016 09:02:34 GMT

command on AP with new vSZ address will do what you want:
set scg ip xxx.xxx.xxx.xxx

Re: Current Migration Process from ZD 3000 to virtual Smartzone Essentials

martin_martin — Fri, 02 Dec 2016 14:46:52 GMT

Correct use the set scg ip x.x.x.x and to make it easy for all AP use the AP CLI script under administration / diagnostics
Create a txt file with the command in it and upload it and execute.

regards
Martin

Re: Current Migration Process from ZD 3000 to virtual Smartzone Essentials

hector_vargas_h — Tue, 14 Feb 2017 21:48:28 GMT

Thank you Sid for all your steps, right now I'm doing the same and the only issue that I'm seeing is that after migrating a group of APs to the vSZ-Essentials none of the AP are getting the new configuration from the vSZ. I found out the below link explaning the problem and how to resolve it but it's tough to connect AP by AP to do a factory reset and reboot when one have more than 400 APs. Why ZD managed AP's fail to get configuration updated after joining vSZ? From So.. in this case I think before continue migrating the other group of APs to see if there is a way using the ZD cli to factory reset first a certain group of APs and then they will get the new IP of the vSZ after reboot and that way they might get the new config right away. Do you have any ideas how to accomplish that? or maybe doing the same after I migrate all the APs to the vSZ, how to do a factory reset on a group or all of them at the same time through the CLI ? Thanks.