topic Re: How to access factory default config files. in Access Points - Indoor and Outdoor

How to access factory default config files.

nick_litteral — Wed, 17 Feb 2016 17:41:05 GMT

How do you access factory default config files ? The application is for an end user that has changed the settings and needs to change them back to the settings that we set for them not the default ruckus has set by pressing the reset button on the back of the unit.

Re: How to access factory default config files.

michael_brado — Wed, 17 Feb 2016 18:17:09 GMT

You can restore a Backup configuration. You can collect a configuration from a defaulted ZoneDirector. Can you please clarify your request?

Re: How to access factory default config files.

nick_litteral — Wed, 17 Feb 2016 18:21:22 GMT

I want to be able to hit the reset button on the back of the R500 and have the defaults be reset to 172.30.255.0 and a few other setting changes instead of 192.168.0.1 and factory defaults

Re: How to access factory default config files.

michael_brado — Wed, 17 Feb 2016 18:33:35 GMT

Ah, I see. Unfortunately, we do not have an AP backup/restore capability today.
You can configure many AP settings by CLI command, and script these to configure a factory defaulted AP,
but it's not a packaged feature per se.

Your Ruckus VAR or account team can file Field Requests on behalf of customers, if this would be a valuable capability.

Re: How to access factory default config files.

eizens_putnins — Wed, 29 Dec 2021 20:39:10 GMT

Actually it seems that such feature does exist, but it is limited to big operators, which are locking APs (so after factory reset AP is still configured to connect to same provider's controllers, to makes pointless to steel them). Of cause, access to this feature isn't provided to end-users, which would render it useless, and most probably requires some elevated and password protected access or even slightly modified firmware. I have seen reports about locked Ruckus APs got from EBAY (mainly from USA), but never have seen such AP myself (so it is possible that reports were just results of faulty APs or user mistakes). Still, it's a well-known feature which is easy to do for vendor and it is required by any really big provider, so I believe it does exist.