<?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 Troubleshooting the ASA tip: in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/troubleshooting-the-asa-tip/m-p/1443746#M662338</link>
    <description>&lt;P&gt;Troubleshooting the ASA tip:&lt;BR /&gt;If you're like me, you perform MANY different tasks throughout the day.&lt;BR /&gt;Many times, I am duplicating the same work at different times throughout the day.&lt;BR /&gt;It takes a lot of time to figure out and setup a capture session each time I need to determine what is going through my firewall or getting blocked before it gets to my firewall. Finally I realized the same exact traffic flow capture filters were being configured, used and then deleted.&lt;BR /&gt;I now have created permanent ACLs to assist troubleshooting the most common tasks.&lt;BR /&gt;I perform a sh run, scroll down to the "cap" acl section, highlight syntax, copy and paste, done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Line 1 of each acl has the syntax to capture my most common data flows.&lt;BR /&gt;Line 2 of each acl has the copy syntax to place the captured raw data onto the Wireshark traffic analyzer/TFTP server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hugh time saver!&lt;BR /&gt;----&lt;BR /&gt;---- Please note: Our firewall is under utilized (running at 2%), &lt;BR /&gt;---- Performing a capture on your firewall must be deamed safe by&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; YOU . . . BEFORE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; trying this else you could be looking for another job.&lt;BR /&gt;---- Remember to terminate your capture when done - no capture #.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list cap-research line 1 REMARK capture 1 access-list cap-research int research real det&lt;BR /&gt;access-list cap-research line 2 REMAKR copy /pcap capture:1 tftp&lt;BR /&gt;!&lt;BR /&gt;access-list cap-research line 3 extended deny ip host 10.99.4.1 host 10.99.4.2 &lt;BR /&gt;access-list cap-research line 4 extended deny ip host 10.99.4.2 host 10.99.4.1&lt;BR /&gt;access-list cap-research line 5 REMARK Ignore firewall-to-firewall keepalives&lt;BR /&gt;!&lt;BR /&gt;access-list cap-research line 6 extended permit ip any host 10.99.4.5&lt;BR /&gt;access-list cap-research line 7 REMARK ingress packets on interface Research&lt;BR /&gt;!&lt;BR /&gt;access-list cap-research line 8 extended permit ip host 10.99.4.5 any &lt;BR /&gt;access-list cap-research line 9 REMARK egress packets on interface Research&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!################################# for clarity&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list cap-eng line 1 REMARK capture 2 access-list cap-eng int eng real det&lt;BR /&gt;access-list cap-eng line 2 REMARK copy /pcap capture:2 tftp&lt;BR /&gt;!&lt;BR /&gt;access-list cap-eng line 3 extended deny ip host 10.91.0.1 host 10.91.0.2 &lt;BR /&gt;access-list cap-eng line 4 extended deny ip host 10.91.0.2 host 10.91.0.1&lt;BR /&gt;access-list cap-eng line 5 REMARK Ignore firewall-to-firewall keepalives&lt;BR /&gt;!&lt;BR /&gt;access-list cap-eng line 6 extended permit TCP any host 10.91.0.33&lt;BR /&gt;access-list cap-eng line 7 REMARK ingress packets on interface ENG&lt;BR /&gt;!&lt;BR /&gt;access-list cap-eng line 8 extended permit TCP host 10.91.0.33 any &lt;BR /&gt;access-list cap-eng line 9 REMARK egress packets on interface ENG&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!################################# for clarity&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list cap-inventory line 1 REMARK capture 3 access-list cap-inventory int inventory real det&lt;BR /&gt;access-list cap-inventory line 2 REMARK copy /pcap capture:3 tftp&lt;BR /&gt;!&lt;BR /&gt;access-list cap-inventory line 3 extended deny ip host 10.3.16.1 host 10.3.16.2 &lt;BR /&gt;access-list cap-inventory line 4 extended deny ip host 10.3.16.2 host 10.3.16.1&lt;BR /&gt;access-list cap-inventory line 5 REMARK Ignore firewall-to-firewall keepalives&lt;BR /&gt;!&lt;BR /&gt;access-list cap-inventory line 6 extended permit UDP any host 10.3.16.15&lt;BR /&gt;access-list cap-inventory line 7 REMARK ingress packets on interface inventory&lt;BR /&gt;!&lt;BR /&gt;access-list cap-inventory line 8 extended permit UDP host 10.3.16.15 any &lt;BR /&gt;access-list cap-inventory line 9 REMARK egress packets on interface inventory&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;Frank&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 18:05:44 GMT</pubDate>
    <dc:creator>fsebera</dc:creator>
    <dc:date>2019-03-11T18:05:44Z</dc:date>
    <item>
      <title>Troubleshooting the ASA tip:</title>
      <link>https://community.cisco.com/t5/network-security/troubleshooting-the-asa-tip/m-p/1443746#M662338</link>
      <description>&lt;P&gt;Troubleshooting the ASA tip:&lt;BR /&gt;If you're like me, you perform MANY different tasks throughout the day.&lt;BR /&gt;Many times, I am duplicating the same work at different times throughout the day.&lt;BR /&gt;It takes a lot of time to figure out and setup a capture session each time I need to determine what is going through my firewall or getting blocked before it gets to my firewall. Finally I realized the same exact traffic flow capture filters were being configured, used and then deleted.&lt;BR /&gt;I now have created permanent ACLs to assist troubleshooting the most common tasks.&lt;BR /&gt;I perform a sh run, scroll down to the "cap" acl section, highlight syntax, copy and paste, done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Line 1 of each acl has the syntax to capture my most common data flows.&lt;BR /&gt;Line 2 of each acl has the copy syntax to place the captured raw data onto the Wireshark traffic analyzer/TFTP server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hugh time saver!&lt;BR /&gt;----&lt;BR /&gt;---- Please note: Our firewall is under utilized (running at 2%), &lt;BR /&gt;---- Performing a capture on your firewall must be deamed safe by&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; YOU . . . BEFORE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; trying this else you could be looking for another job.&lt;BR /&gt;---- Remember to terminate your capture when done - no capture #.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list cap-research line 1 REMARK capture 1 access-list cap-research int research real det&lt;BR /&gt;access-list cap-research line 2 REMAKR copy /pcap capture:1 tftp&lt;BR /&gt;!&lt;BR /&gt;access-list cap-research line 3 extended deny ip host 10.99.4.1 host 10.99.4.2 &lt;BR /&gt;access-list cap-research line 4 extended deny ip host 10.99.4.2 host 10.99.4.1&lt;BR /&gt;access-list cap-research line 5 REMARK Ignore firewall-to-firewall keepalives&lt;BR /&gt;!&lt;BR /&gt;access-list cap-research line 6 extended permit ip any host 10.99.4.5&lt;BR /&gt;access-list cap-research line 7 REMARK ingress packets on interface Research&lt;BR /&gt;!&lt;BR /&gt;access-list cap-research line 8 extended permit ip host 10.99.4.5 any &lt;BR /&gt;access-list cap-research line 9 REMARK egress packets on interface Research&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!################################# for clarity&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list cap-eng line 1 REMARK capture 2 access-list cap-eng int eng real det&lt;BR /&gt;access-list cap-eng line 2 REMARK copy /pcap capture:2 tftp&lt;BR /&gt;!&lt;BR /&gt;access-list cap-eng line 3 extended deny ip host 10.91.0.1 host 10.91.0.2 &lt;BR /&gt;access-list cap-eng line 4 extended deny ip host 10.91.0.2 host 10.91.0.1&lt;BR /&gt;access-list cap-eng line 5 REMARK Ignore firewall-to-firewall keepalives&lt;BR /&gt;!&lt;BR /&gt;access-list cap-eng line 6 extended permit TCP any host 10.91.0.33&lt;BR /&gt;access-list cap-eng line 7 REMARK ingress packets on interface ENG&lt;BR /&gt;!&lt;BR /&gt;access-list cap-eng line 8 extended permit TCP host 10.91.0.33 any &lt;BR /&gt;access-list cap-eng line 9 REMARK egress packets on interface ENG&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!################################# for clarity&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list cap-inventory line 1 REMARK capture 3 access-list cap-inventory int inventory real det&lt;BR /&gt;access-list cap-inventory line 2 REMARK copy /pcap capture:3 tftp&lt;BR /&gt;!&lt;BR /&gt;access-list cap-inventory line 3 extended deny ip host 10.3.16.1 host 10.3.16.2 &lt;BR /&gt;access-list cap-inventory line 4 extended deny ip host 10.3.16.2 host 10.3.16.1&lt;BR /&gt;access-list cap-inventory line 5 REMARK Ignore firewall-to-firewall keepalives&lt;BR /&gt;!&lt;BR /&gt;access-list cap-inventory line 6 extended permit UDP any host 10.3.16.15&lt;BR /&gt;access-list cap-inventory line 7 REMARK ingress packets on interface inventory&lt;BR /&gt;!&lt;BR /&gt;access-list cap-inventory line 8 extended permit UDP host 10.3.16.15 any &lt;BR /&gt;access-list cap-inventory line 9 REMARK egress packets on interface inventory&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;Frank&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:05:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/troubleshooting-the-asa-tip/m-p/1443746#M662338</guid>
      <dc:creator>fsebera</dc:creator>
      <dc:date>2019-03-11T18:05:44Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting the ASA tip:</title>
      <link>https://community.cisco.com/t5/network-security/troubleshooting-the-asa-tip/m-p/1443747#M662349</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Frank,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is a great tip!&amp;nbsp; You are exactly right.&amp;nbsp; One other item that makes this easier is the command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show run access-list | inc cap&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will show all access-lists that are configured that include the word 'cap' - if you have alot of access-lists on your ASA, this one will also save some time and frustrations.&amp;nbsp; The 'show run &lt;X&gt; | inc &lt;Y&gt;' command can be useful for &lt;X&gt; = static, nat, route, interface, etc.&lt;/X&gt;&lt;/Y&gt;&lt;/X&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please mark this thread as "answered" so others can know to reference it in the future!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again for the great tip! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kevin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jun 2010 20:42:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/troubleshooting-the-asa-tip/m-p/1443747#M662349</guid>
      <dc:creator>Kevin Redmon</dc:creator>
      <dc:date>2010-06-30T20:42:08Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting the ASA tip:</title>
      <link>https://community.cisco.com/t5/network-security/troubleshooting-the-asa-tip/m-p/1443748#M662384</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Frank,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is a great tip!&amp;nbsp; You are exactly right.&amp;nbsp; One other item that makes this easier is the command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show run access-list | inc cap&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will show all access-lists that are configured that include the word 'cap' - if you have alot of access-lists on your ASA, this one will also save some time and frustrations.&amp;nbsp; The 'show run &lt;X&gt; | inc &lt;Y&gt;' command can be useful for &lt;X&gt; = static, nat, route, interface, etc.&lt;/X&gt;&lt;/Y&gt;&lt;/X&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please mark this thread as "answered" so others can know to reference it in the future!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again for the great tip! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kevin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jun 2010 20:42:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/troubleshooting-the-asa-tip/m-p/1443748#M662384</guid>
      <dc:creator>Kevin Redmon</dc:creator>
      <dc:date>2010-06-30T20:42:12Z</dc:date>
    </item>
  </channel>
</rss>

