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 (ACX7100-32C, ACX7100-48L, ACX7509, and ACX7024)—Junos OS Evolved 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 for MPLS Layer 2 Connections on subscriber stacking models using dynamic PWHT Interfaces (ACX7100-48L, ACX7332, ACX7348)—Subscriber management and stacking models using PPPoE, DHCPv4, and DHCPv6 over dynamic PWHT interfaces are fully supported for L2CKT, L2VPN, and EVPN types. Use the existing configuration commands under the appropriate interface to configure these options.

    [See MPLS Pseudowire Configuration, Pseudowire Headend Termination (PWHT) Configuration, Pseudowire Termination at an EVPN, and Layer 2 Circuit Overview.]

  • Support for L2VPN and L2CKT over SR-TE (ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, ACX7024X)—We now support L2VPN and L2CKT configurations and features over segment routing-traffic engineered (SR-TE) networks. Supported features include metro services, entropy labels, FAT labels, and pseudowire redundancy. You can see the L2VPN and L2CKT status for SR-TE configurations using the show l2vpn connections and show l2circuit connections commands.

    [See MPLS Traffic Engineering Configuration, show l2vpn connections, and show l2circuit connections.]

  • SRv6-TE tunnels with micro-SIDs in PCEP (ACX7100-32C, ACX7100-48L, ACX7024, ACX7332, ACX7348, ACX7509, and PTX10002-36QDD)—This feature enhances traffic engineering and network optimization by enabling the reporting, delegation, and creation of these tunnels. You can report and delegate static SRv6-TE tunnels with micro-SID configurations to a PCE and initiate these tunnels through PCE, improving control and management. Key functionalities include reporting static SRv6-TE tunnels with micro-SIDs to the PCE, delegating their management, and creating them with proper SID structure and endpoint behavior checks. Existing CLI commands are extended to support these features, facilitating effective configuration and monitoring.

    [See SRv6-TE Tunnels with micro-SIDs in PCEP.]

  • PCEP multipath support for SR-TE (ACX7100-32C, ACX7100-48L, ACX7024, ACX7024X, ACX7332, ACX7348, and ACX7509)—You can configure the multipath feature (primary or secondary paths) for Path Computation Element Protocol (PCEP) segment routing-traffic engineering (SR-TE) as defined in draft-ietf-pcemultipath-06. We support the following multipath capabilities:

    • When the PCEP multipath feature is enabled, you can configure multiple primary or secondary paths in a candidate path that you configure and control using Path Computation Client (PCC). Note that the PCEP multipath feature is enabled by default.

    • When the PCEP multipath feature is disabled, you can configure only one primary path in a candidate path. Note that a secondary path configuration is not allowed.

    The PCEP multipath feature removes the compute-profile restriction of 1 on the maximum number of segment lists (maximum-computed-segment-lists).

    Note:

    When PCEP multipath is enabled, PCCD will not send constraints for PCC-controlled candidate paths.

    [See PCEP Configuration.]

  • SRv6 and MPLS service interworking (ACX7100-32C, ACX7100-48L, ACX7024, ACX7348, and ACX7509)—SRv6 and MPLS service interworking feature enables seamless integration and interoperability between SRv6 and MPLS within a single network, enabling the translation of service instructions and ensuring proper traffic encapsulation and forwarding. This functionality is pivotal for networks transitioning to SRv6 while maintaining their existing MPLS infrastructure, providing a pathway for incremental deployment. This interworking feature supports both BGP SRv6 and BGP MPLS-based Layer 3 services, ensuring redundancy and scalability.

    The PCEP multipath feature removes the compute-profile restriction of 1 on the maximum number of segment lists (maximum-computed-segment-lists).

    [See Understanding SRv6 Network Programming and Layer 3 Services over SRv6 in BGP.]