<?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: ASA removing ACL lines in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-removing-acl-lines/m-p/3189071#M1065865</link>
    <description>I figured as much. This is why you don't use ASDM for all your firewall configuration.</description>
    <pubDate>Mon, 25 Sep 2017 14:04:07 GMT</pubDate>
    <dc:creator>Steven Williams</dc:creator>
    <dc:date>2017-09-25T14:04:07Z</dc:date>
    <item>
      <title>ASA removing ACL lines</title>
      <link>https://community.cisco.com/t5/network-security/asa-removing-acl-lines/m-p/3188975#M1065861</link>
      <description>&lt;P&gt;So I am in this dilema where the person before me configured our internet ASA using all ASDM, so its hard to figure out what is what in the CLI since all I see is DM_INLINE_blah.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;for example:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access-list INSIDE_access_in line 15 extended permit object-group DM_INLINE_SERVICE_6 object-group DM_INLINE_NETWORK_9 any log informational interval 300 0x0aef5baa&lt;BR /&gt;access-list INSIDE_access_in line 15 extended permit tcp 10.0.0.0 255.0.0.0 any eq 1935 log informational interval 300 (hitcnt=2013) 0x8fb5bf4b&lt;BR /&gt;access-list INSIDE_access_in line 15 extended permit tcp ALL_172.16 255.255.0.0 any eq 1935 log informational interval 300 (hitcnt=0) 0x4f0c2f97&lt;BR /&gt;access-list INSIDE_access_in line 15 extended permit tcp ALL_172.26 255.255.0.0 any eq 1935 log informational interval 300 (hitcnt=0) 0x6e98f459&lt;BR /&gt;access-list INSIDE_access_in line 15 extended permit tcp 192.168.0.0 255.255.0.0 any eq 1935 log informational interval 300 (hitcnt=0) 0xb2262918&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As you can see some lines do not have hit counts and I want to remove them. Can I do this line by line or is going to mess something up?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can I do a "no&amp;nbsp;&amp;nbsp;access-list INSIDE_access_in line 15 extended permit tcp 192.168.0.0 255.255.0.0 any eq 1935"and have it take out that one line only?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Oh to make it better this is Code 8.2 &amp;nbsp;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:21:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-removing-acl-lines/m-p/3188975#M1065861</guid>
      <dc:creator>Steven Williams</dc:creator>
      <dc:date>2020-02-21T14:21:30Z</dc:date>
    </item>
    <item>
      <title>Re: ASA removing ACL lines</title>
      <link>https://community.cisco.com/t5/network-security/asa-removing-acl-lines/m-p/3189043#M1065862</link>
      <description>&lt;P&gt;Hi Steven,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Run the following command to check which subnets are there in the object-group:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;show run object-group id DM_INLINE_NETWORK_9&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Then remove those are not required as below:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;object-group network DM_INLINE_NETWORK_9&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;no network-object 192.168.0.0 255.255.0.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"no" in front of network-object will remove subnet from the object, so in this way the ACL line will also be removed.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Sep 2017 13:30:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-removing-acl-lines/m-p/3189043#M1065862</guid>
      <dc:creator>Spooster IT Services</dc:creator>
      <dc:date>2017-09-25T13:30:39Z</dc:date>
    </item>
    <item>
      <title>Re: ASA removing ACL lines</title>
      <link>https://community.cisco.com/t5/network-security/asa-removing-acl-lines/m-p/3189067#M1065863</link>
      <description>The issue with removing the network object is that the acl has multiple ports tied to it. So while 192.168.0.0 255.255.0.0 may not be using port 80 its using port 1433 in the same ACE.</description>
      <pubDate>Mon, 25 Sep 2017 13:59:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-removing-acl-lines/m-p/3189067#M1065863</guid>
      <dc:creator>Steven Williams</dc:creator>
      <dc:date>2017-09-25T13:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: ASA removing ACL lines</title>
      <link>https://community.cisco.com/t5/network-security/asa-removing-acl-lines/m-p/3189070#M1065864</link>
      <description>&lt;P&gt;Hi Steven,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this case you need to create multiple object-group for ports and define accordingly.&lt;/P&gt;&lt;P&gt;But there is no way to delete a single ACE without removing subnet from object group.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Sep 2017 14:02:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-removing-acl-lines/m-p/3189070#M1065864</guid>
      <dc:creator>Spooster IT Services</dc:creator>
      <dc:date>2017-09-25T14:02:37Z</dc:date>
    </item>
    <item>
      <title>Re: ASA removing ACL lines</title>
      <link>https://community.cisco.com/t5/network-security/asa-removing-acl-lines/m-p/3189071#M1065865</link>
      <description>I figured as much. This is why you don't use ASDM for all your firewall configuration.</description>
      <pubDate>Mon, 25 Sep 2017 14:04:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-removing-acl-lines/m-p/3189071#M1065865</guid>
      <dc:creator>Steven Williams</dc:creator>
      <dc:date>2017-09-25T14:04:07Z</dc:date>
    </item>
  </channel>
</rss>

