My answer Stephen, is that you need to start with vSZ on 3.2.x and go thru an SZ 3.4.x zone upgrade, before trying to upgrade further to 3.6.2. Upgrade planners should look at the Release Notes for the version you want to get to (to be sure your AP models are still supported, that your VM has sufficient resources, and that you are on a version that can upgrade to this release).
Did you start with vSZ on 3.2.x, and did/do you have an intermediate SZ 3.4 zone, before you tried to move(supported) APs to your SZ 3.6.2 zone? I hope this is helpful.
thanks that is helpful. Our scenario is a bit unique- we had a vsz that broke about 2 years ago, so aps had been running with no controller in that time (we only use ZD/vSZ to manage APs, no traffic tunnels nor any advanced features).
we recently built a brand new vsz which is at at 3.6.2 and are trying to move APs over (from no/dead controller , to this new one). We have not had issues with other APs that are in the same scenario (about 25 moved so far successfully). Now we are trying to move these 68x and having this issue.
the question is did you begin with vSZ on 3.2.x too did do you have a moderate SZ 3.4 zone before you attempted to move(supported) APs to your SZ 3.6.2 zone
the question is did you begin with vSZ on 3.2.x too did do you have a moderate SZ 3.4 zone before you attempted to move(supported) APs to your SZ 3.6.2 zone
