SZ 100/vSZ H layer 2 discovery differences

  • 1
  • Question
  • Updated 1 month ago
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.

Did someone encountered simmiliar issue ?

Thanks

David
Photo of Support team

Support team

  • 6 Posts
  • 1 Reply Like

Posted 1 month ago

  • 1
Photo of Syamantak Omer

Syamantak Omer, Official Rep

  • 473 Posts
  • 155 Reply Likes
Hi There,

AFAIK vSZ and SZ works the same way and layer-2 discovery was never supported on v/SZ platforms.

Are you sure it was working on SZ100? If yes, what is the SZ100 version and APs were onboarding using what AP standalone version.

Regards,
Syamantak Omer

Photo of Support team

Support team

  • 6 Posts
  • 1 Reply Like
Hello,


Thanks for interest!

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.  

Thanks

David

Photo of Support team

Support team

  • 6 Posts
  • 1 Reply Like
Hello, I tried what you suggested but somehow this command seems to be not working,

vSZ was on 5.1.2.0.302  now I did update to 5.2.0.0.699. and neither discovery or debug command works.



Photo of Syamantak Omer

Syamantak Omer, Official Rep

  • 473 Posts
  • 155 Reply Likes
Hi David,

I have checked this internally and on my lab setup.

AP subnet discovery is supported on both SZ and vSZ. Command is also same and below it the output from my lab setup.


*Click on the image to see in full size.

I would suggest running below command once again.

vsze-60(debug)# ap-subnet-discovery

and then

vsze-60(debug)# show ap-subnet-discovery-status

If still you are facing the issue, please log a case with support with below details.

1- vSZ type (Essential or High Scale) with its version. Output of "show version"
2- Interface type (Single or three interface). Output of "show interface"
3- Output of above commands.
4- If command works but AP L2 discovery still  not working then provide below details as well.
  • AP model(s)
  • AP software version when onboarding APs.
Regards,
Syamantak Omer
Photo of Support team

Support team

  • 6 Posts
  • 1 Reply Like
Hello Syamantak,

I tried on different vSZ we deployed recently and command is not there, might it be difference between vSZ-E and vSZ-H ?
We were told that there is no difference and we should always use High scale.
 
I also tried on 104 without any issue.



Thank you.

David
Photo of Syamantak Omer

Syamantak Omer, Official Rep

  • 473 Posts
  • 155 Reply Likes
Hi David,

I have discussed this internally for vSZ-H and found that AP L2 discovery is not supported on vSZ-H, SZ-200 and SZ-300. Please use DHCP option 43 or DNS for automatic AP controller discovery.

Only vSZ-E and SZ100 supports AP L2 discovery. Same is not support on vSZ-H/SZ-200 and SZ-300 due to design and option of multi interface setup.

Regards,
Syamantak Omer
Photo of Support team

Support team

  • 6 Posts
  • 1 Reply Like
Hello Syamantak,

Thank you for that. It makes sense. 

Now I will be chasing why AP wont aways pickup hostname from dhcp reservation.

David