so I have found that the problem was not in the bandwidth community but rather in the policy I had in place to tag incoming routes from peers. There was an accept in a previous policy term so I didn't get to applying the badnwidth community.
Original Message:
Sent: 07-11-2025 07:22
From: igor.hamzic81
Subject: Assign bandwidth cost to BGP peer
It was one of the articles I was using to configure this. I was following these articles:
https://www.schynetworks.com/load-balancing/
https://www.juniper.net/documentation/us/en/software/junos/ai-ml-evo/bgp/topics/topic-map/bgp-link-bandwidth.html
Original Message:
Sent: 07-11-2025 07:09
From: Andrei Cebotareanu
Subject: Assign bandwidth cost to BGP peer
Hi,
Just out of curiosity- was you following this article?
https://community.juniper.net/blogs/moshiko-nayman/2024/05/13/bgp-link-bandwidth-with-junos
BR
------------------------------
Andrei Cebotareanu
Original Message:
Sent: 07-10-2025 23:01
From: igor.hamzic81
Subject: Assign bandwidth cost to BGP peer
Hi all,
we have several links to our ISPs that are physically on 10G interfaces but have various commits on them. I'm trying to assign bandwidth to them so we can use unequal cost balancing to use links according to their commit rates.
I'm trying to use communities that look like this:
community BW-1.5G members bandwidth:XXXXX:1500000000;
community BW-2G members bandwidth:XXXXX:2000000000;
(XXXXX is our ASN)
and the assign them to a term in an import policy for a specific peer.
The problem is that I'm not seeing traffic distribution according to the link commits but I see that the traffic is being equally distributed across all links.
Perhaps I'm doing something wrong with the statements as there is conflicting info in the documentation as some say use bytes and other say bits?
Thanks in advance for any help.