Step 1

On the menu bar, click Tenant, and in the Navigation pane, expand Tenant_name > Networking > External Routed Networks > Match Rules for Route Maps.

Step 2

Right click Match Rules for Route Maps, and click Create Match Rule for a Route Map.

Step 3

In the Create Match Rule for a Route Map dialog box, enter a name for the rule and choose the desired community terms.

Step 4

In the Create Match Rule dialog box, expand Match Prefix and perform the following actions:

1. In the IP field, enter the explicit prefix list.

   The explicit prefix can denote a BD subnet or an external network.

2. Check the Aggregate check box only if you desire an aggregate prefix. Click Update, and click Submit.

   The match rule can have one or more of the match destination rules and one or more match community terms. Across the match types, the AND filter is supported, so all conditions in the match rule must match for the route match rule to be accepted. When there are multiple match prefixes in Match Destination Rules, the OR filter is supported. Any one match prefix is accepted as a route type if it matches.

Step 5

Under External Routed Networks, click and choose the available default layer 3 out.

Step 6

Right-click Route Maps/Profiles, and click Create Route Map/Profile.

Step 7

In the Create Route Map dialog box, use a default route map, or enter a name for the desired route map.

Step 8

In the Type field, choose Match Routing Policy Only.

Step 9

Expand the + icon to display the Create Route Control Context dialog box.

Step 10

Enter a name for route control context, and choose the desired options for each field. To deny routes that match criteria defined in match rule (Step 11), select the action deny. The default action is permit.

Step 11

In the Match Rule field, choose the rule that was created earlier.

Step 12

In the Set Rule field, choose Create Set Rules for a Route Map.

Step 13

In the Create Set Rules for a Route Map dialog box, enter a name for the action rule and check the desired check boxes. Click Submit.

Step 14

In the Create Route Control Context dialog box, click OK. And in the Create Route Map/Profile dialog box, click Submit.

Configure the route map/profile using explicit prefix list.

<?xml version="1.0" encoding="UTF-8"?>
<fvTenant name="PM" status="">
   <rtctrlAttrP name="set_dest">
      <rtctrlSetComm community="regular:as2-nn2:5:24" />
   </rtctrlAttrP>
   <rtctrlSubjP name="allow_dest">
      <rtctrlMatchRtDest ip="192.169.0.0/24" />
      <rtctrlMatchCommTerm name="term1">
         <rtctrlMatchCommFactor community="regular:as2-nn2:5:24" status="" />
         <rtctrlMatchCommFactor community="regular:as2-nn2:5:25" status="" />
      </rtctrlMatchCommTerm>
      <rtctrlMatchCommRegexTerm commType="regular" regex="200:*" status="" />
   </rtctrlSubjP>
   <rtctrlSubjP name="deny_dest">
      <rtctrlMatchRtDest ip="192.168.0.0/24" />
   </rtctrlSubjP>
   <fvCtx name="ctx" />
   <l3extOut name="L3Out_1" enforceRtctrl="import,export" status="">
      <l3extRsEctx tnFvCtxName="ctx" />
      <l3extLNodeP name="bLeaf">
         <l3extRsNodeL3OutAtt tDn="topology/pod-1/node-101" rtrId="1.2.3.4" />
         <l3extLIfP name="portIf">
            <l3extRsPathL3OutAtt tDn="topology/pod-1/paths-101/pathep-[eth1/25]" ifInstT="sub-interface" encap="vlan-1503" addr="10.11.12.11/24" />
            <ospfIfP />
         </l3extLIfP>
         <bgpPeerP addr="5.16.57.18/32" ctrl="send-com" />
         <bgpPeerP addr="6.16.57.18/32" ctrl="send-com" />
      </l3extLNodeP>
      <bgpExtP />
      <ospfExtP areaId="0.0.0.59" areaType="nssa" status="" />
      <l3extInstP name="l3extInstP_1" status="">
         <l3extSubnet ip="17.11.1.11/24" scope="import-security" />
      </l3extInstP>
      <rtctrlProfile name="default-export" type="global" status="">
         <rtctrlCtxP name="ctx_deny" action="deny" order="1">
            <rtctrlRsCtxPToSubjP tnRtctrlSubjPName="deny_dest" status="" />
         </rtctrlCtxP>
         <rtctrlCtxP name="ctx_allow" order="2">
            <rtctrlRsCtxPToSubjP tnRtctrlSubjPName="allow_dest" status="" />
         </rtctrlCtxP>
         <rtctrlScope name="scope" status="">
            <rtctrlRsScopeToAttrP tnRtctrlAttrPName="set_dest" status="" />
         </rtctrlScope>
      </rtctrlProfile>
   </l3extOut>
   <fvBD name="testBD">
      <fvRsBDToOut tnL3extOutName="L3Out_1" />
      <fvRsCtx tnFvCtxName="ctx" />
      <fvSubnet ip="40.1.1.12/24" scope="public" />
      <fvSubnet ip="40.1.1.2/24" scope="private" />
      <fvSubnet ip="2003::4/64" scope="public" />
   </fvBD>
</fvTenant>

Step 1

On the menu bar, click TENANTS > Tenant_name > Networking > External Routed Networks > Layer3_Outside_name .

Step 2

Right click Layer3_Outside_name and click Create Route Map.

Step 3

In the Create Route Map dialog box, perform the following actions:

1. From the Name field drop-down list, choose the appropriate route profile.

   Depending on your selection, whatever is advertised on the specific outside is automatically used.

2. In the Type field, choose Match Prefix AND Routing Policy.

3. Expand Order.

Step 4

In the Create Route Control Context dialog box, perform the following actions:

1. In the Order field, choose the desired order number.

2. In the Name field, enter a name for the route control private network.

3. From the Match Rule field drop-down list, click Create Match Rule For a Route Map.

4. In the Create Match Rule dialog box, in the Name field, enter a route match rule name. Click Submit.

   Specify the match community regular expression term and match community terms as desired. Match community factors will require you to specify the name, community and scope.

5. From the Set Attribute drop-down list, choose Create Set Rules For a Route Map.

6. In the Create Set Rules For a Route Map dialog box, in the Name field, enter a name for the rule.

7. Check the check boxes for the desired rules you want to set, and choose the appropriate values that are displayed for the choices. Click Submit.

   The policy is created and associated with the action rule.

8. Click OK.

9. In the Create Route Map dialog box, click Submit.

Step 5

In the Navigation pane, choose Route Profile > route_profile_name > route_control_private_network_name.

Step 6

In the Navigation pane, click the Layer3_Outside_name.

Step 7

(Optional) Click the Route Control Enforcement field and check the Import check box to enable the import policy.

Step 8

To create a customized export policy, right-click Route Map/Profiles, click Create Route Map, and perform the following actions:

1. In the Create Route Map dialog box, from the drop-down list in the Name field, choose or enter a name for the export policy.

2. Expand the + sign in the dialog box.

3. In the Create Route Control Context dialog box, in the Order field, choose a value.

4. In the Name field, enter a name for the route control private network.

5. (Optional) From the Match Rule field drop-down list, choose Create Match Rule For a Route Map, and create and attach a match rule policy if desired.

6. From the Set Attribute field drop-down list, choose Create Set Rules For a Route Map and click OK.

   Alternatively, if desired, you can choose an existing set action, and click OK

7. In the Create Set Rules For A Route Map dialog box, in the Name field, enter a name.

8. Check the check boxes for the desired rules you want to set, and choose the appropriate values that are displayed for the choices. Click Submit.

   In the Create Route Control Context dialog box, the policy is created and associated with the action rule.

9. Click OK.

10. In the Create Route Map dialog box, click Submit.

Step 9

In the Navigation pane, expand External Routed Networks > External_Routed_Network_name > Networks > Network_name, and perform the following actions:

1. Expand Route Control Profile.

2. In the Name field drop-down list, choose the policy created earlier.

3. In the Direction field drop-down list, choose Route Control Profile. Click Update.

Step 1

Import Route control using match community, match prefix-list

apic1# configure
apic1(config)# leaf 101 
    # Create community-list
apic1(config-leaf)# template community-list standard CL_1 65536:20 tenant exampleCorp
apic1(config-leaf)# vrf context tenant exampleCorp vrf v1 

     #Create Route-map and use it for BGP import control.
apic1(config-leaf-vrf)# route-map bgpMap
    # Match prefix-list and set route-profile actions for the match.
apic1(config-leaf-vrf-route-map)# ip prefix-list list1 permit 13.13.13.0/24 
apic1(config-leaf-vrf-route-map)# ip prefix-list list1 permit 14.14.14.0/24
apic1(config-leaf-vrf-route-map)# match prefix-list list1 
apic1(config-leaf-vrf-route-map-match)# set tag 200
apic1(config-leaf-vrf-route-map-match)# set local-preference 64
apic1(config-leaf)# router bgp 100 
apic1(config-bgp)# vrf member tenant exampleCorp vrf v1 
apic1(config-leaf-bgp-vrf)# neighbor 3.3.3.3
apic1(config-leaf-bgp-vrf-neighbor)# route-map bgpMap in

Step 2

Export Route Control using match BD, default-export route-profile

# Create custom and "default-export" route-profiles 
apic1(config)# leaf 101
apic1(config-leaf)# vrf context tenant exampleCorp vrf v1
apic1(config-leaf-vrf)# template route-profile default-export
apic1(config-leaf-vrf-template-route-profile)# set metric 256
apic1(config-leaf-vrf)# template route-profile bd-rtctrl
apic1(config-leaf-vrf-template-route-profile)# set metric 128

#Create a Route-map and match on BD, prefix-list
apic1(config-leaf-vrf)# route-map bgpMap
apic1(config-leaf-vrf-route-map)# match bridge-domain bd1
apic1(config-leaf-vrf-route-map-match)#exit
apic1(config-leaf-vrf-route-map)# match prefix-list p1
apic1(config-leaf-vrf-route-map-match)#exit
apic1(config-leaf-vrf-route-map)# match bridge-domain bd2
apic1(config-leaf-vrf-route-map-match)# inherit route-profile bd-rtctrl

Configure the route control protocol using import and export controls.

<l3extOut descr="" dn="uni/tn-Ten_ND/out-L3Out1" enforceRtctrl="export" name="L3Out1" ownerKey="" ownerTag="" targetDscp="unspecified">
        <l3extLNodeP descr="" name="LNodeP1" ownerKey="" ownerTag="" tag="yellow-green" targetDscp="unspecified">
            <l3extRsNodeL3OutAtt rtrId="1.2.3.4" rtrIdLoopBack="yes" tDn="topology/pod-1/node-101">
                <l3extLoopBackIfP addr="2000::3" descr="" name=""/>
            </l3extRsNodeL3OutAtt>
            <l3extLIfP descr="" name="IFP1" ownerKey="" ownerTag="" tag="yellow-green">
                <ospfIfP authKeyId="1" authType="none" descr="" name="">
                    <ospfRsIfPol tnOspfIfPolName=""/>
                </ospfIfP>
                <l3extRsNdIfPol tnNdIfPolName=""/>
                <l3extRsPathL3OutAtt addr="10.11.12.10/24" descr="" encap="unknown" ifInstT="l3-port" 
llAddr="::" mac="00:22:BD:F8:19:FF" mtu="1500" tDn="topology/pod-1/paths-101/pathep-[eth1/17]" targetDscp="unspecified"/>
            </l3extLIfP>
        </l3extLNodeP>
        <l3extRsEctx tnFvCtxName="PVN1"/>
        <l3extInstP descr="" matchT="AtleastOne" name="InstP1" prio="unspecified" targetDscp="unspecified">
            <fvRsCustQosPol tnQosCustomPolName=""/>
            <l3extSubnet aggregate="" descr="" ip="192.168.1.0/24" name="" scope=""/>
        </l3extInstP>
        <ospfExtP areaCost="1" areaCtrl="redistribute,summary" areaId="0.0.0.1" areaType="nssa" descr=""/>
        <rtctrlProfile descr="" name="default-export" ownerKey="" ownerTag="">
            <rtctrlCtxP descr="" name="routecontrolpvtnw" order="3">
                <rtctrlScope descr="" name="">
                    <rtctrlRsScopeToAttrP tnRtctrlAttrPName="actionruleprofile2"/>
                </rtctrlScope>
            </rtctrlCtxP>
        </rtctrlProfile>
    </l3extOut>