F5 and ACI Integration

F5 BIG-IP and Cisco ACI Integration
Network Service Orchestration and Insertion
Jeffrey Wong - Solution Architect

F5 Networks
February, 2015
Agenda
• State of IT
• ACI Overview
• F5 Synthesis Overview
• ACI L4 –L7 Service Insertion Overview
• F5 Device Package Release 1.1.0 Details and Integration with
Cisco ACI
• Workload Migration from Traditional Networks to Cisco ACI
• F5 BIG-IQ Integration with Cisco ACI
© F5 Networks, Inc 2
How Are We Doing?
How much IT will You need ?
But, need this?
Deploy this Much?
But, need this?
? Deploy this Much?
IT impedes growth or, IT spends too much
What if IT was On-Demand? Would that be “Cloud” ?
4
The on-going “IT pain”
• High cost, heterogeneous systems

• Redundant functionality
• Lack of agility to innovate
• Slow time to market
• Rising maintenance costs
• Rising regulatory and compliance costs,
multiplied by:
• Heterogeneous systems
• Geographic expansion / local laws
• Falling IT Budgets
5
What
Happen
ed
?
• Separation of IT areas / buying-
centers / silos preventing IT to
move at the speed demanded by
the business
• Focus changed from

Consolidation to Automation
• Business owners and Apps DevOps

Developers started to go straight
to public cloud to meet agility and
demand. Security and Data
Sovereignty arise.
• Operations become further

relevant. Shift from “what it does
/ how it works” to “how to use /
how to consume it”.
What is ACI?
Introducing: Application Centric Infrastructure (ACI)
Apps + Infrastructure
Open + Secure Physical + Virtual + Containers
On-Premises + Cloud
Application Oriented Policy = Operational Simplicity

Why Networks are Complex
Overloaded Network Constructs
ACI directly maps the application
connectivity requirements onto the
network and services fabric
Redirect and Load Balance Connectivity

Application Requirements
IP Address, VLAN, VRF

Dynamic provisioning of
Control & Audit Connectivity connectivity explicitly defined for
Application Requirements the application
(Security – Firewall, ACL, …)
IP Addressing
IP Address, VLAN, VRF
Application Specific Connectivity
Enable Connectivity
(The Network)
Network-Centric to application-centric
Two types of language
NETWORK LANGUAGE APPLICATION LANGUAGE
• VLAN • Application Tier Policy and

• IP Address Dependencies
• Subnets • Security Requirements
• Firewalls • Service Level Agreement
• Quality of Service • Application Performance
• Load Balancer • Compliance
• Access Lists • Geo Dependencies
• Etc.
Application Policy Model and Instantiation
Application
Client
Application policy model: Defines the
application requirements (application Storage Storage
network profile)
Web Tier App Tier DB Tier
Policy instantiation: Each device

dynamically instantiates the required APIC
changes based on the policies
VM VM VM VM VM VM VM
10.2.4.7 10.9.3.37 10.32.3.7
All forwarding in the fabric is managed through the application network profile
• IP addresses are fully portable anywhere within the fabric
• Security and forwarding are fully decoupled from any physical or virtual network attributes
• Devices autonomously update the state of the network based on configured policy requirements
ACI understands and speaks APPLICATION Needs
WEB APP DB
APPLICATION
WAN ADC from Web Connect to App
REQUIREMENTS
Firewall Connect to DB High Priority
NETWORK WEB APP DB

F/W
REQUIREMENTS ADC ADC
DIRECTLY MAP TO ACI NETWORK PROFILES

ACI BUILDING BLOCKS
ACI building blocks
FUTURE PROOF—SOFTWARE UPGRADABLE TO ACI
next generation nexus—TRADITIONAL NETWORKS
OPEN RESTFUL APIS
CENTRALIZED POLICY MODEL
OPEN SOURCE
APIC
CONTROLLER NEXUS
POLICY 9500 and 9300
MODEL
INNOVATIONS IN SOFTWARE HARDWARE AND SYSTEM DESIGN
PRICE PERFORMANCE PORT DENSITY PROGRAMMABILITY POWER EFFICIENCY
OPTIMIZED NX-OS
ACI
>_
>_
RESILIENCY: 50% SIMPLER FUTURE PROOF NETWORK PROGRAMMABILITY

IN SERVICE PATCHING, CODE BASE UPGRADABLE VIRTUALIZATION AND AUTOMATION
UPGRADE, FAST RESTART TO ACI SUPPORT
F5 Synthesis Overview
Impact on Data Center Architecture: Applications
MICRO-ARCHITECTURES API DOMINANCE
Each service is isolated and requires its own: Proxies are used in emerging API-centric architecture
• Load balancing • API versioning
• Authentication / authorization • Client-based steering
• Security • API Load balancing
• Layer 7 Services • Metering & billing
• May be API-based, expanding services required • API key management
More applications needing services More intelligence needed in services
Service A Service C API v1
Service B Service D API v2
High-Performance Services Fabric
Programmability (iRules / iApps / iControl)
Data Plane Control Plane Management Plane
Virtual Edition Appliance Chassis
Network [Physical • Overlay • SDN]

F5 and Cisco ACI Joint Solution Benefits
F5 DEVICE PACKAGE
• Automated L4-L7 FOR APIC • Preserves richness
application service of F5 Synthesis offering.
insertion Ease of integration due to
rich programmability
• Accelerated • Existing F5 Physical and

application Virtual appliances,
deployments with ACI Fabric topologies integrate
scalableL4-L7 seamlessly with Cisco
services ACI
Programmability (iRules / iApps / iControl)
Data Plane Control Plane Management Plane
• Application agility & • Maintains operational best
F5 Synthesis Fabric
significant reduction in practices & offers faster
operating costs provisioning of workflows
F5 and Cisco ACI Integration – Latest Addition
Announcing APIC and BIG-IQ Integration Early Availability
BIG-IQ
F5 Synthesis Fabric
ACI Fabric
BIG-IP
APIC to BIG-IP Integration Model Phase 1

(Shipping)
APIC to BIG-IQ Integration Model Phase 2
(Early Availability Now, FCS Q2 CY15)
Customers have choice to leverage Cisco APIC to BIG-IP or through BIG-IQ Integration Models
Choosing F5 BIG-IP for Cisco ACI
Supports 11.4.1 and above, Platform Independent
Good, Better, Best Platforms
VIPRION 2200 VIPRION 2400

25M 200M 1Gbps 3Gbps 5Gbps 10Gbps
1600 series* 2000 series* 4000 series 5000 Series 7000 Series 10000 Series 11000 Series VIPRION 4480 VIPRION 4800
Virtual Physical Hybrid

F5 virtual editions F5 physical ADCs Physical + virtual =
Provide flexible deployment options for High-performance with specialized and hybrid ADC infrastructure
virtual environments and the cloud dedicated hardware Ultimate flexibility and performance
Virtual ADC is best for: Physical ADC is best for: Hybrid ADC is best for:
• Accelerated deployment • Fastest performance • Transitioning from physical to
• Maximizing data center efficiency • Highest scale virtual and private data center to
• Private and public cloud deployments • SSL offload, compression, and DoS mitigation cloud
• Application or tenant-based pods • An all F5 solution: integrated HW+SW • Cloud bursting
• Keeping security close to the app • Edge and front door services • Splitting large workloads
• Lab, test, and QA deployments • Purpose-built isolation for application delivery • Tiered levels of service
workloads 20
© F5 Networks, Inc
ACI L4 –L7 Service Insertion
Overview
Traditional Network Service Insertion
Challenges
Configure Network to
Router insert Firewall
Configure firewall
network parameters Service insertion
FW
takes days
Configure firewall rules as
required by the application
Network configuration
Router is time consuming
and error prone
LB Configure Load Balancer
Network Parameters
Difficult to track
Switch configuration on
Configure Router to steer
vFW services
traffic to/from Load Balancer
Server
Configure Load Balancer as
Service Insertion In traditional Networks required by the application
APIC L4 – L7 Service Integration
Traditional F/W
3-Tier WEB ADC APP DB
ADC WEB WEB WEB APP APP APP DB DB DB
Application
TENANT (HR)
APPLICATION
NETWORK PROFILE
endpoint Group (EPG) – collection of bare metal servers, VMs, vNIC

APPLICATION PROFILE (3 TIER APP)
Ex: WEB EPG - all web servers (bare metal or VMs) are grouped into this EPG
EPGS ARE DEFINED HERE
Ex: APP EPG - all APP servers (bare metal or VMs) are grouped into this EPG
NETWORKING POLICY
CONNECTIVITY FOR THE TENANT L2-L3
SECURITY POLICY Contract – services between the WEB and APP EPG (web graph, HTTP graph)
(POLICY DECISION IS DONE HERE) Ex: APP is a provider and WEB is the consumer
FILTERS, QOS, TRAFFIC STEERING Define services within a contract: FW, ADC in this example ADC defined
TROUBLESHOOTING POLICY
SPAN, ERSPAN ETC
MONITORING POLICY
EVENTS, SNMP
L4-L7 SERVICES POLICY Service Graph (Ex: WEB graph utilizes L7 SLB)
DEFINE L4-L7 SERVICE POLICY Logical Device Cluster
F5 Device Package: Definition
APIC requires a Device Package to communicate with service
devices.
A Device Package is a zip file containing two parts:
Device Specification (xml): The configuration of DeviceScript (py): The integration between
the APIC is represented as an object model the APIC and a Device is performed by a
consisting of a large number of Managed Objects DeviceScript, which maps APIC events
(MOs). A Device type is defined by a tree of MOs function calls defined in Device Script
with a Meta Device (MDev) at the root. Device Script
iControl /
EPG level L4-L7 config SouthBound
Configuration
through UI or Python API
APIC
North Bound Service Graph Function Device BIG-IP
APIs Node level L4-L7 config Package Physical or VE
Device Specification
<dev type= “f5”>
<service type= “slb”>
<param name= “vip”>
<dev ident=“210.1.1.1”
<validator=“ip”
<hidden=“no”>
<locked=“yes”>
Service Graph: Definition
Abstract graph concept mapping to Service Graph
Functions rendered on the same device
Consumes Service Graph: “web-application” Provides
EXT WEB
Func: Func: Func:
EXT EXT EXT Firewall SSL offload Load Balancing WEB WEB WEB
EPG - EXT EPG - WEB

Terminals Connectors Terminals
Firewall params SSL params Load-Balancing params
Permit ip tcp * dest-ip <vip> dest-port 80 Ipaddress <vip> port 80 virtual-ip <vip> port 80
Deny ip udp * Lb-aglorithm: round-robin
• Service graph is an ordered set of functions between • A function within a graph may require one or more
a set of terminals e-g; Firewall Function, Load balancer parameters
Function • Parameters can be scoped by an EPG or an application
profile or tenant context
• A function has one or more connectors • Parameter values can be locked from further changes
• Network connectivity like VLAN/VNID tag is assigned
to these connectors
F5 Service Insertion
Web Farm provide services to External Users;
Consume Provide Policy Contract defines relationship between
Web Farm and Users
EPG EXT EPG WEB Users assign to EPG EXT

Ext Web Web Farm assign to EPG WEB
Users Server Users accessing the Web Servers
start
stage
1 ….. stage
N
end
graph Service Graph Insertion at the
Policy Contract Subject level
Application
Construct
inst inst
…
Node Service Graph contains Function Nodes,

inst …. inst Virtual Server is a Function Node
firewall ADC: Virtual Server
Logical Device Cluster F5 BIG-IPs are Concrete Devices belong to a

Logical Device Cluster that enables ADC as a
Concrete Device Concrete Device Function Node within a Service Graph
F5 Device Package Release 1.1.0
Details and Integration Cisco ACI
F5 and Cisco ACI Integration Models
BIG-IQ
F5 Synthesis Fabric
ACI Fabric
BIG-IP
APIC to BIG-IP Integration Model
APIC to BIG-IQ Integration Model
F5 ACI Device Package 1.1.0 is now Released!
Supports ACI FCS+3 version 1.0(2m)
• vCMP support (New with 1.1.0)
• Dynamic endpoint attach and detach (New with 1.1.0)
• Supports any BIG-IP LTM physical and virtual form factor running version 11.4.1 and
above
• Device package can be downloaded from downloads.f5.com at no cost
• Does not require any new module installation on the BIG-IP
• Can leverage BIG-IQ as device management
• iRules (custom defined) that reside in common partition can be called by APIC
• BIG-IP is licensed and OOB management configured prior to APIC integration
• Supports Active / Standby High Availability model per APIC logical device cluster
F5 Device Package 1.1.0 Supported Functions
ce Package 1.1.0 continue to support the same L4 – L7 service functions as 1.0.0 with additional support of vCMP and dynamic endpoint attach/de
Parameters under Virtual Server

Functions • Configuring Global and Tenant Self IP addresses
• Configuring Global and Tenant static routes
• Device Counters
• Virtual Server • Server Pools
 Layer 4 Server Load balancing • TCP Optimizations (WAN/LAN/Mobile)
 Layer 4 SLB with SSL offload • HTTP optimization
 Layer 7 Server Load balancing • HTTP Security (Application protocol security)
 Layer 7 SLB with SSL offload • TCP connection multiplexing (One Connect)
• Microsoft SharePoint • Validators and Creation of tenant OneConnect
profiles
• iRules
• Validators and Creation of tenant acceleration
profiles
• SNAT Pool management
More than 80% of F5 customers use the L4 SLB / L7 SLB / MSFT SharePoint / SSL offload hence 1st release targets these use cases
F5 Device Package 1.1.0: vCMP Guests Support
vCMP (Virtual Clustered Multiprocessing) is F5 purposed built hypervisor, allow
multiple virtual ADC instances, called vCMP guests, reside on the same vCMP host
In release 1.1.0; in vCMP
HA configuration, both
vCMP guests must reside
on the same vCMP host
Using vCMP guests as

L4-L7 Devices when
creating Logical Device
Cluster
vCMP guest 1 and 2

mgmt. IP
vCMP host mgmt.

IP
F5 Device Package 1.1.0: Dynamic endpoint attach/detach
Pool members, which consider endpoint in ACI fabric, once “attached to” OR
“detach from” an EPG; APIC will send notification to BIG-IP to add or remove this
pool member
Internal Connector, which

tied to the provider EPG,
assign to the WEB servers =
pool members in F5 LTM
Pool
Eable Attachement
Notification
Under Graph Template,

function node ADC has
two logical interfaces:
external and internal
No need to define pool

members when adding
configurable parameters to
the service graph template
vCMP host mgmt. IP under

device config as well
BIG-IP Pool has no

pool members
After receiving attach

Assign provider notification from APIC, BIG-
EPG (Web) to IP add members to pool
the servers Same for endpoint detach
Terminology: APIC Tenant Single Context / BIG-IP Partition
Tenant is a container for
policies (filters, contracts,
bridge domains and
application profiles)
BIG-IP partition is
equivalent to a single
context ACI tenant
A function node identifies a set of

network service functions that
are required by an application
BIG-IP Virtual Server is

equivalent to service graph
function node
Device Package Feature: Referencing iRules
APIC can reference

iRules that resides in
BIG-IP Common
partition
BIG-IP is responsible for

iRules management,
including creation /
modification / validation
F5 supports TRUE Multiple Graph Multiple Tenancy
• Multiple Virtual Servers for different
applications in the different BIG-IP
partitions/APIC Tenants, sharing the Tenant N APIC partition:
apic7890
same device Route Domain N
• Partition created by APIC inside BIG-IP Tenant B

App
EPG 1
is prefixed by the apic,”_” tenant-id to
Virtual
APIC partition:
Server 1
apic2345
Client EPG Route Domain B
represent the partition in F5 (for ex :
apic_5437) App App
Tenant A VirtualVirtual
APIC partition:
EPG 1EPG 2
ServerServer 2
• F5 demonstrate true multi-tenancy Client EPG
apic1234
Route Domain A
1
using different partitions for each tenant

in APIC Virtual
App
App EPG 1
EPG 2
Virtual Server 1
Server 2
• Each partition has been assigned Client EPG
individual route domain for L3

separation Virtual Server 2 App EPG 2
• Virtual Servers created by APIC inside

BIG-IP is prefixed by the apic,”_” Single BIG-IP physical
tenant_id”_”graph (for ex :
apic_5437_3456)
F5 BIG-IP + Cisco ACI Integration Options
ACI Fabric ACI Fabric ACI Fabric
Contract with L4-L7
Contract Service Insertion
Contract with L4-L7
Contract Contract Service Insertion
Ext Web Ext Web
EPG EPG EPG EPG
BIG-IP
EPG BIG-IP phy
link to ACI
BIG-IP phy fabric
link to ACI No BIG-IP
fabric EPG required
Common or BIG-IP Common or APIC

APIC
partition BIG-IP partition
partition
partition
Mixed Mode: same BIG-IP

Cisco ACI + F5 BIG-IP Integration
Cisco ACI + F5 BIG-IP without connects to ACI fabric with
using L4 – L7 service insertion
service insertion (using EPG) and without L4-L7 service
using service graph
insertion
All the above Integration Options support 1-Arm / Inline; Physical / Virtual in HA
deployment
Workload Migration from
Traditional Networks to Cisco ACI
Migration: Physical Topology
Traditional Network F5 DEVICE PACKAGE
FOR APIC
BIG-IP Platform
CISCO ACE
ACI Fabric
VIP Traditional VIP ACI BIG-IP PlatformBIG-IP Platform
A B C
WEB
Migration: Approach
VIP Traditional ACI VIP
Clients Step 1:
access A B C • Bring up BIG-IP in ACI fabric
Traditional • Create Application Server
WEB
Network VIP
• ACI L4-L7 service insertion with BIG-IP
Expanding
A B ACI C Step 2:
workload to VIP
ACI fabric • Add ACI VIP to Traditional Pool
WEB

Moving
workload from ACI C A B Step 3:
traditional VIP
• Move Servers
network to WEB
ACI
Completing VIP Traditional ACI VIP

workload A B
Step 4:
C
migration to ACI • Update DNS or GTM
WEB
Clients now • Remove ACI VIP From Traditional Pool
access ACI VIP
Migration: Logical Diagram
Server Pool Server Pool
Server Server
(Node) (Node)
2 Traditional 3 5
ACI
Client Network Server Server
VIP
VIP (Node) (Node)
4
1
Server
(LTM #2 VIP)
DNS
Wiki.mycorp.com = Traditional VIP

Server Pool
Server
(Node)
2 3
ACI
Client Server
VIP (Node)
1
Server
(Node)
DNS
Wiki.mycorp.com = ACI VIP
F5 & Cisco Joint Whitepaper:

http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/guide-c07-733816.pdf
F5 BIG-IQ Integration with Cisco ACI
F5 and Cisco ACI Integration Models
BIG-IQ
F5 Synthesis Fabric
ACI Fabric
BIG-IP
APIC to BIG-IP Integration Model
APIC to BIG-IQ Integration Model
F5 is Industry Leader in Application Delivery
How can we provide full set of F5 functionality to ACI
environment that is “application” focused?
F5 has an
extensive
library of iApps
for deploying
applications
What are iApps?
An iApps is an application-centric configuration template:

• User answers a few questions about deploying an application
• iApps translates answers into a set of configuration options
• iApps can touch almost all BIG-IP functionality
• iRules, profiles, monitors, security policies, and much more …
• There are many F5-provided iApps:
• HTTP, Sharepoint, Exchange, VMware View, …
• Users can build their own iApps
Using BIG-IQ to bring iApps to APIC
F5 Device Package Release
BIG-IQ Integration with Cisco ACI
1.1.0 Deployment Model
1 Device
Device
Package
Package 2 3 BIG-IQ
BIG-IQ
Device
Device
2
downloads.f5.com F5 iApps
Device Package
Package
F5 Synthesis Fabric
Config
Configuration
{'state': 1,
{'state': 1, 'transaction':
'transaction': 0,
0,
'ackedState': 0,
'ackedState': 0, 'value':
'value': {(5,
'DestinationNetmask',
'DestinationNetmask',
{(5, 4a
'Netmask1'): {'state':
'Netmask1'): {'state': 1,
1,
'transaction': 0,
'transaction': 0,
'ackedState': 0,
'value':
'255.255.255.255'}, (5,
'255.255.255.255'}, (5,
4b
1
'DestinationPort', 'port1'):
'DestinationPort', 'port1'):
{'state': 1,
{'state': 1, 'transaction':
'transaction': 0,
0,
'ackedState': 0,
'value': '80'
'80'
ACI Fabric Virtual Edition Appliance Chassis
BIG-IQ integration with APIC

BIG-IP integration with APIC 1 - BIG-IP expose iApps to BIG-IQ
1 - Download device package from F5 2 - BIG-IQ create custom device package
2 - Admin import device package to APIC 3 - Admin import BIG-IQ device package to APIC
3 - APIC sends config to BIG-IP directly 4a - APIC sends iApp config to BIG-IQ -> BIG-IP
4b - APIC sends Device config to BIG-IP
Reference Material i For Your
Reference
• F5 and Cisco ACI Solution Overview

http://www.f5.com/pdf/solution-center/cisco-aci-overview.pdf
• F5 SDAS and Cisco ACI Solution Brief

http://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/unified-fabric/solution-brief-c22-730004.html
• Cisco Application Policy Infrastructure Controller (APIC)

http://www.cisco.com/c/en/us/products/cloud-systems-management/application-policy-infrastructure-controller-
apic/index.html
• F5 BIG-IP LTM and Cisco ACI Integration white paper

http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/white-
paper-c11-732413.pdf
• Cisco Validated Design (CVD) on F5 BIG-IP LTM and Nexus 9000 (Standalone)
http://www.cisco.com/c/dam/en/us/td/docs/solutions/Enterprise/Data_Center/VMDC/BIG-IP-LTM/CiscoVMDCwithF5_BIG-
IP_LTM_WhitePaper.pdf
• F5 BIG-IP: Workload Migration from Traditional Networks to Cisco Application Centric Infrastructure
http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/guide-
c07-733816.pdf
• Follow us on Twitter @f5Networks  Official F5 Networks Channel
DevCentral F5 User Community
Over 180,000 Members in 191 Countries and Growing!
References
• Wikis
• API/SDK Documentation
Resources
• Sample Code
• Tech Tips
• Forums
• Podcasts
• Blogs
Tools and Frameworks

• iRule Editor
• iControl SDK
• .NET, Java, Python,
Powershell, ...
• VMware vSphere Management
Plug-in
• Microsoft SCOM Monitoring Pack
Key Takeaways
• F5 Software Defined Application Services (SDAS) vision perfectly aligns with Cisco’s Application
Centric Infrastructure
• How Cisco ACI solves network services insertion challenges
• How F5 BIG-IP LTM integrates into Cisco ACI architecture
• Key benefits of BIG-IP / ACI model:
 Multi-Tenancy, Multi-Graph Support
 Use Case Focus
 Automation Ready
 Application level visibility and monitoring
• F5 iApps Integration with Cisco ACI using BIG-IQ bringing application requirements to ACI policy
If I can be of further assistance please contact me:
Jeffrey Wong (j.wong@f5.com)

Visit F5 at Cisco Live 2015 in Melbourne
• Date: 18 – 20 March
• Booth: Stand P1
• You can also attend one of our Theatre sessions to learn more:
• Wednesday 18 Mar 11:50 AM - 12:20 PM – Partner Theatre 1
• Thursday 19 Mar 12:20 PM - 12:50 PM – Partner Theatre 2

F5 and ACI Integration

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

F5 and ACI Integration

Transféré par

Droits d'auteur :

Formats disponibles

F5 BIG-IP and Cisco ACI Integration

Network Service Orchestration and Insertion

Jeffrey Wong - Solution Architect

Deploy this Much?

But, need this?

? Deploy this Much?

IT impedes growth or, IT spends too much

What if IT was On-Demand? Would that be “Cloud” ?

• High cost, heterogeneous systems

• Focus changed from

• Business owners and Apps DevOps

• Operations become further

Open + Secure Physical + Virtual + Containers

Application Oriented Policy = Operational Simplicity

Redirect and Load Balance Connectivity

IP Address, VLAN, VRF

• VLAN • Application Tier Policy and

Policy instantiation: Each device

10.2.4.7 10.9.3.37 10.32.3.7

NETWORK WEB APP DB

DIRECTLY MAP TO ACI NETWORK PROFILES

RESILIENCY: 50% SIMPLER FUTURE PROOF NETWORK PROGRAMMABILITY

Service A Service C API v1

Service B Service D API v2

Programmability (iRules / iApps / iControl)

Data Plane Control Plane Management Plane

Virtual Edition Appliance Chassis

Network [Physical • Overlay • SDN]

• Accelerated • Existing F5 Physical and

APIC to BIG-IP Integration Model Phase 1

VIPRION 2200 VIPRION 2400

Virtual Physical Hybrid

endpoint Group (EPG) – collection of bare metal servers, VMs, vNIC

EPG - EXT EPG - WEB

EPG EXT EPG WEB Users assign to EPG EXT

Node Service Graph contains Function Nodes,

Logical Device Cluster F5 BIG-IPs are Concrete Devices belong to a

APIC to BIG-IP Integration Model

APIC to BIG-IQ Integration Model

Parameters under Virtual Server

Using vCMP guests as

vCMP guest 1 and 2

vCMP host mgmt.

Internal Connector, which

Under Graph Template,

No need to define pool

vCMP host mgmt. IP under

BIG-IP Pool has no

After receiving attach

A function node identifies a set of

BIG-IP Virtual Server is

APIC can reference

BIG-IP is responsible for

• Partition created by APIC inside BIG-IP Tenant B

using different partitions for each tenant

• Each partition has been assigned Client EPG

individual route domain for L3

• Virtual Servers created by APIC inside

Common or BIG-IP Common or APIC

Mixed Mode: same BIG-IP

VIP Traditional VIP ACI BIG-IP PlatformBIG-IP Platform

VIP Traditional ACI VIP

Completing VIP Traditional ACI VIP

Wiki.mycorp.com = Traditional VIP