SZ Cluster node rename

[Greg_WiGuy]

I'm planning some overdue architectural updates to our SZ124 deployment

1-Migrating our current only SZ124 from 1G to 10G

• Requires new Managment IP
• Would like to update the hostname (sz01.locationA.mycompany.com)

2-Deployment of a new SZ124 with 10G uplink for failover

• Will be added to the same cluster as current SZ
• Will be hosted at a second location for geo-redundancy (sz01.locationB.mycompany.com)

My concern is, without having much experience with clustering, the hostnames and a possibility of conflict.  As far as I can tell it looks like only the hostname(first word before .) is considered as part of the node name and not the full domain.

If I went with our current deployement standards, I'd end up with two sz01 hostnames.  Should I be concerned about this?  Or should I try deploying unique hostnames like sz01a.locationA and sz01b.locationB...

also wondering if there's a way to rename a cluster?  It was deployed before my time using cisco "wlc" as the convention that kinda irks me 😉

[Greg_WiGuy]

Thanks Albert, your feedback has been instrumental!

[Greg_WiGuy]

Hi Albert,
I was wondering if there's any way to pin WLAN/SSID traffic to one SZ GRE based Data Plane vs another?  My design isn't really impacted by spreading the control plane among different SZs in the same cluster but if theres away to control which SZ the tunneled WLANs terminate on, this would be good enough for us.  Even if it requires manual intervention to flip GRE traffic over to the second SZ in a failure scenario.

[albert_pierson]

Hi Greg,
There is another feature that unfortunately is not available on SZ100, vSZ-E - Node Affinity
This feature configures AP's to prefer one node (data and/or control) per AP Zone.

This feature was never available per WLAN/SSID.  But tunneling (on all SZ platforms) can be enabled per WLAN/SSID.

For fail safe operation all AP's will be configured with a list of all Data Plane IP's available.  As far as I know with SZ100 or vSZ-H there is not way to configure it to prefer one over the other.  If you are using the 2 interface/IP model where the Data Plane is on it's own interface you could use external firewall rules to block which AP's can reach which Data Planes. 

I hope this information is helpful

Thanks
Albert

[Greg_WiGuy]

Thanks for the info Albert!

[Greg_WiGuy]

Albert,
We need to move our only SZ to a new managment IP.  So far I've created an AP Script with the following commmand
"set scg ip ruckuscontroller.mycompany.com"

My question is that when we change the management IP address - will all APs fail back to looking for this DNS entry and redirect to the new management IP, or will they still try to go to the old IP?

I read something that mentioned we might have to re-initialize something on the AP side but I'm not sure if that was only if you were moving from one active SZ to another.