cancel
Showing results for 
Search instead for 
Did you mean: 

SmartZone 100 (SZ104) - Discovering Multiple APs

rajivw
New Contributor III

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. 

1 ACCEPTED SOLUTION

DarrelRhodes
Valued Contributor

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

20 REPLIES 20

rajivw
New Contributor III

@abilashpr

You mean untag the LAG? (Each Fibre Core SW has a port in a LAG to Access Switches eg: 1/1/1 & 2/1/1 in LAG 2 to Floor 2). These LAGs carry multiple VLANs, so I tagged them.

I will try out the enable command for DHCP tomorrow and let you know. I didn't see that in the guide. Also will share the Access SW config tomorrow if this doesn't work. Thanks in advance. 

Dear @rajivw,

Tags are solid, in the above configuration you shared dhcp is not enabled, running "ip dhcp-server enable" would enable core switch to handover DHCP to APs (VLAN 40).

Regards,

Abilash PR

rajivw
New Contributor III

Hi @abilashpr 

It worked! Thank you so much 🙂

APs are now in the WLC. However, there's a 30-second disconnection continuously occurring. They come online and go offline. Also I'm unable to see the APs broadcasting the SSIDs (I've turned on the radios).

Image_ images_messages_61558e97c70d09623cfbd111_45455543eb4971087fb3fe60692031c4_Ap2-0077a7c5-7745-47d8-9bd5-407aba21a8bb-812287838.PNG
Any idea why?

Dear @rajivw ,

Please to ssh into one of the AP try to ping the gateway of the AP and the controller, to see if there is any connectivity issues. 

Regarding APs not broadcasting please ssh into AP and run "show wlanlist", you will able to see if the SSIDs are being broadcasted or not.

Regards,

Abilash PR.

rajivw
New Contributor III

Abilash, this was resolved. Thanks again for the continuous support.