Hi,
On MX, can you try configuring load-balancing per-packet configuration? It says per-packet, but it really is per-flow load-balancing in implementation.
[edit routing-options forwarding-table]
export load-balancing-policy;
[edit policy-options]
policy-statement
load-balancing-policy
{
then
{ load-balance per-packet; }}
To answer some of the questions you had posed -
- Load-balancing across AE member links is performed based on a hashing funtion. Hash computation is performed in hardware on ingress PFE's lookup chip with a combination of several functions. The output of this operation is generation of several
You can also try per-family load-balancing. For example, if you plan to configure load balancing for IPv4 transit traffic, you may configure lb using keys dervied from L3 and L4 headers.
For verification, you may use the following operational mode command -
request pfe execute target fpc<FPC NUMBER FOR INGRESS PORT> command "show jnh lb"
[...] IIF-V4: Yes SPORT-V4: Yes DPORT-V4: Yes TOS: No GTP-TEID-V4: No
IIF-V6: Yes SPORT-V6: Yes DPORT-V6: Yes TRAFFIC_CLASS: No GTP-TEID-V6: No
IIF-MPLS: Yes MPLS_PAYLOAD: Yes ETHER_PW: Yes MPLS_EXP: No CW_PRESENT: No[...]
Some options for family inet load-balancing -
{master}[edit]jnpr@R1-RE0# set forwarding-options enhanced-hash-key family inet ?
Possible completions:
+ apply-groups Groups from which to inherit configuration data
+ apply-groups-except Don't inherit configuration data from these groups
gtp-tunnel-endpoint-identifier Include TEID in the hash key for GTP-U packets
incoming-interface-index Include incoming interface index in the hash key
no-destination-port Omit IP destination port in the hash key
no-source-port Omit IP source port in the hash key
type-of-service Include TOS byte in the hash key