<?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: The best way/easiest way to migrate from 2 nos pair of PA 5250 &amp;amp; 5220 to a pair of PA 5450. in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/the-best-way-easiest-way-to-migrate-from-2-nos-pair-of-pa-5250/m-p/453336#M101347</link>
    <description>&lt;P&gt;Thanks for quick response , manually merging would be huge time consuming also could be error prone as we have total 20 nos vsys configuration from diff set of HA setup , many common setting, named policy like LACP bonding , zone, etc. Does Expedition tell if there is duplicate/shadow/override configuration while merging two configuration.&lt;/P&gt;&lt;P&gt;Is there any ways to do inplace migration with less downtime where in one shot , we can do all instances migrated to new setup?&lt;/P&gt;&lt;P&gt;Also thinking about in parallel migration , apart from time constrain is there any other risk is involve while planning to do batch wise vsys movement.?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 15 Dec 2021 09:45:36 GMT</pubDate>
    <dc:creator>souravpal</dc:creator>
    <dc:date>2021-12-15T09:45:36Z</dc:date>
    <item>
      <title>The best way/easiest way to migrate from 2 nos pair of PA 5250 &amp; 5220 to a pair of PA 5450.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/the-best-way-easiest-way-to-migrate-from-2-nos-pair-of-pa-5250/m-p/453180#M101326</link>
      <description>&lt;DIV&gt;&lt;STRONG&gt;Current setup :&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Multiple virtual instances running on a pair of 5250 and 5220 active-standby deployment each site.&lt;/DIV&gt;&lt;DIV&gt;Meaning 1 pair of 5250 + 1 pair of 5250 &amp;gt; 1 pair of 5450&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&lt;STRONG&gt;Target setup :&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;All virtual instances would be migrated/consolidated to a pair of 5450 modular hardware active-standby deployment each site.&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Note : Migration methodology should be less downtime involved and less complexity.&lt;/DIV&gt;&lt;DIV&gt;What would be easiest way to achieve the same also whether expedition tool can able to merge from two config to a single&lt;/DIV&gt;</description>
      <pubDate>Tue, 14 Dec 2021 13:37:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/the-best-way-easiest-way-to-migrate-from-2-nos-pair-of-pa-5250/m-p/453180#M101326</guid>
      <dc:creator>souravpal</dc:creator>
      <dc:date>2021-12-14T13:37:18Z</dc:date>
    </item>
    <item>
      <title>Re: The best way/easiest way to migrate from 2 nos pair of PA 5250 &amp; 5220 to a pair of PA 5450.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/the-best-way-easiest-way-to-migrate-from-2-nos-pair-of-pa-5250/m-p/453272#M101339</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/114389"&gt;@souravpal&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Expedition can merge multiple configurations, and you can also merge it manually if you're comfortable working with XML (heck, you could even merge it directly on the firewall if you wanted to). If you aren't comfortable working with XML, expedition is going to be the most "user friendly" way of doing so easily.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As for the migration itself, once you have the configuration built out you'll just want to manually go through and verify that everything actually is how it should be. Personally, when doing this sort of migration I like to take the time to go through everything and verify that I'm not moving over unused objects or rulebase entries that don't actually need to exist anymore. Use it to do a bit of "housekeeping" if you will.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Dec 2021 23:42:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/the-best-way-easiest-way-to-migrate-from-2-nos-pair-of-pa-5250/m-p/453272#M101339</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2021-12-14T23:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: The best way/easiest way to migrate from 2 nos pair of PA 5250 &amp; 5220 to a pair of PA 5450.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/the-best-way-easiest-way-to-migrate-from-2-nos-pair-of-pa-5250/m-p/453336#M101347</link>
      <description>&lt;P&gt;Thanks for quick response , manually merging would be huge time consuming also could be error prone as we have total 20 nos vsys configuration from diff set of HA setup , many common setting, named policy like LACP bonding , zone, etc. Does Expedition tell if there is duplicate/shadow/override configuration while merging two configuration.&lt;/P&gt;&lt;P&gt;Is there any ways to do inplace migration with less downtime where in one shot , we can do all instances migrated to new setup?&lt;/P&gt;&lt;P&gt;Also thinking about in parallel migration , apart from time constrain is there any other risk is involve while planning to do batch wise vsys movement.?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Dec 2021 09:45:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/the-best-way-easiest-way-to-migrate-from-2-nos-pair-of-pa-5250/m-p/453336#M101347</guid>
      <dc:creator>souravpal</dc:creator>
      <dc:date>2021-12-15T09:45:36Z</dc:date>
    </item>
  </channel>
</rss>

