01-26-2024 08:03 AM
Since upgrading to 200.15.6.12.304, Apply devices (laptops, phones etc) won't occasionally to the network, 2xH550 and 1xR650. When it happens, the OS shows as "connected" but it fails at DHCP, DHCP is external to Ruckus with short (5 min leases). Never had this issue before, reverting to 200.14.6.1.203 fixes it.
Solved! Go to Solution.
05-13-2024 08:22 PM
Hi All,
We have a official release of 200.15.6.112.54 available in support site, please check.
05-16-2024 04:35 AM - edited 05-16-2024 04:36 AM
It’s doing ok so far so I guess I won’t touch it until problems arise. And I’ll try your advice thank you ( still using 200.14 )
04-10-2024 08:08 PM - edited 04-10-2024 08:09 PM
The problem is not fixed, iPhones cannot roam properly. It’s frustrating that it happened in the first place but even more that it’s not fixed after many months
04-10-2024 08:11 PM
@sgg222
Could you please share us more details on this which will help us to isolate if we are hitting the same issue or a new issue?
1. Is the issue is specific to the devices like iPhone\MAC?
2. Is the issue specific to the devices like Sonos\Apple watch?
3. Issue occurs when roaming\wake up from sleep mode etc..
Can someone share the client connectivity logs from the diagnostics tab?
04-11-2024 04:32 AM
It is the same issue I and many others reported when 200.15.6.12.304 came out. iPhone 14 Pro models are the ones we tested with. Issue occurs when roaming and/or waking up from sleep mode. Unfortunately, I don't have the logs as the issue is too disruptive, so I had to roll back to 200.14.
By the way, as you're downgrading two releases 200.15MR->200.15->200.14 requires you to use local upgrade for 200.15->200.14 with factory reset, which is suboptimal at best. On top of that, 200.15MR configuration backup cannot be restored on 200.14
04-11-2024 04:49 AM
I had the problem with an ipad pro. I also rolled back.