Skip to main content

14 Messages

 • 

240 Points

Wed, Aug 29, 2018 6:59 AM

The indoor R510 APs reboot from time to time giving the error message "AP lost SCG more than 7200 seconds "

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?

Responses

Employee

 • 

37 Messages

 • 

722 Points

2 years ago

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,

14 Messages

 • 

240 Points

2 years ago

My worry is what might cause the AP not to reach the controller?

388 Messages

 • 

5.9K Points

2 years ago

You have to find the reason on wired side.

Employee

 • 

37 Messages

 • 

722 Points

2 years ago

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.

14 Messages

 • 

240 Points

2 years ago

@Sandeep Gupta, the controller is in the cloud but sometimes all the APs are just working fine, at times when i log in to the controller i find that some of them down only to be up after some time 

Employee

 • 

37 Messages

 • 

722 Points

2 years ago

Ok so, if everything continues to function normally and the controller is accessible you would need to perform some deeper troubleshooting to determine root problem.  Best to call TAC.

In the mean time, you could increase the timer so this does not happen so frequently since there is no impact to user experience.