ACI Anywhere Extending The ACI Fabric - Max Ardica

ACI Anywhere: Extending the ACI Fabric
Max Ardica
Principal Engineer – Cisco INSBU
2
Agenda
§ ACI Network and Policy Domain Evolution

§ ACI Multi-Pod
§ ACI Multi-Site
§ ACI Remote Physical Leaf
§ ACI Remote Virtual Leaf (vPod)
§ ACI Extensions to Multi-Cloud
§ Conclusions and Q&A
ACI Network and Policy Domain
Evolution
Introducing: Application Centric Infrastructure (ACI)
Web App DB
Outside QoS QoS QoS
(Tenant Service
Filter Filter
VRF)
APIC
Application Policy
ACI Fabric Infrastructure Controller
Integrated GBP VXLAN Overlay
19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 5

Cisco ACI: Industry Leader
4,800+ 46+% 65+

ACI Customers ACI Attach Rate Ecosystem Partners
Ecosystem Partners

Cisco ACI
Fabric and Policy Domain Evolution
ACI Single Pod Fabric ACI Multi-Site ACI Multi-Cloud

IP
Fabric ‘A’ Fabric ‘n’
MP-BGP - EVPN
…
ACI 2.0 - Multiple Networks ACI 3.1/3.2 - Remote Leaf
(Pods) in a single Availability and vPod extends an
Zone (Fabric) Availability Zone (Fabric) to
remote locations
ACI 1.0 - ACI Multi-Pod Fabric ACI 3.0 – Multiple Availability ACI Remote Leaf Future – ACI Extensions
Leaf/Spine Single Zones (Fabrics) in a Single to Multi-Cloud
Pod Fabric IPN Region ’and’ Multi-Region
Pod ‘A’ Pod ‘n’ Policy Management
MP-BGP - EVPN
…
APIC Cluster

Regions and Availability Zones
OpenStack and AWS Definitions
OpenStack
• Regions - Each Region has its own full OpenStack
deployment, including its own API endpoints, networks
and compute resources
• Availability Zones - Inside a Region, compute nodes can
be logically grouped into Availability Zones, when launching
new VM instance, we can specify AZ or even a specific
node in a AZ to run the VM instance
Amazon Web Services

• Regions – Separate large geographical areas, each
composed of multiple, isolated locations known as
Availability Zones
• Availability Zones - Distinct locations within a region
that are engineered to be isolated from failures in other
Availability Zones and provide inexpensive, low latency
network connectivity to other Availability Zones in the
same region
Typical Requirement
Creation of Two Independent Fabrics/AZs
Fabric ‘A’ (AZ 1)
Fabric ‘B’ (AZ 2)
Application
workloads
deployed across
availability zones 19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 9
Typical Requirement
Creation of Two Independent Fabrics/AZs
Multi-Pod Fabric ‘A’ (AZ 1)

‘Classic’ Active/Active
Pod ‘1.A’ Pod ‘2.A’
ACI Multi-Site
Multi-Pod Fabric ‘B’ (AZ 2)

‘Classic’ Active/Active
Application
Pod ‘1.B’workloads Pod ‘2.B’
deployed across
availability zones 19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 10
ACI Multi-Pod
ACI Multi-Pod
Overview
VXLAN
Inter-Pod Network
Pod ‘A’ Pod ‘n’
MP-BGP - EVPN
APIC Cluster
IS-IS, COOP, MP-BGP IS-IS, COOP, MP-BGP
Availability Zone
• 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
• Single Management and Policy Domain
19 - 21 March 2018 | Cisco Connect | End-to-end
•Rovinj, Croatia
BRKACI-2003 policy enforcement 12
Single Availability Zone with Tenant Isolation
Isolation for ‘Virtual Network Zone and Application’ Changes
Inter-Pod Network
ACI Multi-Pod
Fabric
APIC Cluster
Tenant ‘Prod’ Configuration/Change Domain Tenant ‘Dev’ Configuration/Change Domain
• The ACI ‘Tenant’ construct provide a domain of application and associated virtual
network policy change
• Domain of operational change for an application (e.g. production vs. test)
ACI Multi-Pod
Supported Topologies
Intra-DC Two DC sites directly connected
1G/10G/40G/100G
10G*/40G/100G 10G*/40G/100G
POD 1 POD n POD 1 10G*/40G/100G
Dark fiber/DWDM
10G*/40G/100G
POD 2
(up to 50** msec RTT)
…
APIC Cluster APIC Cluster
3 (or more) DC Sites directly connected Multiple sites interconnected by a

1G/10G/40G/100G generic L3 network
10G*/40G/100G
POD 1 10G*/40G/100G POD 2
Dark fiber/DWDM 10G*/40G/100G 10G*/40G/100G
(up to 50 msec RTT)
L3
10G*/40G/100G
10G*/40G/100G (up to 50msec RTT)
10G*/40G/100G
POD 3 * 10G only 19

with
- 21QSA
Marchadapters on EX/FX
2018 | Cisco and| 9364C
Connect spines
Rovinj, Croatia ** 50 msec support added in SW release 2.3(1) 14
ACI Multi-Site
ACI Multi-Site
Overview
VXLAN
IP Network
MP-BGP - EVPN
Multi-Site Orchestrator
Site 1 Site 2
REST
GUI
API Availability Zone ‘B’
Availability Zone ‘A’
• Separate ACI Fabrics with independent APIC clusters • MP-BGP EVPN control plane between sites
• ACI Multi-Site Orchestrator pushes cross-fabric • Data Plane VXLAN encapsulation across
configuration to multiple APIC clusters providing sites
scoping of all configuration changes • End-to-end policy definition and enforcement
ACI Multi-Site
Main Use Cases
Scale-Up Model to Build a Large Data Center Interconnect (DCI)

Intra-DC Network

ACI Multi-Site
Network and Identity Extended between Fabrics
Network information carried across Identity information carried across
Fabrics (Availability Zones) Fabrics (Availability Zones)
VTEP IP VNID Class-ID Tenant Packet No Multicast Requirement in

Backbone, Head-End
Replication (HER) for any
IP Network Layer 2 BUM traffic)
MP-BGP - EVPN

ACI Multi-Site
Namespace Normalization
VNID à 16678781
Class-ID: 49153 Translation of Class-ID, VNID
(scoping of name spaces)
IP Network
VNID à 16678781 Spine Translation Table
Class-ID: 49153
Rem. Site Local Site
VNID 16678781 16547722

MP-BGP - EVPN Class-ID 49153 32770
VNID à 16547722 EP1

C EP2
EPG
Class-ID: 32770
EPG
VNID à 16678781
Class-ID: 49153 EP1 EP2 Site 2
Site 1 EPG C EPG
Leaf to Leaf VTEP, Class-ID is local to the Fabric
Leaf to Leaf VTEP, Class-ID is local to the Fabric
• Maintain separate name spaces with ID translation performed on the spine nodes
VNID Class-ID Tenant Packet
•
VNID Requires specific HW on the spine to support for this functionality
Class-ID Tenant Packet VNID Class-ID Tenant Packet
• Multi-Site Orchestrator instructs local APIC to program translation tables on spines

ACI Multi-Site
Hardware Requirements
§ Support all ACI leaf switches (1st Generation, -EX and -FX)
§ Only –EX spine (or newer) to Can have only a subset
of spines connecting to
connect to the inter-site network IP Network
the IP network
§ New 9364C non modular spine

1st Gen 1st Gen
(64x40G/100G ports) supported for -EX -EX
Multi-Site from ACI 3.1 release

§ 1st generation spines (including 9336PQ)
not supported
§ Can still leverage those for intra-site leaf
to leaf communication

ACI Multi-Site Networking Options
Per Bridge Domain Behavior
Layer 3 only across sites IP Mobility without BUM flooding Layer 2 adjacency across Sites
1 2 3
ISN ISN ISN
Site Site Site Site

Site
2 Site Site
1 2 1 2 1 2
§ Bridge Domains and subnets not § Same IP subnet defined in separate § Interconnecting separate sites for
extended across Sites Sites fault containment and scalability
reasons
§ Layer 3 Intra-VRF or Inter-VRF § Support for IP Mobility (‘cold’ and
communication (shared services ‘live’* VM migration) and intra- § Layer 2 domains stretched across
across VRFs/Tenants) subnet communication across sites Sites, support for ‘live’* VM
migration and application clustering
§ No Layer 2 BUM flooding across
sites § Layer 2 BUM flooding across
sites
MSO GUI MSO GUI MSO GUI

(BD) (BD) (BD)
19 - 21 March 2018 | Cisco *’Live’

Connect migration officially
| Rovinj, Croatia supported from ACI release 3.2 21
ACI Multi-Site
CloudSec Encryption for VXLAN Traffic
Encrypted Fabric to Fabric Traffic
VTEP Information Clear Text [ GCM-AES-128 (32-bit PN), GCM--AES-256
(32-bit PN), GCM-AES-128-XPN (64-bit PN),
GCM-AES-256-XPN (64-bit PN)])
VTEP IP MACSEC VXLAN Tenant Packet
Inter-Site Network
MP-BGP - EVPN
Support planned for a future ACI release for FX line cards and 9364C platform
ACI Multi-Site
Multi-Site Orchestrator (MSO)
• Micro-services architecture
§ Multiple MSO nodes are created and run
REST concurrently (active/active)
GUI
API
§ vSphere VM only form factor initially (physical
appliance planned for a future ACI release)
ACI Multi-Site
• OOB Mgmt connectivity to the APIC clusters
VM VM VM deployed in separate sites
§ Support for 500 msec to 1 sec RTT
Hypervisor • Main functions offered by MSO:
§ Monitoring the health-state of the different ACI Sites
§ Provisioning of day-0 configuration to establish
…..
Site 1 Site 2 Site n inter-site EVPN control plane
§ Defining and provisioning policies across sites
§ Day-2 operation functionalities

ACI Multi-Site
MSO Schema and Templates
Schema
• Template = APIC policy definition
(App & Network) TemplateDEFINITION
Template
POLICY
• Template is the scope/granularity of what EP1

EPG
C
EP2
EPG
can be pushed to sites

• Template is associated to all managed sites
SITE
or to a subset of sites LOCAL
• Schema = container of Templates sharing a

common use-case
• Scope of change: policies in different Site 1 Site 2
templates can be pushed to separate sites EFFECTIVE EFFECTIVE
POLICY POLICY
at different times

ACI Multi-Site
Day-2 Operations: Full-Stack Consistency Checker
ACI 3.2 Release
• Multi-Site Infra: Unicast, Multicast, BGP TEPs

and Tunnel state
• Multi-Site Tenant and EPG granularity:
§ Inspect and validate full-stack programming: MSC,
APICs and Spine translations
§ Validate the consistency of local and remote inter-
MP-BGP EVPN site EPGs, BD, VRF, External EPG, policies, etc.
Spines VXLAN Spines

§ Root cause configuration programming issues
without calling TAC
• GUI and APIs will both be supported

ACI Remote Physical Leaf
Business Value and Use Cases
Extending the ACI policy model outside the main datacenter to remote
sites distributed over IP Backbone (Satellites DCs, CoLo locations, etc.)
Extending ACI fabric policy and L2/L3 connectivity to a small DR site

without requiring the deployment of a full-blown ACI Fabric
Centralized Policy Management and Control Plane for remote locations
Small form factor solution at locations with space constraints

Conceptual Architecture
A Remote Leaf ‘Site’ gets
associated with the Spines of
one specific Pod in Main DC
APIC and Spine Nodes (Proxy
function) remain at primary Pod(s) IP WAN
IPN L2 / L3
IPN Requirements (3.1)

§ 150 msec maximum RTT
§ 500 Mbps minimum BW
§ 1600B minimum MTU
§ No PIM-Bidir required vSwitch Bare
Metal
Legacy
Infrastructure
Hypervisor
ACI Main DC
Remote Leaf Site: a pair of Nexus 9300 nodes

connected to a L3 Network via uplink ports and
fully managed by a centralized APIC cluster
Hardware/Software Support
All hardware from -EX onwards is required for remote leaf nodes
and the spines to which they get associated
ACI Main Pod Remote Leaf Nodes

Supported Spines Supported Leaf
Fixed • N93180YC-EX
• N9364C • N93108TC-EX
Modular • N93180LC-EX
• N9732C-EX • N93180YC-FX
• N9736C-FX • N9K-C93108TC-FX
• N9K-C9348GC-FXP

Functionalities and Scale
IP WAN Only 2 RLs

ACI Main DC IPN per ‘RL Site’
Remote Leaf Site
L3Out
vSwitch Bare
Hypervisor Metal
§ All major features supported on RL nodes
§ Scalability values are the same as for local
leaf deployments Service Graph
§ 40 RL (20 sites, 2 RL per site) (unmanaged mode) with
PBR

Automatic RL Discovery
OSPF can be
redistributed into
any other WAN
control plane First-hop L3 device
receives reachability
Infra Tenant L3Out information to central
Configuration on IP WAN IPN APIC nodes
Local APIC DHCP requests are
2 relayed to the central
OSPF APIC cluster by the
first-hop L3 device DHCP response
OSPF
received by the RL
DHCP response 4
3 sent to the Relay Node allowing then
RL Node generates DHCP
1 requests on uplinks its full provisioning
Agent
(tagged with VLAN 4)
RL Node
Remote Leaf Site

ACI Main DC

Establishing End-to-End IP Connectivity
First-hop L3 device
receives reachability OSPF can be
information to RL redistributed into any
node other WAN control
IP WAN IPN plane
OSPF
OSPF RL node RL TEPs
configuration OSPF assigned to the
fully provisioned node
RL Node
Remote Leaf Site

ACI Main DC

COOP for Announcing Remote Endpoint Information
COOP Sessions
between RLs
nodes and spines
COOP DB
EP1 RL TEP
IP WAN IPN Anycast
Anycast VTEP
EP2 RL TEP VTEP for (RL
for RLs RLs
TEP)
(RL TEP)
RL Local Table
EP1 vPC Po1
Po1 Po2 EP2 vPC Po2
EP1 EP2
Remote Leaf Site

ACI Main DC

EP-to-EP Flow Local to RL Site (vPC)
EP info sync
over vPC
IP WAN IPN control plane
RL1 Local Table

EP1 vPC Po1
Po1 Po2
EP2 vPC Po2
EP1 EP2
‘Greedy Forwarding’ Remote Leaf Site

ACI Main DC vPC Po1 to Po2 on RL

EP-to-EP Flow Local to RL Site (vPC Link Failure)
IP WAN IPN
RL1 Local Table

EP1 vPC Po1
X
Po1 Po2
EP2 RL2 TEP
EP1 EP2
Remote Leaf Site

ACI Main DC

Communication between Endpoints in Separate RL Sites
RL Site1 RL Site 2
IP WAN
Traffic between
endpoints part of
separate RL sites
always flows through
the spines
ACI Main
| CiscoDC
19 - 21 March 2018 Connect | Rovinj, Croatia 36
ACI Remote Physical Leaf and Multi-Pod
RL Sites Can Be Associated to Separate Pods
RL Site 2
RL Site 1 associated
associated to Pod2
to Pod1
RL Site1 RL Site 2
Inter-Pod Network IP WAN
IP WAN
(Multicast Enabled)
ACI Main DC Pod1 ACI Main DC Pod2

ACI Remote Physical Leaf and Multi-Pod
RL Sites Can Be Associated to Separate Pods (Data Plane)
RL Site 1 RL Site 2
Inter-Pod Network IP WAN
IP WAN
(Multicast Enabled)
ACI Main DC Pod1 ACI Main DC Pod2

ACI Remote Physical Leaf and Multi-Site
RL Sites Can Be Associated to Separate Pods
RL Site 2
RL Site 1 Future ACI associated
associated to ACI Site 2
to ACI Site 1 Release
RL Site 1 RL Site 2
IP WAN
IP WAN Inter-Site Network
ACI Site 1 ACI Site 2

ACI Remote Virtual Leaf (vPod)
Cisco ACI Virtual Edge
Decoupled From Hypervisor Kernel API Dependencies
Q2
ACI Virtual Edge

FY18
ACI 3.1 Legacy AVS Cisco AVE (ACI 3.1 Release)
VM AVE
VM VM
VM VM VM
User
Space
AVE Policy Enforcement,
Services, Telemetry
Kernel Switching +
ACI Virtual Edge (AVE) AVS Native vSwitch
Space Policy Enforcement
VM VM VM VM VM VM VM
Hypervisor Dependent Hypervisor Agnostic
Maintain Existing Simple Transition/Migration Policy Consistency Across AVS/AVE

Operational Models AVS => AVE Multiple Hypervisors Feature Parity

Cisco ACI Virtual Pod (vPod)
Extend ACI To Bare-Metal Cloud
IP Network
Logical Connection To Spine

(BGP-EVPN/ VXLAN) Virtual Pod
vSpine
vLeaf vLeaf
ACI Virtual Edge
Hypervisor
Remote
On-Premise Location
VM VM VM VM VM VM VM VM VM VM VM VM VM VM
Bare Metal Clouds Remote Data Colo Facilities BrownField

(IBM BlueMix, AWS Elastic Metal etc.) Centers (Equinix, CoreSite etc.) Deployments

vPod Functional Components
vSpine, vLeaf, and AVE
vSpine + vLeaf vPod

• Run as container services inside VMs at the vPod vSpine + vLeaf
location (co-located for availability)
COOP BGP
• vLeaf: Distribute APIC policies to AVE forwarders DME/PE Oracle RR
(DME/PE)
• vSpine: Centralized endpoint and LPM database IP Network
(COOP and BGP)
iVXLAN Overlay
• Not in forwarding data path
AVE AVE
Hypervisor
AVE
Hypervisor
AVE
Hypervisor
• Implements ACI data path functions

• Use iVXLAN for communication within Remote site Web App DB
as well as between the vPod and other Pods

Scale Out
BGP EVPN Sessions between Pods
BGP BGP Infrastructure Services (Containers)

RR RR
COOP COOP COOP COOP COOP

Oracle Oracle Oracle Oracle Oracle
DME/PE DME/PE DME/PE DME/PE DME/PE

OPFlex OPFlex OPFlex OPFlex OPFlex
Citizen Citizen Citizen Citizen Citizen
Client Client Client Client Client
BGP BGP BGP BGP BGP
AVE AVE AVE AVE AVE
Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor
19 - 21 March 2018 254| AVE

Ciscoper logical
Connect vPod
| Rovinj, Croatia 44
Flow State and vMotion
BGP BGP Infrastructure Services (Containers)

RR RR

Oracle Oracle Oracle Oracle Oracle
DME/PE DME/PE DME/PE DME/PE DME/PE
State of Flow carried between AVE nodes during vMotion

OPFlex OPFlex OPFlex OPFlex OPFlex
Citizen Citizen Citizen Citizen Citizen
Client Client Client Client Client
BGP BGP BGP BGP BGP
AVE AVE AVE AVE AVE
Hypervisor Hypervisor Hypervisor Hypervisor Hypervisor

vPod
Inter-Pod Control Plane COOP BGP
DME/PE
BGP EVPN Peering Oracle RR
between ‘spines’
iVXLAN Overlay
AVE AVE AVE

Hypervisor Hypervisor Hypervisor
We
App DB
b
IP
Network
DME/PE COOP BGP

Oracle RR
AVE vSwitch vSwitch
iVXLAN Overlay
Web App DB AVE AVE AVE

We
App DB
b

vPod
Inter-Pod Data Plane
iVXLAN Overlay
AVE AVE AVE

iVXLAN Overlay
Web App DB
IP
Network
AVE vSwitch vSwitch

iVXLAN Overlay
Web App DB AVE AVE AVE

Web App DB

ACI Extensions to Multi-Cloud
ACI Extensions To Multi-Cloud
ACI Multi-Site
Orchestrator
Site A
Site C
“Cloud APIC (cAPIC)”
Site D
Site B
VM VM VM
VM VM VM
Consistent Network and Common Single Point of Secure Automated

Policy across clouds Governance Orchestration Connectivity
cAPIC and Policy Mapping
AWS Cloud Constructs
APIC
User Account Tenant

Virtual Private Network VRF
VPC subnet BD Subnet
Security Group EPG
Security Group Rule EPG Contracts
Outbound rule Consumed contracts

Source/Destination: Subnet or IP or Any or ‘Internet’
Protocol
Port
Inbound rule Provided contracts
EC2 Instance
Network Adapter
cAPIC and Policy Mapping
Azure Cloud Constructs
APIC
Resource Group Tenant
Virtual Network VRF
Subnet BD Subnet
Application Security Group EPG

(ASG)
Network Security Group

(NSG) EPG Contracts
Outbound rule Consumed contracts

Source/Destination: ASG or Subnet or IP or Any or ‘Internet’
Protocol
Port
Inbound rule Provided contracts
Virtual Machine
Network Adapter
ACI Anywhere
Where to Go for More Information
ü ACI Multi-Pod White Paper
http://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-
infrastructure/white-paper-c11-737855.html?cachemode=refresh
ü ACI Multi-Pod Configuration Paper
https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-
infrastructure/white-paper-c11-739714.html
ü ACI Multi-Site White Paper
https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-
infrastructure/white-paper-c11-739609.html
ü ACI Multi-Pod Cisco Live Barcelona 2018
https://www.ciscolive.com/global/on-demand-library/?search=weston#/session/BRKACI-2003
ü ACI Multi-Site Cisco Live Barcelona 2018
https://www.ciscolive.com/global/on-demand-library/?search=ardica#/session/BRKACI-2125
ü ACI Physical Remote Leaf White Paper
Coming soon!

ACI Anywhere Extending The ACI Fabric - Max Ardica

Uploaded by

Document Information

Original Description:

Original Title

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 Anywhere Extending The ACI Fabric - Max Ardica

Uploaded by

Copyright:

Available Formats

ACI Anywhere: Extending the ACI Fabric

§ ACI Network and Policy Domain Evolution

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 5

4,800+ 46+% 65+

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 6

ACI Single Pod Fabric ACI Multi-Site ACI Multi-Cloud

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 7

Amazon Web Services

Fabric ‘A’ (AZ 1)

Fabric ‘B’ (AZ 2)

Multi-Pod Fabric ‘A’ (AZ 1)

Pod ‘1.A’ Pod ‘2.A’

Multi-Pod Fabric ‘B’ (AZ 2)

Tenant ‘Prod’ Configuration/Change Domain Tenant ‘Dev’ Configuration/Change Domain

APIC Cluster APIC Cluster

3 (or more) DC Sites directly connected Multiple sites interconnected by a

POD 3 * 10G only 19

Scale-Up Model to Build a Large Data Center Interconnect (DCI)

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 17

VTEP IP VNID Class-ID Tenant Packet No Multicast Requirement in

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 18

VNID 16678781 16547722

VNID à 16547722 EP1

• Multi-Site Orchestrator instructs local APIC to program translation tables on spines

§ New 9364C non modular spine

Multi-Site from ACI 3.1 release

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 20

Site Site Site Site

MSO GUI MSO GUI MSO GUI

19 - 21 March 2018 | Cisco *’Live’

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 23

• Template is the scope/granularity of what EP1

can be pushed to sites

• Schema = container of Templates sharing a

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 24

• Multi-Site Infra: Unicast, Multicast, BGP TEPs

Spines VXLAN Spines

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 25

Extending ACI fabric policy and L2/L3 connectivity to a small DR site

Centralized Policy Management and Control Plane for remote locations

Small form factor solution at locations with space constraints

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 27

IPN Requirements (3.1)

Remote Leaf Site: a pair of Nexus 9300 nodes

ACI Main Pod Remote Leaf Nodes

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 29

IP WAN Only 2 RLs

Remote Leaf Site

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 30

Remote Leaf Site

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 31

Remote Leaf Site

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 32

Po1 Po2 EP2 vPC Po2

Remote Leaf Site

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 33

RL1 Local Table

‘Greedy Forwarding’ Remote Leaf Site

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 34

RL1 Local Table

Remote Leaf Site

19 - 21 March 2018 | Cisco Connect | Rovinj, Croatia 35