Using Autodiscovery with ZoneDirector and vSZ on same network

  • 1
  • Question
  • Updated 6 months ago
  • (Edited)
I hope this is an easy question.

I have a mix of older and newer Ruckus equipment on our network.

I want all my new R610 AP's to auto-discover our new vSZ via a ruckuscontroller.domain.local DNS entry.

However, I also have an older ZoneDirector 1100 on another subnet, mostly with 7962 APs.  I don't want any older series APs to accidentally discover and associate with the vSZ.

Am I right to assume that the newer R-series APs look for "ruckuscontroller" as a DNS entry and the older 7962 and similar vintage APs look for "zonedirector" DNS entries for autodiscovery?

We have a large building, and we will be phasing over from ZD to the vSZ gradually and I don't want to have APs going to the wrong controller during the transition.

Thanks!
Photo of NewsFool

NewsFool

  • 25 Posts
  • 1 Reply Like

Posted 6 months ago

  • 1
Photo of Diego Garcia del Rio

Diego Garcia del Rio

  • 27 Posts
  • 6 Reply Likes
any chance you can use the DHCP option path instead of DNS?... or maybe, via DHCP assign a dns prefix to the R610 APs? so that you can then do something like ruckuscontroller.r610.domain.local (where r610 is a subdoain assigned in the dhcp settings)?
Photo of Dionis Taveras

Dionis Taveras

  • 1 Post
  • 2 Reply Likes
You can use DHCP Option 43 suboption 6 for the SZ controller and sub-option 3 for the ZD APs.  This applies to all SmartZone and all ZD APs.  This will make sure that APs that you want going to the ZD go to the ZD by putting the ZD IP on the suboption 3 section while the ip of SZ will be on the suboption 6 section of the dhcp server.  This can be configured in a switch, router, or server such as Linux and windows. 
Photo of Dionis

Dionis, AlphaDog

  • 80 Posts
  • 45 Reply Likes
You can use DHCP Option 43 suboption 6 for the SZ controller and sub-option 3 for the ZD APs.  This applies to all SmartZone and all ZD APs.  This will make sure that APs that you want going to the ZD go to the ZD by putting the ZD IP on the suboption 3 section while the ip of SZ will be on the suboption 6 section of the dhcp server.  This can be configured in a switch, router, or server such as Linux and windows. 
Photo of NewsFool

NewsFool

  • 25 Posts
  • 1 Reply Like
Thanks. It sounds like the DHCP option is the best way to go for this. 
Photo of Monnat Systems

Monnat Systems, AlphaDog

  • 923 Posts
  • 199 Reply Likes
well the most easiest in few steps is to configure your ZD to ensure that AP's only know one ZD IP to connect to whatsoever...in ZD -- configure - AP - limited ZD discoveryjust fill primary ZD IP as your current ZD IP and for secondary as 0.0.0.0
Photo of Monnat Systems

Monnat Systems, AlphaDog

  • 923 Posts
  • 199 Reply Likes
btw your concern is genuine however ZF7962 with ZD code joining Vsz highly improbable as for that event to happen... AP has to be knowing Vsz IP and Vsz software code
Photo of Dionis

Dionis, AlphaDog

  • 79 Posts
  • 45 Reply Likes
It all depends.  If SZ has LWAPP2SCG discovery function turned on, AP will auto join the SZ (Assuming it knows the IP of the SZ either via DHCP option 43 sub 3 or DNS, etc.) and the SZ will auto upgrade the AP to SZ code.  However, if SZ code is 3.6.x, then this AP itself would not be supported.  Any supported AP, running ZD code can be auto upgraded to SZ code by the SZ itself.  All the AP needs is to know the IP and for the SZ to be running the LWAPP2SCG script. Since he wants to run both, old and new APs and have them go to their respective controller, his best bet is to set Option43 sub3 with IP of ZD and Option 43 sub 6 with IP of SZ.  This way, ZD APs go to ZD and SZ APs go to SZ.  This happens automatically and no need for AP or SZ or ZD specific config.