vSZ - command "set scg ip" not allowed in AP script

[mrwolf]

Hi all,
we need to change IP address of our vSZ-H, which is hosted on our own public cloud infrastructure.

Though we are pretty confident that we did it well in the past, declaring FQDN instead of IP address in "set scg ip" command, we want to make sure that all of our APs are correctly configured before going live with new IP address.

APs are distributed over many customers, thus DHCP 43 is not an option.

We would like to push an AP script command, as suggested in the following KB article: https://support.ruckuswireless.com/articles/000004979

Also, as per this article, "any AP CLI command will be accepted" into the AP script.

However, when we upload the script, we get the following error: "command[set scg ip] is not allowed in AP CLI Script file."

Script is very simple, as following:

#define AP FW version
fw_version=5.1.0.0.595
#define Model class
model=all
# Command
set scg ip FQDN

Any clue on how to upgrade scg ip remotely (with no easy SSH access)?

[mrwolf]

Hi Brian,
unfortunately the remote "set scg ip" option won't work in my scenario.
AP gets the new vsz address, but always shows "SSH tunnel connected to ..." the old address. 

I have tested with a local AP and the only way to force it joining the "new" vsz ip is to provide a scg init command, and after that provide the set scg ip command. 
Unfortunately I see no way to do that remotely, as after "scg init" command the SSH tunnel gets lost, and I can't reach AP anymore through remote ap-cli to provide next command.

Am I missing something?

[brian_powers]

Bummer.  You could try a few different commands to see the end result.  I'll try a few routes as time permits myself as we may run into your pickle at some point down the road ourselves.

set scg reset says that it changes the state to unmanaged.  Might can try that after setting the new IP/FQDN
set scg resetfull says "similar to init but AP doesn't go for reboot" 

Not sure if any would do what you're trying to do, but I use set scg reset more than I've used set scg init in the past when I wanted to restart an APs SSH tunnel process.

[mrwolf]

I probably tried all possible combination to no avail.
I managed to SSH to one AP and what I found out looks somewhat strange:

set scg disable
set scg ip del 
set scg reset

At this point, SSH tunnel went down.

set scg resetfull
set scg ip new.vsz.fqdn
set scg enable

At this point, AP immediately brings up SSH tunnel WITH OLD IP ADDRESS, despite there's no trace left of it on the get scg config output. 😞
It probably goes away after reboot, but I didn't want to give any service outage so I haven't tried that.

So the trick was to block SSH and HTTPS access to old controller IP address before entering previous commands. This way it looks good, joining new controller address.


I will look into this further, since in a few days I have to perform vSZ final migration to the new IP address, and don't want to make more mistakes.

[matt_haywood_9c]

I know this is too late to help you, but we are going through the same thing. Here is what we figured out. Hopefully this will help those of you who are facing the same challenge.

Using the GUI within the existing VSZ:
Use the "switch over clusters" option within the vsz gui which works for all zones running 5.0.0 and higher. This is the easiest, fastest option.
Navigate to a zone or an AP you want to migrate.
Select the AP or multiple AP's, the click on the More drop down box for the AP's and select "Switch Over Clusters".
This will present a dialogue box. Enter the public IP of the new VSZ. Click OK.
Wait for 5 minutes for AP's to appear and push data to the new VSZ.

For zones below 5.0.0.0:
We can run the commands on an AP either via directly connecting to it via SSH OR by SSH'ing to the vsz, then entering enable and using remote ap-cli <ap mac addy> "ap cli command in quotes"

The commands to get an AP connected to a new VSZ (without the AP needing to reboot):
This is once you are SSH'ed to the AP directly:
##run this to confirm the scg ip currently being reported by AP
get scg
##run this to change the scg ip to the new IP
set scg ip <new ip addy>
##run this to force the AP to break the current tunnel and establish a new tunnel using the current scg ip
set scg reset full

Voila. Wait 5 minutes before all the data starts to populate in the new vsz.

Note: to run the above commands using the remote ap-cli here is the commands from CLI of VSZ in enable mode
remote ap-cli XX:XX:XX:XX:XX:XX "get scg"
remote ap-cli XX:XX:XX:XX:XX:XX "set scg ip <XXX.XXX.XXX.XXX>"
remote ap-cli XX:XX:XX:XX:XX:XX "set scg reset full"

Again, voila. Now wait 5 minutes for the data to start populating in the new vsz.

[toomas_kadarpik]

you need to add also 

remote ap-cli "set scg ip IP/FQDN" ; reboot

Toomas 3kgroup