|
Version 12.5(x) |
(top) |
ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
|
Version 12.0(x) |
(top) |
ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
|
|
Version 11.6(x) |
(top) |
ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
|
|
Version 11.5(x) |
(top) |
ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
|
|
Version 11.0(x) |
(top) |
ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
|
|
Version 10.0(x) and 10.5(x) |
(top) |
ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
|
|
Notes on Call+VXML Server VM configuration |
(top) |
|
The following deployments and Unified CVP components have not been qualified and are not supported in virtualization:
H323 Call flow Deployment
Distributed VXML Server and Call Server deployment where each server runs on a separate VM
All in one lab deployment with small reporting server.
Note: Unified CVP components are supported on the UCS platform only in a virtualized environment with ESXi server.
Depending on design requirements, the Media Server component may either be hosted in this VM, or run in a separate VM (see Notes on Media Server VM configuration).
|
|
Notes on Reporting Server VM configuration |
(top) |
|
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.
Steps to configure the ESXi for CVP Reporting server to RAID10 found at CVP Reporting Server Configuration.
|
|
Notes on Operations Console VM configuration |
(top) |
|
None.
|
|
Notes on Media Server VM configuration |
(top) |
|
The Media Server component may either run inside the Call+VXML Server VM or run in a separate VM.
If it runs in a separate VM, it can either use the same VM configuration as the Operations Console or be a customer-tailored VM configuration (since this is a 3rd-party VM).
|
|
Notes on UCS Tested Reference Configuration and Specs-based Support |
(top) |
|
The EOS notice for the Cisco Business Edition 7000M server does not apply to the C220M3SFF TRC (SKU: UCUCS-EZ-C220M3S) or C240M3S TRC #1 (SKU: UCUCS-EZ-C240M3S. The C220M3SFF TRC and C240M3S TRC #1 will continue to be sold until these M3 TRC servers are EOS.
When the hardware support is specified as "Yes (See details)", the following exceptions exist, as applicable to the TRC or Specs-based policy referenced: The UCS M4 generation of C series servers is supported for use with any version of the Cisco Unified CVP where the UCS M3 TRCs are supported as long as the firmware 2.0(9c) and later applied on the UCS C M4 series.
|
|
IOPS and Storage System Performance Requirements |
(top) |
|
Windows Server 2016:
IOPS metrics measured in peak load conditions with failover:
CVP Server |
Average |
Max |
95th Percentile |
Call Server/ VXML Servers/ Media Servers |
50 |
120 |
73 |
Reporting Server |
95 |
150 |
120 |
Operation Server |
10 |
30 |
20 |
Read/Write Ratio:
CVP Server |
Average |
Max |
95th Percentile |
Call Server/ VXML Servers/ Media Servers |
40/2673 |
2989/5723 |
41/2672 |
Reporting Server |
30/700 |
1231/3349 |
138/3221 |
Operation Server |
12/15 |
107/94 |
67/79 |
|
|
|