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; } } }

ZD to VSz Migration (Legacy APs)

unknown

Hi,

I am caught in a situation where I needed some ideas,

We have upgraded the VSZ from 3.6 to 5.2,

We are also in the midst of migrating legacy APs (R700) from the ZD and adding new APs (R650) into the VSZ.

Is there anyway when using the ZD migration tool, to specify which firmware the ZD AP can use?

Current issue, is that the ZD Migration keeps forcing the 5.2 firmware on the R700 which will end up failing. We need the ZD Migration to use the 3.6 firmware for the ZD R700.

Find more posts tagged with

Accepted answers

All comments

DarrelRhodes

Hi Johnny,

Have you tried implementing AP registration rules on the SmartZone? Effectively to point any legacy AP at your 3.6.2 Zone.

https://docs.commscope.com/bundle/sz-512-sz300-vszh-administrator-guide/page/GUID-EF10D5CB-0F7F-4C6D-A629-853AB4B75B3D.html

Hope that helps,
Darrel.

unknown

@darrel_rhodes_ji6v9e14q896y

Yes... this has been done, but this is in the situation of joining a "new" legacy ap to the VSZ,

What I am facing now is that I have hundreds of legacy APs managed by zone director, and I need to use the the AP migration tool in the VSZ to migrate over the legacy APs.

DarrelRhodes

Hi Johnny,

The AP registration rules are to help exactly with as you describe - when a 'new' AP (an AP the SZ has never 'seen' before) tries to join - based on certain criteria, the SZ will ensure the AP is pushed to a specific zone (in your case a 3.6.2. FW zone), rather than landing in the 'staging zone' and being rejected due to incompatible firmware.

Unfortunately I have not run through the above configuration in tandem with the ZoneDirector migration tool. Therefore I would recommend you raise a ticket with Ruckus support for further assistance on this specific challenge.

Thanks,
Darrel.

eizens_putnins

I suppose issue is related with fact that script converting ZD AP to vSZ is using latest firmware -- to move APs from ZD APs are reset to factory twice, before and after installing vSZ firmware, and this will obviously not work in this case. Just joining new AP is different process, new APs are not upgraded to vSZ firmware until moved from staging zone to any other.

But you can install temporary vSZ cluster version 3.6.2 (2 nodes = 10 temporary licenses), migrate APs to it, and than move APs to main cluster. You don't need much AP licenses on temporary cluster -- it's enough to use 10 temporary licenses to get APs converted, as they may stay in staging zone.Than you can move them to main vSZ (shutting down temporary cluster and using DHCP or DNS to set vSZ IP).

As there will be no ZD migration involved in moving APs to vSZ v.5.x, APs will be able to be put in compatible zone without problems. I am quit sure this will work, but unfortunately, I can't test this scenario now. If you try this way - please publish your results. It may be useful to know, as more such migrations are expected in nearest future.

Hope it helps

david_black_594

I'm not sure if you created and locked a 3.6.2 zone before upgrading the vSZ to 5.2, but if you didn't do that, I don't think you will ever get the APs migrated. We've been migrating ZD environments for years and we still do it the same way we did several years ago. There may be better tools now, but our way always works and we've never bothered to change it. Our process would be to install a vSZ that has native support for the older AP model (3.6.2 in your case). Migrate the APs from the ZD to the vSZ. Prior to upgrading the vSZ from 3.6.2 to a version that no longer supports the older APs, segregate the unsupported models in a new zone and lock the AP code for that zone. Other APs that are natively supported by the upgrade version can be left in the default (or whatever) zone. Now you can upgrade the vSZ to the new version and everything will work. Maybe it's changed, but as far as I know if you fail to segregate the older models into a new zone and lock the AP code prior to upgrading, the older models will never work and there is no way to recover (other than unwind and start over).

DarrelRhodes

Hi David,

It's 100% possible to adopt legacy APs on to a 3.6.2 Zone on to a controller that has only ever had 5.x installed; by uploading the 3.6.2. AP FW patch.

This is how it's possible to run SZ-144 with legacy APs, as SZ-144 minimum controller firmware is 5.2.1.

Thanks,
Darrel.

david_black_594

Now that is great news! Apparently when the 144 came out, that forced the creation of the patch. I'm glad to learn this. Now we can retire our "old way" of upgrading.

unknown

Hmmm...

I think I might have figured out how to do this.

1. Setup another VSz base on version 3.62,

2. Use the AP migration tool to migrate the legacy APs over

3. On the Vsz 3.62, use the switchover cluster function to move the legacy zone (which contains the legacy APs) to the upgraded VSz 5.2

I will try this at the next opportunity.

eizens_putnins

Hell, Darrel, I looked on download area and don't see mentioned 3.6.2 AP FW patch for SZ144 or vSZ.

Can you point to download link for this patch?

It would be very convenient to be able to implement older AP support without going through v.3.6.2 installation before upgrading to 5.2.1. For now we always use additional 3.6.2 installation for migration and install/upgrade routine for new vSZ installation, when we need to support zones with legacy APs.