Routing Protocols
-
BGP link bandwidth community ( QFX5130-32CD, QFX5130E-32CD, QFX5130-48C, QFX5700, QFX5700E, QFX5220, QFX5230-64CD, QFX5240-64OD, QFX5240-64QD)—Starting in Junos OS Evolved Release 23.4R2, BGP can communicate link speeds to remote peers, enabling better optimization of traffic distribution for load balancing. A BGP group can send the link-bandwidth non-transitive extended community over an EBGP session for originated or received and readvertised link-bandwidth extended communities.
To configure the non-transitive link bandwidth extended community, include the
bandwidth-non-transitive:value
in the export policy at the[edit policy-options community name members community-ids]
hierarchy level.To enable the device to automatically detect and attach the link-bandwidth community on a route at import, include the
auto-sense
statement at the[edit protocols bgp group link-bandwidth]
hierarchy level. This feature facilitates the integration of devices with different transmission speeds within the network, enabling efficient traffic distribution based on link speed.[See auto-sense, and group (Protocols BGP).]
-
Minimum ECMP (QFX5130-32CD, QFX5130-48C, QFX5220, QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)—Starting in Junos OS Evolved Release 23.4R2, we support conditional advertising and withdrawal of BGP routes based on certain constraints such as bandwidth and minimum available next-hop ECMP. When a BGP receiver learns the same route from multiple BGP peers, BGP updates the active BGP path and the routing information base (RIB), also known as the routing table. The BGP export policy determines whether to advertise the BGP route to these next hops based on the number of ECMP BGP peers it receives the prefix from. A BGP route that has multiple ECMP BGP peers creates better resiliency in case of link failures. You can configure a BGP export policy to withdraw a BGP route unless it receives the BGP route prefix from a minimum number of ECMP BGP peers.