<?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: Avaya Interoperability 3500 Series in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Avaya-Interoperability-3500-Series/m-p/43817#M12480</link>
    <description>Any switch that supports VLANs (and 802.1q trunking) should be compatible with Ruckus ZoneDirector controllers and APs.&lt;BR /&gt;With that being said, there's more to consider than the brand of the switch being used when determining the WiFi/network design and/or compatibility w/ an existing network.&lt;BR /&gt;&lt;BR /&gt;You may want to look at some Avaya "ERS" documents for details:&lt;BR /&gt;&lt;A href="https://downloads.avaya.com/css/P8/documents/100161568" rel="nofollow" target="_blank" title="Link https//downloadsavayacom/css/P8/documents/100161568"&gt;https://downloads.avaya.com/css/P8/documents/100161568&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://blog.michaelfmcnamara.com/2011/01/802-1q-vlan-tagging-on-an-ethernet-routing-switch/" rel="nofollow" target="_blank" title="Link https//blogmichaelfmcnamaracom/2011/01/802-1q-vlan-tagging-on-an-ethernet-routing-switch/"&gt;https://blog.michaelfmcnamara.com/2011/01/802-1q-vlan-tagging-on-an-ethernet-routing-switch/&lt;/A&gt;</description>
    <pubDate>Wed, 09 Mar 2016 15:33:16 GMT</pubDate>
    <dc:creator>bill_burns_6069</dc:creator>
    <dc:date>2016-03-09T15:33:16Z</dc:date>
    <item>
      <title>Avaya Interoperability 3500 Series</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Avaya-Interoperability-3500-Series/m-p/43816#M12479</link>
      <description>All,&lt;BR /&gt;Is &lt;B&gt;AP Zone Flex R700 &lt;/B&gt;and &lt;B&gt;Zone Director 1100 &lt;/B&gt;compatible with &lt;B&gt;Avaya&lt;/B&gt; Ethernet Routing Switch &lt;B&gt;3500 Series&lt;/B&gt;? Is there any application notes about the interoperability?&lt;BR /&gt;&lt;BR /&gt;Regards,</description>
      <pubDate>Tue, 08 Mar 2016 21:26:31 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Avaya-Interoperability-3500-Series/m-p/43816#M12479</guid>
      <dc:creator>daniel_capelass</dc:creator>
      <dc:date>2016-03-08T21:26:31Z</dc:date>
    </item>
    <item>
      <title>Re: Avaya Interoperability 3500 Series</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Avaya-Interoperability-3500-Series/m-p/43817#M12480</link>
      <description>Any switch that supports VLANs (and 802.1q trunking) should be compatible with Ruckus ZoneDirector controllers and APs.&lt;BR /&gt;With that being said, there's more to consider than the brand of the switch being used when determining the WiFi/network design and/or compatibility w/ an existing network.&lt;BR /&gt;&lt;BR /&gt;You may want to look at some Avaya "ERS" documents for details:&lt;BR /&gt;&lt;A href="https://downloads.avaya.com/css/P8/documents/100161568" rel="nofollow" target="_blank" title="Link https//downloadsavayacom/css/P8/documents/100161568"&gt;https://downloads.avaya.com/css/P8/documents/100161568&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://blog.michaelfmcnamara.com/2011/01/802-1q-vlan-tagging-on-an-ethernet-routing-switch/" rel="nofollow" target="_blank" title="Link https//blogmichaelfmcnamaracom/2011/01/802-1q-vlan-tagging-on-an-ethernet-routing-switch/"&gt;https://blog.michaelfmcnamara.com/2011/01/802-1q-vlan-tagging-on-an-ethernet-routing-switch/&lt;/A&gt;</description>
      <pubDate>Wed, 09 Mar 2016 15:33:16 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Avaya-Interoperability-3500-Series/m-p/43817#M12480</guid>
      <dc:creator>bill_burns_6069</dc:creator>
      <dc:date>2016-03-09T15:33:16Z</dc:date>
    </item>
    <item>
      <title>Re: Avaya Interoperability 3500 Series</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Avaya-Interoperability-3500-Series/m-p/43818#M12481</link>
      <description>You might also need/want to know about configuring a "native"/default/untagged VLAN on a trunked port.</description>
      <pubDate>Wed, 09 Mar 2016 15:53:09 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Avaya-Interoperability-3500-Series/m-p/43818#M12481</guid>
      <dc:creator>bill_burns_6069</dc:creator>
      <dc:date>2016-03-09T15:53:09Z</dc:date>
    </item>
    <item>
      <title>Re: Avaya Interoperability 3500 Series</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Avaya-Interoperability-3500-Series/m-p/43819#M12482</link>
      <description>AFAIK:&lt;BR /&gt;The most common and simple design for Ruckus ZoneDirectors and APs involves having a switched network with "end-to-end" VLANs that span your entire network.&lt;BR /&gt;Then you can allocate a single "wireless management" VLAN/Subnet for the management IPs of your controllers and all APs.&lt;BR /&gt;&lt;BR /&gt;(a typical "class C"/24 management subnet would accomodate about 250 APs, assuming there's nothing else in it)&lt;BR /&gt;&lt;BR /&gt;Connect your controller to an "access"/untagged port that only carries the one management VLAN.&lt;BR /&gt;Connect your APs to trunked/tagged ports, that have your management VLAN as the only "native"/untagged VLAN on that port.&lt;BR /&gt;All other VLANs on the trunk ports connected to your APs (the ones that your wireless clients will be in) will be "tagged".&lt;BR /&gt;&lt;BR /&gt;When configuring the ruckus ZoneDirector controller, select one of those "other" VLANS for use w/ each of your SSIDs.&lt;BR /&gt;(I assume that your wired network has centralized routing between subnets)&lt;BR /&gt;&lt;BR /&gt;There are other designs.&lt;BR /&gt;I think it's the simplest one.&lt;BR /&gt;&lt;BR /&gt;If your wired network is compatible w/ this design then it may be a good starting point for you.&lt;BR /&gt;If not, then you will need to look into other designs, possibly including tunneling traffic from APs to ZoneDirectors.&lt;BR /&gt;&lt;BR /&gt;..but you'll need to settle on (or at least narrow-down choices for) a design before going too far w/ configuration details.&lt;BR /&gt;&lt;BR /&gt;If this is too much to consider at once, then you may want consult w/ a contractor.</description>
      <pubDate>Wed, 09 Mar 2016 16:13:41 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Avaya-Interoperability-3500-Series/m-p/43819#M12482</guid>
      <dc:creator>bill_burns_6069</dc:creator>
      <dc:date>2016-03-09T16:13:41Z</dc:date>
    </item>
  </channel>
</rss>

