Implementing Seamless Workload Mobility across Data Center (using OTV) - Session from Tuesday - 6

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public

Implementing Seamless Workload

Mobility across Datacenter (using

OTV)

Prab Kalra


Distributed Data Centers

Building the Data Center Cloud

Distributed Data Center Goals

• Seamless workload mobility

• Distributed applications

• Pool and maximize global resources

• Business Continuity

Interconnect Challenges

• Complex operations

• Transport dependent

• Bandwidth management

• Failure containment Geographically Disperse Data

Centers


Many physical sites - One logical Data

Center

Layer 2 Ethernet Extension

Introducing Overlay Transport Virtualization Simplifying Data Center Interconnect

Ethernet LAN Extension over any Network

• Ethernet in IP “MAC routing”

• Multi -datacenter scalability

Simplified Configuration & Operation

• Seamless overlay - No network re-design

• Single touch site configuration

• Provisioning Automation

High Resiliency

• Failure domain isolation

• Seamless Multi-homing

Maximizes available bandwidth

• Automated multi-pathing

• Optimal multicast replication Any Workload, Anytime, AnywhereUnleashing the full potential of compute virtualization

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 5

Applications that Benefit

from OTV Ethernet LAN Extensions

Cluster (Local)

vMotion

MSCS (with all your back office on it)

Veritas Cluster Server (Local)

Solaris Sun Cluster

Enterprise

RAC (Real Appl.Cluster)

HACMP

Legato Automated Availability Mgr

Metro Cluster

Metrocluster

BACnet (building automation/control - http://www.bacnet.org/)

http://www.bacnet.org/


End of Row

Middle of Row• Clusters and vMotion operate well within

L2

• Build larger L2 networks for improved

access layer load balance

L2L2

L3

ClustersV-Motion

V-Motion Clusters

Cisco OTV: Intra Data Center Layer 2 NetworkingvMotion and Clustering – Bound by L2


End of Row


L2



L2L2

L3

ClustersV-Motion

V-Motion Clusters



End of Row


L2



L2L2

L3

ClustersV-Motion

V-Motion Clusters



End of Row


L2



L2L2

L3

V-Motion

V-Motion



End of Row


L2



L2L2

L3

V-Motion

V-Motion



Access Pod 1

• Clusters, vMotion require L2 extensions

to go across access pods

• Improves Manageability

• Dynamic Annexation

• Portability & Expansion

L2

L2

L3

Access Pod 2

Cisco OTV: Intra Data Center Layer 2 NetworkingUnbinding vMotion and Clustering


Access Pod 1






L2

L2

L3

Access Pod 2



Access Pod 1






L2

L2

L3

Access Pod 2



Access Pod 1






L2

L2

L3

Access Pod 2



Access Pod 1






L2

L2

L3

Access Pod 2



Access Pod 1






L2

L2

L3

Access Pod 2



Access Pod 1






L2

L2

L3

Access Pod 2



Access Pod 1






L2

L2

L3

Access Pod 2



Access Pod 1






L2

L2

L3

Access Pod 2



Cisco OTV: vMotion Across Data CentersLive migration of VMs from one data center to another

Data Center A Data Center BEthernet Extension

Any Transport

Long Distance vMotion

This represents a significant advancement for virtualized environments by simplifying and accelerating long-distance workload migrations.

Ben Matheson, Senior Director, Global Partner Marketing, VMware

Nexus7000

Nexus7000

OTV


Cisco OTV: Data Center InterconnectActive/Active and Disaster Recovery

L2

L3

DR

IP

Main CampusRemote Site< 80 KM

Disaster Recovery> 80 KM



L2

L3

DR

IP





L2

L3

DR

IP





L2

L3

DR

IP





L2

L3

DR

IP





L2

L3

DR

IP





L2

L3

DR

IP





L2

L3

DR

IP





L2

L3

DR

IP





L2

L3

DR

IP





L2

L3

DR

IP




Ease of Provisioning: Data Center Growth Constraints

Problem Primary data center maxed out (space, cooling and power)

Requirement Seamlessly extend clusters and workload across data centers

Challenge Rapidly establish DCI between data centers

• No new transport provisioning required (Dark fiber, MPLS, etc)• Eliminate months of re-design effort • Significant operations and provisioning cost savings (no new protocols )

Solution: OTV – Establish DCI in 5 minutes!

Deploy over existing Network

4 configuration commands per site

No Re-design Required

Ethernet Overlay

One Logical Data Center

Automatic Fault Isolation


OTV at a Technical Glance

• Ethernet traffic between sites is encapsulated in IP: “MAC in IP”

• Dynamic encapsulation based on MAC routing table

• No Pseudo-Wire or Tunnel state maintained

Communication between

MAC1 (site 1) and MAC2 (site 2)EastSite

WestSite

OTV OTV

MAC IF

MAC1 Eth1

MAC2 IP B

MAC3 IP B

IP A IP B

Encap Un-Encap

MAC1 MAC2IP A IP B MAC1 MAC2

MAC1 MAC2

MAC IF

MAC1 IP A

MAC2 Eth 1

MAC3 Eth 2

IP packet Ethernet Frame


Fabric Scalability beyond the POD

Common Infrastructure for flexible deployment models

Complimentary Innovations:• FabricPath: Scalable Fabrics for Application Deployment Flexibility

• OTV : Layer 2 extensions over Layer 3 for Distributed Clustered Applications

• Optimized routing and segmentation within the flexible Fabric

Data Center Interconnect ExtensionOverlay Transport Virtualization

Scalable PodvPC & FEXLink

Classical PodSpanning Tree Protocol

Highly Scalable PodFabricPath


Cisco Overlay Transport Technology

• Simple Configuration

• Ease of Operation

• Automated Multi-homing

• Site Independence

Simplifying & Advancing Data Center Interconnects

35

Date post:	07-Jul-2015
Category:	Technology
Upload:	cisco-data-center-sdn
View:	460 times
Download:	3 times