
Course Introduction & Basics
01 Course Introduction
02 What is ACI
03 More on ACI ...
04 ACI Constructs
05 ACI Bring up process Theory part 01
06 Bring up process Part 02
07 ACI Fabric Discovery
ACI Model & Policies Part 01
08 ACI Object Model
09 Managed object
10 ACI object Programming options part 01
11 ACI object Programming options part 02
12 Fabric Access Policies
ACI Model & Policies Part 02
13 ACI Layer 2 Connectivity
14 Bare Metal Lab Theory
15 Bare Metal Lab Part01
16 Bare Metal Lab Part02
17 Bare Metal Lab Part03 different EPG
18 Summary of this Section
Endpoint Learning & iVxlan
19 Endpoint Learning Part01
20 Endpoint Learning Part02
21 ACI iVxlan introduction
22 What is Vxlan
23 Vxlan Encapsulation
ACI Forwarding Component part 01
24 ACI Packet Forward introduction
25 When Source Leaf knows the destination Leaf
26 Spine-Proxy
27 ACI Flood Method
28 ACI Forwarding Component Part 01
29 ACI Forwarding Component Part 02 VLAN in ACI
ACI Forwarding Component part 02
30 Pervasive Gateway BD SVI
31 Forwarding Scope BD or VRF
32 Forward mode in BD
33 Spine-Proxy & Arp Glean
34 Forwarding Software Architecture and ASIC Generation
35 The life of a packet going through ACI
Continue the bring up process by configuring bond interfaces and assigning management and dynamic IPs on the epic controller, then verify interface status and IP allocation.
Master the ACI fabric discovery by connecting spine and leaf to the epic controller, powering up, and auto registering devices with serial numbers, hostnames, and fabric inventory.
Explore the ACI object model, where every element is a managed object, and learn how logical, resolve, and concrete models, APIs, and CLI configure tenants, EPGs, bridge domains, and subnets.
Explore ACI object programming options from interfaces to APIs and database-enabled configuration, using the management information model reference and API docs to query tenants and health.
Explore how Cisco ACI constructs tenants, virtual networks, bridge domains, and subnets with gateways to build the underlay and overlay, and how contracts and filters govern EPG communication.
Explore bare metal lab concepts, contrasting traditional nexus connectivity with ACA configurations, and learn to implement interface policy, interface policy group, and domain in ACA to connect endpoints.
Learn local and remote endpoint learning in Cisco ACI, including mac and ip address learning, bridge domain and vrf packet behavior, and how moves update coop database entries.
Discover how the ACI data plane uses VXLAN encapsulation to carry inner and outer headers over a leaf-spine fabric, enabling automated, scalable east-to-west traffic and network virtualization.
Explain vxlan encapsulation in Cisco ACI, showing how a frame is wrapped with vxlan, udp, and ip headers, plus outer macs, using a 24-bit vxlan id and udp port 4789.
Explain how ACI floods unknown destination traffic inside a bridge domain using multicast, with a group multicast IP per bridge domain and traffic encapsulated as multicast toward a forwarding tree.
Explore the five bridge-domain forwarding modes, including unique cost routing, unknown unicast and unknown multicast handling, hardware proxy, flagging, flood, and encapsulation options that shape L2 and L3 behavior.
Follow how an icmp packet traverses an ACI fabric, from endpoint learning and arp exchanges to coop lookups and proxy routing across leaves and spine in a bridge domain.
Explore hypervisor integration in Cisco ACI, using the flex open extensible policy to deliver policy across physical and virtual domains, enabling unified security, visibility, and automation.
What is Cisco ACI?
Cisco ACI is the solution that emerged from Cisco, following its acquisition of Insieme, which is
a company they funded for more than two years.
ACI is seen by many as Cisco’s software-defined networking (SDN) offering for data center and
cloud networks.
How Cisco ACI Works?
Cisco ACI is a tightly coupled policy-driven solution that integrates software and hardware.
The hardware for Cisco ACI is based on the Cisco Nexus 9000 family of switches.
The software and integration points for ACI include a few components, including Additional
Data Center Pod, Data Center Policy Engine, and Non-Directly Attached Virtual and Physical Leaf
Switches. While there isn’t an explicit reliance on any specific virtual switch, at this point,
policies can only be pushed down to the virtual switches if Cisco’s Application Virtual Switch (AVS)
is used, though there has been talk about extending this to Open vSwitch in the near future.
To a large extent, the network for Cisco ACI is no different than what has been deployed over
the past several years in enterprise data centers. What is different, however, is the management
and policy framework, along with the protocols used in the underlying fabric.
In a leaf-spine ACI fabric, Cisco is provisioning a native Layer 3 IP fabric that supports
equal-cost multi-path (ECMP) routing between any two endpoints in the network, but uses
overlay protocols, such as virtual extensible local area network (VXLAN) under the covers
to allow any workload to exist anywhere in the network. Supporting overlay protocols is
what will give the fabric the ability to have machines, either physical or virtual, in
the same logical network (Layer 2 domain), even while running Layer 3 routing down to the
top of each rack. Cisco ACI supports VLAN, VXLAN, and network virtualization using generic
routing encapsulation (NV-GRE), which can be combined and bridged together to create a logical
network/domain as needed.