Input errors between Cisco 6500 series switches

Unanswered Question
Jun 21st, 2009

Hi,

Am getting input errors in Cisco switch 6509 and is connected to another swicth 6513.When i tried to ping each other , sometimes there is no packet loss but am getting packet loss and input errors mostly.

Confiration is something like this:

6509:

Interface vlan xxx

ip address x x x x 255.255.252.0

exit

int gig x/x

swithport

swicthport mode trunk

switchport trunk encapsulation isl

exit

6513:

Interface vlan xxx

ip address x x x x 255.255.252.0

exit

int gig x/x

swithport

swicthport mode trunk

switchport trunk encapsulation isl

exit

Hopefully expecting for your replies....

regards

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Giuseppe Larosa Sun, 06/21/2009 - 23:01

Hello Karthi,

to get better help you should post

sh int gix/x

sh int giy/y

from both devices to see the type of errors and to see the flowcontrol settings.

a sh module from both devices can also help, performance changes in different linecards.

Hope to help

Giuseppe

karthi.sd Mon, 06/22/2009 - 00:33

6513:

GigabitEthernet8/1 is up, line protocol is up (connected)

Hardware is C6k 1000Mb 802.3, address is 0011.5cb4.c9d8 (bia 0011.5cb4.c9d8)

MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,

reliability 255/255, txload 7/255, rxload 10/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 1000Mb/s, media type is LH

input flow-control is off, output flow-control is off

Clock mode is auto

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

Last input 00:00:42, output 00:00:41, output hang never

Last clearing of "show interface" counters 04:49:51

Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 41464000 bits/sec, 8827 packets/sec

5 minute output rate 30853000 bits/sec, 8104 packets/sec

221369956 packets input, 128161040987 bytes, 0 no buffer

Received 1503922 broadcasts (991434 multicasts)

71 runts, 0 giants, 0 throttles

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

0 watchdog, 0 multicast, 0 pause input

0 input packets with dribble condition detected

212369473 packets output, 90044899454 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 PAUSE output

0 output buffer failures, 0 output buffers swapped out

karthi.sd Mon, 06/22/2009 - 00:34

6509:

sh int gig 5/2

GigabitEthernet5/2 is up, line protocol is up (connected)

Hardware is C6k 1000Mb 802.3, address is 0017.9441.50ed (bia 0017.9441.50ed)

MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,

reliability 255/255, txload 11/255, rxload 7/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 1000Mb/s, media type is LH

Media-type configured as SFP connector

input flow-control is off, output flow-control is off

Clock mode is auto

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

Last input 00:00:40, output 00:00:42, output hang never

Last clearing of "show interface" counters 02:45:49

Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 30861000 bits/sec, 8367 packets/sec

5 minute output rate 44828000 bits/sec, 9583 packets/sec

123553133 packets input, 55796334027 bytes, 0 no buffer

Received 613071 broadcasts (287169 multicasts)

4871 runts, 0 giants, 0 throttles

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

0 watchdog, 0 multicast, 0 pause input

0 input packets with dribble condition detected

128434756 packets output, 73240658392 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 PAUSE output

0 output buffer failures, 0 output buffers swapped out

robert.horrigan Tue, 06/23/2009 - 09:31

Also make sure the rest of your trunked switches are isl or change everything to dot1q

Giuseppe Larosa Tue, 06/23/2009 - 10:26

Hello Karthi,

I think that Glen has pointed out the possible reason:

the SFP are LH

you have most errors of type frame: the two devices can be too near to each other and so the receiver of one side can find difficult to receive correctly (the signal is too strong).

Hope to help

Giuseppe

Actions

This Discussion