<?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: Zone Director interface configuration tips in ZoneDirector</title>
    <link>https://community.ruckuswireless.com/t5/ZoneDirector/Zone-Director-interface-configuration-tips/m-p/4915#M682</link>
    <description>The simplest thing to do is to put the "first" interface of the ZD3000 in the same subnet as your AP's management addresses.
&lt;BR /&gt;
In my case I connected the ZD3000 to a trunked/tagged interface, and (under Device IP Settings) set the ZD3000's "Access VLAN" to the VLAN that contained the AP's managemet IPs.
&lt;BR /&gt;
An even simpler (and more recommended) approach would be to leave the switch_port configured as an access port in your AP VLAN, and configure the ZD3000 for Access_VLAN:1
&lt;BR /&gt;&lt;BR /&gt;
I didn't bother configuring the "Management Interface" section of the ZD3000.
&lt;BR /&gt;
I use the first ethernet port (the one on the left where it says "10/100/1000") for everything.
&lt;BR /&gt;
If you want to use that interface to manage the ZD3000 itself (and nothing else) tick the "enable Management Interface box" and leave the "default gateway" box unticked.
&lt;BR /&gt;
You've got the same decision to make re: connecting it to a trunked/tagged switch port, or to an access port.
&lt;BR /&gt;&lt;BR /&gt;
Next, to allow your APs to find the ZD3000 (in the simplest way) you should attach them to switch-ports that are trunked/tagged, with their native VLANs set to the VLAN that contains their management IPs.
&lt;BR /&gt;
Each trunk port should also allow VLANs/tags for the VLANs that will carry your user's wireless traffic.
&lt;BR /&gt;
DHCP should be served on the AP management VLAN as well as all of the user/wireless VLANS.
&lt;BR /&gt;&lt;BR /&gt;
In my case, I use a centralized DHCP server for this.
&lt;BR /&gt;
There are options to have the ZD3000 serve DHCP.
&lt;BR /&gt;&lt;BR /&gt;
Does that make sense, and... 
&lt;BR /&gt;
Is that what you were looking for?</description>
    <pubDate>Mon, 13 Jan 2014 19:31:45 GMT</pubDate>
    <dc:creator>bill_burns_6069</dc:creator>
    <dc:date>2014-01-13T19:31:45Z</dc:date>
    <item>
      <title>Zone Director interface configuration tips</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Zone-Director-interface-configuration-tips/m-p/4914#M681</link>
      <description>Can anyone please help me to allow interface configuration of a ZD300 for 2 subnets.
&lt;BR /&gt;
I wish to use a 192.168.x.x subnet for AP management and a 10.10.x.x subnet to be able to access the controller remotely. I have read through the config guide and done what is suggests (the example is pretty ordinary in the guide) its not working still. Any tips would be appreaciated</description>
      <pubDate>Mon, 13 Jan 2014 08:12:15 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Zone-Director-interface-configuration-tips/m-p/4914#M681</guid>
      <dc:creator>duncan_otoole</dc:creator>
      <dc:date>2014-01-13T08:12:15Z</dc:date>
    </item>
    <item>
      <title>Re: Zone Director interface configuration tips</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Zone-Director-interface-configuration-tips/m-p/4915#M682</link>
      <description>The simplest thing to do is to put the "first" interface of the ZD3000 in the same subnet as your AP's management addresses.
&lt;BR /&gt;
In my case I connected the ZD3000 to a trunked/tagged interface, and (under Device IP Settings) set the ZD3000's "Access VLAN" to the VLAN that contained the AP's managemet IPs.
&lt;BR /&gt;
An even simpler (and more recommended) approach would be to leave the switch_port configured as an access port in your AP VLAN, and configure the ZD3000 for Access_VLAN:1
&lt;BR /&gt;&lt;BR /&gt;
I didn't bother configuring the "Management Interface" section of the ZD3000.
&lt;BR /&gt;
I use the first ethernet port (the one on the left where it says "10/100/1000") for everything.
&lt;BR /&gt;
If you want to use that interface to manage the ZD3000 itself (and nothing else) tick the "enable Management Interface box" and leave the "default gateway" box unticked.
&lt;BR /&gt;
You've got the same decision to make re: connecting it to a trunked/tagged switch port, or to an access port.
&lt;BR /&gt;&lt;BR /&gt;
Next, to allow your APs to find the ZD3000 (in the simplest way) you should attach them to switch-ports that are trunked/tagged, with their native VLANs set to the VLAN that contains their management IPs.
&lt;BR /&gt;
Each trunk port should also allow VLANs/tags for the VLANs that will carry your user's wireless traffic.
&lt;BR /&gt;
DHCP should be served on the AP management VLAN as well as all of the user/wireless VLANS.
&lt;BR /&gt;&lt;BR /&gt;
In my case, I use a centralized DHCP server for this.
&lt;BR /&gt;
There are options to have the ZD3000 serve DHCP.
&lt;BR /&gt;&lt;BR /&gt;
Does that make sense, and... 
&lt;BR /&gt;
Is that what you were looking for?</description>
      <pubDate>Mon, 13 Jan 2014 19:31:45 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Zone-Director-interface-configuration-tips/m-p/4915#M682</guid>
      <dc:creator>bill_burns_6069</dc:creator>
      <dc:date>2014-01-13T19:31:45Z</dc:date>
    </item>
  </channel>
</rss>

