<?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: Cisco ASA ACL applied to global in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/cisco-asa-acl-applied-to-global/m-p/288974#M2012</link>
    <description>&lt;P&gt;Actually it turns out the config did get migrated correctly. It appears that the ACL entries for the global access-group get distributed to zones based on routes which I did not realize at first.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the quick response.&lt;/P&gt;</description>
    <pubDate>Wed, 18 Sep 2019 16:17:34 GMT</pubDate>
    <dc:creator>aporue</dc:creator>
    <dc:date>2019-09-18T16:17:34Z</dc:date>
    <item>
      <title>Cisco ASA ACL applied to global</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/cisco-asa-acl-applied-to-global/m-p/288790#M2009</link>
      <description>&lt;P&gt;I am migrating a Cisco ASA config that has an ACL that is applied to global (access-group CSM_FW_ACL_ in interface if_global) as opposed to an interface. I believe I understand how this is applied in the ASA but noticed that Expedition did nothing with the ACL as far as I can tell. Is there a way to handle this in Expedition to make it work? If not does anyone no another way to convert this ACL outside of Expedition? It is an extremely large ACL, otherwise I would just do it by hand.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Sep 2019 15:11:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/cisco-asa-acl-applied-to-global/m-p/288790#M2009</guid>
      <dc:creator>aporue</dc:creator>
      <dc:date>2019-09-17T15:11:09Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA ACL applied to global</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/cisco-asa-acl-applied-to-global/m-p/288906#M2010</link>
      <description>&lt;P&gt;HI,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;we like to get more information about your Cisco ASA configuration and version you are figuring out this issue.&lt;BR /&gt;Can you please get in touch with us via fwmigrate@paloaltonetworks.com or send me a private message here?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;regards&lt;/P&gt;
&lt;P&gt;Sven Waschkut&lt;BR /&gt;Solution Engineer, Expedition&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2019 09:21:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/cisco-asa-acl-applied-to-global/m-p/288906#M2010</guid>
      <dc:creator>swaschkut</dc:creator>
      <dc:date>2019-09-18T09:21:49Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA ACL applied to global</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/cisco-asa-acl-applied-to-global/m-p/288974#M2012</link>
      <description>&lt;P&gt;Actually it turns out the config did get migrated correctly. It appears that the ACL entries for the global access-group get distributed to zones based on routes which I did not realize at first.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the quick response.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2019 16:17:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/cisco-asa-acl-applied-to-global/m-p/288974#M2012</guid>
      <dc:creator>aporue</dc:creator>
      <dc:date>2019-09-18T16:17:34Z</dc:date>
    </item>
  </channel>
</rss>

