topic r310 and VSZ AP detection in SmartZone and Virtual SmartZone

r310 and VSZ AP detection

xxfisherxx — Tue, 14 Jan 2025 23:23:22 GMT

I followed all of the steps for the first AP in the education video and cant see my AP in the staging area inside of virtual smartzone like in video, is there a setting inside of VSZ that I'm missing. also is there an easier way to deploy, detect and configure as I have 50+ to do and this seems not very efficient

Re: r310 and VSZ AP detection

James — Wed, 15 Jan 2025 09:28:21 GMT

Hello,

I understand your R310 AP is detected by the vSZ controller. Please check/ provide the following details.

> Are you using a vSZ-Essential (vSZ-E) or vSZ-High Scale (vSZ-H) ?

>What is the current firmware on the AP, and that on the SmartZone?

>If you are using vSZ-E, what is the firmware on the default AP zone ?

>Please confirm if you have sufficient AP capacity licenses available on the vSZ.

DHCP option 43 sub opt 06 can be used to provide the controller's IP to the AP.

The controller's ip address should be configured under DHCP opt 43 sub opt 06 in hex form. Please use the below link to covert decimal IP address to hex form.

http://shimi.net/services/opt43/index.php

Re: r310 and VSZ AP detection

xxfisherxx — Wed, 15 Jan 2025 14:44:17 GMT

the r310 AP is not detected by our Vsz high scale running 6.1.2.0.441 and the Aps are running 6.1.2.0.1309 we have plenty of licenses 🙄 already setup dhcp option 43 on the sonic wall and I get nothing in Vsz

Re: r310 and VSZ AP detection

James — Wed, 15 Jan 2025 16:52:52 GMT

Please check output for the following commands from the R310

get scg

get rpki-cert issuer

get ntp

Please make sure SSH is allowed between the AP's network to the vSZ controller.

Re: r310 and VSZ AP detection

xxfisherxx — Wed, 15 Jan 2025 18:03:24 GMT

rkscli: get scg

------ SCG Information ------
SCG Service is enabled.
AP is not managed by SCG.
State: CONN_GET_ADDR_STATE
Server List: I've ommitted this
No SSH tunnel exists
Failover List: Not found
Failover Max Retry: 2
DHCP Opt43 Code: 6
Server List from DHCP (Opt43/Opt52): Not found
SCG default URL: RuckusController
SCG config|heartbeat intervals: 30|30
SCG gwloss|serverloss timeouts: 1800|7200
Controller Cert Validation : disable
-----------------------------
OK
rkscli: get rpki-cert issuer
Issuer: RuckusPKI-DeviceSubCA-2
OK
rkscli: get ntp
Device GMT time : Tue May 11 06:47:35 2021
Active NTP Server : ntp.ruckuswireless.com
Backup NTP Server : ntp.ruckuswireless.com
NTP Sync Interval : 60 minutes
NTP enabled: yes
OK
rkscli:

ssh is enabled

Re: r310 and VSZ AP detection

James — Thu, 16 Jan 2025 07:51:31 GMT

The AP - SCG connectivity state shows "State: CONN_GET_ADDR_STATE"

This state usually points to insufficient licenses on the controller. Reference article: https://support.ruckuswireless.com/articles/000011007

But since you've mentioned that there are ample licenses on the controller, that might not be the issue.

I also see that the AP's time is incorrect: Device GMT time : Tue May 11 06:47:35 2021

Please run the command "set ntp update" on the AP and again run "get ntp" to validate if the correct time is seen. See if the controller joins after this.

Re: r310 and VSZ AP detection

xxfisherxx — Thu, 16 Jan 2025 14:41:57 GMT

so I was able to get the aps to join but not using dhcp option 43 as I hoped I want to just connect the new Aps and and have them detected in the staging area however none have showed up in the staging area initially instead they show up in the production zone and I have to configure each AP individually

Re: r310 and VSZ AP detection

James — Fri, 17 Jan 2025 10:13:27 GMT

If the APs are automatically joining a specific AP zone, then its likely that AP registration rules are configured on the controller, or the AP's entry is already present on a certain AP zone. Navigate to Network > AP settings > AP registration to see if there are any rules in place. By default any new AP joining a vSZ-H will come into the staging zone.