Virtualization for Cisco Unified Communications Manager (CUCM)

From DocWiki

Revision as of 12:11, 28 January 2014

Version 10.0(1)

Click here for a Legend

Version 9.1(x)

Click here for a Legend

Version 9.0(1)

Click here for a Legend

Version 8.6(x)

Click here for a Legend

Version 8.5(x)

Click here for a Legend

Note:

clean these up these are not accurate. Fix download link and VM specs (and add notes on what each vDisk is for in the notes).

Version 8.0(2+)

Click here for a Legend

Note:

clean these up these are not accurate. Fix download link and VM specs (and add notes on what each vDisk is for in the notes).

Notes on 1000 user VM configuration

• Use for publishers, subscribers, standalone TFTP, standalone multicast MOH nodes, ELM or PAWS-M.
• User count based on:
  • 1 device per user
  • 1K phones per VM
  • 4K max phones per cluster
  • 6K max BHCC per VM
  • 24K max BHCC per cluster
  • Your design/results may vary

Certain solution releases of Cisco Hosted Collaboration Solution also support a 600 user VM configuration.  For more details, see http://docwiki.cisco.com/wiki/Cisco_Hosted_Collaboration_Solution (specifically the OVA Requirements of the Compatibility Matrix for the HCS solution release desired).

Notes on 2500 user VM configurations

Note:

The 2500 user VM configuration with one vcpu may exhibit performance issues during CPU/IO-intensive operations (such as installs, upgrades, backups and CDR writes), or if your deployment has certain characteristics such as a large quantity of TFTP files. Changing the VM config to 2 vcpu is recommended as a prevention strategy. Otherwise you may deploy with one vcpu and be TAC-supported, but note that if the root cause of performance issues is found to be insufficient vcpu, Cisco TAC will ask that you change this to 2 vcpu. If your deployment is not experiencing any issues you are not required to change to 2 vcpu and may remain on 1 vcpu.

• Use for publishers, subscribers, standalone TFTP, standalone multicast MOH nodes.ELM or PAWS-M
• User count based on:
  • 1 device per user
  • 2.5K phones per VM
  • 10K max phones per cluster
  • 15K max BHCC per VM
  • 60K max BHCC per cluster
  • Your design/results may vary

Cisco Hosted Collaboration Solution has an alternative 2500 user VM configuration.  For more details, see http://docwiki.cisco.com/wiki/Cisco_Hosted_Collaboration_Solution (specifically the OVA Requirements of the Compatibility Matrix for the HCS solution release desired).

Notes on 7500 user VM configuration

• Use for publishers, subscribers, standalone TFTP, standalone multicast MOH nodes, ELM or PAWS-M.
• User count based on:
  • 1 device per user
  • 7.5K phones per VM
  • 30K max phones per cluster
  • 45K max BHCC per VM
  • 180K max BHCC per cluster
  • Your design/results may vary
• VM configurations with 2 virtual disks use them as follows:
  • vDisk 1 = Operating System + app binaries
  • vDisk 2 = Logs

Notes on 10000 user VM configuration

• Use for publishers, subscribers, standalone TFTP, standalone multicast MOH nodes, ELM or PAWS-M.
• User count based on:
  • 1 device per user
  • 10K phones per VM
  • 40K max phones per cluster
  • 60K max BHCC per VM
  • 240K max BHCC per cluster
  • Your design/results may vary
• VM configurations with 2 virtual disks use them as follows:
  • vDisk 1 = Operating System + app binaries
  • vDisk 2 = Logs

Notes on Standalone ELM and PAWS-M VM configurations

For Small or Small Plus TRCs, or for Specs-based servers with a Restricted UC Performance CPU, use UCM 1K user VM configuration as the "Small ELM" or "Small PAWS-M" capacity point.

For all other TRCs, and for Specs-based servers with a Full UC Performance CPU, use the UCM 2.5K user VM configuration as the "Medium/Large ELM" or "Medium/Large PAWS-M" capacity point.

Notes on Standalone PLM VM configurations

VM configuration applies to all TRCs, and for Specs-based both Restricted UC Performance CPUs and Full UC Performance CPUs.  Also ships as part of UCM media kit.

Notes on PCD VM configurations

VM configuration applies to all TRCs, and for Specs-based both Restricted UC Performance CPUs and Full UC Performance CPUs.  PCD OVA containing preinstalled app ships as part of UCM media kit.

IOPS and Storage System Performance Requirements

This section provides the IOPS data for a Cisco Unified Communications Manager system under load. These values are per active VM. Which VMs are active, and how many are active simultaneously, depends on how the CUCM cluster nodes are setup with respect to service activation, redundancy groups, etc. (see www.cisco.com/go/ucsrnd for details).

93-98% ot total IO is "sequential writes" with an IO block size of 4 kilobytes.

• Active call processing: As a reference, the following steady state IOPS were observed at various loads (expressed in Busy Hour Call Attempts):

• 10K BHCA produces ~ 35 IOPS
• 25K BHCA produces ~ 50 IOPS
• 50K BHCA produces ~ 100 IOPS
• 100K BHCA produces ~ 150 IOPS

• Software upgrades during business hours generate 800 to 1200 IOPS in addition to steady state IOPS.
• CDR/CMR via CDR Analysis and Reporting (CAR)
  • CUCM sending CDR/CMR to the external billing server does not incur any additional IOPS.
  • Enabling CAR continuous loading results in around 300 IOPS average on the system.
  • Scheduled uploads are around 250 IOPS for Publisher's VM only.
• Trace collection is 100 IOPS (occurs on all VMs for which tracing is enabled).
• Nightly backup (usually Publisher's VM only) is 50 IOPS.

CUCM in Cisco Mobile Ready Net (MRN)

• Click here for an overview of Cisco Mobile Ready Net (MRN).
• Click here for CUCM authorized platforms when part of Cisco MRN.
• From a technical perspective, CUCM 8.6 or higher is allowed on these platforms, but customers must verify that the desired CUCM version meets certification requirements (JITC, etc.).