Building a Converged IoT Access Network

RUCKUS has developed the RUCKUS IoT Suite to enable a secure IoT access network. The following figure shows the various components that comprise the RUCKUS IoT Suite. The following steps provide a brief introduction to each component, and prerequisites to be considered before installing the components on the network.

Figure 1. RUCKUS IoT Overview

Step 1: Installing a RUCKUS IoT Controller

The RUCKUS IoT Controller is a virtual controller that integrates with the SmartZone Controller to perform connectivity, device, and security management functions for non-Wi-Fi devices. The RUCKUS IoT Controller can be installed on the three hypervisors described in the following table.

Table 1. Supported Hypervisors
Hypervisor Vendor Version
ESXi VMware 6.0 and later
VM Virtual Box Oracle 5.1.20 and later
VM Player VMware 12 or later
KVM Linux 2.11.1 or later

Before you begin installing the RUCKUS IoT Controlleron any hypervisor, consider the following prerequisites:

  • Ports 80, 123 or NTP, 443, 1883, and 8883 must be open.
  • The virtual machine (VM) on which the RUCKUS IoT Controller is installed must have a minimum of 4 vCPUs, 4 GB RAM, and Fixed 20 GB HDD.
Note: RUCKUS recommends a minimum of 8 vCPUs and 8 GB RAM for the RUCKUS IoT Controller.

For information on how to install the RUCKUS IoT Controller, refer to the RUCKUS IoT Controller Installation Guide.

Step 2: Deploying RUCKUS Access Points and Ensuring Discovery of Controllers

Using the Dynamic Host Configuration Protocol (DHCP) Option 43 method, deploy RUCKUS Access Points (APs) and ensure discovery of the WLAN Controller and, subsequently, of the RUCKUS IoT Controller.

The IoT Access Point supports Option 43 with the following suboptions:

  • Suboption 21: Used to configure a RUCKUS IoT Controller IPv4 address or FQDN (mandatory)
  • Suboption 22: Used to set the control VLAN for IoT Control/Data traffic (optional)

Option 43 supports both binary and ASCII formats. The IoT Access Point bootup process checks for Option 43 and suboptions 21 and 22. Once the application receives this information, it uses the information to connect to the RUCKUS IoT Controller over the Pubsub channel.

You can use the DHCP Option 43 sub-option code 06 to set the SCG/vSZ/SZ IP address in the format SubCode /Length/ (Value In Hex). For example : If the IP address is 10.24.123.4, then the hex string is as follows 06 0b 31302e32342e3132332e34.

The DHCP Option 43 sub-option code 21 and 22 is used to set the Ruckus IOT controller IP address.

For Example, Windows DHCP Configuration with Sub-option 21 and 22:
Linux DHCP option 43, sub option 21 configuration is as follows:
  • option RKUS.scg-address "192.168.0.3"
  • option RKUS.riot-address "192.168.0.2";
dhcp_opt43 configuration subopt 22- "vlan_mode.vlan_id"
  • #option RKUS.iotvlan-address "0.4" -enables onlink VLAN
  • #option RKUS.iotvlan-address "1.4" -enables offlink VLAN

• Offlink VLAN configuration is used when the IOT Gateway/AP and IOT controller are in different networks.

• Onlink VLAN configuration is used when the IOT Gateway/AP and IOT controller are in same network.

Step 3: Configuring the RUCKUS IoT Controller and Initializing IoT Services

The RUCKUS IoT APs and devices can be managed using the RUCKUS IoT Controller.

Before you begin configuring RUCKUS IoT Controller services, consider the following prerequisites:

  • The controller must be installed on a hypervisor.
  • The RUCKUS IoT Module must be installed on the RUCKUS AP.
  • The required credentials to log in to the RUCKUS IoT Controller must be secured.

For information on how to configure the RUCKUS IoT Controller, refer to the RUCKUS IoT Controller Configuration Guide.