Virtualization for Cisco Unified Communications Manager (CUCM)

From DocWiki

Revision as of 15:46, 21 May 2013 by Jarias (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Version 9.1(x)

Click here for a Legend

Component & Capacity Point
Use with BE 6000?
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
UCS or 3rd-party Specs-based on Intel Xeon
UCS Tested Reference Configurations
UCS or 3rd-party Specs-based on Intel Xeon
S
M
L
XL
2XL
Full UC Perf. CPU
Restricted UC Perf. CPU
S
M
Full UC Perf. CPU
Restricted UC Perf. CPU
1000 users
See notes
Yes 2 4 GB 1x 80 GB 1 Yes Yes Yes Yes Yes Yes No Yes Yes Yes No
2500 users
(larger vDisk)
See notes
No 1
See notes
4 GB 1x 80 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
2500 users
(smaller vDisk)
See notes
No 2 3 GB 1x 60 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
7500 users
See notes
No 2 6 GB 1x 110 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
10,000 users
See notes
No 4 6 GB 1x 110 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
Cisco Enterprise Licensing Manager (ELM)
No Treat as a Unified CM Subscriber. Use one of the VM configurations above.
Platform Administrative Web Services Management (PAWS-M)
No Treat as a Unified CM Subscriber. Use one of the VM configurations above.


Version 9.0(1)

Click here for a Legend

Component & Capacity Point
Use with BE 6000?
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
UCS or 3rd-party Specs-based on Intel Xeon
UCS Tested Reference Configurations
UCS or 3rd-party Specs-based on Intel Xeon
S
M
L
XL
2XL
Full UC Perf. CPU
Restricted UC Perf. CPU
S
M
Full UC Perf. CPU
Restricted UC Perf. CPU
1000 users
See notes
Yes 2 4 GB 1x 80 GB 1 Yes Yes Yes Yes Yes Yes No Yes Yes Yes No
2500 users
(larger vDisk)
See notes
No 1
See notes
4 GB 1x 80 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
2500 users
(smaller vDisk)
See notes
No 1
See notes
3 GB 1x 60 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
7500 users
See notes
No 2 6 GB 2x 80 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
10,000 users
See notes
No 4 6 GB 2x 80 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
Cisco Enterprise Licensing Manager (ELM)
No Treat as a Unified CM Subscriber. Use one of the VM configurations above.
Platform Administrative Web Services Management (PAWS-M)
No Treat as a Unified CM Subscriber. Use one of the VM configurations above.


Version 8.6(x)

Click here for a Legend

Component & Capacity Point
Use with BE 6000?
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
UCS or 3rd-party Specs-based on Intel Xeon
UCS Tested Reference Configurations
UCS or 3rd-party Specs-based on Intel Xeon
S
M
L
XL
2XL
Full UC Perf. CPU
Restricted UC Perf. CPU
S
M
Full UC Perf. CPU
Restricted UC Perf. CPU
1000 users
See notes
Yes 2 4 GB 1x 80 GB 1 Yes Yes Yes Yes Yes Yes No Yes Yes Yes No
2500 users
(larger vDisk)
See notes
No 1
See notes
4 GB 1x 80 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
2500 users
(smaller vDisk)
See notes
No 1
See notes
3 GB 1x 55 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
7500 users
See notes
No 2 6 GB 2x 80 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
10,000 users
See notes
No 4 6 GB 2x 80 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No


Version 8.5(x)

Click here for a Legend

Note 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).
Component & Capacity Point
Use with BE 6000?
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
UCS or 3rd-party Specs-based on Intel Xeon
UCS Tested Reference Configurations
UCS or 3rd-party Specs-based on Intel Xeon
S
M
L
XL
2XL
Full UC Perf. CPU
Restricted UC Perf. CPU
S
M
Full UC Perf. CPU
Restricted UC Perf. CPU
1000 users
See notes
Yes 2 4 GB 1x 80 GB 1 Yes Yes Yes Yes Yes Yes No Yes Yes Yes No
2500 users
(larger vDisk)
See notes
No 1
See notes
2.25 GB 1x 80 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
7500 users
See notes
No 2 6 GB 2x 80 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No


Version 8.0(2+)

Click here for a Legend

Note 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).
Component & Capacity Point
Use with BE 6000?
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
UCS or 3rd-party Specs-based on Intel Xeon
UCS Tested Reference Configurations
UCS or 3rd-party Specs-based on Intel Xeon
S
M
L
XL
2XL
Full UC Perf. CPU
Restricted UC Perf. CPU
S
M
Full UC Perf. CPU
Restricted UC Perf. CPU
1000 users
See notes
Yes 2 4 GB 1x 80 GB 1 Yes Yes Yes Yes Yes Yes No Yes Yes Yes No
2500 users
(larger vDisk)
See notes
No 1
See notes
2.25 GB 1x 80 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No
7500 users
See notes
No 2 6 GB 2x 80 GB 1 No Yes Yes Yes Yes Yes No No Yes Yes No


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


Notes on 2500 user VM configurations

Note 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.

Note there are two configuration choices for 2500 users.

"Larger vDisk" - targeted for premise UC on UCS

  • 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


"Smaller vDisk" - targeted for hosted HCS or any storage-capacity-sensitive deployment

  • 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
    • 2.5K max phones per cluster (using DB template for max 2.5K)
    • 15K max BHCC per VM
    • 15K max BHCC per cluster
    • Your design/results may vary


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


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).

CUCM storage access is on average 93-98% 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.


Rating: 3.3/5 (7 votes cast)

Personal tools