Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

MPLS

  • RSVP updates available bandwidth values without notifying IS-IS (PTX10001-36MR, PTX10003, PTX10004, PTX10008, QFX5130-32CD, and QFX5220)—When RSVP label-switched paths (LSPs) and segment routing LSPs coexist on a link, RSVP takes into account how much bandwidth the segment routing LSPs use. By default, RSVP updates the values for the local unreserved bandwidth and the maximum available bandwidth and passes the values on to IS-IS. Starting in Junos OS Evolved Release 21.3R1, you can configure RSVP to update available bandwidth values without notifying IS-IS if the bandwidth change is within a certain threshold configured at the [edit protocols rsvp interface interface-name update-threshold-max-reservable].

    If you configure the local-bw-override-threshold statement at the [edit protocols rsvp interface interface-name non-rsvp-bandwdith] hierarchy level, RSVP always updates the available bandwidth values. However, it reports only the new values to IS-IS if the bandwidth change passes the threshold.

    [See update-threshold-max-reservable and local-bw-override-threshold.]

  • BGP-CT planes to facilitate service mapping over colored tunnels (PTX10001-36MR, PTX10004, and PTX10008)—Starting in Junos OS Evolved Release 21.3R1, you can classify colored transport tunnels (RSVP, IS-IS flexible algorithm) in your network into transport classes and map service routes over an intended transport class. You can also extend the transport tunnels to span across multiple domains (autonomous systems (ASs) or IGP areas) by using the new BGP transport address family called BGP Classful Transport (BGP-CT).

    [See BGP Classful Transport Planes Overview.]

  • BGP route service API supports programming routes with IP-IP encapsulation attributes (PTX10001-36MR, PTX10004, and PTX10008)—Starting in Junos OS Evolved Release 21.3R1, you can use the BGP route service API to program BGP routes with IP over IP (IP-IP) encapsulation attributes. You can specify the tunnel type, the remote endpoint address, and the color of the route. Keep the following in mind:

    • The egress endpoint must be a unicast IPv4 address.
    • The colors encoded in tunnel_encap and extended_community must match.
    • If the encapsulation ext_com and the tunnel attribute are both present, the egress endpoint must match the next-hop address.

    To enable this feature, configure the bgp-signal option at the [edit routing-options dynamic-tunnels tunnel-name] hierarchy level.

    [See dynamic-tunnels and JET APIs on Juniper EngNet.]

  • Support for express segments to establish end-to-end segment routing paths (PTX10001-36MR, PTX10003, and PTX10008)—Starting in Junos OS Evolved Release 21.3R1, you can use express segments to establish end-to-end traffic engineering paths between interconnected traffic engineering networks. Express segments (also known as virtual traffic engineering links) are generated dynamically through policies matching the underlay LSPs. Express segments and the corresponding abstracted topology (required by RFC7926) are generated with policies.

    [See Express Segment LSP Configuration.]