topic A problem of election new master after a entirely reboot of all in Unleashed

A problem of election new master after a entirely reboot of all

Hs_Choi — Thu, 01 Apr 2021 01:32:01 GMT

HI.

I tested a failover and takeover of unleashed aps.

However, it did not meet our expectations.

In my lab, I deployed two ap; a H510 and a H320;, and configured static ip address on each.

I did master setup to H510 and member setup to H320.

Once I confirmed all aps were good working, went down power to all APs.

And I was turned on H320 which was member ap before a reboot.

But election of new master didn't occur.

The H320 which was member ap before a reboot became new master for about 20min.

Why is the new election process so slow?

If this situation was a real, customer would have many complaints becasue he thought a network problem.

Are Ruckus aware of this?

Regards.

Re: A problem of election new master after a entirely reboot of all

karthik — Thu, 01 Apr 2021 02:33:47 GMT

Hi,

In CLI, run command get election to see the status of the election process and you may also debug using command set election debug <1-8>.

HTH

Thanks

Karthik

Re: A problem of election new master after a entirely reboot of all

Hs_Choi — Fri, 02 Apr 2021 07:31:01 GMT

Wow.

From your recommentaion, once I tried to replicate this with R610(master, static ip 10.10.20.101) and H510(member, static ip 10.10.20.105), H510 after power-on took over new master in about 90sec but debug log for election is empty on syslog though I set debug level.

Unfortunatly H510 had static ip 10.10.20.101 which was ip address of R610.

What is that?

Regards.

Re: A problem of election new master after a entirely reboot of all

John_Doe — Thu, 02 May 2024 21:27:51 GMT

Hi All,

Pretty old topic, however got the same behaviour running two R550.

What's the fix for this, any idea?