<?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 PIX Interface Errors in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-interface-errors/m-p/481191#M528331</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What could be the causes that would give the following errors on a PIX 535 Gig Interface:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MTU 1500 bytes, BW 1 Gbit full duplex, Force link-up&lt;/P&gt;&lt;P&gt;        3014970004 packets input, 69627346753824 bytes, 22550774 no buffer&lt;/P&gt;&lt;P&gt;        Received 2 broadcasts, 0 runts, 0 giants&lt;/P&gt;&lt;P&gt;        0 input errors, 6 CRC, 6703846 frame, 58 overrun, 6 ignored, 0 abort&lt;/P&gt;&lt;P&gt;        982565866 packets output, 62111142344326 bytes, 0 underruns&lt;/P&gt;&lt;P&gt;        input queue (curr/max blocks): hardware (0/25) software (0/0)&lt;/P&gt;&lt;P&gt;        output queue (curr/max blocks): hardware (0/256) software (0/0)&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 08:39:55 GMT</pubDate>
    <dc:creator>mironduplessis</dc:creator>
    <dc:date>2020-02-21T08:39:55Z</dc:date>
    <item>
      <title>PIX Interface Errors</title>
      <link>https://community.cisco.com/t5/network-security/pix-interface-errors/m-p/481191#M528331</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What could be the causes that would give the following errors on a PIX 535 Gig Interface:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MTU 1500 bytes, BW 1 Gbit full duplex, Force link-up&lt;/P&gt;&lt;P&gt;        3014970004 packets input, 69627346753824 bytes, 22550774 no buffer&lt;/P&gt;&lt;P&gt;        Received 2 broadcasts, 0 runts, 0 giants&lt;/P&gt;&lt;P&gt;        0 input errors, 6 CRC, 6703846 frame, 58 overrun, 6 ignored, 0 abort&lt;/P&gt;&lt;P&gt;        982565866 packets output, 62111142344326 bytes, 0 underruns&lt;/P&gt;&lt;P&gt;        input queue (curr/max blocks): hardware (0/25) software (0/0)&lt;/P&gt;&lt;P&gt;        output queue (curr/max blocks): hardware (0/256) software (0/0)&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:39:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-interface-errors/m-p/481191#M528331</guid>
      <dc:creator>mironduplessis</dc:creator>
      <dc:date>2020-02-21T08:39:55Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Interface Errors</title>
      <link>https://community.cisco.com/t5/network-security/pix-interface-errors/m-p/481192#M528332</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;can you revert the type of equipment where this pix is getting interfaced with on this particular Gigabit interface ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;also did u check up for possible errors on the other end too ??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jan 2006 07:22:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-interface-errors/m-p/481192#M528332</guid>
      <dc:creator>spremkumar</dc:creator>
      <dc:date>2006-01-25T07:22:09Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Interface Errors</title>
      <link>https://community.cisco.com/t5/network-security/pix-interface-errors/m-p/481193#M528333</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunately we dont have access to that device its a Cisco GSR. We are still waiting for provider to let us know if there are any issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Miron&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jan 2006 09:22:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-interface-errors/m-p/481193#M528333</guid>
      <dc:creator>mironduplessis</dc:creator>
      <dc:date>2006-01-25T09:22:59Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Interface Errors</title>
      <link>https://community.cisco.com/t5/network-security/pix-interface-errors/m-p/481194#M528334</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;In first place i would suggest to get the duplex and the speed setting checked up in the GSR side which could also be a potential reason for the same.&lt;/P&gt;&lt;P&gt;Itz always good to have them hardcoded on both the sides instead of leaving them to get negotiated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jan 2006 09:36:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-interface-errors/m-p/481194#M528334</guid>
      <dc:creator>spremkumar</dc:creator>
      <dc:date>2006-01-25T09:36:26Z</dc:date>
    </item>
  </channel>
</rss>

