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 6.1.1 and older access points (r500 & t301)

gsfakian

Hi to all.

I am reading in release notes that its possible to adopt older models like R500 & T300/301 by putting them in a different zone which uses older AP version.. But how can i create such a zone? Whenever i try to create a new one the firmware version is not an option... it just shows the latest one. These old APs still run on a ZD3050 10.1.1.0.42. Newer model R710 was succesfully migrated into the new version of sVZ.

Thanks!

Find more posts tagged with

Accepted answers

Sunil_Acharya

Hi @gsfakian,

Greetings,

After applying patch, Have you created the zone with 5.2.2. on the VSZ.

R500 and T301s is supported on version 5.2.2.x.x.

If you are able to view the AP are connected to the VSZ by using "get scg" but still the AP are not able to view on the SmartZone.

You could use provision tag method to fall the AP to right zone.

Please go through below link for the configuration

https://support.ruckuswireless.com/articles/000002667

Please let us know if you have any additional queries, We are happy to assist you.

Regards,

Sunil Acharya

Vineet_nejwala

Hi @gsfakian

The APs when joining would go to the default zone before they are moved into any other zone. The default zone might be on 6.x code which will not support your r500 model APs hence I woudl suggest to create an AP registration rule to move all R500 APs to a specific zone (5.2.2) when provisioning.

AP Registration rules can be created under System > AP Settings > AP Registration. Select the model and choose the group (5.x group) where the AP should be moved to.

Best Regards

Vineet

All comments

vasanth_edward

Hi @gsfakian,

Thank you for writing to us.

SZ with 6.1.1.0.959 does support 3.6.2.0.795 AP patch, so that older APs can be added in separate zone. For more information on supported & unsupported APs, go through https://support.ruckuswireless.com/documents/3025-smartzone-3-6-2-0-250-mr2-patch2-release-notes once.

In order to install 3.6.2.0.795 AP patch, please go to Administration --> Upgrade --> AP Patch, file can be downloaded from link https://support.ruckuswireless.com/software/3569-smartzone-ap-patch-for-post-3-6-2-patch-2-scg200-sz300-sz-100-vsz.

Hope this is informative.

Regards,

Vasanth Edward

gsfakian

Thank you very much. I found documentation about changing a zone firmare but nowhere was mentioned 'how' to make this firmware appear in the menus.. So i uploaded the 5.2.2 patch and my AP (R500) is running also 5.2.2 having a valid certificate. But no way for the controller to "see" it!.. Tried reboot, defaults, set scg ip but nothing... Also when i try ZD migration from the old controller having the patch installed on sVZ migration fails for models R500 & T301s

Sunil_Acharya

Hi @gsfakian,

Greetings,

After applying patch, Have you created the zone with 5.2.2. on the VSZ.

R500 and T301s is supported on version 5.2.2.x.x.

If you are able to view the AP are connected to the VSZ by using "get scg" but still the AP are not able to view on the SmartZone.

You could use provision tag method to fall the AP to right zone.

Please go through below link for the configuration

https://support.ruckuswireless.com/articles/000002667

Please let us know if you have any additional queries, We are happy to assist you.

Regards,

Sunil Acharya

Vineet_nejwala

Hi @gsfakian

AP Registration rules can be created under System > AP Settings > AP Registration. Select the model and choose the group (5.x group) where the AP should be moved to.

Best Regards

Vineet

gsfakian

Thank you very much!.. This solved the problem!..

I am still wondering if also the ZD migration procedure could succeed in a similar way... Every old AP that starts migration fails... and as i can see i believe this happens because vSZ tries to flash them the newest FW and not 5.2.2.0.2064 .. here is fw show from an AP:

rkscli: fw show
current primary boot image is Image1
--------------------------------------------------------------
Auto F/W upgrade = disabled
Running on image = OTHER
FW Control Control File = wsg/firmware/R500_6.1.1.0.1274.rcks
Control File Server = 10.50.49.3
Protocol = HTTPS
Port = 443
Boot Flags (Main,Backup,Factory,Reset) = M. .. [MB FR]
--------------------------------------------------------------
OK

So as they are a dozen of them i wonder if i have to flash & provision them one by one to be able to join sVZ... 🙂

Thanks!