This article explains key points to check for the load-balance of traffic between all the child links between both the Ae
All packet loading balancing in the LAG child interface is done by the LAG hashing algorithm.
Basically the 2-member LAG that is between MX1 ae1 <> MX2 ae1 is not load balancing traffic properly as we observed most of the traffic is on the first member of the LAG.
For LAG bundles, the hashing algorithm determines how traffic entering a LAG bundle is placed onto the bundle’s member links.
The hashing algorithm tries to manage bandwidth by evenly load-balancing all incoming traffic across the member links in the bundle.
https://www.juniper.net/documentation/us/en/software/junos/high-availability/topics/topic-map/load-balancing-aggregated-ethernet-interfaces.html#:~:text=Aggregated%20Interfaces%20%28also%20called%20AE%20for%20aggregated%20Ethernet%2C,between%20the%20same%20two%20devices%20on%20each%20end.
Kindly modify the hash-key configuration and check if load-balancing of traffic
hash-key {
family inet {
layer-3;
layer-4;
session-id;
}
family mpls {
label-1;
label 2;
label-3;
no-labels;
payload {
ip {
layer-3-only;
port-data {
destination-lsb;
destination-msb;
source-lsb;
source-msb;
family multiservice {
destination-mac;
source-mac;
[edit forwarding-options]
Kindly contact JTAC for further support, if issue Still persist after the above configuration.