Slow response and high errors between 3640 ethernet port & Cat3524 port

ppaki · ‎10-10-2002

We currently have a Cisco 3640 router with an ethernet interface (me680-1). This connects directly to a Catalyst 3524 switch (ultracs-1) via a CAT5 cable. We appear to be getting alot of errors on this connection. We have tried changing the duplex on the switch to full but it makes no difference. We've changed ports on the switch, changed cables still no good. Can you please advise the recommended port settings for each end.

interface FastEthernet0/24

description ME680-1

duplex half

ultracs-1#sh int fastEthernet 0/24

FastEthernet0/24 is up, line protocol is up

Hardware is Fast Ethernet, address is 0005.9bd2.1658 (bia 0005.9bd2.1658)

Description: ME680-1

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

reliability 245/255, txload 30/255, rxload 7/255

Encapsulation ARPA, loopback not set

Keepalive not set

Half-duplex, Auto Speed (10), 100BaseTX/FX

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

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

Last clearing of "show interface" counters 1d02h

Queueing strategy: fifo

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

5 minute input rate 287000 bits/sec, 162 packets/sec

5 minute output rate 1204000 bits/sec, 197 packets/sec

12339501 packets input, 2658520746 bytes

Received 55931 broadcasts, 699666 runts, 0 giants, 0 throttles

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

0 watchdog, 55529 multicast

0 input packets with dribble condition detected

13568361 packets output, 2163783134 bytes, 0 underruns

0 output errors, 450063 collisions, 0 interface resets

0 babbles, 0 late collision, 252415 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

interface Ethernet0/0

description connected to Ultracs Network (192.168.17.0) tpp 6/08/02 me6801_23.cfg

ip address 192.168.17.4 255.255.255.0

ip accounting output-packets

ip accounting precedence input

ip accounting precedence output

half-duplex

standby use-bia

standby 2 priority 105 preempt

standby 2 ip 192.168.17.5

standby 2 track Se0/1.1

me680-1#sh int e0/0

Ethernet0/0 is up, line protocol is up

Hardware is AmdP2, address is 0050.7368.31c1 (bia 0050.7368.31c1)

Description: connected to Ultracs Network (192.168.17.0) tpp 6/08/02 me6801_23.cfg

Internet address is 192.168.17.4/24

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

reliability 255/255, txload 6/255, rxload 31/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

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 6w0d

Queueing strategy: fifo

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

5 minute input rate 1223000 bits/sec, 196 packets/sec

5 minute output rate 274000 bits/sec, 165 packets/sec

376447875 packets input, 263699100 bytes, 9 no buffer

Received 4123899 broadcasts, 0 runts, 0 giants, 0 throttles

1172 input errors, 10 CRC, 3 frame, 0 overrun, 1162 ignored

0 input packets with dribble condition detected

360137416 packets output, 3176524347 bytes, 0 underruns(1309280/2909206/0)

127 output errors, 4218486 collisions, 6 interface resets

0 babbles, 4 late collision, 2845407 deferred

123 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

DALE FRANCIS · ‎10-10-2002

For a start the counters are over 6 weeks old, granted there are definately problems on your interface and most of them seem tro be congestion related.

I would have a look at your buffers on the 3600 and also look at the following and do type this in full:

sh interface eth 0/0 switching and a sh interface et 0/0 stat - this will tell how it was switched, can give us a clue. The fact you have had alot of carrier transitions points to a throttled interface as can be seen by the amount of drops.

I would defanetly check cable length and also i would most definately try and move to FULL duplex on both sides, if you still pick up collision etc then you have an issue with port on the 36xx.

I know i am stating the obvious but you have you tried another Ethernet port on the router if you have one..??

deilert · ‎10-11-2002

it looks like you are doing auto negotiation on the ultracs-1 f0/24 . Try hard coding the speed and duplex setting. auto negotionation is suspect at best

You should also bounce the port to ensure the new settings take effect.

michael-faust · ‎10-11-2002

You have 'keepalive set' on one interface and not on the other. Make them match.

config t

interface f0/24

keepalive 10

end