Ruckus IoT controller DHCP Option Question

[ali_db0udsohr2q]

So I understand how the Option 43 works well for the VSZ and ZD.  However for the IoT controller documentation seems to be a bit confusing.  It says that the IoT controller uses option 43 and suboption 21.  I have tried a few different scenarios but no luck. 

[ali_db0udsohr2q]

Thank you so I have started iot service on the AP by "iotg start" and it shows the MQTT broker IP as vriot.ruckuswireless.com

I am using a Meraki device as a DHCP and I have simply specified Option 43 and then Option 21 with the IP of the IoT controller now as apposed to using the full HEX values previously for VSZ and IoT controller but same results.

Also looks like every time AP reboots we have to restart the iot service with "iotg start" command?

[ali_db0udsohr2q]

Here is a DHCP discover from the 730.  I don't even see it requesting 21.

[kinga_danie]

On vSZ group DPSK provides the dynamic vlan with the PSK being the "authentication" mechanism. No need for radius and easy support for headless devices Speed Test Scrabble Word Finder Solitaire

[krzysztof_bedna]

Does anyone figured it out? I saw https://www.youtube.com/watch?v=Cwnj9mKcaFo I read https://forums.ruckuswireless.com/ruckuswireless/topics/handy_tool_dhcp_option_43_builder and I know https://shimi.net/services/opt43/ but it doesn't work in any configuration.

[michael_brado]

Hello,

   I asked our IoT Experts "How does a customer configure option 21 in ASCII mode, which differs from option 43 for SZ/ZD controllers?"

Answer:
It can be added to the initial hex string for VSZ discovery. I did this a while back when I was doing discovery testing.

 

 

#Begin

Use the calculator below to grab the SZ IP in Hex

https://shimi.net/services/opt43/

Use it again with the vRiot IP then change the 06 at the beginning to 15 which is 21's Decimal Hex Value. 

Option 22 will begin with 16 which is 22’s Hex Value. With the length of the VLAN ID next then the VLAN ID in Hexadecimal converted from string format 

Here is my working ICX Config:

ipdhcp-server pool test

 dhcp-default-router10.50.0.1 

 dns-server8.8.8.8 

 lease0 0 5

 network10.50.0.0 255.255.255.0

 option  43hex 060b31302e37302e31302e3234150b31302e37302e31302e32351603323030

 deploy                                                        

!

SubCode /Length/ (Value In Hex)

06 0b 31302e37302e31302e3234- 10.70.10.24

150b 31302e37302e31302e3235 - 10.70.10.25

16 03 323030- VLAN 200

rkscli:get scg ip

 

------SCG Information ------

SCGService is enabled.

APis not managed by SCG.

State:DISCONNECTED

ServerList: Not found

NoSSH tunnel exists

FailoverList: Not found

FailoverMax Retry: 2

DHCPOpt43 Code: 6

ServerList from DHCP (Opt43/Opt52): 10.70.10.24

SCGdefault URL: RuckusController

SCGconfig|heartbeat intervals: 300|30

SCGgwloss|serverloss timeouts: 1800|7200

-----------------------------

OK

rkscli:get iotg-mqtt-brokerip

10.70.10.25

OK

rkscli:get iotg-ip-vlan

VLANStatus    : Enabled on WAN

VLANInterface : br0.200

IPAddress     : (dynamic, vlan 200), IP: 0.0.0.0, Mask:0.0.0.0

OK