Explains how a route control profile policy organizes ordered match and set rules and generates route maps for route filtering on an L3Out.
A route control profile policy logically represents a route map. It contains ordered route control contexts (rtctrlCtxP) that combine match rules with set rules.
The system can merge multiple route control profile policies into a single route map.
Route control profile types
A route control profile policy supports the following types:
-
Match Prefix and Routing Policy combines pervasive subnets (
fvSubnet) and external subnets (l3extSubnet) with the route control profile policy and merges the information into a route map or route-map entry. This is the default type. -
Match Routing Policy Only uses only the route control profile policy to generate the route map. The policy overrides other route-control attributes.
When you use an explicit prefix list, set the route control profile policy type to Match Routing Policy Only.
Route map creation methods
The system creates route maps in these ways:
-
Creates the
default-exportroute map for export route control and thedefault-importroute map for import route control. -
Creates a route map from relationships to one or more external EPGs (
l3extInstP) or subnets under an external EPG. -
Matches an explicit prefix list by referencing a match profile (
rtctrlSubjP) from the route control profile policy.
For import and export route maps, each route control context (rtctrlCtxP) groups match rules and set rules and defines their relative sequence. Each context can reference one or more match profiles (rtctrlSubjP). Routing protocols enabled on the L3Out, such as BGP, use the import and export route maps to filter routes.