> > > I would say the physical wire is probably bad. Seeing unidirectional
> > errors
> > > in this case wouldn't be uncommon; one of the pair of the receive
wires
> > may
> > > have issues. Have you swapped the cable? Most of the time you won't
see
> > > framing errors related to duplex mismatc
> >> Hello:
> >>
> >> Judging from your output I would say two things:
> >>
> >> 1) You have a bad cable. CRC and framing errors are usually a result
of
> > bad
> >> media.
> >> 2) You should set the port to auto/auto, not 100/Full hard set, unless
you
> >> have specifically set that up in rc.conf
> > Ok.. It is set hard to 100BT/FD on both ends. I don't know if you saw
this,
> > but since resetting the stats a few hours ago, it shows no errors at all
on
> > their end, but were still getting errors on our end... The CRC and frame
> > errors could have been from a media mismatch when things w
> Hello:
>
> Judging from your output I would say two things:
>
> 1) You have a bad cable. CRC and framing errors are usually a result of
bad
> media.
> 2) You should set the port to auto/auto, not 100/Full hard set, unless you
> have specifically set that up in rc.conf. If one side is hard set a
> Improperly negotiating 100-BT/FD and generating lots of late collisions,
> for one. Is the switch managed? What does it's syslog output or the
> local CLI say about the port(s) in question? In Cisco parlance, you may
> want to clear the interface counters and observe 'sh int...' output while
>
> Hmm. Definately try the NIC swap then, couldn't hurt. What's your `uname
> -a`? This is something recent, right?
4.7-RELEASE
> > Thats one idea I was planning on doing, just to be sure its not a NIC
issue.
> > I am also going to try replacing the motherboard with one with a 64-bit
bus,
> > a
> Improperly negotiating 100-BT/FD and generating lots of late collisions,
> for one. Is the switch managed? What does it's syslog output or the
> local CLI say about the port(s) in question? In Cisco parlance, you may
I don't know offhand, it connects to another company, as its our internet
co
> netstat -I xl0 -w 1
input (xl0) output
packets errs bytespackets errs bytes colls
6918228525822 5631 02770466 0
7317219262852 6041 02696855 0
783926 10090955 6426 0
