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.

+

== Unified Communications Manager ==

-

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.

+

This content has moved to [[Virtualization for Cisco Unified Communications Manager (CUCM)]].<br> Please update your bookmarks.

-

<br>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.

*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| Cisco Unified Presence is referred to as 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

+

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

-

:*vDisk 3 = Cisco Unity logs, SQL Server transaction logs

+

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

-

:*vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

+

-

| 1

+

Please update your bookmarks.

-

|

+

-

*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

+

-

+

-

|}

+

-

+

-

<br>

+

-

+

-

== Cisco Unified Presence (referred to as IM and Presence from 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)

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

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

-

<br>

+

<br>

{| border="1"

{| border="1"

Line 572:

Line 457:

! Application, OVA Capacity and Notes+Download Link

! Application, OVA Capacity and Notes+Download Link

! vCPU Cores

! vCPU Cores

+

! vCPU Speed

! vRAM / Memory

! vRAM / Memory

! vDisk

! vDisk

Line 582:

Line 468:

! CUPM up to 1K phones (VM-CUCMS_1S)

! CUPM up to 1K phones (VM-CUCMS_1S)

| 1

| 1

+

| 2.33Ghz

| 2 GB

| 2 GB

| 1x 30 GB

| 1x 30 GB

Line 591:

Line 478:

! CUPM 1K to 10K phones

! CUPM 1K to 10K phones

| 4

| 4

+

| 2.33Ghz

| 4 GB

| 4 GB

| 1x 40 GB (2)

| 1x 40 GB (2)

Line 600:

Line 488:

! CUPM 10K to 60K phones app server

! CUPM 10K to 60K phones app server

| 4

| 4

+

| 2.33Ghz

| 4 GB

| 4 GB

| 1x 30 GB(3)

| 1x 30 GB(3)

Line 609:

Line 498:

! CUPM 10K to 60K phones database server

! CUPM 10K to 60K phones database server

| 4

| 4

+

| 2.33Ghz

| 8 GB

| 8 GB

| 1x 120 GB(3)

| 1x 120 GB(3)

Line 618:

Line 508:

! CUOM/SM 1K phones

! CUOM/SM 1K phones

| 1

| 1

+

| 2.33Ghz

| 3 GB

| 3 GB

| 1x 50 GB

| 1x 50 GB

Line 627:

Line 518:

! CUOM 10K phones (VM-CUCMS_2L)

! CUOM 10K phones (VM-CUCMS_2L)

| 2

| 2

+

| 2.33Ghz

| 8 GB

| 8 GB

| 1x 72 GB

| 1x 72 GB

-

|

+

| 6

-

|

+

| 15

| 1

| 1

| <br>

| <br>

Line 636:

Line 528:

! CUOM 45K phones (VM-CUCMS_4L)

! CUOM 45K phones (VM-CUCMS_4L)

| 4

| 4

+

| 2.33Ghz

| 8 GB

| 8 GB

| 2x 60 GB

| 2x 60 GB

-

|

+

| 6

-

|

+

| 15

| 1

| 1

| <br>

| <br>

Line 645:

Line 538:

! CUSM 10K Phones (VM-CUCMS_2)

! CUSM 10K Phones (VM-CUCMS_2)

| 2

| 2

+

| 2.33Ghz

| 4 GB

| 4 GB

| 1x 72 GB

| 1x 72 GB

-

|

+

| 6

-

|

+

| 15

| 1

| 1

| <br>

| <br>

Line 654:

Line 548:

! CUSM 45K Server (VM-CUCMS_4)

! CUSM 45K Server (VM-CUCMS_4)

| 4

| 4

+

| 2.33Ghz

| 4 GB

| 4 GB

| 2x 60 GB

| 2x 60 GB

-

|

+

| 6

-

|

+

| 15

| 1

| 1

| <br>

| <br>

Line 663:

Line 558:

! CUSSM 10K phones (VM-CUCMS_1)

! CUSSM 10K phones (VM-CUCMS_1)

| 1

| 1

+

| 2.33Ghz

| 4 GB

| 4 GB

| 1x 60 GB

| 1x 60 GB

-

|

+

| 6

-

|

+

| 15

| 1

| 1

| <br>

| <br>

Line 672:

Line 568:

! CUSSM 45K Phones

! CUSSM 45K Phones

| 2

| 2

+

| 2.33Ghz

| 4 GB

| 4 GB

| 1x 72 GB

| 1x 72 GB

-

|

+

| 6

-

|

+

| 15

| 1

| 1

| <br>

| <br>

Line 681:

Line 578:

! CUCMS 10K phones Co-resident (VM_CUCMS_8)

! CUCMS 10K phones Co-resident (VM_CUCMS_8)

| 8

| 8

+

| 2.33Ghz

| 16 GB

| 16 GB

| 1x 320 GB (2)

| 1x 320 GB (2)

Line 691:

Line 589:

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)

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.

+

<br>

-

<br>

+

== Cisco Packaged Contact Center Enterprise ==

-

{| border="1" cellspacing="3" cellpadding="3"

+

Supported OVA templates are documented in the Install and Configuration Guide and in the Packaged CCE Specifications Guide. Both guides are on the Cisco documentation web page.

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

+

-

&nbsp;

+

-

|-

+

-

| '''Rogger 4000 agents'''

+

-

| 4

+

-

| 4

+

-

| 1x 80 for OS<br>1x 150 for DB

+

-

| 2

+

-

| The two vDisks can be in the same datastore

+

-

+

-

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

+

-

&nbsp;

+

-

|-

+

-

| '''Agent PG – CTIOS 2000 agents'''

+

-

| 2

+

-

| 4

+

-

| 1x 80

+

-

| 2

+

-

| &nbsp;

+

-

|-

+

-

| '''Agent PG – CAD 1000 agents'''

+

-

| 2

+

-

| 4

+

-

| 1x 80

+

-

| 2

+

-

| &nbsp;

+

-

|-

+

-

| '''Agent PG – CTIOS 450 agents'''

+

-

| 1

+

-

| 2

+

-

| 1x 80

+

-

| 2

+

-

| &nbsp;

+

-

|-

+

-

| '''Agent PG – CAD 297 agents'''

+

-

| 1

+

-

| 2

+

-

| 1x 80

+

-

| 2

+

-

| &nbsp;

+

-

|-

+

-

| '''MR PG 2000 agents 10 pims'''

+

-

| 2

+

-

| 4

+

-

| 1x 80

+

-

| 2

+

-

| &nbsp;

+

-

|-

+

-

| '''MR PG 1000 agents 5 pims'''

+

-

| 1

+

-

| 2

+

-

| 1x 80

+

-

| 2

+

-

| &nbsp;

+

-

|-

+

-

| '''VRU PG 9600 ports 10 pims'''

+

-

| 2

+

-

| 2

+

-

| 1x 80

+

-

| 2

+

-

| &nbsp;

+

-

|-

+

-

| '''VRU PG 1200 ports 4 pims'''

+

-

| 1

+

-

| 2

+

-

| 1x 80

+

-

| 2

+

-

| &nbsp;

+

-

|-

+

-

| '''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

+

-

| &nbsp;

+

-

|-

+

-

| '''TDM ACD PG 250 agents'''

+

-

| 1

+

-

| 2

+

-

| 1x 80

+

-

| 2

+

-

| &nbsp;

+

-

|-

+

-

| '''UCC Gateway PG 2000 agents'''

+

-

| 2

+

-

| 4

+

-

| 1x 80

+

-

| 2

+

-

| &nbsp;

+

-

|-

+

-

| '''UCC Gateway PG 450 agents'''

+

-

| 1

+

-

| 2

+

-

| 1x 80

+

-

| 2

+

-

| &nbsp;

+

-

|-

+

-

| '''Administration Client'''

+

-

| 1

+

-

| 2

+

-

| 1x 40

+

-

| 1

+

-

| &nbsp;(Client AW)

+

-

|-

+

-

| '''Administration Server - AW'''

+

-

| 1

+

-

| 2

+

-

| 1x 40

+

-

| 1

+

-

| &nbsp;

+

-

|-

+

-

| '''AW-HDS'''

+

-

| 4

+

-

| 4

+

-

| 1x 80 for OS<br>1x 500 for DB

+

-

| 1

+

-

| &nbsp;(200 reporters.)

+

-

+

-

The two vDisks can be in the same datastore

+

-

+

-

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

+

-

|-

+

-

| '''AW-HDS-DDS'''

+

-

| 4

+

-

| 4

+

-

| 1x 80 for OS<br>1x 500 for DB

+

-

| 1

+

-

| &nbsp;(200 reporters.)

+

-

+

-

The two vDisks can be in the same datastore

+

-

+

-

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

+

-

|-

+

-

| '''HDS-DDS'''

+

-

| 4

+

-

| 4

+

-

| 1x 80 for OS<br>1x 500 for DB

+

-

| 1

+

-

| (200 reporters.)

+

-

+

-

The two vDisks can be in the same datastore &nbsp;

+

-

+

-

The DB vDisk can be custom sized at OVA deployment based on solution sizing and customer retention requirements using the DB Estimator tool.

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)

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)