<?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 501 Collisions Outside Interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-501-collisions-outside-interface/m-p/371501#M550007</link>
    <description>&lt;P&gt;PIX 501 outside interface has high number of collisions.  It operates at 10mb half duplex with no way of changing the settings.  Is there anyway to descrease or eliminate the amount of collisions that are taking place?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sincerely,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Joel&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 08:02:29 GMT</pubDate>
    <dc:creator>joel-metz</dc:creator>
    <dc:date>2020-02-21T08:02:29Z</dc:date>
    <item>
      <title>PIX 501 Collisions Outside Interface</title>
      <link>https://community.cisco.com/t5/network-security/pix-501-collisions-outside-interface/m-p/371501#M550007</link>
      <description>&lt;P&gt;PIX 501 outside interface has high number of collisions.  It operates at 10mb half duplex with no way of changing the settings.  Is there anyway to descrease or eliminate the amount of collisions that are taking place?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sincerely,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Joel&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:02:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-501-collisions-outside-interface/m-p/371501#M550007</guid>
      <dc:creator>joel-metz</dc:creator>
      <dc:date>2020-02-21T08:02:29Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 501 Collisions Outside Interface</title>
      <link>https://community.cisco.com/t5/network-security/pix-501-collisions-outside-interface/m-p/371502#M550008</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joel:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What kind of a switch hub is it that the PIX 501 is plugged into?&lt;/P&gt;&lt;P&gt;We tested the 501 in our lab with ethernet0 (outside) plugged into a catalyst 1900 switch with the port harcoded to 100full on both ends, and the interface negotiated to 100full successfully.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pixfirewall(config)# sh ver                           &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco PIX Firewall Version 6.3(4)                                 &lt;/P&gt;&lt;P&gt;Cisco PIX Device Manager Version 3.0(0)132                                          &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Compiled on Fri 02-Jul-04 00:07 by morlee                                         &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pixfirewall up 41 days 16 hours                               &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hardware:   PIX-501, 16 MB RAM, CPU Am5x86 133 MHz                                                  &lt;/P&gt;&lt;P&gt;Flash E28F640J3 @ 0x3000000, 8MB                                &lt;/P&gt;&lt;P&gt;BIOS Flash E28F640J3 @ 0xfffd8000, 128KB                                        &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;0: ethernet0: address is 0007.5057.e29a, irq 9                                              &lt;/P&gt;&lt;P&gt;1: ethernet1: address is 0007.5057.e29b, irq 10                                               &lt;/P&gt;&lt;P&gt;Licensed Features:                  &lt;/P&gt;&lt;P&gt;Failover:                    Disabled                                     &lt;/P&gt;&lt;P&gt;VPN-DES:                     Enabled                                    &lt;/P&gt;&lt;P&gt;VPN-3DES-AES:                Enabled                                    &lt;/P&gt;&lt;P&gt;Maximum Physical Interfaces: 2                              &lt;/P&gt;&lt;P&gt;Maximum Interfaces:          2                              &lt;/P&gt;&lt;P&gt;Cut-through Proxy:           Enabled                                    &lt;/P&gt;&lt;P&gt;Guards:                      Enabled                                    &lt;/P&gt;&lt;P&gt;URL-filtering:               Enabled                                    &lt;/P&gt;&lt;P&gt;Inside Hosts:                50                &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;------------               &lt;/P&gt;&lt;P&gt;pixfirewall(config)# interface ethernet0 100full&lt;/P&gt;&lt;P&gt;                                                &lt;/P&gt;&lt;P&gt;pixfirewall(config)# sh int                           &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 0007.5057.e29a&lt;/P&gt;&lt;P&gt;  IP address 172.18.124.251, subnet mask 255.255.255.0&lt;/P&gt;&lt;P&gt;  MTU 1500 bytes, BW 100000 Kbit full duplex&lt;/P&gt;&lt;P&gt;        2954197 packets input, 221416489 bytes, 0 no buffer&lt;/P&gt;&lt;P&gt;        Received 2943338 broadcasts, 0 runts, 0 giants&lt;/P&gt;&lt;P&gt;        0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort&lt;/P&gt;&lt;P&gt;        3201 packets output, 606124 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 (0/8)&lt;/P&gt;&lt;P&gt;        output queue (curr/max blocks): hardware (0/1) software (0/1)&lt;/P&gt;&lt;P&gt;interface ethernet1 "inside" is up, line protocol is up&lt;/P&gt;&lt;P&gt;  Hardware is i82559 ethernet, address is 0007.5057.e29b&lt;/P&gt;&lt;P&gt;  IP address 10.10.10.1, subnet mask 255.255.255.0&lt;/P&gt;&lt;P&gt;  MTU 1500 bytes, BW 100000 Kbit full duplex&lt;/P&gt;&lt;P&gt;        21944369 packets input, 1500611077 bytes, 0 no buffer&lt;/P&gt;&lt;P&gt;        Received 21944369 broadcasts, 0 runts, 0 giants&lt;/P&gt;&lt;P&gt;        0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort&lt;/P&gt;&lt;P&gt;        0 packets output, 0 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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Binh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Mar 2005 07:01:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-501-collisions-outside-interface/m-p/371502#M550008</guid>
      <dc:creator>bphan</dc:creator>
      <dc:date>2005-03-29T07:01:49Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 501 Collisions Outside Interface</title>
      <link>https://community.cisco.com/t5/network-security/pix-501-collisions-outside-interface/m-p/371503#M550009</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Joel&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is your PIX outside interface hard-coded to work at 10Mbps Halfduplex, or is it set to auto? What about the peer device (switch/hub, or other device)? Any chance that you can hard-code it on both end? On the PIX side the command would be:&lt;/P&gt;&lt;P&gt;interface ethernet0 10baset&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take a look at the following link, you might find it useful:&lt;/P&gt;&lt;P&gt;-- Troubleshooting Ethernet Collisions:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk389/tk214/technologies_tech_note09186a008009446d.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk389/tk214/technologies_tech_note09186a008009446d.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also paste the 'show interface' output into the following link (Output Interpreter) for more useful information...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- Output Interpreter Tool (CCO loging required):&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl?locale=en" target="_blank"&gt;https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl?locale=en&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico Rodriguez&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Mar 2005 07:21:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-501-collisions-outside-interface/m-p/371503#M550009</guid>
      <dc:creator>fedrodri</dc:creator>
      <dc:date>2005-03-29T07:21:28Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 501 Collisions Outside Interface</title>
      <link>https://community.cisco.com/t5/network-security/pix-501-collisions-outside-interface/m-p/371504#M550010</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Collisions are a fact of life with half duplex ethernet connections.  There is nothing you can do about unless you can switch to a full duplex mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Mar 2005 13:27:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-501-collisions-outside-interface/m-p/371504#M550010</guid>
      <dc:creator>scoclayton</dc:creator>
      <dc:date>2005-03-29T13:27:58Z</dc:date>
    </item>
  </channel>
</rss>

