<?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: WCGW: Forklift Migration of our A3 Server. in ExtremeCloud A3</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-a3/wcgw-forklift-migration-of-our-a3-server/m-p/79424#M84</link>
    <description>&lt;P&gt;If the network you're moving to has a different subnet you'll need to change the IP addresses like  you mentioned. You'll also want to verify any VLANs in use are supported on the backend network of the new location. If you're joined to a domain and the new location has a different domain, you'll want to join it to the new domain once you've deployed.  Finally you'll want to update the device list IPs if those are changing at the new location as well. &lt;/P&gt;</description>
    <pubDate>Wed, 09 Oct 2019 19:35:29 GMT</pubDate>
    <dc:creator>samantha_lynn</dc:creator>
    <dc:date>2019-10-09T19:35:29Z</dc:date>
    <item>
      <title>WCGW: Forklift Migration of our A3 Server.</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-a3/wcgw-forklift-migration-of-our-a3-server/m-p/79423#M83</link>
      <description>&lt;P&gt;What could go wrong if we moved the physical server that's hosting A3?  It seems simple logically, backup, change a few IP addresses, shut it down, move it, turn it back on.  Things are never as simple as they seem.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone ever done it before?  How did it go?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're moving into a new corporate headquarters at the end of the month.  Our development instance of A3 is running on a dedicated host and is 90% production ready but its in our old headquarters.  Ideally, we'd do a fresh install, but we don't have the time to do it.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2019 03:39:05 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-a3/wcgw-forklift-migration-of-our-a3-server/m-p/79423#M83</guid>
      <dc:creator>jason_simmons</dc:creator>
      <dc:date>2019-10-09T03:39:05Z</dc:date>
    </item>
    <item>
      <title>Re: WCGW: Forklift Migration of our A3 Server.</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-a3/wcgw-forklift-migration-of-our-a3-server/m-p/79424#M84</link>
      <description>&lt;P&gt;If the network you're moving to has a different subnet you'll need to change the IP addresses like  you mentioned. You'll also want to verify any VLANs in use are supported on the backend network of the new location. If you're joined to a domain and the new location has a different domain, you'll want to join it to the new domain once you've deployed.  Finally you'll want to update the device list IPs if those are changing at the new location as well. &lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2019 19:35:29 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-a3/wcgw-forklift-migration-of-our-a3-server/m-p/79424#M84</guid>
      <dc:creator>samantha_lynn</dc:creator>
      <dc:date>2019-10-09T19:35:29Z</dc:date>
    </item>
    <item>
      <title>Re: WCGW: Forklift Migration of our A3 Server.</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-a3/wcgw-forklift-migration-of-our-a3-server/m-p/79425#M85</link>
      <description>I’ll make sure I do that.  Thanks!&lt;BR /&gt;
&lt;BR /&gt;
JDS</description>
      <pubDate>Wed, 09 Oct 2019 23:08:18 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-a3/wcgw-forklift-migration-of-our-a3-server/m-p/79425#M85</guid>
      <dc:creator>jason_simmons</dc:creator>
      <dc:date>2019-10-09T23:08:18Z</dc:date>
    </item>
  </channel>
</rss>

