<?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 cisco asa netflow in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-netflow/m-p/2118876#M393993</link>
    <description>&lt;P&gt;I am trying to configure netflow export on Cisco ASA firewalls.&lt;/P&gt;&lt;P&gt;I have done config and I can also see some packets exported to fluke. However I am not seeing any data on fluke. Is fluke a supported exporter for cisco ASA firewalls?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found this doc and it says there are problems with understanding Cisco ASA exports:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-wiki-small" href="https://community.cisco.com/docs/DOC-6113" target="_blank"&gt;https://supportforums.cisco.com/docs/DOC-6113&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are running 8.4 ASA code.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 00:38:01 GMT</pubDate>
    <dc:creator>Kashish_Patel</dc:creator>
    <dc:date>2019-03-12T00:38:01Z</dc:date>
    <item>
      <title>cisco asa netflow</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-netflow/m-p/2118876#M393993</link>
      <description>&lt;P&gt;I am trying to configure netflow export on Cisco ASA firewalls.&lt;/P&gt;&lt;P&gt;I have done config and I can also see some packets exported to fluke. However I am not seeing any data on fluke. Is fluke a supported exporter for cisco ASA firewalls?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found this doc and it says there are problems with understanding Cisco ASA exports:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-wiki-small" href="https://community.cisco.com/docs/DOC-6113" target="_blank"&gt;https://supportforums.cisco.com/docs/DOC-6113&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are running 8.4 ASA code.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:38:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-netflow/m-p/2118876#M393993</guid>
      <dc:creator>Kashish_Patel</dc:creator>
      <dc:date>2019-03-12T00:38:01Z</dc:date>
    </item>
    <item>
      <title>cisco asa netflow</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-netflow/m-p/2118877#M394004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Kashish,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the ASA perspective you can issue a "show flow-export counters" and check the "packets sent" section.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The netflow collector must comply with the ASA limitations, otherwise you will not get the correct data from the ASA. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please share tghe ASA configuration just to make sure you have the ASA configure in the proper way. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Juan Lombana&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate helpful posts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Dec 2012 13:13:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-netflow/m-p/2118877#M394004</guid>
      <dc:creator>julomban</dc:creator>
      <dc:date>2012-12-17T13:13:15Z</dc:date>
    </item>
    <item>
      <title>cisco asa netflow</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-netflow/m-p/2118878#M394019</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Kashish,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By any chance is your ASA running the latest version 8.4(5)?&amp;nbsp; If it is, Cisco implemented reverse bytes. You can read about it here: &lt;/P&gt;&lt;H2 id="post-18939"&gt;&lt;A href="http://www.plixer.com/blog/ipfix-2/cisco-asa-8-45-netflow-support/" rel="bookmark" title="Permanent Link: Cisco ASA 8.4(5) NetFlow Support"&gt;Cisco ASA 8.4(5) NetFlow Support&lt;/A&gt;&lt;/H2&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may need to call Fluke and ask them to post a patch.&amp;nbsp; This is an exciting release because it includes support for Active Timeout and a more standard way of exporting bidirectional flows.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this helps, please vote on my post.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sincerely,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jake Wilson&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netflowknights.com/"&gt;NetFlow Knight&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Dec 2012 14:32:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-netflow/m-p/2118878#M394019</guid>
      <dc:creator>jakewilson</dc:creator>
      <dc:date>2012-12-18T14:32:50Z</dc:date>
    </item>
    <item>
      <title>cisco asa netflow</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-netflow/m-p/2118879#M394031</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;fw1/hyd.shaw.net# sh flow-export counters &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;destination: inside 10.219.72.46 2055&lt;/P&gt;&lt;P&gt;&amp;nbsp; Statistics:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; packets sent&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1650073&lt;/P&gt;&lt;P&gt;&amp;nbsp; Errors:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; block allocation failure&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; invalid interface&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; template send failure&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; no route to collector&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What ASA limitations are you referring to? Please let me know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Dec 2012 06:31:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-netflow/m-p/2118879#M394031</guid>
      <dc:creator>Kashish_Patel</dc:creator>
      <dc:date>2012-12-24T06:31:53Z</dc:date>
    </item>
  </channel>
</rss>

