nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Activating APs outside vSZ's network

unknown

How can I activate/connect my new APs (R710 and T300) to my vSZ (hosted with GCE)?

Have in mind that these are brand new unregistered APs and they will be operating outside the vSZ's cloud network.

Find more posts tagged with

Accepted answers

All comments

unknown

Either you pre-prepare the APs by feeding the vSZ IP to each unit manually, or you create a DHCP option in the scope of the remote location where the APs will be installed

unknown

How do I pre-prepare the APs, how do I feed them config parameters such as the vSZ IPs?

Is there a Ruckus guide for this?

What would be the more scalable option (AP IP feeding vs DHCP) considering that I will always be deploying APs outside of the controller's (vSZ) network?

Thank you!

unknown

I use DNS discovery for our APs deployed on customer sites. I use an A record pointing zonedirector.localdomain to the external IP of the vSZ. As long as you have the ports open on vSZ site the AP will end up in staging zone. I recommend reading the administrator manual for the vSZ. It describes all this. There are also documents on the support portal where you can find all the necesary ports that you will need to open so your external AP:s can communicate with your vSZ.

unknown

Hi Niklas, do you know the name of the support material on port opening for AP communication.

unknown

Niklas, by DNS discovery for APs, are you referring to "Method 3: Register the Controller with the

DNS Server" on the "vSZ Getting Started Guide for Release 3.2"?

unknown

I was able to create A records for both RuckusController and zonedirector pointing to the vSZ controller's static IP, what's next?

unknown

Where do I open the DHCP configuration file ? Is this for the controller or the AP?

unknown

If you use DNS you dont have to configure DHCP. You can either use DHCP or DNS. After you have the A-record pointing towards the vSZ you need to open all the relevant ports on the vSZ side. Chapter 8 in this document describes what you need to know : vscg-3-2-1-getting-started-guide-final. I also found the ports needed in this document: vscg-3-0-3-carrier-administrator-guide on page 395. It is an old document but those where the ones i used when I installed our vSZ.

unknown

Got it, but how/where do I tell my APs to look for RuckusController.mydomain.com and zonedirector.mydomain.com?