<?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 minimum throughput in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-minimum-throughput/m-p/1666456#M562502</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Many thanks for your help on this!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 12 May 2011 00:20:41 GMT</pubDate>
    <dc:creator>lcaruso</dc:creator>
    <dc:date>2011-05-12T00:20:41Z</dc:date>
    <item>
      <title>ASA minimum throughput</title>
      <link>https://community.cisco.com/t5/network-security/asa-minimum-throughput/m-p/1666454#M562489</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need a firewall that has an absolutely worst case throughput of 500Mb/s sustained with all security features enabled.I'm looking at the 5550 platform as meeting this requirement, but would like comments.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does the way Cisco specs their throughput with vpn throughput accurately represent this worst case?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the 5550 vpn throughput is 425Mb/s, does that mean if all traffic was vpn traffic that is what I'd be guranteed to get?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do they mean that worst case is when all connections are vpn?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate if someone can clear me up on the worst case throughput specification. Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:32:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-minimum-throughput/m-p/1666454#M562489</guid>
      <dc:creator>lcaruso</dc:creator>
      <dc:date>2019-03-11T20:32:25Z</dc:date>
    </item>
    <item>
      <title>Re: ASA minimum throughput</title>
      <link>https://community.cisco.com/t5/network-security/asa-minimum-throughput/m-p/1666455#M562496</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest you to contact your Account manager from Cisco that can provide you the best option, based on tested scenarios and so on. Here is an extract of what I consider, by far the best document that explains causes of oversubscription&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;"....Let's use the ASA5510 as an example. Its name throughput is 300Mbps, as&amp;nbsp; we see on the table above. So the question is, "if my ASA5510 sees about&amp;nbsp; 280Mbps should it be 100% CPU or not?". A quick answer would be "No".&amp;nbsp; Though, we must not forget that there are many factors involved in this&amp;nbsp; question. In the network industry name speeds of devices come out under&amp;nbsp; certain tests. These tests are repeated and an average is presented as&amp;nbsp; the maximum speed. Though, not always is "real-world" traffic the same&amp;nbsp; traffic as the one used in the tests. We could use the aforementioned&amp;nbsp; ASA5510 for example. Usually, the name speed tests involve stateless&amp;nbsp; protocols with big packets. For a TCP web browsing application though,&amp;nbsp; the packets are much smaller and TCP uses ACKs and is a "synchronized"&amp;nbsp; protocol by nature. That would add more load to the firewall itself,&amp;nbsp; which would make its maximum throughput value drop. On top of that, if&amp;nbsp; the ASA has http inspection configured (which will do deep packet&amp;nbsp; inspection for http) then we understand that its maximum processing&amp;nbsp; throughput would be less than 280Mbps. It is obvious that even though&amp;nbsp; 300Mbps is indeed the throughput the device can achieve, its real-world&amp;nbsp; throughput, based on applications, traffic nature and configuration&amp;nbsp; could practically be less. That is why in our performance documents we&amp;nbsp; also try to provide other metrics. These include the "packets per&amp;nbsp; seconds" (pps) and what is often seen as "real-world HTTP". For example&amp;nbsp; in the ASA table we can see that the 5510 can do 190K pps (small 64-byte&amp;nbsp; packets). These metrics could also be used against the interface&amp;nbsp; statistics collected from the device in order to decide if the box is&amp;nbsp; pusehd to its limits...."&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-wiki-small" href="https://community.cisco.com/docs/DOC-12439"&gt;https://supportforums.cisco.com/docs/DOC-12439&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My point is, not because it is documented, it means that is going to support that amount of traffic, it does have a number of variables that need to be taken in consideraration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers.&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 May 2011 23:33:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-minimum-throughput/m-p/1666455#M562496</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2011-05-11T23:33:37Z</dc:date>
    </item>
    <item>
      <title>Re: ASA minimum throughput</title>
      <link>https://community.cisco.com/t5/network-security/asa-minimum-throughput/m-p/1666456#M562502</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Many thanks for your help on this!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 May 2011 00:20:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-minimum-throughput/m-p/1666456#M562502</guid>
      <dc:creator>lcaruso</dc:creator>
      <dc:date>2011-05-12T00:20:41Z</dc:date>
    </item>
  </channel>
</rss>

