<?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 Multiple tunnel migration from ASA to PAN (zone per tunnel not desired) in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/multiple-tunnel-migration-from-asa-to-pan-zone-per-tunnel-not/m-p/565167#M4832</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am working on a migration where the source ASA has 74 VPN L2L tunnels (to remote stores using same config) and the migration tool has created individual ACLs and Zones for each. This makes managing them tedious and would prefer to have a single zone named VPN STORES and all tunnel interfaces within that zone and one ACL. Is there a method to do this in Expedition? Any help would be appreciated!&lt;/P&gt;</description>
    <pubDate>Fri, 10 Nov 2023 15:21:38 GMT</pubDate>
    <dc:creator>jakegibb2077</dc:creator>
    <dc:date>2023-11-10T15:21:38Z</dc:date>
    <item>
      <title>Multiple tunnel migration from ASA to PAN (zone per tunnel not desired)</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/multiple-tunnel-migration-from-asa-to-pan-zone-per-tunnel-not/m-p/565167#M4832</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am working on a migration where the source ASA has 74 VPN L2L tunnels (to remote stores using same config) and the migration tool has created individual ACLs and Zones for each. This makes managing them tedious and would prefer to have a single zone named VPN STORES and all tunnel interfaces within that zone and one ACL. Is there a method to do this in Expedition? Any help would be appreciated!&lt;/P&gt;</description>
      <pubDate>Fri, 10 Nov 2023 15:21:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/multiple-tunnel-migration-from-asa-to-pan-zone-per-tunnel-not/m-p/565167#M4832</guid>
      <dc:creator>jakegibb2077</dc:creator>
      <dc:date>2023-11-10T15:21:38Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple tunnel migration from ASA to PAN (zone per tunnel not desired)</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/multiple-tunnel-migration-from-asa-to-pan-zone-per-tunnel-not/m-p/565301#M4835</link>
      <description>&lt;P&gt;For the benefit of others, posting an update on solution discussed with&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/23502"&gt;@jakegibb2077&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;This can be achieved with the following steps:&lt;BR /&gt;- Use a filter and detach the tunnel interfaces from the zones.&amp;nbsp;&lt;BR /&gt;- Create a new zone or pick an existing zone to use for all tunnels&lt;BR /&gt;- Attach all the tunnel interfaces to the selected zone.&lt;BR /&gt;Keep in mind the security policies also need to be updated to reference this selected zone.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Nov 2023 06:12:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/multiple-tunnel-migration-from-asa-to-pan-zone-per-tunnel-not/m-p/565301#M4835</guid>
      <dc:creator>sanandh</dc:creator>
      <dc:date>2023-11-13T06:12:45Z</dc:date>
    </item>
  </channel>
</rss>

