<?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 Migrate Panorama to AWS in Panorama Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/panorama-discussions/migrate-panorama-to-aws/m-p/529725#M1350</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm planning to do a migration of Panorama from esxi to&amp;nbsp; AWS.&amp;nbsp; This will require the Panorama to have a different IP address.&amp;nbsp; &amp;nbsp;What's the best way to handle the IP change, if the firewalls are getting the Panorama IP config from device template setting?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it best to override locally after the migration and then update the template after?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 03 Feb 2023 03:32:53 GMT</pubDate>
    <dc:creator>securehops</dc:creator>
    <dc:date>2023-02-03T03:32:53Z</dc:date>
    <item>
      <title>Migrate Panorama to AWS</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/migrate-panorama-to-aws/m-p/529725#M1350</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm planning to do a migration of Panorama from esxi to&amp;nbsp; AWS.&amp;nbsp; This will require the Panorama to have a different IP address.&amp;nbsp; &amp;nbsp;What's the best way to handle the IP change, if the firewalls are getting the Panorama IP config from device template setting?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it best to override locally after the migration and then update the template after?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Feb 2023 03:32:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/migrate-panorama-to-aws/m-p/529725#M1350</guid>
      <dc:creator>securehops</dc:creator>
      <dc:date>2023-02-03T03:32:53Z</dc:date>
    </item>
    <item>
      <title>Re: Migrate Panorama to AWS</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/migrate-panorama-to-aws/m-p/530202#M1356</link>
      <description>&lt;P&gt;Even though the firewalls have the panorama IP from the template, you once had to insert it manually before the firewall was managed by panorama.&lt;BR /&gt;&lt;BR /&gt;so my suggestion would be launch the new panorama with the new ip, migrate the config to the new panorama (new ip) and just change the IP in the template config (from the old panorama ip and do a push) they will connect to the new one, and since it has the same config, no problem.&lt;BR /&gt;&lt;BR /&gt;New ones insert it manually just like you did before.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2023 23:22:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/migrate-panorama-to-aws/m-p/530202#M1356</guid>
      <dc:creator>GabrielMontiel</dc:creator>
      <dc:date>2023-02-07T23:22:58Z</dc:date>
    </item>
  </channel>
</rss>

