<?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: pix overrun errors. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358872#M549063</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you should upgrade your PIX...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 25 Apr 2005 13:25:50 GMT</pubDate>
    <dc:creator>umedryk</dc:creator>
    <dc:date>2005-04-25T13:25:50Z</dc:date>
    <item>
      <title>pix overrun errors.</title>
      <link>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358871#M549062</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My company has a PIX515E with OS 6.3(4). Lately we discovered there were connectivity problems between servers in DMZ interface and servers in outside interface of the PIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Command "show interface" gives me a lot of overrun errors in input queues of outside and dmz interface, and a small number of lost carrier errors. VMS's Performance Monitor for says PIX has around 1 interface error per 5 minutes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can U tell me if my PIX is overloaded? If so my company is able to buy a more powerful one but I need to know it very fast.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are my show's:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#show memory&lt;/P&gt;&lt;P&gt;Free memory:        47552480 bytes&lt;/P&gt;&lt;P&gt;Used memory:        19556384 bytes&lt;/P&gt;&lt;P&gt;-------------     ----------------&lt;/P&gt;&lt;P&gt;Total memory:       67108864 bytes&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#show cpu usage&lt;/P&gt;&lt;P&gt;CPU utilization for 5 seconds = 7%; 1 minute: 11%; 5 minutes: 10%&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#show traffic &lt;/P&gt;&lt;P&gt;outside:&lt;/P&gt;&lt;P&gt;        received (in 71402.490 secs):&lt;/P&gt;&lt;P&gt;                159151661 packets       2558181875 bytes&lt;/P&gt;&lt;P&gt;                2048 pkts/sec   35045 bytes/sec&lt;/P&gt;&lt;P&gt;        transmitted (in 71402.490 secs):&lt;/P&gt;&lt;P&gt;                224006098 packets       1959599619 bytes&lt;/P&gt;&lt;P&gt;                3016 pkts/sec   27023 bytes/sec&lt;/P&gt;&lt;P&gt;inside:&lt;/P&gt;&lt;P&gt;        received (in 71402.490 secs):&lt;/P&gt;&lt;P&gt;                123455 packets  123340347 bytes&lt;/P&gt;&lt;P&gt;                1 pkts/sec      1005 bytes/sec&lt;/P&gt;&lt;P&gt;        transmitted (in 71402.490 secs):&lt;/P&gt;&lt;P&gt;                81267 packets   13063303 bytes&lt;/P&gt;&lt;P&gt;                1 pkts/sec      2 bytes/sec&lt;/P&gt;&lt;P&gt;dmz:&lt;/P&gt;&lt;P&gt;        received (in 71402.500 secs):&lt;/P&gt;&lt;P&gt;                224105464 packets       1975652320 bytes&lt;/P&gt;&lt;P&gt;                3018 pkts/sec   27007 bytes/sec&lt;/P&gt;&lt;P&gt;        transmitted (in 71402.500 secs):&lt;/P&gt;&lt;P&gt;                159135787 packets       2683360111 bytes&lt;/P&gt;&lt;P&gt;                2048 pkts/sec   37039 bytes/sec&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;# show perfmon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERFMON STATS:    Current      Average&lt;/P&gt;&lt;P&gt;Xlates               0/s          0/s&lt;/P&gt;&lt;P&gt;Connections          4/s          0/s&lt;/P&gt;&lt;P&gt;TCP Conns            3/s          0/s&lt;/P&gt;&lt;P&gt;UDP Conns            1/s          0/s&lt;/P&gt;&lt;P&gt;URL Access           0/s          0/s&lt;/P&gt;&lt;P&gt;URL Server Req       0/s          0/s&lt;/P&gt;&lt;P&gt;TCP Fixup         6507/s          0/s&lt;/P&gt;&lt;P&gt;TCPIntercept         0/s          0/s&lt;/P&gt;&lt;P&gt;HTTP Fixup           0/s          0/s&lt;/P&gt;&lt;P&gt;FTP Fixup            0/s          0/s&lt;/P&gt;&lt;P&gt;AAA Authen           0/s          0/s&lt;/P&gt;&lt;P&gt;AAA Author           0/s          0/s&lt;/P&gt;&lt;P&gt;AAA Account          0/s          0/s&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#show interface &lt;/P&gt;&lt;P&gt;is in the attachment&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:05:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358871#M549062</guid>
      <dc:creator>Krystian9</dc:creator>
      <dc:date>2020-02-21T08:05:30Z</dc:date>
    </item>
    <item>
      <title>Re: pix overrun errors.</title>
      <link>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358872#M549063</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you should upgrade your PIX...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Apr 2005 13:25:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358872#M549063</guid>
      <dc:creator>umedryk</dc:creator>
      <dc:date>2005-04-25T13:25:50Z</dc:date>
    </item>
    <item>
      <title>Re: pix overrun errors.</title>
      <link>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358873#M549064</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you verified the speed and duplex mode on the PIX and on the Switch? Most of performance problems and errors like this are simple caused by duplex miss configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set it to &lt;AUTO&gt; &lt;AUTO&gt; or &amp;lt;100MB Full&amp;gt; &amp;lt;100MB Full&amp;gt;.&lt;/AUTO&gt;&lt;/AUTO&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sincerely&lt;/P&gt;&lt;P&gt;Patrick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Apr 2005 14:11:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358873#M549064</guid>
      <dc:creator>Patrick Iseli</dc:creator>
      <dc:date>2005-04-25T14:11:29Z</dc:date>
    </item>
    <item>
      <title>Re: pix overrun errors.</title>
      <link>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358874#M549065</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes I did. &lt;/P&gt;&lt;P&gt;Its working in AUTO AUTO mode on the PIX and the catalyst switch.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Apr 2005 09:41:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358874#M549065</guid>
      <dc:creator>Krystian9</dc:creator>
      <dc:date>2005-04-26T09:41:06Z</dc:date>
    </item>
    <item>
      <title>Re: pix overrun errors.</title>
      <link>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358875#M549066</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm a bit curious about your traffic mix, from all accounts,  CPU utilization is 10% over a 5 minute interval, yet perfmon indicates a TCP fixup rate of 6507 fixups per second. Yet, the number of TCP connections are 3 fixups per second. Is there a database application sql, no ftp fixup, no http fixup ... This is fairly significant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Apr 2005 10:23:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358875#M549066</guid>
      <dc:creator>jtroney</dc:creator>
      <dc:date>2005-04-26T10:23:50Z</dc:date>
    </item>
    <item>
      <title>Re: pix overrun errors.</title>
      <link>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358876#M549067</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 have the same problem with my PIX 515 (CPU 50%, 100full). Did you manage to solve the problem and how?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;./G&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jul 2005 10:59:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358876#M549067</guid>
      <dc:creator>george</dc:creator>
      <dc:date>2005-07-27T10:59:29Z</dc:date>
    </item>
    <item>
      <title>Re: pix overrun errors.</title>
      <link>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358877#M549068</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I also have the same problem but with a 525.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rbpix01# sh int eth0&lt;/P&gt;&lt;P&gt;interface ethernet0 "outside" is up, line protocol is up&lt;/P&gt;&lt;P&gt;  Hardware is i82559 ethernet, address is 0002.b945.bec7&lt;/P&gt;&lt;P&gt;  IP address x.x.x.x, subnet mask x.x.x.x&lt;/P&gt;&lt;P&gt;  MTU 1500 bytes, BW 100000 Kbit full duplex&lt;/P&gt;&lt;P&gt;        32093129 packets input, 357402249 bytes, 0 no buffer&lt;/P&gt;&lt;P&gt;        Received 55720 broadcasts, 0 runts, 0 giants&lt;/P&gt;&lt;P&gt;        79999 input errors, 0 CRC, 0 frame, 79999 overrun, 0 ignored, 0 abort&lt;/P&gt;&lt;P&gt;        30835614 packets output, 2940086169 bytes, 0 underruns&lt;/P&gt;&lt;P&gt;        0 output errors, 0 collisions, 0 interface resets&lt;/P&gt;&lt;P&gt;        0 babbles, 0 late collisions, 0 deferred&lt;/P&gt;&lt;P&gt;        0 lost carrier, 0 no carrier&lt;/P&gt;&lt;P&gt;        input queue (curr/max blocks): hardware (128/128) software (3/141)&lt;/P&gt;&lt;P&gt;        output queue (curr/max blocks): hardware (128/128) software (1629/2659)&lt;/P&gt;&lt;P&gt;rbpix01# sh blocks&lt;/P&gt;&lt;P&gt;  SIZE    MAX    LOW    CNT&lt;/P&gt;&lt;P&gt;     4   1600   1573   1599&lt;/P&gt;&lt;P&gt;    80    400    389    398&lt;/P&gt;&lt;P&gt;   256   1012    498   1012&lt;/P&gt;&lt;P&gt;  1550   7573   3143   3804&lt;/P&gt;&lt;P&gt;  2560    200    197    198&lt;/P&gt;&lt;P&gt;rbpix01# sh perfmon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERFMON STATS:    Current      Average&lt;/P&gt;&lt;P&gt;Xlates              10/s          0/s&lt;/P&gt;&lt;P&gt;Connections        624/s          0/s&lt;/P&gt;&lt;P&gt;TCP Conns          423/s          0/s&lt;/P&gt;&lt;P&gt;UDP Conns          200/s          0/s&lt;/P&gt;&lt;P&gt;URL Access         305/s          0/s&lt;/P&gt;&lt;P&gt;URL Server Req       0/s          0/s&lt;/P&gt;&lt;P&gt;TCP Fixup        22080/s          0/s&lt;/P&gt;&lt;P&gt;TCPIntercept         0/s          0/s&lt;/P&gt;&lt;P&gt;HTTP Fixup       18842/s          0/s&lt;/P&gt;&lt;P&gt;FTP Fixup          135/s          0/s&lt;/P&gt;&lt;P&gt;AAA Authen           0/s          0/s&lt;/P&gt;&lt;P&gt;AAA Author           0/s          0/s&lt;/P&gt;&lt;P&gt;AAA Account          0/s          0/s&lt;/P&gt;&lt;P&gt;rbpix01# sh memory&lt;/P&gt;&lt;P&gt;Free memory:       168768344 bytes&lt;/P&gt;&lt;P&gt;Used memory:        99667112 bytes&lt;/P&gt;&lt;P&gt;-------------     ----------------&lt;/P&gt;&lt;P&gt;Total memory:      268435456 bytes&lt;/P&gt;&lt;P&gt;rbpix01# sh cpu usage&lt;/P&gt;&lt;P&gt;CPU utilization for 5 seconds = 39%; 1 minute: 42%; 5 minutes: 43%&lt;/P&gt;&lt;P&gt;rbpix01# sh traffic&lt;/P&gt;&lt;P&gt;outside:&lt;/P&gt;&lt;P&gt;        received (in 2977.510 secs):&lt;/P&gt;&lt;P&gt;                33129755 packets        508554636 bytes&lt;/P&gt;&lt;P&gt;                11126 pkts/sec  170798 bytes/sec&lt;/P&gt;&lt;P&gt;        transmitted (in 2977.510 secs):&lt;/P&gt;&lt;P&gt;                32079468 packets        4059538981 bytes&lt;/P&gt;&lt;P&gt;                10773 pkts/sec  1363400 bytes/sec&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Oct 2005 14:26:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358877#M549068</guid>
      <dc:creator>richardmcmahon</dc:creator>
      <dc:date>2005-10-19T14:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: pix overrun errors.</title>
      <link>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358878#M549069</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 have a audio media streaming server inside DMZ. Its using TCP/UDP and HTTP plugins. Around 1600 connections are in established mode to this server at the time of the counted capture.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When it comes to the counters you mentioned, I always thought of these as "new connections per second", am I wrong?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Krystian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Oct 2005 18:36:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358878#M549069</guid>
      <dc:creator>Krystian9</dc:creator>
      <dc:date>2005-10-20T18:36:19Z</dc:date>
    </item>
    <item>
      <title>Re: pix overrun errors.</title>
      <link>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358879#M549070</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess that by no answer to our questions its RTFM, but the M is hell not giving me any help in understanding my problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;btw u have a nice load over there &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Oct 2005 18:40:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-overrun-errors/m-p/358879#M549070</guid>
      <dc:creator>Krystian9</dc:creator>
      <dc:date>2005-10-20T18:40:26Z</dc:date>
    </item>
  </channel>
</rss>

