In this article, I will explain how vRIOT Broker IP can be configured by different ways and some basic to debug the AP-vRIOT connectivity.
Below three ways can be utilised to add APs to the vRIOT :
1) Manual command from RKSCLI. 2) AP CLI Script. 3) DHCP option 43
1) Manual command from CLI :
If we have less or specific APs in a zone to be added to vRIOT one can use manual/static entry to add the vRIOT IP to the APs for connectivity.
Login to the AP CLI via any ssh tool, ex Putty, terminal etc and execute the command:
set iotg-mqtt-brokerip <RUCKUS-IoT-Controller-IP-address>
2) AP CLI Script :
If we have to add all APs of a specific zone to the vRIOT, we can use the CLI command in a script ".txt" format to push it from vSZ to all connected AP per zone , example below can be used :
set iotg-mqtt-brokerip <IOT IP> set iotg-enable 1
*Go to v/SZ WebUI : Diagnostics -> Scripts -> AP CLI Scripts -> upload and execute
3) DHCP option 43 :
The DHCP option 43 suboption code 21 and 22 is used to set the RUCKUS IoT Controller IP address.
• 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 suboption 06, 21 and 22. Once the application receives this information it uses the information to connect to the 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.
For Example, Windows DHCP configuration with suboption 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 offlbnh 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.
AP to vRIOT connectivity :
In some of the scenario where we see AP is not joining the vRIOT or IOT software is not working, we should always validate below :
1) Broker IP Configured :
rkscli#get iotg-mqtt-brokerip Unconfigured OK
*By default Broker IP is set to Unconfigured if controller is not reachable for 24Hours by design. *Having a AP script on SZ as backup for such situation is helpul or manual "set iotg-mqtt-brokerip <IP>" if no DHCP option43 configured.
2) IOT process enabled :
rkscli#get iotg-enable 0
* IOTG Enable/disable command is used for IoT gateway application services 0 means disable and 1 for enable. * Manual command "set-iotg enable 1" to activate the gateway service.
3) 802.11AX APs power mode 802.3at :
rkscli: get power-mode PoE Configured Mode : Auto Power Consumption Status : 802.3af Switch/Injector OK
*All 802.11AX APs need to be 802.3AT POE+ for IOT software to work if the power is not sufficient and AP is running on 802.3AF power mode the IOT module/software would not work and show "USB is not having enough power" *One can go to the zone >> edit >> AP model specific configuration >> Select AP model and choose POE operating mode to AT if auto mode is negotiating at AF. *Manual command "set power-mode at" on each AP CLI or AP CLI script can also be used, Diagnostics >> Scripts >> AP CLI Scripts
4) AP software Matrix :
Not all APs are supported on all vRIOT codes and similarly the vRIOT code compatibility with vSZ code needs to be validated.