Cisco 2621xm Input and CRC Errors


I have a Cisco 2621xm and PIX 525 connected together. The Cisco 2621xm is my perimeter router and connects via fast ethernet port to my PIX's outside interface. I am getting CRC and input erros (no collisions) on the Cisco 2621xm but not on my PIX. We have replaced the cable, checked for EMI, but we are still getting these erros. When I do a show interface on my 2621xm this is what it looks like:

FastEthernet0/1 is up, line protocol is up Hardware is AmdFE, address is 000f.24d5.3f61 (bia 000f.24d5.3f61) Description: Public Internet address is MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 100Mb/s, 100BaseTX/FX ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters 4d13h Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 235000 bits/sec, 53 packets/sec 5 minute output rate 247000 bits/sec, 51 packets/sec 5237200 packets input, 3023534728 bytes Received 2790 broadcasts, 0 runts, 0 giants, 0 throttles 606 input errors, 606 CRC, 606 frame, 0 overrun, 0 ignored 0 watchdog 0 input packets with dribble condition detected 5530409 packets output, 3434885318 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out


This is what I get when I do a show interface on the PIX:

interface ethernet0 "outside" is up, line protocol is up Hardware is i82559 ethernet, address is 0013.6031.c216 IP address, subnet mask MTU 1500 bytes, BW 100000 Kbit full duplex 450100968 packets input, 314634984 bytes, 0 no buffer Received 560771 broadcasts, 0 runts, 0 giants 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 394633441 packets output, 4227635261 bytes, 95085 underruns 0 output errors, 0 collisions, 0 interface resets 0 babbles, 0 late collisions, 0 deferred 0 lost carrier, 0 no carrier input queue (curr/max blocks): hardware (128/128) software (0/81) output queue (curr/max blocks): hardware (0/89) software (0/1)


Not sure what is wrong. I have read in some places that this is a warning that a hardware failure is possible in the near future. Has anyone else experienced this problem or does anyone have any suggestions?


Reply to
Loading thread data ...

Just curious, how did you check for EMI?

Regards, Steve

formatting link

Reply to

We did a few things steve. First of all we ran a totally different cable a totally differnt path. Second of all, we put a fluke network meter on there and it didn't find anything. Have you had this problem before and EMI was the resulting problem?

Your input is appreciated.



Reply to
adamclark Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.