Skip to main content

3 Messages

 • 

122 Points

Thu, Jan 3, 2013 2:02 PM

Closed

What are the issues reported by the customers in 9.5.0.0.156 release?

This conversation is no longer open for comments or replies and is no longer visible to community members.

Responses

1 Message

 • 

50 Points

8 years ago

Very sad

18 Messages

 • 

250 Points

8 years ago

I experienced APs rebooting when getting 60-70 clients associated.

683 Messages

 • 

11K Points

Did you get that fixed?

18 Messages

 • 

250 Points

8 years ago

We were advised to downgrade to 9.4.3.12. No reboots now with 150+ associated to some APs

18 Messages

 • 

282 Points

8 years ago

I didn't try 9.5.0.0.156 but 9.5.1.0.50 and had the same issue as Andrew. We downgraded to the same on advice from support and just upgraded to 9.4.3.0.16 which is working fine.

18 Messages

 • 

282 Points

8 years ago

Not sure if it helps but;

I didn't try 9.5.0.0.156 but 9.5.1.0.50 and had the same issue as Andrew.

We have since downgraded to the same on advice from support and just upgraded to 9.4.3.0.16 which is working fine.

18 Messages

 • 

250 Points

8 years ago

It does help. I was thinking of going to 9.5.1.0.50 I guess I'll have to wait.

683 Messages

 • 

11K Points

8 years ago

I'm checking to see if we can ID the specific issue being described so we can give you a target fix.

18 Messages

 • 

250 Points

7 years ago

Thanks Keith, that would be helpful.

7 Messages

 • 

154 Points

7 years ago

We experience the same: ZF7363's are rebooting when the try to serve 50+ clients. We use version 9.5.1.0.5. In the logs it shows the last reboot reason: watchdog timeout or application reboot.

Hopefully 9.6 will solve the issues :)

18 Messages

 • 

282 Points

7 years ago

Follow up:

I upgraded 9.5.0.0.156 last week and had to downgrade back to 9.4 due to the issue. I grabbed the logs from the a couple of the AP's that rebooted and the controllers if Ruckus is interested. Let me know and I can email or open a case again on the issue.

What I observed: Upgraded in the evening (9:00 p.m.?) and everything was great. No reboots overnight. At about 8:15 we started getting AP lost contact messages. It was random from site to site and I would bet that we never had more than 30 clients associated to one AP. At 8:45 a.m. I made the call after 7 different AP's rebooted to downgrade back to 9.4.3.0.16. Since the downgrade, I haven't lost an AP yet and it has been 6 days.

Now, I'm a K-8 school district and at about 8:00 a.m. is when we begin to ramp up for the day. But none of my schools are in session at that time and I wouldn't expect to see more than 300 clients across the entire org. The only thing that I can think that might be an issue, is that we aren't routed at each site but at the district level. This means that the broadcast for a single VLAN could have 1000+ clients (wired/wireless) depending on what network they are connected to (we are changing this over the next 13 months).

Sorry for the length, but the wireless is usually set it and forget it for us. I really want this to work as I'd like to start testing our new 7372 AP as a replacement to our 7363's for future purchases.

683 Messages

 • 

11K Points

This is a great conversation that's separate from the main topic, so I created a new topic to continue the discussion. Please reference the new topic here: Issues in with high client density post 9.5.0

683 Messages

 • 

11K Points

7 years ago

What we think is going on in these cases is a change to the way memory allocations in the AP were handled in 9.5. We have a workaround available (e.g. anyone needing to go to 9.5.1 for new AP model support as mentioned).

Please open a support case at https://support.ruckuswireless.com/ca... -- add any debug, logs, etc you might have so we can quickly ensure it's the same issue).

We're also working on a more transparent fix, but no ETA yet.

-K

18 Messages

 • 

282 Points

First off....Sorry for posting the Case ID. Didn't know that was a problem.

Is this planned on being fixed soon? If not, then I also updated the ticket asking to have our configuration tuned so that we can run it. But if its planned to be resolved in the next month or so then I'll just wait. Don't want a band-aid fix on our wireless network.

We have a 7372 that we would like to test and a 7982 that I would like to see the additional features. Can't do this till we upgrade or have to upgrade and test outside of production hours.

683 Messages

 • 

11K Points

It will likely be addressed in the 9.6.1 release which is still a few weeks away.

7 Messages

 • 

154 Points

We also created a case (i can send the Case ID if you would like to receive it ;)). I don't like to downgrade all our +/- 8 ZoneDirectors, because all the configuration options get lost... And we can't use the 7372. But these 9.5 release are giving us to much downtime due to all the 7363's that keep rebooting.

683 Messages

 • 

11K Points

I have super powers and can locate your cases :) I will make sure its routed appropriately

18 Messages

 • 

282 Points

7 years ago

Keith,

Done. Case ID: 00067398

7 Messages

 • 

154 Points

7 years ago

I would like to know the workaround that is available.

Meanwhile we have an other open case (Case ID: 00064008). It could be related to this AP reboot problem, but I'm not sure. Currently it's not possible to retrieve the logs as the ZD is turned of :)

683 Messages

 • 

11K Points

It involves some configuration adjustment. Beyond that it's best to work with your support engineer as I can't post specifics here. It's context-dependent so there's no general-case workaround to post.

3 Messages

 • 

80 Points

7 years ago

I would like to know if the issues in 9.5 are resolved in 9.6 or is the best option to downgrade to 9.4.3.0.16?

683 Messages

 • 

11K Points

7 years ago

The issue described above is not fixed in 9.6.0.0.267. So the options are to downgrade to 9.4.3.0.16 or to open a case and work with the support engineer to tune the required parameters.

Other issues present in 9.5 are addressed in 9.6 - please refer to the 9.6 release notes for details.

-K