We are trying to migrate a small (13 AP) deployment from a tired old ZD1100 to vSZ. I have read the migration guide on migrating a ZD setup to vSZ, but this seems like overkill for our needs since we want to significantly change the config of the vSZ vs. the ZD anyway and start out fresh... I was hoping that I could do "one AP at a time" by giving it new firmware (thus removing it from the ZD) and pointing it at the new vSZ, but I can't find any information on that procedure...
Maybe because it's impossible? But I wanted to ask just in case. The migration guide is way complicated and makes sense for a large deployment where you want to keep everything the same, but that doesn't describe us.
Hi Jim, Yes, you do pose an interesting question not well explained in our migration guides. Assuming you have ZD and SZ controllers on different VLAN/IP subnets already setup in your plan, you can factory default an AP that has been under either controller control, install the104.x Solo AP image (which can connect to ZD or SZ) with proper DHCP Option 43 settings to point to the new controller in the new network, and they ought to be seen and join the other type of controller ok. By factory defaulting individual APs and updating their current code to Solo AP version, you could do a staged migration.
Hello there Jim. I agree with you. For your purposes, this can be very simple.
When setting up your vSZ, make sure you activate the LWAPP2SCG function, this is the function where it asks you if you want to convert ZD APs to SZ APs automatically when setting up the vSZ.
If already done setting up the vSZ and forgot to do this, go to CLI and check or activate it there.
To do this, login to the CLI using your admin user, go into enable and run this command.
show running-config lwapp2scg
This should give you something that looks like this: vSZ-D-Test1# show running-config lwapp2scg LWAPP2SCG Configuration -------------------------------------------------- ACL Policy : Accept all Dynamic Data Transmission Port Range : Not specified NAT IP Translation in FTP Passive Mode : No ACL APs :
Now, your output may be a bit different, it may say yes on the FTP Passive mode, in which case, you need to make sure that firewall between AP and vSZ is allowing port range 16384-65000; Or, you can narrow that range under this configuration as well.
Either way, make sure that ACL Policy says Accept all. This will indicate that the script is activated. If it doesn't, go into config mode, lwapp2scg and change the policy there.
After that is done, the rest is very simple.
Configure the vSZ with whatever configuration you want, then on the AP, all you have to do is tell it who his new director is. Make sure that the IP you use is the control plane IP if you set up your vSZ for a three IP config instead of a single IP. Otherwise, whatever IP you have is it.
Once you tell the AP who his new director is, reboot it. The AP will come backup and join the vSZ who will see it as a ZD AP and upgrade the image for it automatically and reboot it again. When it comes back online, it will be on the right code and will join the vSZ-E successfully. If you set up the vSZ as a High Scale, instead of the Essentials mode, then you will need to move the AP to the zone you configured.
So, to summarize:
1 - Activate lwapp2scg if not already active (ensure firewalls are setup properly) 2 - Tell the AP to join the new director 3 - Watch the AP migrate itself and get new configuration and go online as configured 4 - You are a happy man 🙂
Just a side note, it may be a good idea to factory default the AP before you point it to the new controller. This will make sure that the new config comes in nice and clean onto the AP when it migrates. Just a thought.
Let us know if you still have questions and good luck and enjoy your new vSZ system..
Awesome, thanks guys! I think I understand... but Dionis, when you say "tell the AP to join the new director" how is that accomplished, exactly? Something in the APs local web UI/CLI, or via the existing ZD, or ?