As mentioned in the last post, let’s make the first step happen: Making an online fabric!
Turn on the UCS server which you have chosen for the APIC role!
It’s presumed that we start with CIMC utility to setup the APIC. As it is with all other Cisco CLIed products, we get a simple wizardish script as below:
Cluster configuration ... Enter the fabric name [ACI Fabric1 #1]: ACI-FABRIC Enter the number of controllers in the fabric (1-16) : 1 Enter the controller ID (1-3) : 1 Enter the controller name [apic2]: APIC1 Enter address pool for TEP addresses [10.0.0.0/16]: 172.16.0.0/12 Enter the VLAN ID for infra network (1-4094): 100 Enter address pool for BD multicast addresses (GIPO) [220.127.116.11/15]: Out-of-band management configuration ... Enter the IP address for out-of-band management: 172.17.1.2/24 Enter the IP address of the default gateway [None]: 172.17.1.1 Enter the interface speed/duplex mode [auto]: Administrator user configuration... Enable strong passwords? [Y] Enter the password for admin:
I’m sure you have the Cisco ACI Fundamentals open, but let me take a look into some of the parameters which was asked:
- TEP Address pool: Every leaf and spine node in the fabric, will be automatically assigned at least one Tunnel End Point address.
- Multicast Address pool: will be used for multicast traffic through the network
- VLAN ID: is used for communication inside the fabric infrastructure network
After a while, the APIC would be up and accessible via the web management interface using the OOB IP address. Now, we have to discover the physical switching nodes.
I never like to go through GUI, so I just name the steps and mention the more important parts.
- From the GUI go to: Fabric tab >> Inventory sub-menu
- Click on Fabric Membership (left)
- Hence your APIC is at least connected to one Nexus switch, you should see a single leaf node. LLDP is the magic which makes this happen. But we have not yet registered the switch, so there is no ID, name and IP listed.
- Double click on each field and simply assign a node ID. After a short break, you will see an IP address for the node. Notice that the IP is assigned from the range we specified for TEP pool during the wizard.
- The switch is registered!
Now, we have officially a leaf node, the rest of network will be discovered and you can see the spine nodes appearing on the Fabric Membership page. As you guess, we have to register these nodes the same as the leaf switch. As the result, the remaining switches will pop up and available for membership.
Once all the switching topology –including other leaf nodes– is discovered, we can initialise the same setup procedure for other APICs and form an APIC Cluster. Keep in mind that we have to use different controller ID, management IP, etc.
By the time all APICs are running, the fabric is almost ready and we can see a graphical topology via Fabric | Inventory section in the APIC GUI.
One more thing to do would be to configure the switching nodes with management IP so they can be managed directly. This is done inside Tenants tab and then the Mgmt tenant, where on the left there is Node Management Addresses which let us to configure management IPs for every single fabric node. The next step is to configure at least an Out-of-Band Contract under Security Policies menu, in order to permit traffic into OOB management interfaces. Finally, under Node Management EPGs, we should assign the OOB contract to our OOB EPG.