Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

How to configure a cluster in ExtremeWiNG Controllers on WiNG5.4 and above

« Go Back

Information

 
TitleHow to configure a cluster in ExtremeWiNG Controllers on WiNG5.4 and above
Symptoms
How to configure a cluster in ExtremeWiNG Controllers on WiNG5.4 and above
Environment
  • Summit WM 3600
  • Wireless Mobility version 5.x
  • Cluster
  • ExtremeWiNG Controllers
  • WirelessWiNG Controllers
  • ExtremeWiNG 5.X firmware 
Cause
Resolution
  • On the Primary Switch configure the following at the Configuration > Device level
rfs7000-76S>en
rfs7000-76S#self
Enter configuration commands, one per line.  End with CNTL/Z.
rfs7000-76S(config-device-00-15-70-38-02-DE)#
  • Configure Cluster Name        
  • Set Cluster Priority to 255
    • Default is 128
    • Primary must have a higher priority than Secondary
rfs7000-76S(config-device-00-15-70-38-02-DE)# cluster name cluster_76
rfs7000-76S(config-device-00-15-70-38-02-DE)# cluster master-priority 255
  • Configure Cluster IP addresses
    1. Set up the IP addresses for both controllers. Select the correct level to establish the MiNT link (either level 1 or level 2), based on the deployment you have.
    2. Configure the force-configured-state and force-configured-state-delay to ensure that in the event of a primary failure, it will assume its role as the primary once it is back online, following the appropriate delay period.
    3. Commit/Save
rfs7000-76S(config-device-00-15-70-38-02-DE)# cluster member ip 10.0.0.60 level 1
rfs7000-76S(config-device-00-15-70-38-02-DE)# cluster member ip 10.0.0.61 level 1
rfs7000-76S(config-device-00-15-70-38-02-DE)# cluster force-configured-state 
rfs7000-76S(config-device-00-15-70-38-02-DE)# cluster force-configured-state-delay 5
rfs7000-76S(config-device-00-15-70-38-02-DE)# comm wr
  • Login to the CLI of the Secondary Switch and run the following command
rfs7000-76P> enable
rfs7000-76P# join-cluster 10.0.0.60 user admin password superuser mode standby
  • “10.0.0.60” is the IP of the Primary Switch
  • “admin” is the admin username of the Primary Switch
  • “superuser” is the admin password of the Primary Switch
  • Configuring as standby mode for the secondary cluster is recommended.
  • Wait a minute or so and then run the following command from the CLI of the Primary Switch
rfs7000-76S> enable
rfs7000-76S# show cluster members
------------------------------------------------------------------------------------------
    HOSTNAME     MEMBER-ID           MAC          MASTER OPERATIONAL-STATE   LAST-SEEN
------------------------------------------------------------------------------------------
  rfs7000-76P   19.6C.94.50   B4-C7-99-6C-94-50   False   standby           00:00:44 ago
  rfs7000-76S   70.38.02.DE   00-15-70-38-02-DE   True    active            self
------------------------------------------------------------------------------------------
  • Verify that the Primary Switch shows Master = True
  • Verify that the Secondary Switch shows Master = False
  • Verify both the Primary show Operational-State = Active and Secondary shows Operational-State = Standby
Additional notes
  • Both Primary and Secondary Controller IP's must be provided via DHCP Options to Layer-3 adopted AP's for adoption fail-over to occur.
  • Always remember to set up correct default-gateway IPs on both controllers and try to ping other controller's IP address before executing the join-cluster command.
  • When getting a replacement device on the cluster, please check the firmware running on the new controller. Devices with different WiNG firmwares running will not create the cluster correctly.
  • In case you need a deeper view or further information about Clustering please check the following link How to use join-cluster on WiNG5.4

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255