New vSZ node can't join Existing Cluster
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2020 04:36 PM
Hello, I am trying to add a new vSZ node to an existing cluster but I keep getting an error
"Cluster name "Existing Cluster Name" does not exist"
I've check the IPs and test hosts on the Cluster vlan can talk to each other.
"Cluster name "Existing Cluster Name" does not exist"
I've check the IPs and test hosts on the Cluster vlan can talk to each other.
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2020 06:08 PM
Hi Mmarengo,
On the existing Cluster, on the GUI under System >> Cluster >> Summary >> you will see the Cluster Name. Is this what you are adding on the new controller which is joining?
You can verify the Cluster name from the CLI as well using the command "show cluster name".
I believe the controller which are trying to join is in Factory default state.
On the existing Cluster, on the GUI under System >> Cluster >> Summary >> you will see the Cluster Name. Is this what you are adding on the new controller which is joining?
You can verify the Cluster name from the CLI as well using the command "show cluster name".
I believe the controller which are trying to join is in Factory default state.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2020 06:26 PM
Hi Sanjay,
I verified the Cluster name several times via GUI and CLI. It looks correct.
How do I know if the controller is in the Factory default state?
I am just following the set up wizard at the GUI after setting up the interfaces via the CLI (initial set up)
Thank you,
I verified the Cluster name several times via GUI and CLI. It looks correct.
How do I know if the controller is in the Factory default state?
I am just following the set up wizard at the GUI after setting up the interfaces via the CLI (initial set up)
Thank you,
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2020 06:31 PM
Hi,
Is the new controller and existing controller on same location\network?
If yes, see if you do the factory reset one more time on the new controller using the command "set-factory". Follow the instruction again.
If you still face the issue, please open a support ticket so that the TAC team can help you on this.
Is the new controller and existing controller on same location\network?
If yes, see if you do the factory reset one more time on the new controller using the command "set-factory". Follow the instruction again.
If you still face the issue, please open a support ticket so that the TAC team can help you on this.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2020 04:25 AM
Hi,
Could you try cluster join operation using CLI. After factory reset, run setup and configure network first. Post that again run setup command and it will ask you to verify IP config. Now it will give you the option to create or join the cluster.
Regards,
Syamantak Omer
Syamantak Omer
Sr.Staff TSE | CWNA | CCNA | RCWA | RASZA | RICXI
RUCKUS Networks, CommScope!
Follow me on LinkedIn
Could you try cluster join operation using CLI. After factory reset, run setup and configure network first. Post that again run setup command and it will ask you to verify IP config. Now it will give you the option to create or join the cluster.
Regards,
Syamantak Omer
Syamantak Omer
Sr.Staff TSE | CWNA | CCNA | RCWA | RASZA | RICXI
RUCKUS Networks, CommScope!
Follow me on LinkedIn

