04-16-2003 08:42 AM - edited 03-02-2019 06:43 AM
hello
i have been receiving a lot of crc errors on a fiber module port. i have replace the fiber patch cable and even went so far as to replace the 4 port fiber card. i can't get a handle on where they are coming from. the other end is connected to a 2900M as well. i only see a larger number of crc on the one interface.
FastEthernet2/2 is up, line protocol is up
Hardware is Fast Ethernet, address is 0003.e393.c468 (bia 0003.e393.c467)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 2/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 100Mb/s
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:10, output 00:00:00, output hang never
Last clearing of "show interface" counters 07:23:38
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 505000 bits/sec, 170 packets/sec
5 minute output rate 828000 bits/sec, 5 packets/sec
3700127 packets input, 1273379232 bytes
Received 6404 broadcasts, 0 runts, 0 giants, 0 throttles
1095 input errors, 1094 CRC, 1 frame, 38 overrun, 39 ignored
0 watchdog, 560 multicast
0 input packets with dribble condition detected
144957 packets output, 2261653952 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
any help in pointing me in the right direction would be greatly appreciated.
thanks
Steve
04-16-2003 09:18 AM
I would check the device it is connected to , make sure it is also hard coded to 100 full duplex , no auto negotiation
04-16-2003 09:22 AM
i havd checked that previously.....here is the other port:
FastEthernet2/1 is up, line protocol is up
Hardware is Fast Ethernet, address is 0090.f230.e2dd (bia 0090.f230.e2dd)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive not set
Full-duplex, 100Mb/s
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:38:40, output hang never
Last clearing of "show interface" counters 3w1d
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 1026000 bits/sec, 377 packets/sec
5 minute output rate 618000 bits/sec, 343 packets/sec
275155144 packets input, 3501740008 bytes, 0 no buffer
Received 7773150 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 367 ignored, 0 abort
0 watchdog, 1723804 multicast
0 input packets with dribble condition detected
266189068 packets output, 1201088733 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
04-16-2003 09:33 AM
Do you have the luxury of a second fiber pair that you can swap to for this connection?
Mark
04-16-2003 09:37 AM
yes i do have some spare dark fibers.....that was going to be my next step, but i wanted to make sure i wasn't overlooking something obvious before i go to the trouble of terminating the spare fiber
thanks
steve.
04-16-2003 10:12 AM
before you go through the trouble of swapping fiber , I would try to bounce the interface on each side , sometimes the interfaces need to be bounced for the speed & duplex is changed .
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: