Re: CRC & INPUT Errors
- From: brickwalls19 <brickwalls19@xxxxxxxxx>
- Date: 1 May 2007 16:10:45 -0700
On Apr 24, 12:39 am, Arthur Brain <arthur_bra...@xxxxxxxxxxx> wrote:
Igor Pinchevskiy wrote:
Hello Arthur,
I checked one of the remote router's ethernet interface and it wasn't
set to full duplex, so i changed it and the CRC's went down, but still
getting some, about 5 every 5 minutes or so.
I was going to suggest doing a sh int on the other end of the ethernet
link (you should have seen Collisions & Late Collisions, plus seen
what it had for a Duplex configuration).
Setting Auto/Auto at each end might work, otherwise forcing both ends
of the link as 100Mb/FullDuplex might be required.
For a comms link like this, specifying 100/FD on both ends would be
the preferable planned configuration, I think.
Having said that, I had one recently where collisions and/or other
errors were generated on a link with every single combination of speed/
duplex EXCEPT Auto/Auto, which was weird.
make sure you stick to a standard configuration for NICs and switch
ports. either have both side in auto-negotiate or hard-coded. there
have been many times where i argued with the server deployment team to
set their NICs to 100/full since i hard-code my switch ports to 100/
full.
collisions / align errors / runts are good indicators of duplex
mismatches.
.
- Prev by Date: Re: Downloading Firmware ?
- Next by Date: Re: Terminal Server Setup
- Previous by thread: ASDM - ACL Manager
- Next by thread: Re: Terminal Server Setup
- Index(es):
Relevant Pages
|
