ACI Fundamentals

Many data center teams still configure switches one device at a time: copying and pasting text files, editing IP addresses and hostnames by hand, and hoping none of 300 devices gets missed. Cisco ACI replaces that approach with policy-driven, centrally managed fabrics. Without a shared foundation, though, teams can stall during adoption or learn by experimenting on production.

Role fit: This course suits network administrators with at least a year of networking experience. It also works for experienced admins who are moving to ACI or preparing for deeper data center study. Team Leads can use it as a common baseline before engineers take on design or troubleshooting work.

Time investment: Plan for about 19 hours per learner across 24 skills of roughly 45–50 minutes each. That makes it practical to complete over several weeks alongside regular duties.

Risk and change management: The instructor recommends the ACI Simulator so learners can run fabric discovery and configuration changes without touching production. Learners practice the same tasks three ways: GUI, CLI, and REST API through Postman. This helps teams move gradually from manual workflows toward repeatable, API-driven policy.

Reinforcement: Built-in lab challenges, a capstone diagramming and configuration challenge, and quiz-style reviews help Training Managers confirm skills before learners apply them in production.

How this training helps your team succeed in the real world

Many data center teams still configure switches one device at a time, copying and pasting text-file "scripts" and hand-editing IP addresses and hostnames. As the course points out, that is how a duplicated IP or the 299th of 300 devices gets missed. This course shows IT Practitioners how Cisco ACI replaces that approach with centralized, policy-driven management through the APIC. Every lab is done in the ACI Simulator, so no one has to learn on production.

• Fewer configuration errors: Your team practices building tenants, VRFs, bridge domains, EPGs, and contracts in the GUI, the CLI, and the API. They can then apply repeatable policy across the fabric and stop touching each switch individually.
• Faster, repeatable changes through automation: Engineers make REST API calls with Postman and an ACI collection. They use the object model and distinguished names to build their own calls for policy they deploy often.
• Smoother integration with existing networks: Team members configure L3Outs and L2 external connectivity, including MST and BPDU handling. This lets a new fabric connect to the network core and campus without surprise outages.
• Better-informed design and resilience planning: Engineers learn how APIC clustering and data sharding behave when an APIC fails. Design challenges, such as extending ACI to a backup data center, prepare them for informed conversations with Cisco SEs and internal stakeholders.

The course ends with a capstone that wipes the configuration and rebuilds the fabric from scratch. Team Leads get clear evidence that each engineer can bring a fabric online end to end.

Knowledge

• Why ACI matters for on-premises data centers, and how its policy-driven model reduces the human error of device-by-device, copy-and-paste configuration
• How the Nexus 9000 spine-leaf architecture, VXLAN forwarding, and ACI fabric forwarding fit together
• How APIC clusters use data sharding to stay resilient when an individual APIC fails
• How the ACI physical and logical models relate: tenants, VRFs, bridge domains, EPGs, and unidirectional contracts, including where Layer 2 versus Layer 3 happens
• How bridge domain options shape address learning, ARP flooding, and unknown unicast forwarding
• How the ACI object model (classes, objects, distinguished names) underpins API calls

Ability

• Prepare an APIC initialization checklist and bring a basic ACI fabric online through fabric discovery, using the ACI simulator to avoid production risk
• Perform the same configuration (tenant, VRF, bridge domain) through the GUI, CLI, and API
• Configure endpoint groups, application network profiles, and contracts to control traffic flow between workloads
• Connect the fabric to external Layer 3 and Layer 2 networks, including STP/MST policy considerations
• Build and modify API calls in Postman using an ACI collection and variables to deploy repeatable policy
• Rebuild a full ACI configuration from scratch in a capstone challenge, from fabric initialization through external connectivity