Routing Protocols
-
Support for accepting BGP routes with
accept-own
community (MX480 and MX960)—Starting in Junos OS Release 21.4R1, MX480 and MX960 routers accept BGP routes with theaccept-own
community, defined by RFC 7611, BGP ACCEPT_OWN Community Attribute.The feature enhances the interoperability of a Juniper router by enabling it to accept routes whose
ORIGINATOR_ID
orNEXT_HOP
value matches that of the receiving BGP speaker. For example, when a provider edge (PE) device advertises routes with the route distinguisher of a source VRF, the route reflector attaches theaccept-own
community and re-advertises the routes back to the originator. The provider edge (PE) device can then import the routes into the other destination VRFs, excluding its own.[See BGP accept-own Community and accept-own.]
-
OSPF link delay measurement and advertising (ACX Series, MX Series, PTX Series, and QFX Series)—Starting in Junos OS Release 21.4R1, you can measure and advertise various performance metrics in IP networks with scalability through probe messages that are sent by Two-Way Active Measurement Protocol (TWAMP) Light. OSPF receives probe messages and the measured values from TWAMP Light. OSPF advertises these messages as TLVs in packets. You can use these metrics to make path-selection decisions based on the network performance.
[See How to Enable Link Delay Measurement and Advertising in OSPF.]
-
Support for FAD and FAPM on traffic engineering database and BGP-LS (ACX Series, MX Series, and PTX Series)—Starting in Junos OS Release 21.4R1, we support FlexAlgo Definition (FAD) and FlexAlgo Prefix Metric (FAPM) on the traffic engineering database and BGP Link State (BGP-LS). You can store FAD and FAPM entries in the traffic engineering database and BGP-LS. You can also store multiple prefix segment identifiers (SIDs) for a prefix in BGP-LS. You can import the FAD and FAPM entries from the traffic engineering database to BGP-LS and export the FAD entries from BGP-LS to the traffic engineering database.