Routing

 View Only
last person joined: 18 hours ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
  • 1.  Assign bandwidth cost to BGP peer

    Posted 07-10-2025 23:01

    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.



  • 2.  RE: Assign bandwidth cost to BGP peer
    Best Answer

    Posted 07-11-2025 07:10

    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
    ------------------------------



  • 3.  RE: Assign bandwidth cost to BGP peer

    Posted 07-11-2025 07:23

    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




  • 4.  RE: Assign bandwidth cost to BGP peer

    Posted 07-22-2025 03:07

    Hi,

    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.

    After correcting this the bandwidth community was applied as expected.