vce shared management platform architecture · pdf fileinter-vblock system networking ......

www.vce.com

VCE™ Shared Management PlatformArchitecture Overview

Document revision 1.0

February 2015

Revision history

Date Document revision Description of changes

February 2015 1.0 Initial release

Shared Management Platform Architecture Overview Revision history

2© 2015 VCE Company, LLC.

All Rights Reserved.

Contents

Introduction.................................................................................................................................................5

Accessing VCE documentation.................................................................................................................6

Overview......................................................................................................................................................7Shared Management Platform overview................................................................................................ 7System overview.................................................................................................................................... 7

SMP layers.......................................................................................................................................7Hardware......................................................................................................................................... 8Hypervisor........................................................................................................................................8Management workload.....................................................................................................................9Application....................................................................................................................................... 9

Compute components..............................................................................................................................11

Storage components................................................................................................................................ 12Block and file disk pools....................................................................................................................... 12

Network components............................................................................................................................... 13Network overview................................................................................................................................. 13Network design.....................................................................................................................................13In-band management networking.........................................................................................................14Out-of-band management networking..................................................................................................14Inter-Vblock system networking........................................................................................................... 14Inter-Vblock system connectivity use cases.........................................................................................17Virtual networking.................................................................................................................................19VMware standard and distributed switch design.................................................................................. 19VMware standard switch design...........................................................................................................21VMware distributed switch design........................................................................................................ 22Virtual machine placement................................................................................................................... 23

Management components........................................................................................................................24AMP-2 overview................................................................................................................................... 24AMP-2P network connectivity...............................................................................................................24Virtual machine network placement within AMP-2P.............................................................................25Management workload......................................................................................................................... 25

Core management workload..........................................................................................................25Optional management workload.................................................................................................... 26Ecosystem management workload................................................................................................27

Virtualization............................................................................................................................................. 28Production vCenter server....................................................................................................................28

Contents Shared Management Platform Architecture Overview



Local vCenter server............................................................................................................................ 28

Additional references............................................................................................................................... 31References overview............................................................................................................................31Virtualization components.................................................................................................................... 31Compute components.......................................................................................................................... 31Network components............................................................................................................................32Storage components............................................................................................................................ 32

Shared Management Platform Architecture Overview Contents



IntroductionThis document describes the high-level design of the VCE™ Shared Management Platform (SMP). Thisdocument also describes configuration options available for the SMP.

The SMP resides on a Vblock System 240 and can manage multiple Vblock Systems.

The target audience for this document includes the customer's technical management team, thecustomer's technical team, the VCE vArchitects/Pre-Sales, VCE Support and other VCE teams notdirectly related to SMP.

The VCE Glossary provides terms, definitions, and acronyms that are related to Vblock Systems.

To suggest documentation changes and provide feedback on this book, send an e-mail to [email protected]. Include the name of the topic to which your feedback applies.

Related information

Accessing VCE documentation (see page 6)

Introduction Shared Management Platform Architecture Overview



mailto:[email protected]?Subject=Documentation Feedback&body=Document: ArchOverviewSystem200Gen2.2 Please provide your comments:

Accessing VCE documentationSelect the documentation resource that applies to your role.

Role Resource

Customer support.vce.com

A valid username and password are required. Click VCE Download Center to access thetechnical documentation.

VCE Partner partner.vce.com

A valid username and password are required.

Cisco, EMC, VCE, orVMware employee

portal.vce.com

VCE employee sales.vce.com/saleslibrary

or

vblockproductdocs.ent.vce.com

Related information

Introduction (see page 5)

Network overview (see page 13)

Shared Management Platform Architecture Overview Accessing VCE documentation



http://support.vce.com

https://partner.vce.com/

https://portal.vce.com/

https://sales.vce.com/saleslibrary/

http://vblockproductdocs.ent.vce.com

Overview

Shared Management Platform overviewShared Management Platform enables customers to manage multiple Vblock Systems from a singleshared management platform. SMP is equipped with management workloads (Core, VCE Optional,and/or Ecosystem) and additional network, storage, virtualization, and compute components.

Note: The initial release of SMP is based on the Vblock System 240 as the host system.

SMP includes the following components:

• Local management

• Production Vblock System management

• Management software to install and operate the components in a Vblock System

The SMP has the ability to:

• Rapidly adapt and respond to growing and changing management capabilities supported by VCE

• Manage multiple Vblock System management platforms

• Leverage a standard Vblock System that meets the requirements for SMP outlined in thisdocument

System overview

SMP layers

The SMP consists of four layers as shown in the following illustration: Hardware, Hypervisor,Management Workload, and Application.

Overview Shared Management Platform Architecture Overview



Hardware

The hardware layer consists of standard Vblock System hardware components.

The SMP requires a physical AMP-2. The single server option of the AMP-2 (AMP-2P) is recommendedfor the Shared Management Platform. For more information about AMP-2, refer to the architectureoverview manual for your Vblock System.

Hypervisor

VMware vSphere Enterprise Plus is the default hypervisor on the Vblock System hosting the SMP.

The following hypervisor features are required:

• VMware High Availability (VMware HA)

• VMware vMotion

• VMware Dynamic Resource Scheduling (VMware DRS)

• VMware CPU and Memory Resource Pools

This lightweight hypervisor requires less than 6 GB of storage to install and has minimal managementoverhead.

VMware vSphere ESXi does not contain a console operating system. On the AMP-2P, the VMwarevSphere Hypervisor ESXi boots from the Cisco FlexFlash (SD card). For the remaining Cisco UCS

Shared Management Platform Architecture Overview Overview



production servers, the VMware vSphere Hypervisor ESXi boots from SAN or from Cisco FlexFlash (SDCard). The stateless hypervisor is not supported.

Management workload

The Management Workload layer is where all the workloads are divided appropriately between local andproduction management. These workloads enhance the scalability of the production hardware on theSMP.

The following table describes the different types of management workloads:

Management workload Description

Core Components required to install, operate and support aVblock System

VCE Optional Non-Core Management Workloads that are supportedand installed by VCE. These workloads managecomponents within the Vblock System.

Ecosystem Management workloads other than Core or VCEOptional whose purpose is to manage or support one ormore Vblock Systems.

Application

The Application layer contains the software components in the SMP. The following table describes thekey software components for the SMP:

Workloads Component

Core management • Hypervisor Management

• Element Managers

• Virtual network components (VMware VDS)

• Fabric Manager

• VCE Vision™ Intelligent Operations and the support resources required to install,operate, and support a Vblock System

VCE Optionalmanagement

This list is inclusive, but not limited to the following:

• Data Protection, Security or Storage management tools

• EMC Unisphere

• EMC RecoverPoint or EMC VPLEX

• EMC Avamar Administrator

• EMC InsightIQ for Isilon

• VMware vCloud Network and Security appliances (vShield Edge / Manager)

• VMware vCenter Operations Manager

Overview Shared Management Platform Architecture Overview



Workloads Component

Ecosystemmanagement

This list is inclusive, but not limited to the following:

• VMware vCloud Director

• VMware View

• Cisco Intelligent Automation for Cloud

• EMC Ionix Unified Infrastructure Manager (UIM)

On the SMP, AMP-2P supports the required components to install and support normal managementoperations. Alternately, the Local Management workload within the Shared Management Platform can bemigrated from the AMP-2P over to the Core Management Workload resource pool within the VblockSystem compute hosts. This move has the benefit of providing high availability and redundancy, whichthe AMP-2P does not provide.

The following table provides a list of the software management components that belong in the LocalManagement Workload and SMP:

Management infrastructure Virtual machines AMP-2 or Vblock System

Local AMP management workload • VCE Vision IntelligentOperations

• Local element manager

AMP-2P

SMP workload • Hypervisor management (localVblock System on which SMPresides)

• Hypervisor management

• SMP element managers

• Virtual networking components(Cisco Nexus 1000V Switch)

• Fabric manager

Vblock System

All other compute components and configuration tasks consist of a standard Vblock System build. Referto the architecture overview document related to your Vblock System for more information.

Shared Management Platform Architecture Overview Overview



Compute componentsThe compute portion requires a minimum of four servers with the following minimum configurations for theCore Management Workload and Optional Workloads.

The SMP requires a physical AMP-2. The single server option of the AMP-2 (AMP-2P) is recommendedfor the Shared Management Platform.

• Memory (minimum): 128 GB of RAM

• CPU (minimum): 2x E5-2600 v2 series CPUs with 6 cores each

A minimum of six servers with the following minimum configurations Core, VCE Optional and Ecosystemworkloads:

• Memory (minimum): 128 GB of RAM

• CPU (minimum): 2x E5-2600 v2 series CPUs with 6 cores each

All other compute components and configuration tasks consist of a standard Vblock System build. Referto the architecture overview document for your Vblock System for more information.

Compute components Shared Management Platform Architecture Overview



Storage components

Block and file disk poolsSizing of the block and file disk pools depends on the Core Workload, the VCE Optional Workload, andthe Ecosystem Workload Applications that are deployed and on the number of hosts and VMs that aremanaged. The standard SMP consists of the following block and file disk pools.

Specifications

Block disk pool - core enabledcluster

Block disk pool – non-coreenabled cluster

File disk pool

Memory: 12.5 TB minimum usable (70% threshold) Memory: 3TB minimum usable

Storage tiers:

• Tier 1 - 200GB SSD RAID-5 (4+1)

• Tier 2 - 600GB SAS 10k RAID-5 (4+1)

• Tier 3 - 2TB NL-SAS 7.2k RAID-6 (6+2)

• 10K SAS minimum or NL-SASwith Fast VP

• RAID 6

Storage feature recommendations

The SMP has the following additional storage features:

• FAST VP with flash disks (recommended for heavily utilized VMware vCenter and VMwarevCenter Operations Manager environments)

• FAST (recommended for SMP storage environments where available)

All other compute components and configuration tasks consist of a standard Vblock System build. Referto the architecture overview document for your Vblock System for more information.

Shared Management Platform Architecture Overview Storage components



Network components

Network overviewThe SMP network architecture is based on a standard Vblock System with the following majordifferences:

• In a standard Vblock System, most of the network connectivity between components is internal tothe Vblock System. In an SMP, the management network(s) connectivity is accessible to anyVblock System that is managed by SMP.

• Layer 3 connectivity is configured between specific hosts and VLANs to enable managementfunctionality. These routing configurations are implemented in customer-provided networkinfrastructure. For Layer 2 option, the SMP Core VLANs are extended through the customer-corenetwork into the Vblock System that is managed by SMP.

• The SMP environment uses a hybrid switch design that utilizes both the VMware Standard andDistributed Switches as its standard virtual networking switch (consistent with a standard VDS-based Vblock System). The option to use Cisco Nexus 1000V Series Switches is not supportedon a standard SMP at this time.

• The SMP utilizes the AMP-2P solution for its local management.

The logical network design for a SMP reduces impact from network outages and optimizes theenvironment for advanced security implementations, such as VCE secure administrative access andtrusted multi-tenancy solutions. The VLAN design is similar to a standard Vblock System.

Related information

Accessing VCE documentation (see page 6)

Network designThe SMP network architecture uses the following types of networking, which are explained in thefollowing sections:

• In-band management networking

• Out-of-band management networking

• Inter-Vblock System networking

• Virtual networking

Network components Shared Management Platform Architecture Overview



In-band management networkingThe in-band management network traverses the production network switches in the Vblock System onwhich the SMP software resides. The following VLANs carry management traffic that is local to the VblockSystem on which the SMP resides.

VLAN name Purpose

vblock_esx_mgmt Local VMware management and applications that may impact production

vblock_esx_vmotion vMotion traffic between SMP ESXi hosts

vblock_esx_ft VMware fault tolerance traffic between SMP ESXi hosts

vblock_nfs NFS traffic internal to SMP

vblock_esx_build Automated deployment of ESXi hosts

vblock_brs_data Backup/recovery with VCE Data Protection solution

vblock_nfs_routed NFS exports accessible by managed Vblock Systems

vblock_cifs_internal CIFS traffic internal to VMs in SMP

fcoe_fabric_a FCOE A VLAN for UCS connectivity

fcoe_fabric_b FCOE B VLAN for UCS connectivity

Out-of-band management networkingThe following networks are considered out of band and do not impact production use of the VblockSystem. They also may not be leveraged for any production data.

VLAN name Purpose

vblock_oob_mgmt VMs and device ports are used for control plane only -No data on this VLAN

Inter-Vblock system networkingThe following VLANs provide network connectivity to the Vblock Systems being managed by the SMP orto the customer management and production networks for consumption. For Layer 2 option, the SMPVLANs extend through the customer-core network into the Vblock Systems that are managed by SMP.

VLAN name Purposes

smp_oob_mgmt Control plane only - No data on this VLAN

smp_esx_mgmt VMware management and applications that may impact production

smp_vceopt_mgmt VCE Optional Management Workload Virtual Machines (may be collapsed into Core)

Shared Management Platform Architecture Overview Network components



VLAN name Purposes

smp_eco_mgmt Ecosystem Management Workload Virtual Machines

The following illustration shows VLAN requirements and usage.




The following table provides descriptions of the production and management VLANs:

VLAN name Description

smp_esx_mgmt Carries inter-Vblock System management traffic to and from the “SMP_Vblock_Central_Prod” management workload. Consider the following specifications forthis VLAN:

• If L2 network connectivity is required, then the assigned subnet must be a /22 subnetor bigger to accommodate for IP addressing of a minimum of 650 (up to 1000) ESXihosts.

• If L3 network connectivity is required, then the assigned subnet must be sizedaccording to the number of virtual machines that are required to support the externalVblock Systems being managed. Each vCenter instance requires four VMs and eachcommon virtual machines (such as element manager and fabric manager) requiressix VMs.

• Must have L2 or L3 connectivity through the customer-provided network to establishmanagement functionality between the SMP and managed Vblock Systems.

smp_oob_mgmt Carries inter-Vblock System management traffic to and from the virtual machines in the“SMP _Vblock_COMMON_Prod” management workload. Consider the followingspecifications for this VLAN:

• If L2 network connectivity is required, then the assigned subnet must be a /22 subnetor bigger to accommodate for IP addressing of a minimum of 650 (up to 1000) ESXihosts.

• If L3 network connectivity is required, then the assigned subnet must be sized toaccommodate less than 30 virtual machines, thus /27 should be sufficient.


smp_vceopt_mgmt Carries inter-Vblock System management traffic to and from the virtual machines in the“Optional Management Workload” VMware vSphere cluster resource pool. Consider thefollowing specifications for this VLAN:

• If L2 network connectivity is required, then the assigned subnet must be a /22 subnetor bigger to accommodate for IP addressing of a minimum of 650 (up to 1000) ESXiHosts and the necessary VCE Optional management workload virtual machines.

• If L3 network connectivity is required, then the assigned subnet should be sized toaccommodate the required number of virtual machines to support the VCE Optionalmanagement workload virtual machines to be installed.


smp_eco_mgmt Carries inter-Vblock System management traffic to and from the virtual machines in the“Ecosystem Management Workload” VMware vSphere cluster resource pool beneath theV2SMP-ECO VMware vSphere Cluster. Consider the following specifications for thisVLAN:

• IP address and subnet allocations for L2 and/or L3 network connectivity are clientspecified to meet the Ecosystem management workload application requirements.





Note: The vblock_esx_vmotion and vblock_esx_nfs VLANs remain local (and internal) to each of themanaged Vblock Systems and are not routed through the core network.

Inter-Vblock system connectivity use casesThe Vblock System Shared Management Platform network architecture allows for multiple scenarios toestablish inter-Vblock connectivity. This section provides use cases, requirements, and caveats.

The Vblock System Shared Management Platform must be in the same data center or within a metro 10milliseconds R/T latency distance of the Vblock Systems being managed.

Use Case 1: Inter-Vblock System connectivity using L3 capability

Description: This option uses L3 routing between the SMP core vlans and the external Vblock Systemvlans for management traffic.

Requirements: The following in-band management networks residing on the external Vblock System aswell as the SMP core management VLANs must have L3 routing configuration implemented through thecustomer-core network.

• vblock_esx_mgmt

• vblock_n1kl3_control (only when using the Cisco Nexus 1000V Switch as the external Vblockvirtual networking switch)

• vblock_oob_mgmt

• psmp_core_mgmt

• psmp_oob_mgmt

This enables management functionality between the Shared Management Platform and the managedVblock Systems.

Note: The vblock_oob_mgmt VLAN may require L3 routing to access applications running onmanagement virtual machines that reside on the out-of-band network. vblock_esx_vmotion andvblock_nfs vlans will remain local (and internal) to each of the managed Vblocks and will not berouted through the core network.




The following illustration is an example of L3 enabled customer-provided network to establish inter-VblockSystem connectivity. It shows the SMP VLANs and provides sample L3 routing configurations required onthe core network layer.

Use Case 2: Inter-Vblock connectivity using L2 capability

Description: This option uses the SMP core vlan as L2 VLAN that will be extended into the VblockSystems for management traffic.

Note: This option requires management networks for external Vblock Systems to move into the sameLayer 2 domain as the SMP core vlans. ESXi hosts on external Vblock Systems may require areconfiguration of the network settings.

Note: Regardless of the VLAN design, SMP requires the Cisco Nexus 1000v Switch to be implementedin L3 mode if present.




Requirements: The following SMP vlan must be extended through the customer-provided network intoeach of the external Vblock Systems for in-band management traffic.

• smp_esx_mgmt

• smp_n1kl3_control (only when using the Cisco Nexus 1000V as the external Vblock virtualnetworking switch)

• smp_oob_mgmt

This enables management functionality between the Shared Management Platform and the managedVblock Systems.

Note: The vblock_vmotion and vblock_nfs VLANs will remain local (and internal) to each of the managedVblock Systems and will not be extended through the core network.

Virtual networkingThe SMP has a standard option for Virtual Networking, allowing each virtual machine to connect to thephysical network. SMP uses the following switches in a hybrid design for virtual networking:

• VMware Standard Switch (vSS)

• VMware Distributed Switch (vDS)

Regardless of the virtual networking technology, the SMP does not support virtual networking capabilitieswith non-SMP VMware hosts or clusters. SMP can use a different virtual networking solution than theVblock Systems it manages. Furthermore, multiple Vblock Systems managed by a single SMP may usedifferent virtual networking solutions. For example, Vblock System A can use Cicso Nexus 1000v Switchwith Advanced Edition while Vblock System B can use a Cisco Nexus 1000v Switch with Essentials, andthe SMP that is managing the two Vblock Systems can use a VMware vSphere Distributed Switch (VDS).

Note: If the Cisco Nexus 1000v Essentials or the Cisco Nexus 1000V Advanced is selected for virtualnetworking on systems managed by SMP, enable L3 mode on each Vblock System that is beingmanaged. If the existing Vblock System uses L2 mode, modify the VLAN to shift to L3 mode forthe Cisco Nexus 1000v Switch.

Deploy the virtual networking components on the SMP and place them in a manner to support amaximum level of redundancy (where choices are available.)

VMware standard and distributed switch designThe SMP environment uses a hybrid switch design that utilizes both the VMware vSphere Standard andVMware vSphere Distributed Switch (VDS) solution (which is consistent with a standard VMware vSphereVDS-based Vblock System).




Each VMware ESXi host has vmkernel port groups, vMotion, and NFS (If used) configured on theVMware vSphere Distributed Switch (VDS). The remaining port groups reside on the VMware vSphereStandard Switch. These ESXi hosts are managed by the local SMP VMware vCenter Server that residesin the “Local Management Workload” pool.

You can host your existing vCenter Server environment from an external Vblock System on the SMPVblock System or individual Vblock System compute hosts in the SMP centralized vCenter instance.Consider the following:

• The SMP Vblock System and individual Vblock compute hosts must be within the same datacenter and must adhere to the 10 ms RTT latency limitations of SMP.

• The Cisco Nexus 1000V must be in L3 Mode. VCE recommends that the L3 control traffic beplaced on the esx_mgmt VLAN.

• Any Vblock system being managed by SMP must be at a supported RCM.

• Any vCenter resources from a different vCenter instance running on SMP cannot be used.

To accommodate hosting the external Vblock System vCenter Services, a dedicated child pool is createdspecifically for each external Vblock System under the “Production Management Workload” pool. Thevirtual machines connect to the appropriate VM distributed port group within the VMware vSphereDistributed Switch (VDS). In this case, two VM distributed port groups are created on the VMwarevSphere Distributed Switch (VDS) used for server management and Cisco Nexus 1000V Switch Layer 3control VM (if needed).

Use the following naming convention for each VM and VMK distributed port group created within theVMware vSphere Distributed Switch (VDS) contains a prefix and a suffix to identify the external VblockSystem and indicate whether it is a vm or a vmk port group. The only vmkernel distributed port groupcreated will be for esx vmotion for the local SMP ESXi hosts. If NFS (local to SMP) exists then it will alsobe on the VMware vSphere Distributed Switch (VDS) as well.

For example:

V2VB220A – This prefix identifies the external Vblock being managed

vm – This suffix identifies the type of port group. (Vm represents VM distributed port group.)

The naming scheme for the VMware Distributed Switch is DVswitchSMP-1.




VMware standard switch designThe following illustration maps out how the VMware Standard Switch is configured on the SMP.

This illustration reflects the connections between the devices, not the quantity of these connections.




VMware distributed switch designThe following illustration shows how the VMware Distributed Switch is configured on the SMP.

This illustration reflects the connections between the devices, not the quantity of these connections.




Virtual machine placement and VLAN assignmentThe following illustration shows the placement of each virtual machine within the SMP Vblock Systemalong with its corresponding VLAN.

Note: The Local Management workload, except for Element Manager and VCE Vision, is migrated to theCore Management Workload resource pool to provide high availability and redundancy which theAMP-2P does not provide.




Management components

AMP-2 overviewAMP-2P is supported with the SMP.

AMP-2P provides a single and dedicated server running the VCE Vision™ Intelligent Operations andElement Manager virtual machines using its own resources, not customer resources.

AMP-2P network connectivityThe right half of the following illustration shows the AMP-2P management connectivity:

Note: Both vblock_oob_mgmt and vblock_oob_mgmt_vmk are on VLAN 101.

Shared Management Platform Architecture Overview Management components



Note: This illustration reflects the connections between the devices, not the quantity of theseconnections.

Virtual machine network placement within AMP-2PThe following illustration shows each virtual machine along with its corresponding VLAN.

Note: The Element Manager within the AMP-2P (not within SMP) is dual homed..

Management workloadThe purpose of dedicated cluster system resource pools is to segregate the required resources needed torun efficiently and provide good performance without hindering other workloads.

There are three different types of workloads and each described in details:

• Core Management Workload

• VCE Optional Management Workload

• Ecosystem Management Workload

Core management workload

The Core Management Workload consists of the Local Management vCenter Server that contains boththe Local Management and Production Shared Management workloads.

Management components Shared Management Platform Architecture Overview



Both workloads are split up into the following VMware vSphere System Resource Pools under theV2SMP-CORE cluster:

• Local Management Workload: Manages the components that are local to the SMP. The localmanagement workload provides the local workloads for the VMware vSphere managementcomponents that run the SMP. The pools allow you to shape the resource management asrequired.

• Production Shared Management Workload: Manages all external Vblock Systems. TheProduction shared managmenet workload provides the “central/shared” workloads for theVMware vSphere management components and the “common” components such as CiscoElement Manager, EMC ESRS, Cisco Fabric Manager, and EMC PowerPath. The pools allowyou to shape the resource management as required.

The “central/shared” and “common” workloads are configured separately as children of the “ProductionShared Management Workload”.

The following table lists the servers that belong in the Local and Production Shared ManagementWorkload.

This workload … Includes these components … And manages these resources

Local management workload -+ Local database server Local Vblock System components

Local vCenter server

Local update manager

Production shared managementworkload

Production database server Managed vblock resources (includingstorage*, compute, virtualization, andnetwork)Production VMware vCenter server

Production update manager

Production Cisco Element Manager

Production Cisco Fabric Manager All Vblock resources (includingstorage*, compute, virtualization, andnetwork)Production EMC ESRS appliance

Production EMC PowerPath licenseserver

* The local element manager manages EMC VMAX storage on the SMP.

Optional management workload

The VCE Optional Management Workload consists of all the VCE Optional software components. It isshared with the Core Management Workload VMware vSphere Cluster, V2SMP-CORE.

A single VMware vSphere system resource pool is created:

Shared Management Platform Architecture Overview Management components



Optional Management Workload: This VMware vSphere system resource pool provides all the DataProtection software components that VCE offers. The pools enable the administrator to shape theresource management as required.

Ecosystem management workload

The Ecosystem Management Workload consists of non-VCE supported Management tools from Cisco,EMC, and VMware as well as software that is certified as Vblock Ready such as VMware vRealize Suite,VMware Horizon View, Cisco UCS Director, EMC Ionix Unified Infrastructure Manager (UIM/P andUIM/O), VMware VMTurbo, and BMC Cloud Lifecycle Management.

A single VMware vSphere system resource pool is created under the VMware vSphere Cluster, V2SMP-ECO:

Ecosystem Management Workload: Ecosystem Management Workload enables you to shape theresource management as required.

The red boxes within the following illustration show how the management and ecosystem VMwarevSphere System Resource Pool workloads appear within the local VMware vCenter Server.

Management components Shared Management Platform Architecture Overview



Virtualization

Production vCenter serverThe vCenter Server includes the following components.

• Virtual Network Switch: vCenter Server uses a Cisco Nexus 1000V Switch or a VMware VirtualDistributed switch for virtual networking.

— Cisco Nexus 1000V: A single pair of Virtual Supervisor Modules (VSMs) can support up to128 Virtual Ethernet Modules (VEMs) or hosts.

— VMware Virtual Distributed Switch: A single VMware VDS switch can support up to 1000VMware ESXi hosts.

• Resource Pool: Varies by the customer depending on the type of workloads running in theenvironment.

Local vCenter serverThe SMP Local Management workload resides on the Vblock System that hosts SMP.

This local vCenter Server manages the SMP.

The following list describes the components of the vCenter Server:

• Virtual Network Switch: VMware vCenter Server uses the VMware Distributed Switch bydefault.

• Datacenter: The datacenter includes two datacenter instances:

— V2SMPAMP: Supports all the Advanced Management Pod workloads from all the externalVblock Systems.

— V2SMPDC: Supports all the workloads within the SMP

• VMware vSphere Cluster: Two VMware vSphere clusters within the VMware vCenter Serveraccommodate the SMP Core and SMP ECO workloads. No cluster is created for the AMP-2Pbecause it uses a single Cisco UCS Server.

• vAPP: A vAPP is assigned to each type of workload. The following workloads have vAPPs:

— V2SMP-Core-vAPP – Provides the VMs for VCE Vision and Element Manager (Local).

— SMPprod-1 – Provides the Production Shared Management VMware vCenter Serverworkload.

Shared Management Platform Architecture Overview Virtualization



— SMPprod-2 – Provides an additional Production Shared Management vCenter Serverworkload .

— SMPcmn-1 – Provides the Shared Managed VMs that support SMP Element Manager,ESRS, Fabric Manage and PowerPath.

• Resource Pool: For the best performance and efficiency resources pools are assigned to eachtype of workload. The following diagram illustrates how they appear in the VMware vCenterServer:

Virtualization Shared Management Platform Architecture Overview



Local Management Workload: After a standard logical build for a Vblock System 240, the LocalManagement Workload (SQL Server, vCenter Server, Updated Manager) is migrated from the AMP-2Phost over to the Local Management Workload pool under the VSMP-CORE cluster.

Related information

Management workload (see page 25)

Shared Management Platform Architecture Overview Virtualization



Additional references

References overviewThe following sections list documentation provided by Cisco, EMC, and VMware for each of the productlines that are discussed in this document.

Virtualization components

Product Description Link to documentation

VMware vCenterServer

Provides a scalable and extensible platform that forms thefoundation for virtualization management.

www.vmware.com/solutions/virtualization-management/

VMware vSphereESXi

Virtualized infrastructure for Vblock Systems. Virtualizesall application servers and provides VMware HighAvailability (HA) and Dynamic Resource Scheduling(DRS). (This is available if VMware vSphere EnterprisePlus is licensed on all ESXi hosts inside a cluster.)

www.vmware.com/products/vsphere/

VMware Single Sign-On (SSO) Service

Provides VMware-specific authentication services. blogs.vmware.com/kb/2012/10/vsphere-sso-resources.html

EMC PowerPath/VE Provides automated data path management and load-balancing capabilities for server, network, and storagedeployed in virtual and physical environments.

www.emc.com/storage/powerpath/powerpath.htm

Compute components


Cisco UCS C220server

High-density, rack-mount server forproduction-level network infrastructure, webservices, and maintenance data center,branch, and remote office applications.

www.cisco.com/en/US/products/ps12369/index.html

Cisco UCS VirtualInterface Card (VIC)1225

FCoE PCIe adapter used with Cisco UCSC220 servers. Used for convergednetworking.

www.cisco.com/en/US/prod/collateral/modules/ps10277/ps12571/data_sheet_c78-708295.html

Additional references Shared Management Platform Architecture Overview



http://www.vmware.com/solutions/virtualization-management/

http://www.vmware.com/solutions/virtualization-management/

http://www.vmware.com/products/vsphere/

http://www.vmware.com/products/vsphere/

http://blogs.vmware.com/kb/2012/10/vsphere-sso-resources.html

http://blogs.vmware.com/kb/2012/10/vsphere-sso-resources.html

http://www.emc.com/storage/powerpath/powerpath.htm

http://www.emc.com/storage/powerpath/powerpath.htm

http://www.cisco.com/en/US/products/ps12369/index.html


http://www.cisco.com/en/US/prod/collateral/modules/ps10277/ps12571/data_sheet_c78-708295.html



Network components


Cisco Nexus 1000VSeries Switches

A software switch on a server that delivers Cisco VN-Linkservices to virtual machines hosted on that server.


VMware VirtualDistributed Switch(VDS)

A VMware vCenter-managed software switch that deliversadvanced network services to virtual machines hosted onthat server.

http://www.vmware.com/products/vsphere/features-distributed-switch

Cisco Nexus 3048Switch

Provides wire speed layer 2 and 3 switching for datacenter top of rack deployments. These switches deliverflexible port densities, low power, and programmability ona data-center-class, Cisco Nexus operating system (CiscoNX-OS).


Cisco Nexus5548UP Switch

Simplifies data center transformation by enabling astandards-based, high-performance unified fabric.


Storage components


EMC VNX5300 storage array

EMC VNX5200 storage array

High-performing unified storage withunsurpassed simplicity and efficiency,optimized for virtual applications.

www.emc.com/products/series/vnx-series.htm

Shared Management Platform Architecture Overview Additional references





HTTP://WWW.VMWARE.COM/PRODUCTS/VSPHERE/FEATURES-DISTRIBUTED-SWITCH







http://www.emc.com/products/series/vnx-series.htm

http://www.emc.com/products/series/vnx-series.htm

www.vce.com

About VCE

VCE accelerates the adoption of converged infrastructure and cloud-based computing models that dramatically reduce thecost of IT while improving time to market for enterprises and service providers globally. Through its leading VblockSystems, VCE delivers the industry's only true converged infrastructure, leveraging Cisco compute and networktechnology, EMC storage and data protection, and VMware virtualization and virtualization management. VCE solutionsare available through an extensive partner network and cover horizontal applications, vertical industry offerings andapplication development environments, enabling customers to focus on business innovation instead of integrating,validating, and managing IT infrastructure.

For more information, go to http://www.vce.com.

© 2015 VCE Company, LLC. All rights reserved. VCE, Vblock, VCE Vision, and the VCE logo are registered trademarks ortrademarks of VCE Company, LLC. and/or its affiliates in the United States or other countries. All other trademarks usedherein are the property of their respective owners.



vce shared management platform architecture · pdf fileinter-vblock system networking ......

Documents