Table of Contents
This document provides information about the platforms supported for Unity Connection 10.x, including those shipped by Cisco and those provided by customers. The Unity Connection installation application prevents installation on servers that do not meet the exact specifications or models listed in this document.
- Platform Overlays
- Configuring vCPU, vRAM, and vDisk for Virtual Machines
- Additional Platform Information
- Supported Platform
- Specifications for Currently Shipping Platforms Supported for Unity Connection 10.x
- Specification for Hardware Platforms and Cisco IOS Software Releases Supported by Unity Connection SRSV 10.0(1) and later
- Specifications for Virtual Platform Overlays Supported by Unity Connection SRSV 10.0(1) and later
- Specification for HTTPS Networking
- Specifications for Virtual Platform Overlays
- Additional Information Related to Platform-Overlay Specifications
- With Unity Connection 10.0(1) and later releases, virtual machines are the only supported platform for installation. Table 1 , “ Specifications for Virtual Platform Overlays for Currently Shipping Unity Connection 10.x Servers ,” lists the virtualization specifications, and the user and port limits when you install Unity Connection 10.x on a virtual machine.
- Specification for Hardware Platforms and Cisco IOS Software Releases Supported by Unity Connection SRSV 10.0(1) and later—Describes only platforms that are supported for use in physical configurations.
For information on system requirements for a virtual environment, see the “Requirements for Installing Cisco Unity Connection on a Virtual Machine” section in the System Requirements for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.html.
For platform/ part number, see the link: http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unity_Connection
1@a minimum of 2.13 GHz (2.13 GHz reserved) or
2 @ minimum of 1.8 GHz each (3.6 GHz reserved)4
Total number of active clients: Cisco Unified Personal Communicator + Third-party IMAP + Cisco Unity conferencing + Cisco Unified Mobile Advantage + RSS + Phone View users (assumes all IMAP Idle clients; see the “IMAP Idle Clients” section)
2.For VMware vSphere ESXi 5.5 and later, Latency Sensitivity function is included to reduce virtual machine latency. When the Latency Sensitivity value is set to high you do not need to leave any unused processor core for the ESXi hypervisor / scheduler.
3.For Spec- based processor requirements, see http://docwiki.cisco.com/wiki/Specification-Based_Hardware_Support#Processor_Requirements.
5.For SRE-910 and UCS E blade, though you are allowed to create more than 8 ports on Cisco Unity Connection Administration, it is recommended to create a maximum of 8 ports to avoid performance issues.
7.The total number of Unity Connection SRSV branches supported is applicable only for Unity Connection 10.5(1) and later releases. The total number for SRSV branches supported for Unity Connection 10.0(1) is 5.
8.The total number of Unity Connection SRSV branches supported is applicable only for Unity Connection 10.5(1) and later releases. The total number for SRSV branches supported for Unity Connection 10.0(1) is 10.
9.The total number of Unity Connection SRSV branches supported is applicable only for Unity Connection 10.5(1) and later releases. The total number for SRSV branches supported for Unity Connection 10.0(1) is 10.
The Unity Connection cluster feature provides high-availability voice messaging with two Unity Connection servers that are configured in a cluster. In this configuration, also known as active-active high availability, a single node consists of two servers, and the number of ports depends on the server model. The total number of node ports is additive (meaning a single node can support up to 500 ports, but the total number of users supported is applicable only to the primary server. The primary and secondary servers in a cluster must match in CPU and amount of memory, or the configuration is not supported.
If the hard disk space does not match on the two servers that you are using for a cluster, the smaller amount of disk space determines the storage capacity for each server in the cluster. See also the “Requirements for a Cisco Unity Connection 10.x Cluster” section in System Requirements for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/requirements/10xcucsysreqs.html.
The calculations for the total number of active clients assume the use of IMAP clients that support IMAP Idle. Cisco Unified Personal Communicator 7.0 and earlier, Cisco Unified Mobility Advantage, and Cisco Unified Mobile Communicator do not support IMAP Idle. As a result, each active instance of each of these clients (that does not support IMAP Idle) that is accessing Unity Connection voice messages counts as four active clients.
To simplify deployment of Unity Connection on a virtual machine, Cisco provides OVA templates for the virtual platform overlays defined in Table 1.
Caution Changing the number of virtual CPUs, the amount of virtual RAM, or the number or size of virtual disks is not supported.
For information on downloading the latest OVA files, see the “Installation and Upgrade Information” section in the applicable Release Notes for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
For information on deploying an OVA file while installing a new Unity Connection virtual server, see Install, Upgrade,and Maintenance Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx.html.
For information on deploying an OVA file while migrating from a physical server to a virtual server, see the “Migrating from a Cisco Unity Connection Physical Server to a Unity Connection 10.x Virtual Server” chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 10.x. .
For information on deploying other Unified Communication applications on the same physical server with Unity Connection, see the Unified Communications Virtualization wiki at http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization.
MCS servers are not supported for use with Unity Connection 10.x, and an attempt to install or upgrade to Unity Connection 10.x on these servers will fail. For more information on migrating a physical server to a virtual machine as you upgrade to Unity Connection 10.x, see the applicable chapter in the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 10.x at
- Currently Shipping Blade Servers for Cisco Integrated Services Routers Generation 2 (ISR G2)
- Currently Shipping Platforms for Virtual Configurations
For more information on SRE-900 and SRE-910, refer to http://docwiki.cisco.com/wiki/Cisco_Unity_Connection_on_UCSE.
For more information on UCS E-140D, E140DP, E160D, and E160DP, refer to http://docwiki.cisco.com/wiki/Cisco_Unity_Connection_on_UCSE.
Specification for Hardware Platforms and Cisco IOS Software Releases Supported by Unity Connection SRSV 10.0(1) and later
Note A different Cisco IOS software release may be required depending on the version of Cisco Unified Communications Manager Express or Cisco Unified Survivable Remote Site Telephony (SRST) being used. For more information refer to Cisco Unified Communications Manager Express documentation available at http://www.cisco.com/en/US/products/sw/voicesw/ps4625/index.html.
Total number of available voice ports 11
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)