APIC Navigation

The APIC infrastructure configuration has already been configured for you. This section will show you the necessary steps to follow in order to configure the APIC.

Step 1 - Connect to APIC GUI via web

You can login into the interface with the credentials


Make no changes to the APIC controller via the GUI. The lab continues and having the infrastructure operational is key to completing.

Create Physical Domain

The physical domain in ACI is utilized to define a pool of resources that ACI can utilize to communicate to an external domain. The domains are:

Create VLAN Pool

A pool represents a range of traffic encapsulation identifiers (for example, VLAN IDs, VNIDs, and multicast addresses). A pool is a shared resource and can be consumed by multiple domains such as VMM and Layer 4 to Layer 7 services. A leaf switch does not support overlapping VLAN pools. You must not associate different overlapping VLAN pools with the VMM domain. The two types of VLAN-based pools are as follows:

Interface Policy Group

Fabric policies govern the operation of internal fabric interfaces and enable the configuration of various functions, protocols, and interfaces that connect spine and leaf switches. Administrators who have fabric administrator privileges can create new fabric policies according to their requirements. The APIC enables administrators to select the pods, switches, and interfaces to which they will apply fabric policies. The following figure provides an overview of the fabric policy model.

Fabric policies are grouped into the following categories:

Interface Policies - Leaf Profiles

Interface Policies - Leaf Policy Groups

Switch Policies - Profiles - Leaf Profiles

Attach Entity Profile

The ACI fabric provides multiple attachment points that connect through leaf ports to various external entities such as baremetal servers, hypervisors, Layer 2 switches (for example, the Cisco UCS fabric interconnect), or Layer 3 routers (for example Cisco Nexus 7000 Series switches). These attachment points can be physical ports, port channels, or a virtual port channel (vPC) on leaf switches, as shown in the figure below.

An Attachable Entitiy Profile (AEP) represents a group of external entities with similar infrastructure policy requirements. The infrastructure policies consist of physical interface policies, such as Cisco Discovery Protocol (CDP), Link Layer Discovery Protocol (LLDP), Maximum Transmission Unit (MTU), or Link Aggregation Control Protocol (LACP). An AEP is required to deploy VLAN pools on leaf switches. Encapsulation pools (and associated VLAN) are reuseable across leaf switches. An AEP implicitly provides the scope of the VLAN pool to the physical infrastructure.

© Copyright Cisco Systems 2017