'''What is an OVA?'''&nbsp; 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".

<br>'''Do Cisco&nbsp;UC&nbsp;VMs require these OVAs?&nbsp;''' To be TAC-supported, Virtual Machines for Cisco Unified Communications applications '''must''' use one of the provided OVA templates on this page.

+

-

+

-

*They represent what the UC apps have been tested with

+

-

*It is the only way to ensure UC apps are deployed on "aligned" disks for SAN deployments (i.e. pre-aligned filesystem disk partitions for the OVA's vDisks).&nbsp;

+

-

*OVA configurations are summarized in the tables below for convenience, but authoritative information is on OVA file's release notes on Download&nbsp;Software on www.cisco.com.

+

-

+

-

&nbsp;<br>

+

-

+

-

'''What does "users"&nbsp;mean in tables below?'''&nbsp;&nbsp; <span style="font-weight: bold">"U</span>'''sers"''' refers to the indicated user count at a particular BHCA, number of devices per user, device mix per&nbsp;VM, etc. using the [http://tools.cisco.com/cucst/faces/login.jsp Cisco Unified Communications Sizing Tool] and the [http://www.cisco.com/go/ucsrnd design guides] . Actual user capacity and total supported devices will be design-dependent; please follow all rules in the design guides and sizing tools for what your application can actually support.

+

-

+

-

<br>'''Where do I&nbsp;download these OVAs from?'''&nbsp; See [[Downloading OVA Templates for UC Applications]] for more information on how to download OVA templates for UC Applications.

* "One vCPU to one physical core" applies for all supported CPU architectures with equivalent performance for UC ([[Unified Communications Virtualization Sizing Guidelines | click here]] for details). E.g. one physical core on E5-2600 at 2.53+ GHz and one physical core on E7-2800 at 2.4+ GHz are equivalent for purposes of UC VM OVAs, sizing and co-residency planning.

+

-

* Each VM OVA is only for use on certain CPU architectures. See the notes column for which CPUs are allowed.

+

-

**E.g. the CUCM 1K user OVA is only for use on E5-2609/2.4 GHz (only found in UCS C220 M3S TRC#2) and E5506/2.13GHz (only found in UCS C220 M2 TRC#1).

+

-

** All other OVAs (such as CUCM 2.5K user, 7.5K user, or 10K user) are only for use on CPUs with minimum core speed of 2.53 GHz [[UC Virtualization Supported Hardware#Processors / CPUs | click here for details]], such as E5-2643/3.3 GHz or E5640 / 2.66 GHz.

+

-

}}

+

-

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.

| CUAC OVA Template contains settings for CPU, vRAM/Memory, vDisk and vNIC only. It does not contain the Operating System of the CUAC software[http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/data_sheet_c78-520987.html ]

*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

+

{{Note| The latest release of Cisco Unified Presence (CUP)is 8.6. These features are provided by Cisco Unified CM - IM and Presence in Release 9.0(1) and later.}}

-

:*36 text-to-speech ports

+

-

|-

+

<br>

-

! 15,000 users

+

-

| 4 (requires VMware CPU Affinity)

+

-

| 4 GB

+

-

|

+

-

4x 24 GB

+

-

:*vDisk 1 = Operating system

+

This content has moved to:

-

:*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

+

:*[[Virtualization for Unified CM IM and Presence]] - 9.x and later versions

-

|

+

:*[[Virtualization for Cisco Unified Presence]] - 8.x versions

-

*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

+

Please update your bookmarks.

-

:*36 text-to-speech ports

+

-

|}

+

<br> <br>

-

+

-

<br>

+

-

+

-

== Cisco Unified Presence ==

+

-

+

-

{{Note| Cisco Unified Presence is referred to as IM and Presence in Release 9.0(1) and later.}}

Notes: <br>(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. <br>(2) PM requires SAS or SCSI drives for deployments over 1K phones up to 10k phones (Disks must be aligned) <br>(3) PM requires FC SAS for deployments over 10K phones (Disks must be aligned)

Notes: <br>(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. <br>(2) PM requires SAS or SCSI drives for deployments over 1K phones up to 10k phones (Disks must be aligned) <br>(3) PM requires FC SAS for deployments over 10K phones (Disks must be aligned)

Notes: <br>(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. <br>(2) PM requires SAS or SCSI drives for deployments over 1K phones up to 10k phones (Disks must be aligned) <br>(3) PM requires FC SAS for deployments over 10K phones (Disks must be aligned)

If you are using third-party hardware for hosting the Cisco VCS VM application, check the hardware compatibility. This can be done using the VMware compatibility guide tool available from [http://www.vmware.com/resources/compatibility/search.php http://www.vmware.com/resources/compatibility/search.php].<br>

+

|-

|-

-

!

+

! Cisco TelePresence Conductor

-

Cisco TelePresence Video Communication Server, Release X7.2

+

| align="center" colspan="5" |

-

+

This content has moved to [[Virtualization for Cisco TelePresence Conductor]].

If you are using third-party hardware for hosting the Cisco VCS VM application, check the hardware compatibility. This can be done using the VMware compatibility guide tool available from [http://www.vmware.com/resources/compatibility/search.php http://www.vmware.com/resources/compatibility/search.php].<br>

If you are using third-party hardware for hosting the TelePresence Conductor VM application, check the hardware compatibility. This can be done using the VMware compatibility guide tool available from [http://www.vmware.com/resources/compatibility/search.php http://www.vmware.com/resources/compatibility/search.php].<br>

If you are using third-party hardware for hosting the TelePresence Conductor VM application, check the hardware compatibility. This can be done using the VMware compatibility guide tool available from [http://www.vmware.com/resources/compatibility/search.php http://www.vmware.com/resources/compatibility/search.php].<br>

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)