[nsp] Duplex issues with 4700

[Beprojects.com]

What is the duplex setting on the other end of the cable?  I'll bet it's
full or auto.  Make sure that it is set to 10/Half (unless it's a hub, which
would already be half).  In my experience, input errors (runts) are almost
always a duplex mismatch.  The one end is half and the other end is full and
you get chopped off packets which show up as runts.  You also get a lot of
timeouts and such as packets are lost.

----- Original Message ----- 
From: "Krzysztof Adamski" <k at adamski.org>
To: "Gert Doering" <gert at greenie.muc.de>
Cc: "Alex Rubenstein" <alex at nac.net>; <cisco-nsp at puck.nether.net>
Sent: Thursday, April 01, 2004 3:05 PM
Subject: Re: [nsp] Duplex issues with 4700


> It's the "Unknown duplex" at the end of this:
> Ethernet0 is up, line protocol is up
>   Hardware is Am79c970, address is 0010.7b47.039a (bia 0010.7b47.039a)
>   Internet address is 6.35.18.16/27
>   MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
>      reliability 255/255, txload 1/255, rxload 1/255
>   Encapsulation ARPA, loopback not set
>   Keepalive set (10 sec)
>   Unknown duplex
> ^^^^^^^^^^^^^^^^^
>
> that has me concerned, I have already changed the cables and I'm seeing a
> 1 to 3% loss on 1000 pings.
>
> K
>
> On Thu, 1 Apr 2004, Gert Doering wrote:
>
> > Hi,
> >
> > On Thu, Apr 01, 2004 at 12:49:33PM -0500, Krzysztof Adamski wrote:
> > > I know it's Half Duplex only, but since the switch is hard code to
half
> > > duplex this does not explain all the errors on the switch interface.
> >
> > Maybe your question should have been more specific :-) - I did also
> > misunderstand your e-mail as "can it do full-duplex".
> >
> > As for the errors:
> >
> > > > >      769086 packets input, 187476366 bytes
> > > > >      Received 205 broadcasts, 7848 runts, 0 giants, 0 throttles
> > > > >      7848 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
> >
> > "runts" are "too short packets" - those can be a sign of bad cabling,
bad
> > ethernet hardware, or "noise".  Possibly they could be reminders of
> > packets after collisions/late collisions.
> >
> > If the interface "pings" fine, I wouldn't worry about it - if it has
> > packet drops on an extended ping, try changing the cables.
> >
> > gert
> >
> >
> > --
> > USENET is *not* the non-clickable part of WWW!
> >
//www.muc.de/~gert/
> > Gert Doering - Munich, Germany
gert at greenie.muc.de
> > fax: +49-89-35655025
gert at net.informatik.tu-muenchen.de
> >
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>