Design Guide for Cisco Unity Connection Release 8.x
Virtualization in Cisco Unity Connection 8.x
Downloads: This chapterpdf (PDF - 83.0KB) The complete bookPDF (PDF - 2.69MB) | Feedback

Table of Contents

Virtualization in Cisco Unity Connection 8.x

Virtualization Requirements for Cisco Unity Connection 8.x

Scalability Differences Between Physical and Virtual Configurations

Licensing Cisco Unity Connection 8.x on Virtual Machines

Installing Cisco Unity Connection 8.x Cluster Servers on Virtual Machines

Migrating Cisco Unity Connection 8.x from Physical Servers to Virtual Machines

Virtualization in Cisco Unity Connection 8.x

Beginning with Cisco Unity Connection 8.x, you can install Connection on a virtual machine. In most ways, Connection running on a virtual machine works the same way as Connection running on a physical server. This chapter discusses the differences.

Virtualization Requirements for Cisco Unity Connection 8.x

Detailed requirements for installing Cisco Unity Connection on a virtual machine are listed in the “Requirements for Installing Cisco Unity Connection on a Virtual Machine” section of System Requirements for Cisco Unity Connection Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html .

Scalability Differences Between Physical and Virtual Configurations

The maximum number of ports, the maximum number of users with mailboxes, and other scalability specifications differ between comparable physical and virtual configurations. For detailed information, see the Cisco Unity Connection 8.x Supported Platforms List at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html .

Licensing Cisco Unity Connection 8.x on Virtual Machines

On Cisco Unity Connection physical servers, each license file for a Cisco Unity Connection is registered to the MAC address of the network interface card in the server. On Connection virtual machines, each license file (except for demonstration license files) is registered to a license MAC value. This value is calculated to look like a MAC address based on several settings (time zone, hostname, IP address, SSL certificate information, and others), but it is not a real MAC address.


Note If you change any of the values from which the license MAC value is calculated, you need to replace Connection licenses with licenses that contain the new license MAC value.


For more information on Connection licensing, including a list of the setting changes that require you to replace license files, see the “ Managing Licenses in Cisco Unity Connection 8.x ” chapter of the System Administration Guide for Cisco Unity Connection Release 8.x , at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagx.html .

Installing Cisco Unity Connection 8.x Cluster Servers on Virtual Machines

Note the following about Cisco Unity Connection clusters and virtualization:

  • You can install a Connection cluster on two virtual machines, or you can install a cluster on one virtual machine and one physical machine.
  • If you install a Connection cluster on two virtual machines, the virtual machines must not be on the same blade. Ideally, the virtual machines will be on separate chassis.
  • If you install a Connection cluster on one virtual machine and one physical machine, we recommend that you configure the virtual machine to match the specifications of the physical server for CPU, memory, and disk space. If disk space on the physical server and virtual machine do not match, Connection uses the smaller disk size to determine when the disk on which messages are stored has reached maximum capacity.
  • For information on installing Connection on physical hosts and on virtual machines, see the Installation Guide for Cisco Unity Connection Release 8.x , at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/installation/guide/8xcucigx.html .

Migrating Cisco Unity Connection 8.x from Physical Servers to Virtual Machines

Note the following about migrating from a Cisco Unity Connection physical server to a Connection 8.x virtual machine: