Sot Server Virt DC A

e d u ca t io n se rv ice s co u rsew a re
SERVER VIRTUALIZATION IN A CLOUD-READY DATA CENTER
Server Virtualization in a Cloud-ready Data Center
Slide 1
2010 Juniper Networks, Inc. All rights reserved. | www.juniper.net | Proprietary and Confidential
Welcome to the Juniper Networks Server Virtualization in a Cloud Ready Data Center eLearning module.
SOT-SERVER-VIRT-DC-A
Juniper Networks, Inc.
Slide 2
2010 Juniper Networks, Inc. All rights reserved.
CONFIDENTIAL
www.juniper.net | 2
Throughout this module, you will find slides with valuable detailed information. You can stop any slide with the Pause button to study the details. You can also read the notes by using the Notes tab. You can click the Feedback link at anytime to submit suggestions or corrections directly to the Juniper Networks eLearning team.
Slide 3
Course Objectives
After successfully completing this course, you will be able to:
Discuss Server virtualization trends and technologies Explain new requirements introduced by server virtualization, related to:
High performance networks The converged data and storage network Network operation simplicity
Describe various infrastructure design considerations, including:

Network reference architect design Over-subscription and uplinks 10 Gigabyte links connecting to servers Operation simplicity with one network operating system
CONFIDENTIAL
www.juniper.net | 3
After successfully completing this course, youll be able to: Discuss server virtualization trends and technologies; Explain new requirements introduced by server virtualization, related to: High performance networks; The converged data and storage network; and Network operation simplicity. And finally, Describe various infrastructure design considerations, including: Network reference architect design; Over-subscription and uplinks; 10 Gigabyte links connecting to servers; and Operation simplicity with one network operating system.
Slide 4
Server Virtualization Trends in Cloud-Ready Data Center
Simplify infrastructure
Consolidate physical servers to virtual machines Improve server and network utilization Simplify network connectivity One Network OS
Accelerate deployment and scale on demand

Operate devices within days Support 100+ to 1000+ servers Provision through central management tool Integrate with private cloud DC
Improve SLA
HA and Reliability Maintainability
CONFIDENTIAL
www.juniper.net | 4
Server virtualization in the enterprise data center allows the simplification of infrastructure with consolidation, utilization improvement, and network connectivity. It also improves SLAs (Service level Agreements) with nonfunctional requirements such as high availability, reliability, and maintainability. The cloud-ready data center is aimed for high efficiency and scalability. It has the additional requirement of operating devices within days, with support of between 100+ and 1000+ servers. It is required to integrate with other private cloud data centers or public cloud data centers. Furthermore, it should be provisioned through central management tools.
Slide 5
Two Server Virtualization Technologies: IBM vs. VMware

~100 VMs ~ 10 VMs
[ source: IBM, VMware ]
CONFIDENTIAL
www.juniper.net | 5
There are two main server virtualization technologies available in todays market: IBM PowerVM, and VMware ESXO vSphere. These tools have four differences. First, they are based on different CPU architectures. PowerVM runs on PowerPC CPUs while ESX runs on Intel and AMD CPUs. They offer different virtualization capability. Each PowerVM system can run up to 100 virtual machines concurrently. The ESX server can run around 10 virtual machines. They use different terminologies. IBM prefers using client partition for the virtual machine, and VMware uses the virtual machine in a straightforward way. Both are aimed at different markets. IBMs PowerVM is well known for its reliability and high performance for the enterprise, while VMwares ESX is very popular in the SMB (Server Message Block) market.
Slide 6
Server Virtualization Concepts are Similar
Virtual Machines ( virtual CPU, Virtual Memory, Virtual Disk and Virtual Ethernet Adapter ) Virtual Switches Hypervisor
[ source: VMware Virtual Networking Concepts ]
CONFIDENTIAL
www.juniper.net | 6
Differences aside, the server virtualization concepts are similar. On the right side of the slide is the IBM Hypervisor, a suite of hardware and software enabled server virtualization, then the virtual switch which manages the network between the virtual machine and the physical server. The top layer is the virtual machine which includes virtual CPU, virtual memory, virtual disk, and virtual Ethernet adapter. On the left of the slide is the similar architecture of VMwares ESX suite.
Slide 7
Server Virtualization Deployment Introduces New Requirements in Data Center Networks
CONFIDENTIAL
www.juniper.net | 7
The left side of the slide represents the traditional standalone server with physical NIC deployment. On the right side is a typical PowerVM server virtualization network deployment. Many virtual machines run on one physical machine sharing the same physical needs. The data flows from the application through the virtual adaptor running on the virtual machine. The data can further be dispatched by the Hypervisor to a corresponding virtual adapter on the VIOS (Virtual Input/Output Server). The VIOS server is a special purpose virtual machine that manages the physical resources of networking and storage. The data is sent to the virtual switch that shows the Ethernet adapter on the VIOS. Furthermore, all the data is sent through an uplink to the physical adapter on the VIOS server and then out to the physical switch (represented here by the EX4200). It is then sent to other applications or to the clients. The server virtualization network deployment seems simple, but it introduces new requirements for the data center network design.
Slide 8
Server Virtualization Demands Connections between Virtual Switch and Physical Switch
vSwitch pSwitch (EX Series)
Layer 2 forwarding engine Layer 2 VLAN tagging, stripping, Filtering Layer 2 security Layer 2 HA, Redundant, CoS Layer 3 Protocols, HA Network Operating System
Software, racing condition on CPU

Support Limited, ACL N/A N/A N/A
Hardware, Scalability
Support + Port-based VLAN, MAC-based Port security, 802.1X VCP, HSRP, RTG, STP, 802.1p RIPv1/v2, OSPF, BGP, IS-IS, VRRP Junos, Configuration Management
CONFIDENTIAL
www.juniper.net | 8
First it demands connections between the virtual switch and physical switch. The virtual switch is the special purpose Layer 2 switch with limited function and security. This slide presents a brief comparison between the virtual switch and the physical switch. The virtual switch may cause a running or overload condition on the CPU and memory when network usage increases. The network design is required to consider the connections between these two switches in VLAN tagging and link aggregation.
Slide 9
Server Virtualization Demands High Performance Networks: High Throughput, 10Gbps Links
VMotion Needs high throughput
High throughput network is required for highly utilized Server Virtualization
[ source: VMware ]
CONFIDENTIAL
www.juniper.net | 9
Server virtualization demands high performance networks with high throughput. Server consolidation means many servers run on a physical server. The CPU and network utilization is improved significantly and network throughput requirements increase accordingly. Currently, quad port Ethernet NIC adapters (1Gbps NIC), is the most economical solution for the server virtualization. However, when virtualization capacity increases, and further reduction on space or rack usage is desired, server consolidation will adopt 10 Gbps network connections at the access layer.
10
Slide 10
Server Virtualization Demands Data- and Storageconverged Networks: COS, ISCSI/NFS

Network Supports Data and Storage (iSCSI/NFS) CoS is needed to secure network performance for prioritized application, LOB, and VM CoS is needed in data and storage converged networks
NFS/iSCSI
[ source: VMware ]
CONFIDENTIAL
www.juniper.net | 10
Converged data and storage networks with class of service are also required. Todays server virtualization supports network storage, which means that enterprise data centers are able to consolidate data in storage and network into one. Class of service is critical and essential for prioritizing many types of traffic on the same network. The traffic includes application production traffic, storage access through NFS (Network File System) and iSCSI (Internet Small Computer System Interface). VMwaress VMotion Traffic and Storage VMotion VMotion is about moving the computing running state from one computing location to another. In other words, it means copying the data in memory. The size of the data is typically between 2GB and 6GB. VMotion Storage enables live migration of the virtual machine disk file across the storage array. Storage VMotion allows customers to reallocate virtual machine disk files between and across shared storage locations, while maintaining continuous service availability and complete transaction integrity. Storage VMotion supports NFS and iSCSI. When Storage VMotion occurs, the whole virtual machine storage will be transferred from one storage location to another. The size of the data is typically between 20GB and 40GB or more. The high performance network with high throughput will process this massive volume efficiently and class of service (or CoS) will prevent any impact due to Storage VMotions traffic burst.
11
Slide 11
Cloud-ready Data Center Demands Provisioning and Data Simplicity

Simplifying Network operation with One Network Operating system on different network layers, and for different network functions. Provisioning Network Deployment efficiently, and maintain network infrastructure with minimum human effort and high maintainability
CONFIDENTIAL
In the cloud-ready data center, the number of virtual machines or virtual end points will be around 10,000 to 100,000. This demands simplifying network operation with one network operating system on different network layers, for different network functions. It also demands provisioning network deployment efficiently, and maintaining network infrastructure with minimum human effort and high maintainability.
12
Slide 12
Design Consideration (1): Cloud-ready Data Center Reference Architect

Core Layer
2-Tier Data Center Core networks Converged data and storage network in Access Layer
Access Layer
L2/L3 available in Access Layer Two Dedicated Virtual Chassis Access Switches: for Product network and Management network 10Gbps Connects to VMware ESX / vSphere, IBM POWERVM
Server Layer DMZ Web Storage APP DB
CONFIDENTIAL
Juniper has a Cloud-ready Data Center Reference Architect tool that can be used as a guideline to save effort and speed up deployment. The reference architect recommends 2-tier data center core networks: core layer and access layer. The access layer is highly recommended for the following considerations: It supports converged data and storage networks It provides Layer 2 and Layer 3 features It implements two dedicated Virtual Chassis Switches: one for production network, and another for management network. It provides optional 10Gbps connections to servers The reference architect also recommends one network operating system for core layer and access layer to achieve operation simplicity.
13
Slide 13
Design Consideration (2A): Top-of-Rack Virtual Chassis
2 TOR VCs (Active/Standby) 4 X 1Gbps LAG Server Connection 10Gbps LAG uplinks to Core layer
CONFIDENTIAL
Juniper considers top-of-rack (TOR) Virtual Chassis at the access layer. The screen shows the basic model to connect the IBM PowerVM in Junipers top-of-rack Virtual Chassis. Two sets of the EX4200 Virtual Chassis are configured and deployed at the top of the server racks, to form two paths to the servers in the active and the standby mode. Each server connects to the switch with four 1Gbps ports to form 4Gbps connections with link aggregation. The virtual switches will have a 10Gbps link aggregation uplink to the core layer.
14
Slide 14
Design Consideration (2B): 4~81Gbps Connections, and Optional 10Gbps Connections

HMC HMC IBM Power 570 systems IBM
10/100/1000 Base- TX PCI - X Adapter 10/100/1000 Base- PCI10 Gigabit Integrated Virtual Ethernet Adapter 10 10 Gigabit Ethernet Adapter 10 Virtual I/O Server Virtual Client Partition Operation System Client
Juniper Networks EX4200-48T, 48P Juniper EX4200JUNOS JUNOS

Virtual Chassis Virtual Uplink Module Uplink
Network Protocol Network

LAG & LACP LAG VLAN VLAN
CONFIDENTIAL
In the implementation guide, Juniper further describes the other three approaches on top of this basic model to achieve high availability, flexibility, and scalability with the IBM Power 570 system configuration.
15
Slide 15
Design Consideration (3A): VLAN Tagging Mode 1 in PowerVM
CONFIDENTIAL
IBMs PowerVM supports three virtual LAN tagging modes. By default, the client partition is VLAN-unaware. In this condition, the virtual switch port in the Hypervisor maintains tracking information for the Ethernet frames coming from and going to the client partition. They are interfaces behaving in access mode related to Junipers EX Series switches. In VLAN tagging mode two, the client partition is configured as VLAN-aware and the traffic is tagged before being delivered to the Hypervisor. The virtual switch port in Hypervisor filters the tagged traffic to or from client partitions acting as interface configured with trunk mode in the EX Series switch. In VLAN tagging mode three, the frames sent from these interfaces are decapsulated. The tagging is performed at the corresponding EX Series switch interfaces configured for access mode. A decision about which mode to deploy is related to how the network administrator and server administrator in a given case wants to manage VLANs within the network. How do the virtual machines in a PowerVM infrastructure appear to those VLANs? Typically VLAN tagging mode one is commonly used. This means that the VIOS trunks the client partitions VLAN traffic to the EX Series switch by setting the AO to the 1Q adapter in the VIOS, and configuring the corresponding EX Series switch interfaces for trunk mode operation.
16
Slide 16
Design Consideration (3B): VLAN Tagging VST Mode in VMware
CONFIDENTIAL
Similar to PowerVM VLAN tagging modes, VMware supports three VLAN tagging modes, depending on where the tagging occurs. Virtual switch tagging which means the tagging occurs at the virtual switch, which is internal to the Hypervisor; EX42 switch tagging the tagging occurs at the EX42 switch; and virtual guest tagging the tagging occurs at the virtual guest, or virtual machine. VST Virtual Switch Tagging mode is commonly used for the virtual machine production traffic, the V switch trunks, or the virtual machine production VLANs traffic to the EX Series switch. The corresponding EX Series switch interfaces are configured for trunk mode operation.
17
Slide 17
Design Consideration (4A): TOR Virtual Chassis Scalability
Deployment Assumption An 8-way CPU Power 570 (4U) hosts up to 80 client partitions. Each Power 570 Server connects to the switch with 1 LAG interface which is formed with four, 1 Gbps Ethernet interfaces. Each client partition uses an Ethernet adapter.
CONFIDENTIAL
Juniper also considers top-of-rack of Virtual Chassis scalability how it supports massive virtual machines deployment. At the access layer, the design should consider the maximum number of the MAC addresses to accommodate the implementation in full capacity. The MAC address learning rate should anticipate network converge time. For convenience, MAC addresses in the virtual machine are considered in this discussion. As the baseline deployment, assume an 8 CPU-powered system with 70 server hosts and up to 80 virtual machines concurrently. Each server connects to the EX4200 with 4Gbps link aggregation interfaces. Each client partition uses a virtual Ethernet adapter, which means each virtual machine has one MAC address. A single EX4200 is deployed to connect eight Power 570 servers, of which, in total, six 640 virtual machines run concurrently. Therefore, the total number of MAC addresses in this deployment is 640, which is lower than the maximum MAC table entries supported in the EX4200 switches. EX4200 supports a maximum of 24,000 MAC addresses. Assuming that all 640 client partitions boot at the same time, the EX4200 switches learn 640 MAC addresses within a second, because its MAC running rate is 700 MAC addresses per second. In another scenario, when the primary switch fails, or when a graceful shutdown occurs, the backup switch takes over and learns all the MAC addresses in this scenario within seconds.
18
Slide 18
Design Consideration (4B): TOR Virtual Chassis Scalability
MAC address per switch is 640 for different scenario MAC address per TOR VC is lower than MAC table entries supported by EX4200
CONFIDENTIAL
As listed in this table, by adding more EX4200 switches to the top-of-rack Virtual Chassis, one can easily scale up to connect more Power 570 systems. In the bottom row, with 7 EX4200 switches, the top-of-rack Virtual Chassis provides a maximum of 336 1Gbps interfaces, with an option of 14 uplink module ports to a group of the 56 Power 570 servers to support around 4500 concurrent running virtual machines. The top-of-rack Virtual Chassis supports 4500 MAC addresses in this scenario, which is lower than the maximum MAC table entries supported in EX4200. Notice that there are 640 MAC addresses per switch, which is a constant in different scenarios. The Virtual Chassis handles relearning the MAC addresses in the following two cases: 1. When one of the member switches fails, relearning MAC addresses is not required in the EX Series Virtual Chassis implementation because the CAM (Content Addressable Memory) tables are already populated among the member switches, including the failover switches. As a result, customers will not experience delay or loss due to relearning of the MAC addresses. Rather, they would experience delay caused by losing the uplink in the failed switch. 2. In rare failure cases, for example, if the top-of-rack Virtual Chassis fails, or a graceful shutdown occurs, the whole Virtual Chassis the other top of rack Virtual Chassis must relearn all the MAC addresses. It takes the Virtual Chassis approximately one second to relearn the MAC addresses, because each member switch relearns 640 MAC addresses within one second, and relearning occurs simultaneously across all the member switches.
19
Slide 19
Design Consideration (5A): Oversubscription Ratio and Uplinks
Oversubscription at the access layer = total active uplink bandwidth at server layer / total active uplink bandwidth at access layer. the oversubscription ratio 4.8:1 in Scenario 1 suggests 20Gbps uplink at access layer, shown in UPLINK BANDWIDTH@ACCESS LAYER column.
CONFIDENTIAL
To describe the flexibility of the configuration in a TOR of Virtual Chassis implementation at the access layer, two deployment scenarios are considered. Scenario one is a moderate scale deployment of 24 power servers in three racks. Scenario two is a large scale deployment of 56 Power 570 servers in seven racks. Each Power 570 with eight CPUs can run up to 80 concurrent virtual machines, and each rack can host eight 570 servers. Both scenarios, using link aggregation for the server connections, have a 4Gbps link aggregation interface in a single TOR Virtual Chassis. The oversubscription ratio is used to determine the gap between baseline and desired configuration on the uplink at the access layer to provide the configuration guideline. Here, the oversubscription is defined at the access layer, equal to total active uplink bandwidth at the server layer, divided by the total active uplink bandwidth at access layer. For example, the oversubscription ratio 4.8 to 1 in the first scenario, suggests a 20Gbps uplink at the access layer, because the uplink bandwidth at the server layer is 96Gbps. The 20Gbps uplink bandwidth at the access layer gives the guideline on the bandwidth. Considering the high availability at the access layer, two of these will be needed. They are running in active and passive mode. This represents two times 10Gbps uplink in the access layer column.
20
Slide 20
Design Consideration (5B): Oversubscription Ratio and Uplinks
CONFIDENTIAL
This slide further demonstrates the flexibility of the TOR Virtual Chassis configuration at the access layer, with six typical deployment scenarios, which are required to deploy different numbers of the Power 570 systems, different oversubscription ratios at the access layer, and different nonfunctional requirement configuration options. When considering the oversubscription ratio 4 to 1 in a scenario number three, the oversubscription ratio suggests six 10Gbps link aggregation uplink at the access layer. The server connections throughput may vary among scenarios 4, 5, and 6 due to the different requirements. If this oversubscription ratio is determined, the uplink throughput will be determined. The bandwidth between servers in the same rack is 4Gbps consistently because the EX4200 provides a line rate throughput between the different link aggregations within the same switch. The bandwidth between two servers in different racks will be calculated by the average bandwidth between servers, which connects to a different Virtual Chassis member switch.
21
Slide 21
Design Consideration (6): Provisioning and Operation Simplicity

S OAP S OAP
Services Menu
SM SM
DC DC
IM IM
B A C
MTOSI E XT-JS -JS MTOSI E XT --JS
EMS Apps EMS Apps
CMP
Auto Provisioning System MX S eries

Juniper Management Platform
A B
SRX Series
EX Series
SRX Series
A
EX4200
CONFIDENTIAL
Junos, the one operating system for routing, switching and security, runs on both the access and core layers in the data center networks, and is the ideal operating system for the cloud-ready data center, providing operation simplicity. It allows the leveraging of Junos ISSU (in-service software upgrade) and Junos Space Service Now to improve infrastructure maintainability. Junos XML API (application programming interface) and Junos Space can be considered to improve the network provisioning.
HTTP HTTP
22
Slide 22
Summary: Advantages of Junipers Design for Cloudready Data Centers

Scalable Simple Virtualized Efficient Reliable Secure Automated Open
1,000,000s of virtual endpoints, 10s of data centres, unmatched policy scale High performance platforms, common software + management, dynamic service creation Network elements, network services, end-to-end infrastructure
Low rack space + power
Comprehensive carrier-grade HA Unmatched capacity, distributed enforcement, centralized management Dynamic service creation, dynamic policy enforcement, extensible auto-configuration interfaces Extensive APIs at management + infrastructure levels, modular/scalable OS
CONFIDENTIAL
As discussed in this presentation, and in more detail in both IBM PowerVM and VMware implementation guides, some advantages of Junipers design for cloud-ready data centers were demonstrated: The EX Series TOR Virtual Chassis supports large scale virtual endpoints; Server virtualization requires high throughput, Class of Service and an optional 10Gbps uplink at the access layer; and Data center networks benefit from network efficiency and Junos operation simplicity.
23
Slide 23
Course Summary
In this course, you learned to:
Discuss Server virtualization trends and technologies Explain new requirements introduced by server virtualization, related to:
High performance networks The converged data and storage network Network operation simplicity
Describe various infrastructure design considerations, including:

Network reference architect design Over-subscription and uplinks 10 Gigabyte links connecting to servers Operation simplicity with one network operating system
CONFIDENTIAL
In this course, you learned to: Discuss server virtualization trends and technologies; Explain new requirements introduced by server virtualization, related to: High performance networks; The converged data and storage network; and Network operation simplicity. And finally, Describe various infrastructure design considerations, including: Network reference architect design; Over-subscription and uplinks; 10 Gigabyte links connecting to servers; and Operation simplicity with one network operating system.
24
Slide 24
Additional Resources
Education Services training classes
http://www.juniper.net/training/technical_education/
Juniper Networks Certification Program Web site

www.juniper.net/certification
Juniper Networks documentation and white papers

www.juniper.net/techpubs
To submit errata or for general questions

elearning@juniper.net
CONFIDENTIAL
For additional resources or to contact the Juniper Networks eLearning team, click the links on the screen.
25
Slide 25
Evaluation and Survey

You have reached the end of this Juniper Networks eLearning module You should now return to your Juniper Learning Center to take the Practice Test and the Student Survey
The test will allow you to gauge your knowledge of the material covered in this course The survey will allow you to give feedback on the quality and usefulness of the course
CONFIDENTIAL
You have now reached the end of this Juniper eLearning module. You should now return to your Juniper Learning Center to take the Practice Test and the Student Survey. The test will allow you to gauge your knowledge of the material covered in this course. The survey will allow you to give feedback on the quality and usefulness of the course.
26
Slide 26
2010 Juniper Networks, Inc.
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.
CONFIDENTIAL
Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, Junos, NetScreen and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. JunosE is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks or registered service marks are the property of their respective owners. Juniper Networks reserves the right to change, modify, transfer or otherwise revise this publication without notice.
27
Slide 27
CONFIDENTIAL
Thank you for participating in this Juniper eLearning presentation. Please feel free to contact Juniper with any questions.
28
ed u ca t i o n ser vic e s co u rsew a re
Co rp o rat e and Sal es Headq uart ers Junip er Net w orks, Inc. 119 4 Nort h Mat hil da Avenue Sunnyvale, CA 9 4 0 8 9 USA Phone: 8 8 8 .JUNIPER ( 8 8 8 .58 6 .4737) o r 4 0 8 .745 .20 0 0 Fax: 4 0 8 .74 5.210 0 w w w .juniper.net
APAC Headq uart ers Junip er Net w orks ( Hong Kong) 26 / F, Cit yp laza One 1111 Kings Road Taiko o Shing, Hong Kong Phone: 8 52.2332.36 36 Fax: 8 52.2574 .78 0 3
EMEA Head q uart ers Juniper Net w orks Irel and Airside Business Park Sw ord s, Count y Dub l in, Irel and Phone: 35.31.8 9 0 3.6 0 0 EMEA Sales: 0 0 8 0 0 .4 5 8 6 .4737 Fax: 35.31.8 9 0 3.6 0 1
Co pyright 20 10 Junip er Net w orks, Inc. Al l right s reserved. Junip er Net w orks, t he Juniper Net w orks logo, Junos, Net Screen, and ScreenOS are regist ered t radem arks o f Junip er Net w orks, Inc. in t he Unit ed St at es and o t her count ries. Al l o t her t rad em arks, service m arks, regist ered m arks, or regist ered service m arks are t he pro pert y of t heir respect ive ow ners. Juniper Net w o rks assum es no responsibil it y f or any inaccuracies in t his docum ent . Juniper Net w orks reserves t he right t o change, m od if y, t ransf er, or ot herw ise revise t his pub l icat ion w it hout not ice.

Sot Server Virt DC A

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Sot Server Virt DC A

Enviado por

Direitos autorais:

Formatos disponíveis

e d u ca t io n se rv ice s co u rsew a re

SERVER VIRTUALIZATION IN A CLOUD-READY DATA CENTER

Server Virtualization in a Cloud-ready Data Center

Server Virtualization in a Cloud-ready Data Center

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

2010 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

Describe various infrastructure design considerations, including:

2010 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

Server Virtualization Trends in Cloud-Ready Data Center

Accelerate deployment and scale on demand

2010 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

Two Server Virtualization Technologies: IBM vs. VMware

[ source: IBM, VMware ]

2010 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

Server Virtualization Concepts are Similar

[ source: VMware Virtual Networking Concepts ]

2010 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

Server Virtualization Deployment Introduces New Requirements in Data Center Networks

2010 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

Software, racing condition on CPU

2010 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

VMotion Needs high throughput

High throughput network is required for highly utilized Server Virtualization

2010 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

Server Virtualization Demands Data- and Storageconverged Networks: COS, ISCSI/NFS

2010 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

Cloud-ready Data Center Demands Provisioning and Data Simplicity

2010 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

Design Consideration (1): Cloud-ready Data Center Reference Architect

Server Layer DMZ Web Storage APP DB

2010 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

Design Consideration (2A): Top-of-Rack Virtual Chassis

2010 Juniper Networks, Inc. All rights reserved.

Juniper Networks, Inc.

Server Virtualization in a Cloud-ready Data Center

Design Consideration (2B): 4~81Gbps Connections, and Optional 10Gbps Connections

Juniper Networks EX4200-48T, 48P Juniper EX4200JUNOS JUNOS

Network Protocol Network

2010 Juniper Networks, Inc. All rights reserved.