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-09-2018 05:47 AM
is the vSZ-E or H deployement. If H deployement you need to take a look at the staging zone. If it's an E deployement you should see the AP's where you need to approve them before they will join
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2018 05:48 AM
Hi,
it is an H enviornment. The thing is the AP does not appear in the list where i should approve it. That is the problem i am having. It seems it is not getting connected to the VSZ-H
it is an H enviornment. The thing is the AP does not appear in the list where i should approve it. That is the problem i am having. It seems it is not getting connected to the VSZ-H
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2018 05:56 AM
make sure it is connected to the same subnet. just to test it. Otherwise set the ip adres of your vSZ via SSH by typing: set scg ip and reboot the ap. this may force a tunnel to the controller
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2018 05:56 AM
Hi Jako,
have you tried factory resetting the AP?
Thanks.
David.
have you tried factory resetting the AP?
Thanks.
David.

