ACI Multi-Site Webinar Section-1

ACI Multi-Site Introduction and
Use Cases
Max Ardica - Principal Engineer (IBNG)
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public 1
ACI Anywhere
Fabric and Policy Domain Evolution
ACI Single Pod Fabric ACI Multi-Site Cloud ACI
ISN
Fabric ‘A’ Fabric ‘n’
MP-BGP - EVPN
… ACI 3.1/4.0 - Remote Leaf

ACI 2.0 - Multiple Networks
(Pods or Availability Zones) and vPod extends a Fabric to
in a single Fabric (Region) remote locations
ACI 1.0 - ACI 3.0 – Multiple Fabrics ACI 4.1 & 4.2 – ACI
ACI Multi-Pod Fabric (Regions) interconnected in the
ACI Remote Leaf
Leaf/Spine Single Extensions to Multi-Cloud
Pod Fabric same Multi-Site Orchestrator
IPN domain
Pod ‘A’ Pod ‘n’
MP-BGP - EVPN
…
APIC Cluster
Multi-Pod or Multi-Site?
That is the question…
And the answer is…
BOTH!
Systems View (How do these things relate)
Change and Network Fault Domain Isolation
Active Workloads Layer 3 Active Workloads
Layer 2 & Layer 3 Inter Region Layer 2 & Layer 3
ACI Multi-Site Orchestrator
Multi-Pod Fabric ‘A’ (Region 1) Multi-Pod Fabric ‘B’ (Region 2)
Fabric NetworkFault Domain Fabric Network Fault Domain Fabric Network Fault Domain Fabric Network Fault Domain
Pod A.1 (AZ 1) Pod A.2 (AZ 2)

Application1 Pod B.1 (AZ 1) Pod B.2 (AZ 2)
Application 2
workloads deployed workloads deployed
Application Policy Change Domain Application Policy Change Domain
across Pods (AZs) across Pods (AZs)
Common Namespace (IP, DNS, Active Directory…)
But wait! Could I deploy
Multi-Site also to handle
more typical Multi-Pod use
cases?
Multi-Site for Active/Active Application Deployments?
Things to Watch Out For
• ACI Multi-Site allows to extend connectivity and

policies between separate APIC domains
• Layer 3 only across sites
• Layer 2 with and without BUM flooding
• Keep in mind some specific considerations before

deploying Multi-Site for “classic” Active/Active
application deployments (i.e. components of a single
application deployed across sites)
• Loss of change and network fault domain isolation across
separate ACI domains
• Creation of separate VMM domains by design (loss of intra-
cluster functionalities like DRS, vSphere FT/HA, …)
• Specific service node insertion deployment considerations (use
of separate service nodes per fabric, limited support for service
nodes clustering across sites, …)
ACI Multi-Site and VMM Integration
Separate VMM per Site
ISN
Site 1 VMM Domain VMM Domain Site 2

DC1 DC2
VMM 1 VMM 2
HV vSwitch1
HV HV Managed by HV vSwitch2
HV HV
VMM 1
HV Cluster 1 Managed HV Cluster 2
by VMM 2
• Typical deployment model for an ACI Multi-Site

• Creation of separate VMM domains in each site, which are then exposed to the Multi-Site
Orchestrator
• No support for DRS, vSphere HA/FT
ACI Multi-Site and Network Services
Overview
VXLAN
IP Network
Site 1 Site 2
MP-BGP - EVPN
Multi-Site Orchestrator
REST
GUI
API
 Separate ACI Fabrics with independent APIC clusters  MP-BGP EVPN control plane between sites
 ACI Multi-Site pushes cross-fabric configuration to multiple  Data Plane VXLAN encapsulation across sites
APIC clusters providing scoping of all configuration changes  End-to-end policy definition and enforcement
ACI Multi-Site
Most Common Use Cases
• Scale-up DC network model • Data Centre Interconnect (DCI)
Building a very large intra-DC network (above 500* leaf nodes) Extend connectivity/policy between ‘loosely coupled’ DC sites
Disaster Recovery and IP mobility use cases
*500 leaf nodes supported in a Multi-Pod fabric starting with ACI 4.2(4) release
• Cloud ACI • SP 5G Telco DC/Cloud**

Integration between on-prem and public clouds Centralized DC Orchestration for 5G distributed DCs
SR-MPLS/MPLS Handoff on Border Leaf nodes
No VXLAN encapsulation between fabrics
**MSO 3.0(1) and ACI 5.0(1) releases (and beyond)

ACI Anywhere
Where to Go for More Information
 ACI Design Guide

https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/
white-paper-c11-737909.html
 ACI Multi-Pod White Paper

 ACI Multi-Pod Configuration White Paper

 ACI Multi-Pod and Service Node Integration White Paper

 ACI Multi-Site White Paper

ACI Anywhere
Where to Go for More Information (2)
 ACI Multi-Site and Service Node Integration White Paper

 ACI Remote Leaf Architecture White Paper

white-paper-c11-740861.
html
 ACI Virtual Pod Architecture White Paper

white-paper-c11-742393
.html
 Cloud ACI on AWS White Paper

.html
 Cloud ACI on Microsoft Azure White Paper

.html

ACI Multi-Site Webinar Section-1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ACI Multi-Site Webinar Section-1

Uploaded by

Copyright:

Available Formats

ACI Multi-Site Introduction and

… ACI 3.1/4.0 - Remote Leaf

That is the question…

ACI Multi-Site Orchestrator

Multi-Pod Fabric ‘A’ (Region 1) Multi-Pod Fabric ‘B’ (Region 2)

Pod A.1 (AZ 1) Pod A.2 (AZ 2)

Common Namespace (IP, DNS, Active Directory…)

• ACI Multi-Site allows to extend connectivity and

• Keep in mind some specific considerations before

Site 1 VMM Domain VMM Domain Site 2

• Typical deployment model for an ACI Multi-Site

• Cloud ACI • SP 5G Telco DC/Cloud**

**MSO 3.0(1) and ACI 5.0(1) releases (and beyond)

 ACI Design Guide

 ACI Multi-Pod White Paper

 ACI Multi-Pod Configuration White Paper

 ACI Multi-Pod and Service Node Integration White Paper

 ACI Multi-Site White Paper

 ACI Multi-Site and Service Node Integration White Paper

 ACI Remote Leaf Architecture White Paper

 ACI Virtual Pod Architecture White Paper

 Cloud ACI on AWS White Paper

 Cloud ACI on Microsoft Azure White Paper

You might also like