Re: mii-diag returns strange errors

[Michael Loftis <mloftis@modwest.com>]

bad auto-negotiate or bad cable.  not knowing any other details i can't say 
if 11mbit is good or not since you weren't clear on what you're serving or 
how.

you can try locking both sides to say 100mbps/fdx or 100mbps/hdx and see if 
that clears things up, or making sure you've no locked settings on the 
catalyst (locking any setting on the a catalyst is known to make autoneg 
prone to fail)

--On November 14, 2006 7:19:57 PM +0100 Wojciech Ziniewicz 
<wojciech.ziniewicz@gmail.com> wrote:

> mii-diag eth0 :
> [...]
>  Error counts, cleared when read:
>      False carriers 258
>      Link disconnects 16389
>      Receive errors 35349
>      Rx symbol errors 0.
>      Rx 10Mbps Early End-Of-Frame errors 2128.
>      Rx 100Mbps Early End-Of-Frame errors 1300.
>      Tx jabber errors 0.
>
> I dont' really understand what does that mean....
>
>
> I dont see any disconnects on my eth0 but mii-diag sees ones...
> eth0 is serving about 400 clients and stale transfer is about 11 mbit...
>
> Is my hardware bad ? the other side is a big backbone catalyst..
>
>
> --
> Wojciech Ziniewicz            |  jid:zeth@chrome.pl
> http://silenceproject.org       | http://zetho.wordpress.com
>
>
> --
> To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org



--
Michael Loftis
Modwest Operations Manager
Powerful, Affordable Web Hosting