<?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 Migrating Cisco multi-contexts into one vsys Palo Alto firewall in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/migrating-cisco-multi-contexts-into-one-vsys-palo-alto-firewall/m-p/1251107#M126207</link>
    <description>&lt;P&gt;Hi there,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="3,0"&gt;We are looking to migrate a Cisco ASA 5545 with two contexts (Internet and LAN) to a PA-1420. We don't have a multi-vsys license, so everything needs to be merged into a single vsys. We’ll be managing the PA locally (no Panorama) and using the Expedition tool for the migration.&lt;/P&gt;
&lt;P data-path-to-node="3,1"&gt;Is it possible to merge both ASA contexts into one vsys? If so, what is the best way to achieve this? I know we can use two Virtual Routers (VRs) to keep the routing tables separate, but I'm unsure about the best approach for merging the security policies, objects, and services.&lt;/P&gt;
&lt;P data-path-to-node="3,1"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="3,1"&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Sat, 28 Mar 2026 16:29:58 GMT</pubDate>
    <dc:creator>AK74</dc:creator>
    <dc:date>2026-03-28T16:29:58Z</dc:date>
    <item>
      <title>Migrating Cisco multi-contexts into one vsys Palo Alto firewall</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/migrating-cisco-multi-contexts-into-one-vsys-palo-alto-firewall/m-p/1251107#M126207</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="3,0"&gt;We are looking to migrate a Cisco ASA 5545 with two contexts (Internet and LAN) to a PA-1420. We don't have a multi-vsys license, so everything needs to be merged into a single vsys. We’ll be managing the PA locally (no Panorama) and using the Expedition tool for the migration.&lt;/P&gt;
&lt;P data-path-to-node="3,1"&gt;Is it possible to merge both ASA contexts into one vsys? If so, what is the best way to achieve this? I know we can use two Virtual Routers (VRs) to keep the routing tables separate, but I'm unsure about the best approach for merging the security policies, objects, and services.&lt;/P&gt;
&lt;P data-path-to-node="3,1"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="3,1"&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 28 Mar 2026 16:29:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/migrating-cisco-multi-contexts-into-one-vsys-palo-alto-firewall/m-p/1251107#M126207</guid>
      <dc:creator>AK74</dc:creator>
      <dc:date>2026-03-28T16:29:58Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating Cisco multi-contexts into one vsys Palo Alto firewall</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/migrating-cisco-multi-contexts-into-one-vsys-palo-alto-firewall/m-p/1251124#M126209</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/169335"&gt;@AK74&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;Is it possible to merge both ASA contexts into one vsys?&lt;/STRONG&gt;&amp;nbsp; Yes.&amp;nbsp; In my opinion, separate vsys are for separate administration and separate VRs are for segmentation.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;If so, what is the best way to achieve this?&lt;/STRONG&gt;&amp;nbsp; Using 2 VRs is the way.&amp;nbsp; You don't need separate security policies.&amp;nbsp; Each VR should have unique zones which ensure the security policy rules only apply to one VR at a time.&amp;nbsp; You can divide your security policy into 2 sections, one for each VR.&amp;nbsp; You could even use tags to group your security policy so that you can manage them separately.&amp;nbsp; Because of the different zones, it is effectively 2 security policies.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I wouldn't worry about the NGFW having the same objects and services to be used by both VRs,&amp;nbsp; The policies and zones determine which is used for each VR.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Tom&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 29 Mar 2026 17:53:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/migrating-cisco-multi-contexts-into-one-vsys-palo-alto-firewall/m-p/1251124#M126209</guid>
      <dc:creator>TomYoung</dc:creator>
      <dc:date>2026-03-29T17:53:52Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating Cisco multi-contexts into one vsys Palo Alto firewall</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/migrating-cisco-multi-contexts-into-one-vsys-palo-alto-firewall/m-p/1251253#M126222</link>
      <description>&lt;P&gt;Thank you so much, Tom&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'll test it and let you know&lt;/P&gt;</description>
      <pubDate>Tue, 31 Mar 2026 07:29:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/migrating-cisco-multi-contexts-into-one-vsys-palo-alto-firewall/m-p/1251253#M126222</guid>
      <dc:creator>AK74</dc:creator>
      <dc:date>2026-03-31T07:29:34Z</dc:date>
    </item>
  </channel>
</rss>

