Wing 5.8 - Cluster - Config

[Phil_storey]

I have tow RFS units setup in a cluster, today I failed the primary over to ensure that the backup took over and then failed back at the times set, which it did, I noticed that on one of the WLAN clients could not connect, when the Primary came back online and the AP's moved back to the primary the clients could connect, so there is some issue with the config, If the cluster is taken down and then recreated will this push the config from the primary to the backup, or is there a command line that I could use to ensure the backup does have the most up to date version that works on the primary ?

[Christoph_S]

Hello Phil,

When creating the cluster using the join-cluster command, the primary config is mirrored on the standby cluster member. Run the show running config on both and make sure that this is the case.

If you have multiple vlans, I would start by checking to make sure that all those vlans are allowed through the switchport the standby controller is connected to. Might be that that specific VLAN the WLAN is mapped to is not allowed out of the either the port on the standby controller or the switch port the standby controller is connected to.

If you feel that this is a clustering issue, you might want to try out this: https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-disable-and-recreate-a-non-working-...

[Carlos_Assunção]

Hi,

How did you create the cluster for the first time.

Best Regards

[Phil_storey]

Hi
there are some differences between the primary and the backup, the cluster is up and I can see the members ( 2 ) operational state is active - the primary is the master and the backup is false. is there a command that will refresh the config on the backup or to pull the config in from the primary ?

[Timo_Sass]

connect to booth RFS via CLI and type:
enable
self
show contex

This show you local overwrites on each RFS. Maybe the interface have a local overwrite.