Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

MPLS

  • OAM support for labeled IS-IS and labeled OSPF flexible algorithm SR paths (PTX10001-36MR, PTX10003, PTX10004, PTX10008, QFX5130-32CD, and QFX5220)—Starting in Junos OS Evolved Release 23.1R1, Junos OS supports the following Operation, Administration, and Maintenance (OAM) capabilities for labeled IS-IS Flexible Algorithm (flex algo) segment routing paths:

    • IPv4 and IPv6 MPLS ping

    • IPv4 and IPv6 MPLS traceroute

    • Equal-cost multipath (ECMP) traceroute

    Junos OS Evolved 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.]

  • Support to report path optimization and computed metrics in PCEP (PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5220, QFX5230-64CD, and QFX5700)—Starting in Junos OS Evolved Release 23.1R1, we report PCEP path optimization metrics (IGP, TE, and delay) and computed metrics 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.]