Hello till now we were deploying high amount of SZ100 clusters, but recently we are switching to vSZ high scale. We always place SZ or vSZ to same subnet as APs.
With SZ100 AP gets IP from dhcp (no dhcp option 43) and is discovered by the controller without any issue. With vSZ it seems different. We use one interface for all services. but APs by default wont get to the controller.(nothing in logs). I have to use DHCP option 43 Then it is fine. Is there any explanation why it is like that ? I tried to run lwapp2scg didn't help.
Why I am bothered ? We are getting AP hostname from DHCP and it seems to me that it is not 100% working in case where DHCP option is used. I would say about 30% of APs will appear with name "Ruckus AP" and only factory reset+AP reboot+delete from SZ will give you propper AP name taken from DHCP server.
for me either it is sometihng I am missing in vSZ settings or our vSZ Virtual machine doesnt have fully transparent L2 network connectivity.
Yes I am sure, we were deploying SZs from end of 2017 starting with 3.5 and I did it same way even with 3.6, 5.0, 5.1. ( I personally did about 5 clusters of SZ 104 ) Always the same, jut same vlan and subnet, and APs were joining SZ automatically. All kind of AP types(H510,H30,R310,R610,R720,T310,T610) not having a clue about version of FW which they were shipped with. Without any issues it worked without DHCP option.
I had issue with SZ 100 once. In combination with GPON network where mdns packets were dropped by default and it only worked with DHCP option. now I am facing the same issue but without GPON using vSZ.