Lists the configuration methods, naming limits, protocol support, management-tool restrictions, and per-peer alternatives for route maps associated with an L3Out.
Route-map configuration for an L3Out has restrictions on prefix configuration methods, generated-name length, protocol support, and management tools.
Route Map Configuration Constraints
Follow these guidelines when you configure route maps:
-
Use only one of the following methods to configure prefixes for a route map:
-
Configure routes under a bridge domain and associate the bridge domain with the L3Out.
-
Configure match prefixes under a match profile (
rtctrlSubjP).
Using both methods creates duplicate entries and an undefined route map.
-
-
The generated name of a route map under an L3Out must contain fewer than 93 characters. The following values contribute to the length:
Route Profile name + Route Profile context name + Route Profile match rule name < 93 characters -
The implicit
deny-staticentry is not supported in an export route map. Explicitly configure the permit and deny entries that control static-route export. -
Per-peer route maps are supported for BGP. OSPF and EIGRP support route maps only at the L3Out level.
-
Do not use a combination of the GUI and API to create one route map. A route map created through the GUI at the L3Out level cannot be applied to an individual peer.
If a protocol does not support a per-peer route map, use one of the following alternatives:
-
Block the prefix from being advertised by the remote neighbor.
-
Block the prefix in the route map on the existing L3Out, move the neighbor to another L3Out on which the prefix is required, and configure a separate route map.