darwin_barredo's profile

9 Messages

 • 

194 Points

Wed, Apr 22, 2020 9:56 AM

Answered

MIGRATE AP FROM SMARTZONE TO DIFFERENT SMARTZONE

Hi Guys is there any ways to migrate the multiple ap from smartzone to diffrent smartzone? i know we can use remote ap-cli  but it is for single ap only. 

NOTE : the version of the controller is 5.1.2 so we cannot use AP CLI SCRIPTS ALSO

Official Rep

 • 

130 Messages

 • 

2.6K Points

2 y ago

We have an option called 'SwitchOver cluster' on the SZ to switch the APs from one SZ to another.

Please refer to the SZ administrator guide for more details about this.

-Anusha

Official Rep

 • 

130 Messages

 • 

2.6K Points

You can also SSH into the AP and execute the below command with the new SZ's IP address

set scg ip

-Anusha

9 Messages

 • 

194 Points

yes i also mention that i know we can do remote api-cli "set scg ip" but it is a lot of work since we need to do it 1 by 1.

is switch over cluster same function as set scg ip ?

Official Rep

 • 

130 Messages

 • 

2.6K Points

Yes, please refer to the administrator guide of SZ.
If it is only for one AP, you can execute the command, 'set scg ip '

-Anusha

Official Rep

 • 

274 Messages

 • 

4.6K Points

2 y ago

Hi Darwin,

You can try loading the AP CLI script to apply the new controller IP to all the APs.

Below is the sample AP CLI Script:

fw_version=firmware of the AP
model=all
set scg ip x.x.x.x (new controller ip)

Below is the KB article for more info.
https://support.ruckuswireless.com/articles/000004057

Make sure to change the AP firmware version (existing AP firmware) on the script.

1. Open a notepad.
2. Copy the above content and save it.
3. On the existing SZ\vSZ, load the text file and apply.
4. Now all the APs will have the new controller IP and will try to connect to it.

9 Messages

 • 

194 Points

Hi Sanjay is says that set scg ip script are not allowed in the version 5.1.1 



4 Messages

 • 

100 Points

2 y ago

Maybe changing the controller IPaddress works.
But I‘m not sure,that’s just a guess .

191 Messages

 • 

3.2K Points

2 y ago

If you’re moving multiple APs you can use DHCP option 43 and reboot the APs.

4 Messages

 • 

100 Points

2 y ago

I think we can set some APs in one domain to another through the public Internet . But I don't know what benefit could be get by this method,maybe just for fun or just a try of experiment.

Official Rep

 • 

1.4K Messages

 • 

18.6K Points

2 y ago

Hi Darwin,

As suggested by Anusha, "Switchover cluster" is the best option if you have both the SZ clusters (source SmartZone and destination SmartZone) online and desired AP(s) is(are) online/connected state on source SmartZone.

As you can see below, you can choose multiple APs or specific selected APs to move from existing cluster to a new cluster. This also gives you option to delete or keep its entry on existing cluster.



About the CLI option, you may need to run "set scg reset" after running "set scg ip xxx.xxx.xxx.xxx" as some times AP do not drops it's connection with currently connected SZ.

Regards,
Syamantak Omer

3 Messages

 • 

84 Points

Is it possible to set mutiple IP ́s when using switchover as in the set scg ip-commande? I,e set scg ip [IP1], [IP2], [IP3]... etc? 

193 Messages

 • 

3K Points

2 y ago

We've just done this a few weeks ago. We set the DHCP option 43 first, then chose the "switch over cluster" feature. Worked like a charm, almost too good. 

147 Messages

 • 

2.9K Points

2 y ago

Hi Darwin,

There is a script that was shared by Jeronimo, this would serve your purpose; if you are good at bashscripting you could enhance it to your needs. 

https://forums.ruckuswireless.com/ruckuswireless/topics/sharing-scripts-for-ruckus-ap

There is little bit work that needs to be done but its lot better than sshing into each AP and doing it, its lot fun and you now knew another way of switching APs. 

Its bad that they have added "set scg ip" command to this list, in fact even if you use dhcp option 43 to let your APs know new controller they go back and join to the old one if they are not deleted on old one; you will not do it unless you want to screw your day, it doesn't work all the time. I have been there too, but this script does the job it requires some time but you are sure that this will get the job done.

Hope it helps!!!

Regards,
Abilash PR.




193 Messages

 • 

3K Points

It doesn't matter if they added "set scp ip" to the list, you CAN still do it. You will get a warning in which you can bypass to achieve this. I learned this because I wanted to mass reboot and thought because it was added to the list, I couldn't do it. UNTIL I actually tried it and it still worked. 

13 Messages

 • 

290 Points

2 y ago

Which would be the best option for migrating over 100+ APs (MSP with different customers and different sites across country) from Essentials to High Scale? I can replicate the settings in the new High Scale SZ prior to migration.

Thanks!
Tim

9 Messages

 • 

194 Points

2 y ago

Hello guys thank you for your suggestions, i was able to move the AP's to different Zone director using "switch over cluster" feature thank you  Anusha ! 

Official Rep

 • 

130 Messages

 • 

2.6K Points

2 y ago

Great to hear that, Darwin.

Have a nice day!

-Anusha

7 Messages

 • 

130 Points

1 y ago

Is there a switchover cluster function in 3.62? I am trying to move legacy Aps to a 5.2 cluster from a 3.6 cluster. For some legacy reasons I cannot upgrade the 3.62 yet. 

The 5.2 cluster was upgraded from another 3.6 cluster. hence a zone based on 3.6 can be created.

3 Messages

 • 

84 Points

1 y ago

We use a combination of 2 BASH-scripts in linux combined with an IP-list that executes the following commands;
IE. 1st script contains login-information to the APs and calls the IP-list (txt-file one IP per row, which then calls the second script that executes the commands. 


set scg fullreset

set scg ip [IP-adress1,IP-adress2,.....]
exit

This works flawlessly in 95% of the cases on first attempt, AP´s not migrating to the new controller, we simply run it again with a new IP-list. 

Worst case if something has not come over successfullyt we do it manually. Migrated 900+ AP´s with this script in batches of 20 aps´s per batch. Did not take to much time. 

We use the same method to for instance set tunnelmgr IP´s and so on depending on what dataplane we want to put workload on. 

Important Announcement