Contents
|
To enable the virtual hardware resource reservation for Unified CVP VMs, the setting for CPU and memory should to be modified as shown in the following table.
For Unified CVP 11.5(1) version
CPU | Hard disk | Hard disk | |||||
Sockets | Cores | Memory | Disk 1 | Disk 2 | CPU speed reservation | Memory reservation | |
CVP VXML | 4 | 1 | 10 GB | 250 GB | NA | 3000 | 10 GB |
OAMP | 2 | 1 | 4 GB | 80 GB | NA | 400 | 4 GB |
Reporting Server | 4 | 1 | 6 GB | 80 GB | 438 GB | 1800 | 6 GB |
For Unified CVP 11.0(1) version
CPU | Hard disk | Hard disk | |||||
Sockets | Cores | Memory | Disk 1 | Disk 2 | CPU speed reservation | Memory reservation | |
CVP VXML | 4 | 1 | 6 GB | 150 GB | NA | 1800 | 6 GB |
OAMP | 2 | 1 | 2 GB | 80 GB | NA | 400 | 2 GB |
Reporting Server | 4 | 1 | 4 GB | 72 GB | 438 GB | 1800 | 4 GB |
For Unified CVP 9.0(1), 10.0(1), and 10.5(1) versions
CPU | Hard disk | Hard disk | |||||
Sockets | Cores | Memory | Disk 1 | Disk 2 | CPU speed reservation | Memory reservation | |
CVP VXML | 2 | 2 | 4 GB | 146 GB | NA | 2200 | 4 GB |
OAMP | 1 | 2 | 2 GB | 40 GB | NA | 400 | 2 GB |
Reporting Server | 2 | 2 | 4 GB | 72 GB | 438 GB | 1800 | 4 GB |
The following table lists Kernel-based Virtual Machine (KVM) profiles for Cisco ISR series routers that support VVB.
Cisco Integrated Service Routers (ISR) * | vCPU | Memory | Disk | NIC | Flash |
ISR 4331 | 6 | 6 GB | 146 GB | 1 | 16 GB |
ISR 4351 | 6 | ||||
ISR 4431 | 6 | ||||
ISR 4451 | 2 |
* Requires IOS XE 3.17 or higher release.
Migration of Unified CVP from physical (MCS) server to any virtual server (UCS or non-UCS) server is not supported.
IMPORTANT: For instructions on performing the network configuration needed to deploy Cisco Unified Customer Voice Portal (Unified CVP) on a virtualized platform, please see below.
1) Network adapter 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.
Instructions:
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 | Releases prior to CVP 8.5(1) ES6 | CVP 8.5(1) ES6 or later releases |
---|---|---|
UCS C Series Virtualized* | TCP | TCP & UDP** |
UCS B Series Virtualized* | TCP | TCP UDP*** |
Non Virtualized (bare metal) | TCP & UDP | TCP & UDP |
Note:
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 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.
*** All the UCS servers listed on the Unified
Communications Virtualization Supported Applications page support UDP on
both VMWare ESXi 4.1 and ESXi 5.0.
3) Cisco VLAN trunking to VMWare For information on best practices
for Cisco VLAN trunking to VMware, refer to the
VMware website
Follow the steps and references below to install or migrate the Unified CVP components on Virtual Machines.
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.
Before You Begin
Shut down the virtual machine.
Ensure that no snapshots are taken for the virtual machine.
Procedure
1. From the ESXi Console Configuration window, enable remote console
access and ssh for remote console.
2. Log in to the ESXi host using a SSL shell client tool such as
PuTTy/SecureCRT.
3. To obtain the <vm.vmdk> information from the vSphere client,
right-click on the virtual machine, and choose Edit Settings > Hard Disk.
4. Navigate to the vmfs/volumes/<datastore>/ VM folder.
5. From the command prompt, run the following command:
vmkfstools -X 80G <vm.vmdk>
Note: Use the virtualmachine.vmdk descriptor file as the parameter in the above command.
6. The script runs and expands the virtual machine disk space.
7. Exit the SSH shell client and power on the virtual machine.
8. To launch the Disk Management tool, choose Start and type
partition in the search box.
9. Right-click on the C drive, choose Extend Volume, and click
Finish.
10. Restart the server.
Note: Ensure that the disk space increased to 80 GB.
In the vSphere client, perform the following steps to deploy the Virtual machines.
Notes:
For administrative tasks, you can use either Windows Remote Desktop or the VMware Infrastructure Client for remote control.
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.