Where to Get a Cisco ACI Lab: Sandbox, Simulator or Hardware
You can get a Cisco ACI lab environment in three ways: Cisco's own sandboxes and simulator, a reservable lab on physical ACI hardware such as CloudMyLab's ACI Learning Lab, or a fabric you buy and rack yourself. The sandboxes are free and quick to reach but share or simulate the switches. A hardware lab gives you real Nexus 9000 leaves and spines, an APIC and a server for VMM integration. Once you pick one, the 14 ACI exercises below run on any of them, with the exceptions noted.
Need ACI on real hardware for a certification, a POC or an integration test? CloudMyLab's Cisco ACI Learning Lab gives you a physical ACI fabric with APIC, Nexus 9000 switches and a UCS server, reserved in 6-day blocks. Contact us to check availability.
Table of contents
- Where can you get a Cisco ACI lab environment?
- Simulated switches or physical switches?
- What the CloudMyLab ACI lab includes
- ACI practice exercises: fabric, policy and VMM
- Advanced ACI exercises
- Next steps
Where can you get a Cisco ACI lab environment?
Start with what you need to prove. Learning the APIC GUI and the policy model works on a simulator. Testing traffic between endpoints, a VMM integration with real hosts or a multipod design needs physical switches.
|
Option |
What you get |
Access |
Best for |
|---|---|---|---|
|
DevNet Always-On ACI Simulator |
A shared APIC on a simulated fabric |
Any time, shared with other users |
Trying the APIC GUI and API calls |
|
DevNet reservable ACI Simulator |
Your own simulated fabric for a set period |
Reserve up to 5 consecutive days with a free Cisco account |
API and automation work you do not want to share |
|
Cisco ACI Simulator on your own server |
APIC software with simulated leaf and spine switches |
Whenever your server runs |
Learning policy and the object model on your own schedule |
|
CloudMyLab ACI Learning Lab |
Physical Nexus 9000 spines and leaves, APIC, UCS server for VMM integration; a multipod and multi-site version and a simulated multi-site lab |
Reserved through our scheduler in 6-day blocks |
Certification practice, ACI proofs of concept and integration testing |
|
Your own hardware |
A fabric you buy and rack |
Always |
Teams that already own spare Nexus 9000 gear |
Cisco's ACI sandbox page describes the Always-On sandbox as a "shared ACI server instance" you can use "at any time or day", and the reservable ACI Simulator sandbox as one you "reserve up to 5 consecutive days". Because the Always-On fabric is shared, expect other users' tenants and changes to be there when you log in.
CloudMyLab is an infrastructure provider. The ACI Learning Lab gives you the hardware, the licensing and sample labs to start from, and you choose what to build on it. CloudMyLab does not run ACI courses; if you want an instructor, we can connect you with our training partners, Patriot Solutions and Training World 360.
Simulated switches or physical switches?
Cisco's ACI Simulator runs, in Cisco's words, "real, fully-featured Cisco APIC software" with simulated leaf and spine switches. The same ACI Simulator release notes are direct about the limit: "you cannot validate a data path." The physical simulator appliance is no longer sold; the simulator ships as a VM, so check that your Cisco account is entitled to download it.
That is the line that decides most choices. If your goal is the DCACI exam topics, the APIC GUI or the REST API, a simulator gets you far. If you need to see endpoints learned on a leaf, test a contract with real traffic, connect an external L3 network or run a VMM integration against a live vCenter, use a fabric with physical switches.
For background on the architecture itself, see our guide to Cisco ACI and these ACI architecture diagrams.
What the CloudMyLab ACI lab includes
The ACI Learning Lab comes in three versions: a standard lab on Gen 1 hardware, a multipod and multi-site lab on Gen 2 hardware, and a simulated multi-site lab. Every version is reserved through our scheduler in blocks of 6 days, Monday to Saturday, with access 24 hours a day.

|
|
ACI V2 standard lab |
ACI multipod and multi-site lab |
|---|---|---|
|
ACI version |
5.x |
5.x |
|
Spine switches |
1 x N9K-9364C |
2 x N9K-9364C |
|
Leaf switches |
2 x N9K-93180 or 93120 |
4 x N9K-93180 or 93120 |
|
APIC controllers |
1 |
2 |
|
UCS server for VMM integration |
1 |
2 |
|
L2/L3 switches |
1 |
2 |
|
IPN switches |
None |
2 x Cisco Nexus |
|
Access |
Jump box and AnyConnect VPN for 2 users |
Jump box and AnyConnect VPN for 2 users |
The only fixed parts of the setup are the IP schema and the underlay subnet. You can change the rest, upload or create your own virtual machines and attach them through the UCS server. Sample labs and a getting-started guide in the knowledge base give you a starting point. Our support team keeps the lab infrastructure running; if you need help with an ACI design or integration, our Professional Services team can be engaged. If you need extra hardware beyond the lab, our proof of concept service or Lab as a Service builds a dedicated environment.
ACI practice exercises: fabric, policy and VMM
These exercises cover the core ACI topics, from fabric discovery to troubleshooting. On a simulator you can practise the configuration objects and the APIC GUI and API, but not anything that needs a data path or real switch hardware: traffic between endpoints, VMware and ASAv integrations with running VMs, NetFlow data, routing adjacencies on external connections, switch out-of-band addresses and hardware counters. The simulator release notes from Cisco list the unsupported features for each version, so check them before you rely on one. On a physical fabric you also need a VMM server and the images you are licensed to use.
Lab 1: Explore the Cisco ACI Fabric Inventory
Learning Objective: Become familiar with the Cisco APIC GUI, explore the ACI fabric inventory, and understand the critical role of Out-of-Band Management for secure and reliable network operations.
This initial lab introduces you to the Cisco Application Policy Infrastructure Controller (APIC) and the fundamental components of an ACI fabric. You will learn to log in to the APIC GUI, explore the fabric inventory, and configure essential initial settings like NTP and DNS. This lab also highlights the importance and configuration of Out-of-Band (OOB) Management, a crucial aspect for secure and resilient network administration.
Cisco APIC Controller Log-In and Fabric Discovery
- Connect to your lab's jump box.
- Log in as an admin with the password provided.
- Open a browser and navigate to the APIC GUI using the IP address provided.
- Review the fabric setup, including NTP and DNS configurations.
- Verify fabric discovery and confirm the fabric switches are registered.
- Configure NTP server settings. You will manually input or select NTP server addresses within the APIC GUI.
- Set up DNS server configurations. You will configure DNS server addresses, search domains, and potentially DNS client settings in the APIC.
- Define OOB management IP addresses for the fabric switches. You will assign dedicated IP addresses for out-of-band (OOB) management to the spine and leaf switches.
- Verify the settings and ensure proper connectivity. You will use tools within the APIC or your jump box to verify that the OOB management is configured correctly and reachable.
- Explore the Cisco APIC GUI and review the global configuration settings. You will navigate through different sections of the APIC GUI, examining global settings that apply to the entire fabric.
- Familiarize yourself with the dashboard and its components. You will examine the APIC dashboard, understanding the different widgets and information displayed, such as fabric health, faults, and inventory summaries.
Why out-of-band management matters: it gives you a management path that does not depend on the fabric data plane, so you can still reach the switches when a policy change breaks in-band connectivity.
Lab 2: Implement Cisco ACI Fabric and data plane
Learning Objective: Build the foundational data plane of the ACI fabric by configuring interface policies, vPCs, and switch profiles, establishing connectivity to hypervisors.
This lab focuses on implementing the data plane of the ACI fabric. You will configure interface policies for physical ports, create vPC (virtual PortChannel) configurations for redundancy, and define switch profiles to apply these configurations to the leaf switches. This lab sets the stage for connecting endpoints, such as hypervisors, to the ACI fabric and establishing basic network connectivity.
Configure Interface Policies
- Create interface policies for CDP, LLDP, and port channels. You will create policies to define how interfaces on the ACI switches will behave, specifically regarding protocols like Cisco Discovery Protocol (CDP), Link Layer Discovery Protocol (LLDP), and port channeling.
- Enable CDP, disable LLDP, and configure port channel policies. You will specifically enable CDP (a Cisco proprietary discovery protocol), disable LLDP (an open standard alternative – often disabled in favor of CDP in Cisco environments), and configure policies for link aggregation (port channels) to increase bandwidth and redundancy.
- Create a vPC interface policy group and bind interface policies to it. You will create a virtual PortChannel (vPC) interface policy group. vPC allows you to create a logical port channel that spans two physical switches (leaf switches in ACI). You will then bind the interface policies created in the previous step to this vPC policy group.
- Specify interface IDs and associate them with the interface policy group. You will create a leaf interface profile and specify the physical interfaces on the leaf switches that will participate in the vPC. You will then associate this interface profile with the vPC interface policy group you created earlier.
- Associate leaf switches with the leaf interface profile for your hypervisor. You will create switch profiles and associate specific leaf switches in your ACI fabric with the leaf interface profile you configured. In this context, you are preparing to connect a hypervisor (like VMware ESXi) to these leaf switches.
- Check the vPC status and ensure proper connectivity between leaves and the hypervisor. You will use APIC GUI or CLI tools to verify the status of the vPC you configured (e.g., peer status, consistency checks). You will also check that the vPC toward the connected hypervisor is up; traffic tests come once EPGs and the VMM domain are in place in Labs 3 and 4.
Physical connectivity: out-of-band management needs its own cabling, separate from the data traffic, and VMM integration depends on how the servers connect to the leaf switches. Check both before you build multipod or multi-site designs on top.
Lab 3: Configure Cisco ACI Logical Constructs
Learning Objective: Master the configuration of key ACI logical constructs including Tenants, VRFs, Bridge Domains, Application Profiles, EPGs, and Contracts to define application-centric network segmentation and policies.
This lab focuses on configuring the fundamental logical building blocks of Cisco ACI. You will learn to create and manage Tenants for network segmentation, Virtual Routing and Forwarding (VRFs) for Layer 3 isolation, Bridge Domains for Layer 2 connectivity, Application Profiles to organize application components, Endpoint Groups (EPGs) to group endpoints, and Contracts to define policy-based communication between EPGs. This lab is crucial for understanding ACI's application-centric approach and how to define network policies using logical constructs.
Create a Tenant and VRF
- Define a tenant and VRF in the APIC GUI. You will create a Tenant, the highest level of logical separation in ACI, and a Virtual Routing and Forwarding (VRF) instance within that tenant. Visualizing and articulating the tenants’ structure enables practitioners to configure contracts, application profile definitions, and subnet policies. This lets relevant endpoints communicate while security controls stay in place across network boundaries.
- Configure a bridge domain and associate it with the VRF. You will create a Bridge Domain, a Layer 2 forwarding construct similar to a VLAN but with more advanced capabilities, and associate it with the VRF created in the previous step.
- Define subnets within the bridge domain. You will define IP subnets associated with the bridge domain.
- Set up an application profile and create EPGs for different application tiers. You will create an Application Profile, which represents a collection of related application components. Within this profile, you will create Endpoint Groups (EPGs), which logically group endpoints (like VMs or servers) based on application function (e.g., web tier, application tier, database tier).
- Define filters for ICMP, SSH, HTTP, and FTP traffic. You will create Filters, which are access control lists (ACLs) that define specific types of network traffic (e.g., ICMP, SSH, HTTP, FTP based on port numbers and protocols).
- Create contracts and associate filters with them. You will create Contracts, which are policy constructs that define how EPGs are allowed to communicate with each other. You will associate the filters you just created with these contracts.
- Assign contracts to EPGs to control traffic permissions between them. You will "consume" and "provide" the contracts you created by associating them with the EPGs. For example, you might configure the 'application tier' EPG to provide the 'HTTP contract' and the 'web tier' EPG to consume it. The consumer starts the connection, so this allows HTTP from the web tier to the application tier, and the contract permits the return traffic.
Lab 4: Integrate Cisco ACI with VMware Using Native DVS
Learning Objective: Master the integration of Cisco ACI with VMware vSphere using the native Distributed Virtual Switch (DVS) integration, enabling unified management of physical and virtual networks.
This lab focuses on integrating your Cisco ACI fabric with a VMware vSphere environment using the native Distributed Virtual Switch (DVS) integration. You will learn to configure the necessary components in both ACI and vCenter to establish seamless communication and policy synchronization between the physical and virtual network layers. This lab demonstrates how ACI extends its application-centric policy model into virtualized environments, enabling consistent management and automation across your entire infrastructure.
Configure VMM Domain Integration
- Define VMware vCenter as a VM manager on the Cisco APIC. You will configure a VMM Domain in the APIC, specifying VMware vCenter as the Virtual Machine Manager.
- Configure a VLAN pool and vCenter domain. You will create a VLAN pool to be used for communication with the VMware environment and associate it with the vCenter domain.
- Ensure the APIC has discovered the vCenter and its inventory. You will check the APIC GUI to confirm that the APIC has successfully connected to the vCenter and has discovered the vCenter inventory (like datacenters, clusters, hosts, VMs).
- Create an Attachable Access Entity Profile (AAEP) for the ESXi host connections. You will create an AAEP, the policy construct that ties domains, and with them their VLAN pools, to the leaf interfaces where the ESXi hosts connect. You will configure the AAEP to selectively allow VLAN traffic relevant to your VMware environment.
- Add the hypervisor and its uplinks to the DVS in the vCenter. Through the vCenter interface (or potentially via APIC integration), you will add an ESXi host and its physical uplinks (network adapters) to the Distributed Virtual Switch (DVS) managed by ACI.
- Link EPGs with the VMM domain to provision DVS port groups. You will associate the Endpoint Group (EPGs) you created in Lab 3 with the VMM Domain. This action will automatically provision Distributed Virtual Port Groups (DVPGs) on the VMware DVS, linked to the ACI EPGs.
- Verify connectivity among VMs within the same EPG. You will deploy or assign virtual machines to a single DVS port group (which corresponds to an ACI EPG). You will then test connectivity (e.g., ping) between VMs within the same EPG to verify that intra-EPG communication is working as expected (and is allowed by default in ACI).
- Test connectivity between VMs in different EPGs based on configured contracts. You will deploy or assign VMs to different DVS port groups (each linked to a different ACI EPG). You will then test connectivity (e.g., ping) between VMs in different EPGs. You will observe whether communication is allowed or denied based on the contracts you configured in Lab 3.
Advanced ACI exercises
Lab 5: Integrate Cisco ASAv with Cisco APIC
Learning Objective: Master the deployment and configuration of service graphs for integrating L4-L7 services like firewalls and load balancers into ACI.
This lab focuses on implementing L4-L7 Service Graphs. You will learn how to integrate virtualized network services, specifically the Cisco Adaptive Security Virtual Appliance (ASAv) firewall, into the ACI fabric using service graphs. You will configure traffic redirection through the ASAv for security inspection, enabling advanced service chaining and policy enforcement.
Lab 6: Configure Role-Based Access Control
Learning Objective: Understand and implement RBAC in ACI to manage user access and administrative permissions for enhanced security and operational control.
This lab covers Role-Based Access Control (RBAC) in ACI. You will learn how to implement RBAC using default roles and how to create custom security domains to delegate administrative privileges and control access to different parts of the ACI fabric based on user roles and responsibilities.
Lab 7: Explore Cisco ACI Monitoring and NetFlow
Learning Objective: Gain proficiency in utilizing Cisco ACI monitoring tools and NetFlow capabilities for network visibility, performance management, and troubleshooting.
This lab focuses on ACI Monitoring and NetFlow. You will explore the built-in monitoring capabilities of ACI, learn how to use tools to monitor fabric health and performance, and configure NetFlow export to collect detailed traffic flow data for analysis and troubleshooting.
Lab 8: Enable Connectivity to External L3 Networks
Learning Objective: Master the configuration of external Layer 3 connectivity in ACI to integrate the fabric with existing routing infrastructure.
This lab covers External Layer 3 Connectivity. You will learn how to connect the ACI fabric to external Layer 3 networks (like the internet or corporate WAN) using protocols like OSPF (Open Shortest Path First). You will configure policies to advertise internal ACI networks to the external world and learn how to control routing and traffic flow.
Lab 9: Enable Connectivity to External L2 Networks
Learning Objective: Understand and configure external Layer 2 connectivity in ACI to seamlessly integrate with existing VLAN-based networks.
This lab focuses on External Layer 2 Connectivity. You will learn how to extend ACI Endpoint Groups (EPGs) and Bridge Domains to external Layer 2 networks. This allows you to integrate legacy VLAN-based networks or physical devices into the ACI fabric at Layer 2, providing a bridge between traditional and ACI-managed environments.
Lab 10: Configure Cisco APIC Using REST API
Learning Objective: Develop skills in using the APIC REST API for programmatic management and automation of ACI fabric configurations.
This lab introduces REST API Automation for APIC. You will learn how to use the RESTful API provided by the APIC to manage and configure the ACI fabric programmatically. You will practice sending API calls to retrieve information, create configurations, and automate tasks, moving towards infrastructure-as-code principles.
Lab 11: Configure Cisco APIC Using Python Scripts
Learning Objective: Learn to automate ACI fabric management using Python scripting and the APIC REST API, improving operational efficiency and consistency.
This lab builds on Lab 10 by focusing on Python Scripting for ACI Automation. You will use Python libraries to interact with the APIC REST API, write scripts to automate repetitive ACI tasks, and learn best practices for using Python to manage network infrastructure.
Lab 12: Explore Cisco ACI App Center and the ACI Optimizer
Learning Objective: Discover the ACI App Center for extending ACI functionality and learn how to use the ACI Optimizer for capacity planning.
This lab explores ACI App Center and Optimization Tools. You will discover the ACI App Center, a platform for deploying and managing applications and integrations within the ACI fabric. You will also explore the ACI Optimizer, which checks a planned configuration against the fabric's scale limits. App Center applications run on the APIC in the 5.x release the CloudMyLab lab uses; check Cisco's release notes before you plan this exercise on a newer release.
Lab 13: Explore Cisco ACI Troubleshooting Tools
Learning Objective: Gain proficiency in using ACI's troubleshooting tools and techniques to diagnose and resolve common network issues within an ACI fabric.
This lab focuses on ACI Troubleshooting Techniques. You will learn to utilize various command-line interface (CLI) tools and diagnostic features built into ACI to troubleshoot common network issues within the fabric. You will practice diagnosing connectivity problems, policy misconfigurations, and hardware faults using ACI's built-in tools.
Lab 14: Export TechSupport
Learning Objective: Understand how to generate and export ACI TechSupport files for advanced troubleshooting and support purposes.
You will learn how to export TechSupport files from the APIC. These files contain detailed logs, configurations, and diagnostic information that are crucial for escalating complex issues to Cisco TAC (Technical Assistance Center) or for in-depth analysis.
Next steps
If a simulator covers what you need, start with the DevNet sandboxes. If you need physical switches, a multipod design or a VMM integration against real hosts, reserve a CloudMyLab ACI Learning Lab. For questions, email support@cloudmylab.com.
Frequently Asked Questions
Where can I get a Cisco ACI lab environment?
Cisco DevNet offers a free Always-On ACI Simulator sandbox and a reservable one for up to 5 consecutive days, both on simulated switches. For physical leaf and spine switches with an APIC and a UCS server, CloudMyLab's ACI Learning Lab can be reserved in 6-day blocks. You can also buy and rack your own fabric.
Is there a free Cisco ACI lab?
Yes. Cisco DevNet runs an Always-On ACI Simulator sandbox you can use at any time, and a reservable ACI Simulator sandbox for up to 5 consecutive days. Both need a free Cisco account, and the Always-On fabric is shared with other users.
Can you practice Cisco ACI without physical hardware?
Yes, for the APIC GUI, the policy model and the REST API. The ACI Simulator uses simulated leaf and spine switches, so traffic tests between endpoints need a fabric with physical switches.
Does CloudMyLab offer Cisco ACI training?
No. CloudMyLab provides the ACI lab infrastructure, licensing and sample labs, not courses. If you want instructor-led training, CloudMyLab can connect you with its training partners, Patriot Solutions and Training World 360.
How long can I book a CloudMyLab ACI lab?
ACI Learning Labs are reserved in blocks of 6 days, Monday to Saturday, with access 24 hours a day. Each lab includes jump box and AnyConnect VPN access for 2 users.