On 11/19/21 17:05, Thomas Bellman via juniper-nsp wrote:
[1] Of the 12 Mbyte buffer space in Trident 2, which is used in
QFX5100 and EX4600, 3 Mbyte is used for per-port dedicated
buffers, and 9 Mbyte is shared between all ports. I believe
on later chips an even larger
On Fri, 19 Nov 2021 at 17:12, Thomas Bellman via juniper-nsp
wrote:
> Cut-through actually *can* help a little bit. The buffer space in
> the Trident and Tomahawk chips is mostly shared between all ports;
> only a small portion of it is dedicated per port[1]. If you have
> lots of traffic on
Can you please share the output of:
show class-of-service shared-buffer
on your QFX5100 ?
Cheers
James
Il giorno ven 19 nov 2021 alle ore 11:58 Thomas Bellman
ha scritto:
> On 2021-11-19 09:49, james list via juniper-nsp wrote:
>
> > I try to rephrase the question you do not understand: if I
On 2021-11-19 10:07, Saku Ytti via juniper-nsp wrote:
> Cut-through does nothing, because your egress is congested, you can
> only use cut-through if egress is not congested.
Cut-through actually *can* help a little bit. The buffer space in
the Trident and Tomahawk chips is mostly shared
On 2021-11-19 09:49, james list via juniper-nsp wrote:
> I try to rephrase the question you do not understand: if I enable cut
> through or change buffer is it traffic affecting ?
On the QFX 5xxx series and (at least) EX 46xx series, the forwarding
ASIC needs to reset in order to change between
On Fri, 19 Nov 2021 at 11:50, james list wrote:
> I also understood cut through cannot help but obviously I cannot change QFX
> switches because we loss few udp packets for a single application, the idea
> could be to change shared buffers for unused queues and add to used one,
> correct ?
Hi
I mentioned MX and QFX (output related QFX5100) in first email because
traffic pattern spread both.
I never mentioned internet.
I also understood cut through cannot help but obviously I cannot change QFX
switches because we loss few udp packets for a single application, the idea
could be to
On Fri, 19 Nov 2021 at 10:49, james list wrote:
Hey,
> I try to rephrase the question you do not understand: if I enable cut through
> or change buffer is it traffic affecting ?
There is no cut-through and I was hoping after reading the previous
email, you'd understand why it won't help you
Hi ytti
I try to rephrase the question you do not understand: if I enable cut
through or change buffer is it traffic affecting ?
Regarding the drops here the outputs (15h after clear statistics):
Physical interface: xe-0/0/19, Enabled, Physical link is Up
Interface index: 939, SNMP ifIndex:
On Thu, 18 Nov 2021 at 23:20, james list via juniper-nsp
wrote:
> 1) is MX family switching by default in cut through or store and forward
> mode? I was not able to find a clear information
Store and forward.
> 2) is in general (on MX or QFX) jeopardizing the traffic the action to
> enable cut
Hi all
Questions:
1) is MX family switching by default in cut through or store and forward
mode? I was not able to find a clear information
2) is in general (on MX or QFX) jeopardizing the traffic the action to
enable cut through or change buffer allocation?
I have some output discard on an
11 matches
Mail list logo