MPLS

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.]