[j-nsp] MX and microbursting...

[Derick Winkworth]

We've done that.  Its the rx-ring on the controller in the NPE-G2.  That is not 
tunable.  A show controller indicates we are basically microbursting 128 or more 
packets at a time (faster than the next cycle to pull packets off the ring).  




Increasing the permanent buffers and the hold-queue definitely reduced the 
number of dropped packets significantly, but still over the last 8 hours 
(business day) I see about 10k drops.  Granted, its over 1.2 billion packets.  I 
just don't like seeing 10k drops during the business day.

I will apply traffic-shaping as per previous post.



________________________________
From: Chris Evans <chrisccnpspam2 at gmail.com>
To: sthaug at nethelp.no
Cc: juniper-nsp at puck.nether.net
Sent: Mon, April 11, 2011 3:15:59 PM
Subject: Re: [j-nsp] MX and microbursting...

You can adjust buffers on the 7200.  It is not an interface parameter tho.
On Apr 11, 2011 2:56 PM, <sthaug at nethelp.no> wrote:
>> {master}
>> show configuration class-of-service fragmentation-maps
>> DO_NOT_FRAG_RT-768
>> forwarding-class {
>> RT {
>> no-fragmentation;
>> }
>> BE {
>> fragment-threshold 768;
>> }
>> SG {
>> fragment-threshold 768;
>> }
>> }
>
> Eh? He said GigE. According to
>
>
http://www.juniper.net/techpubs/en_US/junos10.0/information-products/topic-collections/config-guide-services/fragmentation-maps-edit-cos.html

>
> fragmentation-maps is for link service IQ interfaces only.
>
> Steinar Haug, Nethelp consulting, sthaug at nethelp.no
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp