About Route Map/Profile
The route profile is a logical policy that defines an ordered set (rtctrlCtxP) of logical match action rules with associated set action rules. The route profile is the logical abstract of a route map. Multiple route profiles can be merged into a single route map. A route profile can be one of the following types:
-
Match Prefix and Routing Policy: Pervasive subnets (fvSubnet) and external subnets (l3extSubnet) are combined with a route profile and merged into a single route map (or route map entry). Match Prefix and Routing Policy is the default value.
-
Match Routing Policy Only: The route profile is the only source of information to generate a route map, and it will overwrite other policy attributes.
Note |
When explicit prefix list is used, the type of the route profile should be set to "match routing policy only". |
After the match and set profiles are defined, the route map must be created in the Layer 3 Out. Route maps can be created using one of the following methods:
-
Create a "default-export" route map for export route control, and a "default-import" route map for import route control.
-
Create other route maps (not named default-export or default-import) and setup the relation from one or more l3extInstPs or subnets under the l3extInstP.
-
In either case, match the route map on explicit prefix list by pointing to the rtctrlSubjP within the route map.
In the export and import route map, the set and match rules are grouped together along with the relative sequence across the groups (rtctrlCtxP). Additionally, under each group of match and set statements (rtctrlCtxP) the relation to one or more match profiles are available (rtctrlSubjP).
Any protocol enabled on Layer 3 Out (for example BGP protocol), will use the export and import route map for route filtering.