SZ 3.5 Rebooting when connected to a trunk port

Anonymous · ‎05-22-2017

Hi All, we are investigating an issue we have experienced on multiple controllers whereby if they are running SZ3.5 and are connected to a switchport configured as a trunk (in our case Cisco) the controller goes into a boot loop cycle and you are unable to communicate with it. Changing the port config to access restores stability.

We have a case open with Ruckus support but just wanted to see if anyone had experienced a similar issue?

arul_selvan · ‎05-22-2017

Hi Robert,

Could you please provide me the support case number, I have an another customer with same issue.
We have opened a bug and I am working on this issue with our engineering team.

Regards,
Arul Selvan

Anonymous · ‎05-22-2017

Sure case ID is 538432

Anonymous · ‎05-22-2017

Hi Robert,

We also have problems after upgrading to 3.5. One controller is working fine, other one is disconnected from the cluster and keeps rebooting on the fiber port.

Our network vendor is Huawei. We also have a case with Ruckus and Arul is also working on our case.

Regards Edwin Gerritsen

Anonymous · ‎06-02-2017

Guys this has now been acknowledged by Ruckus as an issue. They say there will be a fix in MR release. There is also some other serious bugs. They have now released a GA refresh but i will wait until a full MR before upgrading