[c-nsp] Best practice - Core vs Access Router

David Prall dcp at dcptech.com
Wed Feb 10 14:22:30 EST 2010


Your drops and flushes counts are the same. A flush is a control plane
packet that pushed to CPU even though the input queue was filled. I don't
believe these two numbers should be the same unless all of the input queue
was filled with these packets.

David

--
http://dcp.dcptech.com


> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of Andy B.
> Sent: Wednesday, February 10, 2010 2:01 PM
> To: David Freedman
> Cc: nsp-cisco
> Subject: Re: [c-nsp] Best practice - Core vs Access Router
> 
> On Wed, Feb 10, 2010 at 7:48 PM, David Freedman
> <david.freedman at uk.clara.net> wrote:
> > So, are you checking your interfaces for incrementing drop/error
> counters?
> >
> > Are you seeing any of this when there is the problem occuring?
> > (clear counters , sh int summ etc..)
> >
> 
> I am having input drops all the time, no matter how high or low I set
> the incoming hold-queue.
> 
> The OSPF and IBGP interfaces approx. 30 minutes after I cleared the
> counters:
> 
> TenGigabitEthernet8/1 is up, line protocol is up (connected)
>   Input queue: 0/2000/622/622 (size/max/drops/flushes); Total output
> drops: 0
> 
> TenGigabitEthernet9/1 is up, line protocol is up (connected)
>   Input queue: 0/4096/1664/1664 (size/max/drops/flushes); Total output
> drops: 0
> 
> TenGigabitEthernet9/2 is up, line protocol is up (connected)
>   Input queue: 0/4096/1916/1916 (size/max/drops/flushes); Total output
> drops: 0
> 
> 
> These links are not congested! Te9/1 is the busiest with maybe 6.5 out
> of 10 Gig. The other two are below 5 Gig.
> _______________________________________________
> 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/



More information about the cisco-nsp mailing list