Re: Trying to find source of collisions

1 msg	Fwd: [networking-discuss] uperf - A network ben...
27 msg	Problems with netgraph
1 msg	Re: kern/123429: [nfe] [hang] 'ifconfig nfe up'...
1 msg	timewait state memory leak
1 msg	Re: Is it possible to change BSD licence to GPL...
4 msg	Change from BSDL to GPL
1 msg	Is it possible to change BSD licence to GPL for...
5 msg	Can I port 4.4BSD-Lite's TCP/IP protocol stack ...

Trying to find source of collisions
\ Igor Zinovik (5 May 2008)
. \ Bill Moran (5 May 2008)
. \ Matthew D. Fuller (5 May 2008)

1 msg	Re: kern/119516: [ip6] [panic] _mtx_lock_sleep:...
1 msg	Re: kern/122858: [nsswitch] nsswitch in 7.0 is ...
1 msg	Re: kern/91594: [em] FreeBSD > 5.4 w/ACPI fa...
1 msg	Re: kern/105925: Regression in ifconfig(8) + vl...
1 msg	Re: bin/108895: pppd(8): PPPoE dead connections...
1 msg	Re: kern/109308: [pppd] [panic] Multiple panics...
1 msg	Re: kern/109733: [bge] bge link state issues [r...
2 msg	Network Patches from -RELEASE to -STABLE 7.0
24 msg	Troubles with em on FreeBSD 7
13 msg	IPPROTO_DIVERT and PF_INET6
11 msg	MFC of em/igb drivers

Subject:	Re: Trying to find source of collisions
Group:	Freebsd-net
From:	Matthew D. Fuller
Date:	5 May 2008

On Mon, May 05, 2008 at 03:49:38PM +0400 I heard the voice of
Igor Zinovik, and lo! it spake thus:
>
> Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
> ed0 1500 <Link#1> 00:80:48:c6:a1:82 35885806 4 23583716 0
> 134590 ...
>
> So i have three questions:
> 1. What can cause such big collisions number? Bad UTP cable? Bad
> NIC? Misbeheaving switch?

That's not a particularly big number; it's half a percent of your
output packets. That probably doesn't have a measurable effect on
your throughput or latency.

Now, that said, if you have a switch, you probably SHOULD be running
full-duplex, in which case you won't have collisions. But you've got
an ed card; some of those may be old enough to not handle FDX.

> 2. Ierr -- seems that some input errors. What are these errors and
> what can cause them?

Cable troubles, NIC troubles, etc. [Un]plugging the cable can cause
it. Some forms of on-wire data corruption could cause it. You've got
4 of them, over 36 million input packets. Don't worry about it.

--
Matthew Fuller (MF4839) | fullermd
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
_______________________________________________
freebsd-net mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe"