Hello,
Thanks to
Joe Fletcher,
Jeffry Hummel,
Mohammed K. Ahmed and
Pat O'Brian,
putting it all together you should check in the following order:
1- Does the switch has the right setting, Netadmin also could check on
errors on the
corespondig port. In my case the switch is a hub and therefor can not
be set to full duplex.
2 - Check the Cabeling:
Does the lenght exceed the recommedations (100 m to the router/swich)
Are possibly some interferences on the cabel (electricity or
telephone wires)
is the cabel physcally ok
3 - replace the nic and check if the errors still come up.
Recommendations for allowabel size of collisions have a broad rang:
from less than 5% up to 1600% (USENET:comp.dcom.lans.ethernet,
thread:ethernet performance numbers (1996))
On Out errors: No good explanation was given.
At the moment we are checking the cabeling
have fun
samier.
Samier.Kesou_at_bfa-berlin.de_at_ornl.gov on 19.12.2001 14:59:01
Gesendet von: tru64-unix-managers-owner_at_ornl.gov
An: tru64-unix-managers_at_ornl.gov
Kopie:
Thema: Out Errors on Network Interface
Hello,
Server: Alpha 1200
OS: DUV40G
NIC: DECchip 21140: Revision: 2.2
10 Mbit half Duplex
We have a network card which has permanently Out Errors:
Ipkts = 3616615
Ierr = 0
Opkt = 4158105
Opkts = 229
Coll = 1203678
Two things i liked to know:
What exactly doest it mean when a Output errors (or In Errors) occure and
to what extent are these errors acceptable.
Thanks in advance
Samier Kesou.
Received on Thu Dec 20 2001 - 10:51:54 NZDT