<?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: Moving Colo Datacenter in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231318#M66412</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;The config is just an xml file soas long as the formatting is correct, a find/replace should work just fine. I would recommen making a copy or two and just have them, but worst case you have the one in the old colo to refer to.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Obivously once you do the find/replace and boot the device, go through the config to make sure its correct and test it out the best you can.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers!&lt;/P&gt;</description>
    <pubDate>Tue, 18 Sep 2018 20:56:23 GMT</pubDate>
    <dc:creator>OtakarKlier</dc:creator>
    <dc:date>2018-09-18T20:56:23Z</dc:date>
    <item>
      <title>Moving Colo Datacenter</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231248#M66400</link>
      <description>&lt;P&gt;Hi folks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We got some dreaded news that our colo vendor is not renewing lease and we are now moving.&lt;/P&gt;&lt;P&gt;We have two 3020 firewalls configured in HA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am looking for any general comments that could help in my direction.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One thought:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Break HA.&lt;/LI&gt;&lt;LI&gt;Take secondary firewall over to new colo datacenter.&lt;/LI&gt;&lt;LI&gt;Edit secondary firewall configuration for new IPs.&lt;/LI&gt;&lt;LI&gt;Make secondary, new primary.&lt;/LI&gt;&lt;LI&gt;Bring over original primary, make secondary, sync new config.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone have comments from experience?&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2018 16:47:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231248#M66400</guid>
      <dc:creator>OMatlock</dc:creator>
      <dc:date>2018-09-18T16:47:14Z</dc:date>
    </item>
    <item>
      <title>Re: Moving Colo Datacenter</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231316#M66410</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Once you break HA there is no more Primary/Secondary so I have modified your steps a bit just to be safe.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Shutdown secondary firewall&lt;/LI&gt;&lt;LI&gt;Disable HA on remaining functioning firewall&lt;/LI&gt;&lt;LI&gt;Take secondary firewall over to new colo datacenter.&lt;/LI&gt;&lt;LI&gt;Edit secondary firewall configuration for new IPs&lt;/LI&gt;&lt;LI&gt;At new Colo, make sure the current running firewall has a lower 'Device Priority' than the one you are brining over&lt;/LI&gt;&lt;LI&gt;Bring over original primary and cable up&lt;/LI&gt;&lt;LI&gt;fire up the original primary and make sure to push a config sync from old secondary to old primary&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Hope that makes sense.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Good luck!&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2018 20:47:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231316#M66410</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2018-09-18T20:47:44Z</dc:date>
    </item>
    <item>
      <title>Re: Moving Colo Datacenter</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231317#M66411</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/27580"&gt;@OtakarKlier&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am wondering if there are an suggestions for editing the config?&lt;/P&gt;&lt;P&gt;After I do a rule cleanup, could use find/replace in config file for public IPs?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sounds scary, but wondering if most config could be populated that way or other, besides only combing through and changing every rule, etc. manually.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2018 20:53:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231317#M66411</guid>
      <dc:creator>OMatlock</dc:creator>
      <dc:date>2018-09-18T20:53:10Z</dc:date>
    </item>
    <item>
      <title>Re: Moving Colo Datacenter</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231318#M66412</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;The config is just an xml file soas long as the formatting is correct, a find/replace should work just fine. I would recommen making a copy or two and just have them, but worst case you have the one in the old colo to refer to.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Obivously once you do the find/replace and boot the device, go through the config to make sure its correct and test it out the best you can.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers!&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2018 20:56:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231318#M66412</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2018-09-18T20:56:23Z</dc:date>
    </item>
    <item>
      <title>Re: Moving Colo Datacenter</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231320#M66413</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/27580"&gt;@OtakarKlier&lt;/a&gt;&amp;nbsp; &amp;nbsp;!!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yea, would certainly review and test.&amp;nbsp; Trying to have it in place ahead of time and validate what we can before moving all the servers over.&amp;nbsp; We do all our routing through the PA firewall.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2018 21:00:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231320#M66413</guid>
      <dc:creator>OMatlock</dc:creator>
      <dc:date>2018-09-18T21:00:23Z</dc:date>
    </item>
    <item>
      <title>Re: Moving Colo Datacenter</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231500#M66472</link>
      <description>&lt;P&gt;I recently moved my company from an owned DC to a CoLo.&amp;nbsp; I did essentially what you documented except used our "OSS" (On-Site Spare).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The set-up was DC 1 &amp;lt;--&amp;gt; DC 2.&amp;nbsp; I prestaged&amp;nbsp;a third 3020 OSS in the new DC (DC 3).&amp;nbsp; I moved HA to DC 2.&amp;nbsp; Went into the Palo portal and said DC 1's FW was "broken" which transferred&amp;nbsp;the licensing and functionality from DC 1 FW to DC 3's FW.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I then HA peered DC 2 and DC 3's FWs.&amp;nbsp; Once that was squared aware I made DC 3's FW active taking over from DC 2.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The whole process took about 45 minutes never creating an outage&amp;nbsp;and we didn't have to go hours running single threaded.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Sep 2018 18:09:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231500#M66472</guid>
      <dc:creator>Brandon_Wertz</dc:creator>
      <dc:date>2018-09-19T18:09:15Z</dc:date>
    </item>
    <item>
      <title>Re: Moving Colo Datacenter</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231513#M66475</link>
      <description>&lt;P&gt;Thank you!&amp;nbsp;&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/5300"&gt;@Brandon_Wertz&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Nice to have the OSS.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I wonder if I will be able to transfer the Licensing, etc. to our secondary FW when time comes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We will have downtime since we will be physically moving our servers, etc.&amp;nbsp; I plan to stand up maybe a test web server and cycle through IPs in the new config to get some level of validation before the servers and switches move in.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Sep 2018 19:11:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231513#M66475</guid>
      <dc:creator>OMatlock</dc:creator>
      <dc:date>2018-09-19T19:11:05Z</dc:date>
    </item>
    <item>
      <title>Re: Moving Colo Datacenter</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231527#M66478</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;The licenses should be easy to swap. You could even get your sales team involded, maybe they can give out temp licenses if you need them for a short time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers!&lt;/P&gt;</description>
      <pubDate>Wed, 19 Sep 2018 20:57:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/moving-colo-datacenter/m-p/231527#M66478</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2018-09-19T20:57:10Z</dc:date>
    </item>
  </channel>
</rss>

