Fed Fabric and Clouds

  • 884 views
Uploaded on

 

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
884
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
82
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. FABRICS AND THE CLOUDREINVENTING THE DATA CENTER NETWORKAndy IngramSVP, Juniper NetworksSeptember, 2011
  • 2. NEW MATH 2096 - 800 = 1296 Federal Data Centers Mandated reduction Future capacity 2096 x 61%* = 1279 Federal Data Centers Average utilization Current requirements 1279 x 1.37 * = 1752 Federal Data Centers Expected increase Future requirements in required capacity 1296 = 1752 /2 Copyright © 2011 Juniper Networks, Inc. www.juniper.net * Per MeriTalk survey of 200 Federal IT decision makers – June 2011
  • 3. SKEPTICISM OR REALISM 23% 10% anticipate there will be of Federal IT more rather than fewerprofessionals believe the data centers in 2015 Feds will reach or exceed the 2015 goal3 Copyright © 2011 Juniper Networks, Inc. www.juniper.net Per MeriTalk survey of 200 Federal IT decision makers – June 2011
  • 4. CAN THE CLOUD HELP? Agenda – The Path to Cloud – Why a Fabric? – Not all Fabrics are Created Equal5 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 5. DATA CENTERS ARE BUILDING CLOUDS The Network A single Resource scalable pool is the Pooling-Clouds foundation6 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 6. PATH TO THE CLOUD 1 2 3 4 Applications Consolidation Optimization Cloud  Client-Server to SOA architecture transition  Challenge: Evolve the applications7 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 7. APPLICATION EVOLUTION SOA Application Web Evolution 2.0 SAAS Client Server Server growth and standardization Storage LAN on a Network FC SAN8 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 8. CHANGING ROLES OF THE NETWORKTraditional role – connecting users• North-South traffic 75% of network traffic Latency Tolerant is now going East-WestNew role – connecting devices Latency Sensitive• East-West traffic• Ideally one hop awayNewest role – foundation of the cloud• Any-to-any connectivity 95% of network traffic was going North-South Application running9 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 9. PATH TO THE CLOUD 1 2 3 4 Applications Consolidation Optimization Cloud  Standardization Non mission critical apps  Reduce complexity Small pools  Improve the Utilization of Servers Relatively static and Storage  Improve economics Simple security model  Challenge: Implementing standardization and virtualization10 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 10. THE ECONOMICS OF THE DATA CENTER Logical Server Installed Base (Millions) 38% Physical Server Installed Base (Millions) Millions Installed Servers Of Federal workloads have 80 been virtualized. Complexity and 64% by 2015 Operating Costs 60 MeriTalk . Capital Implementations Savings 40 97% of organizations 40-45% of workloads Gartner 20 . 0 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 Source: IDC11 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 11. PATH TO THE CLOUD 1 2 3 4 Applications Consolidation Optimization Cloud  Faster provisioning Mission critical apps  Business agility Large pools  Resilience Relatively dynamic  Better user experience & Complex security model economics  Challenge: Evolve the network12 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 12. PATH TO THE CLOUD 1 2 3 4 Applications Consolidation Optimization Cloud  On demand  Self provisioned  Pay-as-you-go  Hybrid Clouds  Challenge: Automation, security13 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 13. THREE PROBLEMS WITH THE LEGACY NETWORK1. Less is More: Multiple networks to orchestrate Production2. Metcalfe’s Revenge: FC SAN ManagementGeometrically increasing complexity3. Tyranny of Trees: vMotion Inconsistent application behavior vCenter 14 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 14. COMPLEXITY – METCALFE’S REVENGE Too Solve for the Complex Devices Interactions smallest N possible 400 10,000 N=1 Interactions 300 7,500 Complexity N*(N-1) No. of Interactions = 200 5,000 *N = No. of managed devices 2 100 2,500 Managed Devices 0 1000 2000 3000 4000 5000 6000 No. of Ports15 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 15. THE TYRANNY OF TREES Typical tree 69% Location matters in a tree architecture configuration Of respondents said Increased Latency and Unpredictable Latency of Applications Bubbles is a problem Optimal performance MeriTalk . One VM Hop16 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 16. THE TYRANNY OF TREES Location matters in a Typical tree tree architecture configuration Appliances and VLANs Shadows VM17 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 17. TRANSFORM THE NETWORK One Network Flat, any-to-any connectivity18 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 18. TRANSFORM THE NETWORK One Network Flat, any-to-any connectivity VM Key resources Key resources are ALWAYS one are one hop away hop away Locality should not matter in a virtualized data center19 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 19. TRANSFORM THE NETWORK One Network Single device Flat, any-to-any N=1 connectivity Switch Fabric Switch Data Plane Fabric  Flat  Any-to-any Control Plane  Single device  Shared state Performance and simplicity of Single switch does not scale a single switch Single point of failure20 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 20. TRANSFORM THE NETWORK One Network Single device Flat, any-to-any N=1 connectivity Switch Fabric Data Plane  Flat  Any-to-any Control Plane  Single device  Shared stateA Network Fabrichas the…. Performance and simplicity of Scalability and resilience a single switch of a network And the…21 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 21. SIMPLIFY THE NETWORK The legacy network, 3 tiers Ethernet Servers NAS FC Storage FC SAN22 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 22. 1 TIER Remote Edge Router Flat, resilient fabric Data Center Everything is one hop away Scale without complexity The ability to add capacity without adding operational complexity N=1 Firewall SLB Servers NAS FC Storage One large, seamless resource pool23 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 23. 3 TYPES OF “FABRICS” 1. Marketing Fabrics 2. Overlay Fabrics 3. Switch Fabrics24 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 24. MARKETING FABRIC Benefits: • No incremental benefit25 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 25. PROTOCOL OVERLAY FABRIC Spine Spanning Tree Leaf26 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 26. PROTOCOL OVERLAY FABRIC Spine TRILL or SPB L2 tunnels Leaf Benefits: • Flatter topology • Virtualizes locality • Eliminates Spanning Tree27 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 27. SWITCH FABRIC28 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 28. DATA PLANE IN A SINGLE SWITCH Data Plane 1. The line cards contain the ports and processing intelligence 2. The fabric cards interconnects all ports – any-to-any 3. A single “full lookup” processes the packets29 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 29. SINGLE SWITCH DOES NOT SCALE Ports can be added to a single switch fabric. …but eventually it runs out of real estate. After this, the network cannot be flat.30 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 30. SINGLE SWITCH DOES NOT SCALE Sacrifice simplicity or… Choice: change the scaling model31 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 31. SCALING THE DATA PLANE Interconnect vs Switch So, we separate the Bandwidth: 10 Tb/s from the fabric. line cards vs 2.5 Tb/s And extend the copper Power: traces with fiber 13 Kw 3 Kw vs links. For redundancy add ASICs in DP: multiple devices. 5 3 vs Latency: 2 us vs 10 us QF/Interconnect QF/Node32 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 32. SCALING THE DATA PLANE Benefits: • Flatter topology 1. All portsconnected directly are • Virtualizes locality to every other port • Eliminates STP, TRILL, SPB QF/Interconnect 2. A single “full lookup” at the • Efficiency (less hardware) ingress QF/Node • Less power, space, cooling device • Faster (lower latency, jitter) QF/Node • Simpler (N=1) • Less expensive 3. Blazingly fast: Always under 5us 3.71us (short cables) QFabric is faster than any Ethernet chassis switch ever built33 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 33. SWITCH VS. OVERLAY FABRIC – 6000 10 GbE PORTS QFabric Switch Fabric Non-Blocking 1 4 L2 & L3  1/3 fewer devices  77% less power 1 125 Savings: $360K/Yr Overlay Fabric  90% less floor space L3  85% fewer links  12-16x faster 1 2 3 4 5 6 7 8  Mgd. Devices L2 only 1 vs. 193 1 16  L2 AND L3 1 .. 21 .. 42 .. 63 .. 84 .. 105 .. 126 .. 147 167 The QFabric is faster than any chassis switch ever built!34 Note: Copyright © 2011 Juniper Networks, Inc. www.juniper.net • OS* Over Subscription 3:1 • Ports: 6000 server ports
  • 34. BUSINESS BENEFITS OF A QFABRIC Performs Scales Simplifies Lowers Cost Every Build large, Less hardware Elegance of application efficient design performs clouds Operational delivers lower better simplicity of OPEX and a switch CAPEX Greater reliability35 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 35. HOW DO I MIGRATE TO QFABRIC? QFabric QFX3500 4 Pod 1 Pod 236 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 36. HOW DO I SECURE QFABRIC? SRX5800 4 vGW in the hypervisor37 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 37. CAN I STRETCH A QFABRIC? Data Center 1 Data Center 238 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 38. A REVOLUTIONARY NEW ARCHITECTURE Performance and simplicity of a single switch Scalability and resiliency of a network39 Copyright © 2011 Juniper Networks, Inc. www.juniper.net
  • 39. WHAT IS NOW POSSIBLE40 Copyright © 2011 Juniper Networks, Inc. www.juniper.net