<?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: firewalling in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewalling/m-p/1681145#M558339</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashish,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you aware of the rate of traffic going through the link, when you see increase in overruns?&lt;/P&gt;&lt;P&gt;Overruns indicate that the rate of packets coming on the interface is so high, that the ASA is unable to pick the packet off the wire.&lt;/P&gt;&lt;P&gt;If that's the case then you would need to see if that rate of traffic is normal. If it is then you might need to divide the traffic somehow between 2 interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please attach the output of "show tech" if possible. The block usage and traffic statistics along with the config might help in determining why there are overruns.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Also, please check that the speed and duplex settings are hardcoded rather than set to &lt;STRONG&gt;auto &lt;/STRONG&gt;on both ends.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Shrikant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 07 Apr 2011 13:51:04 GMT</pubDate>
    <dc:creator>Shrikant Sundaresh</dc:creator>
    <dc:date>2011-04-07T13:51:04Z</dc:date>
    <item>
      <title>firewalling</title>
      <link>https://community.cisco.com/t5/network-security/firewalling/m-p/1681144#M558333</link>
      <description>&lt;P&gt;Hi, i have a 5520 ASA which is connected to 2811 router , the issue is that on the outside interface which is connected to router lots of input errors and overruns is observed due to which lot of latency is faced by outside vpn users when they connect. need some solution on the same.. we have change the cable and speed duplex setting already..&lt;/P&gt;&lt;P&gt;thanks..&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:18:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewalling/m-p/1681144#M558333</guid>
      <dc:creator>ashishdpatel1</dc:creator>
      <dc:date>2019-03-11T20:18:07Z</dc:date>
    </item>
    <item>
      <title>Re: firewalling</title>
      <link>https://community.cisco.com/t5/network-security/firewalling/m-p/1681145#M558339</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashish,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you aware of the rate of traffic going through the link, when you see increase in overruns?&lt;/P&gt;&lt;P&gt;Overruns indicate that the rate of packets coming on the interface is so high, that the ASA is unable to pick the packet off the wire.&lt;/P&gt;&lt;P&gt;If that's the case then you would need to see if that rate of traffic is normal. If it is then you might need to divide the traffic somehow between 2 interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please attach the output of "show tech" if possible. The block usage and traffic statistics along with the config might help in determining why there are overruns.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Also, please check that the speed and duplex settings are hardcoded rather than set to &lt;STRONG&gt;auto &lt;/STRONG&gt;on both ends.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Shrikant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Apr 2011 13:51:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewalling/m-p/1681145#M558339</guid>
      <dc:creator>Shrikant Sundaresh</dc:creator>
      <dc:date>2011-04-07T13:51:04Z</dc:date>
    </item>
  </channel>
</rss>

