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; } } }

(v)SZ High Availability - how does it work?

GreensTheorem

Hey,

I've been trying to find out how (v)SZ High Availability works exactly, but I haven't really found a lot of insight...

As far as I understand, there is "Cluster redundancy", which is meant for large scale deployment where clusters of (v)SZ are deployed in different datacenters.

But how does intra-cluster high availability work?

It seems like "Clustering" is more like "Sharding", i.e. you have a centralised interface, but state is not really replicated across the cluster members?

Also for rebalancing, the manual states that "Devices associated with an AP that uses the Ruckus-GRE tunnel may temporarily lose network connection for a short period of time (typically, around five minutes) during the AP rebalancing process." - Which isn't really high availability.

Any insight would be great!

Find more posts tagged with

Accepted answers

All comments

sanjay_kumar

Hi @GreensTheorem

I believe you are talking about the Cluster Redundancy. SmartZone protects against catastrophic failures
by providing intra-cluster, and inter-cluster failover with geo-redundancy and active/active clusters that yields higher availability than hot standby.

Check out the below document and let me know if it answers your query about the setup.
https://docs.commscope.com/bundle/sz-522-adminguide-sz300vsz/page/GUID-6F9C3B4E-EF2F-44CA-B07E-C316E6CE7280.html

sanjay_kumar

Or if you are talking about 2 different nodes connected to the same Cluster but on different location, then let me know.

networkrookie

Hi @sanjay_kumar,

I'm in the same boat as @GreensTheorem. Seems like there's multiple levels of redundancy available with Ruckus SZ but all confusing. I'm looking to do an active-active redundancy between two virtual smartzone deployments on DIFFERENT locations. Is there real benefit with inter-cluster redundancy with only 1 node in each cluster? Is there a specific document for intra-cluster instead?

sanjay_kumar

Hi @networkrookie @GreensTheorem

Here are some documents which explains about the Cluster Redundancy and the Active-Standby Active-Active setup details. I hope this helps to clarify the info.

https://docs.commscope.com/bundle/sz-600-adminguide-sz300vsz/page/GUID-0ED18779-1D91-4852-879F-3A1B28069D86.html

https://ruckus-support.s3.amazonaws.com/private/documents/2653/sz-5.1.0-cluster-redundancy-dpg.pdf?AWSAccessKeyId=AKIAJM3QLNNKLOV235TQ&Expires=1697513658&Signature=YTHV8qq53y0XRjPxqVF9szUc94w%3D

https://www.youtube.com/watch?v=DTgDMzSC2Gs

GreensTheorem

Hi @sanjay_kumar

I am not looking for cluster redundancy.

I am interested in single cluster and what happens if one cluster member fails.

sanjay_kumar

Hi @GreensTheorem

In a Single Cluster with 2 nodes (example), both are managing the APs in Active-Active setup manner.
One will be the Leader role and other will be Follower. Both will have same config synced.
If one node fails, APs will fall back to the other node (Since it will have both controller address) as failover.

Is there any specific information which you are looking for in a Single cluster with multiple nodes?
Let me know so that I can provide information accordingly.

GreensTheorem

Thank you.

Will there be any noticeable interruption in services during failover, e.g. for RADIUS authentication or tunneled traffic?

If the failed node is brought, will the APs automatically be redistributed to both nodes or is it required to manually start the redistribution process?