04-02-2021 01:08 AM
I've been haunted by the issue as describe in the topic.
My company has recently migrated all of our vm servers to cloud. This includes our vSZ as well.
vSZ is behind a VM fortigate firewall .
Our APs are behind a switch and sophos xg firewall.
Both firewalls has an ipsec tunnel linked.
DHCP server was set on the core switch .
When endpoint devices connected to the SSID of the AP, it has no problem getting IP from the DHCP servers in less than a few seconds. However, it'll show no internet for 4-5 mins.
After sometime, it'll suddenly be with internet.
Although devices connected with the ssid retries connection, it'll immediately have internet connection.
Only for new devices, it'll have a 4-5mins issue without internet .
Anything i need to set on AP side or vSZ side ?
04-20-2021 11:30 AM
Could you share the support case number?
04-22-2021 02:35 AM
Case# 01190975
Case has been closed though.
I've actually contacted a vendor on this.
Vendor routed the support back to Ruckus .
For that i don't have the case number.
11-21-2023 06:17 AM
Hi net_admin_elken
We are facing a similar issue. Did you manage to solve it?
We are using on-prem Ruckus controller and AP r500 and r610.
Often when new clients try to connect it will take a few seconds up to 30 seconds for it to connect, but then it says "no internet". Then if you leave it for a while maybe several minutes then suddely there will be internet access.
11-22-2023 10:14 AM
Hi @JakoRockA,
They raised a case with Support and Support verified the logs, but did not observe any delay in the logs.
For further troubleshooting there was no response thus case was closed.
I suggest posting a new thread with all the details like controller model, software version, symptoms, etc.
04-22-2021 11:04 AM
Hi,
I have reviewed the case and as per AP logs, there was no delay getting IP address, however, it takes few minutes for client to be able to reach internet.
As I said before, we need to take captures on a few points to check exactly where traffic is dropping.
Support also suggested you to take captures to troubleshoot further, but case was closed as there was no response.