Re: [c-nsp] CRC errors on fastethernet interface

2012-11-26 Thread Joseph Mays
. This is a complete surprise to me, to say the least. If there is some other command to set the speed, I can't find it. - Original Message - From: Joe Mays m...@win.net To: cisco-nsp@puck.nether.net Sent: Thursday, November 22, 2012 1:33 AM Subject: [c-nsp] CRC errors on fastethernet interface

Re: [c-nsp] CRC errors on fastethernet interface

2012-11-26 Thread Mikael Abrahamsson
On Mon, 26 Nov 2012, Joseph Mays wrote: This is a complete surprise to me, to say the least. If there is some other command to set the speed, I can't find it. PA-FE and IO-FE does afaik, only support 100 meg (not 10 meg) and only half and full duplex, not autoneg. The IO-2FE and PA-2FE-TX

Re: [c-nsp] CRC errors on fastethernet interface

2012-11-26 Thread Nick Hilliard
On 26/11/2012 17:57, Mikael Abrahamsson wrote: PA-FE and IO-FE does afaik, only support 100 meg (not 10 meg) and only half and full duplex, not autoneg. i could never understand this. the pa-fe and the io-fe both used DEC tulip chips, which were perfectly capable of 10/100, hd/fd. obviously

Re: [c-nsp] CRC errors on fastethernet interface

2012-11-26 Thread Gert Doering
Hi, On Mon, Nov 26, 2012 at 06:25:27PM +, Nick Hilliard wrote: On 26/11/2012 17:57, Mikael Abrahamsson wrote: PA-FE and IO-FE does afaik, only support 100 meg (not 10 meg) and only half and full duplex, not autoneg. i could never understand this. the pa-fe and the io-fe both used DEC

Re: [c-nsp] CRC errors on fastethernet interface

2012-11-26 Thread Mike Andrews
On 11/26/12 1:25 PM, Nick Hilliard wrote: On 26/11/2012 17:57, Mikael Abrahamsson wrote: PA-FE and IO-FE does afaik, only support 100 meg (not 10 meg) and only half and full duplex, not autoneg. i could never understand this. the pa-fe and the io-fe both used DEC tulip chips, which were

Re: [c-nsp] CRC errors on fastethernet interface

2012-11-26 Thread Nick Hilliard
On 26/11/2012 19:10, Mike Andrews wrote: Probably because some (most?) revisions of the Tulip had buggy/broken auto-negotiation logic. they weren't alone in this, then. They're probably the source of most the early hardcoding-speed-and-duplex bad practices. The combo of Tulip to 2924XL

Re: [c-nsp] CRC errors on fastethernet interface

2012-11-23 Thread Jon Harald Bovre
Switch using dot1q, router untagged. Should not make any difference, but try to change switchport to access. Jon ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at

Re: [c-nsp] CRC errors on fastethernet interface

2012-11-22 Thread Aaron
The FE on the 7200 is a FE, not 10/100 switchable, hence no speed. Have you tried a different port on both sides? That would narrow down where the issue is since you tried swapping the cable. Is the cable passing near power cable or over power cables at not 90degs? On Thu, Nov 22, 2012 at 1:33

[c-nsp] CRC errors on fastethernet interface

2012-11-21 Thread Joe Mays
Have a 7206 connected to a Catalyst 2900XL switch port. The 2900XL is getting CRC errors on the port at the rate of about one every one or two seconds. I've tried replacing the cable, no effect. core-sw1.noc#show int fastethernet0/1 FastEthernet0/1 is up, line protocol is up Hardware is Fast