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

PDF

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

Configure Import and Export Route Control Using the GUI

Updated: April 17, 2026

Want to summarize with AI?

Log in

Creates import and export route control profile policies for an L3Out and enables policy enforcement through the Cisco APIC GUI.

Before you begin

  • Configure the tenant, VRF, and bridge domain.

  • Configure the L3Out for the tenant.

This example uses a BGP L3Out. You can also configure import and export route control for an OSPF L3Out.

Import route control is not enforced by default. Enable import enforcement after you create the route control profile policy.

Procedure

  1. Navigate to Tenants > tenant-name > Networking > L3Outs > l3out-name.

  2. Right-click the l3out-name L3Out, and choose Create Route Map for Import and Export Route Control.

  3. Configure the route control profile policy:

    1. In the Create Route Map for Import and Export Route Control dialog box, choose or enter a route control profile policy name in the Name field.
    2. From the Type drop-down list, choose Match Prefix and Routing Policy.
    3. In the Contexts area, click the + icon.

      The Create Route Control Context dialog box opens.

  4. Configure the route control context:

    1. In the Order field, enter the sequence number.
    2. In the Name field, enter a name for the route control context.
    3. From the Match Rule drop-down list, choose Create Match Rule for a Route Map.
    4. In the Create Match Rule dialog box, enter a name, configure the required community regular-expression terms and community terms, and click Submit.
    5. From the Set Rule drop-down list, choose Create Set Rules for a Route Map.
    6. In the Create Set Rules for a Route Map dialog box, enter a name in the Name field.
    7. Select the required set rules, configure their values, and click Finish.
    8. In the Create Route Control Context dialog box, click OK.
    9. In the Create Route Map for Import and Export Route Control dialog box, click Submit.

  5. Navigate to Route Profiles > route-profile-name > route-control-context-name, and verify the route control profile policy and associated set rule in the work pane.

  6. In the navigation pane, choose the l3out-name L3Out, and click the Policy tab.

  7. Under Route Control Enforcement, select Import.

    BGP and OSPF support import route-control enforcement. EIGRP ignores this setting. BGP, EIGRP, and OSPF support export route control.

    Note

    When BGP is established over OSPF, import route control applies to BGP and is ignored for OSPF.

  8. Create a custom export route control profile policy:

    1. Right-click Route Maps for Import and Export Route Control, choose Create Route Map for Import and Export Route Control, and enter an export policy name in the Name field.
    2. In the Contexts area, click the + icon.
    3. In the Create Route Control Context dialog box, enter a sequence number in the Order field.
    4. In the Name field, enter a name for the route control context.
    5. Optional: From the Match Rule drop-down list, choose Create Match Rule for a Route Map, and configure a match rule.
    6. From the Set Rule drop-down list, choose an existing set rule or Create Set Rules for a Route Map.
    7. If you create a set rule, enter a name in the Name field.
    8. Select the required set rules, configure their values, and click Finish.
    9. In the Create Route Control Context dialog box, click OK.
    10. In the Create Route Map for Import and Export Route Control dialog box, click Submit.

  9. Associate the export policy with the external EPG:

    1. Navigate to L3Outs > l3out-name > External EPGs > external-epg-name.
    2. Expand Route Control Profile.
    3. From the Name drop-down list, choose the export policy that you created.
    4. From the Direction drop-down list, choose Route Export Policy, and click Update.

Import route-control enforcement is enabled on the L3Out, and the export route control profile policy is associated with the external EPG.