ACI: Configuring a Layer 3 Outside for Tenant Networks Using the GUI

(This is from ACI Built in Help)

• The tenant, VRF, and bridge domain are created.
• The external routed domain is created and associated to the interface.

The external routed network configured in the example can also be extended to support IPv4. Both IPv4 and IPv6 routes can be advertised to and learned from the external routed network.

1. On the menu bar, click TENANTS.
2. In the Navigation pane, expand the Tenant_name > Networking > External Routed Networks and perform the following actions:
   1. Right-click External Routed Networks and click Create Routed Outside.
   2. In the Create Routed Outside dialog box, in the Name field, enter a name for the routed outside.
   3. In the area with the routing protocol check boxes, check the desired protocol.
      The options available are BGP, OSPF, EIGRP. Later in the steps, this will make available, the route summarization policy in the Create External Network dialog box.
   4. In the VRF field, from the drop-down list, choose the appropriate VRF.
   5. From the External Routed Domain drop-down list, choose the appropriate external routed domain.
   6. Check the check box for the desired protocol.
      Depending on the protocol you choose, the properties that must be set.
   7. Expand Nodes and Interfaces Protocol Profiles.
   8. In the Create Node Profile dialog box, in the Name field, enter a name.
   9. Expand Nodes.
   10. In the Select Node dialog box, from the Node ID drop-down menu, choose the appropriate node ID.
   11. In the Router ID field, enter the router ID.
   12. If the Use Router ID as Loopback Address check box is checked, the Router ID is used as the Loopback Address, otherwise, expand Loopback Addresses, enter an IP address, and click Update.
       Note:
       

       In the Loopback Addresses fields, create an IPv4 and/or IPv6 loopback as desired.
   13. Click OK.
3. Expand Interface Profiles, and perform the following actions:
   1. In the Create Interface Profile dialog box, in the Name field, enter a name for the profile.
   2. Expand Routed Interfaces.
   3. In the Select Routed Interface dialog box, from the Path drop-down list, choose the interface path.
   4. In the IP Address field, enter the IP address.
      Note:
      

      To configure IPv6, you must enter the link-local address in the Link-local Address field in the dialog box.
   5. Click OK.
      The routed interface details are displayed in the Create Interface Profile dialog box.
   6. Click OK.
4. In the Create Node Profile dialog box, click OK.
5. In the Create Routed Outside dialog box, click Next.
6. In the External EPG Networks area, expand External EPG Networks.
7. In the Create External Network dialog box, in the Name field, enter a name for the external network.
8. Expand Subnet.
9. In the Create External Network dialog box, perform the following actions:
   1. Expand Subnet to add another subnet.
   2. In the Create Subnet dialog box, in the IP Address field, enter an IP address.
   3. In the Scope field, check the appropriate check boxes. Click OK.
      Note:
      

      • The import control policy is not enabled by default but can be enabled by the user. The import control policy is supported for BGP and OSPF, but not for EIGRP. If the user enables the import control policy for an unsupported protocol, it will be automatically ignored.
      • The export control policy is supported for BGP, EIGRP, and OSPF.
      • Route aggregation is also supported and the user can optionally choose route aggregation in the desired export or import direction. This feature is available for 0.0.0.0/0 and for the security option. If the import control policy is not enabled, an example of the check boxes to check are Export Subnet, Shared Security Import Subnet, and Aggregate Export. The user must choose route map and security options.
      • If an explicit route control policy is configured for a Layer 3 outside, then only specific Layer 3 outside policies are supported. Explicit route control policies are not supported for aggregate routes.
   4. Optional: In the Route Summarization Policy field, from the drop-down list, choose an existing route summarization policy or create a new one as desired and you must check the check box for Export Route Control Subnet.
   5. In the Create External Network dialog box, click OK.
10. Optional: In the Create Subnet dialog box, perform the following actions:
    1. In the IP Address field, enter the IP address and subnet.
    2. In the Scope field, check the appropriate check box. Click OK.
11. In the Create Routed Outside dialog box, click Finish.
12. In the Navigation pane, under Tenant_name > Networking > Bridge Domains and choose the Bridge_Domain_name.
13. In the Navigation pane, choose the BD you created.
    Note:
    

    If the L3 Out is static, you are not required to choose any settings.
    1. In the Work pane, choose the L3 Configurations tab.
    2. In the Associated L3 Outs field, associate the desired L3 Out and click Update.
    3. In the L3 Out for Route Profile field, choose the desired L3 Out and click Submit.
14. Note:
    

    To set attributes for BGP, OSPF, or EIGRP communication for all routes we receive, create default-import route control profile, create the appropriate set actions and no match actions.
    In the Navigation pane, click Route Maps/Profiles, right-click Create Route Map, and in the Create Route Map dialog box, perform the following actions:
    1. In the Name field, enter a name.
    2. In the Type field, you must click Match Routing Policy Only. Click Submit.
15. Optional: To enable additional communities using the BGP protocol, right-click Set Rules for RouteMaps, click Create Set Rules for a Route Map.
16. Optional: In the Create Set Rules for a Route Map dialog box,click the Add Communities field and follow the steps to assign multiple BGP communities per route prefix if desired.