BRKDCT 3060 Dc Interconnect

8/12/2019 BRKDCT 3060 Dc Interconnect

1/63


2/63

2012 Cisco and/or its affiliates. All rights reserved.BRKDCT-3060 Cisco Public

Deployment Considerationswith Interconnecting Data Centers

BRKDCT-3060

Hernan Vukovic - Consulting Systems Engineer

!


3/63


The main goals of this session are:

! Highlighting the main business requirements drivingData Center Interconnect (DCI) deployments

! Understand the functional components of the holisticCisco DCI solutions

! Get a knowledge of Cisco LAN and SAN extensiontechnologies and associated deployment

considerations

Session Objectives


4/63


Agenda

! Distributed Data Center & Cloud evolution overview! Data Center Interconnect Design Considerations

! Storage Extension! LAN Extension

Ethernet Based

IP Based

! Network Services and Applications! Conclusions


5/63


DCI

Drivers Business Solution Constraints IT Technology

Business

Continuity

"Disaster Recovery"HA Framework

"Stateless"Network Service Sync"Process Sync

"GSLB"Geo-clusters"HA Cluster

Operation Cost

Containment

"Data Center Maintenance /Migration / Consolidation

"Host Mobility "Distributed VirtualData Center

Business

Resource

Optimization

"Disaster Avoidance"Workload Mobility

"VLAN Extension"Statefulness"Bandwidth & Latency "VM Mobility

Cloud Services "Inter-Cloud Networking"XaaS

"Flexibility"Application mobility "VM Mobility"Automation

! Data Centers are extending beyond traditionalboundaries

! Virtualization applications are driving DCI across PODs(aggregation blocks) and Data Centers

Data Center InterconnectBusiness Drivers


6/63


DCI Function Purpose

Storage Extensions Providing applications access to storage locally, as well as remotely with desirable storage attributes

LAN Extensions Extend same VLAN across Data Centers, to virtualize servers and applications

Inter-DC Routing Provide routed connectivity between data centers (used for L3 segmentation/virtualization, etc.)

Path Optimization Routing users to the data center where the application resides while keeping symmetrical routing inconsideration for IP services (e.g. Firewall)

!"#" %&'#&( )'#&(*+''&*# ,!%)-#$%&'$( )$*+$(,(-.

./(#0"1/2"3+'4551/*"3+'67489:#&'6/+'

6

;#+("+

03'


7/63


DC 1 DC 2

ESX-A source ESX-B target

!"#" %&'#&( )'#&(*+''&*##/0 12-,(.3$(

! #4(567$($&. 3*+%3,. .-735- 83.-9(5, %3*3-9'$(! :$59%3;9'$( $< /5'=, #-$79>, 3. ?,4#@3.-9(5, 59( A, 3*+7$=,8 &.3(> BC 955,%,79-$7 $7 59563(>#D37-&9% :E0 3. 9%%$F3(> /5'=,G/5'=,


8/63

2012 Cisco and/or its affiliates. All rights reserved.BRKDCT-3060 Cisco Public H

@)I @)! @)J

#KL

8$*93(

#KL

8$*93(#KL

8$*93(

SiSiSiSi SiSi SiSi

ALT GW ALT ALTGWGW

L9-6 C+'*3;9'$(

@&9%MN$*3(>

#-$79>, ,2-,(.3$(

/(4 -4+, $< %3(?.

#KL @$*93( 3.$%9'$( O #-$7*M5$(-7$%

Data Center InterconnectLAN Extension Model


9/63


Ethernet

MPLS

IP

Over dark fiber or protected D-WDM

$VSS & vPC! Dual site interconnection

$FabricPath (TRILL)MPLS Transport

$ EoMPLS! Transparent point to point

$A-VPLS! Enterprise style MPLS

$ H-VPLS! Large scale & Multi-tenants

IP Transport$ OTV

! Enterprise style Inter-site MAC Routing$ VXLAN

! Intra-site MAC bridging in total virtualized context

LAN Extension for DCITechnology Selection Criteria


10/63


DC 1 DC 2


!"#" %&'#&( )'#&(*+''&*#L9-6 C+'*3;9'$( A53+'6

! 1>7,..#/887,..,8 A4 PNQL P3%-,73(>

! B(>7,..RIS @0# 7,837,5'$( F3-6 /)1GT##!S Q$&-, N,9%-6 B(U,5'$( VQNBWJS :B#L


11/63


! K4+359%%4 /5'=,G#-9(8A4 )%&.-,7 6 +73=9-, (,-F$7? 9. F,%% 9. DBL 5%&.-,7 -67$&>6 -6, +&A%35 (,-F$7?.

Q,[&37,. :94,7 ! +9-6 A,-F,,( 6$.-.

! )%3,(- 7,5$((,5'$( -79(.+97,(- M .697,8 BL 9887,..%:94,7 ! *&.- A, \,2-,(8,8]

Cluster Application such as

! Microsoft MSCS! VMware Cluster! Veritas Cluster! Oracle RAC! .

!(/@&( B C06/'&66 %+'3'0"'*&N3>6 /=93%9A3%3-4 )%&.-,7. M :$59%

Heartbeat 1

SAN A

SAN B

Cluster VIP

EnterpriseCore

Active Standby

Heartbeat 2

Extended LAN

Extended SAN


12/63


! D^9563(, +7$5,.. *3>79'$( 3(57,9.,. 9++%359'$( 9=93%9A3%3-4! :/0 Z #/0 7,[&37, :94,7 ! +9-6 -$ *93(-93( &.,7 .,..3$(. 8&73(> *3>79'$(

DC 1 DC/POD

ESXi-A source ESXi-B target

D+(E1+"? F+G/1/#H I+( !/6"6#&( 4@+/?"'*&@4(9*35 ^$=,*,(- $< D37-&9% ^9563(,.GD^.


13/63


Agenda



Ethernet Based

IP Based



14/63


Business Continuity / Disaster Recovery Options

! Offsite tape vaulting! Backup tapes transported to offsite

location by truck

! Electronic vaulting! Transmission of backup data to offsite

location

! Remote disk replication! Continuous copying of data to offsite

location

! Cold site! Transfer data from offsite location to

new data center

! Duplicated hot site! Replicate data remotely, ready for

operational resumption

!Application sensitivity to delay! Synchronous vs. asynchronous

! Distance requirements! Propagation delays , at least 5 sper Km.

! Service availability at a customersite

! Tag onto existing facilities or newinstall

! Bandwidth requirements! Total cost of ownership

!Equipment Cost v/s Cost ofdowntime


15/63


@,.3>( K,56($%$>4 #$%&'$(. K69- _9%9(5,R

/++%359'$( G L7$5,.. Q,5$=,74 CAU,5'=,. VQLC 9(8 QKCW @3.-9(5, ` a69- 3. 4$&7 \K7,9- Q983&.]b @9-9G#-$79>, )9+953-4 9(8 _9(8F38-6 7,[&37,*,(-. /++%359'$( L,7


16/63


RTO / RPO


17/63


! Synchronous Data replication: The Application receives the acknowledgement for I/O complete when bothprimary and remote disks are updated. This is also known as Zero data loss data replication method (or Zero

RPO)

! Metro Distances (depending on the Application can be 50-300kms max)! Asynchronous Data replication: The Application receives the acknowledgement for I/O complete as soon as

the primary disk is updated while the copy continues to the remote disk.

! Unlimited distances

J

K

L

M J

L

K

SynchronousData Replication

AsynchronousData Replication

;48 9:#&'6/+'#4(567$($&. =.S /.4(567$($&. @9-9 Q,+%359'$(


18/63


7/N/#&? GH A53*6 ,=+O&( C0?&


19/63


! Speed of Light is about 300000 Km/s! Speed is reduced to 200000 Km/s#5 s per Km! That gives us an average of 1ms for the light to cross 200 Kms of fiber! Synchronous Replication: SCSI protocol (FC) takes a four round trips! For each Write cmd a two round trips is about 10 s per kilometer

#20s/km for 4 round trips for Synch data replication

1

2

1

2:$59% #-$79>, /7794 Q,*$-, #-$79>, /7794

!de f. R Q,5gQ,984 b

!de f. R a93-


20/63


Extending Optical SAN ExtensionFibreChannel Frame Buffering

Buffer to buffer credits (BB_Credit) are negotiated between each device in aFC fabric; no concept of end to end buffering

One buffer used per FC frame, irregardless of frame size; small FC frame uses samebuffer as large FC frame

FC frames buffered and queued in intermediate switches Hop-by-hop traffic flow paced by return of Receiver Ready (R_RDY) frames; can only

transmit up to the number of BB_Credits before traffic is throttled

P% >&*&/@&

C0[&(6

Q("\* P1+O

CCY%(&?/#

P1+O %+'#(+1

P% >&*&/@&

C0[&(6

K]^ CCY%(&?/# J_]K`` CCY%(&?/# K]^ CCY%(&?/#

CCY%(&?/#

P1+O %+'#(+1

CCY%(&?/#

P1+O %+'#(+1


21/63


J_ aN

J UG56 P%

M UG56 P%bc EN 5&( P("N&

bK EN 5&( P("N&

Extending Optical SAN ExtensionBB_Credits and Distance

K UG56 P%bJ EN 5&( P("N&

^ UG56 P%bd EN 5&( P("N&

! BB_Credits are used to ensure enough FC frames in flight! A full (2112 byte) FC frame is approx 2 km long @ 1 Gbps, 1 km long

@ 2 Gbps and !km long at 4 Gbps

! As distance increases, the number of available BB_Credits need to increase as well! Insufficient BB_Credits will throttle performanceno data will be transmitted until R_RDY is

returned


22/63


DC 1DC 2

Core Network

Virtual Center


L2 extension for VMotion Network

Target

Volumes

Initiator

;#+("


23/63


Core Network

DC 1 DC 2

Virtual Center

L2 extension for VMotion Network


Improve Latency using Cisco Write Accelerationfeature on MDS Fabric

;#+(", B*+7$=,*,(- E.3(> )3.5$ BC/

Synchronous replcation Latency requirements6789::;;;?:="%@A"4=:#"%%$-,.$%:4=BC0:4=(DE:4=//C:4=FBG:;63-,H8$8,.H#DDI((EF//


24/63


Agenda



Ethernet Based

IP Based



25/63


WAN

L

3

L

3

Server Cabinet Pair 1 Server Cabinet Pair N Server Cabinet Pair 1 Server Cabinet Pair N

L

2

L

2

SiSi SiSi

Primary Root Primary Root

On DCI Etherchannel:! STP Isolation (BPDU Filtering)! Broadcast Storm Control! FHRP Isolation

! Link utilization with Multi-Chassis EtherChannel

! DCI port-channel- 2 or 4 links

! Requires protectedDWDM or Direct fibers

! vPC does not support L3 peering:Use dedicated L3 Links for Inter-DC routing!

! Validated design:200 Layer 2 VLANs + 100 VLAN SVIs

1000 VLAN + 1000 SVI (static routing)

interface port-channel10

desc DCI point to point connection

switchport

switchport mode trunkvpc 10

switchport trunk allowed vlan 100-600

spanning-tree port type edge trunk

spanning-tree bpdufilter enable

storm-control broadcast level 1

storm-control multicast level x

Dual Site InterconnectionLeveraging EtherChannel between Sites


26/63


!0"1 ;/#&6 e6& %"6& ;0NN"(H)3.5$ D9%389-,8 @,.3>( $( )3.5$S5$*

Test Case

Hardware

failure

Ucast

Hardware

failure

Mcast

Hardware

restore

Ucast

Hardware

restore

Mcast

Link

Failure

Ucast

Link

failure

Mcast

Link

Restore

Ucast

Link

Restore

Mcast

VSS-VSS


27/63


FabricPath Simplicity to the Server team

! Benefits server team by providing a network Fabric that looks like a single switch "Breaks down silos,permits workload mobility, provides maximum flexibility

! Lowers OPEX by simplifying server team operation "Reduces dependency on/interaction with networkteam

Web Servers App Servers New Apps

Silo 1 Silo 2 Silo 3

Web Servers

App Servers

New Apps

P9A735L9-6 /(4 /++Y /(4F6,7,h^&%'M@$*93( ` #3%$.

Fabric


28/63


! Ingress FabricPath switch determines destination Switch ID and imposes FabricPath header! Destination Switch ID used to make routing decisions through FabricPath core! No MAC learning or lookups required inside core! Egress FabricPath switch removes FabricPath header and forwards to CE

STP

FabricPath Core

"FabricPath interface

"CE interface

STP

MAC A MAC B

S10 S20

DMAC"B

SMAC"A

Payload

Ingress FabricPathSwitch

Egress FabricPathSwitch

DMAC"B

SMAC"A

Payload

DSID"20

SSID"10

DMAC"B

SMAC"A

Payload

ISIS

FabricPathData Plane Operation


29/63


MAC C

FabricPath Core

MAC A

MAC B

FabricPath

MAC Table on S100

MAC IF/SID

A e1/1 (local)

B S200 (remote)

S100

S200

S300

FabricPath

MAC Table on S200

MAC IF/SID

A S100 (remote)

B e12/1(local)

C S300 (remote)

FabricPath

MAC Table on S300

MAC IF/SID

B S200 (remote)

C e7/10 (local)

FabricPathConversational MAC Learning


30/63


Site C

vPC+

! F1/F2 End to End foroptimal design

! Required point to pointconnections

! Relies on Flooding forUnknown Unicast traffic

! No current Broadcastsuppression! L2 Multipath only for equal

cost path can be leveraged

(i.e. A&B or C&D)

! Conversational MacLearning

! Offer a full HA DCI solutionwith Native STP Isolation

! Provides easy integrationwith Brownfield DC

! Optimized using vPC+Site A

Site B

vPC+

ClassicalEthernet

Cloud

Site D

vPC+

STPVSS

CE

Core FabricPath

FabricPath for DCIPartial-Meshed Topology for different models of DC


31/63


Agenda



Ethernet Based

IP Based



32/63


OTV is a MAC in IP technique to

extend Layer 2 domains

OVER ANY TRANSPORT

Protocol Learning

Built-in Loop Prevention

Preserve Failure Boundary

Site Independence

Automated Multi-homing

Dynamic Encapsulation

No Pseudo-Wire State

Maintenance

Optimal Multicast

Replication

Multipoint Connectivity

Point-to-Cloud Model

First platform to support OTV(since 5.0 NXOS Release)

Nexus 7000

Now also supporting OTV(since 3.5 XE Release)

ASR 1000

J!

Overlay Transport VirtualizationTechnology Pillars


33/63


Overlay Transport VirtualizationOTV Control Plane

! Edge Device (ED): connects the site to the (WAN/MAN) core and responsible forperforming all the OTV functions

! Internal Interfaces: L2 interfaces (usually 802.1q trunks) of the ED that face the site! Join Interface:L3 interface of the ED that faces the core! Overlay Interface: logical multi-access multicast-capable interface. It encapsulates

Layer 2 frames in IP unicast or multicast headers

"#$

B(-,7(9%

B(-,7


34/63


#%&'()*%+

,'-%&(+%./+.%0

OTV OTV OTV OTV

MAC TABLE

VLAN MAC IF

100 MAC 1 Eth 2

100 MAC 2 Eth 1

100 MAC 3 IP B

100 MAC 4 IP B

MAC 1#MAC 3

MAC TABLE

VLAN MAC IF

100 MAC 1 IP A

100 MAC 2 IP A

100 MAC 3 Eth 3

100 MAC 4 Eth 4

:94,7 !

:$$?&+

j

IP A#IP BMAC 1#MAC 3MAC 1#MAC 31'/&)

J20/&)

d

MAC 1#MAC 3WestSite30%40% 5 30%40% 6

EastSite

k

l

,7 8 ,7 9

I

IP A#IP BMAC 1 #MAC 3

OTV Data PlaneInter-Site Packet Flow

Jk


35/63


IP A

IPB

West

East

3 New MACs arelearned on VLAN 100

Vlan 100 MAC A

Vlan 100 MAC B

Vlan 100 MAC C

IPC

South

VLAN MAC IF

100 MAC A IP A

100 MAC B IP A

100 MAC C IP A

4

OTV updates exchanged via

the L3 core

OTVUpdate

3

OTV

Upd

ate

3

2

VLAN MAC IF

100 MAC A IP A

100 MAC B IP A

100 MAC C IP A

4

3 New MACs arelearned on VLAN 100

1

Overlay Transport VirtualizationOTV Control Plane

! Neighbor discovery and adjacency overMulticast (Nexus 7000 and ASR 1000)

Unicast (Adjacency Server Mode currently available with Nexus 7000 from 5.2 release)

! OTV proactivelyadvertises/withdraws MAC reachability (control-plane learning)! IS-IS is the OTV Control Protocol - No specific configuration required

Jd


36/63


OTV Failure Domain IsolationSpanning-Tree Site Independence

! Site transparency: no changes to the STP topology! Total isolation of the STP domain! Default behavior: no configuration is required! BPDUs sent and received ONLY on Internal Interfaces

7K

7L

OTV OTV

QZ& C=!e6

6#+5 Z&(&

QZ& C=!e6

6#+5 Z&(&

Jj


37/63


OTV Failure Domain IsolationPreventing Unknown Unicast Storms

! No requirements to forward unknown unicast frames! Assumption: end-host are not silent or uni-directional! Default behavior: no configuration is required

7K

7L

OTV OTV

MAC TABLE

VLAN MAC IF

100 MAC 1 Eth1

100 MAC 2 IP B

- - -

MAC 1#MAC 3

8+ F4% L /' #Z&

F4% Q"G1&

Jl


38/63


Remote OTV Device MAC

Table

VLAN MAC IF

100 MAC 1 IP A

101 MAC 2 IP B

! Automated and deterministic algorithm (notconfigurable)

! In a dual-homed site:Lower IS-IS System-ID (Ordinal 0) = EVEN VLANs

Higher IS-IS System-ID (Ordinal 1) = ODD VLANs! Future functionality will allow to tune the behavior

OTV OTV

B(-,7(9% +,,73(>


39/63


OTV and MAC Mobility

OTV

49!

49!

OTV

OTV

OTV

F4% f

F4% f

F4% f

VM Moves

F4% f

OTV

F4% f

F4% f

49!

OTVD&6#

D&6# 9"6#

OTV

OTV 9"6#

1

Server originates a

Gratuitous ARP (GARP)frame

AED advertises MAC X with ametric of zero F4% f

LMN J,-,#-= +LO P 3=

4"; %"#$%

F4% f

F4% f

F4% f

1#n

MAC X

1#n

1#n

1#n

MAC X

F4% f

2

2.3

2.2 2.1


40/63


OTV

49!

OTVD&6#

49!

F4% f

49!

OTV

OTV 9"6#

F4% f

LMN 34 =3-, M$=- K".;$.J= -6,

QL1R S."$J#$=- K.$*, $#."==

-6, "T,.%$U49!

F4% f

F4% f

F4% f

1#n

LMN 34 =3-, V,=- K".;$.J= -6,

QL1R 34-" -6, =3-, $4J -6, !/

=;3-#6,= @8J$-, -6,3. OL+ -$S%,=

1#n

MAC X

F4% f

OTV and MAC Mobility

F4% f

49!

OTV

OTVD&6#

49!

OTV

OTV

F4% f

F4% f

9"6#F4% f

F4% f

1#n

1#n

MAC X

F4% f

MN= 34 =3-, V,=- =,, +LO P $JT,.A=,*,4- ;3-6 $ S,7,. *,-.3# K."* =3-, M$=- $4J

#6$42, -6,* -" .,*"-, +LO $JJ.,==>7,>9'$(

)$7,

!&IUDg

P37,F9%%P37,F9%%

"#$"#$

!&IUDg

7K

7L

Placement of the OTV Edge DeviceOption 2 - OTV at the Aggregation with L2-L3 Boundary on External Firewalls

k!


43/63


OTV and SVI RoutingIntroducing the OTV VDC! Guideline: The current OTV implementation on the Nexus 7000 enforces the

separation between SVI routing and OTV encapsulation for any extended VLAN

! This separation can be achieved with having two separate devices to performthese two functions

! An alternative cleaner and less intrusive solution is the use of Virtual DeviceContexts (VDCs)available with Nexus 7000 platform:A dedicated OTV VDC to perform the OTV functionalities

The Aggregation-VDC used to provide SVI routing support

AggregationOTV$2:

OTV

$2:7K

7L

kJ


44/63


! L2-L3 boundary at aggregation! DC Core performs only L3 role!STP and L2 broadcast Domains

isolated between PODs!Intra-DC and Inter-DCs LAN extension

provided by OTV

Requires the deployment of dedicated

OTV VDCs

!Ideal for single aggregation blocktopologies

!Recommended for Green FielddeploymentsNexus 7000 required in aggregation

=L) =L)

;.)6 ;.)6 ;.)6 ;.)6

Placement of the OTV Edge DeviceOption 3OTV in the DC Aggregation

kk


45/63


"#$

$2:

"#$

$2:

7/'E]J 7/'E]K=+J

8ha]4

8ha]C

7/'E]J

7/'E]L 7/'E]M

7/'E]K=+J

R6U=3#$% W3,;

!"23#$% W3,;AQ. .!% AQ. .!%

8ha]4

8ha]C

>+03'< .!%7/'E]L

>+03'< .!%

7/'E]M

7"H&(L

7"H&( K

!May use a single physical link for Join andInternal interfaces

Minimizes the number of ports required tointerconnect the VDCs

!Single link or physical node (or VDC)failures lead to AED re-election

50% of the extended VLANs affected

!Failure of the routed link to the core is notOTV related

Recovery is based on IP convergence

Single Homed OTV VDCSimple Model

kd


46/63


!Logical Port-channels used for the Joinand the Internal interfaces

Increases the number of physical interfaces

required to interconnect the VDCs

!Traffic recovery after single link failureevent based on port-channel re-hashing

No need for AED re-election

!Physical node (or VDC) failure stillrequires AED re-election

In the current implementation may cause fewseconds of outage (for 50% of the extended

VLANs)

"#$

$2:

"#$

$2:

=+J

8ha]4

8ha]C

7/'E 7/'E h

=+J

R6U=3#$% W3,;

!"23#$% W3,;AQ. .!% AQ. .!%

8ha]4

8ha]C

7/'E6 J]K

7"H&( L

7"H&( K

7/'E6 L]M

>+03'< .!% >+03'< .!%7/'

E` 7/'Eh

7/'E_ 7/

'E^

7/'E6 J]K 7/'E6 L]M

7/'E

7/'E _

Dual Homed OTV VDCImproving the Design Resiliency

kj


48/63


Routing VDC

OTV VDC

hostname routing-vdc

!

interface Ethernet1/1

switchport

switchport mode trunk

switchport trunk allowed vlan 100,600-700

!


ip address 3.3.3.1/24

ip router ospf 1 area 0.0.0.0

ip ospf passive-interface

hostname otv-vdc

feature otv

!

otv site-vlan 100

!


description Internal Interface

switchport

switchport mode trunk

switchport trunk allowed vlan 100,600-700

!


description Join Interface

ip address 3.3.3.2/24

!

interface Overlay100

otv join-interface Ethernet2/2otv adjacency-server*

otv use-adjacency-server 10.1.1.1 11.1.1.1

otv extend-vlan 600-700

!

ip route 0.0.0.0 0.0.0.0 3.3.3.1

N7K-Agg1 N7K-Agg2

e1/1 e1/2

e2/2e2/1

L3 LinkL2 Link

Routing VDC Routing VDC

OTVVDC

OTVVDC

Establish L3 peeringon a dedicated VLAN

m 0,,8,8 $(%4 $( -6, /8U95,(54 #,7=,7

OTV in the DC AggregationConfiguration (Unicast Transport)

kH


49/63


Agenda



Ethernet Based

IP Based



50/63


L2 Links (GE or 10GE)


Layer 3 CoreISP A

ISP B

Access

Agg

Access

Agg

DC A DC B

VLAN A

Public Network

Data-BaseFront-End

DB

144.254.100.0/25 & 144.254.100.128/25

EEM or RHI can be used to get very granular

" Move the whole application tier" Optimize the whole path:

! Client to Server! Server to Server! Server to Client

Server-Server

Path Optimization

Egress Path Optimization: Server-Client Egress Path Optimization: Server-Client

Ingress Path Optimization:Clients-Server

Path Optimization and DCIAvoid Suboptimal Traffic Path After Workload Motion

de


51/63


V10V20

HSRPActive

HSRPStandby

ARP forHSRP VIP

ARPreply

Filter HSRP

! Filter FHRP with combination of VACL or PACL! Result: Still have one HSRP group with one VIP, but now have active router at each

site for optimal first-hop routing

Outbound Path OptimizationFHRP Filtering

HSRPActive

HSRPStandby

HSRP Hellos HSRP Hellos

dI


52/63


Ingress Routing Localization

Challenge

! Subnets are spread across locations! Subnet information in the routing tables is not specific

enough

! Routing doesnt know if a server has moved betweenlocations

! Traffic may be sent to the location where the application isnot available

D&6# 9"6#

)'


53/63


VMotion - Primary Service in Left DCGSS and ACE KAL-AP

7"H&( L %+(&

)'#("');= 4);= C

4**&66

4


54/63


7"H&( L %+(&

)'#("');= 4);= C

4**&66

4


55/63


7"H&( L %+(&

)'#("');= 4);= C

4**&66

4


56/63


7"H&( L %+(&

)'#("');= 4);= C

4**&66

4


57/63


7"H&( L %+(&

)'#("');= 4);= C

4**&66

4


58/63




VM= 10.10.10.1

Default GW = 10.10.10.100

VMotionIngress Routing Optimization with LISP

7"H&( L %+(&

)'#("');= 4);= C

4**&66

4


59/63


Agenda



Ethernet Based

IP Based



60/63


Data Center Interconnect - DCI ModelConnecting Virtualized Data Centers

L2 Domain Elasticity- 748 9:#&'6/+'

VM-Mobility

VN-linknotifications

Path Optimization- Optimal Routing- Route Portability

Storage Elasticity

-SAN Extensions

LANExtensionsOTV

OTV

OTV

OTV

! Sync or Async replication modes are driven by the applications, hence thedistance/latency is a key component to select the choice! Localization of Active Storage is key#Distance can be improved using IO accelerator or caching

#Virtual LUN is allowing Active/Active

! #KL B.$%9'$( 3. -6, ?,4 ,%,*,(-! ^&%'+$3(-! :$$+ 9=$389(5, O #-$7*M)$(-7$%

E(?($F( E(359.- Z _7$9859.- 5$(-7$%

! :3(? .-&783(,..! #59%, Z )$(=,7>,(5,

)$(.38,79'$(.! 0,-F$7? 9(8 #,5&73-4 .,7=35,. 8,+%$4*,(-! #,7=,7M)%3,(- P%$F.! #,7=,7M#,7=,7 P%$F.L9-6 C+'*3;9'$( C+'$(.

! 1>7,..#/887,..,8 A4 PNQL P3%-,73(>

! B(>7,..R#/887,..,8 A4 T##O/)1 $7 QNB $7 11^OBL#:/ $7 :B#L

je


61/63


Data Center InterconnectWhere to Go for More Information

http://www.cisco.com/go/dcihttp://www.cisco.com/en/US/netsol/ns749/networking_solutions_sub_program_home.html

jI


62/63


Complete Your OnlineSession Evaluation! Give us your feedback and you

could win fabulous prizes.

Winners announced daily.

! Receive 20 Passport points for eachsession evaluation you complete.

! Complete your session evaluationonline now (open a browser through

our wireless network to access our

portal) or visit one of the Internet

stations throughout the Convention

Center.

Dont forget to activate yourCisco Live Virtual account for access to

all session material, communities, and

on-demand and live activities throughout

the year. Activate your account at theCisco booth in the World of Solutions or visitwww.ciscolive.com.

j!


63/63


BRKDCT 3060 Dc Interconnect

Documents