Re: Runts & Gaints

Hi Tapas,

The 'runts' counter gives the number of packets that are discarded
because they are smaller than the medium's minimum packet size. An
Ethernet frame (IEEE 802.3) minimum packet size is 64 bytes.

The 'giants' counter gives the number of packets that are discarded
because they exceed the medium's maximum packet (MTU) size. The original
default value is 1500 bytes, however it can usually be configured
smaller or larger.

I see that you have Gigabit Ethernet interfaces, yet they have connected
at Fast Ethernet and have an MTU size of 1500 bytes. In my experience,
poor negotiation can cause all sorts of problems. Either when connecting
Ethernet between two vendors equipment, of simply one end is hard set
and the other is configured for auto. Try performing a throughput test
over the link, if the throughput is 10Mbits or less then money is on the
Ethernet negotiation causing the error counters to increment.
If you look at your input queue, in 1w2d you have accumulated 161044
drops - this may seem large, but it only accounts for 0.5% of the total
input traffic. In addition, your CRC counter is 83386 - either the
medium is faulty (i.e. for cable) or the frames are being interrupted.
Note that the other interface has not been cleared for 40 weeks - its
impossible to tell the history from a single snapshot over such a long
duration.

Also, graph the history of the CPU in the device - flat-lining at 100%
for periods of time would also be a possible cause for runts, giants and
CRC's.

regards Andy

Tapas Das wrote:
> Due to what reasons I may recive runts & gaints on my Interface
> SH RUNN INT GI 11/6Building configuration...
> Current configuration : 220 bytes!interface GigabitEthernet11/6 switchport
> switchport access vlan 502 switchport mode access no ip address speed 100
> duplex full spanning-tree portfastend
> XXXXXXXX#SH RUNN INT GI 11/9Building configuration...
> Current configuration : 218 bytes!interface GigabitEthernet11/9 switchport
> switchport access vlan 502 switchport mode access no ip address speed 100
> duplex full spanning-tree portfastend
>
> SH INT GI 11/6GigabitEthernet11/6 is up, line protocol is up (connected)
> Hardware is C6k 1000Mb 802.3, address is 001b.d5fe.29dd (bia 001b.d5fe.29dd)
> Description: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX MTU 1500 bytes, BW
> 100000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255
> Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex,
> 100Mb/s input flow-control is off, output flow-control is on Clock mode is
> auto ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output 00:00:56,
> output hang never Last clearing of "show interface" counters 1w2d Input
> queue: 0/2000/161044/0 (size/max/drops/flushes); Total output drops: 0
> Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 0
> bits/sec, 0 packets/sec 5 minute output rate 3000 bits/sec, 6 packets/sec
> 28590011 packets input, 3155794998 bytes, 0 no buffer Received 3238
> broadcasts (9 multicasts) 8779 runts, 141 giants, 0 throttles 161044
> input errors, 83386 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 0
> multicast, 0 pause input 0 input packets with dribble condition detected
> 53066376 packets output, 57544944850 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
> xxxxxxxxxx#SH INT GI 11/9GigabitEthernet11/9 is up, line protocol is up
> (connected) Hardware is C6k 1000Mb 802.3, address is 001b.d5fe.29e0 (bia
> 001b.d5fe.29e0) Description: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX MTU
> 1500 bytes, BW 100000 Kbit, DLY 10 usec, reliability 255/255, txload
> 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10
> sec) Full-duplex, 100Mb/s input flow-control is off, output flow-control is
> on Clock mode is auto ARP type: ARPA, ARP Timeout 04:00:00 Last input
> never, output 00:00:03, output hang never Last clearing of "show interface"
> counters 40w0d Input queue: 0/2000/31379086/0 (size/max/drops/flushes); Total
> output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5
> minute input rate 70000 bits/sec, 34 packets/sec 5 minute output rate 25000
> bits/sec, 9 packets/sec 1246875972 packets input, 678093317020 bytes, 0 no
> buffer Received 11404 broadcasts (0 multicasts) 336645 runts, 8315
> giants, 0 throttles 31379086 input errors, 30144143 CRC, 0 frame, 0
> overrun, 0 ignored 0 watchdog, 0 multicast, 0 pause input 0 input
> packets with dribble condition detected 828815484 packets output,
> 126903728484 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
> _________________________________________________________________
> MSN Quiz The clash is on to find the best brains. Test your skills with avid
> quizzers on MSN quiz.
> http://specials.msn.co.in/WLSocialNetworkConnector/Chrome.aspx
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Sat Aug 01 2009 - 09:52:44 ART