<?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 ASA5505 latency in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385142#M308661</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need to know how much traffic and what type of traffic goes through your firewall to understand what could be causing latency. You also need to check basic things like interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have Cisco switches you can configure Netflow to collect all this information if you do not you can configure netflow on the ASA but it has its limitations regarding not giving out real time statistics based on the fact that it needs the connection to be built and when it is teardown it gives out info to build a report.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Nov 2013 17:50:14 GMT</pubDate>
    <dc:creator>jumora</dc:creator>
    <dc:date>2013-11-19T17:50:14Z</dc:date>
    <item>
      <title>ASA5505 latency</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385140#M308658</link>
      <description>&lt;P&gt;We need a firewall on our VOIP traffic. Our provider says the device must have a maxium latency of 2ms. Having searched the spec in the Cisco docs on this device and having found nothing on it's latency I wondered if anyone on here might know?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 03:06:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385140#M308658</guid>
      <dc:creator>Rhys Davies</dc:creator>
      <dc:date>2019-03-12T03:06:45Z</dc:date>
    </item>
    <item>
      <title>ASA5505 latency</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385141#M308659</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would think that you might be more likely to get answers to this question if you moved it to the firewalls forum.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Nov 2013 12:28:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385141#M308659</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2013-11-19T12:28:56Z</dc:date>
    </item>
    <item>
      <title>ASA5505 latency</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385142#M308661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need to know how much traffic and what type of traffic goes through your firewall to understand what could be causing latency. You also need to check basic things like interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have Cisco switches you can configure Netflow to collect all this information if you do not you can configure netflow on the ASA but it has its limitations regarding not giving out real time statistics based on the fact that it needs the connection to be built and when it is teardown it gives out info to build a report.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Nov 2013 17:50:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385142#M308661</guid>
      <dc:creator>jumora</dc:creator>
      <dc:date>2013-11-19T17:50:14Z</dc:date>
    </item>
    <item>
      <title>ASA5505 latency</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385143#M308662</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;H2&gt;Netflow on ASA&lt;/H2&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-wiki-small" href="https://community.cisco.com/docs/DOC-6113"&gt;https://supportforums.cisco.com/docs/DOC-6113&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Nov 2013 17:51:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385143#M308662</guid>
      <dc:creator>jumora</dc:creator>
      <dc:date>2013-11-19T17:51:54Z</dc:date>
    </item>
    <item>
      <title>ASA5505 latency</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385144#M308664</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This video is really nice:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://media.plixer.com/screencasts/ciscoAsaConfigurationUsingAsdm/ciscoAsaConfigurationUsingAsdm.html"&gt;http://media.plixer.com/screencasts/ciscoAsaConfigurationUsingAsdm/ciscoAsaConfigurationUsingAsdm.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Nov 2013 17:53:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385144#M308664</guid>
      <dc:creator>jumora</dc:creator>
      <dc:date>2013-11-19T17:53:08Z</dc:date>
    </item>
    <item>
      <title>ASA5505 latency</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385145#M308665</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok thanks Jumora. It looks like there is a no set number for latency then - it's something we have to discover ourselves.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Nov 2013 14:31:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-latency/m-p/2385145#M308665</guid>
      <dc:creator>Rhys Davies</dc:creator>
      <dc:date>2013-11-20T14:31:51Z</dc:date>
    </item>
  </channel>
</rss>

