cancel
Showing results for 
Search instead for 
Did you mean: 

SZ 100/vSZ H layer 2 discovery differences

support_team_3z
New Contributor II
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
8 REPLIES 8

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.

Image_ images_messages_5f91c499135b77e247b05784_2723d45dca674c6f88555bb16105f7d4_RackMultipart20200807528333rw5-7eeebab2-3315-48f5-8ab3-1355de3d437a-1511996114.png1596800187
*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

Syamantak Omer
Sr.Staff TSE | CWNA | CCNA | RCWA | RASZA | RICXI
RUCKUS Networks, CommScope!
Follow me on LinkedIn

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.

Image_ images_messages_5f91c499135b77e247b05a53_66764ea1ef4dc5f541bd1c7c8aa2b565_RackMultipart20200807983451ege-ce34fea4-a3dd-4dc2-9107-148e5544101f-1355278057.png1596802472

Thank you.

David

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

Syamantak Omer
Sr.Staff TSE | CWNA | CCNA | RCWA | RASZA | RICXI
RUCKUS Networks, CommScope!
Follow me on LinkedIn

Hello Syamantak,

Thank you for that. It makes sense. 

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

David