Dear Ruckus users,
I've been working on a vSZ deployment for a while late last year and got it working with a testAP and was very impressed. Now, we've got some projects that will finally utilize our cloud-connected vSZ. However, I cannot seem to get any AP connected anymore. When testing, I did not stick to the rule of documenting everything, so I forgot how I managed to connect an Ruckus AP to our cloudconnected vSZ.
This week I've been searching the net for an answer, but either my AP is bugging out of on me (new R500) or the "guides" are far from complete.
This situation is the following:- vSZ hosted on a vmware platform in the cloud
- vSZ is behind a firewall, but I've opened all necessary ports.
- vSZ was unchanged from our testing period until last night. Last night I decided to upgrade from 3.1.1 to 3.2.1 (patch 3) to try that out.
- AP's are behind a NAT router.
- I've tried firmware versions 9.8.x, 200.x (unleashed, yay!) and 100.1. Currently the AP's are on 100.1
What have i tried:
- Rebooting the vSZ
- Upgrading the vSZ to 3.2.1 to be able to create a GRE tunnel (Ruckus GRE tunnel did not show up in 3.1.1)
- set discovery agent enable
- lwapp2scg > policy accept-all
- DHCP option 43 (which is a bitch on Sonicwall due to Hex config)
- DNS entries for zonedirector.ruckus.local && ruckuscontroller.ruckus.local (if i remember the entry correctly)
- Tried from several different networks
- tried set scg ip
Command is not accepted in 100.1 I remember it working last year, after which I saw the AP showing up on the vSZ shortly after.
- tried set director ip
a million times. Until last nights vSZ update it showed the ip (in get director command) as primary, but said the AP was still standalone. After last nights update the AP now shows the following after that command: Warning: AP is in ZoneDirector-Managed mode Current or latest ZoneDirector: 0.0.0.0 / 00:00:00:00:00:00 Any configuration changes made in CLI may conflict with the ZoneDirector's management and will cause undefined results.rkscli: get director------ ZoneDirector Info ------Primary Controller : Secondary Controller : n/aDHCP Opt43 Code : 3The information of the most recent Zone Director:No info AP is under management of ZoneDirector: 0.0.0.0 / 00:00:00:00:00:00, Currently AP is in state: IMAGEOKrkscli:
This morning I set the AP back to factory defaults and started monitoring the network traffic in the firewall, but the packet inspection is kinda basic in the web gui. I could see a lot of DNS requests. After setting the director and rebooting, i saw DNS traffic, LWAPP broadcast in the local domain and after a minute or so i started contacting the vSZ on ports 23233 and after that a lot of FTP traffic back and forth. However, 2 hours later the AP still didn't show up on the vSZ and contacting the AP through SSH still shows the above error.
To me it seems that the AP is clueless where to actually contact the director. I really have no idea any more what to do. I've spent countless hours on troubleshooting this. Anyone who has an idea on how to move forward? Can anyone confirm 100.1.x is even the right SW version for the AP?
EDIT: some of the links i've used:https://forums.ruckuswireless.com/ruckuswireless/topics/connection-between-ap-and-vszhttps://forums.ruckuswireless.com/ruckuswireless/topics/r710-ap-image-for-vsz-carrierhttps://forums.ruckuswireless.com/ruckuswireless/topics/activating-aps-outside-vszs-networkhttps://support.ruckuswireless.com/answers/000001255https://samepage.io/app/#!/4de82f7f008f3cb343977023611036ed552a71ca/page-260569444487667766-how-to-a...http://www.adnsolutions.com/troubleshoot-ruckus-ap-not-connecting-to-virtual-smartzone-cloud-control...