DocWiki - User contributions [en]

Virtualization for Unified CCE

2012-01-10T13:27:33Z

Sdurvasu: 1 revision

== Updates to this Page ==

The following is a list of significant updates to this page:

{| class="wikitable FCK__ShowTableBorders"
|-
! Date
! Update
|-
| December 09, 2011
| Added PG limited coresidency with UCM/CUP/IPIVR capability.
|-
| November 15,2011
| Added sample deployment for 12,000 agents.
|-
| June 28, 2011
| Updated list of Unified CCE components that have not been qualified and are not supported in virtualization. Updated Section 5.1 ESXI 4.1 Software Requirements to add new link to Disable LRO. Updated Section 6 Unified CCE Component Capacities and VM Configuration Requirements to add new link to Downloading OVA Templates for UC Applications. Removed Section 7.2ESXi 4.1 Network Settings. Changed title from Creating Virtual Machines from OVA VM Templates to Cisco Unified CCE-Specific Information for OVA Templates Removed Section 12.1 Downloading OVA Templates and added new links to Unified Communications Virtualization Downloads and Unified CCE OVA Templates.
|-
| June 1, 2011
| Added Section 5.1 ESXi 4.1 Software Requirements. Added Section 7.2 ESXi 4.1 Network Settings. Removed references to ESXi 4.0. Updated ''UCS Network Configuration'' section.
|-
| May 9, 2011
| Updated the ''Unified CCE Component Co-Residency and Sample Deployments ''section.
|-
| February 17, 2011
|
Updated the ''Creating Virtual Machines from OVA VM Templates'' section. Removed OVA list from this page and added a link. Added the Scalability Assumptions section. Updated the CUIC RAM (GB) numbers in the sample CCE deployments. Updated the sample deployment tables and highlighted optional items.

|-
| December 22, 2010
| Updated the pointer links for the Bill of Material, CCMP virtualization page, and the Hybrid Deployment section.
|-
| December 20, 2010
| Updated the Component Capacities section, the VM configuration requirements table, the Hybrid Deployment Options section, the steps for installing/migrating Unified CCE Components, the Support for Virtualization on the ESXi/UCS Platform section, and the Hardware Requirements section.
|-
| December 14, 2010
| Added Avaya ACD PG, TDM ACD PG, and Unified Contact Center Gateway to the Unified CCE Component Capacities and VM Configuration Requirements section. Updated the Steps for Installing/Migrating Unified CCE Components on Virtual Machines secton. Added Hybrid Deployment Options section.
|-
| December 10, 2010
| Added Unified CVP, Unified IC, Contact Center Management Portal (CCMP), and CAD to the sample deployments section.
|-
| October 1, 2010
| This page, [http://docwiki.cisco.com/wiki/UCCE_on_UCS_Deployment_Certification_Requirements_and_Ordering_Information UCCE on UCS Deployment Certification Requirements and Ordering Information], and [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE UCS Network Configuration for UCCE] updated to reflect support of UCS C-Series hardware on UCCE.
|-
| September 28, 2010
| CVP added to list of supported components/deployments.
|-
| September 21, 2010
| IPIVR added to list of supported components/deployments and as an optional component in the sample deployment tables at [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Sample_CCE_Deployments Sample CCE Deployments].
|}

== Information for Partners about Unified CCE on UCS Deployment Certification and Ordering ==

'''It is important that partners who are planning to sell UCS products on Unified Contact Center Enterprise read the DocWiki page''' [[Unified CCE on UCS Deployment Certification Requirements and Ordering Information]].

This page contains essential information for partners about the following:

:*Partner Certification Requirements
:*UCS Server Ordering Information
:*Important Notes on Cisco UCS Service and Support

== Unified CCE 8.x Support for Virtualization on the ESXi/UCS Platform ==

Starting with Release 8.0(2), virtualization of the following deployments and Unified CCE components on Cisco Unified Computing Systems (UCS) B200 Series and C210 Series hardware is supported:

:*Router
:*Logger
:*Agent PG
:*MR PG
:*VRU PG
:*Unified Contact Center Gateway
:*Avaya ACD PG (Also supported on virtualized ESXi server on MCS-7845-I3-CCE2)
:*TDM ACD PG (Also supported on virtualized ESXi server on MCS-7845-I3-CCE2)
:*Cisco Agent Desktop (CAD) Server
:*Administration and Data Server with one of the following roles:
::*Administration Server and Real-time Data Server (AW)
::*Configuration-only Administration Server (AW-CONFIG)
::*Administration Server and Real-time and Historical Data Server (AW-HDS)
::*Administration Server, Real-time and Historical Data Server, and Detail Data Server (AW-HDS-DDS)
::*Historical Data Server and Detail Data Server (HDS-DDS)
:*Administration Client
:*Outbound Option with SIP Dialer (collocate SIP Dialer and MR PG with Agent PG in the same VM guest. Generic PG can also be collocated with the Agent PG in the same VM guest. Published agent capacity formula with Outbound Option applies.)
:*Support Tools
:*Rogger (a Router and a Logger in the same VM)
:*The Unified Communications Manager (UCM) Clustering Over the WAN deployment model with Unified CCE is supported; see the section [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Support_for_UCM_Clustering_Over_the_WAN_with_Unified_CCE_on_UCS_Hardware Support for UCM Clustering Over the WAN with Unified CCE on UCS Hardware] for important information.
:*Unified IP-IVR is supported with Unified CCE on UCS B-Series solution and on UCS C-Series with the model ([http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210-VCD2)] only. Please refer to the IPIVR product specific pages for detail.
:*CVP is supported with CCE on UCS solution. Please refer to the [http://docwiki.cisco.com/wiki/Unified_Customer_Voice_Portal Unified Customer Voice Portal] wiki page for details.
:*Contact Center Management Portal (CCMP). See the [[Virtualization for CCMP with Unified CCE on UCS Hardware]] wiki page for details.
:*Cisco Unified Intelligence Center (Unified IC). Please refer to the [[Cisco Unified Intelligence Center]] wiki page for details.
:*Cisco E-mail Interaction Manager (EIM)/Web Interaction Manager (WIM). See the Virtualization for EIM-WIM wiki page for details

The following deployments and Unified CCE components have not been qualified and '''are not supported''' in virtualization:

:*Progger (a Router, a Logger, and a Peripheral Gateway); this all-in-one deployment configuration is not scalable in a virtualization environment. Instead, use the Rogger or Router/Logger VM deployment configuration.
:*Unified CCH
:*Unified ICMH
:*Outbound Option with SCCP Dialer
:*WebView Server
:*Expert Advisor
:*Remote Silent Monitoring (RSM)
:*Span based Silent Monitoring on UCS B-series chassis
:*Cisco Unified CRM Connector
:*IPsec. UCS does not support IPsec off-board processing, therefore IPsec is not supported in virtualization.

{{note|The hybrid (virtual and non-virtual server) deployment model is supported. Components that are not yet virtualized can continue to be on MCS in the UCCE on UCS deployment. See the [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE#Hybrid_Deployment_Options Hybrid Deployment Options] section for more information.}}

The following VMware features are not supported with Unified CCE:

:*VMware Physical to Virtual migration
:*VMware snapshots
:*VMware Consolidated Backup
:*VMware High Availability (HA)
:*VMware Site Recovery Manager
:*VMware vCenter Update Manager
:*VMware vCenter Converter

== Hardware Requirements for Unified CCE Virtualized Systems ==

Requirements for Cisco Unified CCE systems using UCS B200 or C210 hardware are located in the [[Unified Computing System Hardware|Unified Computing System Hardware]].

For UCS C210, Unified CCE supports only the model ([http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210-VCD2)] with a specific HDS Virtual Machine (VM) coresidence/population rule. See [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Sample_CCE_Deployments Sample CCE Deployments]

Unified CCE supports MCS-7845-I3-CCE2 with virtualization. For a list of supported virtualized components on MCS servers, see the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release, 8.0(x).] Unified CCE does not support UCS C200.

== VMware and Application Software Requirements ==

The following software requirements apply specifically to Unified Contact Center Enterprise:

:*VMWare ESXi 4.0 or 4.1, minimum version 4.0U1. ''Versions of ESXi prior to 4.0U1 and all versions of ESX are unsupported.''
:*If you are upgrading ESXi software, see the section [http://docwiki-dev.cisco.com/wiki/Ongoing_Virtualization_Operations_and_Maintenance Upgrade ESXi].
:*The Windows, SQL, and other third party software requirements for the Unified CCE applications in the ESXi/UCS platform are the same as in the physical server. For such information see the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise & Hosted, Release 8.0(x)].

=== ESXi 4.1 Software Requirements ===

When Cisco Unified CCE is running on ESXi 4.1, you must perform the following steps:

:*You must install or upgrade VMware Tools for ESXi 4.1 on each of the VMs and use all of the VMware Tools default settings. For more information, see the section [http://docwiki-dev.cisco.com/wiki/VMware_Tools VMware Tools]
:*You must disable Large Receive Offload (LRO). For details, see the section [http://docwiki-dev.cisco.com/wiki/Disable_LRO Disable LRO]

 

= Unified CCE Component Capacities and VM Configuration Requirements =

For supported Unified CCE component capacities and VM computing resource requirements, see the [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Contact_Center_Enterprise List of Unified CCE OVA Templates.]

{{note| You must use the OVA VM templates to create the Unified CCE component VMs.}}

 For instructions on how to obtain the OVA templates, see [http://docwiki.cisco.com/wiki/Downloading_OVA_Templates_for_UC_Applications Downloading OVA Templates for UC Applications]

== Unified CCE Scalability Impacts ==

The [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Contact_Center_Enterprise capacity sizing information] is based on the operating conditions published in the ''Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 8.x'', Chapter 10, ''Operating Conditions'' and the ''Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted'''','''''Release 8.x, Section 5. Both documents are available at [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_implementation_design_guides_list.html Cisco.com]'''.'''

The following features reduce the scalability of certain components below the agent count of the respective OVA [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Contact_Center_Enterprise capacity sizing information].

*CTI OS Security - CTI OS Server capacity is impacted when CTI OS Security is enabled; capacity is decreased by 25%.
*Mobile Agents - Refer to the SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with Mobile Agents.
*Outbound Option – Refer to SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with Outbound Option.
*Agent Greeting – Refer to SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with the Agent Greeting feature enabled.
*Extended Call Context (ECC) usage greater than the level noted in the Operating Conditions will have a performance and scalability impact on critical components of the Unified CCE solution. As noted in the SRND, the capacity impact will vary based on ECC configuration, therefore, guidance must be provided on a case-by-case basis.

= UCS Network Configuration =

:*'''IMPORTANT:''' For instructions on performing the network configuration needed to deploy Cisco Unified Contact Center Enterprise (UCCE) on UCS servers, see [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE UCS Network Configuration for UCCE].
:*QoS should be mandatorily enabled for both Private network connection(between Side A and B) and the public network connection(between the Router and the PG). Refer to Chapter 12,  [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/design/guide/uccesrnd80.pdf Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND)] for more details
:*For information on best practices for Cisco VLAN trunking to VMware, refer to [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806 this website].

== Support for UCM Clustering Over the WAN with Unified CCE on UCS Hardware ==

You can deploy the Unified Communications Manager (UCM) Clustering Over the WAN deployment model with Unified CCE on UCS hardware.

When you implement this deployment model, be sure to follow the best practices outlined in the section "IPT: Clustering Over the WAN" in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/design/guide/uccesrnd80.pdf Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND).]

In addition, note the following expectations for UCS hardware points of failure:

*For communication path single point of failure performed by Cisco on the Unified CCE UCS B-series High Availability (HA) deployment, system call handling was observed to be degraded for up to 45 seconds while the system recovered from the fault, depending upon the subsystem faulted. Single points of failure will not cause the built-in ICM software failover to occur. Single points of failure include, but are not limited to, a single fabric interconnect failure, a single fabric extender failure, and single link failures.

*Multiple points of failure on the Unified CCE UCS HA deployment can cause catastrophic failure, such as ICM software failovers and interruption of service. If multiple points of failure occur, replace the failed redundant components and links immediately.

=== B-Series Considerations ===

When deploying Clustering Over the WAN with B-Series hardware, use of the Cisco UCS '''M81KR''' Virtual Interface Card is mandatory.

New B-Series deployments using Clustering Over the WAN '''must''' use a Nexus 7000 Series / Nexus 5000 Series vPC infrastructure, or a Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720-10G.

See the configuration guidelines in [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE#UCCE_on_UCS_B-Series_Network_Configuration UCCE on UCS B-Series Network Configuration].

=== C-Series Considerations ===

If deploying Clustering Over the WAN with C-Series hardware, '''do not''' trunk public and private networks. You '''must''' use separate physical interfaces off of the C-Series servers to create the public and private connections. See the configuration guidelines in [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE#Network_Requirements_for_C-210_M1_Servers Network Requirements for C-210 M1 Servers].

 

= Notes for Deploying Unified CCE Applications on UCS B-Series Hardware with SAN =

In Storage Area Network (SAN) architecture, storage consists of a series of arrays of Redundant Array of Independent Disks (RAIDs). A Logical Unit Number (LUN) that represents a device identifier can be created on a RAID array. A LUN can occupy all or part of a single RAID array, or span multiple RAID arrays.

In a virtualized environment, datastores are created on LUNs. Virtual Machines (VMs) are installed on the SAN datastore.

Keep the following considerations in mind when deploying UCCE applications on UCS B-series hardware with SAN.

*This deployment must comply with the conditions listed in Section 3.1.6 of the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware & System Software Specification (Bill of Materials) for Cisco Unified Contact Center Enterprise, Release 8.0(1).] In particular, SAN disk arrays must be configured as RAID 5 or RAID 10. 

*Each Historical Data Server (HDS) requires a dedicated LUN and a datastore with a 2 MB block size. No other application can reside on the same datastore as the HDS. The HDS requires a 2 MB block size to accommodate the 500 GB OVA disk size, which exceeds the 256 GB file size supported by the default 1 MB block size for datastores. The HDS block size is configured in VMware at datastore creation.

*To help keep your system running most efficiently, schedule automatic database purging to run when your system is least busy. 

*The SAN design and configuration must meet the following VMware ESXi disk performance guidelines:
**Disk Command Latency – It should be 15 mSec or less. 15mSec latencies or greater indicates a possible over-utilized, misbehaving, or mis-configured disk array.
**Kernel Disk Command Latency – It should be very small in comparison to the Physical Device Command Latency, and it should be close to zero. A high Kernel Command Latency indicates there is a lot of queuing in the ESXi kernel.

*The SAN design and configuration must meet the following Windows performance counters on UCCE VMs:
**AverageDiskQueueLength must remain less than (1.5 ∗ (the total number of disks in the array)).
** %Disktime must remain less than 60%. 

*Any given SAN array must be designed to have an IOPS capacity exceeding the sum of the IOPS required for all resident UC applications. Unified CCE applications should be designed for the 95th percentile IOPS values published in this wiki. For other UC applications, please follow their respective IOPS requirements & guidelines.

 

See below for an example of SAN configuration for Rogger 2000 agent deployment. This example corresponds to the 2000 agent Sample CCE Deployment for UCS B-Series described in: [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Coresidency_and_Sample_Deployments Unified CCE Component Coresidency and Sample Deployments].

== Example of SAN Configuration for Unified CCE ROGGER Deployment up to 2000 Agents ==

The following SAN configuration was a tested design, though generalized here for illustration. It is not the only possible way in which to provision SAN arrays, LUNs, and datastores to UC applications. However, you must adhere to the guidance given earlier in this section (above).

=== Rogger Side A ===

[[Image:RoggerSideA.jpg]]

=== Rogger Side B ===

[[Image:RoggerSideB.jpg]]

= Steps for Installing/Migrating Unified CCE Components on Virtual Machines =

Follow the steps and references below to install the Unified CCE components on virtual machines. You can use these instructions to install or upgrade systems running with Unified CCE 8.0(2) and later. You can also use these instructions to migrate virtualized systems from Unified CCE 7.5(x) to Unified CCE 8.0(2) or later, including the Avaya PG and other selected TDM PGs that were supported on Unified CCE 7.5(x). Not all TDM PGs supported in Unified CCE 7.5(x) are supported in Unified CCE 8.0(x). For more information, see [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release 8.0(1).]

#Acquire the supported servers for Unified CCE 8.0(x).
#*Cisco UCS servers are specified in the [http://docwiki-dev.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE&oldid=63654#Hardware_Requirements_for_Unified_CCE_Virtualized_Systems Hardware Requirements for Unified CCE Virtualized Systems] section.
#*MCS-7845-I3-CCE2 is specified in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release 8.0(1).]
#*If there are PG VMs that are running on the following older MCS servers, MCS-7845-H2 or MCS-7845-I2, replace these servers with supported servers.
#Install, setup, and configure the servers.
#Configure the network. See reference at [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#UCS_Network_Configuration UCS Network Configuration]. {{note |Configuring the network for the MCS servers is the same as configuring the network for the UCS C-Series servers.}}
#If VMware VirtualCenter is used for virtualization management, install or update to VMware vCenter Server 4.0 or later.
#Install and Boot VMWare ESXi. See the [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html Cisco UCS B-Series Blade Servers VMware Installation Guide] or the [http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/os/vmware/install/vmware_install_c.html Cisco UCS C-Series Servers VMware Installation Guide]. On C-Series servers or MCS servers, you must configure the ESXi datastore block size for the Administration & Data Server. See [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Configuring_the_ESXi_Data_Store_Block_Size_for_Administration_and_Data_Server Configuring the ESXi Data Store Block Size for Administration and Data Server] for instructions.
#Create the Unified CCE virtual machines from the OVA templates. See reference at [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Creating_Virtual_Machines_from_OVA_VM_Templates Creating Virtual Machines from OVA VM Templates]. This is a requirement for all component running Unified CCE 8.0(2) and later. In Unified CCE 7.5(x), this is not a requirement.
#Install VMware Tools with the ESXi version on the virtual machines. Install the same version of VMware Tools as the ESXi software on the virtual machines.
#Install Windows OS and SQL Server (for Logger and HDS components) on the created virtual machines. {{note| Microsoft Windows Server 2003 ''Standard Edition'' and Microsoft SQL Server 2005 ''Standard Edition'' should be used for virtual machine guests. See related information in the links below.}}
#Install or migrate the Unified CCE Software components on the configured virtual machines, using Fresh Install or Tech Refresh Upgrade, as described in [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE#Installing_Unified_CCE_Components_on_Virtual_Machines Installing Unified CCE components on virtual machines] and [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE#Migrating_Unified_CCE_Components_to_Virtual_Machines Migrating Unified CCE components].

= Unified CCE Component '''VM Coresidency''' and '''Sample Deployments''' =

You can have one or more Unified CCE VMs coresident on the same ESXi server (for example, B200M2 blade or C210M2 rack mount server).  However, you must follow the rules described below:

:*You can have any number of Unified CCE virtual machines and combination of coresidency of Unified CCE virtual machines on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation does not over commit the available ESXi server computing resources. 
:*You must not have CPU overcommit on the ESXi server that is running Unified CCE realtime application components.  The total number of vCPUs among all the virtual machines on an ESXi host must not be greater than the total number of CPUs available on the ESXi server.  In the case of the Cisco UCS B-200 and C-210, the total number of CPUs available is 8.
:*You must not have memory overcommit on the ESXi host running UC realtime applications.  You must allocate a minimum 2GB of memory for the ESXi kernel.  For example, if an ESXi server on B-200 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel you have 34GB available for the virtual machines.  The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.
:*VM coresidency with Unified Communications '''and''' third party applications (for example, WFM) is '''not''' supported unless it is described in the following subsection.

The following table shows how Unified CCE components can be coresident on the same ESXi server. '''A diamond indicates that coresidency is allowed'''. For example, the first row shows that Unified Communications Applications can not be colocated with Contact Center Tier 1 Applicaitons. The third row shows that Third Party Applications can only be colocated with Contact Center Tier 3 Applications.

{| class="wikitable FCK__ShowTableBorders"
|-
! Unified CCE Component Coresidency
! Contact Center Tier 1 Applications
! Contact Center Tier 2 Applications
! Contact Center Tier 3 Applications
! Unified Communications Applications
! Third Party Applications
|-
| '''Contact Center Tier 1 Applications: Router, Logger, Peripheral Gateway, ADS-HDS'''
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
|
|
|-
| '''Contact Center Tier 2 Applications: CVP Call + VXML Server, CVP Reporting Server, CUIC, CCMP''' 
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
| align="center" |
|-
| '''Contact Center Tier 3 Applications: ADS/AW (any non-HDS), Admin Client, Support Tools, Windows AD DC, CVP Ops/OAMP Server, CVP Media Server, SocialMiner''' 
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
|-
| '''Unified Communications Applications: Communications Manager, Contact Center Express, IPIVR, CUP, Unity, Unity Connection, MediaSense''' 
| align="center" |
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
|
|-
|
|}
{{note|'''EXCEPTIONS''' to the above VM co-residency table:}}
:*On a '''C-Series''' server, the HDS '''cannot''' co-reside with a Router, Logger, or a PG.
:*'''PG''' (in CCE solutions up to 1000 CTIOS agents or 500 CAD agents) VMs '''can''' be co-resident with UCM/CUP/IPIVR VMs on the same ESXi host/server.
 

{{note|If Cisco Support determines that a third party application deployed coresident with a Contact Center Tier 3 application causes that application to fail in performance or function, the customer must address the issue by moving the applications to other servers as necessary to alleviate the failure.}}

For coresidency restrictions specific to individual Unified Communications applications that run on VMs, see the Unified Communications Virtualization Sizing Guideline docwiki.

The following section depicts the CCE sample UCS deployments compliant to the coresidency rules described above.

== Sample CCE Deployments ==

'''Notes'''

#The ESXi Servers listed in these tables can be deployed on either a B-Series or C-Series hardware platform.
#Although the sample deployments in these tables reflect the C-Series restriction that the HDS cannot coreside with a Router, Logger, or a PG, this restriction is '''not''' present on a B-Series hardware platform.
#For deployments where Historical Data Servers (HDSs) are coresident, two RAID 5 groups (one for each HDS) are recommended.
#Any deployment > 2k agents requires at least 2 chassis
#It may be preferable to place your domain controller on bare metal rather than in the UCS B-series chassis itself. When a power failure occurs, the vCenter login credentials are dependent on Active Directory, leading to a potential chicken-and-egg problem if the domain controller is down as well.
#ACE (for CUIC) and CUSP (for CVP) components are not supported virtualized on UCS; these components are deployed on separate hardware. Please review the product SRND for more details.
#'''12,000''' agent is supported from 8.5(3) version onwards and '''requires''' Windows 2008 R2 '''Enterprise edition''' and SQL Server 2005 '''Enterprise Edition'''. Refer to BOM for more details

=== ROGGER Example 1 ===

{| class="wikitable" border="1"
|+ ROGGER (up to 450 CTIOS Agents, or 297 CAD Agents) with 150 IPIVR or 150 CVP ports (N+N), optional 50 CUIC reporting users, as examples
|-
! colspan="4" | Chassis X (B series)/ Rack of C series rack mount Servers
! colspan="4" | Chassis Y (B series)/ Rack of C series rack mount Servers
|-
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
|-
| rowspan="4" | ESXi Server A-1
| Rogger A
| 4
| 4
| rowspan="4" | ESXi Server B-1 
| Rogger B
| 4
| 4
|-
| Agent PG A (generic PG w/ optional VRU), CTIOS/CAD, optional MR PG
| 1
| 2
| Agent PG B (generic PG w/ optional VRU), CTIOS/CAD, optional MR PG
| 1
| 2
|- style="background: rgb(255,224,200)"
| Domain Controller A
| 1
| 2
| Domain Controller B
| 1
| 2
|-
| style="background: rgb(255,224,200)" | Support Tools 
| style="background: rgb(255,224,200)" | 1
| style="background: rgb(255,224,200)" | 2
| CVP Op Svr
| 2 
| 2 
|-
| rowspan="2" | ESXi Server A-2
| AW-HDS-DDS 1
| 4
| 4
| rowspan="2" | ESXi Server B-2
| AW-HDS-DDS 2
| 4
| 4
|- style="background: rgb(255,224,200)"
| CUIC 1
| 4
| 6
| CUIC 2
| 4
| 6
|-
| rowspan="3" | ESXi Server A-3
| UCM Subscriber 1
| 2
| 6
| rowspan="3" | ESXi Server B-3
| UCM Subscriber 2
| 2
| 6
|-
| UCM Publisher
| 2
| 6
| 
| 
| 
|- style="background: rgb(255,224,200)"
| IPIVR 1 or CUP Srv 1
| 2
| 4
| IPIVR 2 or CUP Srv 2
| 2
| 4
|-
| rowspan="2" | ESXi Server A-4
| CVP Call+VXML Srv 1
| 4
| 4
| rowspan="2" | ESXi Server B-4
| CVP Call+VXML Srv 2
| 4
| 4
|- style="background: rgb(255,224,200)"
| CVP Rpt Srv 1
| 4
| 4
| CVP Media Server
| 2
| 2
|-
! colspan="8" | '''Legend'''
|-
| Not shaded
| colspan="7" | Required
|- style="background: rgb(255,224,200)"
| Shaded
| colspan="7" | Optional
|}

=== ROGGER Example 2 ===

{| class="wikitable" border="1"
|+ ROGGER (up to 2,000 CTIOS Agents, or up to 1,000 CAD Agents) with 600 IPIVR or 900 CVP ports (N+N), optional 200 CUIC reporting users, CCMP 1,500 users, as examples
|-
! colspan="4" | Chassis X (B series)/ Rack of C series rack mount Servers
! colspan="4" | Chassis Y (B series)/ Rack of C series rack mount Servers
|-
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
|-
| rowspan="4" | ESXi Server A-1
| Rogger A
| 4
| 4
| rowspan="4" | ESXi Server B-1
| Rogger B
| 4
| 4
|-
| Agent PG A (generic PG w/ optional VRU, CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| Agent PG B (generic PG w/ optional VRU, CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|- style="background: rgb(255,224,200)"
| Domain Controller A
| 1
| 2
| Domain Controller B
| 1
| 2
|- style="background: rgb(255,224,200)"
| Support Tools 
| 1 
| 2 
|-
| rowspan="2" | ESXi Server A-2
| AW-HDS-DDS 1
| 4
| 4
| rowspan="2" | ESXi Server B-2
| AW-HDS-DDS 2
| 4
| 4
|- style="background: rgb(255,224,200)"
| AW-HDS-DDS 3 
| 4
| 4
| AW-HDS-DDS 4 
| 4
| 4
|-
| rowspan="4" | ESXi Server A-3 
| UCM Subscriber 1
| 2
| 6
| rowspan="4" | ESXi Server B-3 
| UCM Subscriber 3
| 2
| 6
|-
| UCM Subscriber 2 
| 2
| 6
| UCM Subscriber 4 
| 2 
| 6 
|-
| UCM Publisher
| 2 
| 6 
| CVP Op Srv 
| 2 
| 2 
|- style="background: rgb(255,224,200)"
| IPIVR 1 or CUP Srv 1 
| 2 
| 4 
| IPIVR 2 or CUP Srv 2 
| 2 
| 4 
|-
| rowspan="2" | ESXi Server A-4
| CVP Call+VXML Srv 1
| 4
| 4
| rowspan="2" | ESXi Server B-4
| CVP Call+VXML Srv 2
| 4
| 4
|- style="background: rgb(255,224,200)"
| CVP Rpt Srv 1
| 4
| 4
| CVP Rpt Srv 2
| 4
| 4
|-
| rowspan="2" | ESXi Server A-5 
| style="background: rgb(255,224,200)" | CUIC1
| style="background: rgb(255,224,200)" | 4 
| style="background: rgb(255,224,200)" | 6 
| rowspan="2" | ESXi Server B-5 
| style="background: rgb(255,224,200)" | CCMP (all in one)
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
|- style="background: rgb(255,224,200)"
| CVP Media Server
| 2
| 2
| CUIC 2
| 4
| 6
|-
! colspan="8" | '''Legend'''
|-
| Not shaded
| colspan="7" | Required
|- style="background: rgb(255,224,200)"
| Shaded
| colspan="7" | Optional
|}

=== ROGGER Example 3 ===

{| style="width: 1057px; height: 574px" class="wikitable" border="1"
|+ ROGGER (up to 4,000 CTIOS Agents, or up to 2,000 CAD Agents) with 1,200 IPIVR or 1,800 CVP ports (N+N), optional 200 CUIC reporting users, CCMP 1,500 users, as examples
|-
! colspan="4" | Chassis X (B series)/ Rack of C series rack mount Servers
! colspan="4" | Chassis Y (B series)/ Rack of C series rack mount Servers
|-
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
|-
| rowspan="2" | ESXi Server A-1
| Rogger A
| 4
| 4
| rowspan="2" | ESXi Server B-1
| Rogger B
| 4
| 4
|-
| Agent PG 1A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| Agent PG 1B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| rowspan="4" | ESXi Server A-2 
|-
| VRU PG A
| 2
| 2
| rowspan="3" | ESXi Server B-2 
| VRU PG B 
| 2
| 2
|-
| style="background: rgb(255,224,200)" | Support Tools 
| style="background: rgb(255,224,200)" | 1 
| style="background: rgb(255,224,200)" | 2 
| CVP Op Srv
| 2 
| 2 
|- style="background: rgb(255,224,200)"
| Domain Controller A 
| 1
| 2
| Domain Controller B 
| 1
| 2
|-
| rowspan="2" | ESXi Server A-3
| width="145" | Agent PG 2A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| rowspan="2" | ESXi Server B-2 
| Agent PG 2B (CTIOS/CAD, optional MR PG, SIP Dialer)
| width="145" | 2
| 4
|- style="background: rgb(255,224,200)"
| CVP Rpt Srv 1
| 4
| 4
| CVP Rpt Srv 2
| 4
| 4
|-
| rowspan="2" | ESXi Server A-4
| AW-HDS-DDS 1
| 4
| 4
| rowspan="2" | ESXi Server B-3
| AW-HDS-DDS 2
| 4
| 4
|- style="background: rgb(255,224,200)"
| AW-HDS-DDS 3 
| 4
| 4
| AW-HDS-DDS 4 
| 4
| 4
|-
| rowspan="4" | ESXi Server A-5
| UCM Subscriber 1
| 2
| 6
| rowspan="4" | ESXi Server B-4
| UCM Subscriber 2
| 2
| 6
|-
| UCM Subscriber 3
| 2
| 6
| UCM Subscriber 4
| 2
| 6
|-
| UCM Publisher
| 2
| 6
| 
| 
| 
|- style="background: rgb(255,224,200)"
| IPIVR 1
| 2
| 4
| IPIVR 3
| 2
| 4
|-
| rowspan="4" | ESXi Server A-6
| UCM Subscriber 5
| 2
| 6
| rowspan="4" | ESXi Server B-5
| UCM Subscriber 6
| 2
| 6
|-
| UCM Subscriber 7
| 2
| 6
| UCM Subscriber 8
| 2
| 6
|- style="background: rgb(255,224,200)"
| IPIVR 2 
| 2
| 4
| IPIVR 4 
| 2
| 4
|- style="background: rgb(255,224,200)"
| CUP Server 1 
| 2
| 4
| CUP Server 2 
| 2
| 4
|-
| rowspan="2" | ESXi Server A-7
| CVP Call+VXML Srv 1
| 4
| 4
| rowspan="2" | ESXi Server B-5
| CVP Call+VXML Srv 2
| 4
| 4
|-
| CVP Call+VXML Srv 3
| 4
| 4
| CVP Call+VXML Srv 4
| 4
| 4
|-
| rowspan="2" | ESXi Server A-7 
| style="background: rgb(255,224,200)" | CVP Media Server
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 2
| rowspan="2" | ESXi Server B-6 
| style="background: rgb(255,224,200)" | CUIC 2
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 6
|- style="background: rgb(255,224,200)"
| CUIC 1
| 4
| 6
| CCMP (all in one)
| 4
| 4
|-
| colspan="9" | 
|-
| Not shaded
| colspan="7" | Required
|- style="background: rgb(255,224,200)"
| Shaded
| colspan="7" | Optional
|}

=== Router/Logger Example 1 ===

{| style="width: 1057px; height: 574px" class="wikitable" border="1"
|+ Router/Logger (up to 8,000 CTIOS Agents, or up to 4,000 CAD Agents) with 3,600 CVP ports (N+N), optional 400 CUIC reporting users, CCMP 8,000 users, as examples
|-
! colspan="4" | Chassis X (B series)/ Rack of C series rack mount Servers
! colspan="4" | Chassis Y (B series)/ Rack of C series rack mount Servers
|-
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
|-
| rowspan="5" | ESXi Server A-1
| width="145" | Router A
| 2
| 4
| rowspan="5" | ESXi Server B-1
| width="145" | Router B
| 2
| 4
|-
| width="145" | Agent PG 1A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| width="145" | Agent PG 1B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| width="145" | Agent PG 3A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| width="145" | Agent PG 3B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|- style="background: rgb(255,224,200)"
| width="145" | Domain Controller A 
| 1
| 2
| width="145" | Domain Controller B 
| 1
| 2
|-
| style="background: rgb(255,224,200)" | Support Tools 
| style="background: rgb(255,224,200)" | 1
| style="background: rgb(255,224,200)" | 2
| width="145" |  
|  
|  
|-
| rowspan="3" | ESXi Server A-2
| width="145" | Logger A
| 4
| 4
| rowspan="3" | ESXi Server B-2
| width="145" | Logger B
| 4
| 4
|-
| width="145" | Agent PG 2A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| width="145" | Agent PG 2B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| width="145" | Agent PG 4A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| width="145" | Agent PG 4B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| rowspan="2" | ESXi Server A-3
| width="145" | HDS-DDS 1
| 4
| 4
| rowspan="2" | ESXi Server B-3
| width="145" | HDS-DDS 2
| 4
| 4
|-
| width="145" | AW-HDS 1
| 4
| 4
| width="145" | AW-HDS 2
| 4
| 4
|-
| rowspan="2" | ESXi Server A-4
| style="background: rgb(255,224,200)" | AW-HDS 3 
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
| rowspan="2" | ESXi Server B-4
| style="background: rgb(255,224,200)" | AW-HDS 4 
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
|- style="background: rgb(255,224,200)"
| width="145" | AW-HDS 5 
| 4
| 4
| width="145" | AW-HDS 6 
| 4
| 4
|-
| rowspan="4" | ESXi Server A-5
| width="145" | UCM 1 Subscriber 1
| 2
| 6
| rowspan="4" | ESXi Server B-5
| width="145" | UCM 1 Subscriber 2
| 2
| 6
|-
| width="145" | UCM 2 Subscriber 1
| 2
| 6
| width="145" | UCM 2 Subscriber 2
| 2
| 6
|-
| width="145" | UCM 1 Subscriber 3
| 2
| 6
| width="145" | UCM 1 Subscriber 4
| 2
| 6
|-
| width="145" | UCM 2 Subscriber 3
| 2
| 6
| width="145" | UCM 2 Subscriber 4
| 2
| 6
|-
| rowspan="4" | ESXi Server A-6
| width="145" | UCM 1 Subscriber 5
| 2
| 6
| rowspan="4" | ESXi Server B-6
| width="145" | UCM 1 Subscriber 6
| 2
| 6
|-
| width="145" | UCM 2 Subscriber 5
| 2
| 6
| width="145" | UCM 2 Subscriber 6
| 2
| 6
|-
| width="145" | UCM 1 Subscriber 7
| 2
| 6
| width="145" | UCM 1 Subscriber 8
| 2
| 6
|-
| width="145" | UCM 2 Subscriber 7
| 2
| 6
| width="145" | UCM 2 Subscriber 8
| 2
| 6
|-
| rowspan="2" | ESXi Server A-7 
| width="145" | UCM Publisher 1
| 2
| 6
| rowspan="2" | ESXi Server B-7 
| style="background: rgb(255,224,200)" | CVP Op Srv
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 2
|- style="background: rgb(255,224,200)"
| width="145" | CUP Server 1 
| 2
| 4
| width="145" | CUP Server 2 
| 2
| 4
|-
| rowspan="2" | ESXi Server A-8
| width="145" | UCM Publisher 2
| 2
| 6
| rowspan="2" | ESXi Server B-8
| style="background: rgb(255,224,200)" | CVP Rpt Srv 2
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
|-
| style="background: rgb(255,224,200)" | CVP Rpt Srv 1
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
| width="145" | 
| 
| 
|-
| rowspan="2" | ESXi Server A-9
| width="145" | CVP Call+VXML Srv 1
| 4
| 4
| rowspan="2" | ESXi Server B-9
| width="145" | CVP Call+VXML Srv 2
| 4
| 4
|-
| width="145" | CVP Call+VXML Srv 3
| 4
| 4
| width="145" | CVP Call+VXML Srv 4
| 4
| 4
|-
| rowspan="2" | ESXi Server A-10
| width="145" | CVP Call+VXML Srv 5
| 4
| 4
| rowspan="2" | ESXi Server B-10
| width="145" | CVP Call+VXML Srv 6
| 4
| 4
|-
| width="145" | CVP Call+VXML Srv 7
| 4
| 4
| width="145" | CVP Call+VXML Srv 8
| 4
| 4
|-
| rowspan="2" | ESXi Server A-11
| style="background: rgb(255,224,200)" | CVP Media Server A 
| style="background: rgb(255,224,200)" | 2 
| style="background: rgb(255,224,200)" | 2 
| rowspan="2" | ESXi Server B-11 
| style="background: rgb(255,224,200)" | CVP Media Server B 
| style="background: rgb(255,224,200)" | 2 
| style="background: rgb(255,224,200)" | 2 
|-
| VRU PG A 
| 2 
| 2 
| VRU PG B 
| 2 
| 2 
|-
| rowspan="2" | ESXi Server A-12
| style="background: rgb(255,224,200)" | CUIC 1 
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 6
| rowspan="2" | ESXi Server B-12 
| style="background: rgb(255,224,200)" | CUIC 2 
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 6
|- style="background: rgb(255,224,200)"
| width="145" | CUIC 3 
| 4
| 6
| width="145" | CUIC 4 
| 4
| 6
|-
| ESXi Server A-13 
| style="background: rgb(255,224,200)" | CCMP DB 
| style="background: rgb(255,224,200)" | 8
| style="background: rgb(255,224,200)" | 4
| ESXi Server B-13
| style="background: rgb(255,224,200)" | CCMP Web/App Svr 
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
|-
! colspan="8" | '''Legend'''
|-
| Not shaded
| colspan="7" | Required
|- style="background: rgb(255,224,200)"
| Shaded
| colspan="7" | Optional
|}

 

 

  

=== Router/Logger Example 2 ===

 Router/Logger (up to 12,000 CTIOS Agents) with 3,600 CVP ports (N+N), optional 400 CUIC reporting users, CCMP 8,000 users, as examples

{| border="1" cellspacing="1" cellpadding="1" width="1057"
|-
| colspan="4" | '''Chassis X (B series)/ Rack of C series rack mount Servers'''
| colspan="4" | '''Chassis Y (B series)/ Rack of C series rack mount Servers'''
|-
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
|-
| rowspan="2" | ESXi Server A-1
| Logger A
| 4
| 8
| rowspan="2" | ESXi Server B-1
| Logger B
| 4
| 8
|-
| Router A
| 4
| 8
| Router B
| 4
| 8
|-
| rowspan="3" | ESXi Server A-2
| Agent PG 1A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| rowspan="3" | ESXi Server B-2
| Agent PG 1B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| Agent PG 3A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| Agent PG 3B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| Agent PG 5A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| Agent PG 5B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| rowspan="3" | ESXi Server A-3
| Agent PG 2A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| rowspan="3" | ESXi Server B-3
| Agent PG 2B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| Agent PG 4A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| Agent PG 4B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| Agent PG 6A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| Agent PG 6B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| rowspan="2" | ESXi Server A-4
| HDS-DDS 1
| 4
| 8
| rowspan="2" | ESXi Server B-4
| HDS-DDS 2
| 4
| 8
|-
| AW-HDS 1
| 4
| 8
| AW-HDS 2
| 4
| 8
|-
| rowspan="2" | ESXi Server A-5
| AW-HDS 3
| 4
| 8
| rowspan="2" | ESXi Server B-5
| AW-HDS 4
| 4
| 8
|-
| AW-HDS 5
| 4
| 8
| AW-HDS 6
| 4
| 8
|-
| rowspan="3" | ESXi Server A-6
| UCM 1 Subscriber 1
| 2
| 6
| rowspan="3" | ESXi Server B-6
| UCM 1 Subscriber 2
| 2
| 6
|-
| UCM 2 Subscriber 1
| 2
| 6
| UCM 2 Subscriber 2
| 2
| 6
|-
| UCM 3 Subscriber 1
| 2
| 6
| UCM 3 Subscriber 2
| 2
| 6
|-
| rowspan="3" | ESXi Server A-7
| UCM 1 Subscriber 3
| 2
| 6
| rowspan="3" | ESXi Server B-7
| UCM 1 Subscriber 2
| 2
| 6
|-
| UCM 2 Subscriber 3
| 2
| 6
| UCM 2 Subscriber 2
| 2
| 6
|-
| UCM 3 Subscriber 3
| 2
| 6
| UCM 3 Subscriber 2
| 2
| 6
|-
| rowspan="3" | ESXi Server A-8
| UCM 1 Subscriber 5
| 2
| 6
| rowspan="3" | ESXi Server B-8
| UCM 1 Subscriber 2
| 2
| 6
|-
| UCM 2 Subscriber 5
| 2
| 6
| UCM 2 Subscriber 2
| 2
| 6
|-
| UCM 3 Subscriber 5
| 2
| 6
| UCM 3 Subscriber 2
| 2
| 6
|-
| rowspan="3" | ESXi Server A-9
| UCM 1 Subscriber 7
| 2
| 6
| rowspan="3" | ESXi Server B-9
| UCM 1 Subscriber 2
| 2
| 6
|-
| UCM 2 Subscriber 7
| 2
| 6
| UCM 2 Subscriber 2
| 2
| 6
|-
| UCM 2 Subscriber 7
| 2
| 6
| UCM 3 Subscriber 2
| 2
| 6
|-
| rowspan="4" | ESXi Server A-10
| style="background: rgb(255,224,200)" | Domain Controller
| style="background: rgb(255,224,200)" | 1
| style="background: rgb(255,224,200)" | 2
| rowspan="4" | ESXi Server B-10
| style="background: rgb(255,224,200)" | Domain Controller
| style="background: rgb(255,224,200)" | 1
| style="background: rgb(255,224,200)" | 1
|-
| UCM Publisher 1
| 2
| 6
| style="background: rgb(255,224,200)" | CVP Op Srv
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 2
|-
| style="background: rgb(255,224,200)" | CUP Server 1 
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | CUP Server 2 
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 4
|-
| Administration Server - AW
| 1
| 2
| Administration Server - AW
| 1
| 2
|-
| rowspan="2" | ESXi Server A-11
| UCM Publisher 2
| 2
| 6
| rowspan="2" | ESXi Server B-11
| style="background: rgb(255,224,200)" | CVP Rpt Srv 2
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
|-
| style="background: rgb(255,224,200)" | CVP Rpt Srv 1
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
| UCM Publisher 3
| 2
| 6
|-
| rowspan="2" | ESXi Server A-12
| CVP Call+VXML Srv 1
| 4
| 4
| rowspan="2" | ESXi Server B-12
| CVP Call+VXML Srv 2
| 4
| 4
|-
| CVP Call+VXML Srv 3
| 4
| 4
| CVP Call+VXML Srv 4
| 4
| 4
|-
| rowspan="2" | ESXi Server A-13
| CVP Call+VXML Srv 5
| 4
| 4
| rowspan="2" | ESXi Server B-13
| CVP Call+VXML Srv 6
| 4
| 4
|-
| CVP Call+VXML Srv 7
| 4
| 4
| CVP Call+VXML Srv 8
| 4
| 4
|-
| rowspan="2" | ESXi Server A-14
| CVP Call+VXML Srv 9
| 4
| 4
| rowspan="2" | ESXi Server B-14
| CVP Call+VXML Srv 10
| 4
| 4
|-
| CVP Call+VXML Srv 11
| 4
| 4
| CVP Call+VXML Srv 12
| 4
| 4
|-
| rowspan="2" | ESXi Server A-15
| style="background: rgb(255,224,200)" | CVP Media Server A
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 2
| rowspan="2" | ESXi Server B-15
| style="background: rgb(255,224,200)" | CVP Media Server B
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 2
|-
| VRU PG A
| 2
| 2
| VRU PG B
| 2
| 2
|-
| rowspan="2" | ESXi Server A-16
| CUIC 1 
| 4
| 6
| rowspan="2" | ESXi Server B-16
| CUIC 2 
| 4
| 6
|-
| CUIC 3 
| 4
| 6
| CUIC 4
| 4
| 6
|-
| rowspan="2" | ESXi Server A-17
| CUIC 5
| 4
| 6
| rowspan="2" | ESXi Server B-17
| CUIC 6
| 4
| 6
|-
| CUIC 7
| 4
| 6
| CUIC 8
| 4
| 6
|-
| ESXi Server A-18
| style="background: rgb(255,224,200)" | CCMP DB
| style="background: rgb(255,224,200)" | 8
| style="background: rgb(255,224,200)" | 4
| ESXi Server B-18
| style="background: rgb(255,224,200)" | CCMP Web/App Svr 
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
|-
! colspan="8" | '''Legend'''
|-
| Not shaded
| colspan="7" | Required
|- style="background: rgb(255,224,200)"
| Shaded
| colspan="7" | Optional
|}

 

 

= Hybrid Deployment Options =

Some Unified Contact Center deployments are supported in a "hybrid" fashion whereby certain components must be deployed on (bare-metal) Media Convergence Servers (MCS) or generic servers, and other components are deployed in virtual machine guests on Unified Computing System (UCS) or MCS servers. The following sub-sections provide further details on these hybrid deployment options.

== Cisco Unified Contact Center Hosted ==

*NAM Rogger is deployed on a (bare-metal) quad CPU server as specified in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release 8.0(1).]
*Each customer instance central controller (CICM) connecting to the NAM may be deployed in its own virtual machine as a Rogger or separate Router/Logger pair on UCS hardware. Multiple CICM instances are not supported collocated in one VM. Existing published rules and capacities apply to CICM Rogger and Router/Logger VMs. (Note: CICMs are not supported on bare-metal UCS.)
*As in Enterprise deployments, each Agent PG is deployed in its own virtual machine. Multi-instance Agent PGs are not supported in a single VM. Existing published rules and capacities apply to PGs in Hosted deployments.

== Parent/Child Deployments ==

*The parent ICM is deployed on (bare-metal) servers as specified in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release 8.0(1).].
*The Unified Contact Center Enterprise (or Express) child may be deployed virtualized according to existing published VM requirements.
*The Unified Contact Center Enterprise Gateway PG and System PG are each deployed in its own virtual machine; agent capacity (and resources allocated to the VM) are the same as the Unified CCE Agent PG @ 2,000 agent capacity. Use the same virtual machine OVA template to create the CCE Gateway or System PG VM.

= Cisco Unified CCE-Specific Information for OVA Templates =

See the following websites for more information: 

*[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates)#Unified_Contact_Center_Enterprise Unified Communications Virtualization Downloads (including OVA/OVF Templates).]
*[http://www.cisco.com/cisco/software/release.html?mdfid=268439622&release=1.1&relind=AVAILABLE&flowid=5210&softwareid=283914286&rellifecycle=&reltype=latest Unified CCE OVA Templates]

 

== Creating Virtual Machines by Deploying the OVA Templates ==

In the vSphere client, perform the following steps to deploy the Virtual machines.

#Highlight the host or cluster to which you wish the VM to be deployed.
#Select '''File''' > '''Deploy OVF Template'''.
#Click the '''Deploy from File''' radio button and specify the name and location of the file you downloaded in the previous section '''OR '''click the '''Deploy from URL''' radio button and specify the complete URL in the field, then click '''Next'''.
#Verify the details of the template, and click '''Next'''.
#Give the VM you are about to create a name, and choose an inventory location on your host, then click '''Next'''.
#Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click '''Next'''.
#Choose a virtual network for the VM, then click '''Next'''.
#Verify the deployment settings, then click '''Finish'''.

== Notes ==

:*VM CPU affinity is not supported. You don't need to set CPU affinity for the VMs that are running Unified CCE applications on the VMware ESXi on UCS platform.
:*VM resource Reservation - VM resource reservation is not supported for the VMs that are running Unified CCE applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations.
:*You cannot change the computing resource configuration of your VM at any time.
:*You can never go below the minimum VM computing resource requirements as defined in the OVA templates.
:*ESXi Server hyperthread is enabled by default.

== Preparing for Windows Installation ==

In the vSphere client, perform the following steps to prepare for operating system installation.

#Right click on the virtual machine you want to edit and select '''Edit Settings'''. A Virtual Machine Properties dialog appears.
#On the Hardware tab, select '''CD/DVD Drive 1'''. Under Device Type, select '''Datastore ISO File''' and enter the location of the operating system ISO.
#Click '''OK''' to save setting changes.
#Power up your VM and continue with operating system installation.

 

= Remote Control of the Virtual Machines =

For administrative tasks, you can use either Windows Remote Desktop or the VMware Infrastructure Client for remote control. The contact center supervisor can access the ClientAW VM using Windows Remote Desktop.

= Installing VMware Tools =

The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Please refer to VMware documentation for instructions on installing or upgrading VMware Tools on the VM with Windows operating system.

= Installing Unified CCE Components on Virtual Machines =

Install the Unified CCE components after you create and configure the virtual machine. Installation of the Unified CCE components on a virtual machine is the same as the installation of the components on physical hardware.

Refer to the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_installation_guides_list.html Unified CCE documentation] for the steps to install Unified CCE components. You can install the supported Virus Scan software, the Cisco Security Agent(CSA), or any other software in the same way as on physical hardware.

= Migrating Unified CCE Components to Virtual Machines =

Migrate the Unified CCE components from physical hardware or another virtual machine after you create and configure the virtual machine. Migration of these Unified CCE software components to a VM is the same as the migration of the components to new physical hardware and follows existing policies. It requires a Tech Refresh as described in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/installation/guide/icm80ug.pdf Upgrade Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted Release 8.0(1)].

= Configuring the ESXi Data Store Block Size for Administration and Data Server =

This section is applicable to storing Virtual Machines on C-210 local storage. The C-210 Server comes with a default local storage configured with two sets of RAID groups. Disk 1-2 is RAID 1, while the remaining disks (3-10) are RAID 5.

The creation of the virtual machine for the Unified CCE Administration and Data Server requires a large virtual disk size. You must follow the steps described below to configure the ESXi data store block size to 2MB for it to handle the Unified CCE Administration and Data Server virtual disk size requirement before you deploy the OVAs for the following Unified CCE components:

:*AW-HDS
:*AW-HDS-DDS
:*HDS-DDS

 Steps to configure the ESXi data store block size to 2MB:

#After you install ESXi on the first disk array group (RAID 1 with disk 1 and disk 2), boot ESXi 4.0 and use VMware vSphere Client to connect to the ESXi host.
#On the Configuration tab for the host, select Storage in the box labeled Hardware. Select the second disk array group with RAID-5 configuration, and you will see in the formatting of “Datastore Details” that the block size is by default 1MB.
#Right-click on this data store and delete it. We will add the data store back in the following steps.
#Click on the “Add Storage…” and select the Disk/LUN.
#The data store that was just deleted will now be available to add, select it.
#In the configuration for this data store you will now be able to select the block size, select 2MB, and finish the adding of the storage to the ESXi host. This storage is now available for deployment of the virtual machines that requires large disk size, such as the Administration and Data Servers.

= Timekeeping Best Practices for Windows =

You should follow the best practices outlined in the VMware Knowledge Base article [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1318 VMware KB: Timekeeping best practices for Windows].

*ESXi hosts and domain controllers should synchronize the time from the same NTP source.
*When Unified CCE virtual machines join the domain, they synchronize the time with the domain controller automatically using w32time.
*Be sure that '''Time synchronization between the virtual machine and the host operating system''' in the VMware Tools tool box GUI of the Windows Server 2003 guest operating system remains deselected; this checkbox is deselected by default.

= System Performance Monitoring Using ESXi Counters =

:*Make sure that you follow VMware's ESXi best practices and SAN vendor's best practices for optimal system performance. 
:*VMware provides a set of system monitoring tools for the ESXi platform and the VMs. These tools are accessible through the VMware Infrastructure Client or through VirtualCenter.
:*You can use Windows Performance Monitor to monitor the performance of the VMs. Be aware that the CPU counters may not reflect the physical CPU usage since the Windows Operating System has no direct access to the physical CPU.
:*You can use Unified CCE Serviceability Tools and Unified CCE reports to monitor the operation and performance of the Unified CCE system.
:*The ESXi Server and the virtual machines must operate within the limit of the following ESXi performance counters.

You can use the following ESXi counters as performance indicators.

{| class="wikitable FCK__ShowTableBorders"
|-
! Category
! Object
! Measurement
! Units
! Description
! Performance Indication and Threshold
|-
| CPU
|
:*ESXi Server
:*VM

| CPU Usage (Average)
| Percent
| CPU Usage Average in percentage for:
:*ESXi server
:*Virtual machine

| Less than 60%.
|-
| CPU
|
:*ESXi Server Processor#
:*VM_vCPU#

| CPU Usage 0 - 7 (Average)
| Percent
| CPU Usage Average for:
:*ESXi server for processors 0 to 7
:*Virtual machine vCPUs

| Less than 60%
|-
| CPU
| VM
| CPU Ready
| mSec
| The time a virtual machine or other process waits in the queue in a ready-to-run state before it can be scheduled on a CPU.
| Less than 150 mSec. If it is greater than 150 mSec doing system failure, you should investigate and understand why the machine is so busy.
|-
| Memory
|
:*ESXi Server
:*VM

| Memory Usage (Average)
| Percent
| Memory Usage = Active/ Granted * 100
| Less than 80%
|-
| Memory
|
:*ESXi Server
:*VM

| Memory Active (Average)
| KB
| Memory that is actively used or being referenced by the guest OS and its applications. When it exceeds the amound of memory on the host, the server starts swap.
| Less than 80% of the Granted memory
|-
| Memory
|
:*ESXi Server
:*VM

| Memory Balloon (Average)
| KB
| ESXi use balloon driver to recover memory from less memory-intensive VMs so it can be used by those with larger active sets of memory.
| Since we do not over commit the memory, this should be 0 or very low. Note: ESXi performs memory ballooning before memory swap.
|-
| Memory
|
:*ESXi Server
:*VM

| Memory Swap used (Average)
| KB
| ESXi Server swap usage. Use the disk for RAM swap
| Since we do not over commit the memory, this should be 0 or very low
|-
| Disk
|
:*ESXi Server
:*VM

| Disk Usage (Average)
| KBps
| Disk Usage = Disk Read rate + Disk Write rate
| Ensure that your SAN is configured to handle this amount of disk I/O.
|-
| Disk
|
:*ESXi Server vmhba ID
:*VMbha ID

| Disk Usage Read rate 
| KBps
| Rate of reading data from the disk
| Ensure that your SAN is configured to handle this amount of disk I/O
|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

| Disk Usage Write rate
| KBps
| Rate of writing data to the disk
| Ensure that your SAN is configured to handle this amount of disk I/O
|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

| Disk Commands Issued
| Number
| Number of disk commands issued on this disk in the period.
| Ensure that your SAN is configured to handle this amount of disk I/O
|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

| Disk Command Aborts
| Number
| Number of disk commands aborted on this disk in the period. Disk command aborts when the disk array is taking too long to respond to the command. (Command timeout)
'''This counter should be zero. A non-zero value indicates storage performance issue.'''

|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

| Disk Command Latency
| mSec
| The average amount of time taken for a command from the perspective of a Gust OS. Disk Command Latency = Kernel Command Latency + Physical Device Command Latency.
| '''15ms latencies or greater indicates a possible over-utilized, misbehaving, or mis-configured disk array.'''
|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

| Kernel Disk Command Latency
| mSec
| The average time spent in ESXi Server VMKernel per command
| '''Kernel Command Latency should be very small in comparison to the Physical Device Command Latency, and it should be close to zero.  Kernel Command Latency can be high, or even higher than the Physical Device Command Latency if there is a lot of queuing in the ESXi kernel.'''
|-
| Network
|
:*ESXi Server
:*VM

| Network Usage (Average)
| KBps
| Network Usage = Data receive rate + Data transmit rate
| Less than 30% of the available network bandwidth. For example, it should be less than 300Mps for 1G network.
|-
| Network
|
:*ESXi Server vmnic ID
:*VM vmnic ID

| Network Data Receive Rate
| KBps
| Less than 30% of the available network bandwidth. For example, it should be less than 300Mps for 1G network.
|-
| Network
|
:*ESXi Server vmnic ID
:*VM vmnic ID

| Network Data Transmit Rate
| KBps
| The average rate at which data is transmitted on this Ethernet port
| Less than 30% of the available network bandwidth.  For example, it should be less than 300Mps for 1G network.
|}

= System Performance Monitoring Using Windows Perfmon Counters =

You must comply with the best practices described in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/design/guide/uccesrnd80.pdf Cisco Unified Contact Center Enterprise Solution Reference Network Design(SRND), Release 8.0] section System Performance Monitoring, and in Chapter 8 Performance Counters in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/configuration/guide/icm80srvg.pdf Serviceability Best Practices Guide for Unified ICM/Contact Center Enterprise].

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

[[Category:Unified_Contact_Center_Enterprise]]

Unified Communications VMware Requirements

2012-01-05T21:39:01Z

Sdurvasu: 1 revision

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

This article describes VMware requirements, feature support, and services and support contracts for virtualized Unified Communications applications.

== Introduction: Mandatory VMware Products and Services ==

'''Note:''' This page only covers VMware product/version/feature support.

:*It does '''not''' cover compute/network/storage hardware support policy for UC virtualization.
:*It does '''not''' cover application co-residency support policy for UC virtualizatoin.
:*See other links at http://www.cisco.com/go/uc-virtualized for these details.

 

'''VMware vSphere ESXi is mandatory''' for UC virtualization and UC on UCS.

:*UC is only supported on UCS servers with VMware vSphere ESXi.
:*See rest of this page for other details on VMware product, version and feature support.
:*'''Nonvirtualized, physical, or bare-metal installations are not supported''' for UC on UCS.

 

'''VMware vCenter''' is:

:*'''Mandatory''' for all Specs-based deployments
:*'''Optional''' for Tested Reference Configuration deployments.

 

For UC on UCS, VMware vSphere ESXi and vCenter may be purchased from Cisco or customer provided. For specs-based with HP/IBM, all VMware software must be customer-provided. See [[Before You Buy or Deploy - Considerations for Design and Procurement]] for information on VMware purchase options. 

Compatibility of UC apps/versions with VMware vSphere ESXi versions varies by UC app and is outlined later in this document. See the following links for details on "legacy" virtualization support (i.e. 7.x of UC apps with VMware vSphere on limited 3rd-party servers):

:*[http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html Cisco Unity Virtualization Design Guide]
:*[http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_7_5/user/guide/VirtualizationGde753.pdf Virtualization Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted 7.5(3)]

 

'''Note:''' in all cases, the customer is required to have a valid service contract (either with Cisco or with VMware, depending on what/how purchased) to be supported. See [[#Services_and_Support_Contracts_for_VMware_are_Required|Services and Support Contracts for VMware are Required]] for how to ensure this is done for different Editions of Vmware vSphere ESXi. 

== Supported Virtualization Hypervisor Vendors ==

At this time, the only vendor supported for UC is VMware.

Other vendors/products - such as Microsoft Hyper-V, Citrix Xen, Red Hat KVM - are not supported for Cisco UC virtualization. 

== Supported VMware Products ==

VMware vSphere ESXi is required for Cisco UC virtualization.

*ESX and ESXi are architecture options for VMware vSphere ([http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html click here for a comparison]). UC only supports ESXi. Recall that vSphere 3.x and 4.x offered both options, but 5.0+ only offers ESXi.
*VMware vSphere ESX, regardless of version, is not supported for UC. This is due to technical reasons and [http://blogs.vmware.com/vsphere/2010/07/esx-41-is-the-last-esx-what-do-i-do-now.html VMware’s direction to transition from ESX to ESXi]. Note a VMware ESX cluster can contain VMware ESXi servers running Cisco Unified Communications.
*No other VMware server virtualization products are supported.

 

== Supported Versions of VMware vSphere ESXi ==

The minimum version for VMware vSphere ESXi is 4.0. But note a higher minimum version may be required depending on what UC apps/versions you run (see tables below) and what hardware you select.

*Note that use of VMware vSphere ESXi 4.1 requires [[Disable LRO|'''disabling the "LRO" setting as described here''']].
*Versions of VMware vSphere ESXi prior to 4.0 are not supported due to technical reasons.
*Each UC app/version will specify the required compatible Major Releases and Minor Releases of VMware vSphere ESXi (e.g. 4.0 or 4.1) in the tables below.
**Unlisted Major/Minor versions are not supported.
**Unless otherwise indicated, the base Major/Minor version shown is the minimum required.
**Some UC apps will also require a minimum Maintenance Release and will indicate if this is the case. Otherwise UC does not specify or recommend patches, updates or Maintenance Releases (e.g. 4.0 U1) for a required Major/Minor Release of vSphere ESXi. Follow recommendations of the server vendor and VMware for what you should use. Unless otherwise indicated by a UC app, UC supports all VMware vSphere ESXi patches, updates and Maintenance Releases for a supported Major/Minor Release at time of VMware launch as long as the server vendor supports them.

 

=== VMware vSphere ESXi Version Support for Call Processing and System Management Applications ===

{| class="wikitable FCK__ShowTableBorders"
|-
!
Application 

! VMware vSphere ESXi 4.0 
! VMware vSphere ESXi 4.1 
! VMware vSphere ESXi 5.0 
|-
| Unified Communications Manager (Unified CM)
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Cisco Emergency Responder (CER)
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Session Manager Edition (SME)
| 8.5+, 8.6+
| 8.5+, 8.6+
| 8.5+, 8.6+
|-
| Unified Attendant Consoles
| 8.0(3)+, 8.5+
| 8.6+
| Not supported
|-
| UC Management Suite (OM, SM, SSM, PM)
| 7.1 and later
| 7.1 and later
| Not supported
|-
| Cisco Intercompany Media Engine (CIME)
| Not supported
| 8.6(2)+
| 8.6(2)+
|}

=== VMware vSphere ESXi Version Support for Messaging and Presence Applications ===

{| style="width: 812px; height: 108px" class="wikitable FCK__ShowTableBorders"
|-
! Application 
! VMware vSphere ESXi 4.0 
! VMware vSphere ESXi 4.1 
! VMware vSphere ESXi 5.0 
|-
| Cisco Unity Connection
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
|-
| Cisco Unity
| 7.x and later
| 7.x and later
| 7.x and later
|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
| 8.0(2) and later
| 8.0(2) and later
| Not Supported
|}

 

=== VMware vSphere ESXi Version Support for Contact Center Applications ===

{{Note| For Virtual Machines that need '''more than 4 vCPUs''', the VMware vSphere ESXi '''Enterprise Plus''' licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)}}

{| style="width: 816px; height: 396px" class="wikitable FCK__ShowTableBorders"
|-
! Application
! VMware vSphere ESXi 4.0 and 4.0 Updates
! VMware vSphere ESXi 4.1  and 4.1 Updates
! VMware vSphere ESXi 5.0  and 5.0 Updates 
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]]
| 8.0(2)+ or 8.5(1)+
| 8.0(2) SU2+ or 8.5(1)+
| 8.0(2) SU4+ or 8.5(1) SU2+
|-
| [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Work Force Optimization (WFO), Quality Management (QM), and Work Force Management (WFM)]
| 8.5(1)+
| 8.5(2)+
| Not supported
|-
| [[Unified Contact Center Enterprise]] 
| ESXi 4.0 Update 1 (minimum required). See below
| See below
| See below
|-
| - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tools (not supported in 8.5x and later)
| 8.0(2)+ or 8.5(1)+
| 8.0(2)+ or 8.5(1)+
| Not supported
|-
| [[Virtualization for Unified Intelligence Center|Cisco Unified Intelligence Center]] 
| 8.0(3)+
| 8.5(2)+
| Not supported
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]
| 8.0(2)+ or 8.5(1)+
| 8.0(2)+ or 8.5(1)+
| Not supported
|-
| [[Unified Customer Voice Portal]] (all components) 
| 8.0(1)+ or 8.5(1)+
| 8.0(1)+ or 8.5(1)+
| Not supported
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| 8.5(1)+
| 8.5(2)+
| Not supported
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| 8.5(1)+
| 8.5(1)+
| Not supported
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Unified Email Interaction Manager and Web Interaction Manager]]
| 4.3(2)+
| 4.3(2)+
| Not supported
|-
| [[Virtualization for Cisco Finesse|Cisco Finesse]]
| 8.5(3)+
| 8.5(3)+
| Not supported
|}

== Support of Cisco VN-Link and Cisco Nexus 1000V ==

Note that Cisco Unified Contact Center Enterprise does NOT support this – see [[UCS Network Configuration for UCCE|UCS Network Configuration for Unified CCE]].

Unless otherwise indicated above, Cisco VN-Link, Cisco Nexus 1000V, Cisco Nexus 1010, and VM-FEX are supported by UC applications that support the VMware vNetwork Distributed Switch (see [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]).

Cisco VN-Link, Cisco Nexus® 1000V, Cisco Nexus 1010, VM-FEX and VMware vNetwork Distributed Switch all require VMware ESXi Enterprise Plus Edition (see [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]). Other editions do not support these capabilities.

For UC on UCS B-series, Cisco UCS 6100 does not currently support Layer 3 to Layer 2 COS markings. Additionally, the UC applications and operating systems cannot set the Layer 2 COS markings. Use of Cisco Nexus® 1000V is therefore strongly recommended as this is the only way to manage traffic congestion through the current UCS 6100. Please recall that traffic congestion risk will vary and is dependent on many factors such as UC vs. non-UC virtual machine count and their traffic characteristics across all blades, chassis and fabric extenders connected to the same UCS 6100.

For UC on UCS C-series, Cisco Nexus® 1000V is recommended but not mandatory as there is no intermediate UCS 6100 to design around.

For more information on Cisco VN-Link, Cisco Nexus 1000V and VM-FEX, see the following:

:*http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns892/ns894/white_paper_c11-525307.html
:*http://www.cisco.com/en/US/products/ps9902/index.html
:*http://www.cisco.com/en/US/netsol/ns1124/index.html

== Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client ==

 '''VMware vSphere Client''' (formerly branded VI Client) and '''VMware vCenter''' are management consoles for VMware vSphere hosts.

:*vSphere Client is free but only has basic management capabilities.
:*vCenter is not free as it has advanced management capabilities, but note UC may not support every feature in vCenter. vCenter is mandatory for any specs-based deployment.

 

'''VMware vSphere ESXi''' is sold in several '''Editions''' with different levels of feature support.

:*[https://www.vmware.com/products/vsphere/buy/editions_comparison.html Click here for a comparison of VMware vSphere ESXi feature Editions on vmware.com].
::*[http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html Click here for a clarification of “free ESXi 4.1” vs. “vSphere ESXi 4.1 Hypervisor Edition”] (formerly branded as "VMware ESXi Single Server Edition" or “free ESXi”).
::*For details on supported features for 4.x versions of other vSphere ESXi Editions, see your VMware account team. VMware on their web site [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010579 provides a "best effort" comparison here].
:*If buying VMware vSphere ESXi direct from VMware:
::*[http://www.vmware.com/products/vsphere/purchase-advisor/index.html Click here for VMware's Purchase Advisor for vSphere on vmware.com].
::*[https://www.vmware.com/files/pdf/vsphere_pricing.pdf Click here for an overview of VMware vSphere ESXi pricing on vmware.com].

 

There are no UC-specific restrictions on what VMware vSphere ESXi feature Edition you "can" use, but the Edition you "should" use will be determined by VMware licensing rules based on aspects of the UC deployment. The customer is responsible for selecting the correct VMware vSphere ESXi Edition based on their feature and UC application requirements. The following non-exhaustive list is provided for convenience only as examples of what must be considered under VMware's current licensing rules, which are subject to change:

:*If you want to use Cisco Nexus 1000V with UC, that requires the VMware vSphere ESXi feature "Distributed Switch" which is only available in Enterprise Plus Edition.
:*If you want to use a UC virtual machine OVA template with a large quantity of vCPU, verify the VMware vSphere ESXi Edition supports sufficient "vCPU Entitlement" for that OVA's vCPU count.
::*E.g. the Unity Connection 20K user OVA that requires 7 vCPU per VM.
:*Verify all the UC-supported VMware vSphere ESXi features you want to use are [https://www.vmware.com/products/vsphere/buy/editions_comparison.html supported by the Edition you pick].
:*The "Cisco UC Virtualization Hypervisor" is only supported for use with Business Edition 6000 and has the following restrictions:
::*It is not available or transferable for use with any other hardware or software.
::*Server Hardware restricted to UCS C200 M2 TRC#1
::*Max total vRAM across all VMs is 16 GB (of which 14 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Does not support VMware vCenter management. Does not offer any [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features like other Editions].
:*The "Cisco UC Virtualization Foundation" is only supported for use with Business Edition 6000 and UC on UCS.
::*Not available direct from VMware, only sold as part of BE6K or UC on UCS. It is not available or transferable for use with non-UCS hardware or non-UC software.
::*Server Hardware restricted to 2-socket UCS B-Series models and 2-socket UCS C-Series models.
::*Max total vRAM across all VMs is 32 GB (of which 30 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Supports VMware vCenter management (purchased separately). UC-supported [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features] limited to vStorage APIs. All other UC-supported features (including but not limited to VMware High Availability, Data Recovery, vMotion, Distributed Switch, etc.) are not offered.

 

Finally, note that UC may not support all of the features that are included in the VMware vSphere ESXi Edition you pick. This may be because the feature is N/A for a UC deployment, or it has not been sufficiently tested before UC will support, or it requires application enhancements before UC can support.

The table below lists VMware feature support by UC app/version. If the feature is supported, click on its name in the table to view UC caveats and best practices. Feature support may vary by UC app. This site will be updated as new support becomes available.

{{note| feature support for Cisco Unified Contact Center Enterprise varies by component (e.g. Peripheral Gateway) and deployment model (e.g. "Rogger") - this section will give a summary support position, but for individual components see [[Unified Contact Center Enterprise|Support for Virtualization on the ESXi/UCS Platform]].}} 

=== Legend for Feature Support Tables ===

:*Y(C) = Supported with '''C'''aveats - see [[#Best_Practices|Best Practices]] for details
:*Y(P) = '''P'''artial (limited) support only - see [[#Best_Practices|Best Practices]] for details
:*No = the feature is not supported at this time - see [[#Best_Practices|Best Practices]] for alternatives, if any.

=== VMware Feature Support for Call Processing and System Management 8.0(2) through 8.6(1) ===

{| border="1"
|+ ''' '''
|-
! Feature
! Unified CM
! CER
! SME
! Unified Attendant Consoles
! UPM
! UOM, USM, USSM
! CIME 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C)
| Y(C) 
| Y(C) 
| Y(C) 
| Yes
| Y(C) 
| Y(C) 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C)
| Y(C)
|  Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(P)
| Y(P)
| No 
| No 
| Y(P)
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No 
| No 
| No
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)  
| Y(P)  
| Y(P)  
| Y(P)  
| Yes
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C)
| No
| Y(C)
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| Y(C) 
| Y(C)
| Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C) 
| Y(C) 
| Y(C) 
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(C)
| Y(C) 
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C) 
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| Y(C)
| No 
| Y(C)
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 5.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! All vSphere ESXi 5.0 Features
| No
| No
| No
| No
| No
| No 
| No
|}

=== VMware Feature Support for Messaging and Presence 8.0(2) through 8.6(1) ===

{| border="1"
|+ '
|-
! Feature
! Unity Connection
! Unity
! Unified Presence
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(PP
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| Y(C)
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| Y(C) 
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(P)
| No
| Y(P)
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| Y(C) 
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
|- align="center"
! [[#Identity|Identity]]
| No  
| No  
| Y(C) 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| 
|}

 

=== VMware Feature Support for Contact Center 8.0(2) through 8.6(1) ===

{| style="width: 906px; height: 823px" border="1"
|+  
|-
! Feature
! Unified CCX
! Cisco WFO, QM, and WFM
! Unified CCE, CVP
! Unified IC
! Cisco MediaSense
! SocialMiner
! Unfied EIM-WIM
! Cisco Finesse
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
|
|
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| Y(C)
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C) 
| Y(C)
| No
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C)
| Y(C) 
| No
| Y(C) 
| No
| No
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P) 
| No
| Y(P) 
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P) 
| Y(P) 
| Y(P) 
| Y(P) 
| No
| No
| No
| No
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| No
| No
| No
| No
| No
| No
| Y(C) 
| No
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| No
| Y(C) 
| Y(C)
| No
| No
| No
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(P) 
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C)
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
|
|
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C)
| No
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No
| No
| No
| 
|}

== Best Practices ==

=== Virtual Machine Templates (OVA files) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

See www.dmtf.org for details on the Open Virtualization Format, which describes an OVF Package (a directory of files describing a virtual machine's configuration) and an OVA Package (single tar file containing an OVF Package).

“Template” in this context refers to an OVA file that defines the virtual server (but not the “workload”, i.e. the UC OS and application). Each virtualized UC product provides a set of predefined virtual machine templates (as OVA files) for supported Virtual Machine (VM) configurations. Customers must download and use these OVA template files for initial install, as they cover items such as supported capacity levels and any required OS/VM/SAN “alignment”. OVAs configured differently than the predefined templates are not supported at this time. To download the OVA files, refer to the [[Unified Communications Virtualization Sizing Guidelines|Unified Communications Virtualization sizing guidelines]].

=== Copy Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Copying a Virtual Machine (VM) copies both the virtual server configuration and the workload (UC OS and application) running on that virtual server to a file on networked shared storage. This allows VMs to be copied, then subsequently modified or shut down. This feature effectively provides a method to do full system backup/restore, take system images or revert changes to software versions, user data and configuration changes.

:*Prior to copying, the VM must first be shutdown (which will shut down the virtual server, the UC OS and the UC application).
:*If uploading a VM copy as a “whole system restore”, clustered UC applications such as CUCM will probably require their replication to be manually “fixed” via a CLI command.

=== Restart Virtual Machine on Different ESXi Host ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

A Virtual Machine (VM) file on network/shared storage can be booted on any physical server hosting ESXi that has access to that network shared storage. With multiple physical ESXi hosts connected to the same network shared storage, this can be used to perform:

:*Fast manual server moves, e.g. moving VM from ESXi host A to ESXi host B in another chassis, closet, building, etc.
:*Fast manual server recovery, e.g. moving VM from ESXi host A that has just had a server hardware or VMware failure to ESXi host B that is healthy. See also VMware High Availability and Site Recovery Manager.
:*Setting up software at a staging location to be later moved or deployed elsewhere. For multi-site scenarios, this may instead require “exporting” the VM.

=== Resize Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Similar to adding/removing physical hardware to/from a physical server, you can add/remove virtual hardware (vCPU, vRAM, vDisk, vNIC, etc.) to/from a Virtual Machine (VM) via a software change in VMware’s configuration interfaces. Where supported, this provides the VM equivalent of migration to a more powerful or less powerful server.

:*Any changes to a VM must align with the best practices in [[#Virtual_Machine_Templates_.28OVA_files.29|Virtual Machine Templates (OVA files)]]. VM changes that result in an unsupported OVA configuration are not allowed. Even if you align with supported OVA configurations, desired VM changes may be prevented by one of the other caveats below.
:*Support for adding virtual hardware resources (similar to moving from a less powerful server to a more powerful server, such as MCS 7825 ⇒ MCS 7845) depends on which resource, and which UC product:
::*Adding vCPU is supported for all apps except Unity and Unity Connection, but requires VM to be shutdown first.
::*Adding vRAM is supported but requires VM to be shutdown first.
::*Adding vDisk is not supported as it would require re-partitioning by the application.
:*Adding vNIC is not supported unless the UC app supports multiple network connections with different IP addresses. See best practices for [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]].
:*For all other changes, it is recommended to backup the application, reinstall application on a new OVA file, and restore the application.
:*Removing virtual hardware resources (vCPU, vRAM, vDisk, etc.) is not supported (similar to moving from a more powerful server to a less powerful server, such as MCS 7845 ⇒ MCS 7825). These migrations require backing up the application, reinstalling on a new OVA file, and and restoring the application.
:*Live runtime resizing via the VMware Hot Add feature is not supported.

=== VMware Hot Add ===

Not supported. See [[#Resize_Virtual_Machine|Resize Virtual Machine instead]].

=== Multiple Physical NICs and vNICs ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). Network traffic is switched from physical NICs to “vNIC’s” of the Virtual Machines (VM) via either VMware vSwitch or Cisco Nexus 1000V. Customers can use these multiple NICs for VM network traffic, VMware console access, or management “back-doors” for administrative access, backups, software updates or other traffic that is desired to be segregated from the VM network traffic. All these uses are supported for UC but note that UC apps like CUCM only support a single vNIC with a single IP address.

=== VMware High Availability (HA) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature automatically restarts a Virtual Machine (VM) on the same physical server or a different physical server. It can be used to supplement software redundancy as a means of fast, automated Failed-server recovery when a VM (but not the application) is hung or if there is a fault with the physical host server or VMware software.

:*Failovers to other servers must not result in an unsupported deployment model (e.g. destination server must align with supported co-residency after failover occurs).
:*Does not protect vs. faults with the SAN or network hardware.

=== VMware Site Recovery Manager (SRM) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature provides an automated disaster recovery solution that works on a “site to site” basis, where a “site” comprises physical servers, VMware and SAN storage. Refer to the VMware documentation for requirements to use this feature. There are no special requirements to use this feature with UC apps that support it.

=== VMware Identity ===

The VMware identity feature allows you to copy an existing instance of a virtual Cisco Unified Presence, and change its identity. The identity of a system is made up of every setting that you usually configure during a fresh install (such as IP address, hostname, passwords).

You can then use this new identity for another instance of a Cisco Unified Presence on a virtual machine. This avoids you having to perform a complete installation each time you deploy a new Cisco Unified Presence.

=== VMware vNetwork Distributed Switch ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Supporting apps in UC on UCS may either use this feature, or the Cisco VN-Link technology (such as Cisco Nexus 1000V).

 

=== VMware vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature migrates a live, running Virtual Machine (VM) from one physical server to another.

The following applies to any use of vMotion with UC apps:

:*VM must be installed on shared storage (SAN).
:*Source and destination physical servers must be connected to same SAN.
:*Destination physical server must not end up with over-subscribed hardware after the migration. Supported capacity and co-residency rules for UC must be followed before and after the migration.
:*VMware “Long Distance vMotion” (site to site) is not supported.
:*The only supported scenario is a manual move to a different server, e.g. for planned maintenance on the server or VMware software, or during troubleshooting to move software off of a physical server having issues.
:*Use of vMotion for real-time load-balancing of live UC VMs is not supported, whether alone or in conjunction with VMware Dynamic Resource Scheduler (DRS) or Dynamic Power Management (DPM).
:*Moving a shut down VM during a maintenance window, i.e. a "cold migration" or "host to host migration", is not vMotion and is supported.

If the UC app is listed as "Supported with Caveats", then support is as described below:

:*Migration of UC VMs that are live and processing live traffic is supported, but note that Cisco testing cannot cover every possible operational scenario. Testing has shown there is a slight risk of calls in progress being impacted for a few seconds as the migration occurs, with worst case result of the affected calls being dropped. If vMotion is suspected as the cause of dropped calls, customers should gather appropriate application logs as well as performance data from VMware vCenter and send to Cisco TAC for analysis.

If the UC app is listed as "Partial" support, then support is “maintenance mode only” as described below:

:*"Maintenance mode only" - VMware vMotion by definition operates on live VMs, but the VM running the UC app must be “live but quiescent”. I.e. in a maintenance window, not in production, not processing live traffic. This is because during the vMotion cutover, the system is paused, which for real-time UC apps creates service interruption which degrade voice quality after the migration for calls in progress.

 

=== VMware Dynamic Resource Scheduler ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== VMware Dynamic Power Management ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== Long Distance vMotion ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported. Long Distance vMotion is a joint Cisco and VMware validated architecture for using the vMotion feature across data centers. For more information, see http://blogs.cisco.com/datacenter/comments/cisco_and_vmware_validated_architecture_for_long_distance_vmotion/ and http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns836/white_paper_c11-557822.pdf.

=== Storage vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This “customer convenience” feature provides easy migration of a live system from one SAN to another SAN. For UC apps, an easier suggested alternative is to just perform manual VM shutdown and migration to the new SAN. However, if Storage vMotion must be used, it is only under the following conditions:

:*Requires SAN storage.
:*May only be done during a maintenance window with UC VMs shut down.

=== VMware vCenter Update Manager (VUM) ===

NOTE: Support varies by application and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature automates patching and updating of VMware vSphere hosts. Note that Cisco Unified Communications applications upgrades, patches and updates can not be delivered through vCenter Update Manager.

=== VMware Consolidated Backup (VCB) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature provides integration with 3rd-party backup utilities so that they can non-disruptively backup the OS and application in a Virtual Machine (VM). See also VMware Data Recovery and Copy Virtual Machine.

Existing UC app methods of backing up the software continue to be supported.

=== VMware Data Recovery ===

Not supported. See [[#VMware_Consolidated_Backup_.28VCB.29|VMware Consolidated Backup]] for what is supported.

=== VMware Snapshots ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

Used to preserve the state of a VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique. See also VMware Data Recovery and Copy Virtual Machine.

=== VMware Fault Tolerance ===

Not supported. See [[#VMware_High_Availability_.28HA.29|VMware High Availability]] for what is supported. Another alternative is manual Virtual Machine shutdown and migration.

=== VMware vCenter Converter ===

P2V tools are not supported. To migrate from bare-metal servers (e.g. Cisco 7800 Series Media Convergence Server) to UC on UCS, the supported procedure is:

:*upgrade to 8.x software version on the bare-metal server
:*take a software backup
:*fresh install 8.x software on VMware / UC on UCS
:*restore from backup

=== VMsafe ===

Not supported. See the documentation for the UC application software or UC appliance software to see what is supported.

=== VMware vShield ===

Not supported. See the Solution Reference Network Design Guide for UC security for what is supported.

=== Virtual Appliance Packaging of UC apps ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party VM-based Backup Tools ===

Not supported. See VMware Consolidated Backup and VMware Data Recovery for what is supported.

=== 3rd-Party VM-based Deployment Tools ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party Physical To Virtual (P2V) Migration Tools ===

Not supported. See VMware vCenter Converter for what is supported.

=== VMware Boot from SAN ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

VMware ESXi 4.1 is required for this feature. Even it works with 4.0, VMware's official support is only for 4.1 and later. Requires use of a "diskless" server - see Supported Hardware for tested reference configurations. Both VMware ESXi and UC apps are installed on, and boot from, the fibre channel SAN. See UCS page at www.cisco.com/go/swonly for storage support policy.

== Services and Support Contracts for VMware are Required ==

Customers deploying virtualized UC must have a valid support contract for the VMware software in order to be supported by Cisco.

Customers purchasing VMware software licenses from Cisco must also purchase a subscription services part number from Cisco (for part number examples, see the UC on UCS page at www.cisco.com/go/swonly).

Customers purchasing VMware software from a 3rd-party must purchase subscription services from that 3rd-party or from VMware.

Customers should note that for VMware vSphere Hypervisor (formerly called “ESXi Single Server Edition” or “free ESXi”), VMware does not offer the same services options and terms as they do for their Standard, Advanced, Enterprise or Enterprise Plus Editions. Customers should take this into account when planning and pricing their support strategy.

Cisco Field and Channel Partners may consult the User Connect Licensing Ordering Guide for more information.

== Cisco TAC Support Expectations ==

The following table describes how TAC support works for VMware in a UC on UCS context, based on who VMware was purchased from.

Special case: when Cisco as a VMware reseller sells VMware Enterprise License Agreements, it is treated as a VMware direct sale for TAC support purposes based on how the maintenance contracts are structured.

 

{| border="1"
|-
! 
! Buy from Cisco as Collaboration SKU
! Buy from Cisco as Data Center SKU
! Buy from 3rd-party, or enterprise/site license
|-
! Available VMware ESXi Editions
| Standard
| Advanced, Enterprise or Enterprise Plus
| Standard, Advanced, Enterprise, Enterprise Plus or vSphere Hypervisor (formerly "Single Server Edition" or "free ESXi"
|-
! Mandatory Support Contracts
| ISV1 from Cisco as Collaboration Service SKU
| ISV1 from Cisco as Data Center Service SKU
| "SnS" subscription from VMware
|-
! Who takes first call?
| Cisco
| Cisco
| VMware
|}

'''TAC Responsibility:''' Note that multi-vendor triage is the norm in virtualized deployments, where the storage, server, hypervisor, OS and application are potentially all from different vendors. Cisco Voice TAC responsibility is the UC application, demarcated at the Virtual Machine. Cisco Server Virtualization TAC responsibility is for VMware (via triage), Cisco UCS, Cisco storage access (or triage with customer and their vendor) and storage array (via triage with customer and their vendor). Escalation to VMware, the customer, or the customer's storage vendors will be done as needed for solution components not produced by Cisco.

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications VMware Requirements

2012-01-05T15:57:40Z

Sdurvasu: 1 revision

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

This article describes VMware requirements, feature support, and services and support contracts for virtualized Unified Communications applications.

== Introduction: Mandatory VMware Products and Services ==

'''Note:''' This page only covers VMware product/version/feature support.

:*It does '''not''' cover compute/network/storage hardware support policy for UC virtualization.
:*It does '''not''' cover application co-residency support policy for UC virtualizatoin.
:*See other links at http://www.cisco.com/go/uc-virtualized for these details.

 

'''VMware vSphere ESXi is mandatory''' for UC virtualization and UC on UCS.

:*UC is only supported on UCS servers with VMware vSphere ESXi.
:*See rest of this page for other details on VMware product, version and feature support.
:*'''Nonvirtualized, physical, or bare-metal installations are not supported''' for UC on UCS.

 

'''VMware vCenter''' is:

:*'''Mandatory''' for all Specs-based deployments
:*'''Optional''' for Tested Reference Configuration deployments.

 

For UC on UCS, VMware vSphere ESXi and vCenter may be purchased from Cisco or customer provided. For specs-based with HP/IBM, all VMware software must be customer-provided. See [[Before You Buy or Deploy - Considerations for Design and Procurement]] for information on VMware purchase options. 

Compatibility of UC apps/versions with VMware vSphere ESXi versions varies by UC app and is outlined later in this document. See the following links for details on "legacy" virtualization support (i.e. 7.x of UC apps with VMware vSphere on limited 3rd-party servers):

:*[http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html Cisco Unity Virtualization Design Guide]
:*[http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_7_5/user/guide/VirtualizationGde753.pdf Virtualization Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted 7.5(3)]

 

'''Note:''' in all cases, the customer is required to have a valid service contract (either with Cisco or with VMware, depending on what/how purchased) to be supported. See [[#Services_and_Support_Contracts_for_VMware_are_Required|Services and Support Contracts for VMware are Required]] for how to ensure this is done for different Editions of Vmware vSphere ESXi. 

== Supported Virtualization Hypervisor Vendors ==

At this time, the only vendor supported for UC is VMware.

Other vendors/products - such as Microsoft Hyper-V, Citrix Xen, Red Hat KVM - are not supported for Cisco UC virtualization. 

== Supported VMware Products ==

VMware vSphere ESXi is required for Cisco UC virtualization.

*ESX and ESXi are architecture options for VMware vSphere ([http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html click here for a comparison]). UC only supports ESXi. Recall that vSphere 3.x and 4.x offered both options, but 5.0+ only offers ESXi.
*VMware vSphere ESX, regardless of version, is not supported for UC. This is due to technical reasons and [http://blogs.vmware.com/vsphere/2010/07/esx-41-is-the-last-esx-what-do-i-do-now.html VMware’s direction to transition from ESX to ESXi]. Note a VMware ESX cluster can contain VMware ESXi servers running Cisco Unified Communications.
*No other VMware server virtualization products are supported.

 

== Supported Versions of VMware vSphere ESXi ==

The minimum version for VMware vSphere ESXi is 4.0. But note a higher minimum version may be required depending on what UC apps/versions you run (see tables below) and what hardware you select.

*Note that use of VMware vSphere ESXi 4.1 requires [[Disable LRO|'''disabling the "LRO" setting as described here''']].
*Versions of VMware vSphere ESXi prior to 4.0 are not supported due to technical reasons.
*Each UC app/version will specify the required compatible Major Releases and Minor Releases of VMware vSphere ESXi (e.g. 4.0 or 4.1) in the tables below.
**Unlisted Major/Minor versions are not supported.
**Unless otherwise indicated, the base Major/Minor version shown is the minimum required.
**Some UC apps will also require a minimum Maintenance Release and will indicate if this is the case. Otherwise UC does not specify or recommend patches, updates or Maintenance Releases (e.g. 4.0 U1) for a required Major/Minor Release of vSphere ESXi. Follow recommendations of the server vendor and VMware for what you should use. Unless otherwise indicated by a UC app, UC supports all VMware vSphere ESXi patches, updates and Maintenance Releases for a supported Major/Minor Release at time of VMware launch as long as the server vendor supports them.

 

=== VMware vSphere ESXi Version Support for Call Processing and System Management Applications ===

{| class="wikitable FCK__ShowTableBorders"
|-
!
Application 

! VMware vSphere ESXi 4.0 
! VMware vSphere ESXi 4.1 
! VMware vSphere ESXi 5.0 
|-
| Unified Communications Manager (Unified CM)
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Cisco Emergency Responder (CER)
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Session Manager Edition (SME)
| 8.5+, 8.6+
| 8.5+, 8.6+
| 8.5+, 8.6+
|-
| Unified Attendant Consoles
| 8.0(3)+, 8.5+
| 8.6+
| Not supported
|-
| UC Management Suite (OM, SM, SSM, PM)
| 7.1 and later
| 7.1 and later
| Not supported
|-
| Cisco Intercompany Media Engine (CIME)
| Not supported
| 8.6(2)+
| 8.6(2)+
|}

=== VMware vSphere ESXi Version Support for Messaging and Presence Applications ===

{| style="width: 812px; height: 108px" class="wikitable FCK__ShowTableBorders"
|-
! Application 
! VMware vSphere ESXi 4.0 
! VMware vSphere ESXi 4.1 
! VMware vSphere ESXi 5.0 
|-
| Cisco Unity Connection
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
|-
| Cisco Unity
| 7.x and later
| 7.x and later
| 7.x and later
|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
| 8.0(2) and later
| 8.0(2) and later
| Not Supported
|}

 

=== VMware vSphere ESXi Version Support for Contact Center Applications ===

{{Note| For Virtual Machines that need '''more than 4 vCPUs''', the VMware vSphere ESXi '''Enterprise Plus''' licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)}}

{| style="width: 816px; height: 396px" class="wikitable FCK__ShowTableBorders"
|-
! Application
! VMware vSphere ESXi 4.0 and 4.0 Updates
! VMware vSphere ESXi 4.1  and 4.1 Updates
! VMware vSphere ESXi 5.0  and 5.0 Updates 
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]]
| 8.0(2)+ or 8.5(1)+
| 8.0(2) SU2+ or 8.5(1)+
| 8.0(2) SU4+ or 8.5(1) SU2+
|-
| [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Work Force Optimization (WFO), Quality Management (QM), and Work Force Management (WFM)]
| 8.5(1)+
| 8.5(2)+
| Not supported
|-
| [[Unified Contact Center Enterprise]] 
| ESXi 4.0 Update 1 (minimum required). See below
| See below
| See below
|-
| - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tools (not supported in 8.5x and later)
| 8.0(2)+ or 8.5(1)+
| 8.0(2)+ or 8.5(1)+
| Not supported
|-
| [[Virtualization for Unified Intelligence Center|Cisco Unified Intelligence Center]] 
| 8.0(3)+
| 8.5(2)+
| Not supported
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]
| 8.0(2)+ or 8.5(1)+
| 8.0(2)+ or 8.5(1)+
| Not supported
|-
| [[Unified Customer Voice Portal]] (all components) 
| 8.0(1)+ or 8.5(1)+
| 8.0(1)+ or 8.5(1)+
| Not supported
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| 8.5(1)+
| 8.5(2)+
| Not supported
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| 8.5(1)+
| 8.5(1)+
| Not supported
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Unified Email Interaction Manager and Web Interaction Manager]]
| 4.3(2)+
| 4.3(2)+
| Not supported
|-
| [[Virtualization_for_Cisco_Finesse|Cisco Finesse]]
| 8.5(3)+
| 8.5(3)+
| Not supported
|}

== Support of Cisco VN-Link and Cisco Nexus 1000V ==

Note that Cisco Unified Contact Center Enterprise does NOT support this – see [[UCS Network Configuration for UCCE|UCS Network Configuration for Unified CCE]].

Unless otherwise indicated above, Cisco VN-Link, Cisco Nexus 1000V, Cisco Nexus 1010, and VM-FEX are supported by UC applications that support the VMware vNetwork Distributed Switch (see [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]).

Cisco VN-Link, Cisco Nexus® 1000V, Cisco Nexus 1010, VM-FEX and VMware vNetwork Distributed Switch all require VMware ESXi Enterprise Plus Edition (see [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]). Other editions do not support these capabilities.

For UC on UCS B-series, Cisco UCS 6100 does not currently support Layer 3 to Layer 2 COS markings. Additionally, the UC applications and operating systems cannot set the Layer 2 COS markings. Use of Cisco Nexus® 1000V is therefore strongly recommended as this is the only way to manage traffic congestion through the current UCS 6100. Please recall that traffic congestion risk will vary and is dependent on many factors such as UC vs. non-UC virtual machine count and their traffic characteristics across all blades, chassis and fabric extenders connected to the same UCS 6100.

For UC on UCS C-series, Cisco Nexus® 1000V is recommended but not mandatory as there is no intermediate UCS 6100 to design around.

For more information on Cisco VN-Link, Cisco Nexus 1000V and VM-FEX, see the following:
:* http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns892/ns894/white_paper_c11-525307.html
:* http://www.cisco.com/en/US/products/ps9902/index.html
:* http://www.cisco.com/en/US/netsol/ns1124/index.html

== Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client ==

 '''VMware vSphere Client''' (formerly branded VI Client) and '''VMware vCenter''' are management consoles for VMware vSphere hosts.

:*vSphere Client is free but only has basic management capabilities.
:*vCenter is not free as it has advanced management capabilities, but note UC may not support every feature in vCenter. vCenter is mandatory for any specs-based deployment.

 

'''VMware vSphere ESXi''' is sold in several '''Editions''' with different levels of feature support.

:*[https://www.vmware.com/products/vsphere/buy/editions_comparison.html Click here for a comparison of VMware vSphere ESXi feature Editions on vmware.com].
::*[http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html Click here for a clarification of “free ESXi 4.1” vs. “vSphere ESXi 4.1 Hypervisor Edition”] (formerly branded as "VMware ESXi Single Server Edition" or “free ESXi”).
::*For details on supported features for 4.x versions of other vSphere ESXi Editions, see your VMware account team. VMware on their web site [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010579 provides a "best effort" comparison here].
:*If buying VMware vSphere ESXi direct from VMware:
::*[http://www.vmware.com/products/vsphere/purchase-advisor/index.html Click here for VMware's Purchase Advisor for vSphere on vmware.com].
::*[https://www.vmware.com/files/pdf/vsphere_pricing.pdf Click here for an overview of VMware vSphere ESXi pricing on vmware.com].

 

There are no UC-specific restrictions on what VMware vSphere ESXi feature Edition you "can" use, but the Edition you "should" use will be determined by VMware licensing rules based on aspects of the UC deployment. The customer is responsible for selecting the correct VMware vSphere ESXi Edition based on their feature and UC application requirements. The following non-exhaustive list is provided for convenience only as examples of what must be considered under VMware's current licensing rules, which are subject to change:

:*If you want to use Cisco Nexus 1000V with UC, that requires the VMware vSphere ESXi feature "Distributed Switch" which is only available in Enterprise Plus Edition.
:*If you want to use a UC virtual machine OVA template with a large quantity of vCPU, verify the VMware vSphere ESXi Edition supports sufficient "vCPU Entitlement" for that OVA's vCPU count.
::*E.g. the Unity Connection 20K user OVA that requires 7 vCPU per VM.
:*Verify all the UC-supported VMware vSphere ESXi features you want to use are [https://www.vmware.com/products/vsphere/buy/editions_comparison.html supported by the Edition you pick].
:*The "Cisco UC Virtualization Hypervisor" is only supported for use with Business Edition 6000 and has the following restrictions:
::*It is not available or transferable for use with any other hardware or software.
::*Server Hardware restricted to UCS C200 M2 TRC#1
::*Max total vRAM across all VMs is 16 GB (of which 14 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Does not support VMware vCenter management. Does not offer any [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features like other Editions].
:*The "Cisco UC Virtualization Foundation" is only supported for use with Business Edition 6000 and UC on UCS.
::*Not available direct from VMware, only sold as part of BE6K or UC on UCS. It is not available or transferable for use with non-UCS hardware or non-UC software.
::*Server Hardware restricted to 2-socket UCS B-Series models and 2-socket UCS C-Series models.
::*Max total vRAM across all VMs is 32 GB (of which 30 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Supports VMware vCenter management (purchased separately). UC-supported [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features] limited to vStorage APIs. All other UC-supported features (including but not limited to VMware High Availability, Data Recovery, vMotion, Distributed Switch, etc.) are not offered.

 

Finally, note that UC may not support all of the features that are included in the VMware vSphere ESXi Edition you pick. This may be because the feature is N/A for a UC deployment, or it has not been sufficiently tested before UC will support, or it requires application enhancements before UC can support.

The table below lists VMware feature support by UC app/version. If the feature is supported, click on its name in the table to view UC caveats and best practices. Feature support may vary by UC app. This site will be updated as new support becomes available.

{{note| feature support for Cisco Unified Contact Center Enterprise varies by component (e.g. Peripheral Gateway) and deployment model (e.g. "Rogger") - this section will give a summary support position, but for individual components see [[Unified Contact Center Enterprise|Support for Virtualization on the ESXi/UCS Platform]].}} 

=== Legend for Feature Support Tables ===

:*Y(C) = Supported with '''C'''aveats - see [[#Best_Practices|Best Practices]] for details
:*Y(P) = '''P'''artial (limited) support only - see [[#Best_Practices|Best Practices]] for details
:*No = the feature is not supported at this time - see [[#Best_Practices|Best Practices]] for alternatives, if any.

=== VMware Feature Support for Call Processing and System Management 8.0(2) through 8.6(1) ===

{| border="1"
|+ ''' '''
|-
! Feature
! Unified CM
! CER
! SME
! Unified Attendant Consoles
! UPM
! UOM, USM, USSM
! CIME 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C)
| Y(C) 
| Y(C) 
| Y(C) 
| Yes
| Y(C) 
| Y(C) 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C)
| Y(C)
|  Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(P)
| Y(P)
| No 
| No 
| Y(P)
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No 
| No 
| No
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)  
| Y(P)  
| Y(P)  
| Y(P)  
| Yes
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C)
| No
| Y(C)
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| Y(C) 
| Y(C)
| Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C) 
| Y(C) 
| Y(C) 
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(C)
| Y(C) 
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C) 
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| Y(C)
| No 
| Y(C)
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 5.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! All vSphere ESXi 5.0 Features
| No
| No
| No
| No
| No
| No 
| No
|}

=== VMware Feature Support for Messaging and Presence 8.0(2) through 8.6(1) ===

{| border="1"
|+ '
|-
! Feature
! Unity Connection
! Unity
! Unified Presence
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(PP
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| Y(C)
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| Y(C) 
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(P)
| No
| Y(P)
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| Y(C) 
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
|- align="center"
! [[#Identity|Identity]]
| No  
| No  
| Y(C) 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| 
|}

 

=== VMware Feature Support for Contact Center 8.0(2) through 8.6(1) ===

{| style="width: 906px; height: 823px" border="1"
|+  
|-
! Feature
! Unified CCX
! Cisco WFO, QM, and WFM
! Unified CCE, CVP
! Unified IC
! Cisco MediaSense
! SocialMiner
! Unfied EIM-WIM
! Cisco Finesse
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
|
|
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| Y(C)
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C) 
| No
| No
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C)
| Y(C) 
| No
| Y(C) 
| No
| No
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P) 
| No
| Y(P) 
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P) 
| Y(P) 
| Y(P) 
| Y(P) 
| No
| No
| No
| No
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| No
| Y(C) 
| Y(C)
| No
| No
| No
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(P) 
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C)
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
|
|
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C)
| No
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No
| No
| No
| 
|}

== Best Practices ==

=== Virtual Machine Templates (OVA files) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

See www.dmtf.org for details on the Open Virtualization Format, which describes an OVF Package (a directory of files describing a virtual machine's configuration) and an OVA Package (single tar file containing an OVF Package).

“Template” in this context refers to an OVA file that defines the virtual server (but not the “workload”, i.e. the UC OS and application). Each virtualized UC product provides a set of predefined virtual machine templates (as OVA files) for supported Virtual Machine (VM) configurations. Customers must download and use these OVA template files for initial install, as they cover items such as supported capacity levels and any required OS/VM/SAN “alignment”. OVAs configured differently than the predefined templates are not supported at this time. To download the OVA files, refer to the [[Unified Communications Virtualization Sizing Guidelines|Unified Communications Virtualization sizing guidelines]].

=== Copy Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Copying a Virtual Machine (VM) copies both the virtual server configuration and the workload (UC OS and application) running on that virtual server to a file on networked shared storage. This allows VMs to be copied, then subsequently modified or shut down. This feature effectively provides a method to do full system backup/restore, take system images or revert changes to software versions, user data and configuration changes.

:*Prior to copying, the VM must first be shutdown (which will shut down the virtual server, the UC OS and the UC application).
:*If uploading a VM copy as a “whole system restore”, clustered UC applications such as CUCM will probably require their replication to be manually “fixed” via a CLI command.

=== Restart Virtual Machine on Different ESXi Host ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

A Virtual Machine (VM) file on network/shared storage can be booted on any physical server hosting ESXi that has access to that network shared storage. With multiple physical ESXi hosts connected to the same network shared storage, this can be used to perform:

:*Fast manual server moves, e.g. moving VM from ESXi host A to ESXi host B in another chassis, closet, building, etc.
:*Fast manual server recovery, e.g. moving VM from ESXi host A that has just had a server hardware or VMware failure to ESXi host B that is healthy. See also VMware High Availability and Site Recovery Manager.
:*Setting up software at a staging location to be later moved or deployed elsewhere. For multi-site scenarios, this may instead require “exporting” the VM.

=== Resize Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Similar to adding/removing physical hardware to/from a physical server, you can add/remove virtual hardware (vCPU, vRAM, vDisk, vNIC, etc.) to/from a Virtual Machine (VM) via a software change in VMware’s configuration interfaces. Where supported, this provides the VM equivalent of migration to a more powerful or less powerful server.

:*Any changes to a VM must align with the best practices in [[#Virtual_Machine_Templates_.28OVA_files.29|Virtual Machine Templates (OVA files)]]. VM changes that result in an unsupported OVA configuration are not allowed. Even if you align with supported OVA configurations, desired VM changes may be prevented by one of the other caveats below.
:*Support for adding virtual hardware resources (similar to moving from a less powerful server to a more powerful server, such as MCS 7825 ⇒ MCS 7845) depends on which resource, and which UC product:
::*Adding vCPU is supported for all apps except Unity and Unity Connection, but requires VM to be shutdown first.
::*Adding vRAM is supported but requires VM to be shutdown first.
::*Adding vDisk is not supported as it would require re-partitioning by the application.
:*Adding vNIC is not supported unless the UC app supports multiple network connections with different IP addresses. See best practices for [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]].
:*For all other changes, it is recommended to backup the application, reinstall application on a new OVA file, and restore the application.
:*Removing virtual hardware resources (vCPU, vRAM, vDisk, etc.) is not supported (similar to moving from a more powerful server to a less powerful server, such as MCS 7845 ⇒ MCS 7825). These migrations require backing up the application, reinstalling on a new OVA file, and and restoring the application.
:*Live runtime resizing via the VMware Hot Add feature is not supported.

=== VMware Hot Add ===

Not supported. See [[#Resize_Virtual_Machine|Resize Virtual Machine instead]].

=== Multiple Physical NICs and vNICs ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). Network traffic is switched from physical NICs to “vNIC’s” of the Virtual Machines (VM) via either VMware vSwitch or Cisco Nexus 1000V. Customers can use these multiple NICs for VM network traffic, VMware console access, or management “back-doors” for administrative access, backups, software updates or other traffic that is desired to be segregated from the VM network traffic. All these uses are supported for UC but note that UC apps like CUCM only support a single vNIC with a single IP address.

=== VMware High Availability (HA) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature automatically restarts a Virtual Machine (VM) on the same physical server or a different physical server. It can be used to supplement software redundancy as a means of fast, automated Failed-server recovery when a VM (but not the application) is hung or if there is a fault with the physical host server or VMware software.

:*Failovers to other servers must not result in an unsupported deployment model (e.g. destination server must align with supported co-residency after failover occurs).
:*Does not protect vs. faults with the SAN or network hardware.

=== VMware Site Recovery Manager (SRM) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature provides an automated disaster recovery solution that works on a “site to site” basis, where a “site” comprises physical servers, VMware and SAN storage. Refer to the VMware documentation for requirements to use this feature. There are no special requirements to use this feature with UC apps that support it.

=== VMware Identity ===

The VMware identity feature allows you to copy an existing instance of a virtual Cisco Unified Presence, and change its identity. The identity of a system is made up of every setting that you usually configure during a fresh install (such as IP address, hostname, passwords).

You can then use this new identity for another instance of a Cisco Unified Presence on a virtual machine. This avoids you having to perform a complete installation each time you deploy a new Cisco Unified Presence.

=== VMware vNetwork Distributed Switch ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Supporting apps in UC on UCS may either use this feature, or the Cisco VN-Link technology (such as Cisco Nexus 1000V).

 

=== VMware vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Cl]]ient.

This feature migrates a live, running Virtual Machine (VM) from one physical server to another.

The following applies to any use of vMotion with UC apps:

:*VM must be installed on shared storage (SAN).
:*Source and destination physical servers must be connected to same SAN.
:*Destination physical server must not end up with over-subscribed hardware after the migration. Supported capacity and co-residency rules for UC must be followed before and after the migration.
:*VMware “Long Distance vMotion” (site to site) is not supported.
:*The only supported scenario is a manual move to a different server, e.g. for planned maintenance on the server or VMware software, or during troubleshooting to move software off of a physical server having issues.
:*Use of vMotion for real-time load-balancing of live UC VMs is not supported, whether alone or in conjunction with VMware Dynamic Resource Scheduler (DRS) or Dynamic Power Management (DPM).
:*Moving a shut down VM during a maintenance window, i.e. a "cold migration" or "host to host migration", is not vMotion and is supported.

If the UC app is listed as "Supported with Caveats", then support is as described below:

:*Migration of UC VMs that are live and processing live traffic is supported, but note that Cisco testing cannot cover every possible operational scenario. Testing has shown there is a slight risk of calls in progress being impacted for a few seconds as the migration occurs, with worst case result of the affected calls being dropped. If vMotion is suspected as the cause of dropped calls, customers should gather appropriate application logs as well as performance data from VMware vCenter and send to Cisco TAC for analysis.

If the UC app is listed as "Partial" support, then support is “maintenance mode only” as described below:

:*"Maintenance mode only" - VMware vMotion by definition operates on live VMs, but the VM running the UC app must be “live but quiescent”. I.e. in a maintenance window, not in production, not processing live traffic. This is because during the vMotion cutover, the system is paused, which for real-time UC apps creates service interruption which degrade voice quality after the migration for calls in progress.

 

=== VMware Dynamic Resource Scheduler ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== VMware Dynamic Power Management ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== Long Distance vMotion ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported. Long Distance vMotion is a joint Cisco and VMware validated architecture for using the vMotion feature across data centers. For more information, see http://blogs.cisco.com/datacenter/comments/cisco_and_vmware_validated_architecture_for_long_distance_vmotion/ and http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns836/white_paper_c11-557822.pdf.

=== Storage vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This “customer convenience” feature provides easy migration of a live system from one SAN to another SAN. For UC apps, an easier suggested alternative is to just perform manual VM shutdown and migration to the new SAN. However, if Storage vMotion must be used, it is only under the following conditions:

:*Requires SAN storage.
:*May only be done during a maintenance window with UC VMs shut down.

=== VMware vCenter Update Manager (VUM) ===

NOTE: Support varies by application and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature automates patching and updating of VMware vSphere hosts. Note that Cisco Unified Communications applications upgrades, patches and updates can not be delivered through vCenter Update Manager.

=== VMware Consolidated Backup (VCB) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature provides integration with 3rd-party backup utilities so that they can non-disruptively backup the OS and application in a Virtual Machine (VM). See also VMware Data Recovery and Copy Virtual Machine.

Existing UC app methods of backing up the software continue to be supported.

=== VMware Data Recovery ===

Not supported. See [[#VMware_Consolidated_Backup_.28VCB.29|VMware Consolidated Backup]] for what is supported.

=== VMware Snapshots ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

Used to preserve the state of a VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique. See also VMware Data Recovery and Copy Virtual Machine.

=== VMware Fault Tolerance ===

Not supported. See [[#VMware_High_Availability_.28HA.29|VMware High Availability]] for what is supported. Another alternative is manual Virtual Machine shutdown and migration.

=== VMware vCenter Converter ===

P2V tools are not supported. To migrate from bare-metal servers (e.g. Cisco 7800 Series Media Convergence Server) to UC on UCS, the supported procedure is:

:*upgrade to 8.x software version on the bare-metal server
:*take a software backup
:*fresh install 8.x software on VMware / UC on UCS
:*restore from backup

=== VMsafe ===

Not supported. See the documentation for the UC application software or UC appliance software to see what is supported.

=== VMware vShield ===

Not supported. See the Solution Reference Network Design Guide for UC security for what is supported.

=== Virtual Appliance Packaging of UC apps ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party VM-based Backup Tools ===

Not supported. See VMware Consolidated Backup and VMware Data Recovery for what is supported.

=== 3rd-Party VM-based Deployment Tools ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party Physical To Virtual (P2V) Migration Tools ===

Not supported. See VMware vCenter Converter for what is supported.

=== VMware Boot from SAN ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

VMware ESXi 4.1 is required for this feature. Even it works with 4.0, VMware's official support is only for 4.1 and later. Requires use of a "diskless" server - see Supported Hardware for tested reference configurations. Both VMware ESXi and UC apps are installed on, and boot from, the fibre channel SAN. See UCS page at www.cisco.com/go/swonly for storage support policy.

== Services and Support Contracts for VMware are Required ==

Customers deploying virtualized UC must have a valid support contract for the VMware software in order to be supported by Cisco.

Customers purchasing VMware software licenses from Cisco must also purchase a subscription services part number from Cisco (for part number examples, see the UC on UCS page at www.cisco.com/go/swonly).

Customers purchasing VMware software from a 3rd-party must purchase subscription services from that 3rd-party or from VMware.

Customers should note that for VMware vSphere Hypervisor (formerly called “ESXi Single Server Edition” or “free ESXi”), VMware does not offer the same services options and terms as they do for their Standard, Advanced, Enterprise or Enterprise Plus Editions. Customers should take this into account when planning and pricing their support strategy.

Cisco Field and Channel Partners may consult the User Connect Licensing Ordering Guide for more information.

== Cisco TAC Support Expectations ==

The following table describes how TAC support works for VMware in a UC on UCS context, based on who VMware was purchased from.

Special case: when Cisco as a VMware reseller sells VMware Enterprise License Agreements, it is treated as a VMware direct sale for TAC support purposes based on how the maintenance contracts are structured.

 

{| border="1"
|-
! 
! Buy from Cisco as Collaboration SKU
! Buy from Cisco as Data Center SKU
! Buy from 3rd-party, or enterprise/site license
|-
! Available VMware ESXi Editions
| Standard
| Advanced, Enterprise or Enterprise Plus
| Standard, Advanced, Enterprise, Enterprise Plus or vSphere Hypervisor (formerly "Single Server Edition" or "free ESXi"
|-
! Mandatory Support Contracts
| ISV1 from Cisco as Collaboration Service SKU
| ISV1 from Cisco as Data Center Service SKU
| "SnS" subscription from VMware
|-
! Who takes first call?
| Cisco
| Cisco
| VMware
|}

'''TAC Responsibility:''' Note that multi-vendor triage is the norm in virtualized deployments, where the storage, server, hypervisor, OS and application are potentially all from different vendors. Cisco Voice TAC responsibility is the UC application, demarcated at the Virtual Machine. Cisco Server Virtualization TAC responsibility is for VMware (via triage), Cisco UCS, Cisco storage access (or triage with customer and their vendor) and storage array (via triage with customer and their vendor). Escalation to VMware, the customer, or the customer's storage vendors will be done as needed for solution components not produced by Cisco.

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications VMware Requirements

2012-01-04T16:23:27Z

Sdurvasu: 1 revision

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

This article describes VMware requirements, feature support, and services and support contracts for virtualized Unified Communications applications.

== Introduction: Mandatory VMware Products and Services ==

'''Note:''' This page only covers VMware product/version/feature support.

:*It does '''not''' cover compute/network/storage hardware support policy for UC virtualization.
:*It does '''not''' cover application co-residency support policy for UC virtualizatoin.
:*See other links at http://www.cisco.com/go/uc-virtualized for these details.

 

'''VMware vSphere ESXi is mandatory''' for UC virtualization and UC on UCS.

:*UC is only supported on UCS servers with VMware vSphere ESXi.
:*See rest of this page for other details on VMware product, version and feature support.
:*'''Nonvirtualized, physical, or bare-metal installations are not supported''' for UC on UCS.

 

'''VMware vCenter''' is:

:*'''Mandatory''' for all Specs-based deployments
:*'''Optional''' for Tested Reference Configuration deployments.

 

For UC on UCS, VMware vSphere ESXi and vCenter may be purchased from Cisco or customer provided. For specs-based with HP/IBM, all VMware software must be customer-provided. See [[Before You Buy or Deploy - Considerations for Design and Procurement]] for information on VMware purchase options. 

Compatibility of UC apps/versions with VMware vSphere ESXi versions varies by UC app and is outlined later in this document. See the following links for details on "legacy" virtualization support (i.e. 7.x of UC apps with VMware vSphere on limited 3rd-party servers):

:*[http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html Cisco Unity Virtualization Design Guide]
:*[http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_7_5/user/guide/VirtualizationGde753.pdf Virtualization Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted 7.5(3)]

 

'''Note:''' in all cases, the customer is required to have a valid service contract (either with Cisco or with VMware, depending on what/how purchased) to be supported. See [[#Services_and_Support_Contracts_for_VMware_are_Required|Services and Support Contracts for VMware are Required]] for how to ensure this is done for different Editions of Vmware vSphere ESXi. 

== Supported Virtualization Hypervisor Vendors ==

At this time, the only vendor supported for UC is VMware.

Other vendors/products - such as Microsoft Hyper-V, Citrix Xen, Red Hat KVM - are not supported for Cisco UC virtualization. 

== Supported VMware Products ==

VMware vSphere ESXi is required for Cisco UC virtualization.

*ESX and ESXi are architecture options for VMware vSphere ([http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html click here for a comparison]). UC only supports ESXi. Recall that vSphere 3.x and 4.x offered both options, but 5.0+ only offers ESXi.
*VMware vSphere ESX, regardless of version, is not supported for UC. This is due to technical reasons and [http://blogs.vmware.com/vsphere/2010/07/esx-41-is-the-last-esx-what-do-i-do-now.html VMware’s direction to transition from ESX to ESXi]. Note a VMware ESX cluster can contain VMware ESXi servers running Cisco Unified Communications.
*No other VMware server virtualization products are supported.

 

== Supported Versions of VMware vSphere ESXi ==

The minimum version for VMware vSphere ESXi is 4.0. But note a higher minimum version may be required depending on what UC apps/versions you run (see tables below) and what hardware you select.

*Note that use of VMware vSphere ESXi 4.1 requires [[Disable LRO|'''disabling the "LRO" setting as described here''']].
*Versions of VMware vSphere ESXi prior to 4.0 are not supported due to technical reasons.
*Each UC app/version will specify the required compatible Major Releases and Minor Releases of VMware vSphere ESXi (e.g. 4.0 or 4.1) in the tables below.
**Unlisted Major/Minor versions are not supported.
**Unless otherwise indicated, the base Major/Minor version shown is the minimum required.
**Some UC apps will also require a minimum Maintenance Release and will indicate if this is the case. Otherwise UC does not specify or recommend patches, updates or Maintenance Releases (e.g. 4.0 U1) for a required Major/Minor Release of vSphere ESXi. Follow recommendations of the server vendor and VMware for what you should use. Unless otherwise indicated by a UC app, UC supports all VMware vSphere ESXi patches, updates and Maintenance Releases for a supported Major/Minor Release at time of VMware launch as long as the server vendor supports them.

 

=== VMware vSphere ESXi Version Support for Call Processing and System Management Applications ===

{| class="wikitable FCK__ShowTableBorders"
|-
!
Application 

! VMware vSphere ESXi 4.0 
! VMware vSphere ESXi 4.1 
! VMware vSphere ESXi 5.0 
|-
| Unified Communications Manager (Unified CM)
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Cisco Emergency Responder (CER)
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Session Manager Edition (SME)
| 8.5+, 8.6+
| 8.5+, 8.6+
| 8.5+, 8.6+
|-
| Unified Attendant Consoles
| 8.0(3)+, 8.5+
| 8.6+
| Not supported
|-
| UC Management Suite (OM, SM, SSM, PM)
| 7.1 and later
| 7.1 and later
| Not supported
|-
| Cisco Intercompany Media Engine (CIME)
| Not supported
| 8.6(2)+
| 8.6(2)+
|}

=== VMware vSphere ESXi Version Support for Messaging and Presence Applications ===

{| style="width: 812px; height: 108px" class="wikitable FCK__ShowTableBorders"
|-
! Application 
! VMware vSphere ESXi 4.0 
! VMware vSphere ESXi 4.1 
! VMware vSphere ESXi 5.0 
|-
| Cisco Unity Connection
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
|-
| Cisco Unity
| 7.x and later
| 7.x and later
| 7.x and later
|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
| 8.0(2) and later
| 8.0(2) and later
| Not Supported
|
|}

 

=== VMware vSphere ESXi Version Support for Contact Center Applications ===

{{Note| For Virtual Machines that need '''more than 4 vCPUs''', the VMware vSphere ESXi '''Enterprise Plus''' licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)}}

{| style="width: 816px; height: 396px" class="wikitable FCK__ShowTableBorders"
|-
! Application
! VMware vSphere ESXi 4.0 and 4.0 Updates
! VMware vSphere ESXi 4.1  and 4.1 Updates
! VMware vSphere ESXi 5.0  and 5.0 Updates 
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]]
| 8.0(2)+ or 8.5(1)+
| 8.0(2) SU2+ or 8.5(1)+
| 8.0(2) SU4+ or 8.5(1) SU2+
|-
| [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Work Force Optimization (WFO), Quality Management (QM), and Work Force Management (WFM)]
| 8.5(1)+
| 8.5(2)+
| Not supported
|-
| [[Unified Contact Center Enterprise]] 
| ESXi 4.0 Update 1 (minimum required). See below
| See below
| See below
|-
| - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tools (not supported in 8.5x and later)
| 8.0(2)+ or 8.5(1)+
| 8.0(2)+ or 8.5(1)+
| Not supported
|-
| [[Virtualization for Unified Intelligence Center|Cisco Unified Intelligence Center]] 
| 8.0(3)+
| 8.5(2)+
| Not supported
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]
| 8.0(2)+ or 8.5(1)+
| 8.0(2)+ or 8.5(1)+
| Not supported
|-
| [[Unified Customer Voice Portal]] (all components) 
| 8.0(1)+ or 8.5(1)+
| 8.0(1)+ or 8.5(1)+
| Not supported
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| 8.5(1)+
| 8.5(2)+
| Not supported
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| 8.5(1)+
| 8.5(1)+
| Not supported
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Unified Email Interaction Manager and Web Interaction Manager]]
| 4.3(2)+
| 4.3(2)+
| Not supported
|-
| [[Virtualization_for_Cisco_Finesse|Cisco Finesse]]
| 8.5(3)+
| 8.5(3)+
| Not supported
|}

== Support of Cisco VN-Link and Cisco Nexus 1000V ==

Note that Cisco Unified Contact Center Enterprise does NOT support this – see [[UCS Network Configuration for UCCE|UCS Network Configuration for Unified CCE]].

Unless otherwise indicated above, Cisco VN-Link, Cisco Nexus 1000V, Cisco Nexus 1010, and VM-FEX are supported by UC applications that support the VMware vNetwork Distributed Switch (see [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]).

Cisco VN-Link, Cisco Nexus® 1000V, Cisco Nexus 1010, VM-FEX and VMware vNetwork Distributed Switch all require VMware ESXi Enterprise Plus Edition (see [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]). Other editions do not support these capabilities.

For UC on UCS B-series, Cisco UCS 6100 does not currently support Layer 3 to Layer 2 COS markings. Additionally, the UC applications and operating systems cannot set the Layer 2 COS markings. Use of Cisco Nexus® 1000V is therefore strongly recommended as this is the only way to manage traffic congestion through the current UCS 6100. Please recall that traffic congestion risk will vary and is dependent on many factors such as UC vs. non-UC virtual machine count and their traffic characteristics across all blades, chassis and fabric extenders connected to the same UCS 6100.

For UC on UCS C-series, Cisco Nexus® 1000V is recommended but not mandatory as there is no intermediate UCS 6100 to design around.

For more information on Cisco VN-Link, Cisco Nexus 1000V and VM-FEX, see the following:
:* http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns892/ns894/white_paper_c11-525307.html
:* http://www.cisco.com/en/US/products/ps9902/index.html
:* http://www.cisco.com/en/US/netsol/ns1124/index.html

== Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client ==

 '''VMware vSphere Client''' (formerly branded VI Client) and '''VMware vCenter''' are management consoles for VMware vSphere hosts.

:*vSphere Client is free but only has basic management capabilities.
:*vCenter is not free as it has advanced management capabilities, but note UC may not support every feature in vCenter. vCenter is mandatory for any specs-based deployment.

 

'''VMware vSphere ESXi''' is sold in several '''Editions''' with different levels of feature support.

:*[https://www.vmware.com/products/vsphere/buy/editions_comparison.html Click here for a comparison of VMware vSphere ESXi feature Editions on vmware.com].
::*[http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html Click here for a clarification of “free ESXi 4.1” vs. “vSphere ESXi 4.1 Hypervisor Edition”] (formerly branded as "VMware ESXi Single Server Edition" or “free ESXi”).
::*For details on supported features for 4.x versions of other vSphere ESXi Editions, see your VMware account team. VMware on their web site [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010579 provides a "best effort" comparison here].
:*If buying VMware vSphere ESXi direct from VMware:
::*[http://www.vmware.com/products/vsphere/purchase-advisor/index.html Click here for VMware's Purchase Advisor for vSphere on vmware.com].
::*[https://www.vmware.com/files/pdf/vsphere_pricing.pdf Click here for an overview of VMware vSphere ESXi pricing on vmware.com].

 

There are no UC-specific restrictions on what VMware vSphere ESXi feature Edition you "can" use, but the Edition you "should" use will be determined by VMware licensing rules based on aspects of the UC deployment. The customer is responsible for selecting the correct VMware vSphere ESXi Edition based on their feature and UC application requirements. The following non-exhaustive list is provided for convenience only as examples of what must be considered under VMware's current licensing rules, which are subject to change:

:*If you want to use Cisco Nexus 1000V with UC, that requires the VMware vSphere ESXi feature "Distributed Switch" which is only available in Enterprise Plus Edition.
:*If you want to use a UC virtual machine OVA template with a large quantity of vCPU, verify the VMware vSphere ESXi Edition supports sufficient "vCPU Entitlement" for that OVA's vCPU count.
::*E.g. the Unity Connection 20K user OVA that requires 7 vCPU per VM.
:*Verify all the UC-supported VMware vSphere ESXi features you want to use are [https://www.vmware.com/products/vsphere/buy/editions_comparison.html supported by the Edition you pick].
:*The "Cisco UC Virtualization Hypervisor" is only supported for use with Business Edition 6000 and has the following restrictions:
::*It is not available or transferable for use with any other hardware or software.
::*Server Hardware restricted to UCS C200 M2 TRC#1
::*Max total vRAM across all VMs is 16 GB (of which 14 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Does not support VMware vCenter management. Does not offer any [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features like other Editions].
:*The "Cisco UC Virtualization Foundation" is only supported for use with Business Edition 6000 and UC on UCS.
::*Not available direct from VMware, only sold as part of BE6K or UC on UCS. It is not available or transferable for use with non-UCS hardware or non-UC software.
::*Server Hardware restricted to 2-socket UCS B-Series models and 2-socket UCS C-Series models.
::*Max total vRAM across all VMs is 32 GB (of which 30 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Supports VMware vCenter management (purchased separately). UC-supported [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features] limited to vStorage APIs. All other UC-supported features (including but not limited to VMware High Availability, Data Recovery, vMotion, Distributed Switch, etc.) are not offered.

 

Finally, note that UC may not support all of the features that are included in the VMware vSphere ESXi Edition you pick. This may be because the feature is N/A for a UC deployment, or it has not been sufficiently tested before UC will support, or it requires application enhancements before UC can support.

The table below lists VMware feature support by UC app/version. If the feature is supported, click on its name in the table to view UC caveats and best practices. Feature support may vary by UC app. This site will be updated as new support becomes available.

{{note| feature support for Cisco Unified Contact Center Enterprise varies by component (e.g. Peripheral Gateway) and deployment model (e.g. "Rogger") - this section will give a summary support position, but for individual components see [[Unified Contact Center Enterprise|Support for Virtualization on the ESXi/UCS Platform]].}} 

=== Legend for Feature Support Tables ===

:*Y(C) = Supported with '''C'''aveats - see [[#Best_Practices|Best Practices]] for details
:*Y(P) = '''P'''artial (limited) support only - see [[#Best_Practices|Best Practices]] for details
:*No = the feature is not supported at this time - see [[#Best_Practices|Best Practices]] for alternatives, if any.

=== VMware Feature Support for Call Processing and System Management 8.0(2) through 8.6(1) ===

{| border="1"
|+ ''' '''
|-
! Feature
! Unified CM
! CER
! SME
! Unified Attendant Consoles
! UPM
! UOM, USM, USSM
! CIME 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C)
| Y(C) 
| Y(C) 
| Y(C) 
| Yes
| Y(C) 
| Y(C) 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C)
| Y(C)
|  Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(P)
| Y(P)
| No 
| No 
| Y(P)
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No 
| No 
| No
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)  
| Y(P)  
| Y(P)  
| Y(P)  
| Yes
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C)
| No
| Y(C)
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| Y(C) 
| Y(C)
| Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C) 
| Y(C) 
| Y(C) 
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(C)
| Y(C) 
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C) 
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| Y(C)
| No 
| Y(C)
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 5.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! All vSphere ESXi 5.0 Features
| No
| No
| No
| No
| No
| No 
| No
|}

=== VMware Feature Support for Messaging and Presence 8.0(2) through 8.6(1) ===

{| border="1"
|+ '
|-
! Feature
! Unity Connection
! Unity
! Unified Presence
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(PP
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| Y(C)
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| Y(C) 
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(P)
| No
| Y(P)
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| Y(C) 
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
|- align="center"
! [[#Identity|Identity]]
| No  
| No  
| Y(C) 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| 
|}

 

=== VMware Feature Support for Contact Center 8.0(2) through 8.6(1) ===

{| style="width: 906px; height: 823px" border="1"
|+  
|-
! Feature
! Unified CCX
! Cisco WFO, QM, and WFM
! Unified CCE, CVP
! Unified IC
! Cisco MediaSense
! SocialMiner
! Unfied EIM-WIM
! Cisco Finesse
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
|
|
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| Y(C)
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C) 
| No
| No
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C)
| Y(C) 
| No
| Y(C) 
| No
| No
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P) 
| No
| Y(P) 
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P) 
| Y(P) 
| Y(P) 
| Y(P) 
| No
| No
| No
| No
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| No
| Y(C) 
| Y(C)
| No
| No
| No
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(P) 
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C)
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
|
|
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C)
| No
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No
| No
| No
| 
|}

== Best Practices ==

=== Virtual Machine Templates (OVA files) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

See www.dmtf.org for details on the Open Virtualization Format, which describes an OVF Package (a directory of files describing a virtual machine's configuration) and an OVA Package (single tar file containing an OVF Package).

“Template” in this context refers to an OVA file that defines the virtual server (but not the “workload”, i.e. the UC OS and application). Each virtualized UC product provides a set of predefined virtual machine templates (as OVA files) for supported Virtual Machine (VM) configurations. Customers must download and use these OVA template files for initial install, as they cover items such as supported capacity levels and any required OS/VM/SAN “alignment”. OVAs configured differently than the predefined templates are not supported at this time. To download the OVA files, refer to the [[Unified Communications Virtualization Sizing Guidelines|Unified Communications Virtualization sizing guidelines]].

=== Copy Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Copying a Virtual Machine (VM) copies both the virtual server configuration and the workload (UC OS and application) running on that virtual server to a file on networked shared storage. This allows VMs to be copied, then subsequently modified or shut down. This feature effectively provides a method to do full system backup/restore, take system images or revert changes to software versions, user data and configuration changes.

:*Prior to copying, the VM must first be shutdown (which will shut down the virtual server, the UC OS and the UC application).
:*If uploading a VM copy as a “whole system restore”, clustered UC applications such as CUCM will probably require their replication to be manually “fixed” via a CLI command.

=== Restart Virtual Machine on Different ESXi Host ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

A Virtual Machine (VM) file on network/shared storage can be booted on any physical server hosting ESXi that has access to that network shared storage. With multiple physical ESXi hosts connected to the same network shared storage, this can be used to perform:

:*Fast manual server moves, e.g. moving VM from ESXi host A to ESXi host B in another chassis, closet, building, etc.
:*Fast manual server recovery, e.g. moving VM from ESXi host A that has just had a server hardware or VMware failure to ESXi host B that is healthy. See also VMware High Availability and Site Recovery Manager.
:*Setting up software at a staging location to be later moved or deployed elsewhere. For multi-site scenarios, this may instead require “exporting” the VM.

=== Resize Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Similar to adding/removing physical hardware to/from a physical server, you can add/remove virtual hardware (vCPU, vRAM, vDisk, vNIC, etc.) to/from a Virtual Machine (VM) via a software change in VMware’s configuration interfaces. Where supported, this provides the VM equivalent of migration to a more powerful or less powerful server.

:*Any changes to a VM must align with the best practices in [[#Virtual_Machine_Templates_.28OVA_files.29|Virtual Machine Templates (OVA files)]]. VM changes that result in an unsupported OVA configuration are not allowed. Even if you align with supported OVA configurations, desired VM changes may be prevented by one of the other caveats below.
:*Support for adding virtual hardware resources (similar to moving from a less powerful server to a more powerful server, such as MCS 7825 ⇒ MCS 7845) depends on which resource, and which UC product:
::*Adding vCPU is supported for all apps except Unity and Unity Connection, but requires VM to be shutdown first.
::*Adding vRAM is supported but requires VM to be shutdown first.
::*Adding vDisk is not supported as it would require re-partitioning by the application.
:*Adding vNIC is not supported unless the UC app supports multiple network connections with different IP addresses. See best practices for [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]].
:*For all other changes, it is recommended to backup the application, reinstall application on a new OVA file, and restore the application.
:*Removing virtual hardware resources (vCPU, vRAM, vDisk, etc.) is not supported (similar to moving from a more powerful server to a less powerful server, such as MCS 7845 ⇒ MCS 7825). These migrations require backing up the application, reinstalling on a new OVA file, and and restoring the application.
:*Live runtime resizing via the VMware Hot Add feature is not supported.

=== VMware Hot Add ===

Not supported. See [[#Resize_Virtual_Machine|Resize Virtual Machine instead]].

=== Multiple Physical NICs and vNICs ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). Network traffic is switched from physical NICs to “vNIC’s” of the Virtual Machines (VM) via either VMware vSwitch or Cisco Nexus 1000V. Customers can use these multiple NICs for VM network traffic, VMware console access, or management “back-doors” for administrative access, backups, software updates or other traffic that is desired to be segregated from the VM network traffic. All these uses are supported for UC but note that UC apps like CUCM only support a single vNIC with a single IP address.

=== VMware High Availability (HA) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature automatically restarts a Virtual Machine (VM) on the same physical server or a different physical server. It can be used to supplement software redundancy as a means of fast, automated Failed-server recovery when a VM (but not the application) is hung or if there is a fault with the physical host server or VMware software.

:*Failovers to other servers must not result in an unsupported deployment model (e.g. destination server must align with supported co-residency after failover occurs).
:*Does not protect vs. faults with the SAN or network hardware.

=== VMware Site Recovery Manager (SRM) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature provides an automated disaster recovery solution that works on a “site to site” basis, where a “site” comprises physical servers, VMware and SAN storage. Refer to the VMware documentation for requirements to use this feature. There are no special requirements to use this feature with UC apps that support it.

=== VMware Identity ===

The VMware identity feature allows you to copy an existing instance of a virtual Cisco Unified Presence, and change its identity. The identity of a system is made up of every setting that you usually configure during a fresh install (such as IP address, hostname, passwords).

You can then use this new identity for another instance of a Cisco Unified Presence on a virtual machine. This avoids you having to perform a complete installation each time you deploy a new Cisco Unified Presence.

=== VMware vNetwork Distributed Switch ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Supporting apps in UC on UCS may either use this feature, or the Cisco VN-Link technology (such as Cisco Nexus 1000V).

 

=== VMware vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Cl]]ient.

This feature migrates a live, running Virtual Machine (VM) from one physical server to another.

The following applies to any use of vMotion with UC apps:

:*VM must be installed on shared storage (SAN).
:*Source and destination physical servers must be connected to same SAN.
:*Destination physical server must not end up with over-subscribed hardware after the migration. Supported capacity and co-residency rules for UC must be followed before and after the migration.
:*VMware “Long Distance vMotion” (site to site) is not supported.
:*The only supported scenario is a manual move to a different server, e.g. for planned maintenance on the server or VMware software, or during troubleshooting to move software off of a physical server having issues.
:*Use of vMotion for real-time load-balancing of live UC VMs is not supported, whether alone or in conjunction with VMware Dynamic Resource Scheduler (DRS) or Dynamic Power Management (DPM).
:*Moving a shut down VM during a maintenance window, i.e. a "cold migration" or "host to host migration", is not vMotion and is supported.

If the UC app is listed as "Supported with Caveats", then support is as described below:

:*Migration of UC VMs that are live and processing live traffic is supported, but note that Cisco testing cannot cover every possible operational scenario. Testing has shown there is a slight risk of calls in progress being impacted for a few seconds as the migration occurs, with worst case result of the affected calls being dropped. If vMotion is suspected as the cause of dropped calls, customers should gather appropriate application logs as well as performance data from VMware vCenter and send to Cisco TAC for analysis.

If the UC app is listed as "Partial" support, then support is “maintenance mode only” as described below:

:*"Maintenance mode only" - VMware vMotion by definition operates on live VMs, but the VM running the UC app must be “live but quiescent”. I.e. in a maintenance window, not in production, not processing live traffic. This is because during the vMotion cutover, the system is paused, which for real-time UC apps creates service interruption which degrade voice quality after the migration for calls in progress.

 

=== VMware Dynamic Resource Scheduler ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== VMware Dynamic Power Management ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== Long Distance vMotion ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported. Long Distance vMotion is a joint Cisco and VMware validated architecture for using the vMotion feature across data centers. For more information, see http://blogs.cisco.com/datacenter/comments/cisco_and_vmware_validated_architecture_for_long_distance_vmotion/ and http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns836/white_paper_c11-557822.pdf.

=== Storage vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This “customer convenience” feature provides easy migration of a live system from one SAN to another SAN. For UC apps, an easier suggested alternative is to just perform manual VM shutdown and migration to the new SAN. However, if Storage vMotion must be used, it is only under the following conditions:

:*Requires SAN storage.
:*May only be done during a maintenance window with UC VMs shut down.

=== VMware vCenter Update Manager (VUM) ===

NOTE: Support varies by application and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature automates patching and updating of VMware vSphere hosts. Note that Cisco Unified Communications applications upgrades, patches and updates can not be delivered through vCenter Update Manager.

=== VMware Consolidated Backup (VCB) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature provides integration with 3rd-party backup utilities so that they can non-disruptively backup the OS and application in a Virtual Machine (VM). See also VMware Data Recovery and Copy Virtual Machine.

Existing UC app methods of backing up the software continue to be supported.

=== VMware Data Recovery ===

Not supported. See [[#VMware_Consolidated_Backup_.28VCB.29|VMware Consolidated Backup]] for what is supported.

=== VMware Snapshots ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

Used to preserve the state of a VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique. See also VMware Data Recovery and Copy Virtual Machine.

=== VMware Fault Tolerance ===

Not supported. See [[#VMware_High_Availability_.28HA.29|VMware High Availability]] for what is supported. Another alternative is manual Virtual Machine shutdown and migration.

=== VMware vCenter Converter ===

P2V tools are not supported. To migrate from bare-metal servers (e.g. Cisco 7800 Series Media Convergence Server) to UC on UCS, the supported procedure is:

:*upgrade to 8.x software version on the bare-metal server
:*take a software backup
:*fresh install 8.x software on VMware / UC on UCS
:*restore from backup

=== VMsafe ===

Not supported. See the documentation for the UC application software or UC appliance software to see what is supported.

=== VMware vShield ===

Not supported. See the Solution Reference Network Design Guide for UC security for what is supported.

=== Virtual Appliance Packaging of UC apps ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party VM-based Backup Tools ===

Not supported. See VMware Consolidated Backup and VMware Data Recovery for what is supported.

=== 3rd-Party VM-based Deployment Tools ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party Physical To Virtual (P2V) Migration Tools ===

Not supported. See VMware vCenter Converter for what is supported.

=== VMware Boot from SAN ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

VMware ESXi 4.1 is required for this feature. Even it works with 4.0, VMware's official support is only for 4.1 and later. Requires use of a "diskless" server - see Supported Hardware for tested reference configurations. Both VMware ESXi and UC apps are installed on, and boot from, the fibre channel SAN. See UCS page at www.cisco.com/go/swonly for storage support policy.

== Services and Support Contracts for VMware are Required ==

Customers deploying virtualized UC must have a valid support contract for the VMware software in order to be supported by Cisco.

Customers purchasing VMware software licenses from Cisco must also purchase a subscription services part number from Cisco (for part number examples, see the UC on UCS page at www.cisco.com/go/swonly).

Customers purchasing VMware software from a 3rd-party must purchase subscription services from that 3rd-party or from VMware.

Customers should note that for VMware vSphere Hypervisor (formerly called “ESXi Single Server Edition” or “free ESXi”), VMware does not offer the same services options and terms as they do for their Standard, Advanced, Enterprise or Enterprise Plus Editions. Customers should take this into account when planning and pricing their support strategy.

Cisco Field and Channel Partners may consult the User Connect Licensing Ordering Guide for more information.

== Cisco TAC Support Expectations ==

The following table describes how TAC support works for VMware in a UC on UCS context, based on who VMware was purchased from.

Special case: when Cisco as a VMware reseller sells VMware Enterprise License Agreements, it is treated as a VMware direct sale for TAC support purposes based on how the maintenance contracts are structured.

 

{| border="1"
|-
! 
! Buy from Cisco as Collaboration SKU
! Buy from Cisco as Data Center SKU
! Buy from 3rd-party, or enterprise/site license
|-
! Available VMware ESXi Editions
| Standard
| Advanced, Enterprise or Enterprise Plus
| Standard, Advanced, Enterprise, Enterprise Plus or vSphere Hypervisor (formerly "Single Server Edition" or "free ESXi"
|-
! Mandatory Support Contracts
| ISV1 from Cisco as Collaboration Service SKU
| ISV1 from Cisco as Data Center Service SKU
| "SnS" subscription from VMware
|-
! Who takes first call?
| Cisco
| Cisco
| VMware
|}

'''TAC Responsibility:''' Note that multi-vendor triage is the norm in virtualized deployments, where the storage, server, hypervisor, OS and application are potentially all from different vendors. Cisco Voice TAC responsibility is the UC application, demarcated at the Virtual Machine. Cisco Server Virtualization TAC responsibility is for VMware (via triage), Cisco UCS, Cisco storage access (or triage with customer and their vendor) and storage array (via triage with customer and their vendor). Escalation to VMware, the customer, or the customer's storage vendors will be done as needed for solution components not produced by Cisco.

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications VMware Requirements

2011-12-22T21:14:32Z

Sdurvasu: 1 revision

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

This article describes VMware requirements, feature support, and services and support contracts for virtualized Unified Communications applications.

== Introduction: Mandatory VMware Products and Services ==

'''Note:''' This page only covers VMware product/version/feature support.

:*It does '''not''' cover compute/network/storage hardware support policy for UC virtualization.
:*It does '''not''' cover application co-residency support policy for UC virtualizatoin.
:*See other links at http://www.cisco.com/go/uc-virtualized for these details.

 

'''VMware vSphere ESXi is mandatory''' for UC virtualization and UC on UCS.

:*UC is only supported on UCS servers with VMware vSphere ESXi.
:*See rest of this page for other details on VMware product, version and feature support.
:*'''Nonvirtualized, physical, or bare-metal installations are not supported''' for UC on UCS.

 

'''VMware vCenter''' is:

:*'''Mandatory''' for all Specs-based deployments
:*'''Optional''' for Tested Reference Configuration deployments.

 

For UC on UCS, VMware vSphere ESXi and vCenter may be purchased from Cisco or customer provided. For specs-based with HP/IBM, all VMware software must be customer-provided. See [[Before You Buy or Deploy - Considerations for Design and Procurement]] for information on VMware purchase options. 

Compatibility of UC apps/versions with VMware vSphere ESXi versions varies by UC app and is outlined later in this document. See the following links for details on "legacy" virtualization support (i.e. 7.x of UC apps with VMware vSphere on limited 3rd-party servers):

:*[http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html Cisco Unity Virtualization Design Guide]
:*[http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_7_5/user/guide/VirtualizationGde753.pdf Virtualization Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted 7.5(3)]

 

'''Note:''' in all cases, the customer is required to have a valid service contract (either with Cisco or with VMware, depending on what/how purchased) to be supported. See [[#Services_and_Support_Contracts_for_VMware_are_Required|Services and Support Contracts for VMware are Required]] for how to ensure this is done for different Editions of Vmware vSphere ESXi. 

== Supported Virtualization Hypervisor Vendors ==

At this time, the only vendor supported for UC is VMware.

Other vendors/products - such as Microsoft Hyper-V, Citrix Xen, Red Hat KVM - are not supported for Cisco UC virtualization. 

== Supported VMware Products ==

VMware vSphere ESXi is required for Cisco UC virtualization.

*ESX and ESXi are architecture options for VMware vSphere ([http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html click here for a comparison]). UC only supports ESXi. Recall that vSphere 3.x and 4.x offered both options, but 5.0+ only offers ESXi.
*VMware vSphere ESX, regardless of version, is not supported for UC. This is due to technical reasons and [http://blogs.vmware.com/vsphere/2010/07/esx-41-is-the-last-esx-what-do-i-do-now.html VMware’s direction to transition from ESX to ESXi]. Note a VMware ESX cluster can contain VMware ESXi servers running Cisco Unified Communications.
*No other VMware server virtualization products are supported.

 

== Supported Versions of VMware vSphere ESXi ==

The minimum version for VMware vSphere ESXi is 4.0. But note a higher minimum version may be required depending on what UC apps/versions you run (see tables below) and what hardware you select.

*Note that use of VMware vSphere ESXi 4.1 requires [[Disable LRO|'''disabling the "LRO" setting as described here''']].
*Versions of VMware vSphere ESXi prior to 4.0 are not supported due to technical reasons.
*Each UC app/version will specify the required compatible Major Releases and Minor Releases of VMware vSphere ESXi (e.g. 4.0 or 4.1) in the tables below.
**Unlisted Major/Minor versions are not supported.
**Unless otherwise indicated, the base Major/Minor version shown is the minimum required.
**Some UC apps will also require a minimum Maintenance Release and will indicate if this is the case. Otherwise UC does not specify or recommend patches, updates or Maintenance Releases (e.g. 4.0 U1) for a required Major/Minor Release of vSphere ESXi. Follow recommendations of the server vendor and VMware for what you should use. Unless otherwise indicated by a UC app, UC supports all VMware vSphere ESXi patches, updates and Maintenance Releases for a supported Major/Minor Release at time of VMware launch as long as the server vendor supports them.

 

=== VMware vSphere ESXi Version Support for Call Processing and System Management Applications ===

{| class="wikitable FCK__ShowTableBorders"
|-
!
Application 

! VMware vSphere ESXi 4.0 
! VMware vSphere ESXi 4.1 
! VMware vSphere ESXi 5.0 
|-
| Unified Communications Manager (Unified CM)
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Cisco Emergency Responder (CER)
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Session Manager Edition (SME)
| 8.5+, 8.6+
| 8.5+, 8.6+
| 8.5+, 8.6+
|-
| Unified Attendant Consoles
| 8.0(3)+, 8.5+
| 8.6+
| Not supported
|-
| UC Management Suite (OM, SM, SSM, PM)
| 7.1 and later
| 7.1 and later
| Not supported
|-
| Cisco Intercompany Media Engine (CIME)
| Not supported
| 8.6(2)+
| 8.6(2)+
|}

=== VMware vSphere ESXi Version Support for Messaging and Presence Applications ===

{| style="width: 812px; height: 108px" class="wikitable FCK__ShowTableBorders"
|-
! Application 
! VMware vSphere ESXi 4.0 
! VMware vSphere ESXi 4.1 
! VMware vSphere ESXi 5.0 
|-
| Cisco Unity Connection
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
|-
| Cisco Unity
| 7.x and later
| 7.x and later
| 7.x and later
|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
| 8.0(2) and later
| 8.0(2) and later
|
|}

 

=== VMware vSphere ESXi Version Support for Contact Center Applications ===

{{Note| For Virtual Machines that need '''more than 4 vCPUs''', the VMware vSphere ESXi '''Enterprise Plus''' licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)}}

{| style="width: 816px; height: 396px" class="wikitable FCK__ShowTableBorders"
|-
! Application
! VMware vSphere ESXi 4.0 and 4.0 Updates
! VMware vSphere ESXi 4.1  and 4.1 Updates
! VMware vSphere ESXi 5.0  and 5.0 Updates 
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]]
| 8.0(2)+ or 8.5(1)+
| 8.0(2) SU2+ or 8.5(1)+
| 8.0(2) SU4+ or 8.5(1) SU2+
|-
| [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Work Force Optimization (WFO), Quality Management (QM), and Work Force Management (WFM)]
| 8.5(1)+
| 8.5(2)+
| Not supported
|-
| [[Unified Contact Center Enterprise]] 
| ESXi 4.0 Update 1 (minimum required). See below
| See below
| See below
|-
| - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tools (not supported in 8.5x and later)
| 8.0(2)+ or 8.5(1)+
| 8.0(2)+ or 8.5(1)+
| Not supported
|-
| [[Virtualization for Unified Intelligence Center|Cisco Unified Intelligence Center]] 
| 8.0(3)+
| 8.5(2)+
| Not supported
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]
| 8.0(2)+ or 8.5(1)+
| 8.0(2)+ or 8.5(1)+
| Not supported
|-
| [[Unified Customer Voice Portal]] (all components) 
| 8.0(1)+ or 8.5(1)+
| 8.0(1)+ or 8.5(1)+
| Not supported
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| 8.5(1)+
| 8.5(2)+
| Not supported
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| 8.5(1)+
| 8.5(1)+
| Not supported
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Unified Email Interaction Manager and Web Interaction Manager]]
| 4.3(2)+
| 4.3(2)+
| Not supported
|-
| [[Virtualization_for_Cisco_Finesse|Cisco Finesse]]
| 8.5(3)+
| 8.5(3)+
| Not supported
|}

== Support of Cisco VN-Link and Cisco Nexus 1000V ==

Note that Cisco Unified Contact Center Enterprise does NOT support this – see [[UCS Network Configuration for UCCE|UCS Network Configuration for Unified CCE]].

Unless otherwise indicated above, Cisco VN-Link, Cisco Nexus 1000V, Cisco Nexus 1010, and VM-FEX are supported by UC applications that support the VMware vNetwork Distributed Switch (see [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]).

Cisco VN-Link, Cisco Nexus® 1000V, Cisco Nexus 1010, VM-FEX and VMware vNetwork Distributed Switch all require VMware ESXi Enterprise Plus Edition (see [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]). Other editions do not support these capabilities.

For UC on UCS B-series, Cisco UCS 6100 does not currently support Layer 3 to Layer 2 COS markings. Additionally, the UC applications and operating systems cannot set the Layer 2 COS markings. Use of Cisco Nexus® 1000V is therefore strongly recommended as this is the only way to manage traffic congestion through the current UCS 6100. Please recall that traffic congestion risk will vary and is dependent on many factors such as UC vs. non-UC virtual machine count and their traffic characteristics across all blades, chassis and fabric extenders connected to the same UCS 6100.

For UC on UCS C-series, Cisco Nexus® 1000V is recommended but not mandatory as there is no intermediate UCS 6100 to design around.

For more information on Cisco VN-Link, Cisco Nexus 1000V and VM-FEX, see the following:
:* http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns892/ns894/white_paper_c11-525307.html
:* http://www.cisco.com/en/US/products/ps9902/index.html
:* http://www.cisco.com/en/US/netsol/ns1124/index.html

== Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client ==

 '''VMware vSphere Client''' (formerly branded VI Client) and '''VMware vCenter''' are management consoles for VMware vSphere hosts.

:*vSphere Client is free but only has basic management capabilities.
:*vCenter is not free as it has advanced management capabilities, but note UC may not support every feature in vCenter. vCenter is mandatory for any specs-based deployment.

 

'''VMware vSphere ESXi''' is sold in several '''Editions''' with different levels of feature support.

:*[https://www.vmware.com/products/vsphere/buy/editions_comparison.html Click here for a comparison of VMware vSphere ESXi feature Editions on vmware.com].
::*[http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html Click here for a clarification of “free ESXi 4.1” vs. “vSphere ESXi 4.1 Hypervisor Edition”] (formerly branded as "VMware ESXi Single Server Edition" or “free ESXi”).
::*For details on supported features for 4.x versions of other vSphere ESXi Editions, see your VMware account team. VMware on their web site [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010579 provides a "best effort" comparison here].
:*If buying VMware vSphere ESXi direct from VMware:
::*[http://www.vmware.com/products/vsphere/purchase-advisor/index.html Click here for VMware's Purchase Advisor for vSphere on vmware.com].
::*[https://www.vmware.com/files/pdf/vsphere_pricing.pdf Click here for an overview of VMware vSphere ESXi pricing on vmware.com].

 

There are no UC-specific restrictions on what VMware vSphere ESXi feature Edition you "can" use, but the Edition you "should" use will be determined by VMware licensing rules based on aspects of the UC deployment. The customer is responsible for selecting the correct VMware vSphere ESXi Edition based on their feature and UC application requirements. The following non-exhaustive list is provided for convenience only as examples of what must be considered under VMware's current licensing rules, which are subject to change:

:*If you want to use Cisco Nexus 1000V with UC, that requires the VMware vSphere ESXi feature "Distributed Switch" which is only available in Enterprise Plus Edition.
:*If you want to use a UC virtual machine OVA template with a large quantity of vCPU, verify the VMware vSphere ESXi Edition supports sufficient "vCPU Entitlement" for that OVA's vCPU count.
::*E.g. the Unity Connection 20K user OVA that requires 7 vCPU per VM.
:*Verify all the UC-supported VMware vSphere ESXi features you want to use are [https://www.vmware.com/products/vsphere/buy/editions_comparison.html supported by the Edition you pick].
:*The "Cisco UC Virtualization Hypervisor" is only supported for use with Business Edition 6000 and has the following restrictions:
::*It is not available or transferable for use with any other hardware or software.
::*Server Hardware restricted to UCS C200 M2 TRC#1
::*Max total vRAM across all VMs is 16 GB (of which 14 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Does not support VMware vCenter management. Does not offer any [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features like other Editions].
:*The "Cisco UC Virtualization Foundation" is only supported for use with Business Edition 6000 and UC on UCS.
::*Not available direct from VMware, only sold as part of BE6K or UC on UCS. It is not available or transferable for use with non-UCS hardware or non-UC software.
::*Server Hardware restricted to 2-socket UCS B-Series models and 2-socket UCS C-Series models.
::*Max total vRAM across all VMs is 32 GB (of which 30 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Supports VMware vCenter management (purchased separately). UC-supported [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features] limited to vStorage APIs. All other UC-supported features (including but not limited to VMware High Availability, Data Recovery, vMotion, Distributed Switch, etc.) are not offered.

 

Finally, note that UC may not support all of the features that are included in the VMware vSphere ESXi Edition you pick. This may be because the feature is N/A for a UC deployment, or it has not been sufficiently tested before UC will support, or it requires application enhancements before UC can support.

The table below lists VMware feature support by UC app/version. If the feature is supported, click on its name in the table to view UC caveats and best practices. Feature support may vary by UC app. This site will be updated as new support becomes available.

{{note| feature support for Cisco Unified Contact Center Enterprise varies by component (e.g. Peripheral Gateway) and deployment model (e.g. "Rogger") - this section will give a summary support position, but for individual components see [[Unified Contact Center Enterprise|Support for Virtualization on the ESXi/UCS Platform]].}} 

=== Legend for Feature Support Tables ===

:*Y(C) = Supported with '''C'''aveats - see [[#Best_Practices|Best Practices]] for details
:*Y(P) = '''P'''artial (limited) support only - see [[#Best_Practices|Best Practices]] for details
:*No = the feature is not supported at this time - see [[#Best_Practices|Best Practices]] for alternatives, if any.

=== VMware Feature Support for Call Processing and System Management 8.0(2) through 8.6(1) ===

{| border="1"
|+ ''' '''
|-
! Feature
! Unified CM
! CER
! SME
! Unified Attendant Consoles
! UPM
! UOM, USM, USSM
! CIME 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C)
| Y(C) 
| Y(C) 
| Y(C) 
| Yes
| Y(C) 
| Y(C) 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C)
| Y(C)
|  Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(P)
| Y(P)
| No 
| No 
| Y(P)
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No 
| No 
| No
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)  
| Y(P)  
| Y(P)  
| Y(P)  
| Yes
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C)
| No
| Y(C)
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| Y(C) 
| Y(C)
| Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C) 
| Y(C) 
| Y(C) 
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(C)
| Y(C) 
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C) 
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| Y(C)
| No 
| Y(C)
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 5.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! All vSphere ESXi 5.0 Features
| No
| No
| No
| No
| No
| No 
| No
|}

=== VMware Feature Support for Messaging and Presence 8.0(2) through 8.6(1) ===

{| border="1"
|+ '
|-
! Feature
! Unity Connection
! Unity
! Unified Presence
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(PP
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| Y(C)
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| Y(C) 
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(P)
| No
| Y(P)
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| Y(C) 
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
|- align="center"
! [[#Identity|Identity]]
| No  
| No  
| Y(C) 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| 
|}

 

=== VMware Feature Support for Contact Center 8.0(2) through 8.6(1) ===

{| style="width: 906px; height: 823px" border="1"
|+  
|-
! Feature
! Unified CCX
! Cisco WFO, QM, and WFM
! Unified CCE, CVP
! Unified IC
! Cisco MediaSense
! SocialMiner
! Unfied EIM-WIM
! Cisco Finesse
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
|
|
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| Y(C)
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C) 
| No
| No
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C)
| Y(C) 
| No
| Y(C) 
| No
| No
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P) 
| No
| Y(P) 
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P) 
| Y(P) 
| Y(P) 
| Y(P) 
| No
| No
| No
| No
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| No
| Y(C) 
| Y(C)
| No
| No
| No
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(P) 
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C)
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
|
|
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C)
| No
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No
| No
| No
| 
|}

== Best Practices ==

=== Virtual Machine Templates (OVA files) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

See www.dmtf.org for details on the Open Virtualization Format, which describes an OVF Package (a directory of files describing a virtual machine's configuration) and an OVA Package (single tar file containing an OVF Package).

“Template” in this context refers to an OVA file that defines the virtual server (but not the “workload”, i.e. the UC OS and application). Each virtualized UC product provides a set of predefined virtual machine templates (as OVA files) for supported Virtual Machine (VM) configurations. Customers must download and use these OVA template files for initial install, as they cover items such as supported capacity levels and any required OS/VM/SAN “alignment”. OVAs configured differently than the predefined templates are not supported at this time. To download the OVA files, refer to the [[Unified Communications Virtualization Sizing Guidelines|Unified Communications Virtualization sizing guidelines]].

=== Copy Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Copying a Virtual Machine (VM) copies both the virtual server configuration and the workload (UC OS and application) running on that virtual server to a file on networked shared storage. This allows VMs to be copied, then subsequently modified or shut down. This feature effectively provides a method to do full system backup/restore, take system images or revert changes to software versions, user data and configuration changes.

:*Prior to copying, the VM must first be shutdown (which will shut down the virtual server, the UC OS and the UC application).
:*If uploading a VM copy as a “whole system restore”, clustered UC applications such as CUCM will probably require their replication to be manually “fixed” via a CLI command.

=== Restart Virtual Machine on Different ESXi Host ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

A Virtual Machine (VM) file on network/shared storage can be booted on any physical server hosting ESXi that has access to that network shared storage. With multiple physical ESXi hosts connected to the same network shared storage, this can be used to perform:

:*Fast manual server moves, e.g. moving VM from ESXi host A to ESXi host B in another chassis, closet, building, etc.
:*Fast manual server recovery, e.g. moving VM from ESXi host A that has just had a server hardware or VMware failure to ESXi host B that is healthy. See also VMware High Availability and Site Recovery Manager.
:*Setting up software at a staging location to be later moved or deployed elsewhere. For multi-site scenarios, this may instead require “exporting” the VM.

=== Resize Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Similar to adding/removing physical hardware to/from a physical server, you can add/remove virtual hardware (vCPU, vRAM, vDisk, vNIC, etc.) to/from a Virtual Machine (VM) via a software change in VMware’s configuration interfaces. Where supported, this provides the VM equivalent of migration to a more powerful or less powerful server.

:*Any changes to a VM must align with the best practices in [[#Virtual_Machine_Templates_.28OVA_files.29|Virtual Machine Templates (OVA files)]]. VM changes that result in an unsupported OVA configuration are not allowed. Even if you align with supported OVA configurations, desired VM changes may be prevented by one of the other caveats below.
:*Support for adding virtual hardware resources (similar to moving from a less powerful server to a more powerful server, such as MCS 7825 ⇒ MCS 7845) depends on which resource, and which UC product:
::*Adding vCPU is supported for all apps except Unity and Unity Connection, but requires VM to be shutdown first.
::*Adding vRAM is supported but requires VM to be shutdown first.
::*Adding vDisk is not supported as it would require re-partitioning by the application.
:*Adding vNIC is not supported unless the UC app supports multiple network connections with different IP addresses. See best practices for [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]].
:*For all other changes, it is recommended to backup the application, reinstall application on a new OVA file, and restore the application.
:*Removing virtual hardware resources (vCPU, vRAM, vDisk, etc.) is not supported (similar to moving from a more powerful server to a less powerful server, such as MCS 7845 ⇒ MCS 7825). These migrations require backing up the application, reinstalling on a new OVA file, and and restoring the application.
:*Live runtime resizing via the VMware Hot Add feature is not supported.

=== VMware Hot Add ===

Not supported. See [[#Resize_Virtual_Machine|Resize Virtual Machine instead]].

=== Multiple Physical NICs and vNICs ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). Network traffic is switched from physical NICs to “vNIC’s” of the Virtual Machines (VM) via either VMware vSwitch or Cisco Nexus 1000V. Customers can use these multiple NICs for VM network traffic, VMware console access, or management “back-doors” for administrative access, backups, software updates or other traffic that is desired to be segregated from the VM network traffic. All these uses are supported for UC but note that UC apps like CUCM only support a single vNIC with a single IP address.

=== VMware High Availability (HA) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature automatically restarts a Virtual Machine (VM) on the same physical server or a different physical server. It can be used to supplement software redundancy as a means of fast, automated Failed-server recovery when a VM (but not the application) is hung or if there is a fault with the physical host server or VMware software.

:*Failovers to other servers must not result in an unsupported deployment model (e.g. destination server must align with supported co-residency after failover occurs).
:*Does not protect vs. faults with the SAN or network hardware.

=== VMware Site Recovery Manager (SRM) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature provides an automated disaster recovery solution that works on a “site to site” basis, where a “site” comprises physical servers, VMware and SAN storage. Refer to the VMware documentation for requirements to use this feature. There are no special requirements to use this feature with UC apps that support it.

=== VMware Identity ===

The VMware identity feature allows you to copy an existing instance of a virtual Cisco Unified Presence, and change its identity. The identity of a system is made up of every setting that you usually configure during a fresh install (such as IP address, hostname, passwords).

You can then use this new identity for another instance of a Cisco Unified Presence on a virtual machine. This avoids you having to perform a complete installation each time you deploy a new Cisco Unified Presence.

=== VMware vNetwork Distributed Switch ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Supporting apps in UC on UCS may either use this feature, or the Cisco VN-Link technology (such as Cisco Nexus 1000V).

 

=== VMware vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Cl]]ient.

This feature migrates a live, running Virtual Machine (VM) from one physical server to another.

The following applies to any use of vMotion with UC apps:

:*VM must be installed on shared storage (SAN).
:*Source and destination physical servers must be connected to same SAN.
:*Destination physical server must not end up with over-subscribed hardware after the migration. Supported capacity and co-residency rules for UC must be followed before and after the migration.
:*VMware “Long Distance vMotion” (site to site) is not supported.
:*The only supported scenario is a manual move to a different server, e.g. for planned maintenance on the server or VMware software, or during troubleshooting to move software off of a physical server having issues.
:*Use of vMotion for real-time load-balancing of live UC VMs is not supported, whether alone or in conjunction with VMware Dynamic Resource Scheduler (DRS) or Dynamic Power Management (DPM).
:*Moving a shut down VM during a maintenance window, i.e. a "cold migration" or "host to host migration", is not vMotion and is supported.

If the UC app is listed as "Supported with Caveats", then support is as described below:

:*Migration of UC VMs that are live and processing live traffic is supported, but note that Cisco testing cannot cover every possible operational scenario. Testing has shown there is a slight risk of calls in progress being impacted for a few seconds as the migration occurs, with worst case result of the affected calls being dropped. If vMotion is suspected as the cause of dropped calls, customers should gather appropriate application logs as well as performance data from VMware vCenter and send to Cisco TAC for analysis.

If the UC app is listed as "Partial" support, then support is “maintenance mode only” as described below:

:*"Maintenance mode only" - VMware vMotion by definition operates on live VMs, but the VM running the UC app must be “live but quiescent”. I.e. in a maintenance window, not in production, not processing live traffic. This is because during the vMotion cutover, the system is paused, which for real-time UC apps creates service interruption which degrade voice quality after the migration for calls in progress.

 

=== VMware Dynamic Resource Scheduler ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== VMware Dynamic Power Management ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== Long Distance vMotion ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported. Long Distance vMotion is a joint Cisco and VMware validated architecture for using the vMotion feature across data centers. For more information, see http://blogs.cisco.com/datacenter/comments/cisco_and_vmware_validated_architecture_for_long_distance_vmotion/ and http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns836/white_paper_c11-557822.pdf.

=== Storage vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This “customer convenience” feature provides easy migration of a live system from one SAN to another SAN. For UC apps, an easier suggested alternative is to just perform manual VM shutdown and migration to the new SAN. However, if Storage vMotion must be used, it is only under the following conditions:

:*Requires SAN storage.
:*May only be done during a maintenance window with UC VMs shut down.

=== VMware vCenter Update Manager (VUM) ===

NOTE: Support varies by application and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature automates patching and updating of VMware vSphere hosts. Note that Cisco Unified Communications applications upgrades, patches and updates can not be delivered through vCenter Update Manager.

=== VMware Consolidated Backup (VCB) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature provides integration with 3rd-party backup utilities so that they can non-disruptively backup the OS and application in a Virtual Machine (VM). See also VMware Data Recovery and Copy Virtual Machine.

Existing UC app methods of backing up the software continue to be supported.

=== VMware Data Recovery ===

Not supported. See [[#VMware_Consolidated_Backup_.28VCB.29|VMware Consolidated Backup]] for what is supported.

=== VMware Snapshots ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

Used to preserve the state of a VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique. See also VMware Data Recovery and Copy Virtual Machine.

=== VMware Fault Tolerance ===

Not supported. See [[#VMware_High_Availability_.28HA.29|VMware High Availability]] for what is supported. Another alternative is manual Virtual Machine shutdown and migration.

=== VMware vCenter Converter ===

P2V tools are not supported. To migrate from bare-metal servers (e.g. Cisco 7800 Series Media Convergence Server) to UC on UCS, the supported procedure is:

:*upgrade to 8.x software version on the bare-metal server
:*take a software backup
:*fresh install 8.x software on VMware / UC on UCS
:*restore from backup

=== VMsafe ===

Not supported. See the documentation for the UC application software or UC appliance software to see what is supported.

=== VMware vShield ===

Not supported. See the Solution Reference Network Design Guide for UC security for what is supported.

=== Virtual Appliance Packaging of UC apps ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party VM-based Backup Tools ===

Not supported. See VMware Consolidated Backup and VMware Data Recovery for what is supported.

=== 3rd-Party VM-based Deployment Tools ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party Physical To Virtual (P2V) Migration Tools ===

Not supported. See VMware vCenter Converter for what is supported.

=== VMware Boot from SAN ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

VMware ESXi 4.1 is required for this feature. Even it works with 4.0, VMware's official support is only for 4.1 and later. Requires use of a "diskless" server - see Supported Hardware for tested reference configurations. Both VMware ESXi and UC apps are installed on, and boot from, the fibre channel SAN. See UCS page at www.cisco.com/go/swonly for storage support policy.

== Services and Support Contracts for VMware are Required ==

Customers deploying virtualized UC must have a valid support contract for the VMware software in order to be supported by Cisco.

Customers purchasing VMware software licenses from Cisco must also purchase a subscription services part number from Cisco (for part number examples, see the UC on UCS page at www.cisco.com/go/swonly).

Customers purchasing VMware software from a 3rd-party must purchase subscription services from that 3rd-party or from VMware.

Customers should note that for VMware vSphere Hypervisor (formerly called “ESXi Single Server Edition” or “free ESXi”), VMware does not offer the same services options and terms as they do for their Standard, Advanced, Enterprise or Enterprise Plus Editions. Customers should take this into account when planning and pricing their support strategy.

Cisco Field and Channel Partners may consult the User Connect Licensing Ordering Guide for more information.

== Cisco TAC Support Expectations ==

The following table describes how TAC support works for VMware in a UC on UCS context, based on who VMware was purchased from.

Special case: when Cisco as a VMware reseller sells VMware Enterprise License Agreements, it is treated as a VMware direct sale for TAC support purposes based on how the maintenance contracts are structured.

 

{| border="1"
|-
! 
! Buy from Cisco as Collaboration SKU
! Buy from Cisco as Data Center SKU
! Buy from 3rd-party, or enterprise/site license
|-
! Available VMware ESXi Editions
| Standard
| Advanced, Enterprise or Enterprise Plus
| Standard, Advanced, Enterprise, Enterprise Plus or vSphere Hypervisor (formerly "Single Server Edition" or "free ESXi"
|-
! Mandatory Support Contracts
| ISV1 from Cisco as Collaboration Service SKU
| ISV1 from Cisco as Data Center Service SKU
| "SnS" subscription from VMware
|-
! Who takes first call?
| Cisco
| Cisco
| VMware
|}

'''TAC Responsibility:''' Note that multi-vendor triage is the norm in virtualized deployments, where the storage, server, hypervisor, OS and application are potentially all from different vendors. Cisco Voice TAC responsibility is the UC application, demarcated at the Virtual Machine. Cisco Server Virtualization TAC responsibility is for VMware (via triage), Cisco UCS, Cisco storage access (or triage with customer and their vendor) and storage array (via triage with customer and their vendor). Escalation to VMware, the customer, or the customer's storage vendors will be done as needed for solution components not produced by Cisco.

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications Virtualization Downloads (including OVA/OVF Templates)

2011-12-16T22:05:40Z

Sdurvasu:

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

= Supported Virtual Machine OVA Templates =

A virtual machine template defines the configuration of the virtual machine's virtual hardware. Open Virtualization Format (OVF) is an open standard for describing a virtual machine template, and Open Virtualization Archive (OVA) is an open standard to package and distribute these templates. Files in OVA format have an extension of ".ova".

Cisco Unified Communications applications '''must''' use one of the supported virtual machine configurations in the tables below in order to be supported. The OVAs contain virtual hard disks with pre-aligned disk partitions. Using the OVA is the only way to deploy the UC applications on aligned disks. Using the OVA also guarantees that all configuration of the virtual machine is correct and supported.

In the tables below '''users''' refers to the [http://tools.cisco.com/cucst/faces/login.jsp Cisco Unified Communications Sizing Tool] and the [http://www.cisco.com/go/ucsrnd design guides] for the indicated user count at a particular BHCA, number of devices per user, device mix per VM, etc. Actual capacity and total supported devices will be design-dependent; please follow all rules in the design guides and sizing tools.

 See [[Downloading OVA Templates for UC Applications]] for more information on how to download OVA templates for UC Applications.

For '''Specifications-based''' deployments (non TRC deployments), the CPU core count AND the CPU core speed correspond to physical CPU cores and physical CPU core speeds. Both are required to be met to support a full load VM OVA. At this time, only core speed for full load is defined. Do not use lower physical CPU core speeds until Cisco defines minimum speed for lower load levels. Cisco TAC will not troubleshoot a VM that is not receiving sufficient CPU cycles.

== Unified Communications Manager ==

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=268439621&catid=278875240 General OVA Template Download Location] 
*[[OVA Template Details for Unifed CM Release 8.0]] 
*[[OVA Template Details for Unifed CM Release 8.5]] 
*[[OVA Template Details for Unifed CM Release 8.6]] 

 

== Cisco Emergency Responder ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Emergency Responder'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 12,000 users (C200 only)]
| 2 @ 2.13 GHz each (600 MHz reserved)
| 4 GB (4 GB reserved)
| 1 x 80 GB
| 1
|
Use on C200 M2 TRC#1 only.

Limits:

:*12,000 IP phones
:*2,500 analog phones
:*1,200 roaming phones (per Emergency Responder cluster)
:*500 LAN switches
:*30,000 switch ports
:*3,000 ERLs

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 20,000 users]
| 1 @ 2.55 MHz (600 MHz reserved)
| 2.25 GB (2.304 GB reserved)
| 1 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

Limits:

:*20,000 IP phones
:*5,000 analog phones
:*2,000 roaming phones (per Emergency Responder cluster)
:*1,000 LAN switches
:*60,000 switch ports
:*7,500 ERLs

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 30,000 users]
| 2 @ 2.55 MHz each
| 6 GB
| 2 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

Limits:

:*30,000 IP phones
:*10,000 analog phones
:*3,000 roaming phones (per Emergency Responder cluster)
:*2,000 LAN switches
:*120,000 switch ports
:*10,000 ERLs

|}

 

== Session Manager Edition ==

{| border="1"
|+ '''Supported OVA Templates: Session Manager Edition'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&isPlatform=Y&mdfid=282827095&sftType=Unified+Communications+Manager+Virtual+Machine+Templates&treeName=Voice+and+Unified+Communications&modelName=Cisco+Unified+Communications+Manager+Version+8.0&mdfLevel=Software%20Version/Option&treeMdfId=278875240&modifmdfid=null&imname=&hybrid=Y&imst=N Use CUCM "7500 users"]
| See CUCM "7500 users"
| See CUCM "7500 users"
| See CUCM "7500 users"
| See CUCM "7500 users"
|
|}

 

== Unified Attendant Consoles ==

{| border="1"
|+ '''Supported OVA Templates: Unified Attendant Consoles'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! OVA for CUxAC
| 1 @ 2.55 GHz
| 2 GB
| 1x 80GB
| 1
| Note: Cisco does not provide preconfigured OVA files for CUxAC. Please build manually using these requirements. CUxAC requires a VM to meet or exceed minimum physical server specs described [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/data_sheet_c78-520987.html on the CUxAC datasheet]
|}

 

== Cisco Intercompany Media Engine ==

{| style="width: 712px; height: 416px" border="1"
|+ '''Supported OVA Templates: Cisco Intercompany Media Engine, Release 8.6(2)'''
|- style="background: rgb(229,228,226)"
! rowspan="2" | VM OVA Capacity 
! colspan="5" | VM OVA Parameters 
! rowspan="2" | Notes 
|- style="background: rgb(229,228,226)"
! vCPU Cores (= Physical Cores)
! Physical CPU Load was Calibrated To
! vRAM (=Physical Memory)
! vDisk (=Physical space)
! vNIC
|-
!
CIME 5 peer IDs node Only for non-BE6K/C200M2 TRC#1

| 2 (with 3600 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 1x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or BE6000. Up to 5 peer IDs.
 

|-
!
CIME 10 peer IDs node Only for non-BE6K/C200M2 TRC#1

| 4 (with 7200 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 2x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or BE6000. Up to 10 peer IDs.
 

|}

 

 

== Cisco Unity Connection ==

*[http://www.cisco.com/cisco/software/type.html?mdfid=283062758&flowid=5455 General Unity Connection OVA Template Download Location] 
*[[OVA Template Details for Unity Connection Release 8.0]] 
*[[OVA Template Details for Unity Connection Release 8.5]] 
*[[OVA Template Details for Unity Connection Release 8.6.1]] 
*[[OVA Template Details for Unity Connection Release 8.6.2]] 

 

== Cisco Unity ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Unity'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! 5000 users
| 2 (requires VMware CPU Affinity)
| 4 GB
|
4x 24 GB

:*vDisk 1 = Operating system
:*vDisk 2 = Cisco Unity binaries
:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

| 1
|
*Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
*Limits:

:*48 ports
:*36 text-to-speech ports

|-
! 15,000 users
| 4 (requires VMware CPU Affinity)
| 4 GB
|
4x 24 GB

:*vDisk 1 = Operating system
:*vDisk 2 = Cisco Unity binaries
:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

| 1
|
*Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
*Limits:

:*144 ports
:*36 text-to-speech ports

|}

 

== Cisco Unified Presence ==

See also:

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=280448682&i=rs General OVA Template Download Location]
*[[OVA Template Details for Unified Presence Release 8.0(x)]] 
*[[OVA Template Details for Unified Presence Release 8.5(x)]] 
*[[OVA Template Details for Unified Presence Release 8.6(1)]] 
*[[OVA Template Details for Unified Presence Release 8.6(2)]] 
*[[OVA Template Details for Unified Presence Release 8.6(3)]] 

 

== Cisco Unified Contact Center Express/Cisco Unified IP Interactive Voice Response (IVR) ==

{{Note| The information for Unified IP IVR is the same as Unified CCX.}}

See also:

*[[Virtualization for Unified CCX]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest| Unified CCX OVA Templates]: {{Note|Unified CCX OVA version 2 is for use with ESXi 4.1. Please follow [[Unified Communications VMware Requirements]] for ESXi 4.1 requirements (VMware Tools upgrade, LRO disabling, etc.)}}

 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Express'''
|- style="background: rgb(229,228,226)"
! colspan="2" | Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 100 agents] (Release 8.5(1))
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 300 agents] (Release 8.0(2) and Release 8.5(1))
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 400 agents] (Release 8.5(1))
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! rowspan="3" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=latest Single OVA] (Release 8.5 (1) or later)
! 100 agents
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
|
|-
! 300 agents
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! 400 agents
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.2]
| 2
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = Optional - can be used to hold SQL Server Data files

| 1
|
Capacities

:*900 named users
:*300 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Base Server Configuration (CR/QM/AQM)]
| 2
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)

| 1
|
Capacities

:*3600 named users
:*1200 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Recording Server Configuration (CR/QM/AQM)]
| 4
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM recording service binaries
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recording cache

| 1
|
Capacities

:*300 concurrent voice recordings for Server (SPAN) and Network recording
:*150 concurrent voice and screen recordings, recordings for Server (SPAN) and Network recording

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.1]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = Optional - can be used to hold SQL Server Data files

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.1 Base Server Configuration (CR/QM/AQM)]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM Configuration (CR/QM/AQM)]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage )

| 2
|
Capacities

:*300 named users
:*150 concurrent users
:*150 voice recordings, for all recording types (desktop, server and network)
:*150 voice+screen recordings, for all recording types (desktop, server and network)

|}

== UC Management Suite (PM, OM, SM, SSM) ==

There are different OVAs for premise UC on UCS deployments vs. Hosted Collaboration Solution deployments.

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise UC on UCS Deployments'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! IOPS (avg) (1)
! IOPS (max) (1)
! vNIC
! Notes
! 
|-
! CUPM up to 1K phones (VM-CUCMS_1S)
| 1
| 2 GB
| 1x 30 GB
| 100
| 500
| 1
| 
|-
! CUPM 1K to 10K phones
| 4
| 4 GB
| 1x 40 GB (2)
| 100
| 500
| 1
| 
|-
! CUPM 10K to 60K phones app server
| 4
| 4 GB
| 1x 30 GB(3)
| 100
| 500
| 1
| requires DB VM
|-
! CUPM 10K to 60K phones database server
| 4
| 8 GB
| 1x 120 GB(3)
| 100
| 500
| 1
| requires App VM
|-
! CUOM/SM 1K phones
| 1
| 3 GB
| 1x 50 GB
| 6
| 15
| 1
| 
|-
! CUOM 10K phones (VM-CUCMS_2L)
| 2
| 8 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUOM 45K phones (VM-CUCMS_4L)
| 4
| 8 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSM 10K Phones (VM-CUCMS_2)
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUSM 45K Server (VM-CUCMS_4)
| 4
| 4 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSSM 10K phones (VM-CUCMS_1)
| 1
| 4 GB
| 1x 60 GB
|
|
| 1
| 
|-
! CUSSM 45K Phones
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUCMS 10K phones Co-resident (VM_CUCMS_8)
| 8
| 16 GB
| 1x 320 GB (2)
| 100
| 500
| 1
| 
|}

Notes: (1) IOPS are for each CM publisher synced in parallel. If only one CM publisher then IOPS are 100/500. The maximum figures would be expected during nightly Infrastructrure or Subscriber syncs. (2) PM requires SAS or SCSI drives for deployments over 1K phones up to 10k phones (Disks must be aligned) (3) PM requires FC SAS for deployments over 10K phones (Disks must be aligned)

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise Systems'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K Server OVA]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K to 10K Server OVA]
| 4
| 4 GB
| 1x 40 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K App/Web Server OVA]
| 4
| 4 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K Database Server OVA]
| 4
| 8 GB
| 1x 120 GB
| 1
| 
|}

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Hosted Collaboration Solution'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283112898&flowid=20421&softwareid=282773197&release=8.0&rellifecycle=&relind=AVAILABLE&reltype=latest CUOM+CUSM 1K phones for HCS (HCS_OM&SM_1K)]
| 1
| 3 GB
| 1x 50 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283315737&flowid=19121&softwareid=281934350&release=2.2&rellifecycle=&relind=AVAILABLE&reltype=latest CUPM 1K phones for HCS (HCS_PM_1K)]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|}

== Unified Contact Center Enterprise ==

See also:

*[[Unified Contact Center Enterprise]]
*[http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Capacities_and_VM_Configuration_Requirements Unified CCE OVA Templates]
*See also [http://docwiki.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE#Unified_CCE_Scalability_Impacts Scalability Impacts]

Templates are available for Windows Server 2003 and Windows Server 2008 R2. [http://www.cisco.com/cisco/software/release.html?mdfid=268439622&release=1.1&relind=AVAILABLE&flowid=5210&softwareid=283914286&rellifecycle=&reltype=latest Download] the appropriate OVA file for the Windows OS that you are configuring. When you deploy the OVA, a drop-down list of the configurations are presented allowing you to select the appropriate configuration for the UCCE sized component that you are installing.

 

{| border="1" cellspacing="3" cellpadding="3"
|- style="background: rgb(229,228,226)"
! Configuration Name
! vCPU Cores
! vRAM / Memory (GB)
! vDisk (GB)
! vNIC 
! Notes
|-
| colspan="7" | '''Note: Windows Server 2008 R2 configurations are contained in the UCCE_8.5_win2008_vmv7_v1.2.ova file, Windows Server 2003 configurations are contained in the UCCE_8.5_win2003_vmv7_v1.1.ova file'''
|-
| '''Router 12000 agents'''
| 4
| 8
| 1 x80
| 2
| Supported on Windows 2008 only 
|-
| '''Logger 12000 agents'''
| 4
| 8
| 1x 80 for OS 1x 500 for DB
| 2
|
The two vDisks can be in the same datastore

Supported on Windows 2008 only

|-
| '''Router 8000 agents'''
| 2
| 4
| 1 x 80
| 2
|
|-
| '''Logger 8000 agents'''
| 4
| 4
| 1x 80 for OS 1x 150 for DB
| 2
| The two vDisks can be in the same datastore 
|-
| '''Rogger 4000 agents'''
| 4
| 4
| 1x 80 for OS 1x 150 for DB
| 2
| The two vDisks can be in the same datastore 
|-
| '''Agent PG – CTIOS 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''Agent PG – CAD 1000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''Agent PG – CTIOS 450 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Agent PG – CAD 297 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''MR PG 2000 agents 10 pims'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''MR PG 1000 agents 5 pims'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''VRU PG 9600 ports 10 pims'''
| 2
| 2
| 1x 80
| 2
|  
|-
| '''VRU PG 1200 ports 4 pims'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Avaya ACD PG'''
| 2
| 4
| 1x 80
| 2
| See the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted] for capacity information.
|-
| '''TDM ACD PG 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''TDM ACD PG 250 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''UCC Gateway PG 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''UCC Gateway PG 450 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Administration Client'''
| 1
| 2
| 1x 40
| 1
|  (Client AW)
|-
| '''Administration Server - AW'''
| 1
| 2
| 1x 40
| 1
|  
|-
| '''AW-HDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
|  (200 reporters.) The two vDisks can be in the same datastore 
|-
| '''AW-HDS(12000 agents)'''
| 4
| 8
| 1x 80 for OS 1x 1TB for DB
| 1
| (200 reporters). The two vDisks can be in the same datastore. Specifically for 12,000 agent deployement.
|-
| '''AW-HDS-DDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
|  (200 reporters.) The two vDisks can be in the same datastore
|-
| '''AW-HDS-DDS (12000 agents)'''
| 4
| 8
| 1x 80 for OS 1x 1TB for DB
| 1
|
(200 reporters). The two vDisks can be in the same datastore. Specifically for 12,000 agent deployement

Supported on Windows 2008 only 

|-
| '''HDS-DDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
| (200 reporters.) The two vDisks can be in the same datastore  
|-
| '''HDS-DDS (12000 agents)'''
| 4
| 8
| 1x 80 for OS 1x 1TB for DB
| 1
|
(200 reporters). The two vDisks can be in the same datastore. Specifically for 12,000 agent deployement

Supported on Windows 2008 only 

|-
| '''CCMP single box 1500 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP Web/App Svr 8000 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP with Config AW 1500 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP DB only 8000 agents'''
| 8
| 4
| 1x 250
| 1
|  
|}

== Unified Customer Voice Portal ==

See also:

*[[Unified Customer Voice Portal]]
*[[Unified Customer Voice Portal#Unified_CVP_Component_Capacities_and_VM_Configuration_Requirements|Unified CVP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Unified Customer Voice Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CVP Call Server + VXML Server (co-located Call Server and VXML Server) (Media Server is optionally included depending on the conditions. See CVP co-residency section for detail)
| 4
| 4 GB
| 1x 146 GB
| 1
| Template Name: Cisco Unified CVP Call Server-VXML Server.ova
|-
! Unified CVP Reporting Server (Large)
| 4
| 4 GB
| Disk 1 - 72 GB, Disk 2 - 438 GB
| 1
| Template Name: Cisco Unified CVP Reporting Server.ova
|-
! Unified CVP Operations Console
| 2
| 2 GB
| 1x 20 GB
| 1
| Template Name: Cisco Unified CVP Operations Console.ova
|}

== Cisco MediaSense ==

See also:

*[[Virtualization for Cisco MediaSense]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco MediaSense OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco MediaSense'''
|-
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! CMS_6T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 146 GB (thick provisioning)
| 1
| rowspan="3" | Release 8.5(1)
|-
! CMS_12T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 300 GB (thick provisioning)
| 1
|-
! CMS_expansion_server_v8.5_vmv7
| 7 
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_12T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 150 GB (thick provisioning) 
| 1
| rowspan="4" | Release 8.5(2)
|-
! CMS_24T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 300 GB (thick provisioning) 
| 1
|-
! CMS_60T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 600 GB (thick provisioning) 
| 1
|-
! CMS_expansion_server_v8.5.2_vmv7
| 7
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_SRE_v8.5_vmv7
| 2
| 6 GB
| 2 x 80 GB (thick provisioning) 1 x 200 GB (thick provisioning) for Media storage
| 1 (with static MAC address)
| Release 8.5(4)
|}

== Cisco Unified Intelligence Center ==

See also:

*[[Cisco Unified Intelligence Center]]
*[[Cisco Unified Intelligence Center#Unified_IC_Component_Capacities_and_VM_Configuration_Requirements|Cisco Unified Intelligence Center OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Intelligence Center'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=282163829&flowid=5228&softwareid=283776220&release=8.0(3)&relind=AVAILABLE&rellifecycle=&reltype=latest CUIC (200 Reporting Users)]
| 4
| 6 GB
| 1x 146 GB
| 1
|
|}

== Cisco Unified Contact Center Management Portal ==

See also:

*[[Support for CCMP with UCCE on UCS Hardware|Cisco Unified Contact Center Management Portal]]
*[[Support for CCMP with UCCE on UCS Hardware#CCMP_Component_Capacities_and_VM_Configuration_Requirements|Unified CCMP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Management Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CCMP (1500 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (Web/App Srv Only) (8000 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (DB Only) (8000 Agents)
| 8
| 4 GB
| 1x 250 GB
| 1
| 
|}

== Cisco SocialMiner ==

See also:

*[[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613136&softwareid=283733464&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco SocialMiner OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco SocialMiner'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Standard Production Server
| 4
| 12 GB
| 1x 146 GB and 1x 256 GB
| 1
| 
|}

== Cisco Unfied Email Interaction Manager and Web Interaction Manager ==

  

Please review the SRND guidelines around agent count and throughput. This is absolutely necessary before identifying the appropriate OVA.

SRND can be found [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/cisco_interaction_manager/cim_441/design/cim441srnd.pdf here].

Read specifically section on “Determining Maximum Number of Emails Per Agent Per Hour” on page 50 and “Determining Maximum Number of Chats Per Agent Per Hour” on page 56

 

{| border="1" cellspacing="1" cellpadding="1"
|-
! scope="col" | Application, OVA Capacity and Notes+Download Link
! scope="col" | Contents
! scope="col" | No of VM's to deploy of each component
! scope="col" | vCPU
! scope="col" | vDisk
! scope="col" | vRAM/Memory
|-
| rowspan="2" | 100 Agents(All in One)
| Web Server
| 1
| 1
| 1 x 80GB
| 2
|-
| Application, Services Server ,File server Messaging Server and  Database server
| 1
| 4
| 1 x 150GB
| 4
|-
| rowspan="6" | 250 Agents
| Web Server
| 1
| 1
| 1 x 80GB
| 1
|-
| Application server
| 1
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Database Server
| 1
| 2
| 1 x 80 GB for OS, 1 x 200 GB for DB
| 4
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" | 500 Agents
| Web Server
| 2 
| 1
| 1 x 80GB
| 1
|-
| Application server
| 2
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 200 GB for DB
| 8
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" | 750 Agents
| Web Server
| 3
| 1
| 1 x 80GB
| 1
|-
| Application server
| 3
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 500 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" | 1000 Agents
| Web Server
| 4
| 1
| 1 x 80GB
| 1
|-
| Application server
| 4
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 8
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 500 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 1
| 1 x 80GB
| 1
|-
| rowspan="6" | 1250 Agents
| Web Server
| 5
| 1
| 1 x 80GB
| 1
|-
| Application server
| 5
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 8
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 500 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|}

 

 

  

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Shared Storage Considerations

2011-12-16T20:52:27Z

Sdurvasu: 1 revision

'''Go to: [[Before You Buy or Deploy - Considerations for Design and Procurement]]'''

'''Go to: [[QoS Design Considerations for Virtual UC with UCS]]''' 

----

 

= Compatible / Supported Storage Arrays (SAN, NAS) =

This section assumes you have already followed either the [[Tested Reference Configurations (TRC)]] or the [[Specification-Based Hardware Support]] policy for UC apps and compute hardware.

Storage arrays used with UC virtualization must align with the following:

*The storage solution must be supported by the Cisco Unified Computing System. For example, visit:
**[http://www.cisco.com/en/US/prod/ps10265/at_work_promo.html#~si Cisco UCS storage certification list]
**http://www.cisco.com/en/US/docs/unified_computing/ucs/interoperability/matrix/hw_sw_interop_matrix_seriesB_111.pdf for Cisco UCS B-Series servers or
**http://www.cisco.com/en/US/docs/unified_computing/ucs/interoperability/matrix/hw_sw_interop_matrix_seriesC_101.pdf for Cisco UCS C-Series servers.
*The storage solution must be supported by VMware ESXi / vSphere 4. For example, refer to the “SAN/Storage” tab at http://www.vmware.com/resources/compatibility/search.php?sourceid=ie7&rls=com.microsoft:en-us:IE-SearchBox&ie=&oe=
*The storage solution must meet Capacity (GB) and Performance (IOPS) requirements of UC VMs described later on this page.
*Otherwise any storage array vendor or product is supported for use with UC.
*In general, all other details, such as configuration of RAID or disk technology options on the storage array (such as choice of SAS, SATA or FC disks) are up to you. "Tier 1 Storage" is generally recommended for UC deployments.

No requirement to dedicate arrays or storage groups to UC (vs. non-UC), or to one UC app vs. other UC apps.

 

= Supported Storage for UCS Tested Reference Configurations =

[[Tested Reference Configurations (TRC)]] only support DAS (with specified RAID configurations), FC SAN and boot from FC SAN (diskless):

*FC SAN is mandatory for all UCS B200 Tested Reference Configurations
*FC SAN is optional for UCS C210 Tested Reference Configuration - see Supported Hardware page for which ones support FC SAN.
*UCS C200 Tested Reference Configurations are DAS only.
 

= Supported Storage for Specs-based Support =

[[Specification-Based Hardware Support]] supports DAS (with custom RAID configurations), NAS, SAN and boot from SAN (diskless) using NFS, FC, iSCSI and FCoE transport options.
* There is no UC-specific requirement for NFS version. Use what VMware and the server vendor recommend for the vSphere ESXi version required by UC.

 

== For UC on UCS '''C-series''' Specs-based ==

*SAN General : Design your deployment in accordance with the UCS High Availability guidelines (see [http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html]).
*FC:
**You must provision a dedicated HBA (see [[Tested Reference Configurations (TRC)]] page for more information).
**Your choice 
*FCoE, iSCSI, or NFS:
**UC requires provisioning a dedicated 10GbE ethernet port on the server to the upstream switch, using [http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/Virtualization/securecldg.html Cisco Platinum Class QOS] for the storage traffic. The port for storage access must be separate from the port used for LAN access. Whether the storage access port is on same adapter as LAN access is up to the customer. E.g. it may be desirable to have LAN and storage access on separate adapters for redundancy purposes, but UC does not require this.
**Normal QoS (L3 and L2 marking) can be used starting from the first upstream switch to the storage array
*The storage array vendor may have additional best practices as well.

 

== For UC on UCS '''B-series''' Specs-based ==

*SAN General : Design your deployment in accordance with the UCS High Availability guidelines (see [http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns944/white_paper_c11-553711.html]).
*FC or FCoE: No additional requirements for UC VM-to-storage traffic. The UCS 6100 switch handles this requirement by default. 
*iSCSI or NFS: Follow these best practices:
** Use a L2 CoS between the chassis and the upstream switch.
** For the storage traffic, recommend a [http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/Virtualization/securecldg.html Platinum class QoS, CoS=5, no drop (Fiber Channel Equivalent)]
** L3 DSCP is optional between the chassis and the first upstream switch.
** From the first upstream switch to the storage array, use the normal QoS (L3 and L2 marking). Note that iSCSI or NFS traffic is typically assigned a separate VLAN.
**iSCSI or NFS: Ensure that the traffic is prioritized to provide the right IOPS. For a configuration example, see the FlexPod Secure Multi-Tenant (SMT) documentation  ([http://www.imaginevirtuallyanything.com/us/ http://www.imaginevirtuallyanything.com/us/]).
*The storage array vendor may have additional best practices as well.

 

= Capacity and Performance Requirements of Storage Solution =

Storage capacity must support the sum of UC VM OVA vDisks, plus overhead for VMware and RAID on the array.

Storage performance must support the sum of UC VM OVA IOPS, documented in the [[IO Operations Per Second (IOPS)]] page (this may result in storage configurations with excess storage capacity due to extra disks/spindles added for higher maximum IOPS). IOPS utilization should be monitored for each application to ensure that the aggregate IOPS is not exceeding the capacity of the array. Prolonged buffering of IOPS against an array may result in degraded system performance and delayed reporting data availability.

Cisco UC uses a 4 kilobyte block size to determine bandwidth needs.

Disk oversubscription is not supported. Storage thin provisioning is not supported (neither at the VM level nor at the array level) and does not result in storage capacity savings. While use of thin provisioning does not impose a VM performance penalty, many UC VMs are designed to fully utilize their allocated vDisk storage for critical operations (such as upgrades or backups) or application-specific functions (such as the Cisco Unity Connection message store). Also, running out of capacity at a critical moment could lock up all UC VMs on the same LUN.

EMC-based storage solutions may use EMC PowerPath/VE multi-pathing (for details, see [http://www.emc.com/products/family/powerpath-family.htm http://www.emc.com/products/family/powerpath-family.htm]). 

== SAN/NAS Link Provisioning and High Availability ==

Consider the following example to determine the number of physical Fiber Channel (FC) or 10Gig Ethernet links required between your storage array (such as the EMC Clariion CX4 series or NetApp FAS 3000 Series) and SAN switch for example, Nexus or MDS Series SAN Switches), and between your SAN switch and the UCS Fabric Interconnect Switch. This example is presented to give a general idea of the design considerations involved. You should contact your storage vendor to determine the exact requirement.

Assume that the storage array has a total capacity of 28,000 Input/output Operations Per Second (IOPS). Enterprise grade SAN Storage Arrays have at least two service processors (SPs) or controllers for redundancy and load balancing. That means 14,000 IOPS per controller or service processor. With the capacity of 28,000 IOPS, and assuming a 4 KByte block size, we can calculate the throughput per storage array controller as follows:

*14,000 I/O per second * (4000 Byte block size * 8) bits = 448,000,000 bits per second
*448,000,000/1024 = 437,500 Kbits per second
*437,500/1024 = ~428 Mbits per second

Adding more overhead, one controller can support a throughput rate of roughly 600 Mbps. Based on this calculation, it is clear that a 4 Gbps FC interface is enough to handle the entire capacity of one Storage Array. Therefore, Cisco recommends putting four FC interfaces between the storage array and storage switch, as shown in the following image, to provide high availability.

[[Image:254783.jpg]]

{{note| Cisco provides storage networking and switching products that are based on industry standards and that work with storage array providers such as EMC, NetApp, and so forth. Virtualized Unified Communications is supported on any storage access and storage array products that are supported by Cisco UCS and VMware. For more details on storage networking, see [http://www.cisco.com/en/US/netsol/ns747/networking_solutions_sub_program_home.html http://www.cisco.com/en/US/netsol/ns747/networking_solutions_sub_program_home.html].}} 

== Best Practices for Storage Array LUNs for Unified Communications Applications ==

There are various ways to create partitions or Logical Unit Numbers (LUNs) in the storage array to meet the IOPS requirement for Cisco Unified Communications applications (see [[IO Operations Per Second (IOPS)]]}.

The best practices mentioned below are meant only to provide guidelines. Data Center storage administrators should carefully consider these best practices and adjust them based on their specific data center network, latency, and high availability requirements.

The storage array Hard Disk Drive (HDD) must be a Fibre Channel (FC) class HDD. These hard drives could vary in size. The current most popular HDD (spindle) sizes are:

*450 GB, 15K revolutions per minute (RPM) FC HDD
*300 GB, 15K RPM FC HDD

Both types of HDD provide approximately 180 IOPS. Regardless of the hard drive size used, it is important to try to balance IOPS load and disk space usage.

LUN size must be less than 2 terabytes (TB) for the virtual machine file system to recognize it. For Cisco Unified Communications virtual applications, the recommendation is to create a LUN size of between 500 GB and 1.5 TB, depending on the size of the disk and RAID group type used. Also as a best practice, select the LUN size so that the number of Unified Communications virtual machines per LUN is between 4 and 8. Do not allocate more than eight virtual machines (VMs) per LUN or datastore. The total size of all Virtual Machines (where total size = VM disk + RAM copy) must not exceed 90% of the capacity of a datastore.

LUN filesystem type must be VMFS. Raw Device Mapping (RDM) is not supported.

The following example illustrates an example of these best practices for UC:

For example, assume RAID5 (4+1) is selected for a storage array containing five 450 GB, 15K RPM drives (HDDs) in a single RAID group. This creates a total RAID5 array size of approximately 1.4 TB usable space. This is lower than the total aggregate disk drive storage space provided by the five 450 GB drives (2.25 TB). This is to be expected because some of the drive space will be used for array creation and almost an entire drive of data will be used for RAID5 striping.

Next, assume two LUNs of approximately 720 GB each are created to store Unified Communications application virtual machines. For this example, between one and three LUNs per RAID group could be created based on need. Creating more than three LUNs per RAID group would violate the previously mentioned recommendation of a LUN size of between 500 GB and 1.5 TB.

A RAID group with RAID 1+0 scheme would also be valid for this example and in fact in some cases could provide better IOPS performance and high availability when compared to a RAID 5 scheme.

The above example of storage array design should be altered based on your specific Unified Communications application IOPS requirements.

Below is a graphic of an example configuration following these best practices guidelines, note there are other designs possible.

 

[[Image:docwiki_SAN_best_practices.png]] 

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255, 215, 0);" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Specification-Based Hardware Support

2011-12-16T20:52:26Z

Sdurvasu: 1 revision

'''Go to:  '''[[Guidelines to Edit UC Virtualization Pages|'''Guidelines to Edit UC Virtualization Pages''']]

== Specs-Based Hardware Requirements for running Cisco Unified Communications on Supported Versions of VMware vSphere ESXi ==

== Introduction ==

Cisco supports [[Unified Communications VMWare Requirements|running UC applications on certain versions of VMware vSphere ESXi]]. Customers may choose one of two different support models for compute, network and storage hardware.

*'''Tested Reference Configurations (TRC)''':
<blockquote>Select hardware configurations tested and documented for specific guaranteed performance, capacity and application co-residency scenarios running "full-load" UC VMs. Intended for customers who want a packaged solution from Cisco that is pre-engineered for a specific deployment scenario and/or customers who are not sufficiently experienced with hardware virtualization. See [[Tested Reference Configurations (TRC)]] for more information. </blockquote>
*'''Specs-Based VMware Hardware Support''':
<blockquote>A flexible support policy described in the remainder of this document. Intended for customers with '''''extensive expertise''''' in virtualization and server/storage sizing who wish to use their own hardware standards. This hardware has not been directly tested or documented by Cisco UC, but meets certain specifications for which UC applications are supported. Performance is not guaranteed, but the Tested Reference Configurations may be used for guidance when sizing hardware. ''Important:'' Customers who choose this option are responsible for sufficiently sizing hardware to meet UC VM performance needs at the level of load deployed. Customers are also responsible for resolving performance problems by adjusting either the hardware configuration or the VM deployment model. '''Cisco is not responsible for performance problems resulting from use of specs-based support when the problem can be resolved by deployment changes such as migrating the virtual machine to a faster hardware platform, powering off or migrating some of the other virtual machines to a different physical server, or splitting up a dense UC VM into multiple less dense UC VMs on different physical servers.''' It is recommended to use the Tested Reference Configurations for guidelines on hardware sizing. Deploying specs better than TRC "should" provide better performance, but should be verified as not guaranteed. Deploying specs worse than TRC "should" provide worse performance, but is not guaranteed. Use of a processor with slower speed than the Tested Reference Configurations is not supported as the deployment will have unknown and unspecified reduction in capacity/performance.
</blockquote>
Customers who require maximum flexibility and are proficient with virtualization, including the above support implications, should use Specs-based VMware Hardware support. Customers who require a simplified solution with guaranteed performance, and who lack experience with virtualization, should use Tested Reference Configurations. 

The following are identical regardless of the support model chosen:

*Virtual machine (OVA) requirements
*VMware product, version and feature support
*VMware configuration requirements for UC
*Application/VM Co-residency policy (specifically regarding application mix, 3rd-party support, reservations, oversubscription). Max VM count per server with specs-based depends on the physical server configuration and the OVAs deployed. E.g. UCS C210 M2 TRC#1 deployed with multiple CUCM 7.5K user OVAs can support 4:1. If specs-based was used with a supported dual 6-core CPU and appropriate increases in memory and storage, the same server model running multiple CUCM 7.5K user OVAs could support 6:1.

 The remainder of this document defines the requirements of the specs-based policy.

== VMware vSphere and vCenter Requirements ==

Supported VMware products, versions and features under this specs-based policy are the same as with the TRCs (Tested Reference Configurations), and are detailed [[Unified Communications VMWare Requirements|here]].

'''VMware vCenter is a required component in any deployment using this specs-based policy. '''

Configuring vCenter to capture detailed logs, as shown in Figure 1 below, is strongly recommended. If not configured by default, Cisco TAC may request enabling these settings in order to troubleshoot problems. It is a requirement that the customer deployment of vCenter be able to capture Statistics Level 4 for all statistics levels for the maximum duration at each level.

 

=== Figure 1 ===

[[Image:VCenter SS.jpg]]

 

== Server Vendors ==

The only supported server vendors are:
* Cisco Unified Computing System
* HP
* IBM

The following are NOT supported:
* Cisco MCS 7800
* Cisco UCS Express on ISR/SRE-V hardware
* Any other 3rd-party server vendor, such as Dell, Fujitsu, Oracle/Sun
 

== Server Models and Generations ==

Any model/generation of any form factor (rack, blade) may be used as long as it complies with the following:
* The server is from one of the supported vendors above
* The server is on the [http://www.vmware.com/go/hcl VMware Hardware Compatibility List] for the version of VMware vSphere ESXi required by UC.
* The server uses a processor supported by UC (described later in this document). Note that your server model choices may be artificially limited by server's processor options vs. the list of what processors UC supports, i.e. not because of the model itself but because of the CPU.
* The server's configuration satisfies all other criteria of this policy.

With this specs-based policy, support is not about the server model per se, but rather the server vendor and the processor used.
 

== Processor Requirements ==

Note that processor support varies by UC application. See the [[Unified Communications Virtualization Supported Applications | Supported Applications matrix]] for the UC apps in your deployment.

The following processor models are supported:
* Intel Xeon 5600 family with minimum physical core speed of 2.53 GHz
* Intel Xeon 7500 family with minimum physical core speed of 2.53 GHz
* Intel Xeon E7-2800 family with minimum physical core speed of 2.4 GHz
* Intel Xeon E7-4800 family with minimum physical core speed of 2.4 GHz
* Intel Xeon E7-8800 family with minimum physical core speed of 2.4 GHz
* CPU models in these families with slower physical core speeds are not supported due to undefined capacity/performance relative to Tested Reference Configurations. UC is sensitive to both the CPU speed and the CPU architecture. Most industry CPU benchmarks do not correlate well with UC application behavior, so "newer" or "faster" does not guarantee "better for UC".

The following processors are NOT supported:
* Intel processor families not on the above list, such as Intel Xeon 6500. These are not supported at this time.
* Other processor vendors such as AMD are not supported.

Total physical core count required is based on the [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|sum of UC virtual machine core requirements]] and the [[Unified Communications Virtualization Sizing Guidelines|co-residency support policy]]. Per these policies, recall that physical CPU cores may not be over-subscribed for UC VMs (one physical CPU core = one VM vCPU core).

Cisco TAC will not troubleshoot performance problems in deployments with insufficient physical processor cores or speed.

 

== RAM ==

Minimum physical RAM required is 2GB for ESXi plus the [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|sum of UC virtual machines' vRAM]].

Recall that physical memory may not be over-subscribed for UC VMs. UC therefore does not require a minimum DIMM speed.

UC does not mandate memory hardware module size, density, speed or quantity - follow server vendor requirements for memory hardware configuration (here is an example for Cisco UCS: http://www.cisco.com/en/US/docs/unified_computing/ucs/hw/chassis/install/blade.html#wp1035302).

Cisco TAC will not troubleshoot performance problems in deployments with insufficient physical RAM.

 

== IO Adapters, Controllers and Devices for LAN Access and Storage Access ==

All adapters used must be on the [http://www.vmware.com/go/hcl VMware Hardware Compatibility List] for the version of vSphere ESXi required by UC.

Only the following I/O Devices are supported:

*HBA
**FC – 2Gbps or faster
**InfiniBand
*NIC
**Ethernet – 1Gbps or faster
**NFS and iSCSI are supported for network storage access - 10Gbps or faster, plus see requirements below
*Cisco VIC or 3rd-party Converged Network Adapter
**FCoE supported for converged Ethernet and network storage access - 10Gbps or faster, plus see requirements below
*RAID Controllers for DAS
**SAS
**SAS SATA Combo
**SAS-RAID
**SAS/SATA-RAID
**SATA

The customer is also responsible for configuring redundant devices on the server (e.g. redundant NIC, CNA, HBA or VIC adapters).

There are no UC restrictions on hardware vendors for I/O Devices other than that VMware and the server vendor/model must be compatible with them and support them

Cisco TAC will not troubleshoot performance problems in a deployment designed with insufficient or overloaded I/O devices.

 

== Storage Hardware and Performance ==

*The '''kernel disk command latency''' must not be greater than 2-3 ms and the '''physical device command latency''' must not be greater than 15-20 ms. When either of these metrics is not met, Cisco considers the storage system inadequate to serve the UC virtual machines. Cisco will not troubleshoot performance problems in an environment where either metric is not being met.

*Additionally, each UC VM OVA has a published IOPS and virtual disk space requirement. It is the responsibility of the customer to provide a storage system that exceeds total vDisk (see [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]] and average IOPS requirements (see [[IO Operations Per Second (IOPS)]]) of the UC virtual machines they will be running on that storage system. It is not necessary to configure the storage system for peak simultaneous IOPS of every virtual machine, but the customer should be aware of excess capacity to avoid over-extending the system (e.g. by upgrading every virtual machine at the same time causing an IOPS spike).

*The storage solution must follow all storage capacity, performance and QoS requirements in [[Shared Storage Considerations]] here.

* Otherwise the following are supported: DAS, NAS, SAN and boot from SAN (diskless) with NFS, FC, iSCSI and FCoE transport options. Note that diskless servers are only supported if all UC apps on the physical server / ESXi host support both vSphere ESXi 4.1 and the VMware "boot from SAN" feature (see the [[Unified Communications VMWare Requirements|VMware Requirements page]]).

* See the [[Shared Storage Considerations]] for an illustration of a best practices SAN/NAS array configuration for UC (using five 300-450 GB 15K rpm SAS or FC drives in a RAID 5 configuration, LUN size of 500 GB to 1.5 TB, <8-10 UC VMs per LUN).

Cisco TAC will not troubleshoot performance problems in a deployment designed with insufficient or overloaded storage hardware.

 

== Mechanical & Environmental Components ==

UC apps have no dependencies on form factor, rack mounting hardware, cable management hardware or power supplies. Redundant power supplies are strongly recommended for high availability. 

 

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255, 215, 0);" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Tested Reference Configurations (TRC)

2011-12-16T20:52:22Z

Sdurvasu: 1 revision

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

== Introduction ==

This web page describes supported compute, storage and network hardware for Virtualization of Cisco Unified Communications using Tested Reference Configurations (TRCs). If you want to use different hardware configurations, follow the [[Specification-Based Hardware Support|"Specs-based VMware Support" Policy here]].

For more details on Cisco UCS servers in general, see the Related Hardware Documentation section below.

Ensure your deployment follows all the [[High-level Checklist for Design and Implementation|design and procurement rules here]].

See [[High-level Checklist for Design and Implementation|procurement considerations here]] for hardware purchase options. Cisco part numbers [http://www.cisco.com/go/swonly are described here]

== What does a Tested Reference Configuration (TRC) cover? ==

TRCs are intended for these types of customers:
* lower levels of virtualization proficiency
* require guaranteed UC app virtual machine performance when the solution elements under Cisco UC's control are configured correctly per UC support policy
* desire Cisco to handle hardware sizing, determining hardware specs and translating those specs into a hardware parts list to ensure the above guarantee
* are willing to accept as tradeoffs for the guarantee less choices for hardware and less choices for virtual machine deployment options.

If a customer requires more flexibility AND they are highly virtualization-proficient AND they are comfortable owning hardware sizing/specs/parts determination AND they are comfortable owning performance assurance, they can instead follow the [[Specification-Based Hardware Support|"Specs-based VMware Support" Policy here]].

TRCs ''do'' cover the following:
* Definition of hardware specs down to the UCS part number level
* DAS/RAID options to use when DAS is part of the definition
* Expectations for supportable virtual machine quantity / size mix, with virtual machines at full load, based on UC sizing rules and co-residency support policy

TRCs do ''not'' cover the following:
* Configuration of solution elements outside Cisco UC's control, such as SAN/NAS-attached storage arrays.
* Configuration settings or step by step procedures for hardware BIOS, firmware, drivers, RAID options
* Configuration settings, patch recommendations or step by step procedures for VMware (use UCS and VMware best practices subject to UC support policy rules)
* Configuration settings or step by step procedures for QoS parameters, virtual-to-physical network mapping or adapters (these will vary by deployment - use UCS and VMware best practices subject to UC support policy rules) 

== Hardware Requirements for Tested Reference Configurations (TRCs) ==

 

To be considered a Tested Reference Configuration (TRC) for support purposes, follow the policy below. '''NOTE: any deviation from policy below is no longer a Tested Reference Configuration and you must follow the [[Specification-Based Hardware Support|"Specs-based VMware Support" Policy here]].'''

*Server model and generation must exactly match table below.

*Physical CPU quantity, CPU model and physical cores per CPU must exactly match table below.

*Total physical Memory/RAM must be same or higher than in table below. Must follow Cisco UCS best practices for memory module density, quantity and speed - no UC-specific requirements on memory configuration other than total RAM.

*Physical/Local/DAS Storage
**Disk quantity must exactly match table below.
**Disk size (e.g. 146GB) must be same or higher than table below for UCS C-Series. For UCS B-series, any disk size may be used.
**Disk speed (e.g. 10k RPM vs. 15k RPM) must be same or higher than table below for UCS C-Series. For UCS B-Series, any disk speed may be used.
**Disk technology (e.g. SAS) must exactly match table below.
**RAID Controller Card and battery backup must exactly match table below and [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html parts lists here].
**RAID configuration, including physical-to-logical volume mapping, must exactly match table below and RAID instructions in the document [http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/virtual/servers.html Installing CUCM on Virtual Servers here].

*Shared Storage (SAN)
**SAN transport must be Fibre Channel. Tested Reference Configurations are not provided for other shared storage options (iSCSI, FCoE, NFS). To use these other options, follow the [[Specification-Based Hardware Support|"Specs-based VMware Support" Policy here]].
**Local disks on UCS B-Series are only used to host/boot VMware. UC apps must host/boot from Fibre Channel SAN. Certain UC apps also support diskless servers for boot from FC SAN.
**Local disks on UCS C-Series DAS-only TRCs are used to host/boot VMware and UC apps.
**Local disks on UCS C-Series TRCs with HBA are only used to host/boot VMware. UC apps must host/boot from Fibre Channel SAN. Certain UC apps also support diskless TRC's for boot from FC SAN.

*Adapters for network and storage access (NIC, HBA, CNA, VIC)
**UCS B-Series may use the mezzanine adapter in table below, or any other supported mezzanine adapter. Which adapter "should" be used is dependent on deployment, design and UC apps.
**UCS C-Series NIC and HBA must exactly match adapters in table below. Other NIC, HBA, CNA or VIC options are not included in Tested Reference Configurations - follow [[Specification-Based Hardware Support|"Specs-based VMware Support" Policy here]].

*Redundant Power supplies on UCS C210 TRCs are highly recommended. UCS C200 TRCs for Business Edition 6000 only ship with one, but a second can be added as separate spare if desired.

*Rack-mounting hardware on UCS C-Series: It is strongly recommended that you keep the Cisco default rail kit, unless you have different rack types such as telco racks or racks proprietary to another server vendor. The Cisco default cable management hardware does not ship with TRCs but can be added as a separate spare. Cisco does not sell any other types of rack-mounting hardware; you must purchase such hardware from a third party.

*Local DVD drive on UCS C-Series: It is strongly recommended that you keep a local DVD drive when the server model supports it and the TRC includes it; otherwise certain customer procedure options for installation and upgrading cannot be supported.

 

{| border="1"
|-
! Base Server Model and Generation
! Tested Reference Configuration (TRC)
! CPU
! RAM
! Storage
! Adapters
! Notes

|-
! [[UC Applications on Cisco UCS B-Series Blade Servers|UCS B230 M2 Blade Server]]
| TRC #1
| Dual E7-2870 (2.4 GHz, 20 total physical cores available to apps)
| 96GB (12x8GB, after ESXi 94 GB total physical RAM available to apps)
| Diskless - FC SAN for VMware and UC apps
| Cisco VIC
| UCS-B230M2-VCDL1

|-
! [[UC Applications on Cisco UCS B-Series Blade Servers|UCS B440 M2 Blade Server]] (full-width)
| TRC #1
| Quad E7-4870 (2.4 GHz, 40 total physical cores available to apps)
| 256GB (16x16GB, after ESXi 254 GB total physical RAM available to apps)
| Diskless - FC SAN for VMware and UC apps
| Cisco VIC
| UCS-B440M2-VCDL1

|-
! rowspan="2" | [[UC Applications on Cisco UCS B-Series Blade Servers|UCS B200 M2 Blade Server]]
| TRC #1
| Dual E5640 (2.66 GHz, 8 total physical cores available to apps)
| 48GB (12x4GB, after ESXi 46 GB total physical RAM available to apps)
|
*DAS (RAID1) for VMware
*FC SAN for UC apps
| Cisco VIC
| UCS-B200M2-VCS1
|-
| TRC #2
| Dual E5640 (2.66 GHz, 8 total physical cores available to apps)
| 48GB (12x4GB, after ESXi 46 GB total physical RAM available to apps)
| Diskless - FC SAN for VMware and UC apps
| Cisco VIC
| Sold as Cisco Data Center SKUs only
|-
! rowspan="2" | [[UC Applications on Cisco UCS B-Series Blade Servers|UCS B200 M1 Blade Server ]]
| TRC #1
| Dual E5540 (2.53 GHz, 8 total physical cores available to apps)
| 36GB (6x2GB+6x4GB, after ESXi 34 GB total physical RAM available to apps)
|
*DAS (RAID1) for VMware
*FC SAN for UC apps
| 3rd-party CNA
| UCS-B200M1-VCS1
|-
| TRC #2
| Dual E5540 (2.53 GHz, 8 total physical cores available to apps)
| 36GB (6x2GB+6x4GB, after ESXi 34 GB total physical RAM available to apps)
| Diskless - FC SAN for VMware and UC apps
| 3rd-party CNA
| Sold as Cisco Data Center SKUs only
|-
! rowspan="3" | [[UC Applications on Cisco UCS C210 Rack-Mount Servers|UCS C210 M2 General-Purpose Rack-Mount Server]]
| TRC #1
| Dual E5640 (2.53 GHz, 8 total physical cores available to apps)
| 48GB (12x4GB, after ESXi 46 GB total physical RAM available to apps)
|
*DAS (2 disks RAID1) for VMware
*DAS (8 disks RAID5) for UC apps
:* 947 GB available to apps after RAID/VMFS overhead, not counting VM overhead
| 1GbE NIC
| UCS-C210M2-VCD2
|-
| TRC #2
| Dual E5640 (2.66 GHz, 8 total physical cores available to apps)
| 48GB (12x4GB, after ESXi 46 GB total physical RAM available to apps)
|
*DAS (2 disks RAID1) for VMware
*FC SAN for UC apps
| 1GbE NIC and 4G FC HBA
| Sold as Cisco Data Center SKUs only
|-
| TRC #3
| Dual E5640 (2.66 GHz, 8 total physical cores available to apps)
| 48GB (12x4GB, after ESXi 46 GB total physical RAM available to apps)
| Diskless - FC SAN for VMware and UC apps
| 1GbE NIC and 4G FC HBA
| Sold as Cisco Data Center SKUs only
|-
! rowspan="4" | [[UC Applications on Cisco UCS C210 Rack-Mount Servers|UCS C210 M1 General-Purpose Rack-Mount Server]]
| TRC #1
| Dual E5540 (2.53 GHz, 8 total physical cores available to apps)
| 12GB (6x2GB, after ESXi 10 GB total physical RAM available to apps)
|
*DAS (2 disks RAID1) for VMware
*DAS (4 disks RAID5) for UC apps
| 1GbE NIC
| UCS-C210M1-VCD1 (note: only supports a single Virtual Machine)
|-
| TRC #2
| Dual E5540 (2.53 GHz, 8 total physical cores available to apps)
| 36GB (6x2GB+6x4GB, after ESXi 34 GB total physical RAM available to apps)
|
*DAS (2 disks RAID1) for VMware
*DAS (8 disks RAID5) for UC apps
:*947 GB available to apps after RAID/VMFS overhead, not counting VM overhead
| 1GbE NIC
| UCS-C210M1-VCD2
|-
| TRC #3
| Dual E5540 (2.53 GHz, 8 total physical cores available to apps)
| 36GB (6x2GB+6x4GB, after ESXi 34 GB total physical RAM available to apps)
|
*DAS (2 disks RAID1) for VMware
*FC SAN for UC apps
| 1GbE NIC and 4G FC HBA
| Sold as Cisco Data Center SKUs only
|-
| TRC #4
| Dual E5540 (2.53 GHz, 8 total physical cores available to apps)
| 36GB (6x2GB+6x4GB, after ESXi 34 GB total physical RAM available to apps)
| Diskless - FC SAN for VMware and UC apps
| 1GbE NIC and 4G FC HBA
| Sold as Cisco Data Center SKUs only
|-
! [[UC Applications on Cisco UCS C200 Rack-Mount Servers|UCS C200 M2 General-Purpose Rack-Mount Server]]
| TRC #1
| Dual E5506 (2.13 GHz, 8 total physical cores available to apps)
| 24GB (6x4GB, after ESXi 22 GB total physical RAM available to apps)
|
*DAS (4 disks RAID10) for VMware + UC apps
:*1.8 TB available to apps after RAID/VMFS overhead, not counting VM overhead
| 1GbE NIC
| UCS-C200M2-VCD2/BE6K/WL8/VCD2BE (note: only scaled for <1K users depending on UC app)
|}

== Related Hardware Documentation ==

==== BIOS, Firmware, Drivers and UCS Software versions ====

There are no direct support requirements for particular versions of any of these items for Cisco UC apps.

Cisco UC apps will specify supported VMware versions and supported server models. Customers should use latest recommended BIOS, firmware, drivers and UCS / UCS Manager Software versions that are compatible with the UC-supported VMware version on the server model being used.

 

==== Monitoring and Alarming for Cisco UCS ====

At this time on Cisco UCS, certain types of serviceability monitoring and alarming (such as hard drive failure) are only available via OS instrumentation. For UC on TRCs or UCS specs-based hardware, this means alerts are generated by VMware in CIM format, and require VMware vCenter or equivalent CIM-compliant console. Refer to the [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/utilities/raid/reference/guide/ucs_raid_smis_reference.html ''UCS RAID Controller SMI-S Reference Guide''] for detailed information on this topic.

=== Related Hardware Documentation ===

For installation and configuration information on UCS servers, refer to the documentation roadmap for either the B-Series or C-Series servers:

*[http://www.cisco.com/go/unifiedcomputing/b-series-doc Cisco UCS B-Series Servers Documentation Roadmap]
*[http://www.cisco.com/go/unifiedcomputing/c-series-doc Cisco UCS C-Series Servers Documentation Roadmap]
*[http://www.cisco.com/en/US/products/ps10739/tsd_products_support_series_home.html Cisco UCS C-Series Integrated Management Controller Documentation]
*[http://www.cisco.com/en/US/products/ps10281/tsd_products_support_series_home.html Cisco UCS Manager Documentation]
*[http://www.cisco.com/go/ucs Cisco UCS home page]
*[http://www.cisco.com/go/uconucs UC on UCS solution home page]
*[http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html Part Number lists for Tested Reference Configurations]

 

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255, 215, 0);" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications VMware Requirements

2011-12-16T20:52:21Z

Sdurvasu: 1 revision

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

This article describes VMware requirements, feature support, and services and support contracts for virtualized Unified Communications applications.

== Introduction: Mandatory VMware Products and Services ==

'''Note:''' This page only covers VMware product/version/feature support.

:*It does '''not''' cover compute/network/storage hardware support policy for UC virtualization.
:*It does '''not''' cover application co-residency support policy for UC virtualizatoin.
:*See other links at http://www.cisco.com/go/uc-virtualized for these details.

 

'''VMware vSphere ESXi is mandatory''' for UC virtualization and UC on UCS.

:*UC is only supported on UCS servers with VMware vSphere ESXi.
:*See rest of this page for other details on VMware product, version and feature support.
:*'''Nonvirtualized, physical, or bare-metal installations are not supported''' for UC on UCS.

 

'''VMware vCenter''' is:

:*'''Mandatory''' for all Specs-based deployments
:*'''Optional''' for Tested Reference Configuration deployments.

 

For UC on UCS, VMware vSphere ESXi and vCenter may be purchased from Cisco or customer provided. For specs-based with HP/IBM, all VMware software must be customer-provided. See [[Before You Buy or Deploy - Considerations for Design and Procurement]] for information on VMware purchase options. 

Compatibility of UC apps/versions with VMware vSphere ESXi versions varies by UC app and is outlined later in this document. See the following links for details on "legacy" virtualization support (i.e. 7.x of UC apps with VMware vSphere on limited 3rd-party servers):

:*[http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html Cisco Unity Virtualization Design Guide]
:*[http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_7_5/user/guide/VirtualizationGde753.pdf Virtualization Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted 7.5(3)]

 

'''Note:''' in all cases, the customer is required to have a valid service contract (either with Cisco or with VMware, depending on what/how purchased) to be supported. See [[#Services_and_Support_Contracts_for_VMware_are_Required|Services and Support Contracts for VMware are Required]] for how to ensure this is done for different Editions of Vmware vSphere ESXi. 

== Supported Virtualization Hypervisor Vendors ==

At this time, the only vendor supported for UC is VMware.

Other vendors/products - such as Microsoft Hyper-V, Citrix Xen, Red Hat KVM - are not supported for Cisco UC virtualization. 

== Supported VMware Products ==

VMware vSphere ESXi is required for Cisco UC virtualization.

*ESX and ESXi are architecture options for VMware vSphere ([http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html click here for a comparison]). UC only supports ESXi. Recall that vSphere 3.x and 4.x offered both options, but 5.0+ only offers ESXi.
*VMware vSphere ESX, regardless of version, is not supported for UC. This is due to technical reasons and [http://blogs.vmware.com/vsphere/2010/07/esx-41-is-the-last-esx-what-do-i-do-now.html VMware’s direction to transition from ESX to ESXi]. Note a VMware ESX cluster can contain VMware ESXi servers running Cisco Unified Communications.
*No other VMware server virtualization products are supported.

 

== Supported Versions of VMware vSphere ESXi ==

The minimum version for VMware vSphere ESXi is 4.0. But note a higher minimum version may be required depending on what UC apps/versions you run (see tables below) and what hardware you select.

*Note that use of VMware vSphere ESXi 4.1 requires [[Disable LRO|'''disabling the "LRO" setting as described here''']].
*Versions of VMware vSphere ESXi prior to 4.0 are not supported due to technical reasons.
*Each UC app/version will specify the required compatible Major Releases and Minor Releases of VMware vSphere ESXi (e.g. 4.0 or 4.1) in the tables below.
**Unlisted Major/Minor versions are not supported.
**Unless otherwise indicated, the base Major/Minor version shown is the minimum required.
**Some UC apps will also require a minimum Maintenance Release and will indicate if this is the case. Otherwise UC does not specify or recommend patches, updates or Maintenance Releases (e.g. 4.0 U1) for a required Major/Minor Release of vSphere ESXi. Follow recommendations of the server vendor and VMware for what you should use. Unless otherwise indicated by a UC app, UC supports all VMware vSphere ESXi patches, updates and Maintenance Releases for a supported Major/Minor Release at time of VMware launch as long as the server vendor supports them.

 

=== VMware vSphere ESXi Version Support for Call Processing and System Management Applications ===

{| class="wikitable FCK__ShowTableBorders"
|-
!
Application 

! VMware vSphere ESXi 4.0 
! VMware vSphere ESXi 4.1 
! VMware vSphere ESXi 5.0 
|-
| Unified Communications Manager (Unified CM)
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
| Not supported
|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Cisco Emergency Responder (CER)
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Session Manager Edition (SME)
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Unified Attendant Consoles
| 8.0(3)+, 8.5+
| 8.6+
| Not supported
|-
| UC Management Suite (OM, SM, SSM, PM)
| 7.1 and later
| 7.1 and later
| Not supported
|-
| Cisco Intercompany Media Engine (CIME)
| Not supported
| 8.6(2)+
| Not supported
|}

=== VMware vSphere ESXi Version Support for Messaging and Presence Applications ===

{| style="width: 812px; height: 108px" class="wikitable FCK__ShowTableBorders"
|-
! Application 
! VMware vSphere ESXi 4.0 or 4.0 Update 1 
! VMware vSphere ESXi 4.1
|-
| Cisco Unity Connection
| 8.0(2) and later
| 8.0(3) and later
|-
| Cisco Unity
| 7.x and later
| 7.x and later
|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
| 8.0(2) and later
| 8.0(2) and later
|}

 

=== VMware vSphere ESXi Version Support for Contact Center Applications ===

{{Note| For Virtual Machines that need '''more than 4 vCPUs''', the VMware vSphere ESXi '''Enterprise Plus''' licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)}}

{| style="width: 816px; height: 396px" class="wikitable FCK__ShowTableBorders"
|-
! Application
! VMware vSphere ESXi 4.0 and 4.0 Updates
! VMware vSphere ESXi 4.1  and 4.1 Updates
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]]
| 8.0(2) and later or 8.5(1) and later
| 8.0(2) SU2 and later or 8.5(1) and later
|-
| [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Work Force Optimization (WFO), Quality Management (QM),and Work Force Management (WFM)]
| 8.5(1) and later
| 8.5(2) and later
|-
| [[Unified Contact Center Enterprise]] 
| ESXi 4.0 Update 1 (minimum required). See below
| See below
|-
| - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tools
| 8.0(2) and later or 8.5(1) and later
| 8.0(2) and later or 8.5(1) and later
|-
| [[Virtualization for Unified Intelligence Center|Cisco Unified Intelligence Center]] 
| 8.0(3) and later
| 8.5(2) and later
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]
| 8.0(2) and later or 8.5(1) and later
| 8.0(2) and later or 8.5(1) and later
|-
| [[Unified Customer Voice Portal]] (all components) 
| 8.0(1) and later or 8.5(1) and later
| 8.0(1) and later or 8.5(1) and later
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| 8.5(1) and later
| 8.5(2) and later
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| 8.5(1) and later
| 8.5(1) and later
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Unified Email Interaction Manager and Web Interaction Manager]]
| 4.3(2) and later
| 4.3(2) and later
|}

== Support of Cisco VN-Link and Cisco Nexus 1000V ==

Note that Cisco Unified Contact Center Enterprise does NOT support this – see [[UCS Network Configuration for UCCE|UCS Network Configuration for Unified CCE]].

Unless otherwise indicated above, Cisco VN-Link, Cisco Nexus 1000V, Cisco Nexus 1010, and VM-FEX are supported by UC applications that support the VMware vNetwork Distributed Switch (see [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]).

Cisco VN-Link, Cisco Nexus® 1000V, Cisco Nexus 1010, VM-FEX and VMware vNetwork Distributed Switch all require VMware ESXi Enterprise Plus Edition (see [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]). Other editions do not support these capabilities.

For UC on UCS B-series, Cisco UCS 6100 does not currently support Layer 3 to Layer 2 COS markings. Additionally, the UC applications and operating systems cannot set the Layer 2 COS markings. Use of Cisco Nexus® 1000V is therefore strongly recommended as this is the only way to manage traffic congestion through the current UCS 6100. Please recall that traffic congestion risk will vary and is dependent on many factors such as UC vs. non-UC virtual machine count and their traffic characteristics across all blades, chassis and fabric extenders connected to the same UCS 6100.

For UC on UCS C-series, Cisco Nexus® 1000V is recommended but not mandatory as there is no intermediate UCS 6100 to design around.

For more information on Cisco VN-Link, Cisco Nexus 1000V and VM-FEX, see the following:
:* http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns892/ns894/white_paper_c11-525307.html
:* http://www.cisco.com/en/US/products/ps9902/index.html
:* http://www.cisco.com/en/US/netsol/ns1124/index.html

== Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client ==

 '''VMware vSphere Client''' (formerly branded VI Client) and '''VMware vCenter''' are management consoles for VMware vSphere hosts.

:*vSphere Client is free but only has basic management capabilities.
:*vCenter is not free as it has advanced management capabilities, but note UC may not support every feature in vCenter. vCenter is mandatory for any specs-based deployment.

 

'''VMware vSphere ESXi''' is sold in several '''Editions''' with different levels of feature support.

:*[https://www.vmware.com/products/vsphere/buy/editions_comparison.html Click here for a comparison of VMware vSphere ESXi feature Editions on vmware.com].
::*[http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html Click here for a clarification of “free ESXi 4.1” vs. “vSphere ESXi 4.1 Hypervisor Edition”] (formerly branded as "VMware ESXi Single Server Edition" or “free ESXi”).
::*For details on supported features for 4.x versions of other vSphere ESXi Editions, see your VMware account team. VMware on their web site [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010579 provides a "best effort" comparison here].
:*If buying VMware vSphere ESXi direct from VMware:
::*[http://www.vmware.com/products/vsphere/purchase-advisor/index.html Click here for VMware's Purchase Advisor for vSphere on vmware.com].
::*[https://www.vmware.com/files/pdf/vsphere_pricing.pdf Click here for an overview of VMware vSphere ESXi pricing on vmware.com].

 

There are no UC-specific restrictions on what VMware vSphere ESXi feature Edition you "can" use, but the Edition you "should" use will be determined by VMware licensing rules based on aspects of the UC deployment. The customer is responsible for selecting the correct VMware vSphere ESXi Edition based on their feature and UC application requirements. The following non-exhaustive list is provided for convenience only as examples of what must be considered under VMware's current licensing rules, which are subject to change:

:*If you want to use Cisco Nexus 1000V with UC, that requires the VMware vSphere ESXi feature "Distributed Switch" which is only available in Enterprise Plus Edition.
:*If you want to use a UC virtual machine OVA template with a large quantity of vCPU, verify the VMware vSphere ESXi Edition supports sufficient "vCPU Entitlement" for that OVA's vCPU count.
::*E.g. the Unity Connection 20K user OVA that requires 7 vCPU per VM.
:*Verify all the UC-supported VMware vSphere ESXi features you want to use are [https://www.vmware.com/products/vsphere/buy/editions_comparison.html supported by the Edition you pick].
:*The "Cisco UC Virtualization Hypervisor" is only supported for use with Business Edition 6000 and has the following restrictions:
::*It is not available or transferable for use with any other hardware or software.
::*Server Hardware restricted to UCS C200 M2 TRC#1
::*Max total vRAM across all VMs is 16 GB (of which 14 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Does not support VMware vCenter management. Does not offer any [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features like other Editions].
:*The "Cisco UC Virtualization Foundation" is only supported for use with Business Edition 6000 and UC on UCS.
::*Not available direct from VMware, only sold as part of BE6K or UC on UCS. It is not available or transferable for use with non-UCS hardware or non-UC software.
::*Server Hardware restricted to 2-socket UCS B-Series models and 2-socket UCS C-Series models.
::*Max total vRAM across all VMs is 32 GB (of which 30 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Supports VMware vCenter management (purchased separately). UC-supported [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features] limited to vStorage APIs. All other UC-supported features (including but not limited to VMware High Availability, Data Recovery, vMotion, Distributed Switch, etc.) are not offered.

 

Finally, note that UC may not support all of the features that are included in the VMware vSphere ESXi Edition you pick. This may be because the feature is N/A for a UC deployment, or it has not been sufficiently tested before UC will support, or it requires application enhancements before UC can support.

The table below lists VMware feature support by UC app/version. If the feature is supported, click on its name in the table to view UC caveats and best practices. Feature support may vary by UC app. This site will be updated as new support becomes available.

{{note| feature support for Cisco Unified Contact Center Enterprise varies by component (e.g. Peripheral Gateway) and deployment model (e.g. "Rogger") - this section will give a summary support position, but for individual components see [[Unified Contact Center Enterprise|Support for Virtualization on the ESXi/UCS Platform]].}} 

=== Legend for Feature Support Tables ===

:*Y(C) = Supported with '''C'''aveats - see [[#Best_Practices|Best Practices]] for details
:*Y(P) = '''P'''artial (limited) support only - see [[#Best_Practices|Best Practices]] for details
:*No = the feature is not supported at this time - see [[#Best_Practices|Best Practices]] for alternatives, if any.

=== VMware Feature Support for Call Processing and System Management 8.0(2) through 8.6(1) ===

{| border="1"
|+ ''' '''
|-
! Feature
! Unified CM
! CER
! SME
! Unified Attendant Consoles
! UPM
! UOM, USM, USSM
! CIME 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C)
| Y(C) 
| Y(C) 
| Y(C) 
| Yes
| Y(C) 
| Y(C) 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C)
| Y(C)
|  Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(P)
| Y(P)
| No 
| No 
| Y(P)
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No 
| No 
| No
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)  
| Y(P)  
| Y(P)  
| Y(P)  
| Yes
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C)
| No
| Y(C)
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| Y(C) 
| Y(C)
| Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C) 
| Y(C) 
| Y(C) 
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(C)
| Y(C) 
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C) 
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| Y(C)
| No 
| Y(C)
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 5.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! All vSphere ESXi 5.0 Features
| No
| No
| No
| No
| No
| No 
| No
|}

=== VMware Feature Support for Messaging and Presence 8.0(2) through 8.6(1) ===

{| border="1"
|+ '
|-
! Feature
! Unity Connection
! Unity
! Unified Presence
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(PP
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| Y(C)
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| Y(C) 
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(P)
| No
| Y(P)
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| Y(C) 
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
|- align="center"
! [[#Identity|Identity]]
| No  
| No  
| Y(C) 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| 
|}

 

=== VMware Feature Support for Contact Center 8.0(2) through 8.6(1) ===

{| style="width: 906px; height: 823px" border="1"
|+  
|-
! Feature
! Unified CCX
! Cisco WFO, QM, and WFM
! Unified CCE, CVP
! Unified IC
! Cisco MediaSense
! SocialMiner
! Unfied EIM-WIM
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
|
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C) 
| No
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C)
| Y(C) 
| No
| Y(C) 
| No
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P) 
| No
| Y(P) 
| No
| No
| No
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P) 
| Y(P) 
| Y(P) 
| Y(P) 
| No
| No
| No
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| No
| Y(C) 
| Y(C)
| No
| No
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(P) 
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C)
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
|
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C)
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No
| No
| 
|}

== Best Practices ==

=== Virtual Machine Templates (OVA files) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

See www.dmtf.org for details on the Open Virtualization Format, which describes an OVF Package (a directory of files describing a virtual machine's configuration) and an OVA Package (single tar file containing an OVF Package).

“Template” in this context refers to an OVA file that defines the virtual server (but not the “workload”, i.e. the UC OS and application). Each virtualized UC product provides a set of predefined virtual machine templates (as OVA files) for supported Virtual Machine (VM) configurations. Customers must download and use these OVA template files for initial install, as they cover items such as supported capacity levels and any required OS/VM/SAN “alignment”. OVAs configured differently than the predefined templates are not supported at this time. To download the OVA files, refer to the [[Unified Communications Virtualization Sizing Guidelines|Unified Communications Virtualization sizing guidelines]].

=== Copy Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Copying a Virtual Machine (VM) copies both the virtual server configuration and the workload (UC OS and application) running on that virtual server to a file on networked shared storage. This allows VMs to be copied, then subsequently modified or shut down. This feature effectively provides a method to do full system backup/restore, take system images or revert changes to software versions, user data and configuration changes.

:*Prior to copying, the VM must first be shutdown (which will shut down the virtual server, the UC OS and the UC application).
:*If uploading a VM copy as a “whole system restore”, clustered UC applications such as CUCM will probably require their replication to be manually “fixed” via a CLI command.

=== Restart Virtual Machine on Different ESXi Host ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

A Virtual Machine (VM) file on network/shared storage can be booted on any physical server hosting ESXi that has access to that network shared storage. With multiple physical ESXi hosts connected to the same network shared storage, this can be used to perform:

:*Fast manual server moves, e.g. moving VM from ESXi host A to ESXi host B in another chassis, closet, building, etc.
:*Fast manual server recovery, e.g. moving VM from ESXi host A that has just had a server hardware or VMware failure to ESXi host B that is healthy. See also VMware High Availability and Site Recovery Manager.
:*Setting up software at a staging location to be later moved or deployed elsewhere. For multi-site scenarios, this may instead require “exporting” the VM.

=== Resize Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Similar to adding/removing physical hardware to/from a physical server, you can add/remove virtual hardware (vCPU, vRAM, vDisk, vNIC, etc.) to/from a Virtual Machine (VM) via a software change in VMware’s configuration interfaces. Where supported, this provides the VM equivalent of migration to a more powerful or less powerful server.

:*Any changes to a VM must align with the best practices in [[#Virtual_Machine_Templates_.28OVA_files.29|Virtual Machine Templates (OVA files)]]. VM changes that result in an unsupported OVA configuration are not allowed. Even if you align with supported OVA configurations, desired VM changes may be prevented by one of the other caveats below.
:*Support for adding virtual hardware resources (similar to moving from a less powerful server to a more powerful server, such as MCS 7825 ⇒ MCS 7845) depends on which resource, and which UC product:
::*Adding vCPU is supported for all apps except Unity and Unity Connection, but requires VM to be shutdown first.
::*Adding vRAM is supported but requires VM to be shutdown first.
::*Adding vDisk is not supported as it would require re-partitioning by the application.
:*Adding vNIC is not supported unless the UC app supports multiple network connections with different IP addresses. See best practices for [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]].
:*For all other changes, it is recommended to backup the application, reinstall application on a new OVA file, and restore the application.
:*Removing virtual hardware resources (vCPU, vRAM, vDisk, etc.) is not supported (similar to moving from a more powerful server to a less powerful server, such as MCS 7845 ⇒ MCS 7825). These migrations require backing up the application, reinstalling on a new OVA file, and and restoring the application.
:*Live runtime resizing via the VMware Hot Add feature is not supported.

=== VMware Hot Add ===

Not supported. See [[#Resize_Virtual_Machine|Resize Virtual Machine instead]].

=== Multiple Physical NICs and vNICs ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). Network traffic is switched from physical NICs to “vNIC’s” of the Virtual Machines (VM) via either VMware vSwitch or Cisco Nexus 1000V. Customers can use these multiple NICs for VM network traffic, VMware console access, or management “back-doors” for administrative access, backups, software updates or other traffic that is desired to be segregated from the VM network traffic. All these uses are supported for UC but note that UC apps like CUCM only support a single vNIC with a single IP address.

=== VMware High Availability (HA) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature automatically restarts a Virtual Machine (VM) on the same physical server or a different physical server. It can be used to supplement software redundancy as a means of fast, automated Failed-server recovery when a VM (but not the application) is hung or if there is a fault with the physical host server or VMware software.

:*Failovers to other servers must not result in an unsupported deployment model (e.g. destination server must align with supported co-residency after failover occurs).
:*Does not protect vs. faults with the SAN or network hardware.

=== VMware Site Recovery Manager (SRM) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature provides an automated disaster recovery solution that works on a “site to site” basis, where a “site” comprises physical servers, VMware and SAN storage. Refer to the VMware documentation for requirements to use this feature. There are no special requirements to use this feature with UC apps that support it.

=== VMware Identity ===

The VMware identity feature allows you to copy an existing instance of a virtual Cisco Unified Presence, and change its identity. The identity of a system is made up of every setting that you usually configure during a fresh install (such as IP address, hostname, passwords).

You can then use this new identity for another instance of a Cisco Unified Presence on a virtual machine. This avoids you having to perform a complete installation each time you deploy a new Cisco Unified Presence.

=== VMware vNetwork Distributed Switch ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Supporting apps in UC on UCS may either use this feature, or the Cisco VN-Link technology (such as Cisco Nexus 1000V).

 

=== VMware vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Cl]]ient.

This feature migrates a live, running Virtual Machine (VM) from one physical server to another.

The following applies to any use of vMotion with UC apps:

:*VM must be installed on shared storage (SAN).
:*Source and destination physical servers must be connected to same SAN.
:*Destination physical server must not end up with over-subscribed hardware after the migration. Supported capacity and co-residency rules for UC must be followed before and after the migration.
:*VMware “Long Distance vMotion” (site to site) is not supported.
:*The only supported scenario is a manual move to a different server, e.g. for planned maintenance on the server or VMware software, or during troubleshooting to move software off of a physical server having issues.
:*Use of vMotion for real-time load-balancing of live UC VMs is not supported, whether alone or in conjunction with VMware Dynamic Resource Scheduler (DRS) or Dynamic Power Management (DPM).
:*Moving a shut down VM during a maintenance window, i.e. a "cold migration" or "host to host migration", is not vMotion and is supported.

If the UC app is listed as "Supported with Caveats", then support is as described below:

:*Migration of UC VMs that are live and processing live traffic is supported, but note that Cisco testing cannot cover every possible operational scenario. Testing has shown there is a slight risk of calls in progress being impacted for a few seconds as the migration occurs, with worst case result of the affected calls being dropped. If vMotion is suspected as the cause of dropped calls, customers should gather appropriate application logs as well as performance data from VMware vCenter and send to Cisco TAC for analysis.

If the UC app is listed as "Partial" support, then support is “maintenance mode only” as described below:

:*"Maintenance mode only" - VMware vMotion by definition operates on live VMs, but the VM running the UC app must be “live but quiescent”. I.e. in a maintenance window, not in production, not processing live traffic. This is because during the vMotion cutover, the system is paused, which for real-time UC apps creates service interruption which degrade voice quality after the migration for calls in progress.

 

=== VMware Dynamic Resource Scheduler ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== VMware Dynamic Power Management ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== Long Distance vMotion ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported. Long Distance vMotion is a joint Cisco and VMware validated architecture for using the vMotion feature across data centers. For more information, see http://blogs.cisco.com/datacenter/comments/cisco_and_vmware_validated_architecture_for_long_distance_vmotion/ and http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns836/white_paper_c11-557822.pdf.

=== Storage vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This “customer convenience” feature provides easy migration of a live system from one SAN to another SAN. For UC apps, an easier suggested alternative is to just perform manual VM shutdown and migration to the new SAN. However, if Storage vMotion must be used, it is only under the following conditions:

:*Requires SAN storage.
:*May only be done during a maintenance window with UC VMs shut down.

=== VMware vCenter Update Manager (VUM) ===

NOTE: Support varies by application and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature automates patching and updating of VMware vSphere hosts. Note that Cisco Unified Communications applications upgrades, patches and updates can not be delivered through vCenter Update Manager.

=== VMware Consolidated Backup (VCB) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature provides integration with 3rd-party backup utilities so that they can non-disruptively backup the OS and application in a Virtual Machine (VM). See also VMware Data Recovery and Copy Virtual Machine.

Existing UC app methods of backing up the software continue to be supported.

=== VMware Data Recovery ===

Not supported. See [[#VMware_Consolidated_Backup_.28VCB.29|VMware Consolidated Backup]] for what is supported.

=== VMware Snapshots ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

Used to preserve the state of a VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique. See also VMware Data Recovery and Copy Virtual Machine.

=== VMware Fault Tolerance ===

Not supported. See [[#VMware_High_Availability_.28HA.29|VMware High Availability]] for what is supported. Another alternative is manual Virtual Machine shutdown and migration.

=== VMware vCenter Converter ===

P2V tools are not supported. To migrate from bare-metal servers (e.g. Cisco 7800 Series Media Convergence Server) to UC on UCS, the supported procedure is:

:*upgrade to 8.x software version on the bare-metal server
:*take a software backup
:*fresh install 8.x software on VMware / UC on UCS
:*restore from backup

=== VMsafe ===

Not supported. See the documentation for the UC application software or UC appliance software to see what is supported.

=== VMware vShield ===

Not supported. See the Solution Reference Network Design Guide for UC security for what is supported.

=== Virtual Appliance Packaging of UC apps ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party VM-based Backup Tools ===

Not supported. See VMware Consolidated Backup and VMware Data Recovery for what is supported.

=== 3rd-Party VM-based Deployment Tools ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party Physical To Virtual (P2V) Migration Tools ===

Not supported. See VMware vCenter Converter for what is supported.

=== VMware Boot from SAN ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

VMware ESXi 4.1 is required for this feature. Even it works with 4.0, VMware's official support is only for 4.1 and later. Requires use of a "diskless" server - see Supported Hardware for tested reference configurations. Both VMware ESXi and UC apps are installed on, and boot from, the fibre channel SAN. See UCS page at www.cisco.com/go/swonly for storage support policy.

== Services and Support Contracts for VMware are Required ==

Customers deploying virtualized UC must have a valid support contract for the VMware software in order to be supported by Cisco.

Customers purchasing VMware software licenses from Cisco must also purchase a subscription services part number from Cisco (for part number examples, see the UC on UCS page at www.cisco.com/go/swonly).

Customers purchasing VMware software from a 3rd-party must purchase subscription services from that 3rd-party or from VMware.

Customers should note that for VMware vSphere Hypervisor (formerly called “ESXi Single Server Edition” or “free ESXi”), VMware does not offer the same services options and terms as they do for their Standard, Advanced, Enterprise or Enterprise Plus Editions. Customers should take this into account when planning and pricing their support strategy.

Cisco Field and Channel Partners may consult the User Connect Licensing Ordering Guide for more information.

== Cisco TAC Support Expectations ==

The following table describes how TAC support works for VMware in a UC on UCS context, based on who VMware was purchased from.

Special case: when Cisco as a VMware reseller sells VMware Enterprise License Agreements, it is treated as a VMware direct sale for TAC support purposes based on how the maintenance contracts are structured.

 

{| border="1"
|-
! 
! Buy from Cisco as Collaboration SKU
! Buy from Cisco as Data Center SKU
! Buy from 3rd-party, or enterprise/site license
|-
! Available VMware ESXi Editions
| Standard
| Advanced, Enterprise or Enterprise Plus
| Standard, Advanced, Enterprise, Enterprise Plus or vSphere Hypervisor (formerly "Single Server Edition" or "free ESXi"
|-
! Mandatory Support Contracts
| ISV1 from Cisco as Collaboration Service SKU
| ISV1 from Cisco as Data Center Service SKU
| "SnS" subscription from VMware
|-
! Who takes first call?
| Cisco
| Cisco
| VMware
|}

'''TAC Responsibility:''' Note that multi-vendor triage is the norm in virtualized deployments, where the storage, server, hypervisor, OS and application are potentially all from different vendors. Cisco Voice TAC responsibility is the UC application, demarcated at the Virtual Machine. Cisco Server Virtualization TAC responsibility is for VMware (via triage), Cisco UCS, Cisco storage access (or triage with customer and their vendor) and storage array (via triage with customer and their vendor). Escalation to VMware, the customer, or the customer's storage vendors will be done as needed for solution components not produced by Cisco.

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications Virtualization Supported Applications

2011-12-16T20:52:19Z

Sdurvasu: 1 revision

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

Version compatibility of virtualized Cisco Unified Communications applications with various server/storage hardware options are listed below.

*Support information below is as of the release date of '''Cisco Unified Communications 8.6(1)''', which updated '''8.0, 8.5 and 8.6''' support policies.

*Ensure your deployment follows the rules listed [[High-level Checklist for Design and Implementation|here]].

*Click on the application name for additional product-specific requirements and information (if any).

*"TRC" = "Tested Reference Configuration" as described [[Unified Computing System Hardware|here]].

 

== Call Processing and System Management Applications ==

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px; height: 476px"
|-
! rowspan="2" | Application
! colspan="2" | [[Specification-Based Hardware Support]]
! colspan="14" | [[Tested Reference Configurations (TRC)]]
|- style="background: rgb(229,228,226)"
! Intel Xeon 56xx/75xx @ 2.53+ GHz
! Intel Xeon E7-xxxx @ 2.4+ GHz
! B230 M2 TRC #1 (Diskless, ESXi 4.1+ only)
! B440 M2 TRC #1 (Diskless, ESXi 4.1+ only)
! B200 M2 TRC #1 (DAS+FC SAN)
! B200 M2 TRC #2 (Diskless, ESXi 4.1+ only)
! B200 M1 TRC #1 (DAS+FC SAN)
! B200 M1 TRC #2 (Diskless, ESXi 4.1+ only)
! C210 M2 TRC #1 (DAS)
! C210 M2 TRC #2 (DAS+FC SAN)
! C210 M2 TRC #3 (Diskless, ESXi 4.1+ only)
! C210 M1 TRC #1 (DAS, single-VM)
! C210 M1 TRC #2 (DAS)
! C210 M1 TRC #3 (DAS+FC SAN)
! C210 M1 TRC #4 (Diskless, ESXi 4.1+ only)
! C200 M2 TRC #1 (DAS)
 

|-
| Unified Communications Manager (1)
 

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
|
*8.5(x)
*8.6(x)

 

|-
| Cisco Emergency Responder
|
*8.5(x)
*8.6(x)

| Not supported
| Not supported
| Not supported
|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|-
| Session Manager Edition
|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

| Not supported
 

|-
| Intercompany Media Engine
|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
*8.6(2+)

|
Not supported

|-
| Unified Attendant Consoles
|
*8.6(x)

| Not supported
| Not supported
| Not supported
|
*8.6(x)

|
*8.6(x)

|
*8.0(3)
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|-
| UC Management Suite (OM, SM, SSM, PM)
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
|}

 (1) Applicable for publishers, subscribers, standalone TFTP and standalone multicast MOH nodes.

== Messaging and Presence Applications ==

{| class="wikitable FCK__ShowTableBorders" style="width: 1076px; height: 476px"
|-
! rowspan="2" | Application
! colspan="2" | [[Specification-Based Hardware Support]]
! colspan="14" | [[Tested Reference Configurations (TRC)]]
|- style="background: rgb(229,228,226)"
! Intel Xeon 56xx/75xx @ 2.53+ GHz
! Intel Xeon E7-xxxx @ 2.4+ GHz
! B230 M2 TRC #1 (Diskless, ESXi 4.1+ only)
! B440 M2 TRC #1 (Diskless, ESXi 4.1+ only)
! B200 M2 TRC #1 (DAS+FC SAN)
! B200 M2 TRC #2 (Diskless, ESXi 4.1+ only)
! B200 M1 TRC #1 (DAS+FC SAN)
! B200 M1 TRC #2 (Diskless, ESXi 4.1+ only)
! C210 M2 TRC #1 (DAS)
! C210 M2 TRC #2 (DAS+FC SAN)
! C210 M2 TRC #3 (Diskless, ESXi 4.1+ only)
! C210 M1 TRC #1 (DAS, single-VM)
! C210 M1 TRC #2 (DAS)
! C210 M1 TRC #3 (DAS+FC SAN)
! C210 M1 TRC #4 (Diskless, ESXi 4.1+ only)
! C200 M2 TRC #1 (DAS)
 

|-
| Cisco Unity Connection
| 8.0(2) and later
| 8.0(2) and later
| 8.0(2) and later
| 8.0(2) and later
| 8.0(2) and later
| 8.0(3) and later
| 8.0(2) and later
| 8.0(3) and later
| 8.0(2) and later
| 8.0(2) and later
| 8.0(3) and later
| 8.0(2) and later
| 8.0(2) and later
| 8.0(2) and later
| 8.0(3) and later
| 8.0(2) and later
|-
| Cisco Unity
| 7.0(2) and later
| 7.0(2) and later
| 7.0(2) and later
| 7.0(2) and later
| 7.0(2) and later
| 7.0(2) and later
| 7.0(2) and later
| 7.0(2) and later
| 7.0(2) and later
| 7.0(2) and later
| 7.0(2) and later
| 7.0(2) and later 
| 7.0(2) and later
| 7.0(2) and later
| 7.0(2) and later 
| Not supported
|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
| 8.6(1) and later
| Not supported
| Not supported
| Not supported
| 8.5 and later
| 8.5 and later
| 8.0(2) and later
| 8.5 and later
| 8.5 and later
| 8.5 and later
| 8.5 and later
| 8.0(2) and later
| 8.0(2) and later
| 8.0(2) and later
| 8.5 and later
| 8.5 and later
|}

 

== Contact Center Applications ==

{| class="wikitable FCK__ShowTableBorders"
|-
! rowspan="2" | Application
! colspan="2" | [[Specification-Based Hardware Support]]
! colspan="14" | [[Tested Reference Configurations (TRC)]]
|- style="background: rgb(229,228,226)"
! Intel Xeon 56xx/75xx @ 2.53+ GHz
! Intel Xeon E7-xxxx @ 2.4+ GHz
! B230 M2 TRC #1 (Diskless, ESXi 4.1+ only)
! B440 M2 TRC #1 (Diskless, ESXi 4.1+ only)
! B200 M2 TRC #1 (DAS+FC SAN)
! B200 M2 TRC #2 (Diskless, ESXi 4.1+ only)
! B200 M1 TRC #1 (DAS+FC SAN)
! B200 M1 TRC #2 (Diskless, ESXi 4.1+ only)
! C210 M2 TRC #1 (DAS)
! C210 M2 TRC #2 (DAS+FC SAN)
! C210 M2 TRC #3 (Diskless, ESXi 4.1+ only)
! C210 M1 TRC #1 (DAS, single-VM)
! C210 M1 TRC #2 (DAS)
! C210 M1 TRC #3 (DAS+FC SAN)
! C210 M1 TRC #4 (Diskless, ESXi 4.1+ only)
! C200 M2 TRC #1 (DAS)
 

|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] 
| 8.5(1) and later 
| 8.5(1) and later
| 8.5(1) and later
| 8.5(1) and later
|
*8.0(2) and later
*8.5(1) and later

| 8.0(2)SU2 and later
|
*8.0(2) and later
*8.5(1) and later

| 8.0(2)SU2 and later
|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

| 8.0(2)SU2 and later
|
*8.0(2) and later
*8.5(1) and later 

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

| 8.0(2)SU2 and later
| 8.5(1) and later
|-
| [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Workforce Optimization (WFO), Quality Management (QM), and WorkForce Management (WFM)]
| 8.5(2) and later 
| 8.5(2) and later
| 8.5(2) and later
| 8.5(2) and later
| 8.5(2) and later
| 8.5(2) and later
| 8.5(2) and later
| 8.5(2) and later
| 8.5(1) and later
| 8.5(1) and later
| 8.5(2) and later
| 8.5(1) and later
| 8.5(1) and later
| 8.5(1) and later
| 8.5(2) and later
| 8.5(2) and later
|-
| [[Unified Contact Center Enterprise]] 
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
|-
| - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tool, limited/hybrid support for Unified ICME/CCH/ICMH
| Not supported 
| Not supported
| Not supported
| Not supported
|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

| Not supported
|
Not supported

| Not supported
|
*8.0(2) and later
*8.5(1) and later

| Not supported
|
Not supported

| Not supported
|-
| - Progger, Outbound Option with SCCP Dialer, Webview, Expert Advisor, RSM, Unified CRM Connector
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
|-
| [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]] 
| 8.5(2) and later
| Not supported
| Not supported
| Not supported
| 8.0(3) and later
| 8.5(2) and later 
| 8.0(3) and later
| 8.5(2) and later
| 8.0(3) and later
| 8.0(3) and later
| 8.5(2) and later
| 8.0(3) and later
| 8.0(3) and later
| 8.0(3) and later
| 8.5(2) and later
| Not supported
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]] 
| Not supported 
| Not supported
| Not supported
| Not supported
|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

| Not supported
| Not supported
| Not supported
|
*8.0(2) and later
*8.5(1) and later

| Not supported
| Not supported
| Not supported
|-
| [[Unified Customer Voice Portal]] (all components) 
| Not supported 
| Not supported
| Not supported
| Not supported
|
*8.0(1) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(1) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(1) and later
*8.5(1) and later

| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| Not supported 
| Not supported
| Not supported
| Not supported
| 8.5(2) and later
| 8.5(2) and later
| 8.5(2) and later
| 8.5(2) and later
| 8.5(1) and later
| Not supported
| Not supported
| 8.5(1) and later
| 8.5(1) and later
| Not supported
| Not supported
| Not supported
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| 8.5(3) and later 
| Not supported
| Not supported
| Not supported
| 8.5(3) and later
| 8.5(3) and later
| 8.5(3) and later
| 8.5(3) and later
| 8.5(3) and later
| 8.5(3) and later
| 8.5(3) and later
| 8.5(3) and later
| 8.5(3) and later
| 8.5(3) and later
| 8.5(3) and later
| 8.5(3) and later
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Cisco Unified Email Interaction Manager and Web Interaction Manager]]
| 4.4(1) and later
| Not supported
| Not supported
| Not supported
| 4.3(2) and later
| 4.3(2) and later
| 4.3(2) and later
| 4.3(2) and later
| 4.3(2) and later
| Not supported
| 4.3(2) and later
| Not supported
| 4.3(2) and later
| Not supported
| 4.3(2) and later
| Not supported
|}

 

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Virtualization for Cisco SocialMiner

2011-12-12T16:16:01Z

Sdurvasu: 1 revision

{{note| Product documentation may reflect varying names that appear in the application user interfaces and application programming interfaces of this product. These names may include Cisco SocialMiner, mmca, and ccp.}}

= Updates to this Page =

The following is a list of significant updates to this page:

 

{| class="wikitable FCK__ShowTableBorders"
|-
! Date
! Update
|-
| November 2010
| Virtualization of Cisco SocialMiner on UCS C Series hardware.
|-
| April 2011
| Added link to Unified Communications Virtualization Supported Applications
|-
| April 2011
| IOPS info
|-
| August 2011
| IOPS info
|}

= Information for Partners about SocialMiner Deployments =

See:

[[Before You Buy or Deploy - Considerations for Design and Procurement]].

[[Unified Communications Virtualization Supported Applications]]

 

= VM-Specific SocialMiner Hardware Requirements =

See [[Tested Reference Configurations (TRC)]].

Before you install the SocialMiner software in any server, you must address the following requirements:

*The VM disk allocation time depends on your VM environment. If you have created several VMs on the host server, your disk allocation takes a longer time. If you have not created any VM in your host server, your disk allocation takes a shorter time. During the course of testing in various environments at Cisco Systems, disk allocation has taken anywhere from 2 minutes to 2 hours for a 34 GB data space. Depending on your space requirement, be sure to make this empty space available for all SocialMiner deployments
*If you are performing a fresh install of SocialMiner in any deployment, be sure to verify that the virtual machine is also fresh (no previously-installed OS is present in the VM).

= SocialMiner-Specific Details for VMware Requirements =

All SocialMiner servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS).

See [[Unified Communications VMWare Requirements]] and [[Ongoing Virtualization Operations and Maintenance]].

*SocialMiner ISO or DVD
*ESXi 4.0 or ESXi 4.1 must be installed prior to the SocialMiner installation. [[#Configuring_ESXi_4.1|ESXi 4.1 requires additional configuration]].
*Cisco UCS Hardware—SocialMiner 8.5(4) supports a [http://docwiki.cisco.com/wiki/Specification-Based_Hardware_Support specifications-based virtualization model.] You can use any hardware platform you like (from any vendor) as long as it supports the specifications required for the VM. Also, you can run any other application(s) you like on that same server.

=== Configuring ESXi 4.1 ===

To ensure normal networking performace, configure the installed ESXi 4.1 host as follows:

#Use vSphere Client to log in to the ESXi host or its vCenter.
#Select host --> Configuration --> Advanced Settings.
#Select Net and scroll down slightly more than half way.
#Set the following parameters from 1 to 0:

*Net.VmxnetSwLROSL
*Net.Vmxnet3SwLRO *Net.Vmxnet3HwLRO
*Net.Vmxnet2SwLRO
*Net.Vmxnet2HwLRO

Reboot the ESXi host to activate these changes.

= VM-Specific SocialMiner Software Requirements =

See [[Unified Communications VMWare Requirements]].

The following software requirements apply specifically to SocialMiner:

*SocialMiner can only be deployed on servers using VMware ESXi 4.0 or ESXi 4.1.
*The downloadable OVF Templates have the hardware configuration for the SocialMiner VM's. This is the only configuration supported. Please use the SocialMiner OVF Appliance to install SocialMiner.
*For other third-party software requirements and for a list of approved UCS servers, see the server requirements and version compatibility with Unified CM sections in the ''Hardware & System Software Specification (Bill of Materials) for Cisco Unified Contact Center Enterprise Guide'' available at http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_user_guide_list.html.

= SocialMiner-Specific Information for OVA Templates =

See [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]].

The SocialMiner OVA can be downloaded here: http://www.cisco.com/cisco/software/release.html?mdfid=283613136&catid=278875240&softwareid=283733464

= SocialMiner-Specific Information for Sizing Guidelines =

The SocialMiner Production OVF includes the following settings:

*4 vCPU
*12 GB RAM
*1 vNIC with static MAC address
*2 vDisks:
**vDisk 1 = 146 GB Operating system, SocialMiner application binaries, Reporting database
**vDisk 2 = 256 GB Data store, Index store, ActiveMQ store, Unified OS logs and SocialMiner logs

== VM IOPS ==

The minimum SocialMiner IOPS requirement is 1400. Upgrades require 3000 IOPS for optimal performance.

= Cisco SocialMiner-Specific VM Information on Installation, Timekeeping, and Best Practices =

== Creating the SocialMiner Virtual Machine ==

Perform the following steps in vSphere client to deploy the Virtual machines:

#Highlight the host or cluster to which you wish the VM to be deployed.
#Select '''File > Deploy OVF Template'''.
#Click the '''Deploy from File''' radio button and specify the name and location of the file you downloaded in the previous section OR click the '''Deploy from URL''' radio button and specify the complete URL in the field, then click Next.
#Enter the name of the VM machine that you are creating and the location where it will be created
#Choose the type of deployment (Production or Lab)
#Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click '''Next'''.
#Verify the deployment settings, then click '''Finish'''.
#Update boot order as per instructions below
#Insert SocialMiner disk and follow SocialMiner installation guide.

== Changing the Boot Order of the Virtual Machine ==

You must change the boot order of the Virtual Machine so that the system boots off the CD/DVD drive for the install.

To change the boot order of the Virtual Machine:

#In VMware vSphere Client, power off the virtual machine onto which you deployed the OVA template.
#In the left pane of vSphere Client, right-click the name of the virtual machine, and select '''Edit Settings'''.
#In the Virtual Machine Properties dialog box, select the Options tab.
#In the Settings column, under Advanced, select '''Boot Options'''.
#Under Force BIOS Setup, check the '''The Next Time the Virtual Machine Boots, Force Entry into the BIOS Setup Screen''' check box.
#Click '''OK''' to close the Virtual Machine Properties dialog box.
#Power on the virtual machine (The virtual machine boots into the BIOS menu)
#Navigate to the Boot menu and change the boot device order so the CD-ROM device is listed first and the Hard Drive device is listed second.
#Save the change and exit BIOS setup.

Note: After finishing the installation, consider changing the boot order back so that the Hard Drive device is again listed before the CD-ROM device.
----

= Related Documents =

[[#SocialMiner_8.5.284|User Guide for SocialMiner Release 8.5(4)]]

----

{| border="1" class="wikitable"
|-
! style="background-color: rgb(255, 215, 0);" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

[[Category:Cisco_SocialMiner]]

Virtualization for Unified CCE

2011-12-12T15:04:38Z

Sdurvasu: 1 revision

== Updates to this Page ==

The following is a list of significant updates to this page:

{| class="wikitable FCK__ShowTableBorders"
|-
! Date
! Update
|-
| December 09, 2011
| Added PG limited coresidency with UCM/CUP/IPIVR capability.
|-
| November 15,2011
| Added sample deployment for 12,000 agents.
|-
| June 28, 2011
| Updated list of Unified CCE components that have not been qualified and are not supported in virtualization. Updated Section 5.1 ESXI 4.1 Software Requirements to add new link to Disable LRO. Updated Section 6 Unified CCE Component Capacities and VM Configuration Requirements to add new link to Downloading OVA Templates for UC Applications. Removed Section 7.2ESXi 4.1 Network Settings. Changed title from Creating Virtual Machines from OVA VM Templates to Cisco Unified CCE-Specific Information for OVA Templates Removed Section 12.1 Downloading OVA Templates and added new links to Unified Communications Virtualization Downloads and Unified CCE OVA Templates.
|-
| June 1, 2011
| Added Section 5.1 ESXi 4.1 Software Requirements. Added Section 7.2 ESXi 4.1 Network Settings. Removed references to ESXi 4.0. Updated ''UCS Network Configuration'' section.
|-
| May 9, 2011
| Updated the ''Unified CCE Component Co-Residency and Sample Deployments ''section.
|-
| February 17, 2011
|
Updated the ''Creating Virtual Machines from OVA VM Templates'' section. Removed OVA list from this page and added a link. Added the Scalability Assumptions section. Updated the CUIC RAM (GB) numbers in the sample CCE deployments. Updated the sample deployment tables and highlighted optional items.

|-
| December 22, 2010
| Updated the pointer links for the Bill of Material, CCMP virtualization page, and the Hybrid Deployment section.
|-
| December 20, 2010
| Updated the Component Capacities section, the VM configuration requirements table, the Hybrid Deployment Options section, the steps for installing/migrating Unified CCE Components, the Support for Virtualization on the ESXi/UCS Platform section, and the Hardware Requirements section.
|-
| December 14, 2010
| Added Avaya ACD PG, TDM ACD PG, and Unified Contact Center Gateway to the Unified CCE Component Capacities and VM Configuration Requirements section. Updated the Steps for Installing/Migrating Unified CCE Components on Virtual Machines secton. Added Hybrid Deployment Options section.
|-
| December 10, 2010
| Added Unified CVP, Unified IC, Contact Center Management Portal (CCMP), and CAD to the sample deployments section.
|-
| October 1, 2010
| This page, [http://docwiki.cisco.com/wiki/UCCE_on_UCS_Deployment_Certification_Requirements_and_Ordering_Information UCCE on UCS Deployment Certification Requirements and Ordering Information], and [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE UCS Network Configuration for UCCE] updated to reflect support of UCS C-Series hardware on UCCE.
|-
| September 28, 2010
| CVP added to list of supported components/deployments.
|-
| September 21, 2010
| IPIVR added to list of supported components/deployments and as an optional component in the sample deployment tables at [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Sample_CCE_Deployments Sample CCE Deployments].
|}

== Information for Partners about Unified CCE on UCS Deployment Certification and Ordering ==

'''It is important that partners who are planning to sell UCS products on Unified Contact Center Enterprise read the DocWiki page''' [[Unified CCE on UCS Deployment Certification Requirements and Ordering Information]].

This page contains essential information for partners about the following:

:*Partner Certification Requirements
:*UCS Server Ordering Information
:*Important Notes on Cisco UCS Service and Support

== Unified CCE 8.x Support for Virtualization on the ESXi/UCS Platform ==

Starting with Release 8.0(2), virtualization of the following deployments and Unified CCE components on Cisco Unified Computing Systems (UCS) B200 Series and C210 Series hardware is supported:

:*Router
:*Logger
:*Agent PG
:*MR PG
:*VRU PG
:*Unified Contact Center Gateway
:*Avaya ACD PG (Also supported on virtualized ESXi server on MCS-7845-I3-CCE2)
:*TDM ACD PG (Also supported on virtualized ESXi server on MCS-7845-I3-CCE2)
:*Cisco Agent Desktop (CAD) Server
:*Administration and Data Server with one of the following roles:
::*Administration Server and Real-time Data Server (AW)
::*Configuration-only Administration Server (AW-CONFIG)
::*Administration Server and Real-time and Historical Data Server (AW-HDS)
::*Administration Server, Real-time and Historical Data Server, and Detail Data Server (AW-HDS-DDS)
::*Historical Data Server and Detail Data Server (HDS-DDS)
:*Administration Client
:*Outbound Option with SIP Dialer (collocate SIP Dialer and MR PG with Agent PG in the same VM guest. Generic PG can also be collocated with the Agent PG in the same VM guest. Published agent capacity formula with Outbound Option applies.)
:*Support Tools
:*Rogger (a Router and a Logger in the same VM)
:*The Unified Communications Manager (UCM) Clustering Over the WAN deployment model with Unified CCE is supported; see the section [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Support_for_UCM_Clustering_Over_the_WAN_with_Unified_CCE_on_UCS_Hardware Support for UCM Clustering Over the WAN with Unified CCE on UCS Hardware] for important information.
:*Unified IP-IVR is supported with Unified CCE on UCS B-Series solution and on UCS C-Series with the model ([http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210-VCD2)] only. Please refer to the IPIVR product specific pages for detail.
:*CVP is supported with CCE on UCS solution. Please refer to the [http://docwiki.cisco.com/wiki/Unified_Customer_Voice_Portal Unified Customer Voice Portal] wiki page for details.
:*Contact Center Management Portal (CCMP). See the [[Virtualization for CCMP with Unified CCE on UCS Hardware]] wiki page for details.
:*Cisco Unified Intelligence Center (Unified IC). Please refer to the [[Cisco Unified Intelligence Center]] wiki page for details.
:*Cisco E-mail Interaction Manager (EIM)/Web Interaction Manager (WIM). See the Virtualization for EIM-WIM wiki page for details

The following deployments and Unified CCE components have not been qualified and '''are not supported''' in virtualization:

:*Progger (a Router, a Logger, and a Peripheral Gateway); this all-in-one deployment configuration is not scalable in a virtualization environment. Instead, use the Rogger or Router/Logger VM deployment configuration.
:*Unified CCH
:*Unified ICMH
:*Outbound Option with SCCP Dialer
:*WebView Server
:*Expert Advisor
:*Remote Silent Monitoring (RSM)
:*Span based Silent Monitoring on UCS B-series chassis
:*Cisco Unified CRM Connector
:*IPsec. UCS does not support IPsec off-board processing, therefore IPsec is not supported in virtualization.

{{note|The hybrid (virtual and non-virtual server) deployment model is supported. Components that are not yet virtualized can continue to be on MCS in the UCCE on UCS deployment. See the [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE#Hybrid_Deployment_Options Hybrid Deployment Options] section for more information.}}

The following VMware features are not supported with Unified CCE:

:*VMware Physical to Virtual migration
:*VMware snapshots
:*VMware Consolidated Backup
:*VMware High Availability (HA)
:*VMware Site Recovery Manager
:*VMware vCenter Update Manager
:*VMware vCenter Converter

== Hardware Requirements for Unified CCE Virtualized Systems ==

Requirements for Cisco Unified CCE systems using UCS B200 or C210 hardware are located in the [[Unified Computing System Hardware|Unified Computing System Hardware]].

For UCS C210, Unified CCE supports only the model ([http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html UCS-C210-VCD2)] with a specific HDS Virtual Machine (VM) coresidence/population rule. See [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Sample_CCE_Deployments Sample CCE Deployments]

Unified CCE supports MCS-7845-I3-CCE2 with virtualization. For a list of supported virtualized components on MCS servers, see the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release, 8.0(x).] Unified CCE does not support UCS C200.

== VMware and Application Software Requirements ==

The following software requirements apply specifically to Unified Contact Center Enterprise:

:*VMWare ESXi 4.0 or 4.1, minimum version 4.0U1. ''Versions of ESXi prior to 4.0U1 and all versions of ESX are unsupported.''
:*If you are upgrading ESXi software, see the section [http://docwiki-dev.cisco.com/wiki/Ongoing_Virtualization_Operations_and_Maintenance Upgrade ESXi].
:*The Windows, SQL, and other third party software requirements for the Unified CCE applications in the ESXi/UCS platform are the same as in the physical server. For such information see the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise & Hosted, Release 8.0(x)].

=== ESXi 4.1 Software Requirements ===

When Cisco Unified CCE is running on ESXi 4.1, you must perform the following steps:

:*You must install or upgrade VMware Tools for ESXi 4.1 on each of the VMs and use all of the VMware Tools default settings. For more information, see the section [http://docwiki-dev.cisco.com/wiki/VMware_Tools VMware Tools]
:*You must disable Large Receive Offload (LRO). For details, see the section [http://docwiki-dev.cisco.com/wiki/Disable_LRO Disable LRO]

 

= Unified CCE Component Capacities and VM Configuration Requirements =

For supported Unified CCE component capacities and VM computing resource requirements, see the [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Contact_Center_Enterprise List of Unified CCE OVA Templates.]

{{note| You must use the OVA VM templates to create the Unified CCE component VMs.}}

 For instructions on how to obtain the OVA templates, see [http://docwiki.cisco.com/wiki/Downloading_OVA_Templates_for_UC_Applications Downloading OVA Templates for UC Applications]

== Unified CCE Scalability Impacts ==

The [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Contact_Center_Enterprise capacity sizing information] is based on the operating conditions published in the ''Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 8.x'', Chapter 10, ''Operating Conditions'' and the ''Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted'''','''''Release 8.x, Section 5. Both documents are available at [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_implementation_design_guides_list.html Cisco.com]'''.'''

The following features reduce the scalability of certain components below the agent count of the respective OVA [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Contact_Center_Enterprise capacity sizing information].

*CTI OS Security - CTI OS Server capacity is impacted when CTI OS Security is enabled; capacity is decreased by 25%.
*Mobile Agents - Refer to the SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with Mobile Agents.
*Outbound Option – Refer to SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with Outbound Option.
*Agent Greeting – Refer to SRND, Chapter 10, ''Sizing Information for Unified CCE Components and Servers ''table for sizing guidance with the Agent Greeting feature enabled.
*Extended Call Context (ECC) usage greater than the level noted in the Operating Conditions will have a performance and scalability impact on critical components of the Unified CCE solution. As noted in the SRND, the capacity impact will vary based on ECC configuration, therefore, guidance must be provided on a case-by-case basis.

= UCS Network Configuration =

:*'''IMPORTANT:''' For instructions on performing the network configuration needed to deploy Cisco Unified Contact Center Enterprise (UCCE) on UCS servers, see [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE UCS Network Configuration for UCCE].
:*QoS should be mandatorily enabled for both Private network connection(between Side A and B) and the public network connection(between the Router and the PG). Refer to Chapter 12,  [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/design/guide/uccesrnd80.pdf Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND)] for more details
:*For information on best practices for Cisco VLAN trunking to VMware, refer to [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806 this website].

== Support for UCM Clustering Over the WAN with Unified CCE on UCS Hardware ==

You can deploy the Unified Communications Manager (UCM) Clustering Over the WAN deployment model with Unified CCE on UCS hardware.

When you implement this deployment model, be sure to follow the best practices outlined in the section "IPT: Clustering Over the WAN" in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/design/guide/uccesrnd80.pdf Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND).]

In addition, note the following expectations for UCS hardware points of failure:

*For communication path single point of failure performed by Cisco on the Unified CCE UCS B-series High Availability (HA) deployment, system call handling was observed to be degraded for up to 45 seconds while the system recovered from the fault, depending upon the subsystem faulted. Single points of failure will not cause the built-in ICM software failover to occur. Single points of failure include, but are not limited to, a single fabric interconnect failure, a single fabric extender failure, and single link failures.

*Multiple points of failure on the Unified CCE UCS HA deployment can cause catastrophic failure, such as ICM software failovers and interruption of service. If multiple points of failure occur, replace the failed redundant components and links immediately.

=== B-Series Considerations ===

When deploying Clustering Over the WAN with B-Series hardware, use of the Cisco UCS '''M81KR''' Virtual Interface Card is mandatory.

New B-Series deployments using Clustering Over the WAN '''must''' use a Nexus 7000 Series / Nexus 5000 Series vPC infrastructure, or a Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720-10G.

See the configuration guidelines in [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE#UCCE_on_UCS_B-Series_Network_Configuration UCCE on UCS B-Series Network Configuration].

=== C-Series Considerations ===

If deploying Clustering Over the WAN with C-Series hardware, '''do not''' trunk public and private networks. You '''must''' use separate physical interfaces off of the C-Series servers to create the public and private connections. See the configuration guidelines in [http://docwiki.cisco.com/wiki/UCS_Network_Configuration_for_UCCE#Network_Requirements_for_C-210_M1_Servers Network Requirements for C-210 M1 Servers].

 

= Notes for Deploying Unified CCE Applications on UCS B-Series Hardware with SAN =

In Storage Area Network (SAN) architecture, storage consists of a series of arrays of Redundant Array of Independent Disks (RAIDs). A Logical Unit Number (LUN) that represents a device identifier can be created on a RAID array. A LUN can occupy all or part of a single RAID array, or span multiple RAID arrays.

In a virtualized environment, datastores are created on LUNs. Virtual Machines (VMs) are installed on the SAN datastore.

Keep the following considerations in mind when deploying UCCE applications on UCS B-series hardware with SAN.

*This deployment must comply with the conditions listed in Section 3.1.6 of the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware & System Software Specification (Bill of Materials) for Cisco Unified Contact Center Enterprise, Release 8.0(1).] In particular, SAN disk arrays must be configured as RAID 5 or RAID 10. 

*Each Historical Data Server (HDS) requires a dedicated LUN and a datastore with a 2 MB block size. No other application can reside on the same datastore as the HDS. The HDS requires a 2 MB block size to accommodate the 500 GB OVA disk size, which exceeds the 256 GB file size supported by the default 1 MB block size for datastores. The HDS block size is configured in VMware at datastore creation.

*To help keep your system running most efficiently, schedule automatic database purging to run when your system is least busy. 

*The SAN design and configuration must meet the following VMware ESXi disk performance guidelines:
**Disk Command Latency – It should be 15 mSec or less. 15mSec latencies or greater indicates a possible over-utilized, misbehaving, or mis-configured disk array.
**Kernel Disk Command Latency – It should be very small in comparison to the Physical Device Command Latency, and it should be close to zero. A high Kernel Command Latency indicates there is a lot of queuing in the ESXi kernel.

*The SAN design and configuration must meet the following Windows performance counters on UCCE VMs:
**AverageDiskQueueLength must remain less than (1.5 ∗ (the total number of disks in the array)).
** %Disktime must remain less than 60%. 

*Any given SAN array must be designed to have an IOPS capacity exceeding the sum of the IOPS required for all resident UC applications. Unified CCE applications should be designed for the 95th percentile IOPS values published in this wiki. For other UC applications, please follow their respective IOPS requirements & guidelines.

 

See below for an example of SAN configuration for Rogger 2000 agent deployment. This example corresponds to the 2000 agent Sample CCE Deployment for UCS B-Series described in: [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Coresidency_and_Sample_Deployments Unified CCE Component Coresidency and Sample Deployments].

== Example of SAN Configuration for Unified CCE ROGGER Deployment up to 2000 Agents ==

The following SAN configuration was a tested design, though generalized here for illustration. It is not the only possible way in which to provision SAN arrays, LUNs, and datastores to UC applications. However, you must adhere to the guidance given earlier in this section (above).

=== Rogger Side A ===

[[Image:RoggerSideA.jpg]]

=== Rogger Side B ===

[[Image:RoggerSideB.jpg]]

= Steps for Installing/Migrating Unified CCE Components on Virtual Machines =

Follow the steps and references below to install the Unified CCE components on virtual machines. You can use these instructions to install or upgrade systems running with Unified CCE 8.0(2) and later. You can also use these instructions to migrate virtualized systems from Unified CCE 7.5(x) to Unified CCE 8.0(2) or later, including the Avaya PG and other selected TDM PGs that were supported on Unified CCE 7.5(x). Not all TDM PGs supported in Unified CCE 7.5(x) are supported in Unified CCE 8.0(x). For more information, see [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release 8.0(1).]

#Acquire the supported servers for Unified CCE 8.0(x).
#*Cisco UCS servers are specified in the [http://docwiki-dev.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE&oldid=63654#Hardware_Requirements_for_Unified_CCE_Virtualized_Systems Hardware Requirements for Unified CCE Virtualized Systems] section.
#*MCS-7845-I3-CCE2 is specified in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release 8.0(1).]
#*If there are PG VMs that are running on the following older MCS servers, MCS-7845-H2 or MCS-7845-I2, replace these servers with supported servers.
#Install, setup, and configure the servers.
#Configure the network. See reference at [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#UCS_Network_Configuration UCS Network Configuration]. {{note |Configuring the network for the MCS servers is the same as configuring the network for the UCS C-Series servers.}}
#If VMware VirtualCenter is used for virtualization management, install or update to VMware vCenter Server 4.0 or later.
#Install and Boot VMWare ESXi. See the [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html Cisco UCS B-Series Blade Servers VMware Installation Guide] or the [http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/os/vmware/install/vmware_install_c.html Cisco UCS C-Series Servers VMware Installation Guide]. On C-Series servers or MCS servers, you must configure the ESXi datastore block size for the Administration & Data Server. See [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Configuring_the_ESXi_Data_Store_Block_Size_for_Administration_and_Data_Server Configuring the ESXi Data Store Block Size for Administration and Data Server] for instructions.
#Create the Unified CCE virtual machines from the OVA templates. See reference at [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Creating_Virtual_Machines_from_OVA_VM_Templates Creating Virtual Machines from OVA VM Templates]. This is a requirement for all component running Unified CCE 8.0(2) and later. In Unified CCE 7.5(x), this is not a requirement.
#Install VMware Tools with the ESXi version on the virtual machines. Install the same version of VMware Tools as the ESXi software on the virtual machines.
#Install Windows OS and SQL Server (for Logger and HDS components) on the created virtual machines. {{note| Microsoft Windows Server 2003 ''Standard Edition'' and Microsoft SQL Server 2005 ''Standard Edition'' should be used for virtual machine guests. See related information in the links below.}}
#Install or migrate the Unified CCE Software components on the configured virtual machines, using Fresh Install or Tech Refresh Upgrade, as described in [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE#Installing_Unified_CCE_Components_on_Virtual_Machines Installing Unified CCE components on virtual machines] and [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCE#Migrating_Unified_CCE_Components_to_Virtual_Machines Migrating Unified CCE components].

= Unified CCE Component '''VM Coresidency''' and '''Sample Deployments''' =

You can have one or more Unified CCE VMs coresident on the same ESXi server (for example, B200M2 blade or C210M2 rack mount server).  However, you must follow the rules described below:

:*You can have any number of Unified CCE virtual machines and combination of coresidency of Unified CCE virtual machines on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation does not over commit the available ESXi server computing resources. 
:*You must not have CPU overcommit on the ESXi server that is running Unified CCE realtime application components.  The total number of vCPUs among all the virtual machines on an ESXi host must not be greater than the total number of CPUs available on the ESXi server.  In the case of the Cisco UCS B-200 and C-210, the total number of CPUs available is 8.
:*You must not have memory overcommit on the ESXi host running UC realtime applications.  You must allocate a minimum 2GB of memory for the ESXi kernel.  For example, if an ESXi server on B-200 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel you have 34GB available for the virtual machines.  The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.
:*VM coresidency with Unified Communications '''and''' third party applications (for example, WFM) is '''not''' supported unless it is described in the following subsection.

The following table shows how Unified CCE components can be coresident on the same ESXi server. '''A diamond indicates that coresidency is allowed'''. For example, the first row shows that Unified Communications Applications can not be colocated with Contact Center Tier 1 Applicaitons. The third row shows that Third Party Applications can only be colocated with Contact Center Tier 3 Applications.

{| class="wikitable FCK__ShowTableBorders"
|-
! Unified CCE Component Coresidency
! Contact Center Tier 1 Applications
! Contact Center Tier 2 Applications
! Contact Center Tier 3 Applications
! Unified Communications Applications
! Third Party Applications
|-
| '''Contact Center Tier 1 Applications: Router, Logger, Peripheral Gateway, ADS-HDS'''
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
|
|
|-
| '''Contact Center Tier 2 Applications: CVP Call + VXML Server, CVP Reporting Server, CUIC, CCMP''' 
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
| align="center" |
|-
| '''Contact Center Tier 3 Applications: ADS/AW (any non-HDS), Admin Client, Support Tools, Windows AD DC, CVP Ops/OAMP Server, CVP Media Server, SocialMiner''' 
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
|-
| '''Unified Communications Applications: Communications Manager, Contact Center Express, IPIVR, CUP, Unity, Unity Connection, MediaSense''' 
| align="center" |
| align="center" | ♦
| align="center" | ♦
| align="center" | ♦
|
|-
|
|}
{{note|'''EXCEPTIONS''' to the above VM co-residency table:}}
:*On a '''C-Series''' server, the HDS '''cannot''' co-reside with a Router, Logger, or a PG.
:*'''PG''' (in CCE solutions up to 1000 CTIOS agents or 500 CAD agents) VMs '''can''' be co-resident with UCM/CUP/IPIVR VMs on the same ESXi host/server.
 

{{note|If Cisco Support determines that a third party application deployed coresident with a Contact Center Tier 3 application causes that application to fail in performance or function, the customer must address the issue by moving the applications to other servers as necessary to alleviate the failure.}}

For coresidency restrictions specific to individual Unified Communications applications that run on VMs, see the Unified Communications Virtualization Sizing Guideline docwiki.

The following section depicts the CCE sample UCS deployments compliant to the coresidency rules described above.

== Sample CCE Deployments ==

'''Notes'''

#The ESXi Servers listed in these tables can be deployed on either a B-Series or C-Series hardware platform.
#Although the sample deployments in these tables reflect the C-Series restriction that the HDS cannot coreside with a Router, Logger, or a PG, this restriction is '''not''' present on a B-Series hardware platform.
#For deployments where Historical Data Servers (HDSs) are coresident, two RAID 5 groups (one for each HDS) are recommended.
#Any deployment > 2k agents requires at least 2 chassis
#It may be preferable to place your domain controller on bare metal rather than in the UCS B-series chassis itself. When a power failure occurs, the vCenter login credentials are dependent on Active Directory, leading to a potential chicken-and-egg problem if the domain controller is down as well.
#ACE (for CUIC) and CUSP (for CVP) components are not supported virtualized on UCS; these components are deployed on separate hardware. Please review the product SRND for more details.
#'''12,000''' agent is supported from 8.5(3) version onwards and '''requires''' Windows 2008 R2 '''Enterprise edition''' and SQL Server 2005 '''Enterprise Edition'''. Refer to BOM for more details

=== ROGGER Example 1 ===

{| class="wikitable" border="1"
|+ ROGGER (up to 450 CTIOS Agents, or 297 CAD Agents) with 150 IPIVR or 150 CVP ports (N+N), optional 50 CUIC reporting users, as examples
|-
! colspan="4" | Chassis X (B series)/ Rack of C series rack mount Servers
! colspan="4" | Chassis Y (B series)/ Rack of C series rack mount Servers
|-
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
|-
| rowspan="4" | ESXi Server A-1
| Rogger A
| 4
| 4
| rowspan="4" | ESXi Server B-1 
| Rogger B
| 4
| 4
|-
| Agent PG A (generic PG w/ optional VRU), CTIOS/CAD, optional MR PG
| 1
| 2
| Agent PG B (generic PG w/ optional VRU), CTIOS/CAD, optional MR PG
| 1
| 2
|- style="background: rgb(255,224,200)"
| Domain Controller A
| 1
| 2
| Domain Controller B
| 1
| 2
|-
| style="background: rgb(255,224,200)" | Support Tools 
| style="background: rgb(255,224,200)" | 1
| style="background: rgb(255,224,200)" | 2
| CVP Op Svr
| 2 
| 2 
|-
| rowspan="2" | ESXi Server A-2
| AW-HDS-DDS 1
| 4
| 4
| rowspan="2" | ESXi Server B-2
| AW-HDS-DDS 2
| 4
| 4
|- style="background: rgb(255,224,200)"
| CUIC 1
| 4
| 6
| CUIC 2
| 4
| 6
|-
| rowspan="3" | ESXi Server A-3
| UCM Subscriber 1
| 2
| 6
| rowspan="3" | ESXi Server B-3
| UCM Subscriber 2
| 2
| 6
|-
| UCM Publisher
| 2
| 6
| 
| 
| 
|- style="background: rgb(255,224,200)"
| IPIVR 1 or CUP Srv 1
| 2
| 4
| IPIVR 2 or CUP Srv 2
| 2
| 4
|-
| rowspan="2" | ESXi Server A-4
| CVP Call+VXML Srv 1
| 4
| 4
| rowspan="2" | ESXi Server B-4
| CVP Call+VXML Srv 2
| 4
| 4
|- style="background: rgb(255,224,200)"
| CVP Rpt Srv 1
| 4
| 4
| CVP Media Server
| 2
| 2
|-
! colspan="8" | '''Legend'''
|-
| Not shaded
| colspan="7" | Required
|- style="background: rgb(255,224,200)"
| Shaded
| colspan="7" | Optional
|}

=== ROGGER Example 2 ===

{| class="wikitable" border="1"
|+ ROGGER (up to 2,000 CTIOS Agents, or up to 1,000 CAD Agents) with 600 IPIVR or 900 CVP ports (N+N), optional 200 CUIC reporting users, CCMP 1,500 users, as examples
|-
! colspan="4" | Chassis X (B series)/ Rack of C series rack mount Servers
! colspan="4" | Chassis Y (B series)/ Rack of C series rack mount Servers
|-
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
|-
| rowspan="4" | ESXi Server A-1
| Rogger A
| 4
| 4
| rowspan="4" | ESXi Server B-1
| Rogger B
| 4
| 4
|-
| Agent PG A (generic PG w/ optional VRU, CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| Agent PG B (generic PG w/ optional VRU, CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|- style="background: rgb(255,224,200)"
| Domain Controller A
| 1
| 2
| Domain Controller B
| 1
| 2
|- style="background: rgb(255,224,200)"
| Support Tools 
| 1 
| 2 
|-
| rowspan="2" | ESXi Server A-2
| AW-HDS-DDS 1
| 4
| 4
| rowspan="2" | ESXi Server B-2
| AW-HDS-DDS 2
| 4
| 4
|- style="background: rgb(255,224,200)"
| AW-HDS-DDS 3 
| 4
| 4
| AW-HDS-DDS 4 
| 4
| 4
|-
| rowspan="4" | ESXi Server A-3 
| UCM Subscriber 1
| 2
| 6
| rowspan="4" | ESXi Server B-3 
| UCM Subscriber 3
| 2
| 6
|-
| UCM Subscriber 2 
| 2
| 6
| UCM Subscriber 4 
| 2 
| 6 
|-
| UCM Publisher
| 2 
| 6 
| CVP Op Srv 
| 2 
| 2 
|- style="background: rgb(255,224,200)"
| IPIVR 1 or CUP Srv 1 
| 2 
| 4 
| IPIVR 2 or CUP Srv 2 
| 2 
| 4 
|-
| rowspan="2" | ESXi Server A-4
| CVP Call+VXML Srv 1
| 4
| 4
| rowspan="2" | ESXi Server B-4
| CVP Call+VXML Srv 2
| 4
| 4
|- style="background: rgb(255,224,200)"
| CVP Rpt Srv 1
| 4
| 4
| CVP Rpt Srv 2
| 4
| 4
|-
| rowspan="2" | ESXi Server A-5 
| style="background: rgb(255,224,200)" | CUIC1
| style="background: rgb(255,224,200)" | 4 
| style="background: rgb(255,224,200)" | 6 
| rowspan="2" | ESXi Server B-5 
| style="background: rgb(255,224,200)" | CCMP (all in one)
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
|- style="background: rgb(255,224,200)"
| CVP Media Server
| 2
| 2
| CUIC 2
| 4
| 6
|-
! colspan="8" | '''Legend'''
|-
| Not shaded
| colspan="7" | Required
|- style="background: rgb(255,224,200)"
| Shaded
| colspan="7" | Optional
|}

=== ROGGER Example 3 ===

{| style="width: 1057px; height: 574px" class="wikitable" border="1"
|+ ROGGER (up to 4,000 CTIOS Agents, or up to 2,000 CAD Agents) with 1,200 IPIVR or 1,800 CVP ports (N+N), optional 200 CUIC reporting users, CCMP 1,500 users, as examples
|-
! colspan="4" | Chassis X (B series)/ Rack of C series rack mount Servers
! colspan="4" | Chassis Y (B series)/ Rack of C series rack mount Servers
|-
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
|-
| rowspan="2" | ESXi Server A-1
| Rogger A
| 4
| 4
| rowspan="2" | ESXi Server B-1
| Rogger B
| 4
| 4
|-
| Agent PG 1A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| Agent PG 1B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| rowspan="4" | ESXi Server A-2 
|-
| VRU PG A
| 2
| 2
| rowspan="3" | ESXi Server B-2 
| VRU PG B 
| 2
| 2
|-
| style="background: rgb(255,224,200)" | Support Tools 
| style="background: rgb(255,224,200)" | 1 
| style="background: rgb(255,224,200)" | 2 
| CVP Op Srv
| 2 
| 2 
|- style="background: rgb(255,224,200)"
| Domain Controller A 
| 1
| 2
| Domain Controller B 
| 1
| 2
|-
| rowspan="2" | ESXi Server A-3
| width="145" | Agent PG 2A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| rowspan="2" | ESXi Server B-2 
| Agent PG 2B (CTIOS/CAD, optional MR PG, SIP Dialer)
| width="145" | 2
| 4
|- style="background: rgb(255,224,200)"
| CVP Rpt Srv 1
| 4
| 4
| CVP Rpt Srv 2
| 4
| 4
|-
| rowspan="2" | ESXi Server A-4
| AW-HDS-DDS 1
| 4
| 4
| rowspan="2" | ESXi Server B-3
| AW-HDS-DDS 2
| 4
| 4
|- style="background: rgb(255,224,200)"
| AW-HDS-DDS 3 
| 4
| 4
| AW-HDS-DDS 4 
| 4
| 4
|-
| rowspan="4" | ESXi Server A-5
| UCM Subscriber 1
| 2
| 6
| rowspan="4" | ESXi Server B-4
| UCM Subscriber 2
| 2
| 6
|-
| UCM Subscriber 3
| 2
| 6
| UCM Subscriber 4
| 2
| 6
|-
| UCM Publisher
| 2
| 6
| 
| 
| 
|- style="background: rgb(255,224,200)"
| IPIVR 1
| 2
| 4
| IPIVR 3
| 2
| 4
|-
| rowspan="4" | ESXi Server A-6
| UCM Subscriber 5
| 2
| 6
| rowspan="4" | ESXi Server B-5
| UCM Subscriber 6
| 2
| 6
|-
| UCM Subscriber 7
| 2
| 6
| UCM Subscriber 8
| 2
| 6
|- style="background: rgb(255,224,200)"
| IPIVR 2 
| 2
| 4
| IPIVR 4 
| 2
| 4
|- style="background: rgb(255,224,200)"
| CUP Server 1 
| 2
| 4
| CUP Server 2 
| 2
| 4
|-
| rowspan="2" | ESXi Server A-7
| CVP Call+VXML Srv 1
| 4
| 4
| rowspan="2" | ESXi Server B-5
| CVP Call+VXML Srv 2
| 4
| 4
|-
| CVP Call+VXML Srv 3
| 4
| 4
| CVP Call+VXML Srv 4
| 4
| 4
|-
| rowspan="2" | ESXi Server A-7 
| style="background: rgb(255,224,200)" | CVP Media Server
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 2
| rowspan="2" | ESXi Server B-6 
| style="background: rgb(255,224,200)" | CUIC 2
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 6
|- style="background: rgb(255,224,200)"
| CUIC 1
| 4
| 6
| CCMP (all in one)
| 4
| 4
|-
| colspan="9" | 
|-
| Not shaded
| colspan="7" | Required
|- style="background: rgb(255,224,200)"
| Shaded
| colspan="7" | Optional
|}

=== Router/Logger Example 1 ===

{| style="width: 1057px; height: 574px" class="wikitable" border="1"
|+ Router/Logger (up to 8,000 CTIOS Agents, or up to 4,000 CAD Agents) with 3,600 CVP ports (N+N), optional 400 CUIC reporting users, CCMP 8,000 users, as examples
|-
! colspan="4" | Chassis X (B series)/ Rack of C series rack mount Servers
! colspan="4" | Chassis Y (B series)/ Rack of C series rack mount Servers
|-
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
|-
| rowspan="5" | ESXi Server A-1
| width="145" | Router A
| 2
| 4
| rowspan="5" | ESXi Server B-1
| width="145" | Router B
| 2
| 4
|-
| width="145" | Agent PG 1A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| width="145" | Agent PG 1B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| width="145" | Agent PG 3A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| width="145" | Agent PG 3B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|- style="background: rgb(255,224,200)"
| width="145" | Domain Controller A 
| 1
| 2
| width="145" | Domain Controller B 
| 1
| 2
|-
| style="background: rgb(255,224,200)" | Support Tools 
| style="background: rgb(255,224,200)" | 1
| style="background: rgb(255,224,200)" | 2
| width="145" |  
|  
|  
|-
| rowspan="3" | ESXi Server A-2
| width="145" | Logger A
| 4
| 4
| rowspan="3" | ESXi Server B-2
| width="145" | Logger B
| 4
| 4
|-
| width="145" | Agent PG 2A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| width="145" | Agent PG 2B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| width="145" | Agent PG 4A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| width="145" | Agent PG 4B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| rowspan="2" | ESXi Server A-3
| width="145" | HDS-DDS 1
| 4
| 4
| rowspan="2" | ESXi Server B-3
| width="145" | HDS-DDS 2
| 4
| 4
|-
| width="145" | AW-HDS 1
| 4
| 4
| width="145" | AW-HDS 2
| 4
| 4
|-
| rowspan="2" | ESXi Server A-4
| style="background: rgb(255,224,200)" | AW-HDS 3 
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
| rowspan="2" | ESXi Server B-4
| style="background: rgb(255,224,200)" | AW-HDS 4 
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
|- style="background: rgb(255,224,200)"
| width="145" | AW-HDS 5 
| 4
| 4
| width="145" | AW-HDS 6 
| 4
| 4
|-
| rowspan="4" | ESXi Server A-5
| width="145" | UCM 1 Subscriber 1
| 2
| 6
| rowspan="4" | ESXi Server B-5
| width="145" | UCM 1 Subscriber 2
| 2
| 6
|-
| width="145" | UCM 2 Subscriber 1
| 2
| 6
| width="145" | UCM 2 Subscriber 2
| 2
| 6
|-
| width="145" | UCM 1 Subscriber 3
| 2
| 6
| width="145" | UCM 1 Subscriber 4
| 2
| 6
|-
| width="145" | UCM 2 Subscriber 3
| 2
| 6
| width="145" | UCM 2 Subscriber 4
| 2
| 6
|-
| rowspan="4" | ESXi Server A-6
| width="145" | UCM 1 Subscriber 5
| 2
| 6
| rowspan="4" | ESXi Server B-6
| width="145" | UCM 1 Subscriber 6
| 2
| 6
|-
| width="145" | UCM 2 Subscriber 5
| 2
| 6
| width="145" | UCM 2 Subscriber 6
| 2
| 6
|-
| width="145" | UCM 1 Subscriber 7
| 2
| 6
| width="145" | UCM 1 Subscriber 8
| 2
| 6
|-
| width="145" | UCM 2 Subscriber 7
| 2
| 6
| width="145" | UCM 2 Subscriber 8
| 2
| 6
|-
| rowspan="2" | ESXi Server A-7 
| width="145" | UCM Publisher 1
| 2
| 6
| rowspan="2" | ESXi Server B-7 
| style="background: rgb(255,224,200)" | CVP Op Srv
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 2
|- style="background: rgb(255,224,200)"
| width="145" | CUP Server 1 
| 2
| 4
| width="145" | CUP Server 2 
| 2
| 4
|-
| rowspan="2" | ESXi Server A-8
| width="145" | UCM Publisher 2
| 2
| 6
| rowspan="2" | ESXi Server B-8
| style="background: rgb(255,224,200)" | CVP Rpt Srv 2
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
|-
| style="background: rgb(255,224,200)" | CVP Rpt Srv 1
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
| width="145" | 
| 
| 
|-
| rowspan="2" | ESXi Server A-9
| width="145" | CVP Call+VXML Srv 1
| 4
| 4
| rowspan="2" | ESXi Server B-9
| width="145" | CVP Call+VXML Srv 2
| 4
| 4
|-
| width="145" | CVP Call+VXML Srv 3
| 4
| 4
| width="145" | CVP Call+VXML Srv 4
| 4
| 4
|-
| rowspan="2" | ESXi Server A-10
| width="145" | CVP Call+VXML Srv 5
| 4
| 4
| rowspan="2" | ESXi Server B-10
| width="145" | CVP Call+VXML Srv 6
| 4
| 4
|-
| width="145" | CVP Call+VXML Srv 7
| 4
| 4
| width="145" | CVP Call+VXML Srv 8
| 4
| 4
|-
| rowspan="2" | ESXi Server A-11
| style="background: rgb(255,224,200)" | CVP Media Server A 
| style="background: rgb(255,224,200)" | 2 
| style="background: rgb(255,224,200)" | 2 
| rowspan="2" | ESXi Server B-11 
| style="background: rgb(255,224,200)" | CVP Media Server B 
| style="background: rgb(255,224,200)" | 2 
| style="background: rgb(255,224,200)" | 2 
|-
| VRU PG A 
| 2 
| 2 
| VRU PG B 
| 2 
| 2 
|-
| rowspan="2" | ESXi Server A-12
| style="background: rgb(255,224,200)" | CUIC 1 
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 6
| rowspan="2" | ESXi Server B-12 
| style="background: rgb(255,224,200)" | CUIC 2 
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 6
|- style="background: rgb(255,224,200)"
| width="145" | CUIC 3 
| 4
| 6
| width="145" | CUIC 4 
| 4
| 6
|-
| ESXi Server A-13 
| style="background: rgb(255,224,200)" | CCMP DB 
| style="background: rgb(255,224,200)" | 8
| style="background: rgb(255,224,200)" | 4
| ESXi Server B-13
| style="background: rgb(255,224,200)" | CCMP Web/App Svr 
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
|-
! colspan="8" | '''Legend'''
|-
| Not shaded
| colspan="7" | Required
|- style="background: rgb(255,224,200)"
| Shaded
| colspan="7" | Optional
|}

 

 

  

=== Router/Logger Example 2 ===

 Router/Logger (up to 12,000 CTIOS Agents) with 3,600 CVP ports (N+N), optional 400 CUIC reporting users, CCMP 8,000 users, as examples

{| border="1" cellspacing="1" cellpadding="1" width="1057"
|-
| colspan="4" | '''Chassis X (B series)/ Rack of C series rack mount Servers'''
| colspan="4" | '''Chassis Y (B series)/ Rack of C series rack mount Servers'''
|-
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
| '''ESXi Server'''
| '''Component'''
| '''#vCPU'''
| '''RAM (GB)'''
|-
| rowspan="2" | ESXi Server A-1
| Logger A
| 4
| 8
| rowspan="2" | ESXi Server B-1
| Logger B
| 4
| 8
|-
| Router A
| 4
| 8
| Router B
| 4
| 8
|-
| rowspan="3" | ESXi Server A-2
| Agent PG 1A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| rowspan="3" | ESXi Server B-2
| Agent PG 1B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| Agent PG 3A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| Agent PG 3B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| Agent PG 5A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| Agent PG 5B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| rowspan="3" | ESXi Server A-3
| Agent PG 2A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| rowspan="3" | ESXi Server B-3
| Agent PG 2B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| Agent PG 4A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| Agent PG 4B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| Agent PG 6A (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
| Agent PG 6B (CTIOS/CAD, optional MR PG, SIP Dialer)
| 2
| 4
|-
| rowspan="4" | ESXi Server A-4
| HDS-DDS 1
| 4
| 8
| rowspan="4" | ESXi Server B-4
| HDS-DDS 2
| 4
| 8
|-
| AW-HDS 1
| 4
| 8
| AW-HDS 2
| 4
| 8
|-
| AW-HDS 3
| 4
| 8
| AW-HDS 4
| 4
| 8
|-
| AW-HDS 5
| 4
| 8
| AW-HDS 6
| 4
| 8
|-
| rowspan="3" | ESXi Server A-5
| UCM 1 Subscriber 1
| 2
| 6
| rowspan="3" | ESXi Server B-5
| UCM 1 Subscriber 2
| 2
| 6
|-
| UCM 2 Subscriber 1
| 2
| 6
| UCM 2 Subscriber 2
| 2
| 6
|-
| UCM 3 Subscriber 1
| 2
| 6
| UCM 3 Subscriber 2
| 2
| 6
|-
| rowspan="3" | ESXi Server A-6
| UCM 1 Subscriber 3
| 2
| 6
| rowspan="3" | ESXi Server B-6
| UCM 1 Subscriber 2
| 2
| 6
|-
| UCM 2 Subscriber 3
| 2
| 6
| UCM 2 Subscriber 2
| 2
| 6
|-
| UCM 3 Subscriber 3
| 2
| 6
| UCM 3 Subscriber 2
| 2
| 6
|-
| rowspan="3" | ESXi Server A-7
| UCM 1 Subscriber 5
| 2
| 6
| rowspan="3" | ESXi Server B-7
| UCM 1 Subscriber 2
| 2
| 6
|-
| UCM 2 Subscriber 5
| 2
| 6
| UCM 2 Subscriber 2
| 2
| 6
|-
| UCM 3 Subscriber 5
| 2
| 6
| UCM 3 Subscriber 2
| 2
| 6
|-
| rowspan="3" | ESXi Server A-8
| UCM 1 Subscriber 7
| 2
| 6
| rowspan="3" | ESXi Server B-8
| UCM 1 Subscriber 2
| 2
| 6
|-
| UCM 2 Subscriber 7
| 2
| 6
| UCM 2 Subscriber 2
| 2
| 6
|-
| UCM 2 Subscriber 7
| 2
| 6
| UCM 3 Subscriber 2
| 2
| 6
|-
| rowspan="4" | ESXi Server A-9
| style="background: rgb(255,224,200)" | Domain Controller
| style="background: rgb(255,224,200)" | 1
| style="background: rgb(255,224,200)" | 2
| rowspan="4" | ESXi Server B-9
| style="background: rgb(255,224,200)" | Domain Controller
| style="background: rgb(255,224,200)" | 1
| style="background: rgb(255,224,200)" | 1
|-
| UCM Publisher 1
| 2
| 6
| style="background: rgb(255,224,200)" | CVP Op Srv
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 2
|-
| style="background: rgb(255,224,200)" | CUP Server 1 
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | CUP Server 2 
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 4
|-
| Administration Server - AW
| 1
| 2
| Administration Server - AW
| 1
| 2
|-
| rowspan="2" | ESXi Server A-10
| UCM Publisher 2
| 2
| 6
| rowspan="2" | ESXi Server B-10
| style="background: rgb(255,224,200)" | CVP Rpt Srv 2
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
|-
| style="background: rgb(255,224,200)" | CVP Rpt Srv 1
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
| UCM Publisher 3
| 2
| 6
|-
| rowspan="2" | ESXi Server A-11
| CVP Call+VXML Srv 1
| 4
| 4
| rowspan="2" | ESXi Server B-11
| CVP Call+VXML Srv 2
| 4
| 4
|-
| CVP Call+VXML Srv 3
| 4
| 4
| CVP Call+VXML Srv 4
| 4
| 4
|-
| rowspan="2" | ESXi Server A-12
| CVP Call+VXML Srv 5
| 4
| 4
| rowspan="2" | ESXi Server B-12
| CVP Call+VXML Srv 6
| 4
| 4
|-
| CVP Call+VXML Srv 7
| 4
| 4
| CVP Call+VXML Srv 8
| 4
| 4
|-
| rowspan="2" | ESXi Server A-13
| CVP Call+VXML Srv 9
| 4
| 4
| rowspan="2" | ESXi Server B-13
| CVP Call+VXML Srv 10
| 4
| 4
|-
| CVP Call+VXML Srv 11
| 4
| 4
| CVP Call+VXML Srv 12
| 4
| 4
|-
| rowspan="2" | ESXi Server A-14
| style="background: rgb(255,224,200)" | CVP Media Server A
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 2
| rowspan="2" | ESXi Server B-14
| style="background: rgb(255,224,200)" | CVP Media Server B
| style="background: rgb(255,224,200)" | 2
| style="background: rgb(255,224,200)" | 2
|-
| VRU PG A
| 2
| 2
| VRU PG B
| 2
| 2
|-
| rowspan="2" | ESXi Server A-15
| CUIC 1 
| 4
| 6
| rowspan="2" | ESXi Server B-15
| CUIC 2 
| 4
| 6
|-
| CUIC 3 
| 4
| 6
| CUIC 4
| 4
| 6
|-
| rowspan="2" | ESXi Server A-16
| CUIC 5
| 4
| 6
| rowspan="2" | ESXi Server B-16
| CUIC 6
| 4
| 6
|-
| CUIC 7
| 4
| 6
| CUIC 8
| 4
| 6
|-
| ESXi Server A-17
| style="background: rgb(255,224,200)" | CCMP DB
| style="background: rgb(255,224,200)" | 8
| style="background: rgb(255,224,200)" | 4
| ESXi Server B-17
| style="background: rgb(255,224,200)" | CCMP Web/App Svr 
| style="background: rgb(255,224,200)" | 4
| style="background: rgb(255,224,200)" | 4
|-
! colspan="8" | '''Legend'''
|-
| Not shaded
| colspan="7" | Required
|- style="background: rgb(255,224,200)"
| Shaded
| colspan="7" | Optional
|}

 

 

= Hybrid Deployment Options =

Some Unified Contact Center deployments are supported in a "hybrid" fashion whereby certain components must be deployed on (bare-metal) Media Convergence Servers (MCS) or generic servers, and other components are deployed in virtual machine guests on Unified Computing System (UCS) or MCS servers. The following sub-sections provide further details on these hybrid deployment options.

== Cisco Unified Contact Center Hosted ==

*NAM Rogger is deployed on a (bare-metal) quad CPU server as specified in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release 8.0(1).]
*Each customer instance central controller (CICM) connecting to the NAM may be deployed in its own virtual machine as a Rogger or separate Router/Logger pair on UCS hardware. Multiple CICM instances are not supported collocated in one VM. Existing published rules and capacities apply to CICM Rogger and Router/Logger VMs. (Note: CICMs are not supported on bare-metal UCS.)
*As in Enterprise deployments, each Agent PG is deployed in its own virtual machine. Multi-instance Agent PGs are not supported in a single VM. Existing published rules and capacities apply to PGs in Hosted deployments.

== Parent/Child Deployments ==

*The parent ICM is deployed on (bare-metal) servers as specified in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/user/guide/icm80bom.pdf Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted, Release 8.0(1).].
*The Unified Contact Center Enterprise (or Express) child may be deployed virtualized according to existing published VM requirements.
*The Unified Contact Center Enterprise Gateway PG and System PG are each deployed in its own virtual machine; agent capacity (and resources allocated to the VM) are the same as the Unified CCE Agent PG @ 2,000 agent capacity. Use the same virtual machine OVA template to create the CCE Gateway or System PG VM.

= Cisco Unified CCE-Specific Information for OVA Templates =

See the following websites for more information: 

*[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates)#Unified_Contact_Center_Enterprise Unified Communications Virtualization Downloads (including OVA/OVF Templates).]
*[http://www.cisco.com/cisco/software/release.html?mdfid=268439622&release=1.1&relind=AVAILABLE&flowid=5210&softwareid=283914286&rellifecycle=&reltype=latest Unified CCE OVA Templates]

 

== Creating Virtual Machines by Deploying the OVA Templates ==

In the vSphere client, perform the following steps to deploy the Virtual machines.

#Highlight the host or cluster to which you wish the VM to be deployed.
#Select '''File''' > '''Deploy OVF Template'''.
#Click the '''Deploy from File''' radio button and specify the name and location of the file you downloaded in the previous section '''OR '''click the '''Deploy from URL''' radio button and specify the complete URL in the field, then click '''Next'''.
#Verify the details of the template, and click '''Next'''.
#Give the VM you are about to create a name, and choose an inventory location on your host, then click '''Next'''.
#Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click '''Next'''.
#Choose a virtual network for the VM, then click '''Next'''.
#Verify the deployment settings, then click '''Finish'''.

== Notes ==

:*VM CPU affinity is not supported. You don't need to set CPU affinity for the VMs that are running Unified CCE applications on the VMware ESXi on UCS platform.
:*VM resource Reservation - VM resource reservation is not supported for the VMs that are running Unified CCE applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations.
:*You cannot change the computing resource configuration of your VM at any time.
:*You can never go below the minimum VM computing resource requirements as defined in the OVA templates.
:*ESXi Server hyperthread is enabled by default.

== Preparing for Windows Installation ==

In the vSphere client, perform the following steps to prepare for operating system installation.

#Right click on the virtual machine you want to edit and select '''Edit Settings'''. A Virtual Machine Properties dialog appears.
#On the Hardware tab, select '''CD/DVD Drive 1'''. Under Device Type, select '''Datastore ISO File''' and enter the location of the operating system ISO.
#Click '''OK''' to save setting changes.
#Power up your VM and continue with operating system installation.

 

= Remote Control of the Virtual Machines =

For administrative tasks, you can use either Windows Remote Desktop or the VMware Infrastructure Client for remote control. The contact center supervisor can access the ClientAW VM using Windows Remote Desktop.

= Installing VMware Tools =

The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Please refer to VMware documentation for instructions on installing or upgrading VMware Tools on the VM with Windows operating system.

= Installing Unified CCE Components on Virtual Machines =

Install the Unified CCE components after you create and configure the virtual machine. Installation of the Unified CCE components on a virtual machine is the same as the installation of the components on physical hardware.

Refer to the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_installation_guides_list.html Unified CCE documentation] for the steps to install Unified CCE components. You can install the supported Virus Scan software, the Cisco Security Agent(CSA), or any other software in the same way as on physical hardware.

= Migrating Unified CCE Components to Virtual Machines =

Migrate the Unified CCE components from physical hardware or another virtual machine after you create and configure the virtual machine. Migration of these Unified CCE software components to a VM is the same as the migration of the components to new physical hardware and follows existing policies. It requires a Tech Refresh as described in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/installation/guide/icm80ug.pdf Upgrade Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted Release 8.0(1)].

= Configuring the ESXi Data Store Block Size for Administration and Data Server =

This section is applicable to storing Virtual Machines on C-210 local storage. The C-210 Server comes with a default local storage configured with two sets of RAID groups. Disk 1-2 is RAID 1, while the remaining disks (3-10) are RAID 5.

The creation of the virtual machine for the Unified CCE Administration and Data Server requires a large virtual disk size. You must follow the steps described below to configure the ESXi data store block size to 2MB for it to handle the Unified CCE Administration and Data Server virtual disk size requirement before you deploy the OVAs for the following Unified CCE components:

:*AW-HDS
:*AW-HDS-DDS
:*HDS-DDS

 Steps to configure the ESXi data store block size to 2MB:

#After you install ESXi on the first disk array group (RAID 1 with disk 1 and disk 2), boot ESXi 4.0 and use VMware vSphere Client to connect to the ESXi host.
#On the Configuration tab for the host, select Storage in the box labeled Hardware. Select the second disk array group with RAID-5 configuration, and you will see in the formatting of “Datastore Details” that the block size is by default 1MB.
#Right-click on this data store and delete it. We will add the data store back in the following steps.
#Click on the “Add Storage…” and select the Disk/LUN.
#The data store that was just deleted will now be available to add, select it.
#In the configuration for this data store you will now be able to select the block size, select 2MB, and finish the adding of the storage to the ESXi host. This storage is now available for deployment of the virtual machines that requires large disk size, such as the Administration and Data Servers.

= Timekeeping Best Practices for Windows =

You should follow the best practices outlined in the VMware Knowledge Base article [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1318 VMware KB: Timekeeping best practices for Windows].

*ESXi hosts and domain controllers should synchronize the time from the same NTP source.
*When Unified CCE virtual machines join the domain, they synchronize the time with the domain controller automatically using w32time.
*Be sure that '''Time synchronization between the virtual machine and the host operating system''' in the VMware Tools tool box GUI of the Windows Server 2003 guest operating system remains deselected; this checkbox is deselected by default.

= System Performance Monitoring Using ESXi Counters =

:*Make sure that you follow VMware's ESXi best practices and SAN vendor's best practices for optimal system performance. 
:*VMware provides a set of system monitoring tools for the ESXi platform and the VMs. These tools are accessible through the VMware Infrastructure Client or through VirtualCenter.
:*You can use Windows Performance Monitor to monitor the performance of the VMs. Be aware that the CPU counters may not reflect the physical CPU usage since the Windows Operating System has no direct access to the physical CPU.
:*You can use Unified CCE Serviceability Tools and Unified CCE reports to monitor the operation and performance of the Unified CCE system.
:*The ESXi Server and the virtual machines must operate within the limit of the following ESXi performance counters.

You can use the following ESXi counters as performance indicators.

{| class="wikitable FCK__ShowTableBorders"
|-
! Category
! Object
! Measurement
! Units
! Description
! Performance Indication and Threshold
|-
| CPU
|
:*ESXi Server
:*VM

| CPU Usage (Average)
| Percent
| CPU Usage Average in percentage for:
:*ESXi server
:*Virtual machine

| Less than 60%.
|-
| CPU
|
:*ESXi Server Processor#
:*VM_vCPU#

| CPU Usage 0 - 7 (Average)
| Percent
| CPU Usage Average for:
:*ESXi server for processors 0 to 7
:*Virtual machine vCPUs

| Less than 60%
|-
| CPU
| VM
| CPU Ready
| mSec
| The time a virtual machine or other process waits in the queue in a ready-to-run state before it can be scheduled on a CPU.
| Less than 150 mSec. If it is greater than 150 mSec doing system failure, you should investigate and understand why the machine is so busy.
|-
| Memory
|
:*ESXi Server
:*VM

| Memory Usage (Average)
| Percent
| Memory Usage = Active/ Granted * 100
| Less than 80%
|-
| Memory
|
:*ESXi Server
:*VM

| Memory Active (Average)
| KB
| Memory that is actively used or being referenced by the guest OS and its applications. When it exceeds the amound of memory on the host, the server starts swap.
| Less than 80% of the Granted memory
|-
| Memory
|
:*ESXi Server
:*VM

| Memory Balloon (Average)
| KB
| ESXi use balloon driver to recover memory from less memory-intensive VMs so it can be used by those with larger active sets of memory.
| Since we do not over commit the memory, this should be 0 or very low. Note: ESXi performs memory ballooning before memory swap.
|-
| Memory
|
:*ESXi Server
:*VM

| Memory Swap used (Average)
| KB
| ESXi Server swap usage. Use the disk for RAM swap
| Since we do not over commit the memory, this should be 0 or very low
|-
| Disk
|
:*ESXi Server
:*VM

| Disk Usage (Average)
| KBps
| Disk Usage = Disk Read rate + Disk Write rate
| Ensure that your SAN is configured to handle this amount of disk I/O.
|-
| Disk
|
:*ESXi Server vmhba ID
:*VMbha ID

| Disk Usage Read rate 
| KBps
| Rate of reading data from the disk
| Ensure that your SAN is configured to handle this amount of disk I/O
|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

| Disk Usage Write rate
| KBps
| Rate of writing data to the disk
| Ensure that your SAN is configured to handle this amount of disk I/O
|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

| Disk Commands Issued
| Number
| Number of disk commands issued on this disk in the period.
| Ensure that your SAN is configured to handle this amount of disk I/O
|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

| Disk Command Aborts
| Number
| Number of disk commands aborted on this disk in the period. Disk command aborts when the disk array is taking too long to respond to the command. (Command timeout)
'''This counter should be zero. A non-zero value indicates storage performance issue.'''

|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

| Disk Command Latency
| mSec
| The average amount of time taken for a command from the perspective of a Gust OS. Disk Command Latency = Kernel Command Latency + Physical Device Command Latency.
| '''15ms latencies or greater indicates a possible over-utilized, misbehaving, or mis-configured disk array.'''
|-
| Disk
|
:*ESXi Server vmhba ID
:*VM vmhba ID

| Kernel Disk Command Latency
| mSec
| The average time spent in ESXi Server VMKernel per command
| '''Kernel Command Latency should be very small in comparison to the Physical Device Command Latency, and it should be close to zero.  Kernel Command Latency can be high, or even higher than the Physical Device Command Latency if there is a lot of queuing in the ESXi kernel.'''
|-
| Network
|
:*ESXi Server
:*VM

| Network Usage (Average)
| KBps
| Network Usage = Data receive rate + Data transmit rate
| Less than 30% of the available network bandwidth. For example, it should be less than 300Mps for 1G network.
|-
| Network
|
:*ESXi Server vmnic ID
:*VM vmnic ID

| Network Data Receive Rate
| KBps
| Less than 30% of the available network bandwidth. For example, it should be less than 300Mps for 1G network.
|-
| Network
|
:*ESXi Server vmnic ID
:*VM vmnic ID

| Network Data Transmit Rate
| KBps
| The average rate at which data is transmitted on this Ethernet port
| Less than 30% of the available network bandwidth.  For example, it should be less than 300Mps for 1G network.
|}

= System Performance Monitoring Using Windows Perfmon Counters =

You must comply with the best practices described in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/design/guide/uccesrnd80.pdf Cisco Unified Contact Center Enterprise Solution Reference Network Design(SRND), Release 8.0] section System Performance Monitoring, and in Chapter 8 Performance Counters in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/configuration/guide/icm80srvg.pdf Serviceability Best Practices Guide for Unified ICM/Contact Center Enterprise].

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

[[Category:Unified_Contact_Center_Enterprise]]

Unified CCE on UCS Deployment Certification Requirements and Ordering Information

2011-12-09T15:43:12Z

Sdurvasu: 1 revision

== Partner Certification Requirements ==

=== B-Series Partner Certification Requirements ===

In order to be able to sell Unified Contact Center Enterprise (Unified CCE) on UCS B-server, partners must have Cisco Data Center Unified Computing (DCUC) Authorized Technology Provider (ATP) certification status in addition to the Unified CCE ATP certification. See [http://www.cisco.com/web/partners/pr11/atp/dcuc/index.html Data Center Unified Computing – Partner Central] for DCUC ATP (also known as UCS ATP)information.

Note that the DCUC ATP certification program has the following prerequisites:

:*Cisco Data Center Networking Infrastructure (DCNI) specialization.

:*Cisco Data Center Storage Networking (DCSN) specialization

See [http://www.cisco.com/web/partners/program/specializations/index.html Specialized Partner - Partner Central] for Data Center Networking Infrastructure and Data Center Storage Networking Specialization information.

In addition to the above certifications, the partners must have VMware training and it is strongly recommended to have VMware Premier or Enterprise Partner status or VMware Professional certification.

ATP partners who do not have the necessary above certifications would be best served by partnering with partners who do.

=== C-Series Partner Certification Requirements ===

Partners who want to sell Unified Contact Center Enterprise on UCS C-Series do not require Data Center certification.

As long as the C-Series is not in the data center, an AUC, or Unified CCE ATP or CVP ATP or Master UC, or Business Edition Partner can sell it. This also means an Advanced Unified Communications Express (Express UC) cannot sell C-series since all they are allowed is Communication Manager.

(AUC = Advanced Unified Communication Specialized. It is also the prerequisite for Unified CCE ATP and CVP ATP. Masters’ is a higher level of AUC).

===Partners Training for UCCE on UCS ===

Partners can attend two courses related to Unified Communications (UC) on UCS. This is also applicable to UCCE on UCS since UCCE is a part of the UC applications. The first is two day UCS Mini-eCamp. The second is a UC on UCS hands on lab course. The hands-on course is by invitation only after an engineer has attended the Mini-eCamp. For more information on UCS partner training, see [https://www.myciscocommunity.com/community/partner/datacenter/products/ucs Cisco Community Central: Community: Unified Computing System (UCS)] or [https://www.myciscocommunity.com/community/partner/collaboration/calendar https://www.myciscocommunity.com/community/partner/collaboration/calendar].

== UCS Server Ordering Information ==

Unified CCE does not have specific UCS SKUs. For deploying the Unified CCE application on UCS, UCS servers may be purchased using either the Voice Technology Group (VTG) Collaboration SKUs or the Data Center SKUs via the 'build-to-order' process.

=== VTG Collaboration SKUs ===

The Part Number Syntax for the VTG UCS Collaboration SKUs is

''UCS-xxxxyy-VCzz.''

:*“UCS-” is to distinguish these SKUs from Cisco MCS 7800 SKUs.
:*xxxx is the server model as described at http://www.cisco.com/go/ucs: For example, “B200” is the server model.
:*yy is the server generation as described at http://www.cisco.com/go/ucs: For example, “M1” is the server generation.
:*VCzz is a suffix indicating a unique hardware configuration. The following suffixes are used:
:**VCS1: “Virtualized Collaboration”, “SAN storage”, 1st configuration
:**VCD1: “Virtualized Collaboration”, “Disks (or DAS) storage”, 1st configuration

For VTG UCS Collaboration SKUs and ordering information, refer to [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html].

Note that for Cisco UCS B series, the VTG UCS Collaboration SKU is available only for the blade component. The rest of the UCS B system/blade server components have to be ordered using the Data Center SKUs. Therefore, you should familiarize yourself with the following resources to help you quote a Unified CCE on UCS B-series solution:

:*Visit the [http://www.cisco.com/web/partners/downloads/partner/WWChannels/technology/ipc/downloads/uc_sol_og_ucl_final.pdf following document] for information on how to order Cisco UCS B-Series blade servers, Cisco UCS 5100 Blade Server Chassis, Cisco UCS 2100 Series Fabric Extenders, and Cisco UCS 6100 Fabric Interconnect Switches. 

:

=== Data Center SKUs - Build-To-Order ===

A Cisco UCS server may also be quoted using a “build-to-order” mechanism with Data Center SKUs/Part Numbers.

For UCS C-series, the servers may be ordered via standard Cisco ordering tools.

For UCS B-series, the server must be ordered  using a designated tool described in the [http://www.cisco.com/web/partners/downloads/partner/WWChannels/technology/ipc/downloads/uc_sol_og_ucl_final.pdf following document].  See [http://www.cisco.com/go/swonly http://www.cisco.com/go/swonly] for the reference configuration as well as the alternative server configurations that are supported.

As described earlier, the Cisco UCS B-Series Blade Server solution requires several other components - Cisco UCS 5100 Blade Server Chassis, Cisco UCS 2100 Fabric Extenders, and Cisco UCS 6100 Fabric Interconnect Switches. These components are available only as Cisco Data Center part numbers. You must use the NetformX DesignXpert ordering tool “UCS Advisor” to properly configure and quote these components. For example configurations, see [http://www.cisco.com/go/swonly http://www.cisco.com/go/swonly].

At least one Cisco UCS 5100 Blade Server Chassis is required for every eight blades. Additional chassis are needed if you want redundant chassis and/or split servers across multiple sites.

Each chassis will require two Cisco UCS 2100 Fabric Extenders for CCE deployment.

Each site requires two Cisco UCS 6100 series Fabric Interconnect Switches for CCE deployment.

Port Licenses may be required to connect all chassis, and interface modules are required for interconnect to customer’s LAN and SAN networks.

Cisco UCS B-series requires the use of SAN. For further SAN ordering information, please refer to Chapter 4 of the [http://www.cisco.com/web/partners/downloads/partner/WWChannels/technology/ipc/downloads/uc_sol_og_ucl_final.pdf following document].

== Important Notes on Cisco UCS Service and Support ==
Cisco UCS does not use Cisco SMARTnet support; instead it uses an extended 3-year warranty with optional value-add services.

Unified CCE on UCS hardware may be serviced at the blade level or component level. Blade server replacements are attempted only after component replacement efforts have failed.

'''Service contracts MUST be purchased for the UCS hardware, VMware software, Unified CCE software, and storage environment to cover the entire solution.'''

As with other Cisco UCS hardware, Warranty Plus services are also offered. For more information on Warranty Plus, see [http://www.cisco.com/en/US/products/ps10321/serv_home.html http://www.cisco.com/en/US/products/ps10321/serv_home.html].

For details of service contract SKUs for UCS hardware and VMware software, please refer to Chapter 4 of the [http://www.cisco.com/web/partners/downloads/partner/WWChannels/technology/ipc/downloads/uc_sol_og_ucl_final.pdf following document ].

-----
Back to [http://docwiki-dev.cisco.com/wiki/Unified_Contact_Center_Enterprise Unified Contact Center Enterprise main page]

OVA Template Details for Unified Presence Release 8.6(3)

2011-12-09T14:35:32Z

Sdurvasu: Protected "OVA Template Details for Unified Presence Release 8.6(3)" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) [cascading]

*'''Go to:''' [http://www.cisco.com/cisco/software/release.html?mdfid=283931705&flowid=28621&softwareid=283757588&release=8.6&relind=AVAILABLE&rellifecycle=&reltype=latest '''OVA Download Location for Unified Presence Release 8.6(x)''']
*'''Go to: [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]'''

 
Note: The information in the table below applies to Cisco Unified Presence release 8.6(3).
 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Presence'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! IM-Only User Deployment Count
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 500 Full UC users]
| 1000 IM-only users
| 1 vCPU (700 MHz reserved)
| 2 GB RAM with 2 GB reservation
| 1x 80 GB vHDD
| 1
|
For use on all supported UCS, IBM, HP, and Specs-based hardware platforms, including CUCM-BE 6000. If you are migrating from a physical server with more than 80 GB of storage space to a virtual machine with a user deployment size of either 500 or 2000, see the Disaster Recovery System Administration Guide for Cisco Unified Presence for more information.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 2000 Full UC users]
| 5000 IM-only users
| 1 vCPU (1500 MHz reserved)
| 4 GB RAM with 4 GB reservation
| 1x 80 GB vHDD
| 1
| For use on B200, C210, and Specs-based supported platforms. If you are migrating from a physical server with more than 80 GB of storage space to a virtual machine with a user deployment size of either 500 or 2000, see the Disaster Recovery System Administration Guide for Cisco Unified Presence for more information.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 5000 Full UC users]
| 12500 IM-only users
| 2 vCPU (2500 MHz reserved)
| 4 GB RAM with 4 GB reservation
| 2x 80 GB vHDD
| 1
| For use on B200, C210, and Specs-based hardware platforms.
For use on all supported UCS, IBM, HP, and Specs-based hardware platforms.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 15000 Full UC users]
| 25000 IM-only users
| 4 vCPU (8000 MHz reserved)
| 6 GB RAM with 6 GB reservation
| 2x 80 GB vHDD
| 1
| For use on B200, C210, and Specs-based hardware platforms.
For use on all supported UCS, IBM, HP, and Specs-based hardware platforms.
|}

Note: Any of the user base sizes above can be used when performing a DRS migration from a physical machine with a disk capacity of less than 80 GB (for example, MCS-7825-H2). 
{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

OVA Template Details for Unified Presence Release 8.6(2)

2011-12-09T14:35:00Z

Sdurvasu: Protected "OVA Template Details for Unified Presence Release 8.6(2)" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) [cascading]

*'''Go to:''' [http://www.cisco.com/cisco/software/release.html?mdfid=283931705&flowid=28621&softwareid=283757588&release=8.6&relind=AVAILABLE&rellifecycle=&reltype=latest '''OVA Download Location for Unified Presence Release 8.6(x)''']
*'''Go to: [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]'''

 
Note: The information in the table below applies to Cisco Unified Presence release 8.6(2).
 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Presence'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! IM-Only User Deployment Count
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 500 Full UC users]
| 1000 IM-only users
| 1 vCPU (700 MHz reserved)
| 2 GB RAM with 2 GB reservation
| 1x 80 GB vHDD
| 1
|
For use on all supported UCS, IBM, HP, and Specs-based hardware platforms, including CUCM-BE 6000. If you are migrating from a physical server with more than 80 GB of storage space to a virtual machine with a user deployment size of either 500 or 2000, see the Disaster Recovery System Administration Guide for Cisco Unified Presence for more information.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 2000 Full UC users]
| 5000 IM-only users
| 1 vCPU (1500 MHz reserved)
| 4 GB RAM with 4 GB reservation
| 1x 80 GB vHDD
| 1
| For use on B200, C210, and Specs-based supported platforms. If you are migrating from a physical server with more than 80 GB of storage space to a virtual machine with a user deployment size of either 500 or 2000, see the Disaster Recovery System Administration Guide for Cisco Unified Presence for more information.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 5000 Full UC users]
| 12500 IM-only users
| 2 vCPU (2500 MHz reserved)
| 4 GB RAM with 4 GB reservation
| 2x 80 GB vHDD
| 1
| For use on B200, C210, and Specs-based hardware platforms.
For use on all supported UCS, IBM, HP, and Specs-based hardware platforms.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 15000 Full UC users]
| 25000 IM-only users
| 4 vCPU (8000 MHz reserved)
| 6 GB RAM with 6 GB reservation
| 2x 80 GB vHDD
| 1
| For use on B200, C210, and Specs-based hardware platforms.
For use on all supported UCS, IBM, HP, and Specs-based hardware platforms.
|}

Note: Any of the user base sizes above can be used when performing a DRS migration from a physical machine with a disk capacity of less than 80 GB (for example, MCS-7825-H2). 
{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

OVA Template Details for Unified Presence Release 8.6(1)

2011-12-09T14:34:34Z

Sdurvasu: Protected "OVA Template Details for Unified Presence Release 8.6(1)" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) [cascading]

*'''Go to:''' [http://www.cisco.com/cisco/software/release.html?mdfid=283931705&flowid=28621&softwareid=283757588&release=8.6&relind=AVAILABLE&rellifecycle=&reltype=latest '''OVA Download Location for Unified Presence Release 8.6(x)''']
*'''Go to: [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]'''

 
Note: The information in the table below applies to Cisco Unified Presence release 8.6(1).
 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Presence'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 1000 users]
| 1 (800 MHz reserved)
| 2 GB RAM with 2 GB reservation
| 1x 80 GB
| 1
|
For use on all supported UCS, IBM, HP, and Specs-based hardware platforms, including CUCM-BE 6000. If you are migrating from a physical server with more than 80 GB of storage space to a virtual machine with a user deployment size of either 1000 or 2500, see the Disaster Recovery System Administration Guide for Cisco Unified Presence for more information.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 2500 users]
| 2 (2000 MHz reserved)
| 4 GB
| 1x 80 GB
| 1
| For use on B200, C210, and Specs-based supported platforms. If you are migrating from a physical server with more than 80 GB of storage space to a virtual machine with a user deployment size of either 1000 or 2500, see the Disaster Recovery System Administration Guide for Cisco Unified Presence for more information.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 5000 users]
| 4 (4000 MHz reserved)
| 6 GB
| 2x 80 GB
| 1
| For use on B200, C210, and Specs-based supported platforms.
|}

Note: Any of the user base sizes above can be used when performing a DRS migration from a physical machine with a disk capacity of less than 80 GB (for example, MCS-7825-H2). 
{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]

|}

OVA Template Details for Unified Presence Release 8.6(1)

2011-12-09T14:30:06Z

Sdurvasu: 1 revision

*'''Go to:''' [http://www.cisco.com/cisco/software/release.html?mdfid=283931705&flowid=28621&softwareid=283757588&release=8.6&relind=AVAILABLE&rellifecycle=&reltype=latest '''OVA Download Location for Unified Presence Release 8.6(x)''']
*'''Go to: [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]'''

 
Note: The information in the table below applies to Cisco Unified Presence release 8.6(1).
 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Presence'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 1000 users]
| 1 (800 MHz reserved)
| 2 GB RAM with 2 GB reservation
| 1x 80 GB
| 1
|
For use on all supported UCS, IBM, HP, and Specs-based hardware platforms, including CUCM-BE 6000. If you are migrating from a physical server with more than 80 GB of storage space to a virtual machine with a user deployment size of either 1000 or 2500, see the Disaster Recovery System Administration Guide for Cisco Unified Presence for more information.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 2500 users]
| 2 (2000 MHz reserved)
| 4 GB
| 1x 80 GB
| 1
| For use on B200, C210, and Specs-based supported platforms. If you are migrating from a physical server with more than 80 GB of storage space to a virtual machine with a user deployment size of either 1000 or 2500, see the Disaster Recovery System Administration Guide for Cisco Unified Presence for more information.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 5000 users]
| 4 (4000 MHz reserved)
| 6 GB
| 2x 80 GB
| 1
| For use on B200, C210, and Specs-based supported platforms.
|}

Note: Any of the user base sizes above can be used when performing a DRS migration from a physical machine with a disk capacity of less than 80 GB (for example, MCS-7825-H2). 
{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]

|}

Unified Communications Virtualization Downloads (including OVA/OVF Templates)

2011-12-08T21:41:28Z

Sdurvasu: 1 revision

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

= Supported Virtual Machine OVA Templates =

A virtual machine template defines the configuration of the virtual machine's virtual hardware. Open Virtualization Format (OVF) is an open standard for describing a virtual machine template, and Open Virtualization Archive (OVA) is an open standard to package and distribute these templates. Files in OVA format have an extension of ".ova".

Cisco Unified Communications applications '''must''' use one of the supported virtual machine configurations in the tables below in order to be supported. The OVAs contain virtual hard disks with pre-aligned disk partitions. Using the OVA is the only way to deploy the UC applications on aligned disks. Using the OVA also guarantees that all configuration of the virtual machine is correct and supported.

In the tables below '''users''' refers to the [http://tools.cisco.com/cucst/faces/login.jsp Cisco Unified Communications Sizing Tool] and the [http://www.cisco.com/go/ucsrnd design guides] for the indicated user count at a particular BHCA, number of devices per user, device mix per VM, etc. Actual capacity and total supported devices will be design-dependent; please follow all rules in the design guides and sizing tools.

 See [[Downloading OVA Templates for UC Applications]] for more information on how to download OVA templates for UC Applications.

For '''Specifications-based''' deployments (non TRC deployments), the CPU core count AND the CPU core speed correspond to physical CPU cores and physical CPU core speeds. Both are required to be met to support a full load VM OVA. At this time, only core speed for full load is defined. Do not use lower physical CPU core speeds until Cisco defines minimum speed for lower load levels. Cisco TAC will not troubleshoot a VM that is not receiving sufficient CPU cycles.

== Unified Communications Manager ==

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=268439621&catid=278875240 General OVA Template Download Location] 
*[[OVA Template Details for Unifed CM Release 8.0]] 
*[[OVA Template Details for Unifed CM Release 8.5]] 
*[[OVA Template Details for Unifed CM Release 8.6]] 

 

== Cisco Emergency Responder ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Emergency Responder'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 12,000 users (C200 only)]
| 2 @ 2.13 GHz each (600 MHz reserved)
| 4 GB (4 GB reserved)
| 1 x 80 GB
| 1
|
Use on C200 M2 TRC#1 only.

Limits:

:*12,000 IP phones
:*2,500 analog phones
:*1,200 roaming phones (per Emergency Responder cluster)
:*500 LAN switches
:*30,000 switch ports
:*3,000 ERLs

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 20,000 users]
| 1 @ 2.55 MHz (600 MHz reserved)
| 2.25 GB (2.304 GB reserved)
| 1 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

Limits:

:*20,000 IP phones
:*5,000 analog phones
:*2,000 roaming phones (per Emergency Responder cluster)
:*1,000 LAN switches
:*60,000 switch ports
:*7,500 ERLs

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 30,000 users]
| 2 @ 2.55 MHz each
| 6 GB
| 2 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

Limits:

:*30,000 IP phones
:*10,000 analog phones
:*3,000 roaming phones (per Emergency Responder cluster)
:*2,000 LAN switches
:*120,000 switch ports
:*10,000 ERLs

|}

 

== Session Manager Edition ==

{| border="1"
|+ '''Supported OVA Templates: Session Manager Edition'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&isPlatform=Y&mdfid=282827095&sftType=Unified+Communications+Manager+Virtual+Machine+Templates&treeName=Voice+and+Unified+Communications&modelName=Cisco+Unified+Communications+Manager+Version+8.0&mdfLevel=Software%20Version/Option&treeMdfId=278875240&modifmdfid=null&imname=&hybrid=Y&imst=N Use CUCM "7500 users"]
| See CUCM "7500 users"
| See CUCM "7500 users"
| See CUCM "7500 users"
| See CUCM "7500 users"
|
|}

 

== Unified Attendant Consoles ==

{| border="1"
|+ '''Supported OVA Templates: Unified Attendant Consoles'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! OVA for CUxAC
| 1 @ 2.55 GHz
| 2 GB
| 1x 80GB
| 1
| Note: Cisco does not provide preconfigured OVA files for CUxAC. Please build manually using these requirements. CUxAC requires a VM to meet or exceed minimum physical server specs described [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/data_sheet_c78-520987.html on the CUxAC datasheet]
|}

 

== Cisco Intercompany Media Engine ==

{| style="width: 712px; height: 416px" border="1"
|+ '''Supported OVA Templates: Cisco Intercompany Media Engine, Release 8.6(2)'''
|- style="background: rgb(229,228,226)"
! rowspan="2" | VM OVA Capacity 
! colspan="5" | VM OVA Parameters 
! rowspan="2" | Notes 
|- style="background: rgb(229,228,226)"
! vCPU Cores (= Physical Cores)
! Physical CPU Load was Calibrated To
! vRAM (=Physical Memory)
! vDisk (=Physical space)
! vNIC
|-
!
CIME 5 peer IDs node Only for non-BE6K/C200M2 TRC#1

| 2 (with 3600 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 1x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or BE6000. Up to 5 peer IDs.
 

|-
!
CIME 10 peer IDs node Only for non-BE6K/C200M2 TRC#1

| 4 (with 7200 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 2x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or BE6000. Up to 10 peer IDs.
 

|}

 

 

== Cisco Unity Connection ==

*[http://www.cisco.com/cisco/software/type.html?mdfid=283062758&flowid=5455 General Unity Connection OVA Template Download Location] 
*[[OVA Template Details for Unity Connection Release 8.0]] 
*[[OVA Template Details for Unity Connection Release 8.5]] 
*[[OVA Template Details for Unity Connection Release 8.6.1]] 
*[[OVA Template Details for Unity Connection Release 8.6.2]] 

 

== Cisco Unity ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Unity'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! 5000 users
| 2 (requires VMware CPU Affinity)
| 4 GB
|
4x 24 GB

:*vDisk 1 = Operating system
:*vDisk 2 = Cisco Unity binaries
:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

| 1
|
*Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
*Limits:

:*48 ports
:*36 text-to-speech ports

|-
! 15,000 users
| 4 (requires VMware CPU Affinity)
| 4 GB
|
4x 24 GB

:*vDisk 1 = Operating system
:*vDisk 2 = Cisco Unity binaries
:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

| 1
|
*Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
*Limits:

:*144 ports
:*36 text-to-speech ports

|}

 

== Cisco Unified Presence ==

See also:

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=280448682&i=rs General OVA Template Download Location]
*[[OVA Template Details for Unified Presence Release 8.0(x)]] 
*[[OVA Template Details for Unified Presence Release 8.5(x)]] 
*[[OVA Template Details for Unified Presence Release 8.6(1)]] 
*[[OVA Template Details for Unified Presence Release 8.6(2)]] 
*[[OVA Template Details for Unified Presence Release 8.6(3)]] 

 

== Cisco Unified Contact Center Express/Cisco Unified IP Intelligent Voice Response (IP IVR) ==

{{Note| The information for Unified IP IVR is the same as Unified CCX.}}

See also:

*[[Virtualization for Unified CCX]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest| Unified CCX OVA Templates]: {{Note| Unified CCX OVA version 2 is for use with ESXi 4.1. Please follow [[Unified Communications VMware Requirements]] for ESXi 4.1 requirements (VMware Tools upgrade, LRO disabling, etc.)}}

 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Express'''
|- style="background: rgb(229,228,226)"
! colspan="2" | Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 100 agents] (Release 8.5(1))
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 300 agents] (Release 8.0(2) and Release 8.5(1))
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 400 agents] (Release 8.5(1))
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! rowspan="3" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=latest Single OVA] (Release 8.5 (1) or later)
! 100 agents
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
|
|-
! 300 agents
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! 400 agents
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.2]
| 2
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = Optional - can be used to hold SQL Server Data files

| 1
|
Capacities

:*900 named users
:*300 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Base Server Configuration (CR/QM/AQM)]
| 2
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)

| 1
|
Capacities

:*3600 named users
:*1200 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Recording Server Configuration (CR/QM/AQM)]
| 4
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM recording service binaries
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recording cache

| 1
|
Capacities

:*300 concurrent voice recordings for Server (SPAN) and Network recording
:*150 concurrent voice and screen recordings, recordings for Server (SPAN) and Network recording

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.1]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = Optional - can be used to hold SQL Server Data files

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.1 Base Server Configuration (CR/QM/AQM)]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM Configuration (CR/QM/AQM)]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage )

| 2
|
Capacities

:*300 named users
:*150 concurrent users
:*150 voice recordings, for all recording types (desktop, server and network)
:*150 voice+screen recordings, for all recording types (desktop, server and network)

|}

== UC Management Suite (PM, OM, SM, SSM) ==

There are different OVAs for premise UC on UCS deployments vs. Hosted Collaboration Solution deployments.

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise UC on UCS Deployments'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! IOPS (avg) (1)
! IOPS (max) (1)
! vNIC
! Notes
! 
|-
! CUPM up to 1K phones (VM-CUCMS_1S)
| 1
| 2 GB
| 1x 30 GB
| 100
| 500
| 1
| 
|-
! CUPM 1K to 10K phones
| 4
| 4 GB
| 1x 40 GB (2)
| 100
| 500
| 1
| 
|-
! CUPM 10K to 60K phones app server
| 4
| 4 GB
| 1x 30 GB(3)
| 100
| 500
| 1
| requires DB VM
|-
! CUPM 10K to 60K phones database server
| 4
| 8 GB
| 1x 120 GB(3)
| 100
| 500
| 1
| requires App VM
|-
! CUOM/SM 1K phones
| 1
| 3 GB
| 1x 50 GB
| 6
| 15
| 1
| 
|-
! CUOM 10K phones (VM-CUCMS_2L)
| 2
| 8 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUOM 45K phones (VM-CUCMS_4L)
| 4
| 8 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSM 10K Phones (VM-CUCMS_2)
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUSM 45K Server (VM-CUCMS_4)
| 4
| 4 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSSM 10K phones (VM-CUCMS_1)
| 1
| 4 GB
| 1x 60 GB
|
|
| 1
| 
|-
! CUSSM 45K Phones
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUCMS 10K phones Co-resident (VM_CUCMS_8)
| 8
| 16 GB
| 1x 320 GB (2)
| 100
| 500
| 1
| 
|}

Notes: (1) IOPS are for each CM publisher synced in parallel. If only one CM publisher then IOPS are 100/500. The maximum figures would be expected during nightly Infrastructrure or Subscriber syncs. (2) PM requires SAS or SCSI drives for deployments over 1K phones up to 10k phones (Disks must be aligned) (3) PM requires FC SAS for deployments over 10K phones (Disks must be aligned)

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise Systems'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K Server OVA]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K to 10K Server OVA]
| 4
| 4 GB
| 1x 40 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K App/Web Server OVA]
| 4
| 4 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K Database Server OVA]
| 4
| 8 GB
| 1x 120 GB
| 1
| 
|}

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Hosted Collaboration Solution'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283112898&flowid=20421&softwareid=282773197&release=8.0&rellifecycle=&relind=AVAILABLE&reltype=latest CUOM+CUSM 1K phones for HCS (HCS_OM&SM_1K)]
| 1
| 3 GB
| 1x 50 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283315737&flowid=19121&softwareid=281934350&release=2.2&rellifecycle=&relind=AVAILABLE&reltype=latest CUPM 1K phones for HCS (HCS_PM_1K)]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|}

== Unified Contact Center Enterprise ==

See also:

*[[Unified Contact Center Enterprise]]
*[http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Capacities_and_VM_Configuration_Requirements Unified CCE OVA Templates]
*See also [http://docwiki.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE#Unified_CCE_Scalability_Impacts Scalability Impacts]

Templates are available for Windows Server 2003 and Windows Server 2008 R2. [http://www.cisco.com/cisco/software/release.html?mdfid=268439622&release=1.1&relind=AVAILABLE&flowid=5210&softwareid=283914286&rellifecycle=&reltype=latest Download] the appropriate OVA file for the Windows OS that you are configuring. When you deploy the OVA, a drop-down list of the configurations are presented allowing you to select the appropriate configuration for the UCCE sized component that you are installing.

 

{| border="1" cellspacing="3" cellpadding="3"
|- style="background: rgb(229,228,226)"
! Configuration Name
! vCPU Cores
! vRAM / Memory (GB)
! vDisk (GB)
! vNIC 
! Notes
|-
| colspan="7" | '''Note: Windows Server 2008 R2 configurations are contained in the UCCE_8.5_win2008_vmv7_v1.1.ova file, Windows Server 2003 configurations are contained in the UCCE_8.5_win2003_vmv7_v1.1.ova file'''
|-
| '''Router 8000 agents'''
| 2
| 4
| 1 x80
| 2
|  
|-
| '''Logger 8000 agents'''
| 4
| 4
| 1x 80 for OS 1x 150 for DB
| 2
| The two vDisks can be in the same datastore 
|-
| '''Rogger 4000 agents'''
| 4
| 4
| 1x 80 for OS 1x 150 for DB
| 2
| The two vDisks can be in the same datastore 
|-
| '''Agent PG – CTIOS 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''Agent PG – CAD 1000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''Agent PG – CTIOS 450 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Agent PG – CAD 297 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''MR PG 2000 agents 10 pims'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''MR PG 1000 agents 5 pims'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''VRU PG 9600 ports 10 pims'''
| 2
| 2
| 1x 80
| 2
|  
|-
| '''VRU PG 1200 ports 4 pims'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Avaya ACD PG'''
| 2
| 4
| 1x 80
| 2
| See the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted] for capacity information.
|-
| '''TDM ACD PG 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''TDM ACD PG 250 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''UCC Gateway PG 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''UCC Gateway PG 450 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Administration Client'''
| 1
| 2
| 1x 40
| 1
|  (Client AW)
|-
| '''Administration Server - AW'''
| 1
| 2
| 1x 40
| 1
|  
|-
| '''AW-HDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
|  (200 reporters.) The two vDisks can be in the same datastore
|-
| '''AW-HDS-DDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
|  (200 reporters.) The two vDisks can be in the same datastore
|-
| '''HDS-DDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
| (200 reporters.) The two vDisks can be in the same datastore  
|-
| '''CCMP single box 1500 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP Web/App Svr 8000 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP with Config AW 1500 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP DB only 8000 agents'''
| 8
| 4
| 1x 250
| 1
|  
|}

== Unified Customer Voice Portal ==

See also:

*[[Unified Customer Voice Portal]]
*[[Unified Customer Voice Portal#Unified_CVP_Component_Capacities_and_VM_Configuration_Requirements|Unified CVP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Unified Customer Voice Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CVP Call Server + VXML Server (co-located Call Server and VXML Server) (Media Server is optionally included depending on the conditions. See CVP co-residency section for detail)
| 4
| 4 GB
| 1x 146 GB
| 1
| Template Name: Cisco Unified CVP Call Server-VXML Server.ova
|-
! Unified CVP Reporting Server (Large)
| 4
| 4 GB
| Disk 1 - 72 GB, Disk 2 - 438 GB
| 1
| Template Name: Cisco Unified CVP Reporting Server.ova
|-
! Unified CVP Operations Console
| 2
| 2 GB
| 1x 20 GB
| 1
| Template Name: Cisco Unified CVP Operations Console.ova
|}

== Cisco MediaSense ==

See also:

*[[Virtualization for Cisco MediaSense]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco MediaSense OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco MediaSense'''
|-
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! CMS_6T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 146 GB (thick provisioning)
| 1
| rowspan="3" | Release 8.5(1)
|-
! CMS_12T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 300 GB (thick provisioning)
| 1
|-
! CMS_expansion_server_v8.5_vmv7
| 7 
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_12T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 150 GB (thick provisioning) 
| 1
| rowspan="4" | Release 8.5(2)
|-
! CMS_24T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 300 GB (thick provisioning) 
| 1
|-
! CMS_60T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 600 GB (thick provisioning) 
| 1
|-
! CMS_expansion_server_v8.5.2_vmv7
| 7
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_SRE_v8.5_vmv7
| 2
| 6 GB
| 2 x 80 GB (thick provisioning) 1 x 200 GB (thick provisioning) for Media storage
| 1 (with static MAC address)
| Release 8.5(4)
|}

== Cisco Unified Intelligence Center ==

See also:

*[[Cisco Unified Intelligence Center]]
*[[Cisco Unified Intelligence Center#Unified_IC_Component_Capacities_and_VM_Configuration_Requirements|Cisco Unified Intelligence Center OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Intelligence Center'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=282163829&flowid=5228&softwareid=283776220&release=8.0(3)&relind=AVAILABLE&rellifecycle=&reltype=latest CUIC (200 Reporting Users)]
| 4
| 6 GB
| 1x 146 GB
| 1
|
|}

== Cisco Unified Contact Center Management Portal ==

See also:

*[[Support for CCMP with UCCE on UCS Hardware|Cisco Unified Contact Center Management Portal]]
*[[Support for CCMP with UCCE on UCS Hardware#CCMP_Component_Capacities_and_VM_Configuration_Requirements|Unified CCMP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Management Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CCMP (1500 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (Web/App Srv Only) (8000 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (DB Only) (8000 Agents)
| 8
| 4 GB
| 1x 250 GB
| 1
| 
|}

== Cisco SocialMiner ==

See also:

*[[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613136&softwareid=283733464&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco SocialMiner OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco SocialMiner'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Standard Production Server
| 4
| 12 GB
| 1x 146 GB and 1x 256 GB
| 1
| 
|}

== Cisco Unfied Email Interaction Manager and Web Interaction Manager ==

  

{| border="1" cellspacing="1" cellpadding="1"
|-
! scope="col" | Application, OVA Capacity and Notes+Download Link
! scope="col" | Contents
! scope="col" | No of VM's to deploy of each component
! scope="col" | vCPU
! scope="col" | vDisk
! scope="col" | vRAM/Memory
|-
| rowspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 50 Agents(All in One)]
| Web Server
| 1
| 1
| 1 x 80GB
| 2
|-
| Application, Services Server ,File server Messaging Server and  Database server
| 1
| 4
| 1 x 150GB
| 4
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 80 Agents]
| Web Server
| 1
| 1
| 1 x 80GB
| 2
|-
| Application server
| 1
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 200 GB for DB
| 4
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 120 Agents]
| Web Server
| 1
| 1
| 1 x 80GB
| 2
|-
| Application server
| 1
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 200 GB for DB
| 4
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 240 Agents]
| Web Server
| 2
| 2
| 1 x 80GB
| 2
|-
| Application server
| 2
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 200 GB for DB
| 8
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 360 Agents]
| Web Server
| 3
| 2
| 1 x 80GB
| 2
|-
| Application server
| 3
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 500 GB for DB
| 16
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 480 Agents]
| Web Server
| 4
| 2
| 1 x 80GB
| 2
|-
| Application server
| 4
| 2
| 1 x 80GB
| 4
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 500 GB for DB
| 16
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 4
|-
| rowspan="6" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 600 Agents]
| Web Server
| 5
| 2
| 1 x 80GB
| 2
|-
| Application server
| 5
| 2
| 1 x 80GB
| 4
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 500 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 4
|}

 

 

  

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

OVA Template Details for Unified Presence Release 8.6(3)

2011-12-08T21:41:27Z

Sdurvasu: 1 revision

OVA Template Details for Unified Presence Release 8.6(2)

2011-12-08T21:41:27Z

Sdurvasu: 1 revision

*'''Go to:''' [http://www.cisco.com/cisco/software/release.html?mdfid=283931705&flowid=28621&softwareid=283757588&release=8.6&relind=AVAILABLE&rellifecycle=&reltype=latest '''OVA Download Location for Unified Presence Release 8.6(x)''']
*'''Go to: [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]'''

 
Note: The information in the table below applies to Cisco Unified Presence release 8.6(2).
 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Presence'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! IM-Only User Deployment Count
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 500 Full UC users]
| 1000 IM-only users
| 1 vCPU (700 MHz reserved)
| 2 GB RAM with 2 GB reservation
| 1x 80 GB vHDD
| 1
|
For use on all supported UCS, IBM, HP, and Specs-based hardware platforms, including CUCM-BE 6000. If you are migrating from a physical server with more than 80 GB of storage space to a virtual machine with a user deployment size of either 500 or 2000, see the Disaster Recovery System Administration Guide for Cisco Unified Presence for more information.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 2000 Full UC users]
| 5000 IM-only users
| 1 vCPU (1500 MHz reserved)
| 4 GB RAM with 4 GB reservation
| 1x 80 GB vHDD
| 1
| For use on B200, C210, and Specs-based supported platforms. If you are migrating from a physical server with more than 80 GB of storage space to a virtual machine with a user deployment size of either 500 or 2000, see the Disaster Recovery System Administration Guide for Cisco Unified Presence for more information.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 5000 Full UC users]
| 12500 IM-only users
| 2 vCPU (2500 MHz reserved)
| 4 GB RAM with 4 GB reservation
| 2x 80 GB vHDD
| 1
| For use on B200, C210, and Specs-based hardware platforms.
For use on all supported UCS, IBM, HP, and Specs-based hardware platforms.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 15000 Full UC users]
| 25000 IM-only users
| 4 vCPU (8000 MHz reserved)
| 6 GB RAM with 6 GB reservation
| 2x 80 GB vHDD
| 1
| For use on B200, C210, and Specs-based hardware platforms.
For use on all supported UCS, IBM, HP, and Specs-based hardware platforms.
|}

Note: Any of the user base sizes above can be used when performing a DRS migration from a physical machine with a disk capacity of less than 80 GB (for example, MCS-7825-H2). 
{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications Virtualization Downloads (including OVA/OVF Templates)

2011-12-08T19:44:09Z

Sdurvasu: 1 revision

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

= Supported Virtual Machine OVA Templates =

A virtual machine template defines the configuration of the virtual machine's virtual hardware. Open Virtualization Format (OVF) is an open standard for describing a virtual machine template, and Open Virtualization Archive (OVA) is an open standard to package and distribute these templates. Files in OVA format have an extension of ".ova".

Cisco Unified Communications applications '''must''' use one of the supported virtual machine configurations in the tables below in order to be supported. The OVAs contain virtual hard disks with pre-aligned disk partitions. Using the OVA is the only way to deploy the UC applications on aligned disks. Using the OVA also guarantees that all configuration of the virtual machine is correct and supported.

In the tables below '''users''' refers to the [http://tools.cisco.com/cucst/faces/login.jsp Cisco Unified Communications Sizing Tool] and the [http://www.cisco.com/go/ucsrnd design guides] for the indicated user count at a particular BHCA, number of devices per user, device mix per VM, etc. Actual capacity and total supported devices will be design-dependent; please follow all rules in the design guides and sizing tools.

 See [[Downloading OVA Templates for UC Applications]] for more information on how to download OVA templates for UC Applications.

For '''Specifications-based''' deployments (non TRC deployments), the CPU core count AND the CPU core speed correspond to physical CPU cores and physical CPU core speeds. Both are required to be met to support a full load VM OVA. At this time, only core speed for full load is defined. Do not use lower physical CPU core speeds until Cisco defines minimum speed for lower load levels. Cisco TAC will not troubleshoot a VM that is not receiving sufficient CPU cycles.

== Unified Communications Manager ==

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=268439621&catid=278875240 General OVA Template Download Location] 
*[[OVA Template Details for Unifed CM Release 8.0]] 
*[[OVA Template Details for Unifed CM Release 8.5]] 
*[[OVA Template Details for Unifed CM Release 8.6]] 

 

== Cisco Emergency Responder ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Emergency Responder'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 12,000 users (C200 only)]
| 2 @ 2.13 GHz each (600 MHz reserved)
| 4 GB (4 GB reserved)
| 1 x 80 GB
| 1
|
Use on C200 M2 TRC#1 only.

Limits:

:*12,000 IP phones
:*2,500 analog phones
:*1,200 roaming phones (per Emergency Responder cluster)
:*500 LAN switches
:*30,000 switch ports
:*3,000 ERLs

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 20,000 users]
| 1 @ 2.55 MHz (600 MHz reserved)
| 2.25 GB (2.304 GB reserved)
| 1 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

Limits:

:*20,000 IP phones
:*5,000 analog phones
:*2,000 roaming phones (per Emergency Responder cluster)
:*1,000 LAN switches
:*60,000 switch ports
:*7,500 ERLs

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 30,000 users]
| 2 @ 2.55 MHz each
| 6 GB
| 2 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

Limits:

:*30,000 IP phones
:*10,000 analog phones
:*3,000 roaming phones (per Emergency Responder cluster)
:*2,000 LAN switches
:*120,000 switch ports
:*10,000 ERLs

|}

 

== Session Manager Edition ==

{| border="1"
|+ '''Supported OVA Templates: Session Manager Edition'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&isPlatform=Y&mdfid=282827095&sftType=Unified+Communications+Manager+Virtual+Machine+Templates&treeName=Voice+and+Unified+Communications&modelName=Cisco+Unified+Communications+Manager+Version+8.0&mdfLevel=Software%20Version/Option&treeMdfId=278875240&modifmdfid=null&imname=&hybrid=Y&imst=N Use CUCM "7500 users"]
| See CUCM "7500 users"
| See CUCM "7500 users"
| See CUCM "7500 users"
| See CUCM "7500 users"
|
|}

 

== Unified Attendant Consoles ==

{| border="1"
|+ '''Supported OVA Templates: Unified Attendant Consoles'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! OVA for CUxAC
| 1 @ 2.55 GHz
| 2 GB
| 1x 80GB
| 1
| Note: Cisco does not provide preconfigured OVA files for CUxAC. Please build manually using these requirements. CUxAC requires a VM to meet or exceed minimum physical server specs described [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/data_sheet_c78-520987.html on the CUxAC datasheet]
|}

 

== Cisco Intercompany Media Engine ==

{| style="width: 712px; height: 416px" border="1"
|+ '''Supported OVA Templates: Cisco Intercompany Media Engine, Release 8.6(2)'''
|- style="background: rgb(229,228,226)"
! rowspan="2" | VM OVA Capacity 
! colspan="5" | VM OVA Parameters 
! rowspan="2" | Notes 
|- style="background: rgb(229,228,226)"
! vCPU Cores (= Physical Cores)
! Physical CPU Load was Calibrated To
! vRAM (=Physical Memory)
! vDisk (=Physical space)
! vNIC
|-
!
CIME 5 peer IDs node Only for non-BE6K/C200M2 TRC#1

| 2 (with 3600 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 1x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or BE6000. Up to 5 peer IDs.
 

|-
!
CIME 10 peer IDs node Only for non-BE6K/C200M2 TRC#1

| 4 (with 7200 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 2x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or BE6000. Up to 10 peer IDs.
 

|}

 

 

== Cisco Unity Connection ==

*[http://www.cisco.com/cisco/software/type.html?mdfid=283062758&flowid=5455 General Unity Connection OVA Template Download Location] 
*[[OVA Template Details for Unity Connection Release 8.0]] 
*[[OVA Template Details for Unity Connection Release 8.5]] 
*[[OVA Template Details for Unity Connection Release 8.6.1]] 
*[[OVA Template Details for Unity Connection Release 8.6.2]] 

 

== Cisco Unity ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Unity'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! 5000 users
| 2 (requires VMware CPU Affinity)
| 4 GB
|
4x 24 GB

:*vDisk 1 = Operating system
:*vDisk 2 = Cisco Unity binaries
:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

| 1
|
*Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
*Limits:

:*48 ports
:*36 text-to-speech ports

|-
! 15,000 users
| 4 (requires VMware CPU Affinity)
| 4 GB
|
4x 24 GB

:*vDisk 1 = Operating system
:*vDisk 2 = Cisco Unity binaries
:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

| 1
|
*Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
*Limits:

:*144 ports
:*36 text-to-speech ports

|}

 

== Cisco Unified Presence ==

See also:

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=280448682&i=rs General OVA Template Download Location]
*[[OVA Template Details for Unified Presence Release 8.0(x)]] 
*[[OVA Template Details for Unified Presence Release 8.5(x)]] 
*[[OVA Template Details for Unified Presence Release 8.6(1)]] 
*[[OVA Template Details for Unified Presence Release 8.6(2)]] 
*[[OVA Template Details for Unified Presence Release 8.6(3)]] 
*[[OVA Template Details for Unified Presence Release 8.6(4)]] 

 

== Cisco Unified Contact Center Express/Cisco Unified IP Intelligent Voice Response (IP IVR) ==

{{Note| The information for Unified IP IVR is the same as Unified CCX.}}

See also:

*[[Virtualization for Unified CCX]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest| Unified CCX OVA Templates]: {{Note| Unified CCX OVA version 2 is for use with ESXi 4.1. Please follow [[Unified Communications VMware Requirements]] for ESXi 4.1 requirements (VMware Tools upgrade, LRO disabling, etc.)}}

 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Express'''
|- style="background: rgb(229,228,226)"
! colspan="2" | Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 100 agents] (Release 8.5(1))
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 300 agents] (Release 8.0(2) and Release 8.5(1))
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 400 agents] (Release 8.5(1))
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! rowspan="3" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=latest Single OVA] (Release 8.5 (1) or later)
! 100 agents
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
|
|-
! 300 agents
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! 400 agents
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.2]
| 2
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = Optional - can be used to hold SQL Server Data files

| 1
|
Capacities

:*900 named users
:*300 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Base Server Configuration (CR/QM/AQM)]
| 2
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)

| 1
|
Capacities

:*3600 named users
:*1200 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Recording Server Configuration (CR/QM/AQM)]
| 4
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM recording service binaries
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recording cache

| 1
|
Capacities

:*300 concurrent voice recordings for Server (SPAN) and Network recording
:*150 concurrent voice and screen recordings, recordings for Server (SPAN) and Network recording

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.1]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = Optional - can be used to hold SQL Server Data files

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.1 Base Server Configuration (CR/QM/AQM)]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM Configuration (CR/QM/AQM)]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage )

| 2
|
Capacities

:*300 named users
:*150 concurrent users
:*150 voice recordings, for all recording types (desktop, server and network)
:*150 voice+screen recordings, for all recording types (desktop, server and network)

|}

== UC Management Suite (PM, OM, SM, SSM) ==

There are different OVAs for premise UC on UCS deployments vs. Hosted Collaboration Solution deployments.

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise UC on UCS Deployments'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! IOPS (avg) (1)
! IOPS (max) (1)
! vNIC
! Notes
! 
|-
! CUPM up to 1K phones (VM-CUCMS_1S)
| 1
| 2 GB
| 1x 30 GB
| 100
| 500
| 1
| 
|-
! CUPM 1K to 10K phones
| 4
| 4 GB
| 1x 40 GB (2)
| 100
| 500
| 1
| 
|-
! CUPM 10K to 60K phones app server
| 4
| 4 GB
| 1x 30 GB(3)
| 100
| 500
| 1
| requires DB VM
|-
! CUPM 10K to 60K phones database server
| 4
| 8 GB
| 1x 120 GB(3)
| 100
| 500
| 1
| requires App VM
|-
! CUOM/SM 1K phones
| 1
| 3 GB
| 1x 50 GB
| 6
| 15
| 1
| 
|-
! CUOM 10K phones (VM-CUCMS_2L)
| 2
| 8 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUOM 45K phones (VM-CUCMS_4L)
| 4
| 8 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSM 10K Phones (VM-CUCMS_2)
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUSM 45K Server (VM-CUCMS_4)
| 4
| 4 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSSM 10K phones (VM-CUCMS_1)
| 1
| 4 GB
| 1x 60 GB
|
|
| 1
| 
|-
! CUSSM 45K Phones
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUCMS 10K phones Co-resident (VM_CUCMS_8)
| 8
| 16 GB
| 1x 320 GB (2)
| 100
| 500
| 1
| 
|}

Notes: (1) IOPS are for each CM publisher synced in parallel. If only one CM publisher then IOPS are 100/500. The maximum figures would be expected during nightly Infrastructrure or Subscriber syncs. (2) PM requires SAS or SCSI drives for deployments over 1K phones up to 10k phones (Disks must be aligned) (3) PM requires FC SAS for deployments over 10K phones (Disks must be aligned)

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise Systems'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K Server OVA]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K to 10K Server OVA]
| 4
| 4 GB
| 1x 40 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K App/Web Server OVA]
| 4
| 4 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K Database Server OVA]
| 4
| 8 GB
| 1x 120 GB
| 1
| 
|}

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Hosted Collaboration Solution'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283112898&flowid=20421&softwareid=282773197&release=8.0&rellifecycle=&relind=AVAILABLE&reltype=latest CUOM+CUSM 1K phones for HCS (HCS_OM&SM_1K)]
| 1
| 3 GB
| 1x 50 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283315737&flowid=19121&softwareid=281934350&release=2.2&rellifecycle=&relind=AVAILABLE&reltype=latest CUPM 1K phones for HCS (HCS_PM_1K)]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|}

== Unified Contact Center Enterprise ==

See also:

*[[Unified Contact Center Enterprise]]
*[http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Capacities_and_VM_Configuration_Requirements Unified CCE OVA Templates]
*See also [http://docwiki.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE#Unified_CCE_Scalability_Impacts Scalability Impacts]

Templates are available for Windows Server 2003 and Windows Server 2008 R2. [http://www.cisco.com/cisco/software/release.html?mdfid=268439622&release=1.1&relind=AVAILABLE&flowid=5210&softwareid=283914286&rellifecycle=&reltype=latest Download] the appropriate OVA file for the Windows OS that you are configuring. When you deploy the OVA, a drop-down list of the configurations are presented allowing you to select the appropriate configuration for the UCCE sized component that you are installing.

 

{| border="1" cellspacing="3" cellpadding="3"
|- style="background: rgb(229,228,226)"
! Configuration Name
! vCPU Cores
! vRAM / Memory (GB)
! vDisk (GB)
! vNIC 
! Notes
|-
| colspan="7" | '''Note: Windows Server 2008 R2 configurations are contained in the UCCE_8.5_win2008_vmv7_v1.1.ova file, Windows Server 2003 configurations are contained in the UCCE_8.5_win2003_vmv7_v1.1.ova file'''
|-
| '''Router 8000 agents'''
| 2
| 4
| 1 x80
| 2
|  
|-
| '''Logger 8000 agents'''
| 4
| 4
| 1x 80 for OS 1x 150 for DB
| 2
| The two vDisks can be in the same datastore 
|-
| '''Rogger 4000 agents'''
| 4
| 4
| 1x 80 for OS 1x 150 for DB
| 2
| The two vDisks can be in the same datastore 
|-
| '''Agent PG – CTIOS 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''Agent PG – CAD 1000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''Agent PG – CTIOS 450 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Agent PG – CAD 297 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''MR PG 2000 agents 10 pims'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''MR PG 1000 agents 5 pims'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''VRU PG 9600 ports 10 pims'''
| 2
| 2
| 1x 80
| 2
|  
|-
| '''VRU PG 1200 ports 4 pims'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Avaya ACD PG'''
| 2
| 4
| 1x 80
| 2
| See the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted] for capacity information.
|-
| '''TDM ACD PG 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''TDM ACD PG 250 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''UCC Gateway PG 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''UCC Gateway PG 450 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Administration Client'''
| 1
| 2
| 1x 40
| 1
|  (Client AW)
|-
| '''Administration Server - AW'''
| 1
| 2
| 1x 40
| 1
|  
|-
| '''AW-HDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
|  (200 reporters.) The two vDisks can be in the same datastore
|-
| '''AW-HDS-DDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
|  (200 reporters.) The two vDisks can be in the same datastore
|-
| '''HDS-DDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
| (200 reporters.) The two vDisks can be in the same datastore  
|-
| '''CCMP single box 1500 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP Web/App Svr 8000 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP with Config AW 1500 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP DB only 8000 agents'''
| 8
| 4
| 1x 250
| 1
|  
|}

== Unified Customer Voice Portal ==

See also:

*[[Unified Customer Voice Portal]]
*[[Unified Customer Voice Portal#Unified_CVP_Component_Capacities_and_VM_Configuration_Requirements|Unified CVP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Unified Customer Voice Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CVP Call Server + VXML Server (co-located Call Server and VXML Server) (Media Server is optionally included depending on the conditions. See CVP co-residency section for detail)
| 4
| 4 GB
| 1x 146 GB
| 1
| Template Name: Cisco Unified CVP Call Server-VXML Server.ova
|-
! Unified CVP Reporting Server (Large)
| 4
| 4 GB
| Disk 1 - 72 GB, Disk 2 - 438 GB
| 1
| Template Name: Cisco Unified CVP Reporting Server.ova
|-
! Unified CVP Operations Console
| 2
| 2 GB
| 1x 20 GB
| 1
| Template Name: Cisco Unified CVP Operations Console.ova
|}

== Cisco MediaSense ==

See also:

*[[Virtualization for Cisco MediaSense]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco MediaSense OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco MediaSense'''
|-
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! CMS_6T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 146 GB (thick provisioning)
| 1
| rowspan="3" | Release 8.5(1)
|-
! CMS_12T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 300 GB (thick provisioning)
| 1
|-
! CMS_expansion_server_v8.5_vmv7
| 7 
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_12T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 150 GB (thick provisioning) 
| 1
| rowspan="4" | Release 8.5(2)
|-
! CMS_24T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 300 GB (thick provisioning) 
| 1
|-
! CMS_60T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 600 GB (thick provisioning) 
| 1
|-
! CMS_expansion_server_v8.5.2_vmv7
| 7
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_SRE_v8.5_vmv7
| 2
| 6 GB
| 2 x 80 GB (thick provisioning) 1 x 200 GB (thick provisioning) for Media storage
| 1 (with static MAC address)
| Release 8.5(4)
|}

== Cisco Unified Intelligence Center ==

See also:

*[[Cisco Unified Intelligence Center]]
*[[Cisco Unified Intelligence Center#Unified_IC_Component_Capacities_and_VM_Configuration_Requirements|Cisco Unified Intelligence Center OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Intelligence Center'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=282163829&flowid=5228&softwareid=283776220&release=8.0(3)&relind=AVAILABLE&rellifecycle=&reltype=latest CUIC (200 Reporting Users)]
| 4
| 6 GB
| 1x 146 GB
| 1
|
|}

== Cisco Unified Contact Center Management Portal ==

See also:

*[[Support for CCMP with UCCE on UCS Hardware|Cisco Unified Contact Center Management Portal]]
*[[Support for CCMP with UCCE on UCS Hardware#CCMP_Component_Capacities_and_VM_Configuration_Requirements|Unified CCMP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Management Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CCMP (1500 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (Web/App Srv Only) (8000 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (DB Only) (8000 Agents)
| 8
| 4 GB
| 1x 250 GB
| 1
| 
|}

== Cisco SocialMiner ==

See also:

*[[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613136&softwareid=283733464&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco SocialMiner OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco SocialMiner'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Standard Production Server
| 4
| 12 GB
| 1x 146 GB and 1x 256 GB
| 1
| 
|}

== Cisco Unfied Email Interaction Manager and Web Interaction Manager ==

  

{| border="1" cellspacing="1" cellpadding="1"
|-
! scope="col" | Application, OVA Capacity and Notes+Download Link
! scope="col" | Contents
! scope="col" | No of VM's to deploy of each component
! scope="col" | vCPU
! scope="col" | vDisk
! scope="col" | vRAM/Memory
|-
| rowspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 50 Agents(All in One)]
| Web Server
| 1
| 1
| 1 x 80GB
| 2
|-
| Application, Services Server ,File server Messaging Server and  Database server
| 1
| 4
| 1 x 150GB
| 4
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 80 Agents]
| Web Server
| 1
| 1
| 1 x 80GB
| 2
|-
| Application server
| 1
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 200 GB for DB
| 4
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 120 Agents]
| Web Server
| 1
| 1
| 1 x 80GB
| 2
|-
| Application server
| 1
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 200 GB for DB
| 4
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 240 Agents]
| Web Server
| 2
| 2
| 1 x 80GB
| 2
|-
| Application server
| 2
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 200 GB for DB
| 8
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 360 Agents]
| Web Server
| 3
| 2
| 1 x 80GB
| 2
|-
| Application server
| 3
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 500 GB for DB
| 16
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 480 Agents]
| Web Server
| 4
| 2
| 1 x 80GB
| 2
|-
| Application server
| 4
| 2
| 1 x 80GB
| 4
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 500 GB for DB
| 16
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 4
|-
| rowspan="6" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 600 Agents]
| Web Server
| 5
| 2
| 1 x 80GB
| 2
|-
| Application server
| 5
| 2
| 1 x 80GB
| 4
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 500 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 4
|}

 

 

  

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications Virtualization Downloads (including OVA/OVF Templates)

2011-12-08T19:42:53Z

Sdurvasu: /* Cisco Unified Contact Center Express/Cisco IP Intelligent Voice Response */

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

= Supported Virtual Machine OVA Templates =

A virtual machine template defines the configuration of the virtual machine's virtual hardware. Open Virtualization Format (OVF) is an open standard for describing a virtual machine template, and Open Virtualization Archive (OVA) is an open standard to package and distribute these templates. Files in OVA format have an extension of ".ova".

Cisco Unified Communications applications '''must''' use one of the supported virtual machine configurations in the tables below in order to be supported. The OVAs contain virtual hard disks with pre-aligned disk partitions. Using the OVA is the only way to deploy the UC applications on aligned disks. Using the OVA also guarantees that all configuration of the virtual machine is correct and supported.

In the tables below '''users''' refers to the [http://tools.cisco.com/cucst/faces/login.jsp Cisco Unified Communications Sizing Tool] and the [http://www.cisco.com/go/ucsrnd design guides] for the indicated user count at a particular BHCA, number of devices per user, device mix per VM, etc. Actual capacity and total supported devices will be design-dependent; please follow all rules in the design guides and sizing tools.

 See [[Downloading OVA Templates for UC Applications]] for more information on how to download OVA templates for UC Applications.

For '''Specifications-based''' deployments (non TRC deployments), the CPU core count AND the CPU core speed correspond to physical CPU cores and physical CPU core speeds. Both are required to be met to support a full load VM OVA. At this time, only core speed for full load is defined. Do not use lower physical CPU core speeds until Cisco defines minimum speed for lower load levels. Cisco TAC will not troubleshoot a VM that is not receiving sufficient CPU cycles.

== Unified Communications Manager ==

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=268439621&catid=278875240 General OVA Template Download Location] 
*[[OVA Template Details for Unifed CM Release 8.0]] 
*[[OVA Template Details for Unifed CM Release 8.5]] 
*[[OVA Template Details for Unifed CM Release 8.6]] 

 

== Cisco Emergency Responder ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Emergency Responder'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 12,000 users (C200 only)]
| 2 @ 2.13 GHz each (600 MHz reserved)
| 4 GB (4 GB reserved)
| 1 x 80 GB
| 1
|
Use on C200 M2 TRC#1 only.

Limits:

:*12,000 IP phones
:*2,500 analog phones
:*1,200 roaming phones (per Emergency Responder cluster)
:*500 LAN switches
:*30,000 switch ports
:*3,000 ERLs

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 20,000 users]
| 1 @ 2.55 MHz (600 MHz reserved)
| 2.25 GB (2.304 GB reserved)
| 1 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

Limits:

:*20,000 IP phones
:*5,000 analog phones
:*2,000 roaming phones (per Emergency Responder cluster)
:*1,000 LAN switches
:*60,000 switch ports
:*7,500 ERLs

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 30,000 users]
| 2 @ 2.55 MHz each
| 6 GB
| 2 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

Limits:

:*30,000 IP phones
:*10,000 analog phones
:*3,000 roaming phones (per Emergency Responder cluster)
:*2,000 LAN switches
:*120,000 switch ports
:*10,000 ERLs

|}

 

== Session Manager Edition ==

{| border="1"
|+ '''Supported OVA Templates: Session Manager Edition'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&isPlatform=Y&mdfid=282827095&sftType=Unified+Communications+Manager+Virtual+Machine+Templates&treeName=Voice+and+Unified+Communications&modelName=Cisco+Unified+Communications+Manager+Version+8.0&mdfLevel=Software%20Version/Option&treeMdfId=278875240&modifmdfid=null&imname=&hybrid=Y&imst=N Use CUCM "7500 users"]
| See CUCM "7500 users"
| See CUCM "7500 users"
| See CUCM "7500 users"
| See CUCM "7500 users"
|
|}

 

== Unified Attendant Consoles ==

{| border="1"
|+ '''Supported OVA Templates: Unified Attendant Consoles'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! OVA for CUxAC
| 1 @ 2.55 GHz
| 2 GB
| 1x 80GB
| 1
| Note: Cisco does not provide preconfigured OVA files for CUxAC. Please build manually using these requirements. CUxAC requires a VM to meet or exceed minimum physical server specs described [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/data_sheet_c78-520987.html on the CUxAC datasheet]
|}

 

== Cisco Intercompany Media Engine ==

{| style="width: 712px; height: 416px" border="1"
|+ '''Supported OVA Templates: Cisco Intercompany Media Engine, Release 8.6(2)'''
|- style="background: rgb(229,228,226)"
! rowspan="2" | VM OVA Capacity 
! colspan="5" | VM OVA Parameters 
! rowspan="2" | Notes 
|- style="background: rgb(229,228,226)"
! vCPU Cores (= Physical Cores)
! Physical CPU Load was Calibrated To
! vRAM (=Physical Memory)
! vDisk (=Physical space)
! vNIC
|-
!
CIME 5 peer IDs node Only for non-BE6K/C200M2 TRC#1

| 2 (with 3600 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 1x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or BE6000. Up to 5 peer IDs.
 

|-
!
CIME 10 peer IDs node Only for non-BE6K/C200M2 TRC#1

| 4 (with 7200 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 2x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or BE6000. Up to 10 peer IDs.
 

|}

 

 

== Cisco Unity Connection ==

*[http://www.cisco.com/cisco/software/type.html?mdfid=283062758&flowid=5455 General Unity Connection OVA Template Download Location] 
*[[OVA Template Details for Unity Connection Release 8.0]] 
*[[OVA Template Details for Unity Connection Release 8.5]] 
*[[OVA Template Details for Unity Connection Release 8.6.1]] 
*[[OVA Template Details for Unity Connection Release 8.6.2]] 

 

== Cisco Unity ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Unity'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! 5000 users
| 2 (requires VMware CPU Affinity)
| 4 GB
|
4x 24 GB

:*vDisk 1 = Operating system
:*vDisk 2 = Cisco Unity binaries
:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

| 1
|
*Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
*Limits:

:*48 ports
:*36 text-to-speech ports

|-
! 15,000 users
| 4 (requires VMware CPU Affinity)
| 4 GB
|
4x 24 GB

:*vDisk 1 = Operating system
:*vDisk 2 = Cisco Unity binaries
:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

| 1
|
*Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
*Limits:

:*144 ports
:*36 text-to-speech ports

|}

 

== Cisco Unified Presence ==

See also:

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=280448682&i=rs General OVA Template Download Location]
*[[OVA Template Details for Unified Presence Release 8.0(x)]] 
*[[OVA Template Details for Unified Presence Release 8.5(x)]] 
*[[OVA Template Details for Unified Presence Release 8.6(1)]] 
*[[OVA Template Details for Unified Presence Release 8.6(2)]] 
*[[OVA Template Details for Unified Presence Release 8.6(3)]] 
*[[OVA Template Details for Unified Presence Release 8.6(4)]] 

 

== Cisco Unified Contact Center Express/Cisco Unified IP Intelligent Voice Response (IP IVR) ==

{{Note| The information for Unified IP IVR is the same as Unified CCX.}}

See also:

*[[Virtualization for Unified CCX]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest| Unified CCX OVA Templates]: {{Note| Unified CCX OVA version 2 is for use with ESXi 4.1. Please follow [[Unified Communications VMware Requirements]] for ESXi 4.1 requirements (VMware Tools upgrade, LRO disabling, etc.)}}

 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Express'''
|- style="background: rgb(229,228,226)"
! colspan="2" | Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 100 agents] (Release 8.5(1))
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 300 agents] (Release 8.0(2) and Release 8.5(1))
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 400 agents] (Release 8.5(1))
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! rowspan="3" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=latest Single OVA] (Release 8.5 (1) or later)
! 100 agents
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
|
|-
! 300 agents
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! 400 agents
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.2]
| 2
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = Optional - can be used to hold SQL Server Data files

| 1
|
Capacities

:*900 named users
:*300 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Base Server Configuration (CR/QM/AQM)]
| 2
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)

| 1
|
Capacities

:*3600 named users
:*1200 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Recording Server Configuration (CR/QM/AQM)]
| 4
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM recording service binaries
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recording cache

| 1
|
Capacities

:*300 concurrent voice recordings for Server (SPAN) and Network recording
:*150 concurrent voice and screen recordings, recordings for Server (SPAN) and Network recording

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.1]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = Optional - can be used to hold SQL Server Data files

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.1 Base Server Configuration (CR/QM/AQM)]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage)

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM Configuration (CR/QM/AQM)]
| 2
| 2 GB
|
2x 146 GB

:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage )

| 2
|
Capacities

:*300 named users
:*150 concurrent users
:*150 voice recordings, for all recording types (desktop, server and network)
:*150 voice+screen recordings, for all recording types (desktop, server and network)

|}

== UC Management Suite (PM, OM, SM, SSM) ==

There are different OVAs for premise UC on UCS deployments vs. Hosted Collaboration Solution deployments.

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise UC on UCS Deployments'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! IOPS (avg) (1)
! IOPS (max) (1)
! vNIC
! Notes
! 
|-
! CUPM up to 1K phones (VM-CUCMS_1S)
| 1
| 2 GB
| 1x 30 GB
| 100
| 500
| 1
| 
|-
! CUPM 1K to 10K phones
| 4
| 4 GB
| 1x 40 GB (2)
| 100
| 500
| 1
| 
|-
! CUPM 10K to 60K phones app server
| 4
| 4 GB
| 1x 30 GB(3)
| 100
| 500
| 1
| requires DB VM
|-
! CUPM 10K to 60K phones database server
| 4
| 8 GB
| 1x 120 GB(3)
| 100
| 500
| 1
| requires App VM
|-
! CUOM/SM 1K phones
| 1
| 3 GB
| 1x 50 GB
| 6
| 15
| 1
| 
|-
! CUOM 10K phones (VM-CUCMS_2L)
| 2
| 8 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUOM 45K phones (VM-CUCMS_4L)
| 4
| 8 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSM 10K Phones (VM-CUCMS_2)
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUSM 45K Server (VM-CUCMS_4)
| 4
| 4 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSSM 10K phones (VM-CUCMS_1)
| 1
| 4 GB
| 1x 60 GB
|
|
| 1
| 
|-
! CUSSM 45K Phones
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUCMS 10K phones Co-resident (VM_CUCMS_8)
| 8
| 16 GB
| 1x 320 GB (2)
| 100
| 500
| 1
| 
|}

Notes: (1) IOPS are for each CM publisher synced in parallel. If only one CM publisher then IOPS are 100/500. The maximum figures would be expected during nightly Infrastructrure or Subscriber syncs. (2) PM requires SAS or SCSI drives for deployments over 1K phones up to 10k phones (Disks must be aligned) (3) PM requires FC SAS for deployments over 10K phones (Disks must be aligned)

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise Systems'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K Server OVA]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K to 10K Server OVA]
| 4
| 4 GB
| 1x 40 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K App/Web Server OVA]
| 4
| 4 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K Database Server OVA]
| 4
| 8 GB
| 1x 120 GB
| 1
| 
|}

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Hosted Collaboration Solution'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283112898&flowid=20421&softwareid=282773197&release=8.0&rellifecycle=&relind=AVAILABLE&reltype=latest CUOM+CUSM 1K phones for HCS (HCS_OM&SM_1K)]
| 1
| 3 GB
| 1x 50 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283315737&flowid=19121&softwareid=281934350&release=2.2&rellifecycle=&relind=AVAILABLE&reltype=latest CUPM 1K phones for HCS (HCS_PM_1K)]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|}

== Unified Contact Center Enterprise ==

See also:

*[[Unified Contact Center Enterprise]]
*[http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Capacities_and_VM_Configuration_Requirements Unified CCE OVA Templates]
*See also [http://docwiki.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE#Unified_CCE_Scalability_Impacts Scalability Impacts]

Templates are available for Windows Server 2003 and Windows Server 2008 R2. [http://www.cisco.com/cisco/software/release.html?mdfid=268439622&release=1.1&relind=AVAILABLE&flowid=5210&softwareid=283914286&rellifecycle=&reltype=latest Download] the appropriate OVA file for the Windows OS that you are configuring. When you deploy the OVA, a drop-down list of the configurations are presented allowing you to select the appropriate configuration for the UCCE sized component that you are installing.

 

{| border="1" cellspacing="3" cellpadding="3"
|- style="background: rgb(229,228,226)"
! Configuration Name
! vCPU Cores
! vRAM / Memory (GB)
! vDisk (GB)
! vNIC 
! Notes
|-
| colspan="7" | '''Note: Windows Server 2008 R2 configurations are contained in the UCCE_8.5_win2008_vmv7_v1.1.ova file, Windows Server 2003 configurations are contained in the UCCE_8.5_win2003_vmv7_v1.1.ova file'''
|-
| '''Router 8000 agents'''
| 2
| 4
| 1 x80
| 2
|  
|-
| '''Logger 8000 agents'''
| 4
| 4
| 1x 80 for OS 1x 150 for DB
| 2
| The two vDisks can be in the same datastore 
|-
| '''Rogger 4000 agents'''
| 4
| 4
| 1x 80 for OS 1x 150 for DB
| 2
| The two vDisks can be in the same datastore 
|-
| '''Agent PG – CTIOS 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''Agent PG – CAD 1000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''Agent PG – CTIOS 450 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Agent PG – CAD 297 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''MR PG 2000 agents 10 pims'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''MR PG 1000 agents 5 pims'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''VRU PG 9600 ports 10 pims'''
| 2
| 2
| 1x 80
| 2
|  
|-
| '''VRU PG 1200 ports 4 pims'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Avaya ACD PG'''
| 2
| 4
| 1x 80
| 2
| See the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted] for capacity information.
|-
| '''TDM ACD PG 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''TDM ACD PG 250 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''UCC Gateway PG 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''UCC Gateway PG 450 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Administration Client'''
| 1
| 2
| 1x 40
| 1
|  (Client AW)
|-
| '''Administration Server - AW'''
| 1
| 2
| 1x 40
| 1
|  
|-
| '''AW-HDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
|  (200 reporters.) The two vDisks can be in the same datastore
|-
| '''AW-HDS-DDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
|  (200 reporters.) The two vDisks can be in the same datastore
|-
| '''HDS-DDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
| (200 reporters.) The two vDisks can be in the same datastore  
|-
| '''CCMP single box 1500 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP Web/App Svr 8000 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP with Config AW 1500 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP DB only 8000 agents'''
| 8
| 4
| 1x 250
| 1
|  
|}

== Unified Customer Voice Portal ==

See also:

*[[Unified Customer Voice Portal]]
*[[Unified Customer Voice Portal#Unified_CVP_Component_Capacities_and_VM_Configuration_Requirements|Unified CVP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Unified Customer Voice Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CVP Call Server + VXML Server (co-located Call Server and VXML Server) (Media Server is optionally included depending on the conditions. See CVP co-residency section for detail)
| 4
| 4 GB
| 1x 146 GB
| 1
| Template Name: Cisco Unified CVP Call Server-VXML Server.ova
|-
! Unified CVP Reporting Server (Large)
| 4
| 4 GB
| Disk 1 - 72 GB, Disk 2 - 438 GB
| 1
| Template Name: Cisco Unified CVP Reporting Server.ova
|-
! Unified CVP Operations Console
| 2
| 2 GB
| 1x 20 GB
| 1
| Template Name: Cisco Unified CVP Operations Console.ova
|}

== Cisco MediaSense ==

See also:

*[[Virtualization for Cisco MediaSense]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco MediaSense OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco MediaSense'''
|-
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! CMS_6T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 146 GB (thick provisioning)
| 1
| rowspan="3" | Release 8.5(1)
|-
! CMS_12T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 300 GB (thick provisioning)
| 1
|-
! CMS_expansion_server_v8.5_vmv7
| 7 
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_12T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 150 GB (thick provisioning) 
| 1
| rowspan="4" | Release 8.5(2)
|-
! CMS_24T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 300 GB (thick provisioning) 
| 1
|-
! CMS_60T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 600 GB (thick provisioning) 
| 1
|-
! CMS_expansion_server_v8.5.2_vmv7
| 7
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_SRE_v8.5_vmv7
| 2
| 6 GB
| 2 x 80 GB (thick provisioning) 1 x 200 GB (thick provisioning) for Media storage
| 1 (with static MAC address)
| Release 8.5(4)
|}

== Cisco Unified Intelligence Center ==

See also:

*[[Cisco Unified Intelligence Center]]
*[[Cisco Unified Intelligence Center#Unified_IC_Component_Capacities_and_VM_Configuration_Requirements|Cisco Unified Intelligence Center OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Intelligence Center'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=282163829&flowid=5228&softwareid=283776220&release=8.0(3)&relind=AVAILABLE&rellifecycle=&reltype=latest CUIC (200 Reporting Users)]
| 4
| 6 GB
| 1x 146 GB
| 1
|
|}

== Cisco Unified Contact Center Management Portal ==

See also:

*[[Support for CCMP with UCCE on UCS Hardware|Cisco Unified Contact Center Management Portal]]
*[[Support for CCMP with UCCE on UCS Hardware#CCMP_Component_Capacities_and_VM_Configuration_Requirements|Unified CCMP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Management Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CCMP (1500 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (Web/App Srv Only) (8000 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (DB Only) (8000 Agents)
| 8
| 4 GB
| 1x 250 GB
| 1
| 
|}

== Cisco SocialMiner ==

See also:

*[[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613136&softwareid=283733464&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco SocialMiner OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco SocialMiner'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Standard Production Server
| 4
| 12 GB
| 1x 146 GB and 1x 256 GB
| 1
| 
|}

== Cisco Unfied Email Interaction Manager and Web Interaction Manager ==

  

{| border="1" cellspacing="1" cellpadding="1"
|-
! scope="col" | Application, OVA Capacity and Notes+Download Link
! scope="col" | Contents
! scope="col" | No of VM's to deploy of each component
! scope="col" | vCPU
! scope="col" | vDisk
! scope="col" | vRAM/Memory
|-
| rowspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 50 Agents(All in One)]
| Web Server
| 1
| 1
| 1 x 80GB
| 2
|-
| Application, Services Server ,File server Messaging Server and  Database server
| 1
| 4
| 1 x 150GB
| 4
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 80 Agents]
| Web Server
| 1
| 1
| 1 x 80GB
| 2
|-
| Application server
| 1
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 200 GB for DB
| 4
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 120 Agents]
| Web Server
| 1
| 1
| 1 x 80GB
| 2
|-
| Application server
| 1
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 200 GB for DB
| 4
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 240 Agents]
| Web Server
| 2
| 2
| 1 x 80GB
| 2
|-
| Application server
| 2
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 200 GB for DB
| 8
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 360 Agents]
| Web Server
| 3
| 2
| 1 x 80GB
| 2
|-
| Application server
| 3
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 500 GB for DB
| 16
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="5" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 480 Agents]
| Web Server
| 4
| 2
| 1 x 80GB
| 2
|-
| Application server
| 4
| 2
| 1 x 80GB
| 4
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 500 GB for DB
| 16
|-
| File and Messaging Server
| 1
| 2
| 1 x 80GB
| 4
|-
| rowspan="6" | [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all 600 Agents]
| Web Server
| 5
| 2
| 1 x 80GB
| 2
|-
| Application server
| 5
| 2
| 1 x 80GB
| 4
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 500 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 4
|}

 

 

  

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications VMware Requirements

2011-12-04T14:58:13Z

Sdurvasu: 1 revision

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

This article describes VMware requirements, feature support, and services and support contracts for virtualized Unified Communications applications.

== Introduction: Mandatory VMware Products and Services ==

'''Note:''' This page only covers VMware product/version/feature support.

:*It does '''not''' cover compute/network/storage hardware support policy for UC virtualization.
:*It does '''not''' cover application co-residency support policy for UC virtualizatoin.
:*See other links at http://www.cisco.com/go/uc-virtualized for these details.

 

'''VMware vSphere ESXi is mandatory''' for UC virtualization and UC on UCS.

:*UC is only supported on UCS servers with VMware vSphere ESXi.
:*See rest of this page for other details on VMware product, version and feature support.
:*'''Nonvirtualized, physical, or bare-metal installations are not supported''' for UC on UCS.

 

'''VMware vCenter''' is:

:*'''Mandatory''' for all Specs-based deployments
:*'''Optional''' for Tested Reference Configuration deployments.

 

For UC on UCS, VMware vSphere ESXi and vCenter may be purchased from Cisco or customer provided. For specs-based with HP/IBM, all VMware software must be customer-provided. See [[Before You Buy or Deploy - Considerations for Design and Procurement]] for information on VMware purchase options. 

Compatibility of UC apps/versions with VMware vSphere ESXi versions varies by UC app and is outlined later in this document. See the following links for details on "legacy" virtualization support (i.e. 7.x of UC apps with VMware vSphere on limited 3rd-party servers):

:*[http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html Cisco Unity Virtualization Design Guide]
:*[http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_7_5/user/guide/VirtualizationGde753.pdf Virtualization Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted 7.5(3)]

 

'''Note:''' in all cases, the customer is required to have a valid service contract (either with Cisco or with VMware, depending on what/how purchased) to be supported. See [[#Services_and_Support_Contracts_for_VMware_are_Required|Services and Support Contracts for VMware are Required]] for how to ensure this is done for different Editions of Vmware vSphere ESXi. 

== Supported Virtualization Hypervisor Vendors ==

At this time, the only vendor supported for UC is VMware.

Other vendors/products - such as Microsoft Hyper-V, Citrix Xen, Red Hat KVM - are not supported for Cisco UC virtualization. 

== Supported VMware Products ==

VMware vSphere ESXi is required for Cisco UC virtualization.

*ESX and ESXi are architecture options for VMware vSphere ([http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html click here for a comparison]). UC only supports ESXi. Recall that vSphere 3.x and 4.x offered both options, but 5.0+ only offers ESXi.
*VMware vSphere ESX, regardless of version, is not supported for UC. This is due to technical reasons and [http://blogs.vmware.com/vsphere/2010/07/esx-41-is-the-last-esx-what-do-i-do-now.html VMware’s direction to transition from ESX to ESXi]. Note a VMware ESX cluster can contain VMware ESXi servers running Cisco Unified Communications.
*No other VMware server virtualization products are supported.

 

== Supported Versions of VMware vSphere ESXi ==

The minimum version for VMware vSphere ESXi is 4.0. But note a higher minimum version may be required depending on what UC apps/versions you run (see tables below) and what hardware you select.

*Note that use of VMware vSphere ESXi 4.1 requires [[Disable LRO|'''disabling the "LRO" setting as described here''']].
*Versions of VMware vSphere ESXi prior to 4.0 are not supported due to technical reasons.
*Each UC app/version will specify the required compatible Major Releases and Minor Releases of VMware vSphere ESXi (e.g. 4.0 or 4.1) in the tables below.
**Unlisted Major/Minor versions are not supported.
**Unless otherwise indicated, the base Major/Minor version shown is the minimum required.
**Some UC apps will also require a minimum Maintenance Release and will indicate if this is the case. Otherwise UC does not specify or recommend patches, updates or Maintenance Releases (e.g. 4.0 U1) for a required Major/Minor Release of vSphere ESXi. Follow recommendations of the server vendor and VMware for what you should use. Unless otherwise indicated by a UC app, UC supports all VMware vSphere ESXi patches, updates and Maintenance Releases for a supported Major/Minor Release at time of VMware launch as long as the server vendor supports them.

 

=== VMware vSphere ESXi Version Support for Call Processing and System Management Applications ===

{| class="wikitable FCK__ShowTableBorders"
|-
!
Application 

! VMware vSphere ESXi 4.0 
! VMware vSphere ESXi 4.1 
! VMware vSphere ESXi 5.0 
|-
| Unified Communications Manager (Unified CM)
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
| Not supported
|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Cisco Emergency Responder (CER)
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Session Manager Edition (SME)
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Unified Attendant Consoles
| 8.0(3)+, 8.5+
| 8.6+
| Not supported
|-
| UC Management Suite (OM, SM, SSM, PM)
| 7.1 and later
| 7.1 and later
| Not supported
|-
| Cisco Intercompany Media Engine (CIME)
| Not supported
| 8.6(2)+
| Not supported
|}

=== VMware vSphere ESXi Version Support for Messaging and Presence Applications ===

{| style="width: 812px; height: 108px" class="wikitable FCK__ShowTableBorders"
|-
! Application 
! VMware vSphere ESXi 4.0 or 4.0 Update 1 
! VMware vSphere ESXi 4.1
|-
| Cisco Unity Connection
| 8.0(2) and later
| 8.0(3) and later
|-
| Cisco Unity
| 7.x and later
| 7.x and later
|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
| 8.0(2) and later
| 8.0(2) and later
|}

 

=== VMware vSphere ESXi Version Support for Contact Center Applications ===

{{Note| For Virtual Machines that need '''more than 4 vCPUs''', the VMware vSphere ESXi '''Enterprise Plus''' licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)}}

{| style="width: 816px; height: 396px" class="wikitable FCK__ShowTableBorders"
|-
! Application
! VMware vSphere ESXi 4.0 and 4.0 Updates
! VMware vSphere ESXi 4.1  and 4.1 Updates
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]]
| 8.0(2) and later or 8.5(1) and later
| 8.0(2) SU2 and later or 8.5(1) and later
|-
| [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Work Force Optimization (WFO), Quality Management (QM),and Work Force Management (WFM)]
| 8.5(1) and later
| 8.5(2) and later
|-
| [[Unified Contact Center Enterprise]] 
| ESXi 4.0 Update 1 (minimum required). See below
| See below
|-
| - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tools
| 8.0(2) and later or 8.5(1) and later
| 8.0(2) and later or 8.5(1) and later
|-
| [[Virtualization for Unified Intelligence Center|Cisco Unified Intelligence Center]] 
| 8.0(3) and later
| 8.5(2) and later
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]
| 8.0(2) and later or 8.5(1) and later
| 8.0(2) and later or 8.5(1) and later
|-
| [[Unified Customer Voice Portal]] (all components) 
| 8.0(1) and later or 8.5(1) and later
| 8.0(1) and later or 8.5(1) and later
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| 8.5(1) and later
| 8.5(2) and later
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| 8.5(1) and later
| 8.5(1) and later
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Unified Email Interaction Manager and Web Interaction Manager]]
| 4.3(2) and later
| 4.3(2) and later
|}

== Support of Cisco VN-Link and Cisco Nexus 1000V ==

Note that Cisco Unified Contact Center Enterprise does NOT support this – see [[UCS Network Configuration for UCCE|UCS Network Configuration for Unified CCE]].

Unless otherwise indicated above, Cisco VN-Link and Cisco Nexus 1000V are supported by UC applications that support the VMware vNetwork Distributed Switch (see [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]).

Cisco VN-Link, Cisco Nexus® 1000V and VMware vNetwork Distributed Switch all require VMware ESXi Enterprise Plus Edition (see [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]). Other editions do not support these capabilities.

For UC on UCS B-series, Cisco UCS 6100 does not currently support Layer 3 to Layer 2 COS markings. Additionally, the UC applications and operating systems cannot set the Layer 2 COS markings. Use of Cisco Nexus® 1000V is therefore strongly recommended as this is the only way to manage traffic congestion through the current UCS 6100. Please recall that traffic congestion risk will vary and is dependent on many factors such as UC vs. non-UC virtual machine count and their traffic characteristics across all blades, chassis and fabric extenders connected to the same UCS 6100.

For UC on UCS C-series, Cisco Nexus® 1000V is recommended but not mandatory as there is no intermediate UCS 6100 to design around.

 For more information on Cisco VN-Link and Cisco Nexus 1000V, see http://www.cisco.com/en/US/netsol/ns894/index.html and http://www.cisco.com/en/US/products/ps9902/index.html.

== Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client ==

 '''VMware vSphere Client''' (formerly branded VI Client) and '''VMware vCenter''' are management consoles for VMware vSphere hosts.

:*vSphere Client is free but only has basic management capabilities.
:*vCenter is not free as it has advanced management capabilities, but note UC may not support every feature in vCenter. vCenter is mandatory for any specs-based deployment.

 

'''VMware vSphere ESXi''' is sold in several '''Editions''' with different levels of feature support.

:*[https://www.vmware.com/products/vsphere/buy/editions_comparison.html Click here for a comparison of VMware vSphere ESXi feature Editions on vmware.com].
::*[http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html Click here for a clarification of “free ESXi 4.1” vs. “vSphere ESXi 4.1 Hypervisor Edition”] (formerly branded as "VMware ESXi Single Server Edition" or “free ESXi”).
::*For details on supported features for 4.x versions of other vSphere ESXi Editions, see your VMware account team. VMware on their web site [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010579 provides a "best effort" comparison here].
:*If buying VMware vSphere ESXi direct from VMware:
::*[http://www.vmware.com/products/vsphere/purchase-advisor/index.html Click here for VMware's Purchase Advisor for vSphere on vmware.com].
::*[https://www.vmware.com/files/pdf/vsphere_pricing.pdf Click here for an overview of VMware vSphere ESXi pricing on vmware.com].

 

There are no UC-specific restrictions on what VMware vSphere ESXi feature Edition you "can" use, but the Edition you "should" use will be determined by VMware licensing rules based on aspects of the UC deployment. The customer is responsible for selecting the correct VMware vSphere ESXi Edition based on their feature and UC application requirements. The following non-exhaustive list is provided for convenience only as examples of what must be considered under VMware's current licensing rules, which are subject to change:

:*If you want to use Cisco Nexus 1000V with UC, that requires the VMware vSphere ESXi feature "Distributed Switch" which is only available in Enterprise Plus Edition.
:*If you want to use a UC virtual machine OVA template with a large quantity of vCPU, verify the VMware vSphere ESXi Edition supports sufficient "vCPU Entitlement" for that OVA's vCPU count.
::*E.g. the Unity Connection 20K user OVA that requires 7 vCPU per VM.
:*Verify all the UC-supported VMware vSphere ESXi features you want to use are [https://www.vmware.com/products/vsphere/buy/editions_comparison.html supported by the Edition you pick].
:*The "Cisco UC Virtualization Hypervisor" is only supported for use with Business Edition 6000 and has the following restrictions:
::*It is not available or transferable for use with any other hardware or software.
::*Server Hardware restricted to UCS C200 M2 TRC#1
::*Max total vRAM across all VMs is 16 GB (of which 14 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Does not support VMware vCenter management. Does not offer any [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features like other Editions].
:*The "Cisco UC Virtualization Foundation" is only supported for use with Business Edition 6000 and UC on UCS.
::*Not available direct from VMware, only sold as part of BE6K or UC on UCS. It is not available or transferable for use with non-UCS hardware or non-UC software.
::*Server Hardware restricted to 2-socket UCS B-Series models and 2-socket UCS C-Series models.
::*Max total vRAM across all VMs is 32 GB (of which 30 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Supports VMware vCenter management (purchased separately). UC-supported [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features] limited to vStorage APIs. All other UC-supported features (including but not limited to VMware High Availability, Data Recovery, vMotion, Distributed Switch, etc.) are not offered.

 

Finally, note that UC may not support all of the features that are included in the VMware vSphere ESXi Edition you pick. This may be because the feature is N/A for a UC deployment, or it has not been sufficiently tested before UC will support, or it requires application enhancements before UC can support.

The table below lists VMware feature support by UC app/version. If the feature is supported, click on its name in the table to view UC caveats and best practices. Feature support may vary by UC app. This site will be updated as new support becomes available.

{{note| feature support for Cisco Unified Contact Center Enterprise varies by component (e.g. Peripheral Gateway) and deployment model (e.g. "Rogger") - this section will give a summary support position, but for individual components see [[Unified Contact Center Enterprise|Support for Virtualization on the ESXi/UCS Platform]].}} 

=== Legend for Feature Support Tables ===

:*Y(C) = Supported with '''C'''aveats - see [[#Best_Practices|Best Practices]] for details
:*Y(P) = '''P'''artial (limited) support only - see [[#Best_Practices|Best Practices]] for details
:*No = the feature is not supported at this time - see [[#Best_Practices|Best Practices]] for alternatives, if any.

=== VMware Feature Support for Call Processing and System Management 8.0(2) through 8.6(1) ===

{| border="1"
|+ ''' '''
|-
! Feature
! Unified CM
! CER
! SME
! Unified Attendant Consoles
! UPM
! UOM, USM, USSM
! CIME 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C)
| Y(C) 
| Y(C) 
| Y(C) 
| Yes
| Y(C) 
| Y(C) 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C)
| Y(C)
|  Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(P)
| Y(P)
| No 
| No 
| Y(P)
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No 
| No 
| No
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)  
| Y(P)  
| Y(P)  
| Y(P)  
| Yes
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C)
| No
| Y(C)
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| Y(C) 
| Y(C)
| Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C) 
| Y(C) 
| Y(C) 
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(C)
| Y(C) 
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C) 
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| Y(C)
| No 
| Y(C)
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 5.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! All vSphere ESXi 5.0 Features
| No
| No
| No
| No
| No
| No 
| No
|}

=== VMware Feature Support for Messaging and Presence 8.0(2) through 8.6(1) ===

{| border="1"
|+ '
|-
! Feature
! Unity Connection
! Unity
! Unified Presence
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(PP
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| Y(C)
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| Y(C) 
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(P)
| No
| Y(P)
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| Y(C) 
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
|- align="center"
! [[#Identity|Identity]]
| No  
| No  
| Y(C) 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| 
|}

 

=== VMware Feature Support for Contact Center 8.0(2) through 8.6(1) ===

{| style="width: 906px; height: 823px" border="1"
|+  
|-
! Feature
! Unified CCX
! Cisco WFO, QM, and WFM
! Unified CCE, CVP
! Unified IC
! Cisco MediaSense
! SocialMiner
! Unfied EIM-WIM
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
|
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C) 
| No
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C)
| Y(C) 
| No
| Y(C) 
| No
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P) 
| No
| Y(P) 
| No
| No
| No
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P) 
| Y(P) 
| Y(P) 
| Y(P) 
| No
| No
| No
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| No
| Y(C) 
| Y(C)
| No
| No
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(P) 
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C)
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
|
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C)
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No
| No
| 
|}

== Best Practices ==

=== Virtual Machine Templates (OVA files) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

See www.dmtf.org for details on the Open Virtualization Format, which describes an OVF Package (a directory of files describing a virtual machine's configuration) and an OVA Package (single tar file containing an OVF Package).

“Template” in this context refers to an OVA file that defines the virtual server (but not the “workload”, i.e. the UC OS and application). Each virtualized UC product provides a set of predefined virtual machine templates (as OVA files) for supported Virtual Machine (VM) configurations. Customers must download and use these OVA template files for initial install, as they cover items such as supported capacity levels and any required OS/VM/SAN “alignment”. OVAs configured differently than the predefined templates are not supported at this time. To download the OVA files, refer to the [[Unified Communications Virtualization Sizing Guidelines|Unified Communications Virtualization sizing guidelines]].

=== Copy Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Copying a Virtual Machine (VM) copies both the virtual server configuration and the workload (UC OS and application) running on that virtual server to a file on networked shared storage. This allows VMs to be copied, then subsequently modified or shut down. This feature effectively provides a method to do full system backup/restore, take system images or revert changes to software versions, user data and configuration changes.

:*Prior to copying, the VM must first be shutdown (which will shut down the virtual server, the UC OS and the UC application).
:*If uploading a VM copy as a “whole system restore”, clustered UC applications such as CUCM will probably require their replication to be manually “fixed” via a CLI command.

=== Restart Virtual Machine on Different ESXi Host ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

A Virtual Machine (VM) file on network/shared storage can be booted on any physical server hosting ESXi that has access to that network shared storage. With multiple physical ESXi hosts connected to the same network shared storage, this can be used to perform:

:*Fast manual server moves, e.g. moving VM from ESXi host A to ESXi host B in another chassis, closet, building, etc.
:*Fast manual server recovery, e.g. moving VM from ESXi host A that has just had a server hardware or VMware failure to ESXi host B that is healthy. See also VMware High Availability and Site Recovery Manager.
:*Setting up software at a staging location to be later moved or deployed elsewhere. For multi-site scenarios, this may instead require “exporting” the VM.

=== Resize Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Similar to adding/removing physical hardware to/from a physical server, you can add/remove virtual hardware (vCPU, vRAM, vDisk, vNIC, etc.) to/from a Virtual Machine (VM) via a software change in VMware’s configuration interfaces. Where supported, this provides the VM equivalent of migration to a more powerful or less powerful server.

:*Any changes to a VM must align with the best practices in [[#Virtual_Machine_Templates_.28OVA_files.29|Virtual Machine Templates (OVA files)]]. VM changes that result in an unsupported OVA configuration are not allowed. Even if you align with supported OVA configurations, desired VM changes may be prevented by one of the other caveats below.
:*Support for adding virtual hardware resources (similar to moving from a less powerful server to a more powerful server, such as MCS 7825 ⇒ MCS 7845) depends on which resource, and which UC product:
::*Adding vCPU is supported for all apps except Unity and Unity Connection, but requires VM to be shutdown first.
::*Adding vRAM is supported but requires VM to be shutdown first.
::*Adding vDisk is not supported as it would require re-partitioning by the application.
:*Adding vNIC is not supported unless the UC app supports multiple network connections with different IP addresses. See best practices for [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]].
:*For all other changes, it is recommended to backup the application, reinstall application on a new OVA file, and restore the application.
:*Removing virtual hardware resources (vCPU, vRAM, vDisk, etc.) is not supported (similar to moving from a more powerful server to a less powerful server, such as MCS 7845 ⇒ MCS 7825). These migrations require backing up the application, reinstalling on a new OVA file, and and restoring the application.
:*Live runtime resizing via the VMware Hot Add feature is not supported.

=== VMware Hot Add ===

Not supported. See [[#Resize_Virtual_Machine|Resize Virtual Machine instead]].

=== Multiple Physical NICs and vNICs ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). Network traffic is switched from physical NICs to “vNIC’s” of the Virtual Machines (VM) via either VMware vSwitch or Cisco Nexus 1000V. Customers can use these multiple NICs for VM network traffic, VMware console access, or management “back-doors” for administrative access, backups, software updates or other traffic that is desired to be segregated from the VM network traffic. All these uses are supported for UC but note that UC apps like CUCM only support a single vNIC with a single IP address.

=== VMware High Availability (HA) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature automatically restarts a Virtual Machine (VM) on the same physical server or a different physical server. It can be used to supplement software redundancy as a means of fast, automated Failed-server recovery when a VM (but not the application) is hung or if there is a fault with the physical host server or VMware software.

:*Failovers to other servers must not result in an unsupported deployment model (e.g. destination server must align with supported co-residency after failover occurs).
:*Does not protect vs. faults with the SAN or network hardware.

=== VMware Site Recovery Manager (SRM) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature provides an automated disaster recovery solution that works on a “site to site” basis, where a “site” comprises physical servers, VMware and SAN storage. Refer to the VMware documentation for requirements to use this feature. There are no special requirements to use this feature with UC apps that support it.

=== VMware Identity ===

The VMware identity feature allows you to copy an existing instance of a virtual Cisco Unified Presence, and change its identity. The identity of a system is made up of every setting that you usually configure during a fresh install (such as IP address, hostname, passwords).

You can then use this new identity for another instance of a Cisco Unified Presence on a virtual machine. This avoids you having to perform a complete installation each time you deploy a new Cisco Unified Presence.

=== VMware vNetwork Distributed Switch ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Supporting apps in UC on UCS may either use this feature, or the Cisco VN-Link technology (such as Cisco Nexus 1000V).

 

=== VMware vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Cl]]ient.

This feature migrates a live, running Virtual Machine (VM) from one physical server to another.

The following applies to any use of vMotion with UC apps:

:*VM must be installed on shared storage (SAN).
:*Source and destination physical servers must be connected to same SAN.
:*Destination physical server must not end up with over-subscribed hardware after the migration. Supported capacity and co-residency rules for UC must be followed before and after the migration.
:*VMware “Long Distance vMotion” (site to site) is not supported.
:*The only supported scenario is a manual move to a different server, e.g. for planned maintenance on the server or VMware software, or during troubleshooting to move software off of a physical server having issues.
:*Use of vMotion for real-time load-balancing of live UC VMs is not supported, whether alone or in conjunction with VMware Dynamic Resource Scheduler (DRS) or Dynamic Power Management (DPM).
:*Moving a shut down VM during a maintenance window, i.e. a "cold migration" or "host to host migration", is not vMotion and is supported.

If the UC app is listed as "Supported with Caveats", then support is as described below:

:*Migration of UC VMs that are live and processing live traffic is supported, but note that Cisco testing cannot cover every possible operational scenario. Testing has shown there is a slight risk of calls in progress being impacted for a few seconds as the migration occurs, with worst case result of the affected calls being dropped. If vMotion is suspected as the cause of dropped calls, customers should gather appropriate application logs as well as performance data from VMware vCenter and send to Cisco TAC for analysis.

If the UC app is listed as "Partial" support, then support is “maintenance mode only” as described below:

:*"Maintenance mode only" - VMware vMotion by definition operates on live VMs, but the VM running the UC app must be “live but quiescent”. I.e. in a maintenance window, not in production, not processing live traffic. This is because during the vMotion cutover, the system is paused, which for real-time UC apps creates service interruption which degrade voice quality after the migration for calls in progress.

 

=== VMware Dynamic Resource Scheduler ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== VMware Dynamic Power Management ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== Long Distance vMotion ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported. Long Distance vMotion is a joint Cisco and VMware validated architecture for using the vMotion feature across data centers. For more information, see http://blogs.cisco.com/datacenter/comments/cisco_and_vmware_validated_architecture_for_long_distance_vmotion/ and http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns836/white_paper_c11-557822.pdf.

=== Storage vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This “customer convenience” feature provides easy migration of a live system from one SAN to another SAN. For UC apps, an easier suggested alternative is to just perform manual VM shutdown and migration to the new SAN. However, if Storage vMotion must be used, it is only under the following conditions:

:*Requires SAN storage.
:*May only be done during a maintenance window with UC VMs shut down.

=== VMware vCenter Update Manager (VUM) ===

NOTE: Support varies by application and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature automates patching and updating of VMware vSphere hosts. Note that Cisco Unified Communications applications upgrades, patches and updates can not be delivered through vCenter Update Manager.

=== VMware Consolidated Backup (VCB) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature provides integration with 3rd-party backup utilities so that they can non-disruptively backup the OS and application in a Virtual Machine (VM). See also VMware Data Recovery and Copy Virtual Machine.

Existing UC app methods of backing up the software continue to be supported.

=== VMware Data Recovery ===

Not supported. See [[#VMware_Consolidated_Backup_.28VCB.29|VMware Consolidated Backup]] for what is supported.

=== VMware Snapshots ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

Used to preserve the state of a VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique. See also VMware Data Recovery and Copy Virtual Machine.

=== VMware Fault Tolerance ===

Not supported. See [[#VMware_High_Availability_.28HA.29|VMware High Availability]] for what is supported. Another alternative is manual Virtual Machine shutdown and migration.

=== VMware vCenter Converter ===

P2V tools are not supported. To migrate from bare-metal servers (e.g. Cisco 7800 Series Media Convergence Server) to UC on UCS, the supported procedure is:

:*upgrade to 8.x software version on the bare-metal server
:*take a software backup
:*fresh install 8.x software on VMware / UC on UCS
:*restore from backup

=== VMsafe ===

Not supported. See the documentation for the UC application software or UC appliance software to see what is supported.

=== VMware vShield ===

Not supported. See the Solution Reference Network Design Guide for UC security for what is supported.

=== Virtual Appliance Packaging of UC apps ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party VM-based Backup Tools ===

Not supported. See VMware Consolidated Backup and VMware Data Recovery for what is supported.

=== 3rd-Party VM-based Deployment Tools ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party Physical To Virtual (P2V) Migration Tools ===

Not supported. See VMware vCenter Converter for what is supported.

=== VMware Boot from SAN ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

VMware ESXi 4.1 is required for this feature. Even it works with 4.0, VMware's official support is only for 4.1 and later. Requires use of a "diskless" server - see Supported Hardware for tested reference configurations. Both VMware ESXi and UC apps are installed on, and boot from, the fibre channel SAN. See UCS page at www.cisco.com/go/swonly for storage support policy.

== Services and Support Contracts for VMware are Required ==

Customers deploying virtualized UC must have a valid support contract for the VMware software in order to be supported by Cisco.

Customers purchasing VMware software licenses from Cisco must also purchase a subscription services part number from Cisco (for part number examples, see the UC on UCS page at www.cisco.com/go/swonly).

Customers purchasing VMware software from a 3rd-party must purchase subscription services from that 3rd-party or from VMware.

Customers should note that for VMware vSphere Hypervisor (formerly called “ESXi Single Server Edition” or “free ESXi”), VMware does not offer the same services options and terms as they do for their Standard, Advanced, Enterprise or Enterprise Plus Editions. Customers should take this into account when planning and pricing their support strategy.

Cisco Field and Channel Partners may consult the User Connect Licensing Ordering Guide for more information.

== Cisco TAC Support Expectations ==

The following table describes how TAC support works for VMware in a UC on UCS context, based on who VMware was purchased from.

Special case: when Cisco as a VMware reseller sells VMware Enterprise License Agreements, it is treated as a VMware direct sale for TAC support purposes based on how the maintenance contracts are structured.

 

{| border="1"
|-
! 
! Buy from Cisco as Collaboration SKU
! Buy from Cisco as Data Center SKU
! Buy from 3rd-party, or enterprise/site license
|-
! Available VMware ESXi Editions
| Standard
| Advanced, Enterprise or Enterprise Plus
| Standard, Advanced, Enterprise, Enterprise Plus or vSphere Hypervisor (formerly "Single Server Edition" or "free ESXi"
|-
! Mandatory Support Contracts
| ISV1 from Cisco as Collaboration Service SKU
| ISV1 from Cisco as Data Center Service SKU
| "SnS" subscription from VMware
|-
! Who takes first call?
| Cisco
| Cisco
| VMware
|}

'''TAC Responsibility:''' Note that multi-vendor triage is the norm in virtualized deployments, where the storage, server, hypervisor, OS and application are potentially all from different vendors. Cisco Voice TAC responsibility is the UC application, demarcated at the Virtual Machine. Cisco Server Virtualization TAC responsibility is for VMware (via triage), Cisco UCS, Cisco storage access (or triage with customer and their vendor) and storage array (via triage with customer and their vendor). Escalation to VMware, the customer, or the customer's storage vendors will be done as needed for solution components not produced by Cisco.

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications VMware Requirements

2011-12-04T14:55:21Z

Sdurvasu: /* Virtual Machine Templates (OVA files) */

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

This article describes VMware requirements, feature support, and services and support contracts for virtualized Unified Communications applications.

== Introduction: Mandatory VMware Products and Services ==

'''Note:''' This page only covers VMware product/version/feature support.

:*It does '''not''' cover compute/network/storage hardware support policy for UC virtualization.
:*It does '''not''' cover application co-residency support policy for UC virtualizatoin.
:*See other links at http://www.cisco.com/go/uc-virtualized for these details.

 

'''VMware vSphere ESXi is mandatory''' for UC virtualization and UC on UCS.

:*UC is only supported on UCS servers with VMware vSphere ESXi.
:*See rest of this page for other details on VMware product, version and feature support.
:*'''Nonvirtualized, physical, or bare-metal installations are not supported''' for UC on UCS.

 

'''VMware vCenter''' is:

:*'''Mandatory''' for all Specs-based deployments
:*'''Optional''' for Tested Reference Configuration deployments.

 

For UC on UCS, VMware vSphere ESXi and vCenter may be purchased from Cisco or customer provided. For specs-based with HP/IBM, all VMware software must be customer-provided. See [[Before You Buy or Deploy - Considerations for Design and Procurement]] for information on VMware purchase options. 

Compatibility of UC apps/versions with VMware vSphere ESXi versions varies by UC app and is outlined later in this document. See the following links for details on "legacy" virtualization support (i.e. 7.x of UC apps with VMware vSphere on limited 3rd-party servers):

:*[http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html Cisco Unity Virtualization Design Guide]
:*[http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_7_5/user/guide/VirtualizationGde753.pdf Virtualization Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted 7.5(3)]

 

'''Note:''' in all cases, the customer is required to have a valid service contract (either with Cisco or with VMware, depending on what/how purchased) to be supported. See [[#Services_and_Support_Contracts_for_VMware_are_Required|Services and Support Contracts for VMware are Required]] for how to ensure this is done for different Editions of Vmware vSphere ESXi. 

== Supported Virtualization Hypervisor Vendors ==

At this time, the only vendor supported for UC is VMware.

Other vendors/products - such as Microsoft Hyper-V, Citrix Xen, Red Hat KVM - are not supported for Cisco UC virtualization. 

== Supported VMware Products ==

VMware vSphere ESXi is required for Cisco UC virtualization.

*ESX and ESXi are architecture options for VMware vSphere ([http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html click here for a comparison]). UC only supports ESXi. Recall that vSphere 3.x and 4.x offered both options, but 5.0+ only offers ESXi.
*VMware vSphere ESX, regardless of version, is not supported for UC. This is due to technical reasons and [http://blogs.vmware.com/vsphere/2010/07/esx-41-is-the-last-esx-what-do-i-do-now.html VMware’s direction to transition from ESX to ESXi]. Note a VMware ESX cluster can contain VMware ESXi servers running Cisco Unified Communications.
*No other VMware server virtualization products are supported.

 

== Supported Versions of VMware vSphere ESXi ==

The minimum version for VMware vSphere ESXi is 4.0. But note a higher minimum version may be required depending on what UC apps/versions you run (see tables below) and what hardware you select.

*Note that use of VMware vSphere ESXi 4.1 requires [[Disable LRO|'''disabling the "LRO" setting as described here''']].
*Versions of VMware vSphere ESXi prior to 4.0 are not supported due to technical reasons.
*Each UC app/version will specify the required compatible Major Releases and Minor Releases of VMware vSphere ESXi (e.g. 4.0 or 4.1) in the tables below.
**Unlisted Major/Minor versions are not supported.
**Unless otherwise indicated, the base Major/Minor version shown is the minimum required.
**Some UC apps will also require a minimum Maintenance Release and will indicate if this is the case. Otherwise UC does not specify or recommend patches, updates or Maintenance Releases (e.g. 4.0 U1) for a required Major/Minor Release of vSphere ESXi. Follow recommendations of the server vendor and VMware for what you should use. Unless otherwise indicated by a UC app, UC supports all VMware vSphere ESXi patches, updates and Maintenance Releases for a supported Major/Minor Release at time of VMware launch as long as the server vendor supports them.

 

=== VMware vSphere ESXi Version Support for Call Processing and System Management Applications ===

{| class="wikitable FCK__ShowTableBorders"
|-
!
Application 

! VMware vSphere ESXi 4.0 
! VMware vSphere ESXi 4.1 
! VMware vSphere ESXi 5.0 
|-
| Unified Communications Manager (Unified CM)
| 8.0(2)+, 8.5+, 8.6+
| 8.0(2)+, 8.5+, 8.6+
| Not supported
|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Cisco Emergency Responder (CER)
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Session Manager Edition (SME)
| 8.5+, 8.6+
| 8.5+, 8.6+
| Not supported
|-
| Unified Attendant Consoles
| 8.0(3)+, 8.5+
| 8.6+
| Not supported
|-
| UC Management Suite (OM, SM, SSM, PM)
| 7.1 and later
| 7.1 and later
| Not supported
|-
| Cisco Intercompany Media Engine (CIME)
| Not supported
| 8.6(2)+
| Not supported
|}

=== VMware vSphere ESXi Version Support for Messaging and Presence Applications ===

{| style="width: 812px; height: 108px" class="wikitable FCK__ShowTableBorders"
|-
! Application 
! VMware vSphere ESXi 4.0 or 4.0 Update 1 
! VMware vSphere ESXi 4.1
|-
| Cisco Unity Connection
| 8.0(2) and later
| 8.0(3) and later
|-
| Cisco Unity
| 7.x and later
| 7.x and later
|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
| 8.0(2) and later
| 8.0(2) and later
|}

 

=== VMware vSphere ESXi Version Support for Contact Center Applications ===

{{Note| For Virtual Machines that need '''more than 4 vCPUs''', the VMware vSphere ESXi '''Enterprise Plus''' licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)}}

{| style="width: 816px; height: 396px" class="wikitable FCK__ShowTableBorders"
|-
! Application
! VMware vSphere ESXi 4.0 and 4.0 Updates
! VMware vSphere ESXi 4.1  and 4.1 Updates
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]]
| 8.0(2) and later or 8.5(1) and later
| 8.0(2) SU2 and later or 8.5(1) and later
|-
| [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Work Force Optimization (WFO), Quality Management (QM),and Work Force Management (WFM)]
| 8.5(1) and later
| 8.5(2) and later
|-
| [[Unified Contact Center Enterprise]] 
| ESXi 4.0 Update 1 (minimum required). See below
| See below
|-
| - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tools
| 8.0(2) and later or 8.5(1) and later
| 8.0(2) and later or 8.5(1) and later
|-
| [[Virtualization for Unified Intelligence Center|Cisco Unified Intelligence Center]] 
| 8.0(3) and later
| 8.5(2) and later
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]
| 8.0(2) and later or 8.5(1) and later
| 8.0(2) and later or 8.5(1) and later
|-
| [[Unified Customer Voice Portal]] (all components) 
| 8.0(1) and later or 8.5(1) and later
| 8.0(1) and later or 8.5(1) and later
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| 8.5(1) and later
| 8.5(2) and later
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| 8.5(1) and later
| 8.5(1) and later
|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Unified Email Interaction Manager and Web Interaction Manager]]
| 4.3(2) and later
| 4.3(2) and later
|}

== Support of Cisco VN-Link and Cisco Nexus 1000V ==

Note that Cisco Unified Contact Center Enterprise does NOT support this – see [[UCS Network Configuration for UCCE|UCS Network Configuration for Unified CCE]].

Unless otherwise indicated above, Cisco VN-Link and Cisco Nexus 1000V are supported by UC applications that support the VMware vNetwork Distributed Switch (see [[#Supported_Editions_and_Features_of_VMware_vSphere_ESXi.2C_VMware_vCenter_and_VMware_vSphere_Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]).

Cisco VN-Link, Cisco Nexus® 1000V and VMware vNetwork Distributed Switch all require VMware ESXi Enterprise Plus Edition (see [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]). Other editions do not support these capabilities.

For UC on UCS B-series, Cisco UCS 6100 does not currently support Layer 3 to Layer 2 COS markings. Additionally, the UC applications and operating systems cannot set the Layer 2 COS markings. Use of Cisco Nexus® 1000V is therefore strongly recommended as this is the only way to manage traffic congestion through the current UCS 6100. Please recall that traffic congestion risk will vary and is dependent on many factors such as UC vs. non-UC virtual machine count and their traffic characteristics across all blades, chassis and fabric extenders connected to the same UCS 6100.

For UC on UCS C-series, Cisco Nexus® 1000V is recommended but not mandatory as there is no intermediate UCS 6100 to design around.

 For more information on Cisco VN-Link and Cisco Nexus 1000V, see http://www.cisco.com/en/US/netsol/ns894/index.html and http://www.cisco.com/en/US/products/ps9902/index.html.

== Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client ==

 '''VMware vSphere Client''' (formerly branded VI Client) and '''VMware vCenter''' are management consoles for VMware vSphere hosts.

:*vSphere Client is free but only has basic management capabilities.
:*vCenter is not free as it has advanced management capabilities, but note UC may not support every feature in vCenter. vCenter is mandatory for any specs-based deployment.

 

'''VMware vSphere ESXi''' is sold in several '''Editions''' with different levels of feature support.

:*[https://www.vmware.com/products/vsphere/buy/editions_comparison.html Click here for a comparison of VMware vSphere ESXi feature Editions on vmware.com].
::*[http://blogs.vmware.com/vsphere/2010/07/introducing-vmware-sphere-hypervisor-41-the-free-edition-of-vmware-vsphere-41.html Click here for a clarification of “free ESXi 4.1” vs. “vSphere ESXi 4.1 Hypervisor Edition”] (formerly branded as "VMware ESXi Single Server Edition" or “free ESXi”).
::*For details on supported features for 4.x versions of other vSphere ESXi Editions, see your VMware account team. VMware on their web site [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010579 provides a "best effort" comparison here].
:*If buying VMware vSphere ESXi direct from VMware:
::*[http://www.vmware.com/products/vsphere/purchase-advisor/index.html Click here for VMware's Purchase Advisor for vSphere on vmware.com].
::*[https://www.vmware.com/files/pdf/vsphere_pricing.pdf Click here for an overview of VMware vSphere ESXi pricing on vmware.com].

 

There are no UC-specific restrictions on what VMware vSphere ESXi feature Edition you "can" use, but the Edition you "should" use will be determined by VMware licensing rules based on aspects of the UC deployment. The customer is responsible for selecting the correct VMware vSphere ESXi Edition based on their feature and UC application requirements. The following non-exhaustive list is provided for convenience only as examples of what must be considered under VMware's current licensing rules, which are subject to change:

:*If you want to use Cisco Nexus 1000V with UC, that requires the VMware vSphere ESXi feature "Distributed Switch" which is only available in Enterprise Plus Edition.
:*If you want to use a UC virtual machine OVA template with a large quantity of vCPU, verify the VMware vSphere ESXi Edition supports sufficient "vCPU Entitlement" for that OVA's vCPU count.
::*E.g. the Unity Connection 20K user OVA that requires 7 vCPU per VM.
:*Verify all the UC-supported VMware vSphere ESXi features you want to use are [https://www.vmware.com/products/vsphere/buy/editions_comparison.html supported by the Edition you pick].
:*The "Cisco UC Virtualization Hypervisor" is only supported for use with Business Edition 6000 and has the following restrictions:
::*It is not available or transferable for use with any other hardware or software.
::*Server Hardware restricted to UCS C200 M2 TRC#1
::*Max total vRAM across all VMs is 16 GB (of which 14 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Does not support VMware vCenter management. Does not offer any [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features like other Editions].
:*The "Cisco UC Virtualization Foundation" is only supported for use with Business Edition 6000 and UC on UCS.
::*Not available direct from VMware, only sold as part of BE6K or UC on UCS. It is not available or transferable for use with non-UCS hardware or non-UC software.
::*Server Hardware restricted to 2-socket UCS B-Series models and 2-socket UCS C-Series models.
::*Max total vRAM across all VMs is 32 GB (of which 30 GB are available to UC apps)
::*Max vCPU per VM is 8
::*Supports VMware vCenter management (purchased separately). UC-supported [https://www.vmware.com/products/vsphere/buy/editions_comparison.html advanced operational features] limited to vStorage APIs. All other UC-supported features (including but not limited to VMware High Availability, Data Recovery, vMotion, Distributed Switch, etc.) are not offered.

 

Finally, note that UC may not support all of the features that are included in the VMware vSphere ESXi Edition you pick. This may be because the feature is N/A for a UC deployment, or it has not been sufficiently tested before UC will support, or it requires application enhancements before UC can support.

The table below lists VMware feature support by UC app/version. If the feature is supported, click on its name in the table to view UC caveats and best practices. Feature support may vary by UC app. This site will be updated as new support becomes available.

{{note| feature support for Cisco Unified Contact Center Enterprise varies by component (e.g. Peripheral Gateway) and deployment model (e.g. "Rogger") - this section will give a summary support position, but for individual components see [[Unified Contact Center Enterprise|Support for Virtualization on the ESXi/UCS Platform]].}} 

=== Legend for Feature Support Tables ===

:*Y(C) = Supported with '''C'''aveats - see [[#Best_Practices|Best Practices]] for details
:*Y(P) = '''P'''artial (limited) support only - see [[#Best_Practices|Best Practices]] for details
:*No = the feature is not supported at this time - see [[#Best_Practices|Best Practices]] for alternatives, if any.

=== VMware Feature Support for Call Processing and System Management 8.0(2) through 8.6(1) ===

{| border="1"
|+ ''' '''
|-
! Feature
! Unified CM
! CER
! SME
! Unified Attendant Consoles
! UPM
! UOM, USM, USSM
! CIME 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C)
| Y(C) 
| Y(C) 
| Y(C) 
| Yes
| Y(C) 
| Y(C) 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C)
| Y(C)
|  Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(P)
| Y(P)
| No 
| No 
| Y(P)
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No 
| No 
| No
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)  
| Y(P)  
| Y(P)  
| Y(P)  
| Yes
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C)
| No
| Y(C)
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| Y(C) 
| Y(C)
| Y(C)
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C) 
| Y(C) 
| Y(C) 
| No
| Y(C)
| No 
| Y(C)
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(C)
| Y(C) 
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C) 
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| Yes
| No 
| No
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| Y(C)
| No 
| No
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No 
| No
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| Y(C)
| No 
| Y(C)
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No 
| No
|- style="background: rgb(229,228,226)"
! vSphere ESXi 5.0 Features
| 
| 
| 
| 
| 
| 
| 
|- align="center"
! All vSphere ESXi 5.0 Features
| No
| No
| No
| No
| No
| No 
| No
|}

=== VMware Feature Support for Messaging and Presence 8.0(2) through 8.6(1) ===

{| border="1"
|+ '
|-
! Feature
! Unity Connection
! Unity
! Unified Presence
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(PP
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| Y(C)
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| Y(C) 
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(P)
| No
| Y(P)
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| Y(C) 
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
|- align="center"
! [[#Identity|Identity]]
| No  
| No  
| Y(C) 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| 
|}

 

=== VMware Feature Support for Contact Center 8.0(2) through 8.6(1) ===

{| style="width: 906px; height: 823px" border="1"
|+  
|-
! Feature
! Unified CCX
! Cisco WFO, QM, and WFM
! Unified CCE, CVP
! Unified IC
! Cisco MediaSense
! SocialMiner
! Unfied EIM-WIM
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
|
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C) 
| No
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C)
| Y(C) 
| No
| Y(C) 
| No
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P) 
| No
| Y(P) 
| No
| No
| No
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P) 
| Y(P) 
| Y(P) 
| Y(P) 
| No
| No
| No
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| No
| Y(C) 
| Y(C)
| No
| No
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(P) 
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C)
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Backup_Tools|3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
|
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C) 
| Y(C)
| Y(C)
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No
| No
| No
| 
|}

== Best Practices ==

=== Virtual Machine Templates (OVA files) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

See www.dmtf.org for details on the Open Virtualization Format, which describes an OVF Package (a directory of files describing a virtual machine's configuration) and an OVA Package (single tar file containing an OVF Package).

“Template” in this context refers to an OVA file that defines the virtual server (but not the “workload”, i.e. the UC OS and application). Each virtualized UC product provides a set of predefined virtual machine templates (as OVA files) for supported Virtual Machine (VM) configurations. Customers must download and use these OVA template files for initial install, as they cover items such as supported capacity levels and any required OS/VM/SAN “alignment”. OVAs configured differently than the predefined templates are not supported at this time. To download the OVA files, refer to the [[Unified Communications Virtualization Sizing Guidelines|Unified Communications Virtualization sizing guidelines]].

=== Copy Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Copying a Virtual Machine (VM) copies both the virtual server configuration and the workload (UC OS and application) running on that virtual server to a file on networked shared storage. This allows VMs to be copied, then subsequently modified or shut down. This feature effectively provides a method to do full system backup/restore, take system images or revert changes to software versions, user data and configuration changes.

:*Prior to copying, the VM must first be shutdown (which will shut down the virtual server, the UC OS and the UC application).
:*If uploading a VM copy as a “whole system restore”, clustered UC applications such as CUCM will probably require their replication to be manually “fixed” via a CLI command.

=== Restart Virtual Machine on Different ESXi Host ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

A Virtual Machine (VM) file on network/shared storage can be booted on any physical server hosting ESXi that has access to that network shared storage. With multiple physical ESXi hosts connected to the same network shared storage, this can be used to perform:

:*Fast manual server moves, e.g. moving VM from ESXi host A to ESXi host B in another chassis, closet, building, etc.
:*Fast manual server recovery, e.g. moving VM from ESXi host A that has just had a server hardware or VMware failure to ESXi host B that is healthy. See also VMware High Availability and Site Recovery Manager.
:*Setting up software at a staging location to be later moved or deployed elsewhere. For multi-site scenarios, this may instead require “exporting” the VM.

=== Resize Virtual Machine ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Similar to adding/removing physical hardware to/from a physical server, you can add/remove virtual hardware (vCPU, vRAM, vDisk, vNIC, etc.) to/from a Virtual Machine (VM) via a software change in VMware’s configuration interfaces. Where supported, this provides the VM equivalent of migration to a more powerful or less powerful server.

:*Any changes to a VM must align with the best practices in [[#Virtual_Machine_Templates_.28OVA_files.29|Virtual Machine Templates (OVA files)]]. VM changes that result in an unsupported OVA configuration are not allowed. Even if you align with supported OVA configurations, desired VM changes may be prevented by one of the other caveats below.
:*Support for adding virtual hardware resources (similar to moving from a less powerful server to a more powerful server, such as MCS 7825 ⇒ MCS 7845) depends on which resource, and which UC product:
::*Adding vCPU is supported for all apps except Unity and Unity Connection, but requires VM to be shutdown first.
::*Adding vRAM is supported but requires VM to be shutdown first.
::*Adding vDisk is not supported as it would require re-partitioning by the application.
:*Adding vNIC is not supported unless the UC app supports multiple network connections with different IP addresses. See best practices for [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]].
:*For all other changes, it is recommended to backup the application, reinstall application on a new OVA file, and restore the application.
:*Removing virtual hardware resources (vCPU, vRAM, vDisk, etc.) is not supported (similar to moving from a more powerful server to a less powerful server, such as MCS 7845 ⇒ MCS 7825). These migrations require backing up the application, reinstalling on a new OVA file, and and restoring the application.
:*Live runtime resizing via the VMware Hot Add feature is not supported.

=== VMware Hot Add ===

Not supported. See [[#Resize_Virtual_Machine|Resize Virtual Machine instead]].

=== Multiple Physical NICs and vNICs ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). Network traffic is switched from physical NICs to “vNIC’s” of the Virtual Machines (VM) via either VMware vSwitch or Cisco Nexus 1000V. Customers can use these multiple NICs for VM network traffic, VMware console access, or management “back-doors” for administrative access, backups, software updates or other traffic that is desired to be segregated from the VM network traffic. All these uses are supported for UC but note that UC apps like CUCM only support a single vNIC with a single IP address.

=== VMware High Availability (HA) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature automatically restarts a Virtual Machine (VM) on the same physical server or a different physical server. It can be used to supplement software redundancy as a means of fast, automated Failed-server recovery when a VM (but not the application) is hung or if there is a fault with the physical host server or VMware software.

:*Failovers to other servers must not result in an unsupported deployment model (e.g. destination server must align with supported co-residency after failover occurs).
:*Does not protect vs. faults with the SAN or network hardware.

=== VMware Site Recovery Manager (SRM) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This feature provides an automated disaster recovery solution that works on a “site to site” basis, where a “site” comprises physical servers, VMware and SAN storage. Refer to the VMware documentation for requirements to use this feature. There are no special requirements to use this feature with UC apps that support it.

=== VMware Identity ===

The VMware identity feature allows you to copy an existing instance of a virtual Cisco Unified Presence, and change its identity. The identity of a system is made up of every setting that you usually configure during a fresh install (such as IP address, hostname, passwords).

You can then use this new identity for another instance of a Cisco Unified Presence on a virtual machine. This avoids you having to perform a complete installation each time you deploy a new Cisco Unified Presence.

=== VMware vNetwork Distributed Switch ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

Supporting apps in UC on UCS may either use this feature, or the Cisco VN-Link technology (such as Cisco Nexus 1000V).

 

=== VMware vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Cl]]ient.

This feature migrates a live, running Virtual Machine (VM) from one physical server to another.

The following applies to any use of vMotion with UC apps:

:*VM must be installed on shared storage (SAN).
:*Source and destination physical servers must be connected to same SAN.
:*Destination physical server must not end up with over-subscribed hardware after the migration. Supported capacity and co-residency rules for UC must be followed before and after the migration.
:*VMware “Long Distance vMotion” (site to site) is not supported.
:*The only supported scenario is a manual move to a different server, e.g. for planned maintenance on the server or VMware software, or during troubleshooting to move software off of a physical server having issues.
:*Use of vMotion for real-time load-balancing of live UC VMs is not supported, whether alone or in conjunction with VMware Dynamic Resource Scheduler (DRS) or Dynamic Power Management (DPM).
:*Moving a shut down VM during a maintenance window, i.e. a "cold migration" or "host to host migration", is not vMotion and is supported.

If the UC app is listed as "Supported with Caveats", then support is as described below:

:*Migration of UC VMs that are live and processing live traffic is supported, but note that Cisco testing cannot cover every possible operational scenario. Testing has shown there is a slight risk of calls in progress being impacted for a few seconds as the migration occurs, with worst case result of the affected calls being dropped. If vMotion is suspected as the cause of dropped calls, customers should gather appropriate application logs as well as performance data from VMware vCenter and send to Cisco TAC for analysis.

If the UC app is listed as "Partial" support, then support is “maintenance mode only” as described below:

:*"Maintenance mode only" - VMware vMotion by definition operates on live VMs, but the VM running the UC app must be “live but quiescent”. I.e. in a maintenance window, not in production, not processing live traffic. This is because during the vMotion cutover, the system is paused, which for real-time UC apps creates service interruption which degrade voice quality after the migration for calls in progress.

 

=== VMware Dynamic Resource Scheduler ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== VMware Dynamic Power Management ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported.

=== Long Distance vMotion ===

Not supported. See [[#VMware_vMotion|vMotion]] for what is supported. Long Distance vMotion is a joint Cisco and VMware validated architecture for using the vMotion feature across data centers. For more information, see http://blogs.cisco.com/datacenter/comments/cisco_and_vmware_validated_architecture_for_long_distance_vmotion/ and http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns836/white_paper_c11-557822.pdf.

=== Storage vMotion ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

This “customer convenience” feature provides easy migration of a live system from one SAN to another SAN. For UC apps, an easier suggested alternative is to just perform manual VM shutdown and migration to the new SAN. However, if Storage vMotion must be used, it is only under the following conditions:

:*Requires SAN storage.
:*May only be done during a maintenance window with UC VMs shut down.

=== VMware vCenter Update Manager (VUM) ===

NOTE: Support varies by application and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature automates patching and updating of VMware vSphere hosts. Note that Cisco Unified Communications applications upgrades, patches and updates can not be delivered through vCenter Update Manager.

=== VMware Consolidated Backup (VCB) ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature provides integration with 3rd-party backup utilities so that they can non-disruptively backup the OS and application in a Virtual Machine (VM). See also VMware Data Recovery and Copy Virtual Machine.

Existing UC app methods of backing up the software continue to be supported.

=== VMware Data Recovery ===

Not supported. See [[#VMware_Consolidated_Backup_.28VCB.29|VMware Consolidated Backup]] for what is supported.

=== VMware Snapshots ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

Used to preserve the state of a VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique. See also VMware Data Recovery and Copy Virtual Machine.

=== VMware Fault Tolerance ===

Not supported. See [[#VMware_High_Availability_.28HA.29|VMware High Availability]] for what is supported. Another alternative is manual Virtual Machine shutdown and migration.

=== VMware vCenter Converter ===

P2V tools are not supported. To migrate from bare-metal servers (e.g. Cisco 7800 Series Media Convergence Server) to UC on UCS, the supported procedure is:

:*upgrade to 8.x software version on the bare-metal server
:*take a software backup
:*fresh install 8.x software on VMware / UC on UCS
:*restore from backup

=== VMsafe ===

Not supported. See the documentation for the UC application software or UC appliance software to see what is supported.

=== VMware vShield ===

Not supported. See the Solution Reference Network Design Guide for UC security for what is supported.

=== Virtual Appliance Packaging of UC apps ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party VM-based Backup Tools ===

Not supported. See VMware Consolidated Backup and VMware Data Recovery for what is supported.

=== 3rd-Party VM-based Deployment Tools ===

Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party Physical To Virtual (P2V) Migration Tools ===

Not supported. See VMware vCenter Converter for what is supported.

=== VMware Boot from SAN ===

NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client|Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client]].

VMware ESXi 4.1 is required for this feature. Even it works with 4.0, VMware's official support is only for 4.1 and later. Requires use of a "diskless" server - see Supported Hardware for tested reference configurations. Both VMware ESXi and UC apps are installed on, and boot from, the fibre channel SAN. See UCS page at www.cisco.com/go/swonly for storage support policy.

== Services and Support Contracts for VMware are Required ==

Customers deploying virtualized UC must have a valid support contract for the VMware software in order to be supported by Cisco.

Customers purchasing VMware software licenses from Cisco must also purchase a subscription services part number from Cisco (for part number examples, see the UC on UCS page at www.cisco.com/go/swonly).

Customers purchasing VMware software from a 3rd-party must purchase subscription services from that 3rd-party or from VMware.

Customers should note that for VMware vSphere Hypervisor (formerly called “ESXi Single Server Edition” or “free ESXi”), VMware does not offer the same services options and terms as they do for their Standard, Advanced, Enterprise or Enterprise Plus Editions. Customers should take this into account when planning and pricing their support strategy.

Cisco Field and Channel Partners may consult the User Connect Licensing Ordering Guide for more information.

== Cisco TAC Support Expectations ==

The following table describes how TAC support works for VMware in a UC on UCS context, based on who VMware was purchased from.

Special case: when Cisco as a VMware reseller sells VMware Enterprise License Agreements, it is treated as a VMware direct sale for TAC support purposes based on how the maintenance contracts are structured.

 

{| border="1"
|-
! 
! Buy from Cisco as Collaboration SKU
! Buy from Cisco as Data Center SKU
! Buy from 3rd-party, or enterprise/site license
|-
! Available VMware ESXi Editions
| Standard
| Advanced, Enterprise or Enterprise Plus
| Standard, Advanced, Enterprise, Enterprise Plus or vSphere Hypervisor (formerly "Single Server Edition" or "free ESXi"
|-
! Mandatory Support Contracts
| ISV1 from Cisco as Collaboration Service SKU
| ISV1 from Cisco as Data Center Service SKU
| "SnS" subscription from VMware
|-
! Who takes first call?
| Cisco
| Cisco
| VMware
|}

'''TAC Responsibility:''' Note that multi-vendor triage is the norm in virtualized deployments, where the storage, server, hypervisor, OS and application are potentially all from different vendors. Cisco Voice TAC responsibility is the UC application, demarcated at the Virtual Machine. Cisco Server Virtualization TAC responsibility is for VMware (via triage), Cisco UCS, Cisco storage access (or triage with customer and their vendor) and storage array (via triage with customer and their vendor). Escalation to VMware, the customer, or the customer's storage vendors will be done as needed for solution components not produced by Cisco.

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Virtualization for Unified Email Interaction Manager - Web Interaction Manager

2011-12-01T23:38:51Z

Sdurvasu: 1 revision

== Updates to this Page ==

The following is a list of significant updates to this page:

 

{| class="wikitable FCK__ShowTableBorders"
|-
! Date
! Update
|-
| April 06 2011
| Initial version of virtualization information for Cisco Unified EIM-WIM
|}

 

== Information for Partners about Cisco Unified EIM-WIM Deployment Certification and Ordering ==

This page contains essential information for partners about the following:

*Partner Certification Requirements
*UCS Server Ordering Information
*Important Notes on Cisco UCS Service and Support

Please visit [[Unified Communications in a Virtualized Environment]] for more details

== Cisco Unified EIM-WIM , Release 4.3(2) Support for Virtualization on the ESXi/UCS Platform ==

Starting with Release 4.3(2), virtualization of Cisco Unified EIM-WIM on Cisco Unified Computing Systems(UCS)is supported B series models.To know about specific models please visit [[Unified Communications Virtualization Supported Applications]].

== UCS Hardware Requirements ==

Requirements for Cisco Unified EIM-WIM systems using UCS B200 M2 hardware are located at [[Unified Computing System Hardware]].

== VMware and Application Software Requirements ==

The following software requirements apply specifically to Cisco Unified EIM-WIM :

*EIM-WIM support ESX 4.0U1 and subsequent updates and ESXi 4.1.

== Configuring the ESXi Host Network for the Virtual Machines ==

To configure the network for VMs, you create a virtual switch connected to an Ethernet port on the server, and then associate the virtual machine's network adapter to this virtual switch. To Add a vSwitch

*Login to the ESXi host using VMware Infrastructure Client
*Select the ESXi host
*Click on the Configuration tab
*Click on Hardware/Networking
*Click on Add Networking...
*Select Connection Types: Virtual Machine. Click Next.
*Select "Create a virtual switch" and select an associated VM NIC.
*Enter Port Group Properties/Network label: VM Network n, where n is an integer.(Example: "VM Network 1")
*Click on Finish.

To Associate a VM Network Adapter to Network Connection

*Edit virtual machine settings.
*Select the Network Adapter.
*Select a virtual switch from the Network Connection/network label. (Example: "VM Network 1")
*Click OK.
*Click on Hardware/Networking
*Click on Add Networking...
*Select Connection Types: Virtual Machine. Click Next.
*Select "Create a virtual switch" and select an associated VM NIC.
*Enter Port Group Properties/Network label: VM Network n, where n is an integer.(Example: "VM Network 1")
*Click on Finish.

To Associate a VM Network Adapter to Network Connection

*Edit virtual machine settings.
*Select the Network Adapter.
*Select a virtual switch from the Network Connection/network label. (Example: "VM Network 1")
*Click OK.

 

 

== Installing Cisco Unified EIM-WIM components on Virtual Machines ==

Follow the steps and references below to install OR migrate the Cisco Unified EIM-WIM components on Virtual Machines.

*Install setup and configure the UCS Hardware
*Configure the UCS Network. Follow the link [[Unified Communications VMWare Requirements]].
*Install and Boot VMWare ESXi. Refer to the following installation guide: [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html|Cisco UCS B-Series Blade Servers VMware Installation Guide.]
*Create Cisco Unified EIM-WIM Virtual Machines from the OVA template. OVA templates are available on Cisco.com.

== Creating Virtual Machines from OVA VM Template ==

Please see  [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]] for more information.

 

== Downloading OVA Template ==

:*Proceed to the [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&flowid=5224&softwareid=283929858&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=latest Release 4.3(2) Cisco download page].

:*To download a OVA file, click the '''Download File''' button next to that file. click the '''Add to Cart''' button next to file, then click on the '''Download Cart''' link. A Download Cart page appears.

:*Click the '''Proceed with Download''' button on this page. A Software License Agreement page appears.

:*Read the Software License Agreement, then click the '''Agree''' button

:*On the next page, click on either the '''Download Manager''' link (requires Java) or the '''Non Java Download Option''' link. A new browser window appears.

:*If you selected Download Manager, a Select Location dialog box appears. Specify the location where you want to save the file, and click '''Open''' to save the file to your local machine.

:*If you selected Non Java Download Option, click the '''Download''' link on the new browser window. Specify the location and save the file to your local machine.

== Creating Virtual Machines by Deploying the OVA Templates ==

In the vSphere client, perform the following steps to deploy the Virtual machines.

*Highlight the host or cluster to which you wish the VM to be deployed.
*Select File > Deploy OVF Template.
*Click the Deploy from File radio button and specify the name and location of the file you downloaded in the previous section OR click the Deploy from URL radio button and specify the complete URL in the field, then click Next.
*Verify the details of the template, and click Next.
*Give the VM you are about to create a name, and choose an inventory location on your host, then click Next.
*Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click Next.
*Choose a virtual network for the VM, then click Next.
*Verify the deployment settings, then click Finish.

Note:

*VM CPU affinity is not supported. You don't need to set CPU affinity for the VMs that are running Cisco Unified EIM-WIM applications on the VMware ESXi on UCS platform.
*VM resource Reservation - VM resource reservation is not supported for the VMs that are running Cisco Unified EIM-WIM applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations.
*You cannot change the computing resource configuration of your VM at any time.
*You can never go below the minimum VM computing resource requirements as defined in the OVA templates.
*ESXi Server hyperthread is enabled by default.

 

== Cisco Unified EIM-WIM Component Capacities and VM Configuration Requirements ==

This table shows the supported Cisco Unified EIM-WIM components, their capacities, and the VM computing resource requirements. You must use the OVA virtual machine templates to create the Cisco Unified EIM-WIM component VMs.

Note: For Virtual Machines that need more than 4 vCPUs, the VMware vSphere ESXi Enterprise Plus licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)

For different sizing configuration , please refer to [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]] 

== Cisco Unified EIM-WIM Component Co-Residency ==

You can have one or more EIM-WIM components co-resident on the same ESXi server. However, you must follow the rules described below:

1)EIM/WIM Virtual Machines with the exception of DB server Virtual Machine can co-reside with any other UC application Virtual Machine as long as there is no oversubscription of CPU and Memory. DB Server Virtual Machine can co-reside with UC applications Virtual Machines which are not DB server themselves

2)Co-Residency of EIM-WIM components with third party application is not supported

3)You can have any number of EIM-WIM virtual machines on an ESXi server as long as the sum of all the virtual machine CPU and memory resource allocation is not over committed on the available ESXi server computing resources.

4) You must not have CPU overcommitted on the ESXi server that is running EIM-WIM components . The total number of vCPUs among all the virtual machines on an ESXi host must not greater than the total number of CPUs available on the ESXi server. In the case of the Cisco UCS B-200 M1, the total number of CPUs available is 8.

5)You must not have memory overcommitted on the ESXi host that is running UC realtime applications. You must allocate minimum 2GB of memory for the ESXi kernel. For example, if an ESXi server on B-200 M1 hardware has 36GB of memory, after you allocate 2GB for the ESXi kernel, you have 34GB available for the virtual machines. The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34GB in this case.

== Performance Requirements ==

CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM. Memory usage (average) should not exceed 80%x for the ESXi Server and for each of the VMs. VM snapshots are not supported in production since they have significant impact on system performance.

 The data is collected from the test run of 200 users working on Email, 200 users working on Chat and 200 more working on Blended Collaboration activities (Total of 600 agents). Email activities were processing at 12 per hour per agent and Chat and Blended Collaboration activities were processed at the rate of 10 per hour per agent. 

{| class="wikitable FCK__ShowTableBorders"
|-
! rowspan="2" | EIM-WIM Components
! colspan="3" | IOPS
! colspan="3" | Disk Read KBytes / sec
! colspan="3" | Disk Write KBytes / sec
|-
| '''Peak'''
| '''95th Pct.'''
| '''Avg.'''
| '''Peak'''
| '''95th Pct.'''
| '''Avg.'''
| '''Peak'''
| '''95th Pct.'''
| '''Avg.'''
 

|-
| Application Server
| 11.7
| 3.21
| 1.55
| 51
| 1
| 0.726
| 103
| 19
| 8.32
|-
| File Server
| 43.65
| 25.23
| 14.36
| 189
| 2
| 2
| 1769
| 1025.9
| 446
|-
| Database Server
| 736.9
| 552
| 263.31
| 35450
| 23184
| 3903
| 5737
| 2872
| 1625
|-
| Messaging Server
| 9.15
| 2.71
| 1.47
| 57
| 1
| 0.7
| 88
| 15.1
| 8
|-
| Services Server
| 11.15
| 3.155
| 1.53
| 55
| 1
| 0.73
| 1.89
| 17
| 9
|-
| Web Server
| 11.2
| 3.36
| 1.43
| 55
| 1
| 0.8
| 173
| 21
| 10.24
|}

== Installing VMware Tools ==

The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806 VMware documentation] for instructions on installing or upgrading VMware Tools on the VM with Windows operating system.

== Installing Cisco Unified EIM-WIM Components on Virtual Machines ==

You can install the Cisco Unified EIM-WIM components after the configuration of the VMs. Installation of these Cisco Unified EIM-WIM components on a VM is the same as the installation of these components on physical hardware. Refer to the Cisco Unified EIM-WIM Install Guide for the steps to install Cisco Unified EIM-WIM components.

== Migrating ==

Migration of EIM-WIM components from existing physical boxes to VMs is not supported.Also we do not support EIM-WIM deployments which are mix of physical hardware and VMs

== Unified EIM-WIM, Release 4.3(2) Support for Virtualization on the ESXi/UCS Platform ==

*Unified EIM-WIM is qualified with ESXi4.0 and ESXi 4.1.Note that once the VM is upgraded to ESXi 4.1 , VMWare tools need to upgraded as well in all VMs. For more information on upgrading refer to [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806 VMware documentation]