The indoor R510 APs reboot from time to time giving the error message "AP lost
SCG more than 7200 seconds "
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2018 11:59 PM
The indoor R510 APs reboot from time to time giving the error message "AP lost SCG more than 7200 seconds ". APs are managed by a Virtual Smartzone Essentials, 3.6 version. Have someone experienced this error before and what is the solution to this?
6 REPLIES 6

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2018 06:00 AM
Hi There,
This is expected behaviour per default settings. You can change the timer, but 2 hours is the default if the AP cannot reach the controller for it to reboot itself in an attempt to resolve connectivity issues.
You should be able to change this in the controller, under access point group configuration. AP Reboot Timeout.
Cheers,
This is expected behaviour per default settings. You can change the timer, but 2 hours is the default if the AP cannot reach the controller for it to reboot itself in an attempt to resolve connectivity issues.
You should be able to change this in the controller, under access point group configuration. AP Reboot Timeout.
Cheers,
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2018 06:35 AM
My worry is what might cause the AP not to reach the controller?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2018 06:42 AM
You have to find the reason on wired side.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2018 10:02 AM
Yes, so that is a bigger question and would require reviewing system logs, etc. to determine why the AP lost connectivity in the first place. It is most likely a network issue somewhere.
I'm assuming the controller did not go down for an extended period? Was any client connectivity affected prior to the reboot taking place? Are both the controller and access point on the same LAN? If the controller is in the cloud, you must ensure the public IP (Control NAT IP) is configured to be sent to the AP otherwise it will only look for local private IP and never reach the controller.
Best bet is to work with your VAR to help determine the issue. If it is Ruckus networking hardware, you could also engage our TAC.
I'm assuming the controller did not go down for an extended period? Was any client connectivity affected prior to the reboot taking place? Are both the controller and access point on the same LAN? If the controller is in the cloud, you must ensure the public IP (Control NAT IP) is configured to be sent to the AP otherwise it will only look for local private IP and never reach the controller.
Best bet is to work with your VAR to help determine the issue. If it is Ruckus networking hardware, you could also engage our TAC.

