nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

vSZ cannot migrate ZD3k after updating to v10.2.1.0.75

nickzourdos

I am running vSZ version 5.1.0.0.496 and trying to use the ZD Migration Tool to migrate from a ZD3k. When the ZD was on 10.1.2.0.120 I was getting a strange tftp error after selecting AP's to migrate, and the process would fail. After a lot of troubleshooting I decided to move one of our ZDs to the latest version hoping that might clear it up. Ever since moving the ZD to 10.2.1.0.75 the vSZ fails the migration instantly with a network error:

Can't connect to ZoneDirector. Please check IP, User name, Password and make sure ZoneDirector is reachable.

I have other ZDs that are still on 10.1.2.0.120 and the vSZ has no problem connecting to them during the migration process. It only seems to be affecting ZDs on 10.2.1.0.75. The ZD can ping the vSZ's control interface, and vice versa. We are trying to proof-of-concept this process for our upcoming vSZ deployment but so far we have not been able to perform a single successful migration.

Is this a known issue? It's worth mentioning that the vSZ is a 90-day evaluation. Is the migration process supported on an eval?

Find more posts tagged with

Accepted answers

All comments

Ankush_Chandan

Hi Nick,

I hope the TFTP is allowed between the SZ and the ZD as moment you hit connect, it will download ZD backup file. Further the password you use for the ZD should match the SZ's password security rule. If not, you could not start the migration process. Could you please check if ZD password have an Upper Case Letter, a Number and a special character in it.

Regards,
-Ankush

nickzourdos

Thanks for the quick reply. The vSZ's control interface is on the same subnet as the ZD, and there are no L2/L3 access restrictions configured. Is the vSZ using the control interface for this migration process?

The password on the ZD and vSZ meet those requirements.

Ankush_Chandan

Hi Nick,

If it is a 3 NIC configuration, it depends upon which interface is configured as the default gateway. The same interface should have connectivity to the ZD.

-Ankush

nickzourdos

Right now the vSZ has the management interface set as the gateway. Is it possible to change which interface is configured as the default gateway?

This still would not explain why the vSZ can begin the migration process with ZD's that are on an earlier version of code, but not the latest version

unknown

Hello. Was this resolved? I'm having the exact same issue, I can't start the migration proccess after upgrade, I get the same error that says the SZ can't connect to ZD.

nickzourdos

Yes, this was an issue with versioning. My ZD was on a version of code that was "too new" for vSZ and the migration wasn't supported yet. I had to wait for a new version of SmartZone code to be released.

unknown

Still not working for me. SZ100 is on 5.2.0.0.699 and ZD on 10.2.1.0 build 147 (lastest firmware I found) and I'm still getting the same error.
It was working when the ZD was on 9.13.3.0.164, but now I can't downgrade it without a factory reset.

nickzourdos

ZD 10.2 migration support was added in SmartZone 5.1.1

1. Do you have mesh enabled on either controller?

2. Does your SmartZone have multiple interfaces (cluster/management/control)? If so, which one are you using for the migration?

3. Do you have the Access and Core Separation setting enabled on your SmartZone?