Hi Dan, Saku, Marcin,
My understanding was that you might be able to oversubscribe only using PIR
(need to test).
And in that case all the queues are in the excess region.
So only the excess priorities are honoured (HI and LO in strict priority
fashion) and queues with the same priority are
Hi Adam,
My understanding was that you might be able to oversubscribe only using PIR
(need to test).
And in that case all the queues are in the excess region.
So only the excess priorities are honoured (HI and LO in strict priority
fashion) and queues with the same priority are serviced round
On 24 June 2015 at 21:05, Saku Ytti s...@ytti.fi wrote:
On 24 June 2015 at 22:29, Dan Peachey d...@illusionnetworks.com wrote:
Hey,
I thought the weights were determined by the %? The weights are then used
to schedule the queues appropriately. Even if the queues are in excess,
they
Hi Dan,
Seems odd to me that this needs to be done. Documentation I've read appears
to suggest that in PIR mode (no guaranteed-rate set) the per-queue
guarantee/transmit rate is calculated from the shaper rate and when a queue
exceeds it's guaranteed rate it is in excess, but this doesn't
On 25 June 2015 at 15:48, Marcin Wojcik mail.network.b...@gmail.com wrote:
Hi Dan,
Seems odd to me that this needs to be done. Documentation I've read
appears
to suggest that in PIR mode (no guaranteed-rate set) the per-queue
guarantee/transmit rate is calculated from the shaper rate and
Thanks Steven and Saku, that's what I was looking for.
Dan
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
On 23 June 2015 at 17:43, Saku Ytti s...@ytti.fi wrote:
I don't have access to any JNPR box right now, so can't give exact command.
But as you're using QX for scheduling, you'll need the chipID, and
L2/L3 index, and taildrop index, then you can use 'show qx ..' to
fetch the size of the tail,
On (2015-06-24 11:40 +0100), Dan Peachey wrote:
Hey Dan,
I must be missing something, but it seems that regardless of what I set as
a temporal buffer, the byte buffer value assigned doesn't appear to change.
Can you give
CLI config (TCP, shaper and queues)
show cos halp ifl X
show qx N
Hey Dan,
I must be missing something, but it seems that regardless of what I set
as
a temporal buffer, the byte buffer value assigned doesn't appear to
change.
Can you give
CLI config (TCP, shaper and queues)
show cos halp ifl X
show qx N tail-rule Y 0 0
show qx N q Z queue-length
On (2015-06-24 16:08 +0100), Dan Peachey wrote:
Hey Dan,
class-of-service {
traffic-control-profiles {
10M {
scheduler-map 10M_COS;
shaping-rate 10m;
guaranteed-rate 10m; # add this
}
QueueStateMax Guaranteed
On 24 June 2015 at 22:29, Dan Peachey d...@illusionnetworks.com wrote:
Hey,
I thought the weights were determined by the %? The weights are then used
to schedule the queues appropriately. Even if the queues are in excess,
they should be weighted correctly?
I tested this when Trio came out,
Hi all,
I have an IFL on a 10G interface configured with a traffic-control-profile
that has a 10M shaper and references a scheduler-map with 5 queues. The
platform is MX960 with MPC2E-3D-Q linecard.
I would like to find out the per-queue buffer sizes as configured on the
PFE in bytes. Is there a
12 matches
Mail list logo
