topic Re: Ruckus IoT controller DHCP Option Question in Access Points - Indoor and Outdoor

Ruckus IoT controller DHCP Option Question

ali_db0udsohr2q — Tue, 14 May 2019 22:48:32 GMT

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.

Re: Ruckus IoT controller DHCP Option Question

michael_brado — Wed, 15 May 2019 18:29:42 GMT

Hi Ali,
   The IoT Getting Started Guide says DHCP Option 43 is used to direct APs to the controller.
https://support.ruckuswireless.com/documents/2460-ruckus-iot-suite-getting-started-guide-gsg

    We have a number of knowledge base articles on how to configure DHCP option 43 on different
server platforms.
https://support.ruckuswireless.com/articles?article_id=&query=option+43

    I hope this is helpful.

Re: Ruckus IoT controller DHCP Option Question

ali_db0udsohr2q — Wed, 15 May 2019 19:47:12 GMT

Thank you Michael, so I already know how to configure DHCP Option 43 and no issues there. I'm having some trouble with the DHCP Option 43 with Sub Option 21 for IoT controller.
Normally Option 43 would be:
06:XX = Length of the IP:Rest of the Hex
Where 06 is the Sub Option

Now if I have to do the same for VSZ and IoT what would be the format? Would it be something like below?

06:XX:Rest of the Hex:15:XX:Rest of the Hex

06 = Suboption for VSZ
XX = Length of the IP

Re: Ruckus IoT controller DHCP Option Question

michael_brado — Thu, 16 May 2019 23:09:31 GMT

Sub option 21 (hex 15) holds the IoT Controller IP address in ASCII mode. This value is used (if IoT Service is started on the AP) to connect to IoT Controller.

It starts with length of the value, followed by the value (exactly the same way, how the sub options 3 and 6 is configured on the DHCP server).

Re: Ruckus IoT controller DHCP Option Question

ali_db0udsohr2q — Fri, 17 May 2019 17:40:49 GMT

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?

Re: Ruckus IoT controller DHCP Option Question

ali_db0udsohr2q — Fri, 17 May 2019 19:20:04 GMT

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

Re: Ruckus IoT controller DHCP Option Question

kinga_danie — Thu, 23 May 2019 21:42:29 GMT

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

Re: Ruckus IoT controller DHCP Option Question

ali_db0udsohr2q — Wed, 29 May 2019 17:55:40 GMT

I have tried this on multiple devices Meraki Firewall DHCP and Cisco ios DHCP using IP and HEX multiple combinations and nothing works. Even if I manually start the service on the access point (which I shouldn't have to because that does not make sense, if I am deploying 100 AP's I will have to log into each AP and start the service?) it goes to the default server vriot.ruckuswireless.com

Links you suggested all talk about really DHCP Option 43 with ZD or SCG config and that part I already works.

Question is, how to add the DHCP sub option 21 so this works? Still testing and trying to find an asnwer

Thank you.

Re: Ruckus IoT controller DHCP Option Question

krzysztof_bedna — Fri, 08 Nov 2019 16:43:22 GMT

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.

Re: Ruckus IoT controller DHCP Option Question

michael_brado — Fri, 08 Nov 2019 18:41:45 GMT

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

Re: Ruckus IoT controller DHCP Option Question

krzysztof_bedna — Wed, 13 Nov 2019 12:21:13 GMT

Thank you, @ Michael Brado
your method works*. As I said before, I know site https://shimi.net/services/opt43/ but when you try to generate code for 2 controllers it gaves you hex string separated by "2c". In tutorial https://youtu.be/Cwnj9mKcaFo it wasn't explained, that you have to replace excatly this part with "15". Actually, they called it "sub-code" which is a little bit confusing.

*It works on Windows Server DHCP, but on Palo Alto Networks firewall - no.

Re: Ruckus IoT controller DHCP Option Question

ali_db0udsohr2q — Wed, 13 Nov 2019 12:32:52 GMT

See if this helps ya, it is a work in progress.

http://dot11ali.com/2017/08/31/ruckus-dhcp-option-43/