<?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: Auto-install of ZoneDirector possible? in ZoneDirector</title>
    <link>https://community.ruckuswireless.com/t5/ZoneDirector/Auto-install-of-ZoneDirector-possible/m-p/43751#M7907</link>
    <description>A factory defaulted ZoneDirector, not connected to a network, will come up with the
&lt;BR /&gt;
default IP 192.168.0.2.  You typically attach a pre-configured PC with 192.168.0.x
&lt;BR /&gt;
address, and use &lt;A href="https://192.168.0.2" rel="nofollow"&gt;https://192.168.0.2&lt;/A&gt; to configure the ZD thru the Setup Wizard.
&lt;BR /&gt;&lt;BR /&gt;
When connected to a network with a DHCP server, the ZD will pull a DHCP IP 
&lt;BR /&gt;
address, and you will need to find the ZD's MAC address on the server to determine
&lt;BR /&gt;
it's IP address then.  Just the same, when you HTTPS into the ZD, you will have to
&lt;BR /&gt;
configure initially thru the Setup Wizard.  While Ruckus is working on a text config
&lt;BR /&gt;
backup/restore, this is still a Feature Request at this time, so no auto-configuration
&lt;BR /&gt;
is possible at this date.</description>
    <pubDate>Thu, 19 Jun 2014 23:02:30 GMT</pubDate>
    <dc:creator>michael_brado</dc:creator>
    <dc:date>2014-06-19T23:02:30Z</dc:date>
    <item>
      <title>Auto-install of ZoneDirector possible?</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Auto-install-of-ZoneDirector-possible/m-p/43750#M7906</link>
      <description>When a ZoneDirector boots up, does it perform DHCP requests by default?  I'm interested in pre-configuring DHCP on routers at remote locations, then sending an install team.  The idea is to open a fresh box and just plug it in, with no configuration of the individual ZD by the installer (or by a pre-staging team).  I'd like to have DHCP direct the ZD to a TFTP server with the filename of a pre-generated configuration file for that location.  Is this possible with Ruckus?  We previously did this with our Cisco solution that we are looking to replace.</description>
      <pubDate>Wed, 18 Jun 2014 12:08:19 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Auto-install-of-ZoneDirector-possible/m-p/43750#M7906</guid>
      <dc:creator>paul_taylops</dc:creator>
      <dc:date>2014-06-18T12:08:19Z</dc:date>
    </item>
    <item>
      <title>Re: Auto-install of ZoneDirector possible?</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Auto-install-of-ZoneDirector-possible/m-p/43751#M7907</link>
      <description>A factory defaulted ZoneDirector, not connected to a network, will come up with the
&lt;BR /&gt;
default IP 192.168.0.2.  You typically attach a pre-configured PC with 192.168.0.x
&lt;BR /&gt;
address, and use &lt;A href="https://192.168.0.2" rel="nofollow"&gt;https://192.168.0.2&lt;/A&gt; to configure the ZD thru the Setup Wizard.
&lt;BR /&gt;&lt;BR /&gt;
When connected to a network with a DHCP server, the ZD will pull a DHCP IP 
&lt;BR /&gt;
address, and you will need to find the ZD's MAC address on the server to determine
&lt;BR /&gt;
it's IP address then.  Just the same, when you HTTPS into the ZD, you will have to
&lt;BR /&gt;
configure initially thru the Setup Wizard.  While Ruckus is working on a text config
&lt;BR /&gt;
backup/restore, this is still a Feature Request at this time, so no auto-configuration
&lt;BR /&gt;
is possible at this date.</description>
      <pubDate>Thu, 19 Jun 2014 23:02:30 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Auto-install-of-ZoneDirector-possible/m-p/43751#M7907</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2014-06-19T23:02:30Z</dc:date>
    </item>
  </channel>
</rss>

