ACI
ACI
ACI
We identify the requirements, we describe the application, we tell ACI how we want the
application to behave, who its going to talk to, and Fabric deploys the policies to Hardware
Switches based on Promise Theory.
ACI Constructs & Terminologies
OSI Model vs ACI Logical Model
ACI Underlay Hardware – Nexus 9500 & 9300 Switches
Leaf Switches provide connectivity into the Fabric at the ToR or EoR. They
serve as distributed layer 3 gateways, the policy enforcement points, and
gateways into external networks.
Border Leaf Switches are any leaf nodes that connect to a network device
external to the ACI fabric, such as firewalls, load balancers, routers, or non-
ACI switches; allowing a smooth migration to an ACI network.
Spine Switches provide a non-blocking fabric with rapid failure detection and
re-routing. These are used to forward traffic between two leaf switches.
Beginning with Software version 2.0(2), ACI supports Layer 3 connections with
EVPN to the spine switches.
APIC Controllers provide the centralized point of management for fabric
configuration and observing the summary operational state. From a policy
perspective, the APIC is the primary point of contact for configuration and
acts as the policy repository.
ACI Network – Spine-Leaf Multistage (CLOS) Fabric
Fabric Policies – Configure Interfaces that connects Spines & Leaf Switches, and does other POD
Mgmt. tweaks, like NTP, BGP, ISIS, COOP GPO, Mgmt. Access, Date/Time, etc.
ACI – Access Policy
Access Policies – Configures External facing Interfaces, like Servers, External Switches,
etc.