On 9/6/23 17:27, Tom Beecher wrote:
At least on MX, what Juniper calls 'per-packet' is really 'per-flow'.
Unless you specifically configure true "per-packet" on your LAG:
set interfaces ae2 aggregated-ether-options load-balance per-packet
I ran per-packet on a Juniper LAG 10 years ago. It produced 100% perfect
traffic distribution. But the reordering was insane, and the
applications could not tolerate it.
If you applications can tolerate reordering, per-packet is fine. In the
public Internet space, it seems we aren't there yet.
Mark.
