Describes how L3Out policies control route import and export, default-route leaking, route attributes, and BGP or OSPF configuration for transit routing.
Transit route control is a routing-policy capability that
-
controls route import and export through Layer 3 external network profiles (
l3extInstP), -
defines route-control policies in an
l3extOutpolicy, and -
uses the
enforceRtctrlproperty to specify the route-control directions.
Route-control and routing-protocol configuration
Properties and relations of the l3extOut managed object control transit routes. By default, every route has import scope. Export route maps use prefix-list matches.
To enable default-route leaking, define the l3extDefaultRouteLeakP managed object under the l3extOut managed object.
The following set-rule managed objects modify route attributes:
-
Route preference:
rtctrlSetPref -
Route metric:
rtctrlSetRtMetric -
Route metric type:
rtctrlSetRtMetricType
The rtctrlSetComm managed object supports the following BGP community values:
-
no-advertise -
no-export -
no-peer
To enable BGP peering, define the bgpExtP managed object under an l3extOut managed object. Define at least one peer policy on each border leaf switch by using a physical interface or loopback interface.
The
l3extOutpolicy specifies the routing protocol, and the L3Out interface profile specifies the interface configuration. Both configurations are required to enable the protocol.
To enable OSPF, define an ospfExtP managed object under an l3extOut managed object. To configure OSPF policies at the VRF level, use the fvRsCtxToOspfCtxPol relation.