Updated feedback to the following sections: Modified link to Information for Partners; Unified CVP 8.0(1) Support for Virtualization on the ESXi/UCS Platform (Modified bullet that referred to 'Distributed'; Coresidency (Deleted references to realtime; Modified last bullet regarding support on Blade.)

UCS Network Configuration

1) TCP Setting modification on Reporting Server -The customers must modify the "Number of Receive Buffers" setting on the Reporting server to maximize full reporting and call load on the virtualized platform. If this setting is not modified after installing the OS, messages will get backed up on the CallServer and Message Queues will fill up resulting in a sharp drop in cps rate.

Set the "Number of Receive buffers" on the Reporting Server TCP settings to 4096 (max).

Instructions:

On Reporting server, click on Control Panel->Network Connection.

Right click on Network Connection.

Click on advanced tab.

Under property tab, select "Number of Receive Buffers".

In the Value pulldown, enter 4096.

Restart the Reporting Server.

2) The following table provides the transport protocols supported by different CVP versions on virtual and non-virtual (bare metal or MCS servers) deployments. The same transport protocol must be used on all call legs of the SIP comprehensive call flow deployments.

SIP transport protocols supported across various deployments:

Type of Hardware

CVP 8.5(1) ES6 or later releases

Releases prior to CVP 8.5(1) ES6

UCS C Series Virtualized*

TCP & UDP**

TCP

UCS B Series Virtualized*

TCP UDP***

TCP

Non Virtualized (bare metal)

TCP & UDP

TCP & UDP

The session transport protocol can be set to tcp or udp in the POTS dialpeer. Any other combinations of the transport protocols other than the ones listed above can cause call setup failures or abnormally long call setup times under heavy load.

Footnote:* Check the Docwiki supported Application page: docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications for the Cisco UCS B-series and C-series hardware models supported by the Unified CVP.** To avoid CPU utilization spikes under load conditions, the time synchronization between virtual machine and the ESX server must be disabled. To disable it, install VMware Tools in the virtual machine, in the Windows task bar, double click on the VM icon, in VMware Tools Properties window, uncheck Time synchronization between the virtual machine and the ESX Server checkbox.*** The UDP is supported on VMs on UCS B-200 M2 servers only. The UDP support is not qualified on other UCS B-series models and VMWare ESXi versions.3) Cisco VLAN trunking to VMWare For information on best practices for Cisco VLAN trunking to VMware, refer to the VMware website.

Support for Unified Communications Manager Clustering Over the WAN with Unified CVP on UCS Hardware

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

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

Multiple points of failure on the Unified CVP 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 should use a Nexus 7000 Series / Nexus 5000 Series vPC infrastructure, or a Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720-10G.

Notes for Deploying Unified CVP 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 Unified CVP applications on UCS B-series hardware with SAN:

Compliance Considerations

A dedicated SAN LUN and datastore must be used for Unified CVP database components. This means the CVP SAN LUNs cannot be shared by other applications. The SAN disk/storage array must be configured to meet the CVP IOPS requirements. The FC SAN solution is deployed in a shared environment where multiple applications are contending for storage access. The customers need to monitor the FC SAN performance and take appropriate actions to ensure the CVP IOPS and other UC IOPS requirements that share the same FC SAN systems are met. Should in the process of troubleshooting the SAN itself be identified as the problem, the customer must contact the system integrator or the SAN vendor for resolution.

For UCS B-series, Virtual Machines must be stored on and booted from the SAN.

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 Unified CVP 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 CVP applications should be designed for the 95th percentile IOPS values published in this wiki. Refer to the Performance Requirements section below for additional information. For other UC applications, please follow their respective IOPS requirements and guidelines.

Storage/Size Considerations

Unified CVP requires application storage to be on VMFS. Raw Device Mapping (RDM) is not supported.

The total size of all Virtual Machines on a disk (total size = VM disk + RAM copy) must not exceed 90% of the capacity of a datastore.

Input/Output Operations per Second (IOPS) Considerations

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. Refer to the Performance Requirements section below for additional information.

Maintenance Considerations

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

Notes for Deploying Unified CVP Applications on UCS C-Series Hardware

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 are either RAID 5 or RAID10.

Install ESXi 4.0/4.1 on the first disk array group (RAID 1 with disk 1 and disk 2)

The creation of the virtual machine for the Reporting Server requires a large virtual disk size. Max disk size for a single VM to be 438GB for the large reporting server.

You must follow the steps described below to configure the ESXi data store block size to 2MB.

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

Boot ESXi 4.0/4.1 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 (or RAID-10 ) configuration, and you will see in the formatting of “Datastore Details” that the block size is by default 1MB.

Right-click 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.

Steps for Installing Unified CVP Components on Virtual Machines

Follow the steps and references below to install or migrate the Unified CVP components on Virtual Machines.

Create the Unified CVP Virtual Machines from the OVA template. OVA templates are available here

Install Windows OS and Websphere Application Server (if using VXML Server with WAS) on the created Virtual Machines. (Note: Microsoft Windows Server 2003 Standard Edition should be used for virtual machine guests. See related information in the links below.)

Unified CVP Component Capacities and VM Configuration Requirements

This table shows the supported Unified CVP components, their capacities, and the VM computing resource requirements. You must use the OVA virtual machine templates to create the Unified CVP component VMs.

Unified CVP Component Co-Residency and Sample Deployments

You can have one or more Unified CVP VMs co-resident on the same ESXi server. However, you must follow the rules described below:

You can have any number of Unified CVP virtual machines and combination of co-residency of Unified CVP virtual machines with other UC applications 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.

You must not have CPU overcommitted on the ESXi server that is running Unified CVP application 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.

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.

VM co-residency with third party applications is not supported unless it is specifically described in this page. Currently, the Media Server for CVP is not recommended to be co-loaded on the CVP call server+vxml server VM.

The Media Server VM can use a 2 vCPU VM profile like the CVP Operations Console VM profile. However, this is a third party VM and can be tailored to have a different VM profile to satisfy a particular CVP deployment need.

On the other hand, CVP Media Server can be on the CVP Call Server+VXMl Server VM, providing the following conditions are met:

- IIS is used; not Tomcat.

- Audio prompts are cached on the VGW.

- Logging is turned off on the MS media server.

Creating Virtual Machines from OVA VM Templates

Open Virtualization Format (OVF) is an open standard for packaging and distributing virtual appliances. Files in this format have an extension of .ova. The naming convention for the template is PRODUCT_COMPONENT_USER COUNT_VERSION_VMVER.ova

Follow the instructions in the Downloading OVA Templates section below to download the OVA templates from cisco.com to a local datastore that vSphere Client can access.

Downloading OVA Templates

To download a single OVA file, click the Download File button next to that file. To download multiple OVA files, click the Add to Cart button next to each file that you want to download, 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.

Notes

VM CPU affinity is not supported. You do not need to set CPU affinity for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform.

VM resource Reservation - VM resource reservation is not supported for the VMs that are running Unified CVP 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.

It is required that hyperthreading be enabled by default when running CVP on ESXi. ESXi Server hyperthread is enabled by default and this setting should not be modified. Please ensure all VM's with CVP servers has hyperthreading enabled.

Remote Control of the Virtual Machines

For administrative tasks, you can use either Windows Remote Desktop or the VMware Infrastructure Client for remote control.

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 the VMware documentation for instructions on installing or upgrading VMware Tools on the VM with Windows operating system.

Installing Unified CVP Components on Virtual Machines

You can install the Unified CVP components after the configuration of the VMs. Installation of these Unified CVP components on a VM is the same as the installation of these components on physical hardware.

Refer to the Unified CVP documentation for the steps to install Unified CVP components. You can install the supported Virus Scan software, or any other software in the same way as on physical hardware. Refer to the CVP Hardware and System Software Specification for more information.

The creation of the virtual machine for the Unified CVP Reporting Server requires a large virtual disk size. You must follow the steps described below to configure the ESXi data store size to 438 GB for it to handle the Unified CVP Reporting Server data before you deploy the OVAs

Timekeeping Best Practices for Windows

ESXi hosts and domain controllers should synchronize the time from the same NTP source.

When Unified Unified CVP 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.