Ruckus vSZ-E 6.1.1

[Phawkins1]

Hi,

I am currently having some issues regarding the Ruckus vSZE. We have one site in particular which has multiple outdoor and indoor APs, 1 T350C, 3 T310D, 11 T310C, 23 R510, 12 R350, and 302 R320. 

We use 4 seperate SSIDs, one for a corporate network, one for a general-use for the camp, one for the TVs on the camp and one for IOT devices. As this is a mining camp, we see a massive influx of users from roug

hly 530PM to 9PM. With issues generally starting at around 8, the highest peak time. They have all been set up as static IPs and dhcp exclusions have been set and this is fine. 

APs seem to drop in and out and some of the errors we get are as followed:

AP [] was rebooted by the system because of [unknown reason]. 

AP [] was rebooted by the system because of [system fault].

These issues below occur together:

AP [] is unable to reach radius server [x].

AP [] is unable to reach radius server [x].

AP [] was rebooted by the system because of [rsmd_func cia monitor AP lost SCG more than 7200 seconds].

- sometimes this issue occurs with it: AP [] was rebooted by the system because of [system fault].

Also during peak times it seems that some users can't use face-time or apps on their TVs correctly, issues with buffering etc.

We did a site visit and replaced a lot of PoE Injectors, ONTs and APs, but these issues are still occuring. 

[Ayush_Tripathi]

Hello @Phawkins1 

Please download the AP support logs at the time of the issue and check for the reboot reason in the support logs.

For AP reboot reason-[rsmd_func cia monitor AP lost SCG more than 7200 seconds], you configure the AP reboot time to 0 hours, AP Zone setting > Advanced Options >  AP reboot timeout > "Reboot AP if it cannot reach default gateway after" to "0"

Also upgrade the firmware version on the controller to 6.1.2.0.404 as this version is latest technology release.

https://support.ruckuswireless.com/products?view_type=recommended_releases_table

[sanjay_kumar]

Hi @Phawkins1 

Looking at the below logs, it does seems like a communication issue between the AP and Controller:
"AP [] was rebooted by the system because of [rsmd_func cia monitor AP lost SCG more than 7200 seconds]."

Also, below log indicates that the AP is not able to reach the Radius Server as well:
"AP [] is unable to reach radius server [x]."

So it does seem like a communication issue for the AP.

However, below log shows that there is something else is causing the issue as well, which is rebooting the APs.
AP [] was rebooted by the system because of [unknown reason].
AP [] was rebooted by the system because of [system fault].

On the AP Zone settings >> Advanced Settings, can you set the below options to 0 and see if the APs are still rebooting?
If they are not rebooting after changing the settings, then it will be easy to troubleshoot the issue if it is communication issue.