The following services can resolve their next hop over an SRv6 policy in TTMv6:
As with MPLS SR policies, the next hop resolution is based on the color (if present) and on the comparison of the next hop with the SR policy endpoint. The color, the endpoint, and the head end define a matching policy, but a matching policy can be an SR MPLS policy or an SRv6 policy. Therefore, the service also uses the data plane technology of the policy to select the tunnel type to resolve over:
An SRv6 service cannot fall back to an MPLS tunnel type. Suppose the configuration of the resolution allows an SRv6 policy, but an SRv6 policy with a matching color and endpoint does not exist in TTMv6. In that case, the SRv6 service can fall back to any SRv6 shortest path tunnel in TTMv6 or RTM, if the locator of the tunnel matches the locator of the SRv6 service.
tunnel-table
Resolve the route to a tunnel in TTMv6. The system tries to find an SRv6 policy with a matching color and endpoint locator for BGP routes received with an SRv6 TLV and containing an SRv6 service SID in the IPv6 tunnel table. If none is found, the resolution fails.
route-table
Resolve the route to an IPv6 route in RTM. If none is found, the resolution fails. This is the default behavior.
fallback-tunnel-to-route-table
First try resolving the route to a tunnel in the IPv6 tunnel table. If none is found, fall back to resolving the route in RTM. If none is found, the resolution fails.
Use the resolution command in the following contexts to configure the resolution options:
configure router bgp segment-routing-v6 familyconfigure service vprn bgp-ipvpn segment-routing-v6configure service epipe bgp-evpn segment-routing-v6configure service vpls bgp-evpn segment-routing-v6configure service vprn bgp-evpn segment-routing-v6