Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

IPv6

  • SRv6-TE micro-SID support for transport and L3VPN (ACX7348 and ACX7509)—Starting in Junos OS Evolved Release 23.4R1, we extend the micro-segment identifier (micro-SID) support for SRv6 traffic engineering (TE). We support SR-TE micro-SID only with default block configurations across the whole network domain. However, if any block configurations are present, then those configurations must be the same throughout the network. The Packet Forwarding Engine supports the bit shifting operation for both <block>:<uN>:<uA> and <block>:<uA> routes. You must configure the full SID, the way it is advertised in the IS-IS IGP—that is, <block>:<uN> or <block>:<uN>:<uA>.

    We’ve introduced the following two configuration statements:

    • micro-srv6-sid statement under the protocols source-packet-routing segment-list <name> <hop-name> hierarchy to configure micro-SIDs in an SR-TE SRv6 segment list

    • strict-adjacency statement under the protocols source-packet-routing segment-list <name> <hop-name> hierarchy to strictly follow the micro-adjacency SID

    You can configure the segment list containing micro-SIDs with the existing srv6 configuration statement like the traditional SRv6 configuration. The only difference between the traditional and micro-SID configuration is that in the traditional SRv6-TE segment-list configuration, you must use the configuration statement srv6-sid. However, for micro-SID configuration, you must use the new configuration statement micro-srv6-sid.

  • Operations, Administration, and Maintenance (OAM) ping and traceroute support for SRv6 uSID (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7348, and ACX7509)—Starting in Junos OS Evolved Release 23.4R1, we support pinging an SRv6 micro-segment identifier (uSID) to verify that the uSID is reachable and is locally programmed at the target node. We also support tracerouting to an SRv6 uSID for hop-by-hop fault localization as well as path tracing to a uSID.

    As part of this feature, we support SRv6 uSID ping and traceroute for the following SIDs:

    • SRv6 IS-IS ping and traceroute for end behavior with NEXT-CSID (uN)/uN+End.X behavior with NEXT-CSID (uA)/uN+End.DT behavior with NEXT-CSID (uDT) SIDs

    • SRv6 IS-IS ping and traceroute for compressed SIDs (compressed SID to be provided by user) for uN/uA/uDT

    • SRv6 micro-SIDs-stack ping and traceroute for uN/uN+uA/nN+uDT SIDs

    We’ve introduced the following commands for this feature:

    • ping srv6 spring-te micro-sids-stack nexthop-address <nh-addr> nexthop-interface <if-name> usids [usid1 usid2 …]

    • traceroute srv6 spring-te micro-sids-stack nexthop-address <nh-addr> nexthop-interface <if-name> usids [usid1 usid2 …]

    • traceroute srv6 spring-te micro-sids-stack nexthop-address <nh-addr> nexthop-interface <if-name> usids [usid1 usid2 …] probe-icmp

  • Optimizing ARP, NDP and Default-Route handling in internal DB of DCD (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved 23.4R1, DCD only deletes routing entries for addresses that are completely unlinked from all associated addresses. Additionally, we introduce checks to prevent configuring multiple static MAC addresses for a single ARP and NDP address, which helps improve system stability and avoid potential conflicts in network configurations.