Virtualization for Cisco Paging Server
(→Cisco Paging Server overhaul)
m (1 revision)
Revision as of 13:46, 22 May 2013
| || || |
click to download OVA file for this version
| || |
| || || || || || || || |
| || || || || || || || || || || || || |
| 1000 users |
|Yes||1||4 GB||1x 78 GB||1||Same hardware support as the "1000 user" VM configuration from Cisco Unified Communications Manager 9.1.|
|All other user sizes||No|| Same VM specs and hardware support as a Unified CM Subscriber. Use one of the VM configurations from Cisco Unified Communications Manager 9.1.
Notes on 1000 user VM configuration
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.