Source Packet Routing in Networking (SPRING) or Segment Routing
-
Support for IPv6 endpoints for SR-MPLS DTM SR-TE tunnels (MX10003, MX10004, MX10008, and MX10016)—Starting in Junos OS Release 24.2R1, we support IPv6 end points for SR-MPLS DTM segment routing–traffic engineering (SR-TE) tunnels. You can configure IPv6 destination networks under spring-te dynamic tunnels and support dynamic segment list and DCSPF (using compute-profile). The following SR-TE dynamic tunnel models are supported:
-
IPv6 endpoint for DTM uncolored SR-TE tunnels
-
IPv6 endpoint for DTM SR-TE tunnels (SR-MPLS) with inet6color.0 model
-
IPv6 endpoint for DTM SR-TE tunnels (SR-MPLS) with transport-rib model
To support transport-rib model for IPv6 DTM SR-TE tunnels, include the
use-transport-classstatement at the [edit dynamic-tunnels tunnel-name spring-te] hierarchy level.If the
use-transport-classstatement is not configured, then, catch all route and application route is created in the inet6color.0 table. If theuse-transport-classstatement is configured then catch all route and application route is created in color.inet6.3 table. This behavior is irrespective of using theuse-transport-classstatement at the [edit protocols source-packet-routing] hierarchy level. For DT tunnels, SR-TE takes preference of theuse-transport-classstatement at the [edit dynamic-tunnels tunnel-name spring-te] hierarchy rather than at the [edit protocols source-packet-routing] hierarchy level. -
-
BGP classful transport support for dynamic tunnels and colored transport-rib for next-hop-based tunnels (MX304, MX10004, and MX10008)—Starting in Junos OS Release 24.2R1, we support colored transport-rib model for next-hop-based dynamic tunnels. By default GRE tunnels are logical interface-based tunnels. IPIP and UDP tunnels are next-hop based tunnels. GRE tunnels can also be configured as next-hop based tunnels by including the GRE
next-hop-based-tunnelstatement at the [edit routing-options dynamic-tunnels] hierarchy level.For logical interface and next-hop-based tunnels, dynamic tunnel specific route addition is triggered when an application route with protocol next-hop is resolved on dynamic tunnel catch-all route.
To support colored transport-rib model for DTM next-hop based tunnels, you should configure the
use-transport-classstatement under the [edit dynamic-tunnels tunnel-name] configuration. If theuse-transport-classstatement is not configured then catch all route and application route is created in the inet(6)color.0 table. If theuse-transport-classstatement is configured then catch all route and application route is created in the color.inet(6).3 table. If you include thebest-effortstatement at the [edit routing-options dynamic-tunnels dynamic-tunnel-name destination-networks ip-address] hierarchy level, dynamic tunnels are created in the inet(6)color.0 table.To enable the
use-transport-classstatement under dynamic tunnel, you should includeauto-createstatement at the [edit routing-options transport-class] hierarchy level.To configure colored transport-rib, you should include the
preserve-nexthop-hierarchystatement at the [edit routing-options resolution] hierarchy level.