<?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: Importing PA200 configuration to PA220. in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/importing-pa200-configuration-to-pa220/m-p/214303#M62284</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/75149"&gt;@Nischal&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;From the Firewall Migration Guide :&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Determine the target PAN‐OS release — Before you Migrate to New Firewalls, ensure that the old firewall is running the same PAN‐OS release and the same content release version as is installed on the new firewall. If the old firewall does not support the PAN‐OS release that is installed on the new firewall, you must ensure that the old firewall is no more than one feature release behind.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can find the entire guide on this page :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.paloaltonetworks.com/documentation/platforms" target="_blank"&gt;https://www.paloaltonetworks.com/documentation/platforms&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers !&lt;/P&gt;
&lt;P&gt;-Kiwi&lt;/P&gt;</description>
    <pubDate>Tue, 15 May 2018 12:24:12 GMT</pubDate>
    <dc:creator>kiwi</dc:creator>
    <dc:date>2018-05-15T12:24:12Z</dc:date>
    <item>
      <title>Importing PA200 configuration to PA220.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/importing-pa200-configuration-to-pa220/m-p/214283#M62280</link>
      <description>&lt;P&gt;We are planning to phase out PA200 firewall with PA220 .&lt;/P&gt;&lt;P&gt;PA200 firewall is running PAN OS 7.1.14.&lt;/P&gt;&lt;P&gt;PA 220 firewall comes preloaded with PAN OS version 8.0.X.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My concerns is,&amp;nbsp;Can we directly import the firewall configuration&amp;nbsp; (device state) from PA200 to PA220 without any issue?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or do we need to upgrade the PA 200 first to 8.0.x and then export and import this config to new PA220?&lt;/P&gt;</description>
      <pubDate>Tue, 15 May 2018 09:37:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/importing-pa200-configuration-to-pa220/m-p/214283#M62280</guid>
      <dc:creator>Nischal</dc:creator>
      <dc:date>2018-05-15T09:37:01Z</dc:date>
    </item>
    <item>
      <title>Re: Importing PA200 configuration to PA220.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/importing-pa200-configuration-to-pa220/m-p/214303#M62284</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/75149"&gt;@Nischal&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;From the Firewall Migration Guide :&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Determine the target PAN‐OS release — Before you Migrate to New Firewalls, ensure that the old firewall is running the same PAN‐OS release and the same content release version as is installed on the new firewall. If the old firewall does not support the PAN‐OS release that is installed on the new firewall, you must ensure that the old firewall is no more than one feature release behind.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can find the entire guide on this page :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.paloaltonetworks.com/documentation/platforms" target="_blank"&gt;https://www.paloaltonetworks.com/documentation/platforms&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers !&lt;/P&gt;
&lt;P&gt;-Kiwi&lt;/P&gt;</description>
      <pubDate>Tue, 15 May 2018 12:24:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/importing-pa200-configuration-to-pa220/m-p/214303#M62284</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2018-05-15T12:24:12Z</dc:date>
    </item>
    <item>
      <title>Re: Importing PA200 configuration to PA220.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/importing-pa200-configuration-to-pa220/m-p/214317#M62289</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/75149"&gt;@Nischal&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;As&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/11943"&gt;@kiwi&lt;/a&gt;&amp;nbsp;noted these need to be running the same version to properly perform the migration as you are planning. Of course, you could perform this migration without updating if you simply utilize the running-config.xml as a basis of re-creating the configurtation directly on the PA-220 instead of importing it. This would allow a chance to go through the entire configuration and verify that there are not any unneeded statements, as well as giving you a chance to properly test traffic before installing it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 May 2018 13:46:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/importing-pa200-configuration-to-pa220/m-p/214317#M62289</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-05-15T13:46:54Z</dc:date>
    </item>
  </channel>
</rss>

