netstat -i shows tx-errors

Ken Kleiner ken at cs.uml.edu
Thu Oct 2 15:10:22 CDT 2008


I've seen this before here.  Try hard coding the interface to 100MB
Full, and also set the switch port for that.  I think autoneg in some
cases 'gets it wrong'.

On Thu, 2008-10-02 at 14:05 -0600, Howard, Chris wrote:
> I have a Dell 2850 running Red Hat EL 4.x
>  
> One of the network interfaces, I believe it is a dual port e1000 card,
> is showing this:
>  
> eth0      Link encap:Ethernet  HWaddr 00:14:22:24:2F:D4  
>           inet addr:10.202.1.4  Bcast:10.202.1.255  Mask:255.255.255.0
>           inet6 addr: fe80::214:22ff:fe24:2fd4/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:158347 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:176684 errors:8834 dropped:0 overruns:0 carrier:8834
>           collisions:15324 txqueuelen:100 
>           RX bytes:117555605 (112.1 MiB)  TX bytes:109598594 (104.5 MiB)
>           Base address:0xecc0 Memory:fe6e0000-fe700000 
> 
>  
> What might be the problem with TX-errors and TX-carrier?  I have not been
> able to find any information about TX-carrier and what that means.
>  
> It is set up for autonegotiate, and the switch it is attached to, I believe the switch
> is bumping it down to 100/half-duplex.  Would that cause the errors?
>  
> 
> 
> 
> 
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
-- 
Ken Kleiner
System Manager
UMass Lowell
978 934 3645




More information about the Linux-PowerEdge mailing list