fed fabric and clouds

FABRICS AND THE CLOUDREINVENTING THE DATA CENTER NETWORK

Andy Ingram

SVP, Juniper Networks

September, 2011

2 Copyright © 2011 Juniper Networks, Inc. www.juniper.net

NEW MATH

2096Federal Data Centers

800Mandated reduction

- 1296Future capacity

=

1279Current requirements

=

1752Future requirements

=

* Per MeriTalk survey of 200 Federal IT decision makers – June 2011

x 61%Average utilization

*

x 1.37Expected increase

in required capacity

*


1279Current requirements

1296

1752

=/



1296 1752


SKEPTICISM OR REALISM

10%of Federal IT

professionals believe the

Feds will reach or

exceed the 2015 goal

Per MeriTalk survey of 200 Federal IT decision makers – June 2011

23%anticipate there will be

more rather than fewer

data centers in 2015


CAN THE CLOUD HELP?

Agenda

– The Path to Cloud

– Why a Fabric?

– Not all Fabrics are Created Equal


DATA CENTERS ARE BUILDING CLOUDS

ResourcePooling-Clouds

A single scalable pool

The

Networkis the

foundation


PATH TO THE CLOUD

Client-Server to SOA architecture transition

Challenge: Evolve the applications

Applications

1Consolidation

2Optimization

3Cloud

4


APPLICATION EVOLUTION

FC SAN

LAN

SAAS

SOA

Web 2.0

Client Server

Storage on a Network

Server growth and standardization

Application Evolution


Latency Sensitive

CHANGING ROLES OF THE NETWORK

Application running

Latency Tolerant

Traditional role – connecting users• North-South traffic

New role – connecting devices• East-West traffic

• Ideally one hop away

95% of network traffic

was going North-South

75% of network traffic

is now going East-West

Newest role – foundation of the cloud• Any-to-any connectivity


PATH TO THE CLOUD

Standardization

Reduce complexity

Improve the Utilization of Servers and Storage

Improve economics

Challenge: Implementing standardization and virtualization

Applications

1Consolidation

2Optimization

3Cloud

4

Non mission critical apps

Small pools

Relatively static

Simple security model


CapitalSavings

THE ECONOMICS OF THE DATA CENTER

0

20

40

60

80

1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013

Physical Server Installed Base (Millions)

Logical Server Installed Base (Millions) MillionsInstalledServers

Source: IDC

Complexity andOperating Costs

Implementations

97% of organizations40-45% of workloads

Gartner .

38%Of Federal workloads have

been virtualized.

64% by 2015MeriTalk .


PATH TO THE CLOUD

Faster provisioning

Business agility

Resilience

Better user experience & economics

Challenge: Evolve the network

Applications

1Consolidation

2Optimization

3Cloud

4

Mission critical apps

Large pools

Relatively dynamic

Complex security model


PATH TO THE CLOUD

On demand

Self provisioned

Pay-as-you-go

Hybrid Clouds

Challenge: Automation, security

Applications

1Consolidation

2Optimization

3Cloud

4


THREE PROBLEMS WITH THE LEGACY NETWORK

Production

vMotion vCenter

ManagementFC SAN

1. Less is More:

Multiple networks to orchestrate

3. Tyranny of Trees:

Inconsistent application behavior

2. Metcalfe’s Revenge:

Geometrically increasing complexity

1. Less is More:

Multiple networks to orchestrate


Com

ple

xity

5,000

2,500

0 20001000 3000

No. of Ports

50004000 6000

10,000

7,500

200

100

400

300

Devices Interactions

Interactions

ManagedDevices

TooComplex

N*(N-1)

2No. of Interactions =*N = No. of managed devices

Solve for the smallest N possible

N=1

COMPLEXITY – METCALFE’S REVENGE


THE TYRANNY OF TREES

VM

Location matters in a tree architecture

OneHop

BubblesOptimal performance

Typical tree configuration

69%Of respondents said

Increased Latency

and

Unpredictable Latency

of Applications

is a problemMeriTalk .


THE TYRANNY OF TREES

VM

Appliances and VLANs

Shadows

Location matters in a tree architectureTypical tree

configuration


TRANSFORM THE NETWORK

One NetworkFlat, any-to-any

connectivity



Locality should not matter in a virtualized data center

Key resourcesare one hop away

Key resourcesare ALWAYS one

hop away


connectivity

VM



Switch

Fabric

Single switch does not scaleSingle point of failure

Switch Fabric

Data Plane

Flat

Any-to-any

Control Plane

Single device

Shared state

Single deviceN=1


connectivity

Performance and simplicity ofa single switch


Switch Fabric

Data Plane

Flat

Any-to-any

Control Plane

Single device

Shared state


Scalability and resilience of a network

Performance and simplicity ofa single switch

Single deviceN=1

A Network Fabric has the….

And the…


connectivity


SIMPLIFY THE NETWORK

The legacy network, 3 tiers

Ethernet

FC SAN

Servers FC StorageNAS


1 TIER

Firewall SLB

One large, seamless resource pool

Servers NAS FC Storage

Edge RouterRemote

Data Center

Flat, resilient fabricEverything is one hop away

Scale without complexityThe ability to add capacity without adding

operational complexity

N=1


3 TYPES OF “FABRICS”

1. Marketing Fabrics

2. Overlay Fabrics

3. Switch Fabrics


MARKETING FABRIC

Benefits:• No incremental benefit


PROTOCOL OVERLAY FABRIC

Spine

Leaf

Spanning Tree


PROTOCOL OVERLAY FABRIC

Spine

Leaf

TRILL or SPB

L2 tunnels

Benefits:• Flatter topology

• Virtualizes locality

• Eliminates Spanning Tree


SWITCH FABRIC


DATA PLANE IN A SINGLE SWITCH

1. The line cards contain the ports and processing intelligence

2. The fabric cards interconnects all ports – any-to-any

Data Plane

3. A single “full lookup” processes the packets


SINGLE SWITCH DOES NOT SCALE

…but eventually it runs out of real estate.

After this, the network cannot be flat.

Ports can be added to a single switch fabric.


SINGLE SWITCH DOES NOT SCALE

Sacrifice simplicity or…change the scaling modelChoice:


SCALING THE DATA PLANE

So, we separate theline cards from the fabric.

And extend the coppertraces with fiber links.

For redundancy addmultiple devices.

QF/Interconnect

QF/Node

Interconnect vs Switch

Bandwidth: 10 Tb/s vs 2.5 Tb/s

Power: 3 Kw vs 13 Kw

ASICs in DP: 3 vs 5

Latency: 2 us vs 10 us


SCALING THE DATA PLANE

QFabric is faster than any Ethernet chassis switch ever built

1. All ports are directly connectedto every other port

2. A single “full lookup” at the ingress QF/Node device

3. Blazingly fast: Always under 5us 3.71us (short cables)

QF/Node

QF/Interconnect

Benefits:• Flatter topology

• Virtualizes locality

• Eliminates STP, TRILL, SPB

• Efficiency (less hardware)• Less power, space, cooling

• Faster (lower latency, jitter)

• Simpler (N=1)

• Less expensive


Overlay Fabric

SWITCH VS. OVERLAY FABRIC – 6000 10 GbE PORTS

Note:

• OS* Over Subscription 3:1

• Ports: 6000 server ports

QFabric

L2 & L3

Non-Blocking

1 125

41

.. .. .... .. .. ..

L3

L2 only

105 1671 21 42 63 84 126 147

1 62 3 4 5 87

Switch Fabric

1/3 fewer devices

77% less powerSavings: $360K/Yr

90% less floor space

85% fewer links

12-16x faster

Mgd. Devices 1 vs. 193

L2 AND L31 16

The QFabric is faster than any chassis switch ever built!


Every application performs

better

Build large, efficient clouds

Less hardware

Operational simplicity of

a switch

Greater reliability

Elegance of design

delivers lower OPEX and

CAPEX

Lowers CostSimplifiesScalesPerforms

BUSINESS BENEFITS OF A QFABRIC


HOW DO I MIGRATE TO QFABRIC?

QFX3500

QFabric

Pod 1 Pod 24


HOW DO I SECURE QFABRIC?

4 vGWin the hypervisor

SRX5800


CAN I STRETCH A QFABRIC?

Data Center 1 Data Center 2


Performance and simplicity

of a single switch

A REVOLUTIONARY NEW ARCHITECTURE

Scalability and resiliencyof a network


WHAT IS

NOWPOSSIBLE

fed fabric and clouds

Technology