cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
446
Views
3
Helpful
5
Replies

Interface Problem HELP..!

Hi, I get this output and I worry 'cause I see a lot of Collisions. I am trying to figure out why it is happening so can you give me any hint to fix this problem. It will be appreciate:

Thanks a lot

Regards

Ethernet3/0 is up, line protocol is up

Hardware is AmdP2, address is 0006.28ac.b6f0 (bia 0006.28ac.b6f0)

Description: ENLACE JOSE-TAEJ

Internet address is 167.175.XXX.XXX/24

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

reliability 252/255, txload 9/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:01, output 00:00:00, output hang never

Last clearing of "show interface" counters 3w3d

Queueing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 43000 bits/sec, 40 packets/sec

5 minute output rate 362000 bits/sec, 48 packets/sec

63633860 packets input, 2953326560 bytes, 0 no buffer

Received 2783968 broadcasts, 0 runts, 0 giants, 0 throttles

73 input errors, 73 CRC, 71 frame, 0 overrun, 0 ignored

0 input packets with dribble condition detected

67426757 packets output, 2044491211 bytes, 0 underruns(251948/145126/0)

867630 output errors, 397074 collisions, 863606 interface resets

0 babbles, 867631 late collision, 314972 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

FastEthernet0/0 is up, line protocol is up

Hardware is AmdFE, address is 0006.28ac.b6c0 (bia 0006.28ac.b6c0)

Description: RED LAN JOSE

Internet address is XXX.XXX.XXX.XXX/23

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)

Half-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 3w3d

Queueing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 48822 drops

5 minute input rate 661000 bits/sec, 175 packets/sec

5 minute output rate 645000 bits/sec, 149 packets/sec

181857038 packets input, 3358605878 bytes

Received 9629171 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog

0 input packets with dribble condition detected

182533535 packets output, 3842462072 bytes, 0 underruns(134903/233069/0)

0 output errors, 367972 collisions, 0 interface resets

0 babbles, 0 late collision, 431672 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

FastEthernet2/0 is up, line protocol is up

Hardware is AmdFE, address is 0006.28ac.b6e0 (bia 0006.28ac.b6e0)

Description: RED LAN BITOR-JOSE

Internet address is XXX.XXX.XXX.XXX/24

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

reliability 255/255, txload 3/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Half-duplex, 10Mb/s, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:05, output 00:00:01, output hang never

Last clearing of "show interface" counters 3w3d

Queueing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 18000 bits/sec, 2 packets/sec

5 minute output rate 128000 bits/sec, 4 packets/sec

18937196 packets input, 551573510 bytes

Received 432197 broadcasts, 0 runts, 0 giants, 0 throttles

12 input errors, 12 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog

0 input packets with dribble condition detected

21194159 packets output, 3783328332 bytes, 0 underruns(103346/137869/0)

0 output errors, 241215 collisions, 0 interface resets

0 babbles, 0 late collision, 104084 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped o

5 Replies 5

Hello,

collisions are usually caused by speed and/or duplex settings mismatches. Make sure that whatever is connected to your (Fast)Ethernet ports has the same settings. A good strategy to find out the settings of the connected devices is to set your ports to autonegotiate mode, e.g.:

interface FastEthernet0/0

speed auto

duplex auto

and then check what is negotiated with the ´show interfaces FastEthernet0/0´ command. After you have verified the settings, you might want to fix the settings in your configuration, e.g.:

interface FastEthernet0/0

speed 100

duplex full

HTH,

Georg

I have verified the spped and duplex but the problem still there. Any other suggestion?

Thanks

Why the interface resets ...?

Collisions can also be caused by bad ethernet cables. Replace the cabling between devices with known good cables.

grantlewis
Level 1
Level 1

All three of your interfaces are set at half duplex.

is Ethernet 3/0 connected on the other end to a device that is:

duplex = halfduplex

speed = 10 Mb/s ?

is FastEthernet 0/0 connected on the other end to a device that is:

duplex = halfduplex

speed = 100 Mb/s ?

is FastEthernet 2/0 connected on the other end to a device that is:

duplex = halfduplex

speed = 10 Mb/s ?

If you have access to CCO, paste your output into the output interperter tool, which will "troubleshoot" your interfaces for you and provide some links like the one below to understand what is going on.

http://www.cisco.com/univercd/cc/td/doc/cisintwk/itg_v1/tr1904.htm

glen.grant
VIP Alumni
VIP Alumni

Collisions in a half duplex environment are not inherently bad , it is doing it's job . The main problem is how many you are getting to total traffic transmitted and recieved , anything under 10 percent is probably not a problem . If these links are being driven hard ,which isn't very hard on 10/half links you are going to see considerable collisions, runts, crcs etc... You need to look at the traffic patterns and utilization on the links to see if this is your problem if all your Layer 1 stuff checks out . If utilization is continually high then you need to consider upgrading all your links to 100/full duplex which will eliminate this problem totally . Utilization of above 30 % will cause all kinds of slowdowns and user problems in a half duplex environment .