There's a bit of legacy behind this but indeed when you configure "load-balance per-packet" it effectively does per-flow-loadbalancing.
The setting "load-balance per-flow" has been recently added for a more correct naming, and the "load-balance per-packet" is effectively deprecated, but will continue to be present because many people have this as an important part of their configuration.
So essentially: "load-balance per-flow" is the correct way to configure it, but "per-packet" is still there and works exactly the same, but is purely maintained for legacy purposes.
As it says on Configuring Per-Flow Load Balancing | Junos OS | Juniper Networks : "Note: You can use the load-balance per-packet
or load-balance per-flow
option, and both have the same functionality."
Original Message:
Sent: 03-20-2025 10:04
From: Anonymous
Subject: loal-balance per-flow vs per-packet
This message was posted by a user wishing to remain anonymous
Hello.
I have a question about load-balance per-flow vs per-packet difference.
I'm curious about the difference between the "set policy-options policy-statement ECMP then load-balance per-flow" and "set policy-options policy-statement ECMP then load-balance per-packet" commands.
If you go to the URL, it says that if you type "load-balance per-packet" it will work as "per-flow".
Configuring Per-Packet Load Balancing
Juniper | remove preview |
| Configuring Per-Packet Load Balancing | In Junos OS, you enable per-flow load balancing by setting the load-balance per-packet action in the routing policy configuration. The naming may be counter-intuitive, because in Junos, per-packet load balancing is functionally equivalent to what other vendors may term per-flow load balancing. | View this on Juniper > |
|
|
