This section describes how the matrix of include or exclude colors in a route-admin-tag-policy policy-name, which is assigned to a route, are matched against LSP internal colors. This is a generic algorithm. The following sections provide further details of how this applies to specific use cases.
Internal color matching occurs before any resolution filter is applied.
The following selection process assumes the system starts with a set of eligible RSVP and SR-TE LSPs to the appropriate BGP next hop.
Prune the following RSVP and SR-TE LSPs from the eligible set:
uncolored LSPs
LSPs where none of the internal colors match any "include" color for the route
LSPs where any of the internal colors match any "exclude" color for the route
If none of the LSPs match, then the default behavior is that the route does not resolve. Depending on the context, configure a fall-back method, as described in LSP admin tag use in tunnel selection for VPRN and E-VPN auto-bind.
If a route does not have an admin-tag policy, it is assumed that the operator does not want to express a preference for the LSP to use. Therefore, routes with no admin-tag policy can still resolve to any tagged or untagged LSP.
This selection process results in a set of one or more ECMP LSPs, which may be further reduced by a resolution filter.