<?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: SD-WAN Hardware Change / Migration in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/sd-wan-hardware-change-migration/m-p/436385#M96262</link>
    <description>&lt;P&gt;Hi Mate,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Export the device state from the PA-220 and import and load &lt;STRONG&gt;through the CLI&lt;/STRONG&gt; to the PA-400 series, that will have the merged configuration from Panorama. Make sure Panorama is running 10.1.x if adding in a PA-440. Connect the PA-440 to Panorama (point towards and add in auth key). Remove the PA-220 from the templates and device groups, and check the box for the PA-400 series.&lt;/P&gt;&lt;P&gt;If mission critical network I would look for a maintenance window.&amp;nbsp;&lt;/P&gt;&lt;P&gt;//&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Import device state (firewall only)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Import the device state information that was exported using the Export device state option. This includes the current running config, Panorama templates, and shared policies. If the device is a Global Protect Portal, the export includes the Certificate Authority (CA) information and the list of satellite devices and their authentication information.&lt;/P&gt;&lt;P&gt;//&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClRcCAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClRcCAK&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;best regards&lt;/P&gt;&lt;P&gt;Rob&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 24 Sep 2021 06:46:00 GMT</pubDate>
    <dc:creator>rdonohoe23</dc:creator>
    <dc:date>2021-09-24T06:46:00Z</dc:date>
    <item>
      <title>SD-WAN Hardware Change / Migration</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sd-wan-hardware-change-migration/m-p/435869#M96108</link>
      <description>&lt;P&gt;We have been running SD-WAN since release a year or so ago, regular PAN-OS SD-WAN not Prisma SD-WAN.&amp;nbsp; All the sites were deployed with PA-220 at the time, but we are rolling more sites in and I need to swap a couple of the PA-220s with a PA-440.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone done a hardware replacement of an SD-WAN device, that is being repurposed?&amp;nbsp; I followed along the migration guide, and I am afraid that the SD-WAN connection will break as soon as I commit.&amp;nbsp; Most of the settings are tied to the device in Panorama, and I am not confident that just loading an export will be enough, as behind the scenes the config is probably tied to the serial number.&amp;nbsp; I can think of a couple ways but they all seem more painful and error prone than they should be.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Sep 2021 14:56:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sd-wan-hardware-change-migration/m-p/435869#M96108</guid>
      <dc:creator>bschaper</dc:creator>
      <dc:date>2021-09-22T14:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: SD-WAN Hardware Change / Migration</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sd-wan-hardware-change-migration/m-p/436385#M96262</link>
      <description>&lt;P&gt;Hi Mate,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Export the device state from the PA-220 and import and load &lt;STRONG&gt;through the CLI&lt;/STRONG&gt; to the PA-400 series, that will have the merged configuration from Panorama. Make sure Panorama is running 10.1.x if adding in a PA-440. Connect the PA-440 to Panorama (point towards and add in auth key). Remove the PA-220 from the templates and device groups, and check the box for the PA-400 series.&lt;/P&gt;&lt;P&gt;If mission critical network I would look for a maintenance window.&amp;nbsp;&lt;/P&gt;&lt;P&gt;//&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Import device state (firewall only)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Import the device state information that was exported using the Export device state option. This includes the current running config, Panorama templates, and shared policies. If the device is a Global Protect Portal, the export includes the Certificate Authority (CA) information and the list of satellite devices and their authentication information.&lt;/P&gt;&lt;P&gt;//&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClRcCAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClRcCAK&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;best regards&lt;/P&gt;&lt;P&gt;Rob&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Sep 2021 06:46:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sd-wan-hardware-change-migration/m-p/436385#M96262</guid>
      <dc:creator>rdonohoe23</dc:creator>
      <dc:date>2021-09-24T06:46:00Z</dc:date>
    </item>
    <item>
      <title>Re: SD-WAN Hardware Change / Migration</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sd-wan-hardware-change-migration/m-p/436581#M96279</link>
      <description>&lt;P&gt;Have you tried this with a SD-WAN configuration? &amp;nbsp;The plug-in in Panorama has part of the configuration, and the device needs to be added there as well, along with deploying the sdwan plugin. I am afraid future commits will just break it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 25 Sep 2021 15:55:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sd-wan-hardware-change-migration/m-p/436581#M96279</guid>
      <dc:creator>bschaper</dc:creator>
      <dc:date>2021-09-25T15:55:55Z</dc:date>
    </item>
  </channel>
</rss>

