This section describes the physical LED status and descriptions of the Ruckus Access Points.

If you believe an AP is not operating normally, checking the onboard LEDs can help you determine the AP behavior.

If wireless devices that are connected to your APs are experiencing connectivity issues, check the AP LEDs to determine if your APs are operating normally.

Should you have an issue upgrading a Ruckus AP's firmware via Web GUI, you can upgrade alternatively by using a combination of an SSH session and an FTP Server.

Putty - SSH Software: https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

MobaXterm - FTP Software: https://mobaxterm.mobatek.net/download-home-edition.html

Start your FTP server. For the purpose of this document, we will be using MobaXterms FTP server.

Edit the FTP server by clicking the TOOLS icon.

Select the location of the file (the desktop in this case), username, and password, and leave the port number as default (21). Click 'OK' to confirm the settings.

Open the server again and click the PLAY/START button to start the server.

SSH into the AP using Putty. Use the IP address of the Access Point in the 'Hostname (or IP address)' section. Ensure that you are using port 22 and that SSH is selected. Click 'Open' to begin the connection.

Log in with the Access Points username and password.

This will either be default or defined by the administrator. Once logged in use the following command to begin the upgrade process:

fw set control FILENAME INCLUDING EXTENSION

fw set proto TRANSFER PROTOCOL METHOD

fw set port PORT NUMBER

fw set host IP ADDRESS/HOSTNAME OF FTP SERVER

fw set user SERVER USERNAME

fw set password SERVER PASSWORD

fw up

For example;

fw set control R510_104.0.0.0.1347.bl7

fw set proto ftp

fw set port 21

fw set host 192.168.88.254

fw set user username1

fw set password password1

fw up

Once successful you will receive a 'Completed' status. You must now reboot the AP by typing 'reboot' no quotes and pressing enter to confirm.

Once booted, confirm your work by typing 'get version' no quotes to ensure that the file is successfully uploaded/updated.

Direct management of ICX switches can be performed either via a command-line interface (CLI) or via a web GUI. By default, only the CLI is enabled. This guide explains how to access the CLI, enable the web GUI, and secure all configuration access methods. The web GUI allows full configuration and monitoring of Layer 2 functions, QoS, ACL, authentication, PoE, performing software updates, and much more.

Start by powering up the switch, and connect a serial cable to the console port on the switch. Once this connection has been made to the switch, a command-line interface (CLI) session can be initiated via a terminal emulation program such as PuTTY (www.putty.org). When PuTTY is started, use the following settings depending on whether you are connecting via Telnet or a serial interface:

Once connected to the switch, the interface will present a console prompt. 

IMPORTANT

As of version 80.9x the first thing you will be forced to do when you login to the switch via CLI is change the default password for the default user 'super'.

When you follow the instructions below you will reach the command line ' username <username> password <password>'

If your username differs from the default 'super' you will be creating an additional user account. With this in mind, you may want to remove the 'super' account. Particularly if you have put in a memorable/simple password in for the sake of logging into the unit (you may have put '12345678' or 'password' in to initially login).

To remove an account enter the following command at the config level:

device(config)#no user <username>

You can see what users have been created by running the following command at enable level:

device#show users

The following commands enable web access and secure the web GUI and serial interfaces with a default username and password of your choice.

IMPORTANT

The following commands were used on version SPS08090k (stable release as of August 2022). Upgrading/downgrading from the release may result in unrecognised commands.

device>enable
device#conf t
device(config)#crypto-ssl certificate generate
device(config)#aaa authentication web-server default local
device(config)#aaa authentication login default local
device(config)#enable telnet authentication
device(config)#username XXXX password XXXX
device(config)#enable super-user-password XXXX
device(config)#enable aaa console
device(config)#no telnet server
device(config)#web-management https
device(config)#no user super
device(config)#wr me

The password can be changed by repeating the username <username> password <password> command or via the web interface under Configure > System > Management > User Account.

Cut and paste the following command set at the user EXEC prompt to apply the complete configuration outlined above and set a default username of super with a password of sp-admin and an enable password of password

enable
conf t
crypto-ssl certificate generate
aaa authentication web-server default local
aaa authentication login default local
enable telnet authentication
username super password sp-admin
enable super-user-password password
enable aaa console
no telnet server
web-management https
no user super
wr me

Access to the web interface is now possible, and all access methods are protected by a username and password.

IMPORTANT

To ensure that your switches are secure from unauthorized access, always set a secure password. Never leave a switch with the default brocade/brocade or super/sp-admin settings provided above.

To access the device by web interface simply browse to the dynamic IP the switch obtains (by default the switch is DHCP) or add a static IP address to the device. For example, if you wanted to access the switch based on a static IP address of 192.168.2.100/24 and a gateway address of 192.168.2.1 you would need to do the following;

device> enable

device# conf t

device(config)# ip address 192.168.2.100 255.255.255.0

device(config)# ip default-gateway 192.168.2.1

device(config)# wr mem

device(config)# exit

device#

You should now be able to browse to 192.168.2.100 via a web browser.

Following best practices and for some features to work the firmware of the ICX switches must be upgraded for mostly all scenarios. This guide serves as a step-by-step guide to upgrading the firmware.

You will need:

• ICX Switch
• PC/Laptop
• USB
• Console Cable
• Ethernet Cable
• Firmware image

It is highly recommended you follow the Initial/Basic Setup of an ICX Switch guide.

This will give you access to the switch which you may find easier to understand the upgrade process.

For the purpose of this guide, I shall start the procedure assuming that the initial setup has been completed.

Step 1)

Download and extract the software required.

Downloads can be found here: https://support.ruckuswireless.com/software N.B. you will need Ruckus credentials to obtain the software.

Step 2)

Copy the firmware to the USB root directory.

Step 3)

Start by powering up the switch, and connect a serial cable to the console port on the switch.

Once this connection has been made to the switch, a command-line interface (CLI) session can be initiated via a terminal emulation program such as PuTTY (www.putty.org).

When PuTTY is started, use the following settings to connect via serial interface:

Select Serial

Speed: 9600

Serial line: COMxx

xx being the COM port your device is connected to.

To find which COM port. Open Device Manager under Ports it will be listed USB Serial Port(COMxx)

Once connected to the switch, the interface will present a console prompt.

Step 4)

Plug the USB into the ICX switch

Step 5)

The following commands will copy the firmware to Primary and then to secondary

• ICX5150-24P Switch# Copy disk0 flash SPSxxxxxdufi.bin primary

Note xxxxx is the firmware version.

(When completed you should get a Flash Done message)

• ICX5150-24P Switch# Copy disk0 flash SPSxxxxxdufi.bin secondary

Note xxxxx is the firmware version.

(When completed you should get a Flash Done message)

Once the firmware is completed you need to reboot the switch for changes to come into effect. Type the command:

Reload

You will be asked if you are sure of doing so, confirm it by typing:

Y

Step 6)

Log into the switch. Once logged in check the firmware version.

Show version or abbreviated to sh fl

If the bootroms do not match enter the following commands

copy fl fl following by primary or secondary depending on which bootrom partition has not updated.

For example

copy fl fl primary

(this will update the primary bootrom image with an image from the bootrom secondary partition)

Following best practices and for some features to work the firmware of the ICX switches must be upgraded for mostly all scenarios. This guide serves as a step-by-step guide to upgrading the firmware.

You will need:

• ICX Switch
• PC/Laptop
• TFTP Server Software
• Console Cable
• Ethernet Cable
• Firmware image

Step 1) Download and extract the software required. Downloads can be found here: https://support.ruckuswireless.com/software N.B. you will need Ruckus credentials to obtain the software.

Step 2) Start up a TFTP Server. For this guide I will be using MobaXterm. Once running, click 'Servers'. A new page will load up.

Step 3) Click the 'Configuration' box under TFTP and select the file path of the firmware images

Step 4) Once the information has been entered correctly, start the server by clicking the 'Play' icon.

Be aware there is a default 360-second timeout in which to carry out the next steps before the TFTP server closes.

Step 5) Log in to the ICX Switch via web browser and browse to: TFTP > Image

You will need to enter the IP address of the server (in this case the computers IP address) and the **file name, including the extension.

The file required will be under 'Images' and not 'Firmware'.

SPS - Switch

SPR - Router

Do not use the ufi.bin files, only use the .bin file types when uploading.

Step 6) On the web interface of the switch click 'Copy from Server'. If successful, the device should start the upgrading process.

The GUI will then display a red processing bar, wait until this is complete.

You may refer back to the serial connection to monitor progress, it will take a couple of minutes to write the new firmware and restart.

Step 7) Reboot the device. On the web interface browse to: Command > Reload

Confirm with 'Yes' to reboot. Alternatively, perform a hard (physical) reboot.

Step 8) Confirm firmware is upgraded by logging back in after the reboot.

• CLI command: show version

• Web interface: Monitor> Device

  

SmartZone management and monitoring of ICX switches. The initial release (v.08.0.80) is the first step toward a full-featured wired/wireless integration plan and focuses on monitoring, status, usage visibility, and some basic management, including configuration backups and firmware management.

To direct an ICX switch to the cloud there are a few parameters that must be met;

• SZ Firmware (must be v.5 minimum)
• ICX Firmware (must be v.08.0.80 minimum)

Once the following has been met, check the connection to the cloud controller by pinging the necessary IP, for example;

Should you not be able to ping the controller you must check the following; L2/L3 network, firewall(s), etc.

Point the Switch toward the cloud with the following command(s) your IP may vary depending on the vSZ you are directing your switch to;

Log in to the SZ and go to: Switches > Default Group (Staging Zone), highlight the device, and move to the required switch group. The switch will appear in the group as offline until approved. check the MAC address to ensure you have the correct switch.

Highlight the correct switch and then click move to relocate the switch to the correct zone as required.

This section explains how to recover ICX devices from image installation failure or deleted or corrupted flash images.

IMPORTANT

Text marked in Red is a variable command and may differ from your configuration.

• Connect a console cable from the ICX switches console port to your PC/laptop.

• Connect an Ethernet cable from the management port (the port located under the console port on the ICX switch) to the PC/laptop which will need to host a TFTP server.
  boot up your ICX switch while continuing to press 'B'. The device will be in boot mode for recovery.

• Set the TFTP server IP address that hosts a valid ICX software image using the setenv serverip command.

  ICX 7450-48> setenv serverip 192.168.88.1

  
  

• Set the IP address, gateway IP address, and netmask for the ICX switch (management port), and save the configuration using the setenv ipaddr, setenv gatewayip, setenv netmask, and saveenv commands.

  ICX 7450-48> setenv ipaddr 192.168.88.2
  ICX 7450-48> setenv gatewayip 192.168.88.254
  ICX 7450-48> setenv netmask 255.255.255.0
  ICX 7450-48> saveenv

  
  Note: The IP address and the gateway IP address set for the device management port should be for the same subnet as the TFTP server NIC.

• Enter the printenv command to verify the IP addresses that you configured for the device and the TFTP server.

  ICX 7450-48> printenv    
  baudrate=9600
  ipaddr=192.168.88.2
  gatewayip=192.168.88.254
  netmask=255.255.255.0
  serverip=192.168.88.1
  uboot=brocade/ICX7450/bootcode/spz10115
  Version:10.1.06T215 (May 15 2015 - 11:28:23)

  
  

• Test the connectivity to the TFTP server from the device using the ping command to ensure a working connection.

  ICX 7450-48> ping 192.168.88.1
  ethPortNo = 0
  Using egiga0 device
  host 192.168.88.1 is alive

  
  

• Provide the file name of the image that you want to copy from the TFTP server using the setenv image_name command.

  ICX 7450-48> setenv image_name SPR08090.bin

  
  

• Update the flash using the update_primary or update_secondary command as appropriate.

  ICX 7450-48> update_primary

  
  

• Set the file name of the boot image which was copied from the tftp server.

  > setenv uboot SPR08090.bin

  
  

• Update the uboot file.

  ICX 7450-48> update_uboot

  
  

• Load the image from the primary or secondary flash using the boot_primary or boot_secondary command as appropriate.

  ICX 7450-48> boot_primary                                                                                                                                                                                                                                                                                                                                                                                                                                     

• Optional/Recommended: Providing the switch boots correctly you may now want to ensure both primary and secondary banks are hosting valid and working software images. To do this you can use the method above (steps 8-11 on the opposite bank that you previously flashed) or refer to the following article(s):
• Upgrading ICX Firmware via USB
• Upgrading ICX Firmware via TFTP

If a password has been configured for the device but the password has been lost, you can regain Super User access to the device using the following procedure.

Recovery from a lost password requires direct access to the serial port and a system reboot.

Best practice switch port configuration for trunk and access ports.

Apply the below config line at EXEC level globally.

system-max spanning-tree 253

Apply the below configs on a port/interface level as per switch port mode.

Trunk Port
spanning-tree 802-1w admin-pt2pt-mac

Access Port
spanning-tree 802-1w admin-edge-port

The client would like to use RSTP on ICX switches for automatic failover of a primary and secondary wireless PtP link.

2x ICX switch, 1x primary wireless bridge, 1x secondary wireless bridge

Enable RSTP on ICX switches. By default, each port-based VLAN on the device has its own spanning tree. To enable 802.1w Draft 3 in a port-based VLAN, enter commands such as the following.  

device(config)# vlan 1

device(config-vlan-1)# spanning-tree rstp

Note

STP must be enabled before you can enable 802.1w Draft 3.

Once complete run the following command on the switch ports where the primary radios are terminated (on both switches):

device(config)# spanning-tree 802-1w ethernet 1/1/x priority 64

By default all ports have a priority of 128* so if you give a priority of 64 that port will be preferred to be Forwarding on RSTP.

With this setup both primary ports will be functioning in a forwarding state. Dynamically, one of the backup ports will also be running in a forwarding state while the opposite end will be running in a discarding state to prevent a loop. Should the main wireless link disconnect or one of the heads power down, both backup ports will resume a forwarding state.

Ports roles can have one of the following states:

• Forwarding - 802.1W is allowing the port to send and receive all packets.
• Discarding - 802.1W has blocked data traffic on this port to prevent a loop. The device or VLAN can reach the root bridge using another port, whose state is forwarding. When a port is in this state, the port does not transmit or receive data frames, but the port does continue to receive RST BPDUs. This state corresponds to the listening and blocking states of 802.1D.
• Learning - 802.1W is allowing MAC entries to be added to the filtering database but does not permit forwarding of data frames. The device can learn the MAC addresses of frames that the port receives during this state and make corresponding entries in the MAC table.
• Disabled - The port is not participating in 802.1W. This can occur when the port is disconnected or 802.1W is administratively disabled on the port.
  
  

Link reference: (http://docs.ruckuswireless.com/fastiron/08.0.80/fastiron-08080-l2guide/GUID-65F3A36C-6A87-4752-9CBD-5C7E7CB505F9.html)

DHCP/NAT functionality on SZ-managed APs and DPs (data planes) allows customers to reduce costs and complexity by removing the need for DHCP server/NAT router to provide IP addresses to clients. 

Three general DHCP scenarios are supported:

• SMB Single AP: DHCP is running on a single AP only. This AP also functions as the Gateway AP.
• SMB Multiple APs (<12): DHCP service is running on all APs, among which two of the APs will be Gateway APs. These two Gateway APs will provide the IP addresses as well as Internet connectivity to the clients via NAT.
• Enterprise (>12): For Enterprise sites, an additional on-site vSZ-D will be deployed at the remote site which will assume the responsibilities of performing DHCP/NAT functions. Therefore, DHCP/NAT service will not be running on any APs (they will serve clients only), while the DHCP/NAT services are provided by the onsite vSZ-D.

Login to the vSZ and Navigate to Services and Profiles then DHCP & NAT. Locate the domain under the organisation pane, then expand the required domain and highlight the zone you wish to configure your DHCP service. There will be an option to Enable DHCP Service. Enable this, to be directed through a configuration wizard.

Select the appropriate Base Settings. The options are Single AP (1), Multiple APs (<12), or Hierarchal APs (>12). For the purpose of this KB we will only be looking at Single AP or Multiple AP scenarios as Hierarchal will require a data plane. Click Next to continue.

Create a DHCP Pool by clicking on the +. A new page will pop up. Simply enter the required information and click OK. Repeat more networks if necessary. Once done, highlight and move the Pools from Available Pools to Selected Pools and click Next to continue.

On the next page, select your Gateway AP(s). The options are either Automatic or Manual. If you are selecting Manual, you will need to move AP(s) similar to moving the Pool(s) in the previous step and select a Primary and Secondary AP. Click Next to continue.

Review your configuration and click OK to confirm.

Configure your WLANs now as you normally would, however, ensure that under Advanced Options that your Access VLAN is set as per your DHCP profile. 

Perform testing to ensure all is working as expected.

To prevent the two network users from being able to communicate with one another you must now create L3 Access Control profile(s). This will look something like the following:

Action: Block

Source Network Address/Subnet Mask 

Destination Network Address/Subnet Mask

So for example, if we want to block communication between our Private and Guest wireless networks we will need to create two rules and affix these to the respective WLAN.

Block Guest on Private

Action: Block

Source 192.168.66.0/24

Destination 192.168.99.0/24

Block Private on Guest

Action: Block

Source 192.168.99.0/24

Destination 192.168.66.0/24

Navigate to Firewall then L3 Access Control, highlight the appropriate domain then click Create. A new page will pop up. Provide a Name and Description and create a rule by clicking Create. Add a Description, under Access select Block from the drop-down. Enter the Source and Destination Network Address and Subnet Mask. Set the Direction to Dual. Create profiles for any necessary networks.

Apply these to your WLANs by navigating to Wireless LANs, highlight and configure your WLAN, scroll down to Firewall and select the tickbox for Enable WLAN specific. Under the L3 Access Control Policy use the dropdown to select the appropriate profile. Repeat for all necessary WLANs.

Perform testing to ensure all is working as expected.

Notes

Some clients do not roam even if they are physically moved to a new location. Not all clients have roaming aggressiveness setting to fine-tune roaming. Apple devices are reported to cling to the AP they first learn an SSID on.

In a multi-AP environment, a client will always be looking for the best AP to connect to. It will remain connected to its current AP and roam to an adjacent AP once the signal level falls below a certain threshold. This behavior ensures best possible performance at all times.

To achieve this, a client must be doing background scanning to learn about its environment. Frequency of this background scan can determine the roaming behavior. Certain clients such as Windows clients allow roaming aggressiveness to be tweaked. "High" setting will make the client to perform background scanning more often to learn about available APs to connect. While the "Low" setting will make the client do less frequent scanning. This setting can be found under the wireless adapter properties.

Unfortunately, this tweaking is not readily available for all client types. For example, various smartphones and Apple clients do not provide this setting to encourage roaming.

For these types of clients, it is obvious to look towards infrastructure for help. Ruckus has added firmware support to disconnect a client if its signal falls below the user-definable threshold. This feature is called SmartRoam. With this feature, there will be an explicit disassociate message to kick off the client.

This is a per-SSID setting as illustrated above. "smart-roam" parameter takes values from 1 to 10.
These are called roam factors, and they map to an RSSI value in dB as per the list below:

The configuration can be changed from the CLI of the SmartZone.

config
domain "Domain Name"
zone "Zone Name"
wlan "WLAN Name"
roam
roam-factor 2.4g x
roam
roam-factor 5g x

Red writing indicates a value that will be unique to your configuration. Note also that the quotes are required for parameters within a partner domain.

Additionally, if you enable DB Persistence event 209/218 on the vSZ you can see the system logs (events) for roaming activity.

Some clients do not roam even if they are physically moved to a new location. Not all clients have roaming aggressiveness setting to fine-tune roaming. Apple devices are reported to cling to the AP they first learn an SSID on.

In a multi-AP environment, a client will always be looking for the best AP to connect to. It will remain connected to its current AP and roam to an adjacent AP once the signal level falls below a certain threshold. This behavior ensures best possible performance at all times.

To achieve this, a client must be doing background scanning to learn about its environment. Frequency of this background scan can determine the roaming behavior. Certain clients such as Windows clients allow roaming aggressiveness to be tweaked. "High" setting will make the client to perform background scanning more often to learn about available APs to connect. While the "Low" setting will make the client do less frequent scanning. This setting can be found under the wireless adapter properties.

Unfortunately, this tweaking is not readily available for all client types. For example, various smartphones and Apple clients do not provide this setting to encourage roaming.

For these types of clients, it is obvious to look towards infrastructure for help. Ruckus has added firmware support to disconnect a client if its signal falls below the user-definable threshold. This feature is called SmartRoam. With this feature, there will be an explicit disassociate message to kick off the client.

This is a per-SSID setting as illustrated above. "smart-roam" parameter takes values from 1 to 10.
These are called roam factors, and they map to an RSSI value in dB as per the list below:

The configuration can be changed from the CLI of the SmartZone.

config
domain "Domain Name"
zone "Zone Name"
wlan "WLAN Name"
roam
roam-factor 2.4g x
roam
roam-factor 5g x

Red writing indicates a value that will be unique to your configuration. Note also that the quotes are required for parameters within a partner domain.

x Defines the roam factor in the table above i.e. 1-10.

Remember to ensure configuration is saved.

Additionally, if you enable DB Persistence event 209/218 on the vSZ you can see the system logs (events) for roaming activity.

RUCKUS Analytics is a cloud service for network intelligence and service assurance. Powered by machine learning and artificial intelligence, it gives IT comprehensive visibility into network operations. The service accelerates troubleshooting and helps IT teams meet their network SLAs. RUCKUS Analytics delivers powerful incident analytics, network health monitoring, advanced client troubleshooting and more. 

This guide will help you create a Resource Group, then Invite a 3rd Party to manage said group.

You can provide Role-Based Access Control (RBAC) to allow an administrator to manage APs and switches organized into resource groups.

A resource group is made up of your selection of APs and switches available in RUCKUS Analytics. There are many roles associated with resource groups with specific functional privileges. The roles available are Admin, Network Admin and Reporting. A resource group allows the Admin to confine access for a group of users to a restricted set of APs and switches. Therefore, a resource group is equivalent to a tenant.

RUCKUS Analytics contains a Default resource group. This group corresponds to the entire set of Wi-Fi assets. The Default resource group cannot be edited or deleted.

1. To create a resource group of APs and switches, from the web interface, go to Admin > Resource Groups. The Resource Groups page is displayed.
2. Click Create Resource Group.
   The Create Resource Group page is displayed.
   Configure the following options:
   • Name: Enter the name of the resource group that you are want to create. In this case, use the Customer Company Name
   • Description: Enter a short description about the group for reference.
   • Click the AP radio button and Switch radio button to view the devices within the network and domains. Choose the devices that you want by selecting the check-boxes, and click Create. The resource group with the selected APs and switches is created and displayed in the Resource Group page.

You can add registered users, assign roles to the users, associate them to resource groups, and manage users from the RUCKUS Analytics web interface.

1. From the web interface, go to Admin > Users.
2. Add third-party users by clicking Invite 3rd Party.

   A third-party user is a user who does not belong to your organization. By inviting a third-party user, you are explicitly granting access to someone outside your organization to the RUCKUS Analytics service account. Ensure that you have the necessary authorization to do so. A third-party user or a partner can only access a single resource group as defined by the administrator.

   
   

   Note: If the Admin role is granted, the third-party user will also be able to invite other users into your account. If this is not desired, you can grant the third-party user a Network Admin or Report Only role. Network Admin is the preferred role for most deployments.

   
   
   The Invite 3rd Party dialog box is displayed where you can search for the user by their email ID. After typing the email ID, click Find. Select the specific Resource Group and Role that you want the third-party user to be associated with and click Invite. Network Admin is the preferred role for most deployments.

   
   

   Note: The user must have a valid email ID that is registered with RUCKUS support. Else, the third-party account will be rendered invalid.

   
   

   Information relevant to the invitee is displayed in the Users page. The user can accept or reject the invitation; the status of which is also displayed on this page as Accepted, Rejected or Pending. The user must also have a registered RUCKUS Analytics account to accept the invitation. Additionally, only users having their own account with RUCKUS Analytics can accept invitations. Else, they will not be granted permission to access the application. If the user wants to use another account to accept invitations, then the new account has to be added and registered with RUCKUS Analytics before the user can accept invitation from that account.
3. Partners or third party users who are invited to manage multiple customer accounts can take advantage of single sign-on by clicking on Accounts in the profile icon (top right). Partners can conveniently switch account views without having to re-login.