Re: 5.2-RC oerrs and collisions on dc0

From: Kevin Oberman <oberman_at_es.net>
Date: Sun, 28 Dec 2003 15:33:31 -0800
> From: Dejan Lesjak <dejan.lesjak_at_ijs.si>
> Date: Sun, 28 Dec 2003 00:49:50 +0100
> Sender: owner-freebsd-current_at_freebsd.org
> 
> 
> --Boundary-00=_eqh7/a7oNAgo+1o
> Content-Type: text/plain;
>   charset="us-ascii"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> Hello,
> 
> I tried 5.2-RC2 on alpha and netstat -i keeps showing oerrs and collisions
> on dc card (DEC DE500-BA):
> 
> Name    Mtu Network       Address              Ipkts Ierrs    Opkts Oerrs  
> Coll
> nge0*  1500 <Link#1>      00:04:5a:71:d2:e0        0     0        0     0     
> 0
> dc0    1500 <Link#2>      00:00:f8:10:52:47     1478     0      737   335  
> 5695
> dc0    1500 193.2.4       ewok                  1103     -      733     -     
> -
> lo0   16384 <Link#3>                              14     0       14     0     
> 0
> lo0   16384 your-net      localhost                0     -        0
-    

This looks very much like an auto-negotiation problem. Can you check
ifconfig dc0? 

To have collisions, it must be running half-duplex. (By definition
collision detection is disabled in FDX.) The additional errors further
support this.

The other question is what the other end of this link sees. Is it
running full or half duplex? If full duplex, is it seeing input errors?

If the far end is running FDX, can you set this end explicitly to FDX?
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman_at_es.net			Phone: +1 510 486-8634
Received on Sun Dec 28 2003 - 14:33:35 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:35 UTC