MPLS

RSVP signaling over IS-IS nonforwarding adjacency (PTX10008)—Starting in Junos OS Evolved Release 22.1R1, you can configure any Level 1-Level 2 (L1-L2) routers that have been configured as a flood-reflector client to expand the flood-reflector hops in the Explicit Route Objects (EROs) carried in the Path messages. This feature enables the L1-L2 routers to signal RSVP over IS-IS nonforwarding adjacency by expanding the flood-reflector hops in the EROs instead of propagating the Path messages over the UDP tunnels.

To know how to configure the flood-reflector interfaces, see How to Configure Flood-Reflector Interfaces in IS-IS Networks.

To expand the flood-reflector hops in EROs, use the rsvp expand-flood-reflector-hop configuration statement at the [edit protocols] hierarchy level.

Using the traceoptions (Protocols RSVP) command with the flag event option, you can view the new trace messages in the file that is created.

The show ted database and show rsvp session command outputs introduce the following additional information:

[See How to Configure Flood-Reflector Interfaces in IS-IS Networks, show ted database, show rsvp session, and traceoptions (Protocols RSVP).]

MPLS TTL propagation flexibility for LDP-signaled LSPs (PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016)—Starting in Junos OS Evolved Release 22.1R1, we support disabling time-to-live (TTL) propagation at a more granular level. You can disable it specifically for LDP-signaled label-switched paths (LSPs). When a route is very long, disable TTL propagation to ensure the TTL doesn't expire while the packet is traversing the path. This feature also gives you more flexibility in hiding your network topology.

To disable TTL propagation for LDP-signaled LSPs, use the no-propagate-ttl statement at the [edit protocol ldp] hierarchy.

Note: If the TTL value of the top label is less than the TTL value of the bottom label at an egress node, Junos OS copies the TTL value from the top label to the bottom label. In this case, the TTL value can still propagate down even when no-propagate-ttl is configured.

[See no-propagate-ttl.]

Supports MD5 authentication algorithm for subnet level configuration (ACX Series, PTX Series, and QFX Series)—Starting from Junos OS Evolved 22.1R1 Release, MD5 authentication algorithm for subnet level key configuration is supported for all Junos OS Evolved platforms. Whereas, aes-128-cmac-96 and hmac-sha-1-96 algorithms are not supported for subnet level key configuration in Junos OS Evolved Releases.

[See session-group and Configuring the TCP MD5 Signature for LDP Sessions.]