MPLS

• IPv4 and IPv6 MPLS ping

• IPv4 and IPv6 MPLS traceroute

• Equal-cost multipath (ECMP) traceroute

Junos OS also supports IPv4 MPLS ping and IPv4 MPLS traceroute for labeled OSPF flex algo segment routing paths. The OAM functionality is used to detect data plane failures in segment routing paths for the purposes of fault detection and isolation.

To enable these OAM capabilities, we've introduced the algorithm option in the following commands:

• ping mpls segment routing isis fec algorithm algorithm-id

• ping mpls segment routing ospf fec algorithm algorithm-id

• traceroute mpls segment routing isis fec algorithm algorithm-id

• traceroute mpls segment routing ospf fec algorithm algorithm-id

[See ping mpls segment routing isis, ping mpls segment routing ospf, traceroute mpls segment-routing ospf, and traceroute mpls segment-routing isis.]

Include IGP metric to RSVP routes using conditional metric (MX10004, MX10008, and MX10016)—Starting in Junos OS Release 23.1R1, you can include the actual IGP metric to RSVP routes that use the conditional metric. Including the IGP metric helps preserve its value for use in certain use cases—for example, in calculating the BGP MED.

[See Preserving the IGP metric in RSVP LSP routes, and include-igp-metricinclude-igp-metric.]

Targeted load-balancing support for business edge customers using PWHT service interfaces (MX Series)—Starting in Junos OS Release 23.1R1, we support targeted load balancing on pseudowire headed termination (PWHT) service interfaces. If you configure the member links of a redundant logical tunnel (RLT) in active-active mode with targeting on PWHT service interfaces, then traffic gets distributed to specific logical tunnel interfaces on different Packet Forwarding Engines. You use distribution lists to manage targeted load balancing. With this feature, you guarantee accurate shaping or policing by adding only a one-member logical tunnel interface to a distribution list.

[See PWHT RLT Configuration Modes].

PWHT Support for family mpls (MX Series)—Starting in Junos OS Release 23.1R1, we support family mpls on pseudowire headend termination (PWHT) service interfaces using inter-AS Option B. MX Series devices support for the following features on PWHT service interfaces:

• MPLS, including MPLS-IPv4 and MPLS-IPv6

• MPLS CoS

• MPLS inline active flow monitoring

[See Interprovider VPNs, Inline Flow Monitoring Overview, and MPLS CoS Configuration].

Enable TLS for PCEP sessions (ACX5448, ACX5448-D, ACX5448-M, MX150, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, and vMX)—Starting in Junos OS Release 23.1R1, you can enable Transport Layer Security (TLS) in a Path Computation Client (PCC) to establish a TCP connection with the Path Computation Element (PCE). This connection creates a secure Path Computation Element Protocol (PCEP) session to transport PCEP messages.

To enable TLS in a PCC process (PCCD) and to establish a PCEP session, set the tls-strict configuration statement at the [edit protocols pcep] hierarchy level.

[See Enabling Transport Layer Security for PCEP Sessions.]

Support to report path optimization and computed metrics in PCEP (ACX710, ACX5448, ACX5448-M, ACX5448-D, MX150, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, and vMX)—Starting in Junos OS Release 23.1R1, we report PCEP path optimization metrics (IGP, TE, and delay) for RSVP and segment routing–traffic engineering (SR-TE) label-switched paths (LSPs).

To configure the interior gateway protocol (IGP), traffic engineering, and path delay optimization metrics for RSVP LSPs, include the metric-type igp|te|delay|delay minimum CLI statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level.

To configure the optimization metrics for SR-TE LSPs, include the metric-type igp|te|delay|delay minimum CLI statement at the [edit protocols source-packet-routing compute-profile compute-profile-name] hierarchy level.

[See Reporting Path Optimization Metrics in PCEP.]