Thank you so does it still have any value even without a license?  Also is there a config wipe feature or if I simply do a factory reset and remove it from under my organization it is all wiped? ... View more

It actually shows the HEX value I have specified and the two IP addresses but I don't see Option 21 in there even though I have have added it in the HEX as 15 with the Length of 0A.   ... View more

Here is the offer, don't see 21 in there either, there is a disconnect some where, another weird thing is I have to manually start the service in the AP and when I do it looks for the default server just like in Cisco AP.   So here is what I am thinking: 1- Since the service is not starting automatically it is possible that is why I am not seeing Sub option 21 in there. 2- Or AP doesn't request Sub option 21 but it needs to be part of Option 43 in Hex like I had it before perhaps.  Still working on it will update more later.  This has been so weird.   ... View more

So I don't see the AP requesting 21 in Discover, nor do I see it in the Response. ... View more

Tried that and same results.  Also I got a response from Ruckus that sub option 21 would hold the IoT controller IP in ASCII mode.  So in Meraki DHCP I simply just added another custom code and entered 21 there and then the IP of the IoT controller.  Am I missing a step? ... View more

So yes there is ZD that uses sub option 03 and VSZ that uses sub option 06.  In my case I am using 06 (VSZ).    Correct two different IP's and per their documentation IoT controller is option 21 (Hex Length = 15).   So here is what I added in Meraki:   06:0A:AA:BB:CC:DD:EE:FF:GG:HH:ZZ:ZZ:2C:15:0A:XX:YY:ZZ:XX:YY:ZZ:XX:YY:ZZ:AA   06 = VSZ sub option they need 0A = Length of the IP next 2C = for the , 15 = Sub option 21 0A = Length o fthe IP Rest is the actual IP   Do you think I need to take out that comma (2C)?  I can try it yeah pcap is the next step I was looking to do as soon as I get a chance. ... View more

Thanks again for the reply, so that is actually me in that post asking about the calculation Ruckus uses.  Based on how Ruckus does it I actually already have a template that converts all that.  15 in this case was the hex for 21 actual length of the IP was 21 because there are two IP's that are involved.  VSZ IP and IoT controller IP.  Just like with Cisco WLC if there are two WLC IP's there is a specific hex code to specify that.   So in summary trying to figure out how best those two IP's will go in Meraki DHCP. ... View more

Thank you @BrechtSchamp yes I saw that website good read.  So I have no issues converting the two IP's to Hex.  I actually created an excel template that will do it.     I'm not sure if the format I'm using in Meraki is correct or not as it is still not working.  Please see below: (Yes Ruckus IoT) 06:15:IP-IN-HEX-HERE:2c:15:IP-IN-HEX-HERE   06 = For VSZ 15 Length of IP All in bold = VXZ IP in hex 2c = , 15 = Sub option 21 in Hex All in bold = IoT controller IP in Hex   I think I may be missing something here still.   ... View more

Thank you @kYutobi , yes I did see that but that doesn't apply to my situation. ... View more