Does the standalone 7982 AP support configuring via config file (ala Cisco APs)

  • 1
  • Question
  • Updated 6 years ago
  • Answered
Currently evaluating Ruckus 7900 series AP for our Bingo application used by 100's of Bingo Halls.

Currently using Cisco AP's where we can configure a model and send the config file to the location to be uploaded, thus eliminating the need for configuration on-site by our techs. Can the Ruckus AP support this model?

These can be small locations with one or two AP's which do not warrant a Zone Director.

I have AP configured and it is working great but missing a config file could be a deal killer for us.
Photo of Mel Costello

Mel Costello

  • 1 Post
  • 0 Reply Likes

Posted 6 years ago

  • 1
Photo of Harish

Harish, Employee

  • 21 Posts
  • 4 Reply Likes
Official Response
Hi Mel,

With Regards to your question on standalone 7982 AP support configuring via config file .
There is no option to take a backup of Ruckus standalone AP configuration, it is only possible to take a backup of ZD configuration since unlike ZD, AP does not have much things like local database, DPSK or guest pass keys stored in its memory.

However you can push the AP Configuration Templates to all standalone AP's if these AP's are connected with Flex-Master[Ruckus Management Software].

Configuration templates allow you to provision changes in bulk to a group of devices.Attributes, such as SSIDs, login info, and L2TP settings, can be applied in bulk by simply deploying a configuration template. For example, you can change the SSIDs or L2TP settings of a group of ZoneFlex 2942 APs.

Please go through the below link which helps you to know about template creation in FlexMaster
https://support.ruckuswireless.com/do...

All the best.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2955 Posts
  • 414 Reply Likes
We have an outstanding Feature Request for a text AP configuration backup and
restore capability, that has yet to receive Product Marketing approval. Please let
your Ruckus Sales team know you would like this feature, as their pressure is what
it takes.

Meanwhile, I have addressed this question previously, and wrote this doc on info
you can collect and use to re-create or build an AP from scratch.

Filename: AP-Standalone-Backup.doc

We don’t have a backup under GUI/CLI for standalone APs, but you can collect information that will help reconfigure an AP, if you should ever have to factory default or replace one. Use an SSH application like putty.exe to access the AP and the ‘help’ command to display available commands. The output of these can
be helpful to (re)configure an AP from factory defaults.

If you have an online working AP, collect the important IP scheme/gateway and SSID name/security policies from it, otherwise obtain new/previous IP addressing and VLAN-ID/subnet mapping from network admins.

Assuming you will be setting up APs with a static/known IP address with a known default-gateway router,
you can follow these configuration steps to setup a new/factory defaulted AP for standalone mode service.
---
Configuring AP:

1. Perform factory default of AP (boot 3 minutes, press Hard Reset for 8+ seconds, wait until you get replies to
pings to 192.168.0.1 IP address, from your pre-configured (192.168.0.anything-else) PC/laptop. Open a
browser session to https://192.168.0.1, and login with ‘super / sp-admin’ credentials.

2. From Configuration::Device, enter an AP Device Name: _______ and click Update Settings. Use a name
that can help identify it’s location/purpose.

3. From Configuration::Wireless (or Radio 2.4G and Radio 5G, respectively) and Common tab, be sure or set
Country Code to United States, click Update Settings.

4. From Wireless 1 tab, enter Wireless Network: ______ and SSID: _______ names (usually matching).
Click Enabled for Wireless Availability and set option for Broadcast SSID as desired. If using anything
but Open Authentication, click and choose from Encryption Method: dropdown choice of WEP or WPA
and setup the encryption and passphrase information. (we recommend WPA2/AES with PSK)

5 Repeat on Wireless 2 tab, for additional SSID, Wireless 3 tab, etc.

6. If using VLANs and different subnets for your wireless SSIDs, go to Configuration::VLAN page. Enter the
VLAN-ID number in the box beside the SSID to assign it. Click Update Settings (test) button when
complete, and the AP will check the switchport to see if all VLANs are available on the trunk.

7. For last step, go to Configuration::Internet page, and enter the router default Gateway IP address for the
subnet that the AP will be connected to. Change the default Connection Type from DHCP to Static IP and
enter the IP Address: __.__.__.__ and network Mask: __.__.__.__ (ie 255.255.224.0 for /27 bit subnet).

This is the “last step”, because when you click Update Settings, your 192.168.0.x PC/Laptop will lose connectivity with the AP, and it’s ready to be attached to your (PoE) switch port configured to trunk the
optional VLANs that you can assign to WLAN SSIDs.
---

Collecting AP Backup Information:

SSH to an AP’s IP address with utility like putty.exe and collect/save the output from these commands which should be sufficient to reconfigure a defaulted (or apply to new) APs, as far as IP addressing and WLAN details.

If using the putty terminal application, you can save session output to a filename, as your backup reference.
http://www.chiark.greenend.org.uk/~sg...

Open putty.exe. In top/left, under Session, click Logging.

Under Session logging:, click Log all session output. Rename putty.log to AP10-7-7-81-102710.log (for example, using AP’s IP address and a date in the filename), and Browse to the directory where you want
the session backup file saved.

In top/left, click on Session. Enter the IP address of the new/factory defaulted AP, 192.168.0.1 and note
that SSH (tcp:22) is specified as the default Protocol (you can telnet to devices that don’t support SSH).
Click Open to access the AP. If prompted that you haven’t seen this host before, accept the challenge.

Run these AP commands to collect the useful information. In my example, I have one open auth WLAN
on 2.4GHz, and one open and one WPA2-PSK WLAN on 5GHz of my dual-band 7962 model AP. I do
not have VLANs assigned however.

rkscli: get boarddata # optional, displays AP model and s/n info
name: zf7962
magic: 35333131
cksum: a47
rev: 5.3
Serial#: 180901007787
Customer ID: 4bss
Model: zf7962
rkscli: get version
Ruckus 7962 Multimedia Hotzone Wireless AP
Version 8.2.1.0.21
rkscli: get device-name
device name : ‘mb7962-AP’
rkscli: get ipaddr wan
IP Address Configuration Type: static, IP: 192.168.65.15 Netmask 255.255.255.0 Gateway 192.168.65.1
rkscli: get vlan
-----------------------------------------------------------------------------------
Network 0: (Management) VID 1
Services: StaticIP
Eth Port (no tag): 0,1
Wireless (no tag):
- wlan0 (mb7962-bgn)
- wlan1 (Wireless 2)
- wlan2 (Wireless 3)
- wlan3 (Wireless 4)
- wlan4 (Wireless 5)
- wlan5 (Wireless 6)
- wlan6 (Wireless 7)
- wlan7 (Wireless 8)
- wlan8 (mb7962-an)
- wlan9 (mb7962-an2)
- wlan10 (Wireless 11)
- wlan11 (Wireless 12)
- wlan12 (Wireless 13)
- wlan13 (Wireless 14)
- wlan14 (Wireless 15)
- wlan15 (Wireless 16)
-----------------------------------------------------------------------------------
OK
rkscli: get wlanlist # Note which wlanX have status of ‘up’, and run cmds below on them only.

name status type wlanID radioID bssid
-----------------------------------------------------------
svcp up AP wlan0 0 00:24:82:3d:35:98
home down AP wlan1 0 00:00:00:00:00:00
rcks down AP wlan2 0 00:00:00:00:00:00
mdfx down AP wlan3 0 00:00:00:00:00:00
wlan4 down AP wlan4 0 00:00:00:00:00:00
wlan5 down AP wlan5 0 00:00:00:00:00:00
wlan6 down AP wlan6 0 00:00:00:00:00:00
wlan7 down AP wlan7 0 00:00:00:00:00:00
wlan8 up AP wlan8 1 00:24:82:3d:35:9c
wlan9 up AP wlan9 1 00:24:82:7d:35:9c
wlan10 down AP wlan10 1 00:00:00:00:00:00
wlan11 down AP wlan11 1 00:00:00:00:00:00
wlan12 down AP wlan12 1 00:00:00:00:00:00
wlan13 down AP wlan13 1 00:00:00:00:00:00
wlan14 down AP wlan14 1 00:00:00:00:00:00
wlan15 down AP wlan15 1 00:00:00:00:00:00
OK
rkscli:
rkscli:
rkscli: get ssid wlan0
wlan0 SSID: mb7962-bgn
OK
rkscli: get encryption wlan0
SSID : mb7962-bgn
Net Security : Open (plain-text)
Authentication : Open
Encryption : disabled
OK
rkscli: get passphrase wlan0
bad key:wlans/wlan0/wlan-wpa-passphrase
rkscli: get dvlan wlan0
wlan0 Dynamic-VLAN Mode: Disabled
OK
rkscli:
rkscli:
rkscli:
rkscli: get ssid wlan8
wlan8 SSID: mb7962an
OK
rkscli: get encryption wlan8
SSID : mb7962an
Net Security : Open (plain-text)
Authentication : Open
Encryption : disabled
OK
rkscli: get passphrase wlan8
bad key:wlans/wlan8/wlan-wpa-passphrase
rkscli: get dvlan wlan8
wlan8 Dynamic-VLAN Mode: Disabled
OK
rkscli:
rkscli:
rkscli:
rkscli: get ssid wlan9
wlan9 SSID: mb7962an2
OK
rkscli: get encryption wlan9
SSID : mb7962an2
Net Security : WPA
Protocol Version : WPA2
Authentication : Open
Cipher Algorithm : AES-CCMP
WPA PassPhrase : 1234567890
OK
rkscli: get passphrase wlan9
wlan9 WPA PassPhrase (10): 1234567890
OK
rkscli: get dvlan wlan9
wlan9 Dynamic-VLAN Mode: Disabled
OK
rkscli:
rkscli:
rkscli: exit
Quit:
OK