Unleashed AP(s) disassociate from Master and also become Master

[bryan_schneider]

I have several clients that have this same issue where one or more APs become a Master also. Here is what I mean when I login to what I know to be the Master dashboard with a static IP, one or more APs are disconnected which are DHCP. After a bit of hunting for the other APs IP I am able to login to those disconnected APs and one of them are also a Master.

My only recourse, that I know of, to put them back on to the Master that I want is to remove the disconnected APs in the Master dashboard and then reset them.

It's as if the communication between the master that I chose and the other APs are lost for a little bit (hour or so?) one of the others take the Master role. Once the communication is restored, the role doesn't reverse and the original master is still the Master while the other APs is also a Master. 

Advice?

[michael_grant_6]

What firmware version are you on? Does this adversely effect network performance/connectivity at all?

[bryan_schneider]

The one client that I just "fixed" this morning was on 200.2.9.13.186. I just updated them to 200.3.9.13.228. That second Master, I was able to factory default it remotely and it joined the real master as expected as the fix.

No as to your second question. Devices can still connect and no performance impact. This is just a management issue at this time.

[wes_turner_hc8m]

I have noticed this issue after a power outage. Whichever AP reboots first will become the new master and assume its static IP (if it was set to static). If it is not the original master AP, you get the duplicate IP issue and APs going offline.

Not all our installs are on UPS, but even some that are have the issue. I will say they are usually existing poor quality line-interactive UPS units and not Online type. We have never had an issue when using an online type UPS. Client budget or existing systems does not always allow for an online UPS.

I will say the issue seems to happen less now running the latest firmware release. We have migrated old systems to the newest firmware if we have had to go onsite to fix the disassociated APs but we have also changed the masters to dhcp and given up remote access. Not sure which move made the difference.

[michael_grant_6]

I had a very similar issue on 200.2 firmware after power loss, but have since updated to 200.3 and put my PoE switch on a UPS. 200.3 release notes say:

"Resolved an issue that could lead to IP address conflicts when the Unleashed Master AP was configured with a static IP address and failed to come back online after upgrade/reboot. This could result in multiple member APs being assigned the same conflicting IP address as the statically configured original Master. [ER- 4863]"

Similar issues have been reported: https://forums.ruckuswireless.com/ruc...

[bryan_schneider]

It looks like I will be updating all firmware to 200.3. I am doing that as I type with that second client with 4 R600.