Demo: Interface Profiles

Create Leaf Interface Profile

Demo: Switch Profiles

Create a Leaf Profile

*Skip Step 2 (Associations for now), click Finish.


This is for VPC...

Demo: Interface Policies

Create Link Level Policy:

Create CDP Interface Policy

Create LLDP Interface Policy

Create Port Channel Policy

MCP Interface Policy

Demo: OOB Mgmt Policies

Tenant > mgmt

Node Management Address > Create Node Management Address

IP Address Pool has also been automatically created.

When you go up to Fabric > Inventory > Pod 1 >  Leaf (Node-101) > Interfaces  > Management Interfaces , you should see the given OOB IP address.

Demo: Creating Bridge Domain and Context

Tenants > Networking > dnd BD

Create a subnet.

 Creating 3 subnets...

Demo: Creating a Tenant

Topology

Tenants > Add

By default you have Common / Infra / Mgmt

Create Tenant Brisbane

Create Tenant Sydney

Demo: Fabric Discover Process

Credits to Mr. Lunde.


Fabric > Fabric Membership

Here, the process of LLDP, COOP (Council of Oracle Protocol) takes place...

ACI: Configuring a SPAN Session

(This is from ACI Built in Help)

This procedure shows how to configure a SPAN policy to forward replicated source packets to a remote traffic analyzer.

1. In the menu bar, click Tenants.
2. In the submenu bar, click the tenant that contains the source endpoint.
3. In the Navigation pane, expand the tenant, expand Troubleshooting Policies, and expand SPAN.
4. Under SPAN, right-click SPAN Destination Groups and choose Create SPAN Destination Group.
   The Create SPAN Destination Group dialog appears.
5. Enter the appropriate values in the required fields of the Create SPAN Destination Group dialog box then click OK and Submit.
   Note:

   For a description of a field, click the information icon (i) at the top-right corner of the dialog box to display the help file.
6. Under SPAN, right-click SPAN Source Groups and choose Create SPAN Source Group.
   The Create SPAN Source Group dialog appears.
7. Enter the appropriate values in the required fields of the Create SPAN Source Group dialog box then click OK and Submit.
   Note:

   For a description of a field, click the information icon (i) at the top-right corner of the dialog box to display the help file.

Using a traffic analyzer at the SPAN destination, you can observe the data packets from the SPAN source EPG to verify the packet format, addresses, protocols, and other information.

ACI: Troubleshooting Endpoint Connectivity

(This is from ACI Built in Help)

1. Inspect the operational status of each endpoint.
   The operational status will reveal any fault or misconfiguration of the endpoints. See

   Inspecting the Endpoint Status .
2. Inspect the status of the tunnel interface.
   The operational status will reveal any fault or misconfiguration of the tunnel. See Inspecting the Tunnel Interface Status.
3. Perform a traceroute between the endpoint groups (EPGs).
   A traceroute will reveal any problems with intermediate nodes, such as spine nodes, between the endpoints. See Performing a Traceroute Between Endpoints.
4. Configure an atomic counter on an endpoint.
   The atomic counter will confirm whether the source endpoint is transmitting packets or the destination endpoint is receiving packets, and whether the number of packets received equals the number of packets sent. See Configuring Atomic Counters.
5. Inspect the contracts under each EPG.
   Inspect the contracts under each EPG to make sure they allow the traffic that should flow between the EPGs. As a test, you can temporarily open the contracts to allow unrestricted traffic.
6. Configure a SPAN policy to forward source packets to a monitoring node.
   A packet analyzer on the monitoring node will reveal any packet issues such as an incorrect address or protocol. See Configuring a SPAN Session.

• Inspecting the Endpoint Status
• Inspecting the Tunnel Interface Status
• Performing a Traceroute Between Endpoints

ACI: Configuring Atomic Counters

(This is from ACI Built in Help)

1. In the menu bar, click Tenants.
2. In the submenu bar, click the desired tenant.
3. In the Navigation pane, expand the tenant and expand Troubleshoot Policies.
4. Under Troubleshoot Policies, expand Atomic Counter Policy and choose a traffic topology.
   You can measure traffic between a combination of endpoints, endpoint groups, external interfaces, and IP addresses.
5. Right-click the desired topology and choose Add topology Policy to open an Add Policy dialog box.
6. In the Add Policy dialog box, perform the following actions:
   1. In the Name field, enter a name for the policy.
   2. choose or enter the identifying information for the traffic source.
      The required identifying information differs depending on the type of source (endpoint, endpoint group, external interface, or IP address).
   3. choose or enter the identifying information for the traffic destination.
   4. Optional: (Optional) In the Filters table, click the + icon to specify filtering of the traffic to be counted.
      In the resulting Create Atomic Counter Filter dialog box, you can specify filtering by the IP protocol number (TCP=6, for example) and by source and destination IP port numbers.
   5. Click Submit to save the atomic counter policy.
7. In the Navigation pane, under the selected topology, choose the new atomic counter policy.
   The policy configuration is displayed in the Work pane.
8. In the Work pane, click the Operational tab and click the Traffic subtab to view the atomic counter statistics.

ACI: Monitoring EPG Statistics

(This is from ACI Built in Help)

For detailed information about monitoring policies, see Configuring Monitoring Policies.

To collect and export statistics on one or all endpoint groups (EPGs), follow these steps:

1. Create a monitoring policy.
   See Creating a Monitoring Policy.
   1. In the monitoring policy, configure a statistics collection policy to determine what gets collected.
      See Configuring a Statistics Collection Policy.
   2. In the monitoring policy, configure a statistics export policy to determine when and to where statistics are sent.
      See Configuring a Statistics Export Policy.
2. Apply the monitoring policy to a single EPG in an application profile or to all EPGs in an application profile.
   See Applying a Monitoring Policy to EPGs.

ACI: Applying a Service Graph Template to Endpoint Groups Using the GUI

(This is from ACI Built in Help)

You must have created the following things:

• Application endpoint groups
• A service graph template

The following procedure explains how to apply a service graph template to endpoint groups:

1. On the menu bar, choose Tenants > All Tenants.
2. In the Work pane, double click the tenant's name.
3. In the Navigation pane, choose Tenant tenant_name > L4-L7 Services > L4-L7 Service Graph Templates > template_name.
4. In the Work pane, choose Actions > Apply L4-L7 Service Graph Template.
   You will be associating a Layer 4 to Layer 7 service graph template to your consumer and provider endpoint groups.
5. In the Apply L4-L7 Service Graph Template To EPGs dialog, in the EPG Information section, complete the following fields:

   Name	Description
   Consumer EPG/External Network drop-down list	Choose a consumer endpoint group.
   Provider EPG/External Network drop-down list	Choose a provider endpoint group.

6. In the Contract Information section, complete the following fields:

   Name	Description
   Contract radio buttons	Choose to create a contract or choose an existing contract.
   Contract Name field	(Only for creating a contract) Enter the name of the contract.
   No Filter (Allow All Traffic) check box	(Only for creating a contract) Put a check in the box to allow all traffic, or remove the check from the box to filter traffic.
   Filter Entries	(Only for filtering traffic) Click + and enter the filter information, then click Update.
   Existing Contract With Subjects drop-down list	(Only for choosing an existing contract) Choose an existing contract.

7. Click Next.
8. In the Graph Template drop-down list, choose a service graph template.
9. (Only for a Layer 4 to Layer 7 device) In the L4L7_device_name Information section for each Layer 4 to Layer 7 device, complete the following fields:

   Name	Description
   Router Config drop-down list	(Only if you chose Route Peering for the consumer type or provider type) The router configuration to use for policy-based redirect.

   Consumer Connector

   Name	Description
   Type radio buttons	The connector type. The type can be: General Route Peering—Enables route peering on the device.
   BD drop-down list	(Only if you chose General for the type) Choose or create a bridge domain for the consumer connector. The bridge domain is used for the data path traffic.
   L3 Ext Network drop-down list	(Only if you chose Route Peering for the type) Choose a Layer 3 external (outside) network for the consumer connector.
   Cluster Interface drop-down list	Choose or create an interface for the consumer connector.

   Provider Connector

   Name	Description
   Type radio buttons	The connector type. The type can be: General Route Peering—Enables route peering on the device.
   BD drop-down list	(Only if you chose General for the type) Choose or create a bridge domain for the provider connector. The bridge domain is used for the data path traffic.
   L3 Ext Network drop-down list	(Only if you chose Route Peering for the type) Choose a Layer 3 external (outside) network for the provider connector.
   Cluster Interface drop-down list	Choose or create an interface for the provider connector.

   The Application Policy Infrastructure Controller (APIC) uses the chosen bridge domains for data path traffic between function nodes as required by the chosen service graph template. Refer to the online help for the service graph templates to learn more about how this bridge domain is used.
10. (Only for a copy device) In the copy_device_name Information section for each copy device, in the Cluster Interface drop-down list, choose the cluster interface that you defined for that copy device.
11. (Only for a managed Layer 4 to Layer 7 device) Click Next.
12. (Only for a managed Layer 4 to Layer 7 device) In the Parameters screen, in the Required Parameters tab, enter the names and values, as appropriate, for all of the required parameters.
13. Click Finish.
    You now have an active service graph template. The APIC populates the Layer 4 to Layer 7 parameters based on the chosen function profile and colors the mandatory parameters in green if they are configured correctly.

ACI: Creating an Application Profile Using the GUI

(This is from ACI Built in Help)

1. On the menu bar, choose TENANTS. In the Navigation pane, expand the tenant, right-click Application Profiles, and click Create Application Profile.
2. In the Create Application Profile dialog box, in the Name field, add the application profile name (OnlineStore).

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.