Reset Search
 

 

Article

How to disable and recreate a non-working cluster on WiNG controllers

« Go Back

Information

 
TitleHow to disable and recreate a non-working cluster on WiNG controllers
Objective
To disable and recreate a non-working cluster on WiNG controllers
Environment
  • RFS 4000/6000/7000
  • NX 5500/6500/7500/9500/9600
  • VX9000
  • WiNG 5.x
Procedure
Prerequisites:
  • SSH client such as Putty.exe or similar
  • Flash enabled web browser
  • Successful ping between both controllers 
Procedure:

       A - Removing the existing cluster settings:
  1. Follow these instructions to remove the cluster settings from both (Primary and Standby) controllers: How to reset cluster configuration settings on a WiNG controller from CLI
Alternatively, you can use the instructions in step 1 on the primary controller, but as for the standby controller, completely reset it back to factory defaults by following these instructions: How to factory reset the config of a WiNG AP or controller from CLI

       B - Reconfiguring the cluster:
  1. From the Web UI On the Primary controller, go to Configuration > Devices > Device Configuration > Select the System Name > click on the Edit button > Profile overrides > Cluster
  2. Configure the following settings:
  • Cluster mode: Active​
  • Cluster name: <cluster name>
  • Master priority: 255
  • Force Configured State: Check box (this allows the APs to re-adopt onto the primary controller once it is back online)
  • Force Configured State Delay: <3 to 1800 minutes>
Note: There is no need to add a Cluster Member at this point.
User-added image
  1. Click OK and then Commit and Save
  2. a. SSH into the Standby controller and run the following CLI commands (for Mint Level 2 deployments go to section 4b):
>enable
#join-cluster <primary_ip> user admin password <pswd> mode <active or standby>

- <primary_IP> Enter IP address of primary controller
- <pswd> Enter the password used to log into the primary controller with
- <active or standby> Select active for an active-active cluster or standby for 
  an active-standby (recommended) cluster 

Example:
#join-cluster 192.168.1.10 user admin password admin123 mode standby
  1. b. Mint level 2 deployments:
In deployments where Mint level 2 is required, routing level 2 should be specified when joining the cluster:
>en 
#join-cluster <primary_ip> user admin password <pswd> level 2 mode <active or standby> 

- <primary_IP> Enter IP address of primary controller 
- <pswd> Enter the password used to log into the primary controller with 
- <active or standby> Select active for an active-active cluster or standby for
 an active-standby (recommended) cluster 

Example: 
#join-cluster 10.120.200.40 user admin password admin123 level 2 mode standby
  1. Run show commands to make sure that the cluster is properly configured and working:
#sh cluster status
#sh cluster members
#sh cluster config
Additional notes
Recommendations and clustering best practices: Where can I find best practices and recommendations for WiNG deployment?

Please contact our Global Technical Assistance Center (GTAC) if further assistance is required.

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255