MPLS
-
Support for LDP dual transport over IPv4 and IPv6 sessions with NSR configuration (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 24.2R1, you can configure the LDP dual transport mechanism to establish IPv4 and IPv6 sessions with NSR configurations. This configuration helps in forwarding IPv4 and IPv6 traffic and to support LDP IPv6 sessions in a routing instance.
[See Carrier-of-Carrier VPNs, LDP Overview, and LDP Configuration.]
-
Distributed CSPF support for IPv6-based SR-TE (ACX7024 and PTX10001-36MR)—Starting in Junos OS Evolved Release 24.2R1, we support distributed CSPF path computation and auto-translation of IPv6 addresses through SR-TE configuration. A path’s destination address family determines the address family of the SIDs used for the path. Configuring IPv6 addresses through SR-TE results in auto-translation of IPv6 addresses to the associated SIDs. IPv6 hops are defined in compute segment-lists.
Use the following CLI configurations to enable auto-translation of IPv6 addresses:
user@host# set protocols source-packet-routing segment-list name auto-translate user@host# set protocols source-packet-routing segment-list name name ip-address IPv6-address
Use the following CLI configurations to define IPv6 hops in compute segment-lists:
user@host# set protocols source-packet-routing compute-profile name compute-segment-list name user@host# set protocols source-packet-routing segment-list name compute user@host# set protocols source-packet-routing segment-list name name ip-address IPv6-address
Use the following CLI configurations to enable IPv6 path end points:
user@host# set protocols source-packet-routing compute-profile name … user@host# set protocols source-packet-routing source-routing-path name to IPv6-address user@host# set protocols source-packet-routing source-routing-path name primary name compute compute-profile-name
Note:End points must be IPv6 router IDs. Other addresses can be router IDs or interface addresses.
The
show spring-traffic-engineering lspcommand has been enhanced to show the details of IPv6 addresses. -
Support for MPLS-over-GRE through next hop-based dynamic tunnel (ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, and ACX7024X)—Starting in Junos OS Evolved Release 24.2R1, you can configure next-hop-based MPLS-over-GRE tunnels along with firewall filter-based tunnel decapsulation. MPLS-over-GRE tunnels create a tunnel composite next hop, an indirect next hop, and a forwarding next hop to resolve a tunnel destination route.
You can configure dynamic GRE next-hop-based tunnel by including the
gre next-hop-based-tunnelstatement at the[edit routing-options dynamic-tunnels]hierarchy.You can configure MPLS-over-GRE firewall filter-based decapsulation by including the
grestatement at the[edit firewall family family-name filter filter-name term term-name then decapsulate]hierarchy level. Only decapsulate action is supported in the firewall filter rule. MPLS-over-GRE firewall filter-based decapsulation is supported for family inet and inet6.You can retrive encapsulation tunnel statistics by configuring specific interval using the
intervalstatement at the[edit routing-options dynamic-tunnels statistics]hierarchy level.