[j-nsp] Tail vs RED dropped packet counter

[Derick Winkworth]

Yes it is.

The SRX can do flow-based QoS, while the m10i does not.  You will want RED enabled for trafffic that responds to it on the m10i (TCP traffic, and any other traffic that will respond to loss packets by rating down or slow-starting, such as IP BARR).

In fact, RED is just "on" by default on the m10i.  I think the default is "instantaneous buffer occupancy."  You don't want this.  You want to do a weighted average, and you should set the weight to "9" to start.  Otherwise the m10i will drop far too aggressively.  I think if you do a "show interface detail" or "extensive" it will tell you what the RED buffer occupancy setting is.





________________________________
From: Abel Alejandro <aalejandro at worldnetpr.com>
To: juniper-nsp at puck.nether.net
Sent: Wed, November 11, 2009 8:41:35 AM
Subject: [j-nsp] Tail vs RED dropped packet counter

Hello,

I have a m10i and a SRX 210 both running JunOS 9.6. The CoS
configuration is basically the same with just differences on the
interface names.
There are no drop profiles configured. However when I run the command
"show interfaces queue <intfname> egress" on the m10i I see the RED
dropped packet counter incrementing and the Tail counter at 0. The SRX
210 is just the other way around the Tail drop counter is incrementing
and the RED drop packet is at 0. Is this because of a hardware
difference ?

Abel.




_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp