Cisco APIC Layer 3 Networking Configuration Guide, Release 6.2(x)

PDF

Cisco APIC Layer 3 Networking Configuration Guide, Release 6.2(x)

Route control profile policies

Want to summarize with AI?

Log in

Explains how route control profile policies and action rule profiles apply route-map set clauses to routes that enter or leave the ACI fabric.


Route control profile policies control routes that enter or leave the ACI fabric. Action rule profiles define the route-map set clauses that the policies apply.

Route control profile properties and application

The table lists the route-map set clauses that action rule profiles support for each routing protocol.

Table 1. Action rule profile properties

Property

OSPF

EIGRP

BGP

Description

Set community

No

No

Yes

Supports regular and extended BGP communities.

Set additional community

No

No

Yes

Supports regular and extended BGP communities.

Route tag

Yes

Yes

No

Supports bridge domain subnets only. The system always assigns tag 4294967295 to transit prefixes.

Preference

No

No

Yes

Sets the BGP local preference.

Metric

Yes

Yes

Yes

Sets the BGP multi-exit discriminator (MED). For EIGRP, changes the metric but does not support specifying the EIGRP composite metric.

Metric type

Yes

No

No

Supports OSPF Type 1 and OSPF Type 2 metrics.

You can reference a route control profile policy from these objects:

  • Tenant bridge domain subnet

  • Tenant bridge domain

  • External EPG

  • External EPG import or export subnet

The system applies route control profile policies in this order:

  1. Fabric routes: tenant bridge domain subnet, tenant bridge domain, and L3Out.

  2. Transit routes: external EPG prefix, external EPG, and L3Out.

Note

You can use route-map policies, including match and set rules, only in the tenant where you create them. You can use a route-map policy created in the common tenant only in the common tenant.

Import route control for BGP

To set the BGP local preference for routes from autonomous system AS300, enable import route control enforcement on the L3Out. Configure an action rule profile that sets the local preference to 200. On the external EPG, configure the 0.0.0.0/0 import aggregate policy to allow all routes.

Run the show ip bgp vrf vrf-name command to display the MP-BGP table. Verify that prefix 151.0.1.0/24 has a local preference of 200.