Showing results for 
Search instead for 
Did you mean: 

vSZ - AWS | Join a new node to the cluster fails with the error 'cluster doesn't exist'

RUCKUS Team Member


When adding a new Virtual SmartZone (vSZ) node to an existing cluster in an Amazon Web Services (AWS) environment, it's important to consider the cloud region of the new node. This article provides guidance on how to handle situations where the new node is in a different region from the existing cluster.


  1. Identify the Cloud Region: Determine whether the new vSZ node is in the same cloud region as the existing cluster. You can do this by checking the region information in the AWS Management Console.

  2. Establish VPC Peering: If the new node is in a different region, you must establish a Virtual Private Cloud (VPC) peering connection between the regions. This is necessary because the nodes in the cluster communicate with each other using their private IP addresses.

Note: VPC Peering allows for direct network routing between two VPCs, enabling instances in either VPC as if they were within the same network. This is crucial for the proper functioning of the vSZ cluster nodes across different regions.

This is the configuration you should use when setting up the 'Join an existing cluster' procedure:



By following these steps, you can successfully set up a new vSZ node in a different region from an existing cluster. Remember, the establishment of a VPC peering connection is a critical step when the new node and the existing cluster are in different regions.

With regards,
Orlando Elias
Technical Support