Unified Communications Virtualization Sizing Guidelines

From DocWiki

Revision as of 09:53, 8 December 2010 by Rpandara (Talk | contribs)
Jump to: navigation, search

Contents

Introduction

This article provides specifics and examples to aid in sizing Unified Communications applications for the UCS B-series servers.

UCS B-Series Sizing

UCS B-Series Application Requirements

The table below shows the Virtual CPU (vCPU) and memory requirements for Unified Communications applications running on the B-series blade servers under VMware ESXi 4.0. Additional information is contained in the Hardware Requirements and Templates sections. Note that there can be no over-subscription of either vCPU or memory on a Blade server; i.e. the number of vCPUs and amount of memory required by a combination of applications on a blade cannot exceed that blade's resources. Each application also requires a single virtual NIC.

Virtual machine templates are recommended and available for most Unified Communications application. These templates have pre-partitioned disks that are aligned on 64k boundaries.

Application Number Of CPUs Memory OVA Template Notes
Unified Communications Manager 2 vCPU 6 GB 7500 User none
Cisco Unity Connection 1 vCPU 2 GB 500 Users Cisco Unity Connection 8.0(3) minimum. Requires an idle/unused vCPU per server to remain available for ESXi scheduler.
2 vCPU 4 GB 5000 Users Cisco Unity Connection 8.0(2) minimum. Requires an idle/unused vCPU per server to remain available for ESXi scheduler.
4 vCPU 4 GB 10,000 User Cisco Unity Connection 8.0(2) minimum. Requires an idle/unused vCPU per server to remain available for ESXi scheduler.
7 vCPU 8 GB 20,000 User Cisco Unity Connection 8.0(3) minimum. Requires an idle/unused vCPU per server to remain available for ESXi scheduler.
Cisco Unity 4 vCPU 4 GB 15,000 User (refer to note) Cisco Unity virtual machines have a dedicated one-to-one mapping of physical CPU core to vCPU and requires CPU affinity. Downloadable templates are not available for Cisco Unity. For configuration information refer to Design Guide for Cisco Unity Virtualization.
2 vCPU 4 GB 5000 User (refer to note) Cisco Unity virtual machines have a dedicated one-to-one mapping of physical CPU core to vCPU and requires CPU affinity. Downloadable templates are not available for Cisco Unity. For configuration information refer to Design Guide for Cisco Unity Virtualization.
Cisco Unified Presence 2 vCPU 4 GB 2500 Users Adding 1 GB memory can help the virtual machines performance if experiencing performance issues. Resource reservation is highly recommended if maximum number of users is configured. Set kernel timer frequency divider to 10 if performance is critical, or seeing performance issues.
4 vCPU 4 GB 5000 Users Adding 1 GB memory can help the virtual machines performance if experiencing performance issues. Resource reservation is highly recommended if maximum number of users is configured. Set kernel timer frequency divider to 10 if performance is critical, or seeing performance issues.
Unified Contact Center Express/IPIVR 2 vCPU 4 GB 300 Agent none
Unified Contact Center Enterprise Multiple templates and configurations exist for Unified Contact Center Enterprise based on system component. Refer to Unified CCE Component Capacities and VM Configuration Requirements for full details.
Unified Intelligence Center Refer to the following link for full details Unified IC Component Capacities and VM Configuration Requirements.

UCS B-Series Co-Residence Requirements

Co-residency is limited to applications that support the server model, generation and configuration in use. See the supported applications page for a list of which applications and versions are supported on each server.

Cisco Unified Communications IP telephony applications can be co-resident on a B-series blade server in any combination that does not oversubscribe hardware. For example, Cisco Unified Communications Manager, Cisco Unity Connection, Cisco Presence Server, Cisco Unified Intelligence Center and Cisco Contact Center Express can co-reside together on the same B-series blade server as long as there is no oversubscription of either CPU cores or RAM.

At this time, if a Cisco Unity or Cisco Unity Connection virtual machine is loaded and running, an idle/unused CPU core (vCPU) must remain available for VMware ESXi. This allows the ESXi scheduler to properly schedule and allow for predictable real-time audio streaming which voice messaging depends on.

Cisco Unity can co-reside with other Cisco Unified Communication applications but does require CPU affinity which may not be desirable for that application to use.

At this time there is no support for co-residency with non-Unified Communications Cisco applications, nor with third-party applications.

UCS B-Series Redundancy and Failover

Redundant model and failover concepts remain the same for Cisco Unified Communications when running on VMware ESXi 4.0 and UCS B-Series blade servers. Care and caution when distributing Cisco Unified Communications so that primary and backup are not on the same blade server or an active/active failover pair on the same blade server.

SAN Sizing and IOPS

(under construction) IOPS

UCS C-Series Sizing

UCS C-Series Application Requirements

The table below shows the CPU and memory requirements for Unified Communications applications running on the C-Series servers under VMware ESXi 4.0. Additional information is contained in the Hardware Requirements and Templates sections.

Virtual machine templates are available for most Unified Communications application. These templates have pre-partitioned disks that are aligned on 64k boundaries.

Application Number Of CPUs Memory OVA Template Notes
Unified Communications Manager 2 vCPU 6 GB 7500 User none
Cisco Unity Connection 1 vCPU 2 GB 500 Users Cisco Unity Connection 8.0(3) minimum. Requires an idle/unused vCPU per server to remain available for ESXi scheduler.
2 vCPU 4 GB 5000 Users Cisco Unity Connection 8.0(2) minimum. Requires an idle/unused vCPU per server to remain available for ESXi scheduler.
4 vCPU 4 GB 10,000 User Cisco Unity Connection 8.0(2) minimum. Requires an idle/unused vCPU per server to remain available for ESXi scheduler.
7 vCPU 8 GB 20,000 User Cisco Unity Connection 8.0(3) minimum. Requires an idle/unused vCPU per server to remain available for ESXi scheduler.
Unified Contact Center Express/IPIVR 2 vCPU 4 GB 300 Agent none


UCS C-Series Co-Residence Requirements

Note: the UCS C210 M1 Reference Configuration 1 does not support co-residency. Co-residency is only supported on Reference Configurations 2 and 3. Reference Configuration 1 is not field-upgradeable to Reference Configuration 2.

Co-residency is limited to applications that support the server model, generation and configuration in use. See the supported applications page for a list of which applications and versions are supported on each server.

Supported Cisco Unified Communications IP telephony applications can be co-resident on C210 M1 Reference Configuration 2 and Reference Configuration 3, in any combination that does not oversubscribe hardware. For example, multiple instances of Cisco Unified Communications Manager and Cisco Unity Connection can co-reside together on the same server as long as there is no oversubscription of either CPU cores or RAM.

At this time, if a Cisco Unity Connection virtual machine is loaded and running, an idle/unused CPU core (vCPU) must remain available for VMware ESXi. This allows the ESXi scheduler to properly schedule and allow for predictable real-time audio streaming which Cisco Unity Connection voice messaging depends on.

At this time there is no support for co-residency with non-Unified Communications Cisco applications, nor with third-party applications.

UCS C-Series Redundancy and Failover

Redundant model and failover concepts remain the same for Cisco Unified Communications when running on VMware ESXi 4.0 and UCS C-series servers. One C-Series server is equivalent to one MCS.

SAN Sizing and IOPS

Reference Configuration 3 requires installation of VMware to local disks (DAS), and installation of Unified Communications applications on the SAN. Refer to the IOPS data to determine appropriate SAN sizing. The SAN support policy for Reference Configuration 3 is identical to the SAN support policy of UC on UCS B-series.

Sizing Examples

Note: For sizing and co-residency examples for Cisco Unified Contact Center Enterprise, go here.

The figure below illustrates a sample system configuration based on the guidelines in this article and in the topics listed under Related Documentation. This sample has the following characteristics:

  • General Characteristics
  • Eight blades in system with two to four Unified Communications applications per blade
  • Blade 7 used for non-Cisco applications and services
  • Blade 8 reserved as a spare to be used in case of blade failure
  • Two cores on Blade 6 are unused and available for future expansion or as a spare
  • Unified Communications Manager
  • Up to 7500 users
  • One Publisher, five Subscribers
  • DHCP, TFTP, MOH, and DNS
  • 7500 User
  • Unity Connection
  • Up to 10,000 users
  • Two Servers in Active/Active configuration
  • 10,000 User
  • Unified Presence
  • Up to 10,000 users
  • Two servers supporting 5000 users each
  • 5000 Users
  • Unified Intelligence Center
  • Up to 1200 users
  • One Publisher, Seven Subscribers , database replicated among all 8 nodes
  • 200 Users
  • Unified Contact Center Express
  • Up to 300 agents
  • Two servers suping 300 agents each; active/standby redundancy
  • 300 Agent
  • Nexus 1000v
  • Virtual machine access switch
  • Refer to cisco.com/go/nexus1000v for detailed information on Cisco Nexus 1000V Series Switches

Note one CPU has been reserved on Blade 1 and Blade 3 to satisfy the Unity Connection resource requirement.


UCS Blade Layout.JPG

Sizing and Ordering Tools

The suite of tools listed below can assist you with the sizing, configuring and quoting of Cisco Unified Communications solutions on the Unified Computing System.

Cisco Solution Expert

Cisco Solution Expert assists Cisco field and Cisco Unified Communications specialized channel partners in designing and quoting UC on UCS solutions using the Cisco Unified Workspace Licensing or the traditional design model. Solution Expert delivers a Bill of Materials for the Unified Communications software and the UCS B-series Blade Servers and VMWare ordered as Collaboration SKUS.

Netformx DesignXpert

Netformx DesignXpert is a third party application used to design and quote the Cisco Unified Computing System B-series. DesignXpert has two advisor modules that can be used to quote a Unified Communications solution with the Unified Computing System:

  • UC Advisor – a designing and quoting solution used to quote Unified Communications software and the UCS B-series Blade Servers and VMWare ordered as Collaboration SKUs. Other UCS B-series components must be configured via UCS Advisor below.
  • UCS Advisor - a designing and quoting solution for all UCS B-series components ordered as Data Center SKUs, including Blade Servers, UCS 5100 Blade Server Chassis, UCS 2100 Fabric Extender and UCS 6100 Fabric Interconnect Switch.

Cisco Unified Communications Sizing Tool

Cisco Unified Communications Sizing Tool delivers hardware sizing for complex Enterprise Unified Communications solutions, including Cisco Unified Contact Center Enterprise. The Sizing Tool delivers the virtual machine requirements for Unified Communications applications on the Unified Computing System platform.

Cisco Configuration Tool

Cisco Configuration Tool is part of the suite of Internet Commerce Tools for managing online ordering of Cisco products. It enables you to configure products and view lead times and prices for each selection. The Cisco Configuration Tool, also known as the Dynamic Configuration Tool, is used to configure the Unified Communications products and the B series SKU and VMWare ordered as Collaboration SKUs.

Ordering Guides

Ordering Guides for Unified Communications System 8.0(2) are available for Cisco sales, partners, and customers.



Back to Unified Communications Virtualization main page

Rating: 4.3/5 (32 votes cast)

Personal tools