<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SZ 100/vSZ H layer 2 discovery differences in SmartZone and Virtual SmartZone</title>
    <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29160#M2009</link>
    <description>Hi David,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;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.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Syamantak Omer</description>
    <pubDate>Fri, 07 Aug 2020 13:42:29 GMT</pubDate>
    <dc:creator>syamantakomer</dc:creator>
    <dc:date>2020-08-07T13:42:29Z</dc:date>
    <item>
      <title>SZ 100/vSZ H layer 2 discovery differences</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29153#M2002</link>
      <description>Hello till now we were deploying high amount of SZ100 clusters, but recently we are switching to vSZ high scale.&amp;nbsp; We always place SZ or vSZ to same subnet as APs.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;With SZ100 AP gets IP from dhcp (no dhcp option 43) and is discovered by the controller without any issue.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;With vSZ it seems different. We use one interface for all services. but APs by default wont get to the controller.(nothing in logs).&amp;nbsp; I have to use DHCP option 43 Then it is fine. Is there any explanation why it is like that ?&amp;nbsp; I tried to run&amp;nbsp;lwapp2scg didn't help.&lt;BR /&gt;&lt;BR /&gt;Why I am bothered ?&amp;nbsp; 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&amp;nbsp; from SZ will give you propper AP name taken from DHCP server.&lt;BR /&gt;&lt;BR /&gt;for me either it is sometihng I am missing in vSZ settings or our vSZ Virtual machine doesnt have fully transparent L2 network connectivity.&lt;BR /&gt;&lt;BR /&gt;Did someone encountered simmiliar issue ?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;David</description>
      <pubDate>Tue, 04 Aug 2020 19:41:37 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29153#M2002</guid>
      <dc:creator>support_team_3z</dc:creator>
      <dc:date>2020-08-04T19:41:37Z</dc:date>
    </item>
    <item>
      <title>Re: SZ 100/vSZ H layer 2 discovery differences</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29154#M2003</link>
      <description>Hi There,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;AFAIK vSZ and SZ works the same way and layer-2 discovery was never supported on v/SZ platforms.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Are you sure it was working on SZ100? If yes, what is the SZ100 version and APs were onboarding using what AP standalone version.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Regards,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Syamantak Omer&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Tue, 04 Aug 2020 20:30:07 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29154#M2003</guid>
      <dc:creator>syamantakomer</dc:creator>
      <dc:date>2020-08-04T20:30:07Z</dc:date>
    </item>
    <item>
      <title>Re: SZ 100/vSZ H layer 2 discovery differences</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29155#M2004</link>
      <description>Hello,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Thanks for interest!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;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.&amp;nbsp; ( I personally did about 5 clusters of SZ 104 ) Always the same, jut same vlan and subnet, and APs were joining SZ automatically.&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;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.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;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.&amp;nbsp;&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Thanks&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;David&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Tue, 04 Aug 2020 20:46:50 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29155#M2004</guid>
      <dc:creator>support_team_3z</dc:creator>
      <dc:date>2020-08-04T20:46:50Z</dc:date>
    </item>
    <item>
      <title>Re: SZ 100/vSZ H layer 2 discovery differences</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29156#M2005</link>
      <description>Hi David,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Please confirm the vSZ firmware version and also try to enable ap-subnet-discovery from vSZ CLI.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;SmartZone&amp;gt; en&lt;/I&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;Password: ********&lt;/I&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;SmartZone&lt;/I&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;# debug&lt;/I&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;SmartZone&lt;/I&gt;(debug)# show ap-subnet-discovery-status&amp;nbsp;&lt;/I&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;&amp;nbsp; &amp;nbsp;AP Subnet Discovery Status: Enabled&lt;/I&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;If it is enabled then try to disable and re-enable&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;SmartZone&lt;/I&gt;(debug)#no ap-subnet-discovery&amp;nbsp;&lt;/I&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;Successful operation&lt;/I&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;If it is disabled, please enable it.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;SmartZone&lt;/I&gt;(debug)# ap-subnet-discovery&amp;nbsp;&lt;/I&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;I alt="" name="" rel="" target="" title="" type="" value=""&gt;Successful operation&lt;/I&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Regards,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Syamantak Omer</description>
      <pubDate>Wed, 05 Aug 2020 11:44:42 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29156#M2005</guid>
      <dc:creator>syamantakomer</dc:creator>
      <dc:date>2020-08-05T11:44:42Z</dc:date>
    </item>
    <item>
      <title>Re: SZ 100/vSZ H layer 2 discovery differences</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29157#M2006</link>
      <description>Hello, I tried what you suggested but somehow this command seems to be not working,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;vSZ was on&amp;nbsp;5.1.2.0.302&amp;nbsp; now I did update to&amp;nbsp;5.2.0.0.699. and neither discovery or debug command works.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c499135b77e247b054b6_5260465af78a9cf366a6247af8f40743_RackMultipart2020080642850fjd1-589c79c2-2a0f-4a65-abf9-b939d4d5b16e-995161561.jpg1596746826"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/1822i180AE9A24CD39CE3/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c499135b77e247b054b6_5260465af78a9cf366a6247af8f40743_RackMultipart2020080642850fjd1-589c79c2-2a0f-4a65-abf9-b939d4d5b16e-995161561.jpg1596746826" alt="Image_ images_messages_5f91c499135b77e247b054b6_5260465af78a9cf366a6247af8f40743_RackMultipart2020080642850fjd1-589c79c2-2a0f-4a65-abf9-b939d4d5b16e-995161561.jpg1596746826" /&gt;&lt;/span&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Thu, 06 Aug 2020 20:47:27 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29157#M2006</guid>
      <dc:creator>support_team_3z</dc:creator>
      <dc:date>2020-08-06T20:47:27Z</dc:date>
    </item>
    <item>
      <title>Re: SZ 100/vSZ H layer 2 discovery differences</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29158#M2007</link>
      <description>Hi David,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I have checked this internally and on my lab setup.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;AP subnet discovery is supported on both SZ and vSZ. Command is also same and below it the output from my lab setup.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c499135b77e247b05784_2723d45dca674c6f88555bb16105f7d4_RackMultipart20200807528333rw5-7eeebab2-3315-48f5-8ab3-1355de3d437a-1511996114.png1596800187"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/1823iDB4FDF916DCEEC2E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c499135b77e247b05784_2723d45dca674c6f88555bb16105f7d4_RackMultipart20200807528333rw5-7eeebab2-3315-48f5-8ab3-1355de3d437a-1511996114.png1596800187" alt="Image_ images_messages_5f91c499135b77e247b05784_2723d45dca674c6f88555bb16105f7d4_RackMultipart20200807528333rw5-7eeebab2-3315-48f5-8ab3-1355de3d437a-1511996114.png1596800187" /&gt;&lt;/span&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;*Click on the image to see in full size.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I would suggest running below command once again.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;I&gt;vsze-60(debug)# ap-subnet-discovery&lt;/I&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR /&gt;and then&lt;BR /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;I&gt;vsze-60(debug)# show ap-subnet-discovery-status&lt;/I&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;If still you are facing the issue, please log a case with support with below details.&lt;BR /&gt;&lt;BR /&gt;1- vSZ type (Essential or High Scale) with its version. Output of "show version"&lt;BR /&gt;2- Interface type (Single or three interface). Output of "show interface"&lt;BR /&gt;3- Output of above commands.&lt;BR /&gt;4- If command works but AP L2 discovery still&amp;nbsp; not working then provide below details as well.&lt;BR /&gt;&lt;UL&gt;&lt;LI&gt;AP model(s)&lt;/LI&gt;&lt;LI&gt;AP software version when onboarding APs.&lt;/LI&gt;&lt;/UL&gt;Regards,&lt;BR /&gt;Syamantak Omer</description>
      <pubDate>Fri, 07 Aug 2020 11:44:25 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29158#M2007</guid>
      <dc:creator>syamantakomer</dc:creator>
      <dc:date>2020-08-07T11:44:25Z</dc:date>
    </item>
    <item>
      <title>Re: SZ 100/vSZ H layer 2 discovery differences</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29159#M2008</link>
      <description>Hello Syamantak,&lt;BR /&gt;&lt;BR /&gt;I tried on different vSZ we deployed recently and command is not there, might it be difference between vSZ-E and vSZ-H ?&lt;BR /&gt;We were told that there is no difference and we should always use High scale.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;I also tried on 104 without any issue.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c499135b77e247b05a53_66764ea1ef4dc5f541bd1c7c8aa2b565_RackMultipart20200807983451ege-ce34fea4-a3dd-4dc2-9107-148e5544101f-1355278057.png1596802472"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/1824iF79EF9ABD095A8EF/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c499135b77e247b05a53_66764ea1ef4dc5f541bd1c7c8aa2b565_RackMultipart20200807983451ege-ce34fea4-a3dd-4dc2-9107-148e5544101f-1355278057.png1596802472" alt="Image_ images_messages_5f91c499135b77e247b05a53_66764ea1ef4dc5f541bd1c7c8aa2b565_RackMultipart20200807983451ege-ce34fea4-a3dd-4dc2-9107-148e5544101f-1355278057.png1596802472" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Thank you.&lt;BR /&gt;&lt;BR /&gt;David</description>
      <pubDate>Fri, 07 Aug 2020 12:16:43 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29159#M2008</guid>
      <dc:creator>support_team_3z</dc:creator>
      <dc:date>2020-08-07T12:16:43Z</dc:date>
    </item>
    <item>
      <title>Re: SZ 100/vSZ H layer 2 discovery differences</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29160#M2009</link>
      <description>Hi David,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;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.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Syamantak Omer</description>
      <pubDate>Fri, 07 Aug 2020 13:42:29 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29160#M2009</guid>
      <dc:creator>syamantakomer</dc:creator>
      <dc:date>2020-08-07T13:42:29Z</dc:date>
    </item>
    <item>
      <title>Re: SZ 100/vSZ H layer 2 discovery differences</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29161#M2010</link>
      <description>Hello Syamantak,&lt;BR /&gt;&lt;BR /&gt;Thank you for that. It makes sense.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Now I will be chasing why AP wont aways pickup hostname from dhcp reservation.&lt;BR /&gt;&lt;BR /&gt;David</description>
      <pubDate>Fri, 07 Aug 2020 13:52:47 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SZ-100-vSZ-H-layer-2-discovery-differences/m-p/29161#M2010</guid>
      <dc:creator>support_team_3z</dc:creator>
      <dc:date>2020-08-07T13:52:47Z</dc:date>
    </item>
  </channel>
</rss>

