CommScope RUCKUS Community Forums

rajivw · ‎09-20-2021

Planning to deploy 100+ APs in to a SZ cluster (2x SZ104). What's the best way to enable AP discovery by the WLC?

WLC IP is in 172.x.x.x/24 range (MGT). Do the APs have to be in the same range as the WLC to be discovered? If so, how can we enable 172.x.x.x range in all the APs? (Is the only option to use DHCP Option 43?)

All the APs are connected to the Switches and are under VLAN 100 (Untagged - 192.x.x.x DATA range). Will this be an issue for the discovery process, because those are in different subnets?

Also we're using One-port Group Mode (Control+Data traffic). We don't mind using the 192.x.x.x range to manage the WLC as well, because there's no requirement for a separate MGT and DATA planes.

Thanks in Advance.

DarrelRhodes · ‎09-21-2021

Hi Rajiv,

APs and SmartZone do not need to be on the same IP subnet. You will need to configure each SZ in the cluster with a NAT IP, so it can push it's configuration to the APs and they know where to contact it.

This document on our support portal may help: https://support.ruckuswireless.com/documents/1336-smartzone-network-design-with-nat

I've also found a 3rd-party guide which might help: https://wifidevan.wordpress.com/2020/07/27/configure-ruckus-smartzone-behind-nat-to-manage-remote-ap...

In order for APs to discover the SZ(s) when on a different subnet you will need to configure DHCP option 43 or use DNS controller discovery. More info here: https://docs.commscope.com/bundle/ap-110.0-indooruserguide/page/GUID-120D8DDA-3008-45EC-BB67-60B8E87...

DHCP Option 43: https://support.ruckuswireless.com/articles/000008703

The key thing to remember is that the APs discover the SZ (using the methods mentioned above) - the SZ does not discover the APs.

I hope that helps,
Darrel.

View solution in original post

DarrelRhodes · ‎09-23-2021

@rajivw

I don't think changing the IP address of your controller temporarily is a viable solution.

If the APs are not discovering your controller then it could be something else on your network. Can the APs ping the controller IP? Have you rebooted the controller?

If you still don't have any success then I'd recommend raising a ticket with Ruckus support.

Best,
Darrel.

rajivw · ‎09-23-2021

Hi @darrel_rhodes

With the above config I shaded, APs are not getting DHCP leases. Since APs are on the default subnet of 192.168.0.0/24 and the WLC is on 192.168.40.0/24, we used DHCP Op43 on an ICX Switch to lease IPs to the APs.