[c-nsp] 6509 input queue drops

[Matthew Huff]

The 6148 isn't a fabric enabled blade.

You are probably running into microburst (short lived high packet count bursts of traffic) which overflow the hardware buffers on the linecard. You probably need to upgrade to a fabric enabled card such as 6548 or 6748.

you can also do:

"show counters interface gi3/2"

To get an idea of what packets it's dropping.



----
Matthew Huff       | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10577
http://www.ox.com  | Phone: 914-460-4039
aim: matthewbhuff  | Fax:   914-460-4139


> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jared
> Mauch
> Sent: Wednesday, July 21, 2010 1:56 PM
> To: Chris Lane
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] 6509 input queue drops
> 
> check:
> 
> Router#show plat hard cap interface
> Interface Resources
>   Interface drops:
>     Module    Total drops:    Tx            Rx      Highest drop port:  Tx  Rx
>     1                 1261502177           367                           7   7
> 
> You may be having higher-level buffering drops depending on traffic patterns that will be seen here.
> 
> You may also want to check the output of 'show fabric'..
> 
> - Jared
> 
> On Jul 21, 2010, at 11:58 AM, Chris Lane wrote:
> 
> > All,
> >
> > I have a 48 port 10/100/1000mb EtherModule      WS-X6148-GE-TX  on a 6509
> > running s72033-advipservicesk9_wan-mz.122-33.SXH7.bin
> > Interface built as layer3 with a p2p site to site
> > experiencing tons of Input queue drops but no other errors on port.
> > cr.nyc1.ny#sh int g3/2
> > GigabitEthernet3/2 is up, line protocol is up (connected)
> >  Hardware is C6k 1000Mb 802.3, address is
> >  Description: xxxxxxxxx
> >  Internet address is
> >  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
> >     reliability 255/255, txload 4/255, rxload 1/255
> >  Encapsulation ARPA, loopback not set
> >  Keepalive set (10 sec)
> >  Full-duplex, 1000Mb/s, media type is 10/100/1000BaseT
> >  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:04, output 00:00:05, output hang never
> >  Last clearing of "show interface" counters 00:07:15
> > *  Input queue: 0/75/45605/0 (size/max/drops/flushes); Total output drops: 0
> > *
> >  Queueing strategy: fifo
> >  Output queue: 0/40 (size/max)
> >  5 minute input rate 5511000 bits/sec, 3615 packets/sec
> >  5 minute output rate 19240000 bits/sec, 5080 packets/sec
> >  L2 Switched: ucast: 68 pkt, 4484 bytes - mcast: 79854 pkt, 5112676 bytes
> >  L3 in Switched: ucast: 1116996 pkt, 233979838 bytes - mcast: 0 pkt, 0
> > bytes mcast
> >  L3 out Switched: ucast: 2138144 pkt, 982224161 bytes mcast: 0 pkt, 0 bytes
> >     1496205 packets input, 261671862 bytes, 0 no buffer
> >     Received 358394 broadcasts (0 IP multicasts)
> >     0 runts, 0 giants, 2606 throttles
> >    * 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored*
> >     0 watchdog, 0 multicast, 0 pause input
> >     0 input packets with dribble condition detected
> >     2158283 packets output, 988796454 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
> >
> > Anybody experience such an odd error?
> >
> > --
> > //CL
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/