VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview

Transcription

1 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Document revision 1.6 February 2016

2 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Revision history Revision history Date VCE System Document revision Description of changes February 2016 Gen Updated to include the following: 8 EMC X-Bricks, 20 TB 6 and 8 EMC X-Bricks, 40 TB November 2015 Gen Updated to include 40 TB EMC X-Brick October 2015 Gen Updated to include VMware vsphere 6.0 with Cisco Nexus 1000V Switch August 2015 Gen Updated to include VxBlock Systems. Added support for VMware vsphere 6.0 with VMware VDS on the VxBlock System and for existing Vblock Systems. February 2015 Gen Updated Intelligent Physical Infrastructure appliance information. December 2014 Gen Updates to Vblock System 540 Gen 2.0 October 2014 Gen Initial version 2

3 Contents VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Contents Introduction...5 Accessing VCE documentation...6 System overview...7 System architecture and components... 7 Base configurations and scaling...9 Connectivity overview...12 Network topology Compute layer overview...15 Compute overview...15 Cisco Unified Computing System...15 Cisco UCS fabric interconnects...16 Cisco Trusted Platform Module VCE bare metal support policy...16 Disjoint layer 2 configuration Storage layer overview...19 Storage layer hardware EMC XtremIO storage arrays EMC XtremIO storage array configurations and capacities EMC XtremIO storage array physical specifications Network layer overview...25 Network layer hardware Port utilization...26 Cisco Nexus 3064-T Switch - management networking Cisco Nexus 5548UP Switch Cisco Nexus 5596UP Switch Cisco Nexus 9396PX Switch Cisco MDS 9148S Multilayer Fabric Switch...28 Virtualization layer overview...30 Virtualization components VMware vsphere Hypervisor ESXi...30 VMware vcenter Server Management...34 Management components overview...34 Management hardware components...34 Management software components

4 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Contents Management network connectivity System infrastructure...38 Cabinets overview Intelligent Physical Infrastructure appliance Cabinet types Power options...39 Sample configurations Sample VCE Systems with EMC XtremIO Additional references Virtualization components Compute components Network components...46 Storage components

5 Introduction VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Introduction This document describes the high-level design of the VCE System. This document also describes the hardware and software components that VCE includes in the VCE System. In this document, the Vblock System and VxBlock System are referred to as VCE Systems. The VCE Glossary provides terms, definitions, and acronyms that are related to VCE. To suggest documentation changes and provide feedback on this book, send an to Include the name of the topic to which your feedback applies. 5

6 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Accessing VCE documentation Accessing VCE documentation Select the documentation resource that applies to your role. Role Customer Cisco, EMC, VMware employee, or VCE Partner VCE employee Resource support.vce.com A valid username and password are required. Click VCE Download Center to access the technical documentation. partner.vce.com A valid username and password are required. sales.vce.com/saleslibrary or vblockproductdocs.ent.vce.com 6

7 System overview VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview System overview System architecture and components VCE Systems are modular platforms with defined scale points that meet the higher performance and availability requirements of an enterprise's business-critical applications. VCE Systems are designed for deployments involving large numbers of VMs and users. VCE Systems provide the following features: Deliver a multi-controller, scale-out architecture with consolidation and efficiency for the enterprise Allow scaling of resources through common and fully redundant building blocks Use a SAN storage medium Note: Local boot disks are optional and available only for bare metal blades The following table shows the VCE System architecture: Component Cisco B-series blade chassis VCE Systems 64 chassis maximum with a full configuration of double height blades and a maximum of up four Cisco UCS domains Cisco B-series blades (maximum) Half-width = 192 Full-width = 192 Double-height = 128 Note: A minimum of six EMC X-Bricks are required to support maximum hosts. Back-end buses Data store type Boot path Two SAS loops per EMC X-Brick controller VMFS SAN Disk drives maximum Eight EMC X-Bricks = 200 Six EMC X-Bricks = 150 Four EMC X-Bricks = 100 Two EMC X-Bricks = 50 One EMC X-Brick = 25 7

8 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview System overview VCE Systems contains the following key hardware and software components: Resource Components VCE System management Virtualization and management VCE Vision Intelligent Operations consists of: VCE Vision Intelligent Operations System Library VCE Vision Intelligent Operations Plug-in for vcenter VCE Vision Intelligent Operations Compliance Checker VCE Vision Intelligent Operations API for System Library VCE Vision Intelligent Operations API for Compliance Checker VMware vsphere Server Enterprise Plus VMware vsphere ESXi VMware vcenter Server VMware vsphere Web Client VMware Single Sign-On (SSO) Service Cisco UCS C240 Servers for AMP-2HA EMC PowerPath/VE Cisco UCS Manager EMC XtremIO Management Server EMC Secure Remote Support (ESRS) EMC PowerPath Electronic License Manager Server (ELMS) Cisco Data Center Network Manager for SAN Compute Cisco UCS 5108 Server Chassis Cisco UCS B-Series M3 Blade Servers with Cisco UCS VIC 1240, optional port expander or Cisco UCS VIC 1280 Cisco UCS B-Series M4 Blade Servers with Cisco UCS VIC 1340, optional port expander or Cisco UCS VIC 1380 Cisco UCS 2204XP Fabric Extenders or Cisco UCS 2208XP Fabric Extenders Cisco UCS 6248UP Fabric Interconnects or Cisco UCS 6296UP Fabric Interconnects Network Cisco Nexus 5548UP Switches, Cisco Nexus 5596UP Switches, or Cisco Nexus 9396PX Switches Cisco Nexus 3064-T Switches (Optional) Cisco Nexus 1000V Series Switches (Optional) VMware vsphere Distributed Switch (VDS) (Optional) VMware NSX Virtual Networking Storage EMC XtremIO 10 TB (encryption capable) EMC XtremIO 20 TB (encryption capable) EMC XtremIO 40 TB (encryption capable) 8

9 System overview VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview The following scenarios benefit from VCE Systems with EMC XtremIO: Scenario Virtual Desktop Infrastructure (VDI) applications Virtual server applications High-performance database applications Benefit VDI applications, such as VMware Horizon View and Citrix XenDesktop deployments, with an excess of 1000 desktops that require: The ability to use full clone or linked clone technology interchangeably and without drawbacks Assured project success from pilot to large-scale deployment A fast, simple method of performing high volume cloning of desktops, even during production hours Virtual server applications, such as VMware vcloud Director deployments, in largescale environments that require: A simple, dynamic method of creating a large number of virtual machines, even during production hours Application scenarios requiring mixed read and write workloads that need to adapt to high degrees of growth over time. OLTP database, database test/developer environments, and database analytic applications such as Oracle and Microsoft SQL Server that require: Consistent, low I/O (<1ms) latency to meet the performance service level objectives of the database workload Multiple space-efficient test or development copies The ability to reduce database licensing costs (EMC XtremIO increases database server CPU utilization so fewer database CPU core licenses are needed) The VCE Release Certification Matrix provides a list of the certified versions of components for VCE Systems. For information about VCE System management, refer to the VCE Vision Intelligent Operations Technical Overview. Related information Accessing VCE documentation (see page 6) Base configurations and scaling In a VCE System, there is a base configuration that is a minimum set of compute and storage components, as well as fixed network resources. 9

10 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview System overview These components are integrated within one or more 28-inch 42U cabinets. Within the base configuration, you can customize the following hardware aspects: Hardware How it can be customized Compute blades Cisco UCS B-series blade type including Cisco UCS B-Series M3 Blade Servers and Cisco UCS B-Series M4 Blade Servers A minimum of four Cisco UCS B-Series blade servers per VCE System Compute chassis A minimum of two Cisco UCS Chassis per VCE System Up to sixteen Cisco UCS server chassis per Cisco UCS domain Up to four Cisco UCS domains (four pairs of fabric interconnects) Supports up to 128 half-width Cisco UCS blade servers per domain Supports up to 192 blade servers per VCE System Edge servers (with optional VMware NSX) Four to six Cisco UCS B-series Blade Servers, including the B200 M4 with VIC 1340 and VIC For more information, see the VCE VxBlock Systems for VMware NSX Architecture Overview. Network One pair of Cisco MDS 9148S Multilayer Switches One pair of Cisco Nexus 55xxUP or 9396XP Switches per VCE System One pair of Cisco Nexus 3064-T Switches per VCE System Storage One EMC XtremIO cluster per VCE System EMC XtremIO 40 TB cluster Contains one, two, four, six, or eight EMC X-Bricks with a maximum of 32 front-end ports Encryption Capable Supports drives depending on the configuration Each EMC X-Brick contains 25 x 1.6 TB Encryption Capable drives EMC XtremIO 20 TB cluster Contains one, two, four, and six or eight EMC X-Bricks with a maximum of 32 front-end ports Supports drives depending on the configuration Each EMC X-Brick contains 25 x 800 GB Encryption Capable drives EMC XtremIO 10 TB cluster Contains one, two, or four EMC X-Bricks with a maximum of 16 frontend ports Encryption capable Supports drives depending on the configuration Each EMC X-Brick contains 25 x 400 GB Encryption Capable drives Management hardware options The second generation of the Advanced Management Platform (AMP-2HA) is the high availability model that centralizes management components of the VCE System. The optional VMware NSX feature requires AMP-2HA Performance. 10

11 System overview VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Together, the components offer balanced CPU, I/O bandwidth, and storage capacity relative to the compute and storage arrays in the VCE System. All components have N+N or N+1 redundancy. Scaling up compute resources Compute resources can be scaled up as necessary to meet increasingly stringent requirements. The maximum supported configuration differs based on core components. To scale up compute resources, you can add blade packs and chassis activation kits when VCE Systems are built or after they are deployed. Cisco UCS blades are sold in packs of two, and include two identical Cisco UCS blades. The base configuration of each VCE System includes two blade packs. The maximum number of blade packs depends on the selected scale point. Each blade type must have a minimum of two blade packs as a base configuration and can be increased in single blade pack increments thereafter. Each blade pack is added along with license packs for the following software: Cisco UCS Manager (UCSM) VMware vsphere ESXi Cisco Nexus 1000V Series Switch (Cisco Nexus 1000V Advanced Edition only) (if required) EMC PowerPath/VE Note: License packs for VMware vsphere ESXi, Cisco Nexus 1000V Series Switch, and EMC PowerPath/VE are not available for bare metal blades. The Vblock System Blade Pack Reference provides a list of supported Cisco UCS blades. The power supplies and fabric extenders for all chassis are pre-populated and cabled, and all required Twinax cables and transceivers are populated. However, in base VCE System configurations, there are a minimum of two Cisco UCS 5108 Server Chassis. There are no unpopulated server chassis unless they are ordered that way. This limited licensing reduces the entry cost for VCE Systems. As more blades are added and additional chassis are required, chassis activation kits are added automatically to an order. The kit contains software licenses to enable additional fabric interconnect ports. Only enough port licenses for the minimum number of chassis to contain the blades are ordered. Add chassis activation kits up-front to allow for flexibility in the field or to initially spread the blades across a larger number of chassis. Optionally, add expansion cabinets with additional resources. Scaling up storage resources To scale up storage resources, you can add EMC X-Bricks to VCE Systems. Adding EMC X-Bricks might require a data migration service, depending on the cluster firmware. Additionally, EMC X-Bricks must be placed in contiguous RUs. VCE Systems place EMC XtremIO components in a dedicated rack. 11

12 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview System overview Related information Storage layer hardware (see page 19) Connectivity overview Components and interconnectivity within VCE Systems conceptually subdivide into compute, storage, and network layers are described. The following table describes the layers: Layer Compute Storage Network Description Contains the following compute power components: Cisco UCS blade servers Cisco UCS chassis Cisco UCS fabric interconnects Contains EMC XtremIO as the storage component. Contains the following components to provide switching and routing between the compute and storage layers within a VCE System, and between the VCE System and the external network: Cisco MDS switches Cisco Nexus switches All components incorporate redundancy into the design. Related information Compute layer (see page 15) Storage layer (see page 19) Network layer (see page 25) Network topology In the network topology for the VCE System, LAN and SAN connectivity is segregated into separate switches in the VCE System. LAN switching uses either the Cisco Nexus 9396PX Switch, Cisco Nexus 5548UP Switch, or Cisco Nexus 5596UP Switch. SAN switching uses the Cisco MDS 9148S Multilayer Fabric Switch. Note: The optional VMware NSX feature uses the Cisco Nexus 9396PX switches for LAN switching. For more information, see the VCE VxBlock Systems for VMware NSX Architecture Overview. 12

13 System overview VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview The compute layer connects to both the Ethernet and Fibre Channel (FC) components of the network layer. Cisco UCS fabric interconnects connect to the Cisco Nexus switches in the Ethernet network through 10 GbE port channels and to the Cisco MDS switches through port channels made up of multiple 8 Gb links. The storage layer consists of an EMC XtremIO storage array. The front-end IO modules connect to the Cisco MDS switches within the network layer over 8 Gb FC links. The following illustration shows a block storage configuration for the VCE System: 13

14 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview System overview SAN boot storage configuration VMware vsphere ESXi hosts always boot over the FC SAN from a 10 GB Boot LUN, which contains the hypervisor's locker for persistent storage of logs and other diagnostic files. The remainder of the storage can be presented as VMFS data stores or as raw device mappings (RDM). 14

15 Compute layer VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Compute layer Compute overview Cisco UCS B-Series Blades installed in the Cisco UCS chassis provide computing power within a VCE System. Fabric extenders (FEX) within the Cisco UCS chassis connect to Cisco fabric interconnects over converged Ethernet. Up to eight 10 GbE ports on each Cisco UCS fabric extender connect northbound to the fabric interconnects, regardless of the number of blades in the chassis. These connections carry IP and storage traffic. VCE uses multiple ports for each fabric interconnect for 8 Gb Fibre Channel (FC). These ports connect to Cisco MDS storage switches and the connections carry FC traffic between the compute layer and the storage layer. These connections also enable SAN booting of the Cisco UCS blades. Cisco Unified Computing System This topic provides an overview of the Cisco Unified Compute System (UCS) data center platform that unites compute, network, and storage access. Optimized for virtualization, the Cisco UCS integrates a low-latency, lossless 10 Gb Ethernet unified network fabric with enterprise-class, x86-based servers (the Cisco B-Series). VCE Systems contain a number of Cisco UCS 5108 Server Chassis. Each chassis can contain up to eight half-width Cisco UCS B-Series M3 and M4 Blade Servers, four full-width, or two double-height blades. The full-width, double-height blades must be installed at the bottom of the chassis. In a VCE System, each chassis also includes Cisco UCS fabric extenders and Cisco UCS B-Series Converged Network Adapters. VCE Systems powered by Cisco UCS offer the following features: Built-in redundancy for high availability Hot-swappable components for serviceability, upgrade, or expansion Fewer physical components than in a comparable system built piece by piece Reduced cabling Improved energy efficiency over traditional blade server chassis The Vblock System Blade Pack Reference provides a list of supported Cisco UCS blades. 15

16 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Compute layer Related information Accessing VCE documentation (see page 6) Cisco Unified Compute System fabric interconnects Cisco Unified Computing System (UCS) fabric interconnects provide network connectivity and management capabilities to the Cisco UCS blades and chassis. Cisco UCS fabric interconnects offer line-rate, low-latency, lossless 10 Gigabit Ethernet and Fibre Channel over Ethernet (FCoE) functions. VCE Systems use Cisco UCS 6248UP or Cisco UCS 6296UP Fabric Interconnects. The optional VMware NSX feature uses Cisco UCS 6296UP Fabric Interconnects to accommodate the port count needed for VMware NSX external connectivity (edges). For more information, see the VCE VxBlock Systems for VMware NSX Architecture Overview. Cisco Trusted Platform Module Cisco TPM provides authentication and attestation services that provide safer computing in all environments. Cisco TPM is a computer chip that securely stores artifacts such as passwords, certificates, or encryption keys that authenticate the VCE System. Cisco TPM is available by default within the VCE System as a component within the Cisco UCS B-Series M3 Blade Servers and Cisco UCS B-Series M4 Blade Servers, and is shipped disabled. The Vblock System Blade Pack Reference contains additional information about Cisco TPM. VCE supports only the Cisco TPM hardware. VCE does not support the Cisco TPM functionality. Because making effective use of the Cisco TPM involves the use of a software stack from a vendor with significant experience in trusted computing, VCE defers to the software stack vendor for configuration and operational considerations relating to the Cisco TPM. Related information VCE bare metal support policy Since many applications cannot be virtualized due to technical and commercial reasons, VCE Systems support bare metal deployments, such as non-virtualized operating systems and applications. 16

17 Compute layer VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview While it is possible for VCE Systems to support these workloads (with caveats noted below), due to the nature of bare metal deployments, VCE is able to provide only reasonable effort" support for systems that comply with the following requirements: VCE Systems contain only VCE published, tested, and validated hardware and software components. The VCE Release Certification Matrix provides a list of the certified versions of components for VCE Systems. The operating systems used on bare-metal deployments for compute and storage components must comply with the published hardware and software compatibility guides from Cisco and EMC. For bare metal configurations that include other hypervisor technologies (Hyper-V, KVM, etc.), those hypervisor technologies are not supported by VCE. VCE Support is provided only on VMware Hypervisors. VCE reasonable effort support includes VCE acceptance of customer calls, a determination of whether a VCE System is operating correctly, and assistance in problem resolution to the extent possible. VCE is unable to reproduce problems or provide support on the operating systems and applications installed on bare metal deployments. In addition, VCE does not provide updates to or test those operating systems or applications. The OEM support vendor should be contacted directly for issues and patches related to those operating systems and applications. Related information Accessing VCE documentation (see page 6) Disjoint layer 2 configuration In the disjoint layer 2 configuration, traffic is split between two or more different networks at the fabric interconnect to support two or more discrete Ethernet clouds. The Cisco UCS servers connect to two different clouds. Upstream disjoint layer 2 networks allow two or more Ethernet clouds that never connect to be accessed by VMs located in the same Cisco UCS domain. 17

18 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Compute layer The following illustration provides an example implementation of disjoint layer 2 networking into a Cisco UCS domain: Virtual port channels (VPCs) 101 and 102 are production uplinks that connect to the network layer of the VCE Systems. Virtual port channels 105 and 106 are external uplinks that connect to other switches. If you use Ethernet performance port channels (103 and 104 by default), port channels 101 through 104 are assigned to the same VLANs. Disjoint layer 2 network connectivity can also be configured with an individual uplink on each fabric interconnect. 18

19 Storage layer VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Storage layer Storage layer hardware This topic provides an overview of the storage layer hardware for EMC XtremIO. EMC XtremIO fully leverages the properties of random access flash media. The resulting system addresses the demands of mixed workloads with superior random I/O performance, instant response times, scalability, flexibility, and administrator agility. EMC XtremIO delivers consistent low latency response times (below <1 ms) with a set of non-stop data services. Features include: Inline data reduction and compression Thin provisioning Snapshots percent availability enhances host performance Unprecedented responsiveness for enterprise applications The EMC XtremIO Management Server is a virtual machine that provides a browser-based GUI for device creation, management, and monitoring of EMC XtremIO storage arrays. Related information EMC XtremIO storage array configurations and capacities (see page 22) EMC XtremIO storage arrays (see page 19) EMC XtremIO storage array physical specifications (see page 23) EMC XtremIO storage arrays This topic provides an overview of the common EMC XtremIO storage array characteristics across all EMC XtremIO models. The following illustration shows the interconnection of EMC XtremIO in VCE Systems. EMC XtremIO storage arrays include the following features: Two 8 Gb Fibre Channel (FC) ports per controller (four per EMC X-Brick) 25 drives per EMC X-Brick Encryption capable 19

20 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Storage layer All EMC X-Bricks within the cluster must be the same type All EMC XtremIO cluster components must reside in the same cabinet in contiguous RUs Note: Depending on the firmware version, EMC X-Bricks seven and eight can be placed in an adjacent cabinet for non-disruptive expansion of the cluster. The maximum number of supported hosts depends on the number of EMC X-Bricks in the configuration. VCE recommends that while the maximum number of initiators per EMC XtremIO cluster is 1024, the recommended limit of initiators is 64 per FC port for performance. 20

21 Storage layer VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Fan-in ratio The following table provides the sizing guidelines for the VCE Systems at 32:1 best practice for performance fan-in ratio: EMC X-Bricks FC ports FC ports per host Maximum number of physical hosts Half-width blades The maximum number of hosts supported with half-width blades depends on the number of EMC X- Bricks: EMC X-Bricks Physical host maximum* Full-width blades The maximum number of hosts supported with full-width blades depends on the number of EMC X-Bricks: EMC X-Bricks Physical host maximum*

22 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Storage layer Double-height blades The maximum number of hosts supported with double-height blades depends on the number of EMC X- Bricks: EMC X-Bricks Physical host maximum* ** 8 128** * Physical host maximums aggregate across all blade types and form factors. ** Due to a 512 slot maximum across four Cisco UCS domains, a maximum of 128 double-height blades are supported in VCE Systems. The recommended fan in ratio for high IOPS workloads for EMC XtremIO front-end ports is 32:1. Higher ratios can be achieved based on the workload profile. Proper sizing of the EMC XtremIO is crucial to ensure that the EMC XtremIO front-end ports are not saturated. EMC XtremIO storage array configurations and capacities To deploy the EMC X-Bricks, use the following configurations and capacities for EMC XtremIO storage arrays. VCE Systems support the following options for EMC XtremIO: 10 TB EMC X-Brick (encryption capable) 20 TB EMC X-Brick (encryption capable) 40 TB EMC X-Brick (encryption capable) Note: If additional EMC X-Bricks are added to clusters post-deployment, a data migration professional services engagement is required. VCE recommends planning for future growth during the initial purchase. Supported standard configurations (tier 1) Model Encryption Drive size EMC X-Brick cluster One Two Four Six Eight 10 TB Y 400 GB N/A N/A 20 TB Y 800 GB

23 Storage layer VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Model Encryption Drive size EMC X-Brick cluster One Two Four Six Eight 40 TB Y 1.6 TB EMC XtremIO 10 TB capacities Capacity EMC X-Brick cluster One Two Four Raw (TB) Usable (TiB) EMC XtremIO 20 TB capacities Capacity EMC X-Brick cluster One Two Four Six Eight Raw (TB) Usable (TiB) EMC XtremIO 40 TB capacities Capacity EMC X-Brick cluster One Two Four Six Eight Raw (TB) Usable (TiB) EMC XtremIO storage array physical specifications This topics provides an overview of the EMC XtremIO physical specifications. Physical specifications Each EMC X-Brick consists of the following components: Two EMC X-Brick Controllers One EMC X-Brick disk array enclosure (DAE) Two (single EMC X-Brick system) or one (multiple EMC X-Brick system) battery backup units (BBU) A pair of EMC Infiniband switches are required in two, four, six, or eight EMC X-Brick clusters. 23

24 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Storage layer The following table provides physical specifications for each component: Device RU Weight (lbs) Typical power consumption C14 power sockets EMC X-Brick controller 1U W 2 EMC X-Brick DAE 2U W 2 Battery backup unit 1U 44 N/A 1 EMC Infiniband switches* 3U 41 65W 4 *Two 1U switches and 1U for cabling. The following table provides the total RU for each EMC X-Brick: Model One EMC X-Brick Two EMC X-Brick cluster Four EMC X-Brick cluster Six EMC X- Brick cluster Eight EMC X-Brick cluster 10 TB (encrypted) 6U 13U 23U N/A N/A 20 TB (encrypted) 6U 13U 23U 33U 33U+10** 40 TB (encrypted) 6U 13U 23U 33U 33U+10** Because VCE cabinets are 42U, split the EMC X-Bricks between two cabinets as (6+2) EMC X-Bricks. 24

25 Network layer VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Network layer Network layer hardware The LAN network layer and SAN network layer make up the network layer of the VCE System. Each VCE System includes two Cisco Nexus 9396PX Switches, two Cisco Nexus 5548UP Switches, or two Cisco Nexus 5596UP Switches. LAN network layer Each VCE System requires a pair of Cisco Nexus 3064-T Switches for all device management connectivity and management traffic within the VCE System.. Each Cisco Nexus 3064-T Switch provides 48 ports of 100/1000/10 Gb twisted pair connectivity and four QSFP+ ports. The 48 ports on each switch provide management interface connectivity for all devices in the VCE System. The Cisco Nexus 5548UP Switch, Cisco Nexus 5596UP Switch, and Cisco Nexus 9396PX Switch in the network layer provide 10 Gb connectivity using SFP+ modules for all VCE System production traffic. The following table shows LAN network layer components: Component Description Cisco Nexus 5548UP Switch 1RU appliance Supports 32 fixed 10 Gbps SFP+ ports Expands to Gbps SFP+ ports through an available expansion module Cisco Nexus 5596UP Switch 2RU appliance Supports 48 fixed 10 Gbps SFP+ ports Expands to Gbps SFP+ ports through three available expansion slots Cisco Nexus 9396PX Switch 2RU appliance Supports 48 fixed 10 Gbps SFP+ ports and 12 fixed 40 Gbps QSFP+ ports Cisco Nexus 3064-T Switch 1RU appliance Supports 48 fixed, 10GBase-T RJ45 ports and four fixed, 40 Gbps QSFP+ ports for the management layer of the VCE System SAN network layer VCE Systems contain two Cisco MDS switches to provide Fibre Channel (FC) connectivity between the compute and storage layer components. These switches comprise two separate fabrics. Connections from the storage components provide 8 Gb of bandwidth. Cisco UCS fabric interconnects provide a FC port channel of four 8 Gb connections (32 Gb bandwidth) to each fabric. This can be increased to eight connections for 64 Gb bandwidth or sixteen connections for 128 Gb bandwidth. These connections also facilitate SAN booting of the blades in the compute layer. 25

26 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Network layer Two Cisco MDS 9148S Multilayer Fabric Switches provide: FC connectivity between the compute layer components and the storage layer components Connectivity for backup and business continuity requirements when configured Note: Inter-Switch Links (ISLs) to existing SAN or between switches is not permitted. Cisco MDS 9148S Multilayer Fabric Switches provide 12 to 48 line-rate ports for non-blocking 16 Gbps throughput. 24 are licensed; additional ports can be licensed as needed. Port utilization This section describes the switch port utilization for Cisco Nexus switches in the networking configuration. Cisco Nexus 3064-T Switch - management networking The base Cisco Nexus 3064-T Switch provides Mbps/1GbE/10GbE Base-T fixed ports and 4- QSFP+ ports to provide 40GbE connections. The following table shows core connectivity for the Cisco Nexus 3064-T Switch for management networking and reflects the AMP-2 HA base for two servers: Feature Used ports Port speeds Media Management uplinks from fabric interconnect (FI) 2 1GbE Cat6 Uplinks to customer core 2 Up to 10G Cat6 VPC peer links 2QSFP+ 10GbE/40GbE Cat6/MMF 50µ/125 LC/LC Uplinks to management 1 1GbE Cat6 Cisco Nexus management ports 1 1GbE Cat6 Cisco MDS management ports 2 1GbE Cat6 AMP2-CIMC ports 1 1GbE Cat6 AMP2-Gi ports 2 1GbE Cat6 AMP2-10G ports 2 10GbE Cat6 EMC VNXe management ports 1 1GbE Cat6 EMC VNXe_NAS ports 4 10GbE Cat6 EMC XtremIO Controllers 2 per EMC X-Brick 1GbE Cat6 Gateways Mb/1GbE Cat6 26

27 Network layer VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview The remaining ports in the Cisco Nexus 3064-T Switch provide support for additional domains and their necessary management connections. Related information Management components overview (see page 34) Cisco Nexus 5548UP Switch The base Cisco Nexus 5548UP Switch provides 32 SFP+ ports used for 1G or 10G connectivity for LAN traffic. The following table shows the core connectivity for the Cisco Nexus 5548UP Switch (no module): Feature Used ports Port speeds Media Uplinks from fabric interconnect (FI) 8 10G Twinax Uplinks to customer core 8 Up to 10G SFP+ Uplinks to other Cisco Nexus 55xxUP Switches 2 10G Twinax Uplinks to management 3 10G Twinax Customer IP backup 4 1G or 10G SFP+ If an optional 16 unified port module is added to the Cisco Nexus 5548UP Switch, there are 28 additional ports are available to provide additional network connectivity. Cisco Nexus 5596UP Switch The base Cisco Nexus 5596UP Switch provides 48 SFP+ ports used for 1G or 10G connectivity for LAN traffic. The following table shows core connectivity for the Cisco Nexus 5596UP Switch (no module): Feature Used ports Port speeds Media Uplinks from Cisco UCS fabric interconnect 8 10G Twinax Uplinks to customer core 8 Up to 10G SFP+ Uplinks to other Cisco Nexus 55xxUP Switches 2 10G Twinax Uplinks to management 2 10G Twinax 27

28 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Network layer The remaining ports in the base Cisco Nexus 5596UP Switch (no module) provide support for the following additional connectivity option: Feature Used ports Port speeds Media Customer IP backup 4 1G or 10G SFP+ If an optional 16 unified port module is added to the Cisco Nexus 5596UP Switch, additional ports are available to provide additional network connectivity. Cisco Nexus 9396PX Switch The base Cisco Nexus 9396PX Switch provides 48 SFP+ ports used for 1G or 10G connectivity and 12 40G QSFP+ ports for LAN traffic. The following table shows core connectivity for the Cisco Nexus 9396PX Switch: Feature Used ports Port speeds Media Uplinks from fabric interconnect 8 10G Twinax Uplinks to customer core 8(10G)/2(40G) Up to 40G SFP+/QSFP+ VPC peer links 2 40G Twinax Uplinks to management 2 10G Twinax The remaining ports in the Cisco Nexus 9396PX Switch provide support for a combination of the following additional connectivity options: Feature Available ports Port speeds Media Customer IP backup 8 1G or 10G SFP+ Uplinks from Cisco UCS FIs for Ethernet BW enhancement 8 10G Twinax Cisco MDS 9148S Multilayer Fabric Switch This section describes port utilization for Cisco MDS 9148S Multilayer Fabric Switch networking configurations. VCE Systems incorporate the Cisco MDS 9148S Multilayer Fabric Switch to provide Fibre Channel (FC) connectivity from storage to compute. The Cisco MDS 9148S Multilayer Fabric Switch is a fixed switch with no IOM expansion for additional ports. The Cisco MDS 9148S Multilayer Fabric Switch provides connectivity for up to 48 ports from Cisco UCS fabric interconnects and an EMC XtremIO storage array that supports up to eight EMC X-Bricks. The Cisco MDS 9148S Multilayer Fabric Switch uses dynamic port mapping. There are no port reservations. 28

29 Network layer VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview For fabric interconnect (FI) connectivity to the SAN, all FI domains use four, eight, or 16 FC connections from the Cisco UCS FI switches to the Cisco MDS switches. For the storage array, each EMC X-Brick provides four FC ports. VCE connects two FC ports from each EMC X-Brick to each SAN fabric. VCE only supports FC connectivity for the VCE System. The following table shows connectivity for the Cisco MDS 9148S Multilayer Fabric Switch with available ports for EMC XtremIO: Domains Domain Maximum storage ports Total FI FC ports

30 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Virtualization layer Virtualization layer Virtualization components VMware vsphere is the virtualization platform that provides the foundation for the private cloud. The core VMware vsphere components are the VMware vsphere ESXi and VMware vcenter Server for management. Depending on the version that you are running, VMware vsphere 5.x includes a Single Sign-on (SSO) component as a standalone Windows server or as an embedded service on the vcenter server.vmware vsphere 6.0 includes a pair of Platform Service Controller Linux appliances to provide the Single Sign-on (SSO) service. The hypervisors are deployed in a cluster configuration. The cluster allows dynamic allocation of resources, such as CPU, memory, and storage. The cluster also provides workload mobility and flexibility with the use of VMware vmotion and Storage vmotion technology. VMware vsphere Hypervisor ESXi The VMware vsphere Hypervisor ESXi runs in the management servers and in VCE Systems using VMware vsphere Server Enterprise Plus. The lightweight hypervisor requires very little space to run (less than six GB of storage required to install) and has minimal management overhead. VMware vsphere ESXi does not contain a console operating system. The VMware vsphere Hypervisor ESXi boots from the SAN through an independent Fibre Channel (FC) LUN presented from the EMC storage array to the compute blades. The FC LUN also contains the hypervisor's locker for persistent storage of logs and other diagnostic files to provide stateless computing within VCE Systems. The stateless hypervisor (PXE boot into memory) is not supported. Cluster configuration VMware vsphere ESXi hosts and their resources are pooled together into clusters. These clusters contain the CPU, memory, network, and storage resources available for allocation to virtual machines (VMs). Clusters can scale up to a maximum of 32 hosts for VMware vsphere 5.1/5.5 and 64 hosts for VMware vsphere 6.0. Clusters can support thousands of VMs. The clusters can also support a variety of Cisco UCS blades running inside the same cluster. Note: Some advanced CPU functionality might be unavailable if more than one blade model is running in a given cluster. Data stores VCE Systems support a mixture of data store types: block level storage using VMFS or file level storage using NFS. The maximum size per VMFS volume is 64 TB (50 TB 1 MB). Beginning with 30

31 Virtualization layer VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview VMware vsphere 5.5, the maximum VMDK file size is 62 TB. Each host/cluster can support a maximum of 255 volumes. VCE optimizes the advanced settings for VMware vsphere ESXi hosts that are deployed in VCE Systems to maximize the throughput and scalability of NFS data stores. VCE Systems currently support a maximum of 256 NFS data stores per host. Virtual networks Virtual networking in the Advanced Management Platform uses the VMware Virtual Standard Switch (VSS). Virtual networking is managed by either the Cisco Nexus 1000V distributed virtual switch or VMware vsphere Distributed Switch (VDS). The Cisco Nexus 1000V Series Switch ensures consistent, policy-based network capabilities to all servers in the data center by allowing policies to move with a VM during live migration. This provides persistent network, security, and storage compliance. Alternatively, virtual networking in VCE Systems is managed by VMware VDS with comparable features to the Cisco Nexus 1000V where applicable. The VMware VDS option consists of both a VMware VSS and a VMware VDS and uses a minimum of four uplinks presented to the hypervisor. The implementation of Cisco Nexus 1000V for VMware vsphere 5.1/5.5 and VMware VDS for VMware vsphere 5.5 use intelligent network Class of Service (CoS) marking and Quality of Service (QoS) policies to appropriately shape network traffic according to workload type and priority. With VMware vsphere 6.0, QoS is set to Default (Trust Host). The vnics are equally distributed across all available physical adapter ports to ensure redundancy and maximum bandwidth where appropriate. This provides general consistency and balance across all Cisco UCS blade models, regardless of the Cisco UCS Virtual Interface Card (VIC) hardware. Thus, VMware vsphere ESXi has a predictable uplink interface count. All applicable VLANs, native VLANs, MTU settings, and QoS policies are assigned to the virtual network interface cards (vnics) to ensure consistency in case the uplinks need to be migrated to the VMware vsphere Distributed Switch (VDS) after manufacturing. VMware vcenter Server This topic describes the VMware vcenter Server which is a central management point for the hypervisors and VMs. VMware vcenter is installed on a 64-bit Windows Server. VMware Update Manager is installed on a 64- bit Windows Server and runs as a service to assist with host patch management. VMware vcenter Server provides the following functionality: Cloning of VMs Template creation VMware vmotion and VMware Storage vmotion Initial configuration of VMware Distributed Resource Scheduler (DRS) and VMware vsphere high-availability clusters 31

32 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Virtualization layer VMware vcenter Server also provides monitoring and alerting capabilities for hosts and VMs. System administrators can create and apply alarms to all managed objects in VMware vcenter Server, including: Data center, cluster, and host health, inventory, and performance Data store health and capacity VM usage, performance, and health Virtual network usage and health Databases The back-end database that supports VMware vcenter Server and VUM is Microsoft SQL Authentication VMware Single Sign-On (SSO) Service integrates multiple identity sources including Active Directory, Open LDAP, and local accounts for authentication. VMware SSO is available in VMware vsphere 5.x and later. VMware vcenter Server, Inventory, Web Client, SSO, Core Dump Collector, and VUM run as separate Windows services, which can be configured to use a dedicated service account depending on security and directory services requirements. VCE supported features VCE supports the following VMware vcenter Server features: VMware SSO Service (version 5.x and later) VMware vsphere Web Client (used with VCE Vision Intelligent Operations) VMware vsphere Distributed Switch (VDS) VMware vsphere High Availability VMware DRS VMware Fault Tolerance VMware vmotion Layer 3 capability available for compute resources (version 6.0 and higher) VMware Storage vmotion Raw Device Maps Resource Pools Storage DRS (capacity only) 32

33 Virtualization layer VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Storage-driven profiles (user-defined only) Distributed power management (up to 50 percent of VMware vsphere ESXi hosts/blades) VMware Syslog Service VMware Core Dump Collector VMware vcenter Web Services Related information Management components overview (see page 34) 33

34 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Management Management Management components overview The Advanced Management Platform (AMP-2HA) provides a single management point for VCE Systems. The AMP-2HA provides the ability to: Run the Core and VCE Optional Management Workloads Monitor and manage VCE System health, performance, and capacity Provide network and fault isolation for management Eliminate resource overhead on VCE Systems The Core Management Workload is the minimum set of required management software to install, operate, and support VCE Systems. This includes all hypervisor management, element managers, virtual networking components (Cisco Nexus 1000V or VMware vsphere Distributed Switch (VDS)), and VCE Vision Intelligent Operations Software. The VCE Optional Management Workload is non-core Management Workloads, which are supported and installed by VCE, and whose primary purpose is to manage components within VCE Systems. The list includes but is not limited to EMC Data Protection, security, or storage management tools such as EMC Avamar Administrator, EMC InsightIQ for Isilon, and VMware vcns appliances (vshield Edge/Manager). Management hardware components The second generation of the Advanced Management Platform (AMP-2HA) is available with two or three physical servers that use their own resources to run workloads without consuming resources on VCE Systems. The following table provides an overview of the AMP-2HA physical servers: Option Physical server Storage Description AMP-2HA Base Two Cisco UCS C240 servers FlexFlash SD for VMware vsphere ESXi boot EMC VNXe3200 for file VM data stores Implements VMware vsphere HA/DRS with shared storage provided by the EMC VNXe3200. AMP-2HA Performance Three Cisco UCS C240 servers FlexFlash SD for VMware vsphere ESXi boot EMC VNXe3200 for file VM data stores Adds a third Cisco UCS C240 Server and additional storage for EMC FAST VP. 34

35 Management VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Management software components Software is delivered pre-configured with the second generation of the Advanced Management Platform (AMP-2HA). AMP-2HA is delivered pre-configured with the following software components which are dependent on the selected VCE Release Certification Matrix: Microsoft Windows Server 2008 R2 SP1 Standard x64 Microsoft Windows Server 2012 R2 Standard x64 VMware vsphere Enterprise Plus VMware vsphere Hypervisor ESXi VMware Single Sign-On (SSO) Service VMware vsphere Web Client Service VMware vsphere Inventory Service VMware vcenter Server Vmware vcenter Database using Microsoft SQL Server 2012 Standard Edition VMware vcenter Update Manager VMware vsphere client VMware vsphere Syslog Collector service (optional) VMware vsphere Core Dump service (optional) VMware vsphere Distributed Switch (VDS) or Cisco Nexus 1000V virtual supervisor module (VSM) EMC PowerPath/VE Electronic License Management Server (ELMS) EMC Secure Remote Support (ESRS) Array Management modules, including, but not limited to, EMC XtremIO Management Server and PowerPath Viewer Cisco Prime Data Center Network Manager and Device Manager (Optional) EMC RecoverPoint management software that includes EMC RecoverPoint Management Application and EMC RecoverPoint Deployment Manager 35

36 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Management Management network connectivity This topic provides an overview of Advanced Management Platform (AMP-2HA) network connectivity and server assignments. AMP-2HA network connectivity The following illustration provides an overview of the network connectivity for AMP-2HA: 36

37 Management VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview AMP-2HA server assignments The following illustration provides an overview of the VM server assignment for AMP-2HA: Note: VCE Systems that use VMware vsphere Distributed Switch (VDS) do not include Cisco Nexus 1000V virtual supervisor module (VSM) VMs. 37

38 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview System infrastructure System infrastructure Cabinets overview In each VCE System, the compute and network layer components are distributed within the cabinets. Distributing the components in this manner balances out the power draw and reduces the size of the power distribution units (PDUs) that are required. Each cabinet has a capacity for physical dimensions such as weight, heat dissipation, power draw, RU space, and receptacle count. This design improves flexibility when upgrading or expanding VCE Systems as capacity needs increase. For some configurations, VCE preinstalls all wiring based on the predefined layouts. VCE cabinets are designed to be installed contiguously to one another within the data center. If the base and expansion cabinets need to be physically separated, customized cabling is needed, which incurs additional cost and delivery delays. Note: The cable length is not the same as distance between cabinets. The cable must route through the cabinets and through the cable channels overhead or in the floor. Related information Power options (see page 39) Intelligent Physical Infrastructure appliance The Intelligent Physical Infrastructure (IPI) appliance allows users to collect and monitor environmental data, and monitor control power and security. For more information about the IPI appliance, refer to the administration guide for your VCE System and to the VCE Intelligent Physical Infrastructure (IPI) Appliance User Manual. Related information Accessing VCE documentation (see page 6) Cabinet types This topic provides an overview of the sample cabinets for VCE Systems. 38

39 System infrastructure VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Sample compute and network cabinet A sample compute and network cabinet can contain: Cisco Nexus 5548UP, Cisco Nexus 5596UP, or Cisco Nexus 9396PX Switches Cisco Nexus 3064-T Switches Cisco MDS 9148S Switches Cisco UCS C240 Servers EMC VNXe3200 Cisco Nexus 6248UP or Cisco Nexus 6296UP Fabric Interconnects Cisco UCS 5108 Server Chassis EMC XtremIO storage array cluster If VCE System configurations expand, a compute and network expansion cabinet can be added for additional Cisco UCS 5108 chassis. This modular design makes it easier to add hardware later if necessary. The compute and network expansion cabinet can be expanded in a modular configuration. Power options VCE Systems support several power distribution unit (PDU) options inside and outside of North America. Power options for VCE System cabinets The following table lists the PDUs that are available: PDU Power specifications Number per CN or S IEC P+PE 3-phase Delta / 60A 2 pairs of PDUs per cabinet NEMA L15-30P 3-phase Delta / 30A 3 pairs of PDUs per cabinet NEMA L6-30P Single phase / 30A 3 pairs of PDUs per cabinet IEC P+N+PE 3-phase WYE / 30 / 32A / 2 pairs of PDUs per cabinet IEC P+E Single phase / 32A 3 pairs of PDUs per cabinet 39

40 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview System infrastructure Balancing cabinet maximum usable power The VCE System maximum usable power must be balanced in the cabinets based on the amount of components in the cabinet. The maximum kilowatt draw for a VCE System PDU that has been derated to 80 percent is listed in the following table: Power option Kilowatt draw per PDU 3-Phase Delta 60A@208V Phase Delta 30A@208V Phase WYE 32A@230V 17.7 Single Phase 30A@208V 5 Single Phase 32A@230V 5.9 Note: The kilowatt draw per PDU is an approximate measurement. The following PDU limitations per cabinet are for a VCE System with one or more Cisco UCS 5108 Blade Server Chassis installed: Power option Number of Cisco UCS 5108 Blade Server Chassis Maximum PDUs per cabinet Three-Phase Delta 60A 1-3 One pair Three-Phase Delta 60A 4-6 Two pair Three-Phase Delta 30A 1-3 Two pair Three-Phase Delta 30A 4 Three pair Three-Phase WYE 30A or 32A 1-3 One pair Three-Phase WYE 30A or 32A 4-6 Two pair Single Phase 30A or 32A 1 Two pair Single Phase 30A or 32A 2 Three pair Related information Accessing VCE documentation (see page 6) 40

41 Sample configurations VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Sample configurations Sample VCE System with EMC XtremIO VCE System cabinet elevations vary based on the specific configuration requirements. The following elevations are provided for sample purposes only. Note that storage cabinets are not shown. For specifications for a specific VCE System design, consult your varchitect. VCE System with EMC XtremIO cabinet front 41

42 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Sample configurations VCE System with EMC XtremIO cabinet rear 42

43 Sample configurations VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview VCE System with EMC XtremIO cabinet 1 43

44 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Sample configurations VCE System with EMC XtremIO cabinet 2 44

45 Sample configurations VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview VCE System with EMC XtremIO cabinet 3 45

46 VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Additional references Additional references Virtualization components Product Description Link to documentation VMware vcenter Server VMware vsphere ESXi Provides a scalable and extensible platform that forms the foundation for virtualization management. Virtualizes all application servers and provides VMware high availability (HA) and dynamic resource scheduling (DRS). vcenter-server/ vsphere/ Compute components Product Description Link Cisco UCS B-Series Blade Servers Servers that adapt to application demands, intelligently scale energy use, and offer best-in-class virtualization. ps10280/index.html Cisco UCS Manager Cisco UCS 2200 Series Fabric Extenders Cisco UCS 5100 Series Blade Server Chassis Cisco UCS 6200 Series Fabric Interconnects Provides centralized management capabilities for the Cisco Unified Computing System (UCS). Bring unified fabric into the blade-server chassis, providing up to eight 10 Gbps connections each between blade servers and the fabric interconnect. Chassis that supports up to eight blade servers and up to two fabric extenders in a six rack unit (RU) enclosure. Cisco UCS family of line-rate, low-latency, lossless, 10 Gigabit Ethernet, Fibre Channel over Ethernet (FCoE), and Fibre Channel functions. Provide network connectivity and management capabilities. ps10281/index.html support/servers-unifiedcomputing/ucs-2200-seriesfabric-extenders/tsd-productssupport-series-home.html ps10279/index.html ps11544/index.html Network components Product Description Link to documentation Cisco Nexus 1000V Series Switches A software switch on a server that delivers Cisco VN-Link services to virtual machines hosted on that server. ps9902/index.html 46

47 Additional references VCE Vblock and VxBlock Systems 540 Gen 2.1 Architecture Overview Product Description Link to documentation VMware vsphere Distributed Switch (VDS) Cisco Nexus 5000 Series Switches Cisco MDS 9148S Multilayer Fabric Switch Cisco Nexus 3064-T Switch Cisco Nexus 9396PX Switch A VMware vcenter-managed software switch that delivers advanced network services to virtual machines hosted on that server. Simplifies data center transformation by enabling a standards-based, high-performance unified fabric. Provides 48 line-rate 16-Gbps ports and offers cost-effective scalability through on-demand activation of ports. Provides management access to all VCE System components using vpc technology to increase redundancy and scalability. Provides high scalability, performance, and exceptional energy efficiency in a compact form factor. Designed to support Cisco Application Centric Infrastructure (ACI). vsphere/features/distributed-switch.html switches/nexus-5000-series-switches/ index.html collateral/storage-networking/ mds-9148s-16g-multilayer-fabric-switch/ datasheet-c html switches/nexus-3064-t-switch/ model.html switches/nexus-9396px-switch/ model.html Storage components Product Description Link EMC XtremIO Delivers industry-leading performance, scale, and efficiency for hybrid cloud environments. h12451-xtremio-4-system-specificationsss.pdf 47

48 About VCE VCE, an EMC Federation Company, is the world market leader in converged infrastructure and converged solutions. VCE accelerates the adoption of converged infrastructure and cloud-based computing models that reduce IT costs while improving time to market. VCE delivers the industry's only fully integrated and virtualized cloud infrastructure systems, allowing customers to focus on business innovation instead of integrating, validating, and managing IT infrastructure. VCE solutions are available through an extensive partner network, and cover horizontal applications, vertical industry offerings, and application development environments, allowing customers to focus on business innovation instead of integrating, validating, and managing IT infrastructure. For more information, go to Copyright VCE Company, LLC. All rights reserved. VCE, VCE Vision, VCE Vscale, Vblock, VxBlock, VxRack, and the VCE logo are registered trademarks or trademarks of VCE Company LLC. All other trademarks used herein are the property of their respective owners. 48