Ruckus VSZ Unable to find new R510 AP
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2018 05:37 AM
I am running VSZ version 3.4.0.0.976. I have currently 21 AP. I purchased 5 AP and configured 4 of them without an issue, when setting up the last one it is not showing up in the vSZ.
Everything has been done over the same physical port with no configuration changes. I am able to ping the VSZ from the AP. The AP is running firmware 110.0.0.0.663. Currently i have 1 license free of 21 in the vSZ. I have tried resetting and reconfiguring the AP from CLI over SSH and over the browser. Any ideas what else to try?
I have attached the picture of my VSZ licenseses.
Everything has been done over the same physical port with no configuration changes. I am able to ping the VSZ from the AP. The AP is running firmware 110.0.0.0.663. Currently i have 1 license free of 21 in the vSZ. I have tried resetting and reconfiguring the AP from CLI over SSH and over the browser. Any ideas what else to try?
I have attached the picture of my VSZ licenseses.
18 REPLIES 18
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2018 05:18 AM
Hi Jako,
this could be a HW problem with the AP. Could you please log a case to Ruckus Support? We need to troubleshoot this in deeper detail.
There seems to be a problem when creating the ssh tunnel:
Oct 10 11:36:34 RuckusAP daemon.err wsgclient[707]: curl_https_request:1060 curl _easy_perform failed:[35][SSL connect error].
Thanks.
David.
this could be a HW problem with the AP. Could you please log a case to Ruckus Support? We need to troubleshoot this in deeper detail.
There seems to be a problem when creating the ssh tunnel:
Oct 10 11:36:34 RuckusAP daemon.err wsgclient[707]: curl_https_request:1060 curl _easy_perform failed:[35][SSL connect error].
Thanks.
David.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2018 03:11 AM
Hi all,
got a completely new device from factory as replacement, same issue. The last device tested in another enviornment worked fine so the issue must be with the management. Thing is it stopped working after 20 licenses were consumed, maybe its related? Even tho i have 1 AP license free so it is extremely confusing.
got a completely new device from factory as replacement, same issue. The last device tested in another enviornment worked fine so the issue must be with the management. Thing is it stopped working after 20 licenses were consumed, maybe its related? Even tho i have 1 AP license free so it is extremely confusing.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2018 03:43 AM
Hi,
as a conclusion i was able to get the device to the management console. I had to downgrade the AP firmware from 110 to 104.xx and after that it was accepted from the management.
as a conclusion i was able to get the device to the management console. I had to downgrade the AP firmware from 110 to 104.xx and after that it was accepted from the management.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2018 04:15 PM
Thanks for sharing your solution!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2019 11:16 AM
Thank you for sharing I had the same exact problem. VSZ 3.4.1.0.208 however it's not VSZ fault just sharing for reference. It's the APs firmware! After troubleshooting DHCP options, trying to set controller IP manually, and looking at logs I found that SSL error.
It was the AP 510's firmware version "110.0.0.0.663" which has a bug or something. As I also got the SSL error. This was on SIX 510's with the same exact firmware. Downgrade worked for ALL SIX! So not random
"Jan 4 17:45:28 RuckusAP daemon.err wsgclient[716]: curl_https_request:1060 curl_easy_perform failed:[35][SSL connect error]. "
I downgraded from "110.0.0.0.663" to "104.0.0.0.1347" For anyone else experiencing this problem. I can't say for sure if other models have this problem with 110 firmware however the 510 for sure do. As OP and I had 510's. I had SIX 510s doing the same exact thing as shown in the logs.
THANK YOU FOR SHARING!
It was the AP 510's firmware version "110.0.0.0.663" which has a bug or something. As I also got the SSL error. This was on SIX 510's with the same exact firmware. Downgrade worked for ALL SIX! So not random
"Jan 4 17:45:28 RuckusAP daemon.err wsgclient[716]: curl_https_request:1060 curl_easy_perform failed:[35][SSL connect error]. "
I downgraded from "110.0.0.0.663" to "104.0.0.0.1347" For anyone else experiencing this problem. I can't say for sure if other models have this problem with 110 firmware however the 510 for sure do. As OP and I had 510's. I had SIX 510s doing the same exact thing as shown in the logs.
THANK YOU FOR SHARING!

