Your SlideShare is downloading. ×
  • Like
Presentación Data Center Chile Logicalis
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Presentación Data Center Chile Logicalis


Presentación del evento Data Center Chile

Presentación del evento Data Center Chile

Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • VM Connection Policy = Defined in the network, applied in Virtual Center
  • VM Connection Policy = Defined in the network, applied in Virtual Center
  • Virtual Supervisor Module (VSM) Virtual or Physical appliance running Cisco OS (supports HA) Performs management, monitoring, & configuration Tight integration with VMware Virtual Center Virtual Ethernet Module (VEM) Enables advanced networking capability on the hypervisor Provides each VM with dedicated “switch port” Collection
  • DOM= digital optical monitoring Portulla (2248) and Woodside (2232) ASICs support both local classification and policiers. No commited features on the roadmap to leverage the policiers currently. QoS policies on the system are function of both the line card (N2K) and the parent switch (N5K/N7K) and the system QOS design will leverage overall capabilities of both. Transcript : So if you look at the lay of the land at the moment with the 2148T, we obviously have the 2148T shipping today. And there's a couple of things that I'll probably want to point out. Certainly I think you're probably all familiar with the architecture and the restrictions of the platform today. But some of the things I probably want to call out include support only for 1Gig, so essentially 1000Base-T. Essentially also there's no local classification capabilities, no FCoE support, as well as no local port channel capabilities today. However it is obviously shipping and supported today. And certainly if you do have any requirements to propose an architecture in any new data center build outs that require 1Gig connectivity, Certainly I would encourage you to actively keep selling the 2148T. It has been very very popular and has been very very successful for the Nexus 5000 series platform. So also with the upcoming new series platforms we're going to be introducing them in essentially two phases. One is what we call the SFP sort of pluggable options and the second one would be a 10Base-T type of option. So first and foremost, probably around Q2 timeframe with Calendar Year 2010 we're going to be introducing a 2248 what we call TP. I'll talk about a nomenclature in a moment, but we're also going to at the same time be introducing the 2232PP as well. So both SFP pluggable-type of options for uplinks and in the case of the 2232 SFP options for downlinks as well. Both of them will still be one rack unit in form factor. The 2248 will add the connectivity capabilities of 100Meg in addition to 1Gig and the 2232 will essentially have both 1Gig and 10Gig connectivity options as well. Likewise as I mentioned earlier, there is some local classification capabilities both for QoS and ACLs, so we're basically going to be factoring both of them in, although maybe not at FCS, most likely in a subsequent software upgrade. But bear in mind that the hardware is capable of handling that for a software upgrade. Other things include local port channel capabilities. Once again, we do support VPC across Nexus 2148T ports today, but the current generation of 2000s don't have any local port channel intelligence. As a result of that you can't channel between ports locally on the same Nexus 2000. So with the new Nexus 2000s we will offer that capability, so both on the 2248Ts as well as the 2232s we'll offer local port channels as well as VPCs. From a timeframe perspective the new Nexus 2000s will be introduced starting from Q2 of 2010 for the pluggable options, and moving to second half of 2010 for the 10GBase-T options as well. From the Nexus 7000, just reading from this slide, certainly the first FCS will be available with the 2148T from the Cairo software release, which will be roughly about the Q2 timeframe, and then following with the 2248T from Q3 and the 2232 from Q4 and onwards. Author’s Original Notes:
  • Transcript: Now let's look at an actual simplified deployment model for the consolidated fabric, and in this case using Fibre Channel over Ethernet. On the left we show an simplified model of a traditional data center infrastructure today. In the servers at the bottom of the left hand side, you see a multitude of network interface modules inside the servers. Again, typically between six and eight adapters per physical server. And in the access layer, you have many different types of switch devices. You have your traditional LAN switches for Ethernet, your SAN switches for your storage traffic, or Fibre Channel traffic, and you have redundant links, naturally, in order to maximize uptime, in both the Fibre Channel space, and also in the LAN space. Now this is simplified because traditionally in data centers you also have many different cluster environments that are often autonomous, separate networks. So if you look at the network on the right, we've implemented I/O consolidation through the use of a unified fabric. And in this case, because it's Fibre Channel, also the use of Fibre Channel over Ethernet, or FCoE. So we go down from four switches on the left, to two switches on the right, and two switches for redundancy purposes. And we go down from about six to eight adapters on the left, to just two converged network adapters per server in the picture on the right. And if those were six adapters on the left, this would correlate to a 66% reduction in the number of cables inside this simplified network architecture. In this environment we're showing that the Nexus 5000s take in traditional Ethernet traffic, 10GE traffic, coming from the converged network adapters out of the servers, as well as Fibre Channel over Ethernet, again, also coming from the converged network adapters. And then the Nexus 5000s actually convert the FCoE traffic back to Fibre Channel for connectivity back to the SAN A and SAN B target systems. Author’s Original Notes: Today: Parallel LAN/SAN Infrastructure Inefficient use of Network Infrastructure 5+ connections per server – higher adapter and cabling costs Adds downstream port costs; cap-ex and op-ex Each connection adds additional points of failure in the fabric Longer lead time for server provisioning Multiple fault domains – complex diagnostics Management complexity – firmware, driver-patching, versioning
  • Transcript : What is FCoE? It's the mapping of FC frames. It's basically the letter in the envelope; the letter is now fiber channel, the envelope is Ethernet. Stick one inside the other, when it gets to the edge of the network where fiber channel is required we just rip off the Ethernet envelope and pass it along as fiber channel normally passes traffic along. Now both block I/O and Ethernet are running over a common infrastructure. There's a ton of savings there. Reduction in power and cooling, reduction of cabling infrastructure. Reduction of overall management of the infrastructure; you have one big unified fabric to manage as opposed to managing separate islands. Fewer adaptors are needed and there's no Gateway required it's a full stateless implementation. This is why it's so attractive to our customers. We don't have to worry about performance penalties for doing fiber channel over Ethernet like in iSCSI and we will do both. Actually DCB will even benefit iSCSI networks. Why, because it's lossless. So we're still heading down both paths, it's just a customer choice. Cisco does not hold technology religion, we never did, never will.


  • 1. Tendencias en los Data Center 3.0 Carlos Spera SDM Data Center Southern Cone Business and Technology Working as One
  • 2. Presiones del negocio y del Data Center Business and Technology Working as One
  • 3. Tecnologías estratégicas para 2010 Las 10 tecnologías estratégicas mas importantes de Gartner para 2010, definidas como “de potencial impacto considerable en la empresa en los próximos tres años”:1. Virtualización.2. Cloud computing.3. Servidores (Más allá de Blades).4. Arquitecturas orientadas a la Web.5. Aplicaciones Web híbridas empresariales.6. Sistemas especializados.7. Software / Redes Sociales.8. Comunicaciones unificadas.9. Inteligencia de negocios.10. TI Ecológica (“Green IT”). Business and Technology Working as One
  • 4. Cloud Computing “Cloud computing es un paradigma que permite ofrecer servicios de computación a través de Internet” Business and Technology Working as One
  • 5. Cloud Computing: ConceptosDefinimos al “Cloud Computing” como un estilo de computación donde los recursos de IT son: Brindados a los clientes como un servicio utilizando tecnologías de Internet. Masivamente escalables. De alcance global. Distribuibles dinámicamente, “a demanda” en cantidad y calidad medibles Asignados Just in Time Servicios a múltiples clientes que comparten los mismos recursos. Se paga solo por el servicio que se utiliza.La virtualizacion es el fundamento para avanzar hacia los servicios del cloud computing Business and Technology Working as One
  • 6. Las empresas hacia el cloud computing Las empresas dispondrán de una infraestructura dedicada para algunos propósitos y consumirán servicios On Demand obtenidos de la nube para otros. Business and Technology Working as One
  • 7. Algunos Beneficios del Cloud Computing Las infraestructuras de Cloud Computing proporcionan mayor capacidad de adaptación, recuperación de desastres y reducción al mínimo de los tiempos de inactividad. No necesita instalar ningún tipo de hardware o software: una infraestructura 100% de Cloud Computing tiene como atractivo su simplicidad… y el hecho de que requiera mucha menor inversión para empezar a trabajar. Se redirigen los costos de CAPEX y problemas de capacidad al cloud provider. Los cloud providers están interesados en tener lo más que puedan de la infraestructura de storage y procesamiento de sus clientes. Business and Technology Working as One
  • 8. SaaS, PaaS, IaaS ?!!?SaaS (Software as a Service): Significa una sóla instancia del software que corre en la infraestructura del proveedor y sirve a múltiples organizaciones de clientes. Ejemplo: Salesforce.comPaaS (Plataform as a Service): Es la encapsulación de una abstracción de un ambiente de desarrollo. Ejemplo: (Infraestructura as a Service): Es un medio de entrega de almacenamiento básico y capacidades de cómputo como servicios estandarizados en la red. Servidores, sistemas de almacenamiento, conexiones, routers, y otros sistemas son concentrados (por ejemplo a través de tecnología de virtualización) para manejar tipos específicos de cargas de trabajo. Ejemplo: Web Services de Amazon Business and Technology Working as One
  • 9. Virtualización  La Virtualización consiste en la abstracción de los recursos físicos existentes en un equipo informático para poder correr sobre el mismo equipos virtuales.  Cada uno de estos equipos virtuales ve un servidor completo, interactuando con el mismo a través de la tecnología de virtualización. Business and Technology Working as One
  • 10. Atributos impulsores de la Virtualización Business and Technology Working as One
  • 11. Next Generation Data CenterA medida que la infraestructura IT se vuelve más compleja, los requisitos de IT cambian de gerenciar operaciones técnicas a operaciones de servicios. Esto plantea la necesidad de transformación del DC.Cuatro fuerzas evolutivas La nueva generación de Data CentersEstán dando forma al NGDC sera… • Una infraestructura provisionada dinámicamente por medio del uso de capacidades automatizadas soportando el proceso de negocio de la compañía. • Servicios de tecnología construidos sobre infraestructura virtual. • Procesos estandarizados. • Arquitecturas tecnológicas que permitan consolidar recursos de IT. Business and Technology Working as One
  • 12. La evolución de la arquitectura de los DC Data Center 1.0 Data Center 2.0 Data Center 3.0 Client-Server and Service Oriented and Mainframe Distributed Computing Web 2.0 BasedIT Relevance and Consolidate Virtualize Automate Centralized Decentralized Virtualized Application Architecture Evolution Business and Technology Working as One
  • 13. Descriptas las tendencias en el Data Center La pregunta es… ¿Cuáles son las tendencias tecnológicasen lo referente al networking asociadas con las anteriores? 10GE to the server (with enhancements) Unified IO Server virtualization Server mobility (inter and intra DCs) Aceleracion y optimizacion de Aplicaciones Business and Technology Working as One
  • 14. Cisco NEXUS 1000V Business and Technology Working as One
  • 15. VN-Link Brings VM Level Granularity Problems: VMotion • VMotion may move VMs across physical ports—policy must follow • Impossible to view or apply policy to locally switched traffic • Cannot correlate traffic on physical links—from multiple VLAN VMs 101 VN-Link: •Extends network to the VM •Consistent servicesCisco VN-Link Switch •Coordinated, coherent management Business and Technology Working as One
  • 16. Cisco Nexus 1000V Faster VM Deployment Cisco VN-Link—Virtual Network Link Policy-Based Mobility of Network Non-Disruptive VM Connectivity & Security Properties Operational Model Server Server VM VM VM VM VM VM VM VM #1 #2 #3 #4 #5 #6 #7 #8    VM Connection Policy Cisco Nexus 1000V Linked to VM UUID Applied in Virtual Center Defined in the network VMW ESX VMW ESXDefined PoliciesWEB AppsHRDB VirtualCompliance Center Business and Technology Working as One
  • 17. Cisco Nexus 1000V Richer Network Services VN-Link: Virtualizing the Network Domain Policy-Based Mobility of Network Non-Disruptive VM Connectivity & Security Properties Operational Model Server Server VM VM VM VM VM VM VM VM VM#1 VM#2 VM#3 VM#4 #1 #2 #3 #4 #5 #6 #7 #8    VN-Link Property Mobility Maintains connection state Ensures VM security VMotion for the network VMs Need to Move Cisco Nexus 1000VHardware Failure SW Upgrade/Patch DRS VMotion VMW ESX VMW ESX Virtual Center Business and Technology Working as One
  • 18. Cisco Nexus 1000V Architecture Server 1 Server 2 Server 3 VM VM VM VM VM VM VM VM VM VM VM VM #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 VEM VMware vSwitch VEM VMware vSwitch Nexus 1000V VMware vSwitch VEM VMW ESX VMW ESX VMW ESXVirtual Supervisor Module (VSM) Virtual or Physical applianceVirtual Ethernet Module (VEM) running Cisco OS (supports HA) Enables advanced networkingCisco Nexus 1000V Enables: Virtual Center capability management, monitoring, Performs on the hypervisor & configuration Connectivity Provides eachVM with VMware Policy Based Nexus 1000V “switch port” VM with dedicated Tight integration & Security Mobility of Network Virtual Center Properties Collection of VEMs = 1 Distributed Non-Disruptive Operational Model Switch VSM Business and Technology Working as One
  • 19. Cisco Nexus 1000V Scalability  A single Nexus 1000V supports: 2 Virtual Supervisor modules (HA) Nexus 1000V 64 Virtual Ethernet modules 512 Active VLANs 2048 Ports (Eth + Veth) 256 Port Channels  A single Virtual Ethernet module supports: A B C 216 Ports Veths 32 Physical NICs 8 Port Channels Business and Technology Working as One
  • 21. NX-OS: Purpose Built for the Data Center IOS NX-OSSAN-OS Business and Technology Working as One
  • 22. Business and Technology Working as One
  • 23. Nexus 5000 Family Overview Nexus 2000Nexus 5010 Fabric Extender20 Fixed Ports 10G/FCoE/IEEE DCB Nexus 5020Line-rate, Non-blocking 10G 40 Fixed Ports 10G/FCoE/IEEE DCB1 Expansion Module Slot Line-rate, Non-blocking 10GRedundant Fans & Power Supplies 2 Expansion Module Slots Redundant Fans & Power Supplies Ethernet Ethernet + Fibre Channel Fibre Channel 8G Fibre Channel6 Ports 10G/FCoE/IEEE DCB 4 Ports 10G/FCoE/IEEE DCB 8 Ports 1/2/4G Fibre Channel 6 Ports 2/4/8G Fibre Channel 4 Ports 1/2/4G Fibre Channel Business and Technology Working as One
  • 24. Data Center Access Layer OptionsTop of Rack (ToR)• Typically 1-RU servers• 1-2 GE LOMs• Mostly 1, sometimes 2 ToR switches• Copper cabling stays within rack• Low copper density in ToR• Higher chance of East-West traffic hittingaggregation layer• Drives higher STP logical port count foraggregation layer• Denser server countMiddle of Row (MoR) (or End of Row)• May be 1-RU or multi-RU servers• Multiple GE or 10GE NICs• Horizontal copper cabling for servers• High copper cable density in MoR• Larger portion of East-West traffic staysin access• Larger subnets  less address waste• Keeps agg. STP logical port count low(more EtherChannels, fewer trunk ports)• Lower # of network devices to manage Business and Technology Working as One
  • 25. Cisco Nexus 2000 Fabric Extender (FEX) Nexus 2000 Fabric Extender (FEX)• Nexus 5000 + Nexus 2000 is a Virtual Chassis• Nexus 2000 is a Virtual Line Card to the Nexus 5000• No Spanning Tree between Nexus 2000 and Nexus 5000• Nexus 5000 maintains all management and configuration Business and Technology Working as One
  • 26. Cisco Nexus 2000 Fabric Extender (FEX)Model Nexus 2148T Nexus 2248 TP Nexus 2232-10G PPForm Factor 1 RU 1 RU 1 RUUplink Ports 4 x 10GbE SFP+ 2248TP: 4 x 10GbE SFP+ 2232PP: 8 x 10GbE SFP+Uplink SFP+ Copper CX-1 (passive): 1m, 3m, 5mTransceivers Supported Optical: SR, LR [distance limited to 300m] FETHost Facing Ports 48 x 1GbE RJ45 48 x 100/1000Base-T RJ45 2232PP: 32 x SFP+ (10G) (note: 1000BaseT only)Local Classification No Yes YesFCoE No No YesPower Consumption 165W maximum 165 W 270 wBuffering per port 90KB/port within FEX 195 KB -> Network to Host 147.50 KB/port -> for( N2H) (*) (N2H) (*)Multiple PortChannel Not Supported Yes Yesmember ports on a FEXLatency ~ 7us (LIFO) ~ 4.5 us 4.6 us Business and Technology Working as One
  • 27. Business and Technology Working as One
  • 28. Nexus 2000 — Deployment BenefitsN Business and Technology Working as One
  • 29. I/O Consolidation Today I/O Consolidation with FCoE SAN A SAN B LAN LAN SAN A SAN B Nexus 5000 N2232 N2232 Business and Technology Working as One
  • 30. FC over Ethernet (FCoE) FCoE Benefits Mapping of FC Frames over Fewer Cables Ethernet  Both block I/O & Ethernet traffic Enables FC to Run on a Lossless co-exist on same cable Ethernet Network Fewer adapters needed Overall less power Interoperates with existing SAN’s No Gateway - Stateless Ethernet Fibre Channel Traffic Business and Technology Working as One
  • 32. Cisco Nexus Data Center Portfolio Nexus 7000 Data Center Core/Aggregation Nexus 5000 Unified Server Access Nexus 4000 Unified Fabric Blade Switch Nexus 2000 Remote Module & Scale Nexus 1000V VM-Aware Policy Switching Business and Technology Working as One
  • 33. Nexus 7000 Module Overview Business and Technology Working as One
  • 34. Nexus 7000 SeriesVirtual Device Contexts (VDCs) Up to 4 separate virtual switches from a single physical chassis with common supervisor modules. Separate control plane instances and management/CLI for each virtual switch. Interfaces only belong to one of the active VDCs in the chassis, external connectivity required to pass traffic between VDCs of the same switch Business and Technology Working as One
  • 35. Que beneficios tiene el Nexus 7000? New data center or network builds  Looking for a scalable platform for the future Highest levels of reliability  NX-OS modularity  In Service Software Upgrades  No Single Point of Failure High 10 GbE port count  Up to 256 ports of 10 Gb Ethernet Highest performance  Up to 230 Gb/sec per slot  Scalability to 40 Gb and 100 Gb Ethernet Customer plans to implement Unified I/O and FCoE Business and Technology Working as One 35
  • 36. Nexus 7000 and Catalyst 6500 SeriesOperational Management Features Additional Nexus 7000 ValueData Center Network Manager GUI based Element Manager Full featured XML Interface to programmatically interact withNetconf XML API Nexus 7000 & NX-OSConfiguration Checkpoint & Better protection from user & configuration errors, tighterRollback change managementVerify – Commit Model for ACL Dry run ACL settings before committing themWireshark Integration Simplified troubleshooting with integrated wiresharkNetflow Enhancements including HW Sampled Netflow. Larger Netflow table with ability toL2 Netflow track L2 Netflow StatisticsConnectivity Management Lights-out device management using out of band portsProcessor Common Features Embedded Element Manager (EEM) Catalyst 6500 Nexus 7000 Netflow, SPAN SNMP Business and Technology Working as One
  • 37. Nexus 7000 and Catalyst 6500 Series Scalability Features Catalyst 6500 Nexus 7000 Additional Nexus 7000 Value Higher bandwidth withTotal Bandwidth Today 720 Gbps 7.2 Tbps head room for growth 2 Tbps with Future 15+ Tbps with Future proof Data CenterTotal Bandwidth Scalability chassis future fabrics for scalability 768 / 2880 with Consolidate 1GE Servers inMax 10/100/1000 Ports 576 N2K a single chassisMaximum 10GE Ports 128 512TodayLine-rate 10GE Ports Today 34 128 High density solutionsLine-rate 10GE Ports 96 768FutureLine-rate 40/100GE 40GE – 96 40GE – 22Density 100GE - 32 Business and Technology Working as One
  • 38. Partnerships - Logicalis Management Sistemas Applications Aplicaciones Data Bases Sistemas Security Firewal IPS Anti l Virus Server Servers Blade Virtual Servers Storage BackUp Fiber Virtual Std Channel Storage Storage Network Core Agregacion Acesso Infra Cabling Cooling Energia Business and Technology Working as OneData Center | CONFIDENCIAL
  • 39. Q&A Business and Technology Working as One