<?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: Expedition to migrate between two different PA FW models? in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-to-migrate-between-two-different-pa-fw-models/m-p/264579#M1661</link>
    <description>&lt;P&gt;I found it was easier and faster to use good old sed to quickly swap out interface names between a 5060 and 5260 config.&lt;/P&gt;</description>
    <pubDate>Fri, 31 May 2019 19:36:55 GMT</pubDate>
    <dc:creator>CGal</dc:creator>
    <dc:date>2019-05-31T19:36:55Z</dc:date>
    <item>
      <title>Expedition to migrate between two different PA FW models?</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-to-migrate-between-two-different-pa-fw-models/m-p/263681#M1652</link>
      <description>&lt;P&gt;We are upgrading into newer/faster firewall models, and I am curious if the Expedition tool could be used to re-map the old firewall physical interfaces identifiers to the new firewall interface identifiers?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Or, is there an easier process to maintain our FW configurations while upgrading into a new firewall hardware model.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" size="2"&gt;OLD&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; NEW&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" size="2"&gt; ethernet1/3&amp;nbsp; &amp;nbsp; ethernet1/6&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" size="2"&gt;ethernet1/2&amp;nbsp; &amp;nbsp; ethernet 1/3&lt;BR /&gt;&lt;/FONT&gt;&lt;FONT face="courier new,courier" size="2"&gt;etc.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank You,&lt;/P&gt;
&lt;P&gt;~Eric&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 May 2019 23:24:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-to-migrate-between-two-different-pa-fw-models/m-p/263681#M1652</guid>
      <dc:creator>edavistvcorg</dc:creator>
      <dc:date>2019-05-30T23:24:33Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition to migrate between two different PA FW models?</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-to-migrate-between-two-different-pa-fw-models/m-p/264579#M1661</link>
      <description>&lt;P&gt;I found it was easier and faster to use good old sed to quickly swap out interface names between a 5060 and 5260 config.&lt;/P&gt;</description>
      <pubDate>Fri, 31 May 2019 19:36:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-to-migrate-between-two-different-pa-fw-models/m-p/264579#M1661</guid>
      <dc:creator>CGal</dc:creator>
      <dc:date>2019-05-31T19:36:55Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition to migrate between two different PA FW models?</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-to-migrate-between-two-different-pa-fw-models/m-p/269735#M1684</link>
      <description>&lt;P&gt;That's what we finally did. Thanks for your reply!&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2019 19:57:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-to-migrate-between-two-different-pa-fw-models/m-p/269735#M1684</guid>
      <dc:creator>edavistvcorg</dc:creator>
      <dc:date>2019-06-13T19:57:42Z</dc:date>
    </item>
  </channel>
</rss>

