r500 configuration get failed

  • 1
  • Question
  • Updated 9 months ago
  • Answered
SZ100 running version 5.1.2.0.302.  AP firmware 5.1.2.0.373
All of our R500s are showing event code 117 - AP configuration get failed
Severity shows "Informational".
Event shows up about every 5-15 seconds per AP. We have 350 R500 APs so event log fills up really quick.
None of our R710,R610 or R510s are having this issue.  It's only the R500 APs
Everything seems to work just fine.  I see clients connected and traffic on the AP.
I have searched Google and Ruckus, but so far no information on my this happens or how to fix it. 
Is it really just "informational" or is there something wrong.  Will the APs not update their config?

Photo of Jason Hilt

Jason Hilt

  • 4 Posts
  • 0 Reply Likes

Posted 9 months ago

  • 1
Photo of Syamantak Omer

Syamantak Omer, Official Rep

  • 503 Posts
  • 162 Reply Likes
Hi Jason,

Event suggesting that AP is unable to get new configuration from controller.

Could you try to make any minor configuration change from controller to just one AP, like changing the AP's name and see if it reflects on AP CLI.

To check AP name from AP CLI, SSH into the AP and run below command.

get device-name

Clients can still be operational even if AP is unable to get new configuration, so you may not see any service impact, until you try to make any major change like adding a new SSID or deleting the existing SSID, etc.

Also confirm if these R500s are part of a single AP zone or different? What about other AP models, are they also in same AP zone or different?

Any differance betweeen R500 (non-working) vs other AP models (working) like connected to same site or different sites, connected to same switch or different switches, conected to different networks, etc.
Photo of Jason Hilt

Jason Hilt

  • 4 Posts
  • 0 Reply Likes
Not sure what fixed it,  but they are mostly now working correctly.  Still have a few that are failing, but at least it's not hundreds of them anymore
It may have been changing the AP admin login password or just from changing the config and rebooting them.
All APs are in the same zone, but separated in different AP groups.
I'll update if I should find anything more definitive on what fixed it.