<?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: Migration from Palo Alto Multivsys to single Vsys in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/migration-from-palo-alto-multivsys-to-single-vsys/m-p/315998#M81328</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/101331"&gt;@SureshBalaji&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It should be straight forward but it will take a bit of time of planning, if each vsys has their own untrust interface and address space, that should be pretty easy.&amp;nbsp; On the multi vsys one, security, nat polcies, etc are all in set vsys vsysX stazes.&amp;nbsp; Just need to change from set vsys vsys2 rulebase and update to set rulebase.&amp;nbsp; You can manually edit in XML (if you are comfortable) or you can do it via the set command set as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;E&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 12 Mar 2020 12:53:52 GMT</pubDate>
    <dc:creator>nextgenhappines</dc:creator>
    <dc:date>2020-03-12T12:53:52Z</dc:date>
    <item>
      <title>Migration from Palo Alto Multivsys to single Vsys</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/migration-from-palo-alto-multivsys-to-single-vsys/m-p/315857#M81310</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;Is there a we can migrate a PA 5050 multivsys configuration from one appliance and migrate it to two different 3220 appliances. Where Each Vsys from single PA 5050 goes to different 3220 appliance. For instance (Vsys1-PA 5050) should converted to one (PA 3220) and another (Vsys2 -5050) goes to second 3220 appliance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Mar 2020 19:20:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/migration-from-palo-alto-multivsys-to-single-vsys/m-p/315857#M81310</guid>
      <dc:creator>SureshBalaji</dc:creator>
      <dc:date>2020-03-11T19:20:16Z</dc:date>
    </item>
    <item>
      <title>Re: Migration from Palo Alto Multivsys to single Vsys</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/migration-from-palo-alto-multivsys-to-single-vsys/m-p/315998#M81328</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/101331"&gt;@SureshBalaji&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It should be straight forward but it will take a bit of time of planning, if each vsys has their own untrust interface and address space, that should be pretty easy.&amp;nbsp; On the multi vsys one, security, nat polcies, etc are all in set vsys vsysX stazes.&amp;nbsp; Just need to change from set vsys vsys2 rulebase and update to set rulebase.&amp;nbsp; You can manually edit in XML (if you are comfortable) or you can do it via the set command set as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;E&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Mar 2020 12:53:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/migration-from-palo-alto-multivsys-to-single-vsys/m-p/315998#M81328</guid>
      <dc:creator>nextgenhappines</dc:creator>
      <dc:date>2020-03-12T12:53:52Z</dc:date>
    </item>
    <item>
      <title>Re: Migration from Palo Alto Multivsys to single Vsys</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/migration-from-palo-alto-multivsys-to-single-vsys/m-p/335529#M84553</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/101331"&gt;@SureshBalaji&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One easy way of achieving this if you do have Panorama integration is, use the article below&amp;nbsp;to export 5020 multivsys config to Panorama where each vsys will be segregated to different device-group and template . Then add your new 3220 devices to same panorama and push this configuration to each devices separately.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then go to each 3220 device and select disable device group and template in Device&amp;gt;setup&amp;gt;management&amp;gt; panorama configuration , where you can make all Panorama pushed config into local config.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/panorama/9-0/panorama-admin/manage-firewalls/transition-a-firewall-to-panorama-management/migrate-a-firewall-to-panorama-management" target="_blank"&gt;https://docs.paloaltonetworks.com/panorama/9-0/panorama-admin/manage-firewalls/transition-a-firewall-to-panorama-management/migrate-a-firewall-to-panorama-management&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jun 2020 13:45:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/migration-from-palo-alto-multivsys-to-single-vsys/m-p/335529#M84553</guid>
      <dc:creator>skumar1</dc:creator>
      <dc:date>2020-06-26T13:45:25Z</dc:date>
    </item>
  </channel>
</rss>

