Smartzone Migration

[alex_shalima]

Hi Guys/Gals,

Hope you are all doing well during these times.

I'm looking to migrate a High Scale vSZ from one datacenter to another.

Current vSZ is setup on public IP (behind a NAT). It manages WAPs and switches. Version 5.1.1.0.598.

We are looking to do the same thing in the second datacenter with a new public IP.

I have been able to set up the vSZ. At this point I'm looking for an advice or best practice on how to make this transition smooth. Here is my option that I can think of:

1.

- Load a backup of the current vSZ to the new one.

- Move all of the equipment (change the SCG IP address) using AP scripts and switch batch cli facility.

2.

- Change the SCG IP to a FQDN for WAPs and switches (not sure if it is possible).

- Load a backup of the current vSZ to the new one

- Change the IP in the DNS

3. 

- Setup a new vSZ and add it to the cluster

- Let all the equipment get the new SCG IP 

- Shutdown the current vSZ

- Remove the old (current) smartzone from the cluster

Please let me know which one of the above would be the preferred method. Also, if you know of a better way to do it - please let me know.

Happy thanksgiving!

Cheers,

Alex

[syamantakomer]

Hi All,

I don't want to contradict with pervious suggestions as all are correct. However, I think 3rd option is the best one.

"

3. 

- Setup a new vSZ and add it to the cluster

- Let all the equipment get the new SCG IP 

- Shutdown the current vSZ

- Remove the old (current) smartzone from the cluster

"

Below are the advantages with 3rd plan:

• Zero downtime required.
• No need to migrate the APs manually or point them to new vSZ IP.
• No manual configuration required on new vSZ in DC2.
• Full database of the existing vSZ will sync with new node, not just the configuration.

[syamantakomer]

In addition, I suggest shutting down the vSZ on DC1 (or just shut the virtual port from VM side, so that it can easily be switch On, in case of any failure with new cluster node), make sure everything is working on new node in DC2, then only remove the old node from the cluster or decommission it from VM.

[alex_shalima]

Thanks Syamantak_omer,

It was mentioned in the above comment that clustering between two different datacenters is not recommended. Do you see an issue in that?

Cheers,

Alex

[syamantakomer]

Hi Alex,

It depends upon the latency between the DCs.

eizens_putnins explained it correctly in his comment but vSZ is supported on different DCs on a single cluster.

[eizens_putnins]

For clarity I want to add, that sz controller list on AP doesn't use FQDN, list  contains node IP addresses (both internal and external for each node). So for AP onnects to SZ using IP address, not FQDN. It avoids disruptions because of DNS issues, but doesn't allow to change cluster target using DNS.

If you have new cluster configured and ready to go, than to move APs from one vSZ cluster to different one is really easy, you just use move menu from vSZ, and move APs to different cluster (there you can use IP or cluster FQDN).  Problem is that you need during this transfer licenses available for each AP on both systems, so if you are just moving installation, it is more practical to move VMs, not to make a new installation.