Date: Fri, 14 Nov 1997 13:31:19 -0800 From: David Greenman <dg@root.com> To: Eric Anderson <keric@websidestory.com> Cc: Doug White <dwhite@resnet.uoregon.edu>, freebsd-questions@FreeBSD.ORG Subject: Re: Ethernet problem with 2.2.5 and 3C509B Message-ID: <199711142131.NAA09421@implode.root.com> In-Reply-To: Your message of "Fri, 14 Nov 1997 12:03:40 PST." <Pine.BSI.3.96.971114104637.18807D-100000@mail.websidestory.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>Maybe someone else can help me explain this - we're running a whole >bunch of Intel 10/100 nics on Pentium Pro/II machines here and every >machine to the T has this type of problem: > >bash-2.01$ netstat -i >Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll >fxp0 1500 <Link> 00.a0.c9.6e.e5.xx 10023234 0 8567462 0 4867357 >fxp0 1500 hitbox-netblk xxx 10023234 0 8567462 0 4867357 >lo0 16384 <Link> 50 0 50 0 0 >lo0 16384 127 localhost 50 0 50 0 0 >bash-2.01$ > >Of course, these machines are experiencing huge data loads (2+ million >hits/day) BUT.. we also have a couple of machines with the 3Com 905 NICs >getting the same traffic load and: > >bash-2.01$ netstat -i >Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll >vx0 1500 <Link> 00.60.97.b5.a3.xx 5855565 0 5020088 0 30 >vx0 1500 hitbox-netblk xxx 5855565 0 5020088 0 30 >lo0 16384 <Link> 28 0 28 0 0 >lo0 16384 127 localhost 28 0 28 0 0 >bash-2.01$ > >and those figures are consistent with the other 3Com cards we have. Is >the 3Com driver just better? None of the cards are in full duplex mode, >though I tried with the Intel cards (man fxp) and none of the >link1-link2 options work - they just shut the card down. I'm not sure I understand what the problem is. Please explain the nature of the problem you are having - other than the collision rate being a bit high, I don't see anything wrong with the above numbers. You mentioned that you tried setting full duplex...what is the machine connected to? It must be connected to a switch for full duplex to work. Moreover, if the switch is a Cisco Catalyst (or Cisco router), you have to configure the switch port explicitly to full duplex - it will not autonegotiate. Also, you mentioned that you are messing with the -link ifconfig flags. This tells me that you aren't running 2.2.5, -stable, or -current, since in all of those cases, the method for setting the duplex and speed is entirely different. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711142131.NAA09421>