|
|
In article <4733113f$1_1@xxxxxxxxxxxxxxxxxxxxxx>,
Geoffrey Clements <geoffrey.clementsNO@xxxxxxxxxxxxxxxxxx> wrote:
>"Elliot J" <elliotj@xxxxxxxxx> wrote in message
>> If I run ifconfig on one of our servers, a quantity of collisions are
>> reported on one of the NICs. Should I be concerned?
>>
>> RX packets:23921568 errors:0 dropped:0 overruns:333 frame:0
>> TX packets:20756867 errors:0 dropped:0 overruns:0 carrier:44
>> collisions:1185571 txqueuelen:1000
>
>Possible network congestion or you need to check the duplex settings at both
>end of the physical link.
The interesting part is overruns and carrier errors, which should be
vanishingly rare. These indicate that your network is not performing
within spec, ie. it's not merely due to network congestion.
I agree with checking that the duplex settings match. The symptoms of
this are that small packets work fine and large packets be very, very
slow. If your equipment won't tell you what duplex settings are in
use, you can check this by sending pings of various sizes.
If that's not the problem, other things to check are:
* network diameter, esp. if you have daisychained 100Mb/s hubs.
* cable faults, eg. badly crimped UTP or mismatched pairs.
I've seen switches go wrong when connected to certain NICs, but this
is very rare. If this happens, you can put a mini-switch between the
affected NIC and the building wiring. Sometimes the problem is
specific to certain ports on the switch and there may be upgrade to
the switch firmware to fix it.
Peter
|
|