Virtualization for Unified CCE

From DocWiki

Revision as of 17:36, 1 April 2014 by Aspauldi (Talk | contribs)
Jump to: navigation, search



Contents

Version 10.0(x)


Click here for a Legend

Component & Capacity Point
Preloaded with Business Edition?
VM Configuration Requirements
click to download OVA file for this version
Supported Hardware (Latest)
Supported Hardware (Older)
vCPU
vRAM
vDisk
vNIC
UCS Tested Reference Configurations
S is same as BE6000 MD
S+ is same as BE6000 HD
M includes BE7000
UCS or 3rd-party Specs-based on Intel Xeon
UCS Tested Reference Configurations
UCS or 3rd-party Specs-based on Intel Xeon
S
S+
M
L
XL
2XL
Full UC Perf. CPU
Restricted UC Perf. CPU
S
M
Full UC Perf. CPU
Restricted UC Perf. CPU
Router
See notes
No 4 8 GB 1x 80 GB 2 No No Yes Yes Yes Yes Yes No No Yes Yes No
Logger
See notes
No 4 8 GB 1x 80 GB (OS)
1x 500 GB (DB)
2 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
Rogger
See notes
No 4 6 GB 1x 80 GB (OS)
1x 150 GB (DB)
2 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
Progger
See notes
No 4 6 GB 1x 150 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Large Agent PG
See notes
No 2 6 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Large CAD Agent PG
See notes
No 2 6 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Large CAD Agent PG w/ SQL
See notes
No 4 6 GB 1x 80 GB (OS)
1x 80 GB (DB)
2 No Yes Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
Small Agent PG
See notes
No 1 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Small CAD Agent PG
See notes
No 1 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Small CAD Agent PG w/ SQL
See notes
No 2 6 GB 1x 80 GB (OS)
1x 80 GB (DB)
2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Large MR PG
See notes
No 2 6 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Small MR PG
See notes
No 1 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Large VRU PG
See notes
No 2 2 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Small VRU PG
See notes
No 1 2 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Avaya ACD PG
See notes
No 2 6 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Large TDM ACD PG
See notes
No 2 6 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Small TDM ACD PG
See notes
No 1 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Large UCC Gateway PG
See notes
No 2 6 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Small UCC Gateway PG
See notes
No 1 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Administration Client
See notes
No 1 2 GB 1x 40 GB 1 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Administration Server - AW
See notes
No 1 2 GB 1x 40 GB 1 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
AW-HDS
See notes
No 4 8 GB 1x 80 GB (OS)
1x 500 GB (DB)
1 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
AW-HDS-DDS
See notes
No 4 8 GB 1x 80 GB (OS)
1x 500 GB (DB)
1 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
HDS-DDS
See notes
No 4 8 GB 1x 80 GB (OS)
1x 500 GB (DB)
1 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
Sigtran Gateway
See notes
No 2 4 GB 1x 100 GB 1 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Remote Silent Monitor
See notes
No 2 4 GB 1x 100 GB 1 No Yes Yes Yes Yes Yes Yes No No Yes Yes No


Version 8.5(2+) through 9.0(x)


Click here for a Legend

Component & Capacity Point
Preloaded with Business Edition?
VM Configuration Requirements
click to download OVA file for this version
Supported Hardware (Latest)
Supported Hardware (Older)
vCPU
vRAM
vDisk
vNIC
UCS Tested Reference Configurations
S is same as BE6000 MD
S+ is same as BE6000 HD
M includes BE7000
UCS or 3rd-party Specs-based on Intel Xeon
UCS Tested Reference Configurations
UCS or 3rd-party Specs-based on Intel Xeon
S
S+
M
L
XL
2XL
Full UC Perf. CPU
Restricted UC Perf. CPU
S
M
Full UC Perf. CPU
Restricted UC Perf. CPU
Router
See notes
No 4 8 GB 1x 80 GB 2 No No Yes Yes Yes Yes Yes No No Yes Yes No
Logger
See notes
No 4 8 GB 1x 80 GB (OS)
1x 500 GB (DB)
2 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
Rogger
See notes
No 4 6 GB 1x 80 GB (OS)
1x 150 GB (DB)
2 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
Agent PG w/ CTI OS - 2,000 agents
See notes
No 2 6 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Agent PG w/ CTI OS - 450 agents
See notes
No 1 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Agent PG w/ CAD - 1,000 agents
See notes
No 2 6 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
Agent PG w/ CAD - 297 agents
See notes
No 1 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
MR PG - 2,000 agents - 10 PIMs
See notes
No 2 6 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
MR PG - 1,000 agents - 5 PIMs
See notes
No 1 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
VRU PG - 9,600 ports - 10 PIMs
See notes
No 2 2 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
VRU PG - 1,200 ports - 4 PIMs
See notes
No 1 2 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Avaya (Definity) ACD PG
See notes
No 2 6 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
TDM ACD PG - 2,000 agents
See notes
No 2 6 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
TDM ACD PG - 250 agents
See notes
No 1 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
UCC Gateway PG - 2,000 agents
See notes
No 2 6 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
UCC Gateway PG - 450 agents
See notes
No 1 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Administration Client
See notes
No 1 2 GB 1x 40 GB 1 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Administration Server - AW
See notes
No 1 2 GB 1x 40 GB 1 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
AW-HDS
See notes
No 4 8 GB 1x 80 GB (OS)
1x 500 GB (DB)
1 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
AW-HDS-DDS
See notes
No 4 8 GB 1x 80 GB (OS)
1x 500 GB (DB)
1 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
HDS-DDS
See notes
No 4 8 GB 1x 80 GB (OS)
1x 500 GB (DB)
1 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No


Version 8.0(2+) through 8.5(1)


Click here for a Legend

Component & Capacity Point
Preloaded with Business Edition?
VM Configuration Requirements
click to download OVA file for this version
Supported Hardware (Latest)
Supported Hardware (Older)
vCPU
vRAM
vDisk
vNIC
UCS Tested Reference Configurations
S is same as BE6000 MD
S+ is same as BE6000 HD
M includes BE7000
UCS or 3rd-party Specs-based on Intel Xeon
UCS Tested Reference Configurations
UCS or 3rd-party Specs-based on Intel Xeon
S
S+
M
L
XL
2XL
Full UC Perf. CPU
Restricted UC Perf. CPU
S
M
Full UC Perf. CPU
Restricted UC Perf. CPU
Router 8000 agents
See notes
No 2 4 GB 1x 80 GB 2 No No Yes Yes Yes Yes Yes No No Yes Yes No
Logger 8000 agents
See notes
No 4 4 GB 1x 80 GB (OS)
1x 150 GB (DB)
2 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
Rogger 4000 agents
See notes
No 4 4 GB 1x 80 GB (OS)
1x 150 GB (DB)
2 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
Agent PG - CTIOS 2000 agents
See notes
No 2 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Agent PG - CTIOS 450 agents
See notes
No 1 2 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Agent PG - CAD 1000 agents
See notes
No 2 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
Agent PG - CAD 297 agents
See notes
No 1 2 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
MR PG 2000 agents 10 pims
See notes
No 2 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
MR PG 1000 agents 5 pims
See notes
No 1 2 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
VRU PG 9600 ports 10 pims
See notes
No 2 2 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
VRU PG 1200 ports 4 pims
See notes
No 1 2 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Avaya ACD PG
See notes
No 2 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
TDM ACD PG 2000 agents
See notes
No 2 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
TDM ACD PG 250 agents
See notes
No 1 2 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
UCC Gateway 2000 agents
See notes
No 2 4 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
UCC Gateway 450 agents
See notes
No 1 2 GB 1x 80 GB 2 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Administration Client
See notes
No 1 2 GB 1x 40 GB 1 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
Administration Server - AW
See notes
No 1 2 GB 1x 40 GB 1 No Yes Yes Yes Yes Yes Yes No No Yes Yes No
AW-HDS
See notes
No 4 4 GB 1x 80 GB (OS)
1x 500 GB (DB)
1 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
AW-HDS-DDS
See notes
No 4 4 GB 1x 80 GB (OS)
1x 500 GB (DB)
1 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No
HDS-DDS
See notes
No 4 4 GB 1x 80 GB (OS)
1x 500 GB (DB)
1 No No Yes Yes Yes Yes Yes No No All except:
C210 M1 TRC#1
Yes No


IOPS and Storage System Performance Requirements

Unified CCE follows UC storage system design requirements. For more information, refer to UC Virtualization Storage System Design Requirements.

For information about TRC versus specs-based support for storage systems, refer to UC Virtualization Supported Hardware.

All Unified CCE VM vDisks must be deployed Thick Provisioned, Lazy, or Eager Zeroed. Thin Provisioned vDisks are not supported.

Storage Area Networks and Specs-based policy storage solutions must be able to handle the following Unified CCE application disk I/O characteristics. Tested Reference Configurations (TRC) for Cisco UCS C-Series servers do not need to apply these requirements against their Direct Attached Storage Arrays (DAS).

The data below is based on CCE 10.0(1) running on Windows Server 2008 R2 Enterprise.

Unified CCE Component IOPS Disk Read KBytes / sec Disk Write KBytes / sec Operating Conditions
Peak Avg. 95th Percentile Peak Avg. 95th Percentile Peak Avg. 95th Percentile


Router 9 4 6 1 0 0 134 95 111 12,000 agent;100 CPS, ECC: 5 scalars @ 40 bytes each; 200 Reporting users at max query load.
Logger 2365 1582 2076 19603 10846 16169 56969 31443 47395
HDS 1622 806 1239 81429 13386 35178 29406 8101 22747
DDS 2440 1460 2052 19201 9281 14654 59932 30624 49995
HDS 1561 365 957 61240 963 5374 12792 1068 5593 4,000 agents; 30 cps; ECC: 5 scalars @ 40 bytes each; 200 Reporting Users at max query load.
Rogger 1400 64 116 14226 204 203 24469 1339 3918
Agent PG 106 75 90 256 9 54 5548 3464 4384 2,000 agents, 15 cps


The data below is based on CCE 8.5(3)+ and 9.0(1)+ running on Windows Server 2008 R2 Enterprise.  

Unified CCE Component IOPS Disk Read KBytes / sec Disk Write KBytes / sec Operating Conditions
Peak Avg. 95th Percentile Peak Avg. 95th Percentile Peak Avg. 95th Percentile
Router 27 14 19 619 11 12 436 246 313 12,000 agent;100 CPS, ECC: 5 scalars @ 40 bytes each; 200 Reporting users at max query load
Logger 3662 917 1793 12821 735 11571 38043 2777 11832
HDS 1017 321 693 2748 250 2368 19351 1441 3879
Router 118 11 13 1681 14 5 971 66 172 8,000 agents;60 CPS; ECC:5 scalars @ 40 bytes each; 200 Reporting users at max query load
Logger 1614 502 1065 6137 341 4993 30379 558 5911
HDS 1395 165 541 1995 186 1776 12525 1299 2965
Rogger 1598 250 292 2227 1837 1984 13243 867 2308 4,000 agents; 30 cps; ECC: 5 scalars @ 40 bytes each


The data below is based on CCE 8.0(2) running on Windows Server 2003 R2.

Unified CCE Component IOPS Disk Read KBytes / sec Disk Write KBytes / sec Operating Conditions
Peak Avg. 95th Percentile Peak Avg. 95th Percentile Peak Avg. 95th Percentile


Router 20 8 10 520 30 180 400 60 150 8,000 agents; 60 cps; ECC: 5 scalars @ 35 bytes each; No reporting.
Logger 1,000 600 700 4,000 600 2,500 12,000 3,000 7,000
HDS 1,600 1,000 1,100 600 70 400 6,000 2,000 3,800
Agent PG 125 40 70 300 5 20 2,000 1,200 1,500 2,000 agents, 15 cps


HDS 3,900 2,500 3,800 75,000 30,000 50,000 9,500 2,200 5,800 8,000 agents; 60 cps; 200 reporting users at max query load; ECC: 5 scalars @ 35 bytes each.
ROGGER 610 360 425 2,700 400 1,600 7,500 2,150 4,300 4,000 agents; 30 cps; ECC: 5 scalars @ 35 bytes each


Unified CCE Network Configuration in a Virtualized Environment

For network configuration requirements and reference designs for Cisco Unified Contact Center Enterprise deployed on VMware vSphere, see Unified CCE Network Configuration in a Virtualized Environment.

QoS must be enabled for Unified CCE Private network communications Web Setup for the Router and PG Setup. For additional details, refer to the appropriate section in the Cisco Unified Contact Center Enterprise Installation and Upgrade Guide.

VMware vSphere ESXi NIC Teaming is required for Unified CCE Visible and Private network communications, please see Unified CCE Network Configuration in a Virtualized Environment as linked above.

Microsoft Windows Server software based IPSec is not supported.


Unified CCE Co-residency Support Policy

Unified CCE Co-residency policy is stated as Limited, though it may actually align to one of the other policies. This is due to IO limitations for Direct Attached Storage (DAS) arrays used with Unified CCE database applications.

Note: For any single DAS array, you cannot have two or more of the following on any single array: Logger, Rogger, Progger, HDS, or CVP Reporting Server.

Unified CCE otherwise adheres to the following Co-residency policies by version:

Version Co-residency Policy
10.0(x) Full
8.0(2+) - 9.0(x) UC on UC only

Full details of these policies are located on the Unified Communications Virtualization Sizing Guidelines page.


Hybrid Unified CCE Deployment Options

Unified CCE 10.0(x) and later supports only virtualized deployment on VMware vSphere ESXi. This is inclusive of Unified ICME, CCH, and ICMH.

Unified CCE releases prior to 10.0(x) support Hybrid deployment where some components could be deployed bare metal (OS on Server) on MCS servers alongside virtualized Unified CCE applications. Hybrid deployment does not allow A/B application processes to be disparate hardware server type or virtualized/bare metal deployed.

The following unified CCE applications do not support hybrid A/B:

  • Router
  • Logger
  • Rogger
  • Peripheral Gateway (all types) 

Hybrid deployment does, however, allow Router A/B to be bare metal on MCS with Logger A/B virtualized. 

Some examples of common hybrid deployments are as follows: 

  • Parent Unified ICME as bare metal on MCS with Child Unified CCE virtualized. 
  • Unified ICMH NAM as bare metal on MCS with Unified ICMH CICM virtualized (single instance). 
  • Unified CCE virtualized with ICM to ICM Gateway to Unified CCE bare metal on MCS. 


Unified CCE Hardware Requirements for Duplex Synchronized Applications

Unified CCE allows for application VMs to be deployed on different supported servers, whether Cisco UCS or 3rd Party Specs-based within the same or multiple data center sites, excepting duplex and synchronized operation applications, which have a more restrictive requirement.

The following Unified CCE applications are hardware-constrained for side A and B pairings:

  • Router
  • Logger
  • Rogger
  • Peripheral Gateway (PG, all types)

These require that the A and B application instances be installed to separate host servers have exact matching:

  • Processor make, model and speed
  • Memory type and speed
  • Mainboard chipset controller


Installing VMware Tools

You must install the VMware Tools on each of the VMs, and you must use all of the VMware Tools default settings. Please refer to VMware documentation for instructions on installing or upgrading VMware Tools on the VM with the Windows operating system.


Timekeeping Best Practices for Windows

Follow the instructions provided in the VMware Knowledge Base article VMware KB: Timekeeping best practices for Windows.

  • ESXi hosts and domain controllers must synchronize the time from the same NTP source.
  • When Unified CCE 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 2008 R2 guest operating system remains deselected; this check box is deselected by default.


System Performance Monitoring Using ESXi Counters

  • Make sure that you follow VMware's ESXi requirements and the SAN vendor's instructions for optimal system performance. 
  • VMware provides a set of system monitoring tools for the ESXi platform and the VMs. These tools are accessible through the VMware Infrastructure Client or through VirtualCenter.
  • You can use Windows Performance Monitor to monitor the performance of the VMs. Be aware that the CPU counters may not reflect the physical CPU usage since the Windows Operating System has no direct access to the physical CPU.
  • You can use Unified CCE Serviceability Tools and Unified CCE reports to monitor the operation and performance of the Unified CCE system.
  • The ESXi Server and the virtual machines must operate within the limit of the following ESXi performance counters.


Use the following ESXi counters as performance indicators.

Category Object Measurement Units Description Performance Indication and Threshold
CPU
  • ESXi Server
  • VM


CPU Usage (Average) Percent CPU Usage Average in percentage for:
  • ESXi server
  • Virtual machine


Less than 60%.
CPU
  • ESXi Server Processor#
  • VM_vCPU#


CPU Usage 0 - 7 (Average) Percent CPU Usage Average for:
  • ESXi server for processors 0 to 7
  • Virtual machine vCPUs


Less than 60%
CPU VM CPU Ready mSec The time a virtual machine or other process waits in the queue in a ready-to-run state before it can be scheduled on a CPU. The raw counter value cannot be used by itself but rather should be converted to a percentage (i.e., the percentage of time spent waiting for a CPU to become ready) using the following formula (assume sample interval is 20 seconds and the CPU Ready counter value is 400ms):

Divisor = (Sample Interval (in milliseconds) / 100)
Example: (20s * 1000ms) / 100 = 20,000 / 100 =200

Single vCPU: Percentage = Value / Divisor
Example: 400 / 200 = 2.0%

Entire VM: Percentage = Value / Divisor * (#vCPU allocated to VM))
Example: 400 / (200 * 4) = 0.5%

The threshold for a single vCPU is 10%.

The threshold for a VM is 2.5%.
Memory
  • ESXi Server
  • VM


Memory Usage (Average) Percent Memory Usage = Active/ Granted * 100 Less than 80%
Memory
  • ESXi Server
  • VM


Memory Active (Average) KB Memory that is actively used or being referenced by the guest OS and its applications. When it exceeds the amount of memory on the host, the server starts a memory swap. Less than 80% of the Granted memory
Memory
  • ESXi Server
  • VM


Memory Balloon (Average) KB ESXi uses balloon driver to recover memory from less memory-intensive VMs so it can be used by those with larger active sets of memory. Since the memory is not overcommitted, this should be 0 or very low. Note: ESXi performs memory ballooning before memory swap.
Memory
  • ESXi Server
  • VM


Memory Swap used (Average) KB ESXi Server swap usage. Use the disk for RAM swap Since the memory is not overcommitted, this should be 0 or very low.
Disk
  • ESXi Server
  • VM


Disk Usage (Average) KBps Disk Usage = Disk Read rate + Disk Write rate Ensure that the SAN is configured to handle this amount of disk I/O.
Disk
  • ESXi Server vmhba ID
  • VMbha ID


Disk Usage Read rate  KBps Rate of reading data from the disk Ensure that the SAN is configured to handle this amount of disk I/O.
Disk
  • ESXi Server vmhba ID
  • VM vmhba ID


Disk Usage Write rate KBps Rate of writing data to the disk Ensure that the SAN is configured to handle this amount of disk I/O.
Disk
  • ESXi Server vmhba ID
  • VM vmhba ID


Disk Commands Issued Number Number of disk commands issued on this disk in the period. Ensure that the SAN is configured to handle this amount of disk I/O.
Disk
  • ESXi Server vmhba ID
  • VM vmhba ID


Disk Command Aborts Number Number of disk commands aborted on this disk in the period. Disk command aborts when the disk array is taking too long to respond to the command. (Command timeout)

This counter should be zero. A non-zero value indicates a storage performance issue.

Disk
  • ESXi Server vmhba ID
  • VM vmhba ID


Disk Command Latency mSec The average amount of time taken for a command from the perspective of a Guest OS. Disk Command Latency = Kernel Command Latency + Physical Device Command Latency. A latency of 24ms or greater is indicative of a possibly overutilized, misbehaving, or misconfigured disk array.
Disk
  • ESXi Server vmhba ID
  • VM vmhba ID


Kernel Disk Command Latency mSec The average time spent in ESXi Server VMKernel per command. Kernel Command Latency must be very small in comparison to the Physical Device Command Latency, and it must be close to zero.  Kernel Command Latency can be high, or even higher than the Physical Device Command Latency if there is a lot of queuing in the ESXi kernel.
Network
  • ESXi Server
  • VM


Network Usage (Average) KBps Network Usage = Data receive rate + Data transmit rate Less than 30% of the available network bandwidth; for example, less than 300Mps for a 1G network.
Network
  • ESXi Server vmnic ID
  • VM vmnic ID


Network Data Receive Rate KBps Less than 30% of the available network bandwidth; for example, less than 300Mps for a 1G network.
Network
  • ESXi Server vmnic ID
  • VM vmnic ID


Network Data Transmit Rate KBps The average rate at which data is transmitted on this Ethernet port Less than 30% of the available network bandwidth; for example, less than 300Mps for a 1G network.


System Performance Monitoring Using Windows Perfmon Counters

You must comply with the requirements described in the System Performance Monitoring section of the Unified Contact Center Enterprise Design Guide and in the Performance Counters section in the Release 10.0(1) Serviceability Best Practices Guide for Unified ICM/Contact Center Enterprise.


Information for Partners About Unified CCE on UCS Deployment Certification and Ordering

It is important that partners who are planning to sell UCS products on Unified Contact Center Enterprise read the following Doc Wiki page: UCCE on UCS Deployment Certification Requirements and Ordering Information.

This page contains essential information for partners about the following:

  • Partner Certification Requirements
  • UCS Server Ordering Information
  • Important Notes on Cisco UCS Service and Support




Back to: Unified Communications in a Virtualized Environment

Rating: 3.9/5 (18 votes cast)

Personal tools