Professional Documents
Culture Documents
Deployment Options
Max Ardica – Principal Engineer
BRKACI-2003
Agenda
• ACI Introduction and Multi-Fabric Use Cases
• ACI Multi-Fabric Design Options
• ACI Stretched Fabric Overview
• ACI Multi-Pod Deep Dive
• ACI Multi-Site Solutions Overview
• Conclusions
3
Session Objectives
4
Introducing: Application Centric Infrastructure (ACI)
Web App DB
Outside QoS QoS QoS
(Tenant
Filter Service Filter
VRF)
APIC
Application Policy
ACI Fabric Infrastructure Controller
Integrated GBP VXLAN Overlay
6
ACI MultiPod/MultiSite Use Cases
Single Site Multi-Fabric
Multiple Fabrics connected within the same DC (between halls, buildings, … within the
same Campus location)
Cabling limitations, HA requirements, Scaling requirements
8
ACI Multi-Fabric Design Options
Single APIC Cluster/Single Domain Multiple APIC Clusters/Multiple Domains
Stretched Fabric Dual-Fabric Connected (L2 and L3 Extension)
ACI Fabric ACI Fabric 1 ACI Fabric 2
Site 1 Site 2
L2/L3
Pod ‘A’ IP Network Pod ‘n’ Site ‘A’ IP Network Site ‘n’
MP-BGP - EVPN
… MP-BGP - EVPN
9
APIC Cluster
Agenda
• ACI Introduction and Multi-Fabric Use Cases
• ACI Multi-Fabric Design Options
• ACI Stretched Fabric Overview
• ACI Multi-Pod Deep Dive
• ACI Multi-Site Solutions Overview
• Conclusions
10
For more information on ACI Stretched
Stretched ACI Fabric Fabric Deployment:
BRKACI-3503
DC Site 1 DC Site 2
vCenter
Fabric stretched to two sites works as a Work with one or more transit leaf per site
single fabric deployed within a DC any leaf node can be a transit leaf
One APIC cluster one management and Number of transit leaf and links dictated by
configuration point redundancy and bandwidth capacity decision
Anycast GW on all leaf switches Different options for Inter-site links (dark fiber, 11
Site 1
Site 3
Transit Leaf
2x40G or 4x40G
16
Agenda
• ACI Introduction and Multi-Fabric Use Cases
• ACI Multi-Fabric Design Options
• ACI Stretched Fabric Overview
• ACI Multi-Pod Solution Deep Dive
• ACI Multi-Site Solutions Overview
• Conclusions
17
ACI Multi-Pod Solution
Overview
Inter-Pod Network
MP-BGP - EVPN
Multiple ACI Pods connected by an IP Inter-Pod Forwarding control plane (IS-IS, COOP)
L3 network, each Pod consists of leaf and spine fault isolation
nodes Data Plane VXLAN encapsulation between
Managed by a single APIC Cluster Pods
18
Single Management and Policy Domain End-to-end policy enforcement
ACI Multi-Pod Solution
Use Cases
Handling 3-tiers physical Pod
cabling layout Inter-Pod
Leaf Nodes Network
Cable constrain (multiple
buildings, campus, metro)
requires a second tier of “spines” Spine Nodes
Preferred option when compared
to ToR FEX deployment
Software
The solution will be available from Q3CY16 SW Release
Hardware
The Multi-Pod solution can be supported with all currently shipping Nexus
9000 platforms
The requirement is to use multicast in the Inter-Pod Network for handling
BUM (L2 Broadcast, Unknown Unicast, Multicast) traffic across Pods
20
ACI Multi-Pod Solution
Supported Topologies
Intra-DC Two DC sites connected
back2back
10G/40G/100G
40G/100G 40G/100G
Pod 1 Pod n Pod 1 40G/100G 40G/100G
Pod 2
Dark fiber/DWDM (up
to 10 msec RTT)
…
APIC Cluster APIC Cluster
DB Web/App Web/App DB Web/App Web/App
L3
40G/100G 40G/100G 40G/100G
21
Pod 3
ACI Multi-Pod Solution
Scalability Considerations
Use case 1: larger number of Pods (up to 20) with a small number of
leaf nodes in each Pod (20-30)
Use case 2: low number of Pods (2-3) with large number of leaf
nodes in each Pod (up to 200)
22
ACI Multi-Pod Solution
Inter-Pod Network (IPN) Requirements
Not managed by APIC, must be pre-configured
23
APIC – Distributed Multi-Active Data Base
Shard 1 Shard 11
Shard Shard 1
APIC APIC APIC
Shard 2 Shard 3 Shard 2 Shard 3 Shard 2 Shard 3
When an APIC fails a backup copy of the shard is promoted to active and it takes over
for all tasks associated with that portion of the Data Base
26
APIC – Design Considerations
X X
APIC APIC APIC
Additional APIC will increase the system APIC will allow read-only access to the DB
scale (today up to 5 nodes supported) but when only one node remains active
does not add more redundancy (standard DB quorum)
28
ACI Multi-Pod Solution
Auto-Provisioning of Pods
DHCP requests are relayed
by the IPN devices back to
Provisioning interfaces on the the APIC in Pod 1 Spine 1 in Pod 2 connects
spines facing the IPN and EVPN to the IPN and generates
control plane configuration 5 DHCP requests
3 4
6
DHCP response reaches Spine 1
allowing its full provisioning
2 7
30
ACI Fabric – Integrated Overlay
Decoupled Identity, Location & Policy
APIC
ACI Fabric decouples the tenant end-point address, it’s “identifier”, from the location of that end-
point which is defined by it’s “locator” or VTEP address
Forwarding within the Fabric is between VTEPs (ACI VXLAN tunnel endpoints) and leverages an
extender VXLAN header format referred to as the ACI VXLAN policy header
The mapping of the internal tenant MAC or IP address to location is performed by the VTEP using
a distributed mapping database 31
Host Routing - Inside
Inline Hardware Mapping DB - 1,000,000+ hosts
10.1.3.35 Leaf 3
10.1.3.11 Leaf 1
Global Station Table Proxy Proxy Proxy Proxy fe80::8e5e Leaf 4
contains a local cache fe80::5b1a Leaf 6
of the fabric endpoints
10.1.3.35 Leaf 3
Proxy Station Table contains
addresses of ‘all’ hosts attached
* Proxy A to the fabric
10.1.3.11 Port 9
Local Station Table The Forwarding Table on the Leaf Switch is divided between local (directly attached) and
contains addresses of global entries
‘all’ hosts attached The Leaf global table is a cached portion of the full global table
directly to the Leaf
If an endpoint is not found in the local cache the packet is forwarded to the ‘default’
forwarding table in the spine switches (1,000,000+ entries in the spine forwarding table)
32
ACI Multi-Pod Solution
Inter-Pods MP-BGP EVPN Control Plane
34
ACI Multi-Pod Solution
Overlay Data Plane
Group
VTEP IP VNID Tenant Packet
Policy
Spine encapsulates
172.16.2.40 Leaf 4 Leaf 4
172.16.1.20 Proxy B traffic to remote 172.16.1.20
Proxy A
172.16.2.40
Proxy B Spine VTEP Spine encapsulates
traffic to local leaf
3 4
Proxy A Proxy B
172.16.2.40 Pod1 L4
* Proxy A
5 * Proxy B
35
ACI Multi-Pod Solution
Overlay Data Plane (2)
Group
VTEP IP VNID Tenant Packet
Policy
172.16.1.20 Pod2 L4
172.16.2.40 Pod1 L4
* Proxy A
8 * Proxy B
36
ACI Multi-Pod Solution
Handling of Multi-Destination Traffic (BUM*)
IPN replicates traffic to all
the Pods that joined GIPo 1
(optimized delivery to Pods)
Spine 2 is responsible to
4
send GIPo 1 traffic toward
the IPN
3
37
39
ACI Integration with WAN at Scale
‘Project GOLF’ Overview
‘GOLF’ Devices Addresses both control plane and data
WAN plane scale
VXLAN data plane between ACI spines and
WAN Routers
MP-BGP BGP-EVPN control plane between ACI spines
EVPN IP Network and WAN routers
OpFlex for exchanging config parameters (VRF
names, BGP Route-Targets, etc.)
MP-BGP
MP-BGP
EVPN IP Network IP Network
EVPN
MP-BGP
EVPN
41
Multi-Pod and GOLF
Intra-DC Deployment – Control Plane
GOLF
Devices WAN
WAN routes received on the Pod
spines as EVPN routes and translated
MP-BGP EVPN Control Plane to VPNv4/VPNv6 routes with the spine
proxy TEP as Next-Hop
IPN
Public BD subnets advertised to
GOLF devices with the external
spine-proxy TEP as Next-Hop
Multiple
Pods
Web/App Web/App
... Web/App
DB DB
Single
Single APIC Cluster
APIC Domain
42
Multi-Pod and GOLF
Intra-DC Deployment – Control Plane
Multiple
Pods
Web/App Web/App
... Web/App
DB DB
Single
Single APIC Cluster
APIC Domain
43
*Not available at FCS
Multi-Pod and GOLF
Multi-DC Deployment – Control Plane
Web/App Web/App
DB DB
Single APIC Cluster
46
Multi-Pod and GOLF
Multi-DC Deployment – Data Plane
IPN
Spine encapsulates traffic
Proxy A Proxy B
to the destination VTEP
that can then apply policy
Web/App Web/App
DB DB
Single APIC Cluster
47
Multi-Pod and GOLF
Multi-DC Deployment – Data Plane (2)
Traffic is received by
the external user
GOLF devices de-encapsulate traffic WAN
and route it to the WAN (or LISP
encapsulates to the remote router)
IPN
Web/App Web/App
DB
Single APIC Cluster
48
ACI Multi-Pod Solution
Summary
49
Agenda
• ACI Introduction and Multi-Fabric Use Cases
• ACI Multi-Fabric Design Options
• ACI Stretched Fabric Overview
• ACI Multi-Pod Solution Deep Dive
• ACI Multi-Site Solutions Overview
• Conclusions
50
For more information on ACI Dual Fabric
ACI Dual-Fabric Solution Deployment:
Overview BRKACI-3503
L2/L3
DCI
MP-BGP - EVPN
…
Separate APIC
IS-IS, COOP, MP-BGP Clusters IS-IS, COOP, MP-BGP
Multiple ACI fabrics connected via IP Network End to end policy enforcement
Separate availability zones with maximum isolation with policy collaboration
Separate APIC clusters, separate management and Support multiple sites
policy domains, separate fabric control planes Not bound by distance 52
ACI Multi-Site
Reachability
Inter-Site Network
MP-BGP - EVPN
…
Separate APIC
Clusters
Web1 Web2 Import Web & App Export Web & App Web1 Web2
from Fabric ‘B’ to Fabric ‘A’
MP-BGP - EVPN
…
Separate APIC
Clusters
Policy is applied at provider of the contract (always at fabric where the provider endpoint is
connected)
Scoping of changes
No need to propagate all policies to all fabrics
Different policy applied based on source EPG (which fabric)
Agenda
• ACI Introduction and Multi-Fabric Use Cases
• ACI Multi-Fabric Design Options
• ACI Stretched Fabric Overview
• ACI Multi-Pod Solution Deep Dive
• ACI Multi-Site Solutions Overview
• Conclusions
56
Conclusions
Cisco ACI offers different multi-fabric
options that can be deployed today
There is a solid roadmap to evolve those
options in the short and mid term
Multi-Pod represents the natural evolution
of the existing Stretched Fabric design
Multi-Site will replace the Dual-Fabric
approach
57
Where to Go for More Information
58
Thank you
59