DocWiki - User contributions [en]

File:UCVirtualSizingEx4.jpg

2010-12-16T19:41:10Z

Wamaxwel:

File:UCVirtualSizingEx3.jpg

2010-12-16T19:41:01Z

Wamaxwel:

File:UCVirtualSizingEx2.jpg

2010-12-16T19:40:49Z

Wamaxwel:

2010-12-15T21:54:28Z

Wamaxwel: 1 revision

{{note| Product documentation may reflect varying names that appear in the application user interfaces and application programming interfaces of this product. These names may include Cisco Unified Media Capture Platform (Unified MCP), Media Capture Platform (MCP/mcp), or Open Recording Architecture (ORA/ora).}}

= Updates to this Page =
The following is a list of significant updates to this page:

{| class="wikitable"
|-
! Date
! Update
|-
| November 2010
| Virtualization of Unified MCP on UCS C Series hardware.
|}

= Information for Partners about Unified MCP Deployments =
See [[High-level Checklist for Design and Implementation]].

= VM-Specific Unified MCP Hardware Requirements =
See [[Unified Computing System Hardware]].

Before you install the Unified MCP software in any server, you must address the following requirements:
* Only Unified MCP must be running on this VM host. No other product can be installed on this server.
* If you are performing a fresh install of Unified MCP in any deployment, be sure to verify that the virtual machine is also fresh (no previously-installed OS is present in the VM).

= Unified MCP-Specific Details for VMware Requirements =
See [[Unified Communications VMWare Requirements]]

Cisco UCS C-Series Servers, Unified MCP ISO, ESXi 4.0 must be installed prior to the Unified MCP installation.

== Unified MCP, Release 8.5(1) ==
All Unified MCP servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS).
{{note| If you are using ESXi 4.1, be sure to disable Large Receive Offload (LRO) on the ESXi 4.1 host.}}

To disable LRO, follow this procedure:
# Log into the ESXi host or its vCenter with vSphere Client.
# Select the host > Configuration > Advanced Settings.
# Select Net and scroll down slightly more than half way.
# Set the following parameters from 1 to 0:
#* Net.VmxnetSwLROSL
#* Net.Vmxnet3SwLRO
#* Net.Vmxnet3HwLRO
#* Net.Vmxnet2SwLRO
#* Net.Vmxnet2HwLRO
# Reboot the ESXi host to activate these changes.

= VM-Specific Unified MCP Software Requirements =
See [[Unified Communications VMWare Requirements]].

The following software requirements apply specifically to Unified MCP:

* For other third-party software requirements and for a list of approved UCS servers, see the server requirements and version compatibility with Unified CM sections in the ''Hardware & System Software Specification (Bill of Materials) for Cisco Unified Contact Center Enterprise Guide'' available at http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_user_guide_list.html.

= VM-Specific Unified MCP Hardware Requirements =
See [[Unified Computing System Hardware]].

Unified MCP only supports UCS C210 M1 and M2 servers for Release 8.5(1).

= Unified MCP-Specific Information for OVA Templates =
See [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]].

[http://www.cisco.com/en/US/products/ps11389/tsd_products_support_series_home.html| Cisco MediaSense OVA Templates]

= Unified MCP-Specific Information for Sizing Guidelines =
The VM-specific sizing informaton required for Unified MCP is additional virtual disks for media storage. See the SRND for Cisco MediaSense for further information.

[http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/mediasense/85/srnd/mssrnd85.pdf| SRND for Cisco MediaSense, Release 8.5(1)]

-----

Back to [[Unified Communications Virtualization]]

[[Category:Cisco MediaSense]]

License MAC Generation

2010-12-15T21:54:28Z

Wamaxwel: 1 revision

Several Cisco Unified Communications applications use a different license enforcement mechanism when on VMware vs. when on non-virtualized servers such as MCS 7800. These applications enforce licensing via a software-generated "License MAC" instead of the "burned-in" MAC address on the physical server's NIC.

For applications that require a License MAC, it can be created using the [http://www.cisco.com/web/cuc_afg/index.html Answer File Generator] prior to application installation in the Virtual Machine. This will output both the License MAC value as well as the answer file for unattended installation. This method is recommended as the most effective way to obtain the license MAC.

A License MAC is in the same format as a physical MAC address, i.e. a 12 digit hexadecimal value, but it is generated by hashing the following user-configured parameters:
:* Time zone
:* NTP server 1 (or “none”)
:* NIC speed (or “auto”)
:* Hostname
:* IP Address (or “dhcp”)
:* IP Mask (or “dhcp”)
:* Gateway Address (or “dhcp”)
:* Primary DNS (or “dhcp”)
:* SMTP server (or “none”)
:* Certificate Information (Organization, Unit, Location, State, Country)

run the 'show status' CLI command after installation.

To view the current value of a License MAC for applications that require it, after installation select Show > System in the Cisco Unified Operating System Administration web page or run the CLI command "show status".

[[Category:Unified Communications Virtualization Upgrade, Migration, and Best Practices]]

Unified Communications Virtualization Downloads (including OVA/OVF Templates)

2010-12-15T21:54:28Z

Wamaxwel: 1 revision

== Supported Virtual Machine OVA Templates ==

A virtual machine template defines the configuration of the virtual machine's virtual hardware. Open Virtualization Format (OVF) is an open standard for describing a virtual machine template, and Open Virtualization Archive (OVA) is an open standard to package and distribute these templates. Files in OVA format have an extension of ".ova".

Cisco Unified Communications applications must use one of the supported virtual machine templates in the table below. For most applications, a preconfigured OVA file is provided by Cisco and must be used. Otherwise the customer must manually build OVA files that meet the indicated requirements.

'''Application co-residency''' is dependent on which mix of OVA files will be deployed on the same server, as well as the server's compute/storage/network hardware configuration.

When a '''static MAC address''' is required, choose a complex address to prevent accidental licensing overlap between different application instances in different VMs. An example of a complex MAC address is 00:50:56:01:3B:9F. A less complex MAC address is 00:50:56:11:11:11 (because of the "all-ones") and is more likely to conflict with other VMs.

{| border="1"

|-
|+ '''Supported Virtual Machines OVA Templates'''
|- style="background:#E5E4E2"
! Application, OVA Capacity and Notes+Download Link !! vCPU Cores !! vRAM / Memory !! vDisk !! vNIC !! Notes !!

|-
! .
| . || . || . || .|| .
|-

|-
|- style="background:#E5E4E2"
! Unified Communications Manager
| || || || ||
|-

|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283423434&flowid=21301&softwareid=283088407&release=1.1%281%29&rellifecycle=&relind=AVAILABLE&reltype=latest 1000 users (C200 only)]
| 2 (600 MHz reserved) || 4 GB (4 GB reserved) ||
1x 80 GB

|| 1 (with static MAC address) || Requires License MAC ([[License MAC Generation|click here for details]]). Use on C200 only.
|-

|-
! [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&isPlatform=Y&mdfid=282827095&sftType=Unified+Communications+Manager+Virtual+Machine+Templates&treeName=Voice+and+Unified+Communications&modelName=Cisco+Unified+Communications+Manager+Version+8.0&mdfLevel=Software%20Version/Option&treeMdfId=278875240&modifmdfid=null&imname=&hybrid=Y&imst=N 2500 users]
| 1 (600 MHz reserved) || 2.25 GB (2.304 GB reserved) ||
1x 80 GB

|| 1 (with static MAC address) || Requires License MAC ([[License MAC Generation|click here for details]]). Use on B200 and C210 only.
|-

|-
! [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&isPlatform=Y&mdfid=282827095&sftType=Unified+Communications+Manager+Virtual+Machine+Templates&treeName=Voice+and+Unified+Communications&modelName=Cisco+Unified+Communications+Manager+Version+8.0&mdfLevel=Software%20Version/Option&treeMdfId=278875240&modifmdfid=null&imname=&hybrid=Y&imst=N 7500 users]
| 2 || 6 GB ||
2x 80 GB
:* vDisk 1 = Operating System + app binaries
:* vDisk 2 = Logs

|| 1 (with static MAC address) || Requires License MAC ([[License MAC Generation|click here for details]]). Use on B200 and C210 only.
|-

|-
|- style="background:#E5E4E2"
! Cisco Emergency Responder
| || || || ||
|-

|-
! 12,000 users [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&isPlatform=Y&mdfid=282827095&sftType=Unified+Communications+Manager+Virtual+Machine+Templates&treeName=Voice+and+Unified+Communications&modelName=Cisco+Unified+Communications+Manager+Version+8.0&mdfLevel=Software%20Version/Option&treeMdfId=278875240&modifmdfid=null&imname=&hybrid=Y&imst=N (use CUCM "1000 users")]
| See CUCM "1000 users" || See CUCM "1000 users" || See CUCM "1000 users" || See CUCM "1000 users" ||

Requires License MAC ([[License MAC Generation|click here for details]])
Limits:
:* 12,000 IP phones
:* 2,500 analog phones
:* 1,200 roaming phones (per Emergency Responder cluster)
:* 500 LAN switches
:* 30,000 switch ports
:* 3,000 ERLs

|-

|-
! 20,000 users [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&isPlatform=Y&mdfid=282827095&sftType=Unified+Communications+Manager+Virtual+Machine+Templates&treeName=Voice+and+Unified+Communications&modelName=Cisco+Unified+Communications+Manager+Version+8.0&mdfLevel=Software%20Version/Option&treeMdfId=278875240&modifmdfid=null&imname=&hybrid=Y&imst=N (use CUCM "2500 users")]
| See CUCM "2500 users" || See CUCM "2500 users" || See CUCM "2500 users" || See CUCM "2500 users" ||
Requires License MAC ([[License MAC Generation|click here for details]])
Limits:
:* 20,000 IP phones
:* 5,000 analog phones
:* 2,000 roaming phones (per Emergency Responder cluster)
:* 1,000 LAN switches
:* 60,000 switch ports
:* 7,500 ERLs

|-

|-
! 30,000 users [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&isPlatform=Y&mdfid=282827095&sftType=Unified+Communications+Manager+Virtual+Machine+Templates&treeName=Voice+and+Unified+Communications&modelName=Cisco+Unified+Communications+Manager+Version+8.0&mdfLevel=Software%20Version/Option&treeMdfId=278875240&modifmdfid=null&imname=&hybrid=Y&imst=N (use CUCM "7500 users")]
| See CUCM "7500 users" || See CUCM "7500 users" ||
See CUCM "7500 users"

|| See CUCM "7500 users" ||
Requires License MAC ([[License MAC Generation|click here for details]])
Limits:
:* 30,000 IP phones
:* 10,000 analog phones
:* 3,000 roaming phones (per Emergency Responder cluster)
:* 2,000 LAN switches
:* 120,000 switch ports
:* 10,000 ERLs

|-

|-
|- style="background:#E5E4E2"
! Session Manager Edition
| || || || ||
|-

|-
! [http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&isPlatform=Y&mdfid=282827095&sftType=Unified+Communications+Manager+Virtual+Machine+Templates&treeName=Voice+and+Unified+Communications&modelName=Cisco+Unified+Communications+Manager+Version+8.0&mdfLevel=Software%20Version/Option&treeMdfId=278875240&modifmdfid=null&imname=&hybrid=Y&imst=N Use CUCM "7500 users"]

| See CUCM "7500 users" || See CUCM "7500 users" || See CUCM "7500 users" || See CUCM "7500 users" || Requires License MAC ([[License MAC Generation|click here for details]])
|-

|-
|- style="background:#E5E4E2"
! Unified Attendant Consoles
| || || || ||
|-

|-
! OVA for CUxAC
| 1 || 2 GB || 1x 80GB|| 1 (with static MAC address)|| Note: Cisco does not provide preconfigured OVA files for CUxAC. Please build manually using these requirements. CUxAC requires a VM to meet or exceed minimum physical server specs described [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/data_sheet_c78-520987.html on the CUxAC datasheet]
|-

|-
|- style="background:#E5E4E2"
! Cisco Unity Connection
| || || || ||
|-

|-
! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=OVA&mdfid=283062758&sftType=Unity+Connection+Software&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unity+Connection+Virtualization&treeMdfId=278875240&treeName=Voice+and+Unified+Communications&modifmdfid=null&imname=&hybrid=null&imst=null&lr=Y 500 users]
| 1 || 2 GB || 1x 160 GB || 1 (with static MAC address) ||
Requires License MAC ([[License MAC Generation|click here for details]])

Limits for Standalone Configuration:
:* 16 ports G.711 or G.729a (combined TUI, VUI, or TTS)
:* 4 ports iLBC or G.722

Limits for Active/Active Cluster Configuration:
:* 32 ports G.711 or G.729a (combined TUI, VUI, or TTS)
:* 8 ports iLBC or G.722

|-

|-
! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=OVA&mdfid=283062758&sftType=Unity+Connection+Software&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unity+Connection+Virtualization&treeMdfId=278875240&treeName=Voice+and+Unified+Communications&modifmdfid=null&imname=&hybrid=null&imst=null&lr=Y 1000 users]
| 1 || 4 GB || 1x 160 GB || 1 (with static MAC address) ||
Requires License MAC ([[License MAC Generation|click here for details]])

Limits for Standalone Configuration:
:* 24 ports G.711 or G.729a (combined TUI, VUI, or TTS)
:* 6 ports iLBC or G.722

Limits for Active/Active Cluster Configuration:
:* 48 ports G.711 or G.729a (combined TUI, VUI, or TTS)
:* 12 ports iLBC or G.722

|-

|-
! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=OVA&mdfid=283062758&sftType=Unity+Connection+Software&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unity+Connection+Virtualization&treeMdfId=278875240&treeName=Voice+and+Unified+Communications&modifmdfid=null&imname=&hybrid=null&imst=null&lr=Y 5000 users]
| 2 || 4 GB || 1x 200 GB || 1 (with static MAC address) ||
Requires License MAC ([[License MAC Generation|click here for details]])

Limits for Standalone Configuration:
:* 100 ports G.711 or G.729a (combined TUI, VUI, or TTS)
:* 25 ports iLBC or G.722

Limits for Active/Active Cluster Configuration:
:* 200 ports G.711 or G.729a (combined TUI, VUI, or TTS)
:* 50 ports iLBC or G.722

|-

|-
! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=OVA&mdfid=283062758&sftType=Unity+Connection+Software&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unity+Connection+Virtualization&treeMdfId=278875240&treeName=Voice+and+Unified+Communications&modifmdfid=null&imname=&hybrid=null&imst=null&lr=Y 10,000 users]
| 4 || 4 GB || 2x 146 GB || 1 (with static MAC address) ||
Requires License MAC ([[License MAC Generation|click here for details]])

Limits for Standalone Configuration:
:* 150 ports G.711 or G.729a (combined TUI, VUI, or TTS)
:* 35 ports iLBC or G.722

Limits for Active/Active Cluster Configuration:
:* 300 ports G.711 or G.729a (combined TUI, VUI, or TTS)
:* 70 ports iLBC or G.722

|-

|-
! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=OVA&mdfid=283062758&sftType=Unity+Connection+Software&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unity+Connection+Virtualization&treeMdfId=278875240&treeName=Voice+and+Unified+Communications&modifmdfid=null&imname=&hybrid=null&imst=null&lr=Y 20,000 users]
| 7 || 8 GB || 2x 300 GB || 1 (with static MAC address) ||
Require ESXi Enterprise Plus Licensing since it uses over 4 vCPUs for the Virtual Machine.

Requires License MAC ([[License MAC Generation|click here for details]])

Limits for Standalone Configuration:
:* 250 ports G.711 or G.729a (combined TUI, VUI, or TTS)
:* 60 ports iLBC or G.722

Limits for Active/Active Cluster Configuration:
:* 500 ports G.711 or G.729a (combined TUI, VUI, or TTS)
:* 120 ports iLBC or G.722

|-

|-
|- style="background:#E5E4E2"
! Cisco Unity
| || || || ||
|-

|-
! 5000 users
| 2 (requires VMware CPU Affinity) || 4 GB ||
4x 24 GB
:* vDisk 1 = Operating system
:* vDisk 2 = Cisco Unity binaries
:* vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:* vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

|| 1 (with static MAC address) ||
* Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
* Limits:
:* 48 ports
:* 36 text-to-speech ports
|-

|-
! 15,000 users
| 4 (requires VMware CPU Affinity) || 4 GB ||
4x 24 GB
:* vDisk 1 = Operating system
:* vDisk 2 = Cisco Unity binaries
:* vDisk 3 = Cisco Unity logs, SQL Server transaction logs
:* vDisk 4 = Cisco Unity Message Repository (UMR), SQL Server database

|| 1 (with static MAC address) ||
* Cisco does not provide preconfigured OVA files for Cisco Unity. Please build manually using these requirements and the configuration information in [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html the Design Guide for Cisco Unity Virtualization].
* Limits:
:* 144 ports
:* 36 text-to-speech ports

|-

|-
|- style="background:#E5E4E2"
! Cisco Unified Presence
| || || || ||
|-

|-
! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0(1)&mdfid=282892411&sftType=Unified+Presence+Server+(CUP)+Updates&optPlat=&nodecount=8&edesignator=null&modelName=Cisco+Unified+Presence+Version+8.0&treeMdfId=278875240&modifmdfid=null&imname=&treeName=Voice+and+Unified+Communications&hybrid=Y&imst=N 1000 users]
| 1 (800 MHz reserved) || 2 GB || 1x 80 GB || 1 (with static MAC address) || Requires License MAC ([[License MAC Generation|click here for details]])
|-

|-
! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0(1)&mdfid=282892411&sftType=Unified+Presence+Server+(CUP)+Updates&optPlat=&nodecount=8&edesignator=null&modelName=Cisco+Unified+Presence+Version+8.0&treeMdfId=278875240&modifmdfid=null&imname=&treeName=Voice+and+Unified+Communications&hybrid=Y&imst=N 2500 users]
| 2 || 4 GB || 1x 80 GB || 1 (with static MAC address) || Requires License MAC ([[License MAC Generation|click here for details]]). Use when migrating from MCS 7825 with disks smaller than 80 GB.
|-

|-
! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0(1)&mdfid=282892411&sftType=Unified+Presence+Server+(CUP)+Updates&optPlat=&nodecount=8&edesignator=null&modelName=Cisco+Unified+Presence+Version+8.0&treeMdfId=278875240&modifmdfid=null&imname=&treeName=Voice+and+Unified+Communications&hybrid=Y&imst=N 5000 users]
| 4 || 4 GB || 2x 80 GB || 1 (with static MAC address) || Requires License MAC ([[License MAC Generation|click here for details]]). Use when migrating from MCS 7845.
|-

|-
|- style="background:#E5E4E2"
! [[Virtualization for Unified CCX|Cisco Unified Contact Center Express]]
| || || || ||
|-

|-
! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0%282%29&mdfid=270569179&sftType=Cisco+Customer+Response+Solution+Software+Releases&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unified+Contact+Center+Express&treeMdfId=278875240&treeName=Voice+and+Unified+Communications&modifmdfid=null&imname=&hybrid=Y&imst=N&lr=Y 100 agents] (Release 8.5(1) only)
| 2 || 4 GB || 1x 146 GB
2 vCPU
2 GB RAM
1 vNIC with static MAC address
1 vDisk: vDisk 1 = 146 GB
|| 1 (with static MAC address) || Requires License MAC ([[License MAC Generation|click here for details]])
'''Note:''' Though the configuration for “100 agents” and “300 agents” templates are similar in Unified CCX 8.5(1), an updated 100 agent template that consumes less resources will be available in an upcoming Unified CCX release.

|-

|-
! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0%282%29&mdfid=270569179&sftType=Cisco+Customer+Response+Solution+Software+Releases&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unified+Contact+Center+Express&treeMdfId=278875240&treeName=Voice+and+Unified+Communications&modifmdfid=null&imname=&hybrid=Y&imst=N&lr=Y 300 agents] (Release 8.0(2) and Release 8.5(1))
| 2 || 4 GB ||
2x 146 GB
:* vDisk 1 = Operating System and Unified CCX binaries
:* vDisk 2 = Unified CCX logs
|| 1 (with static MAC address) || Requires License MAC ([[License MAC Generation|click here for details]])
|-

|-
! [http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=8.0%282%29&mdfid=270569179&sftType=Cisco+Customer+Response+Solution+Software+Releases&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unified+Contact+Center+Express&treeMdfId=278875240&treeName=Voice+and+Unified+Communications&modifmdfid=null&imname=&hybrid=Y&imst=N&lr=Y 400 agents] (Release 8.5(1) only)
| 4 || 8 GB ||
2x 146 GB
:* vDisk 1 = Operating System and CUCCX binaries
:* vDisk 2 = UCCX logs
|| 1 (with static MAC address) || Requires License MAC ([[License MAC Generation|click here for details]])
|-

|-
! Unified CCX WFM
| 2 || 2 GB ||
2x 146 GB
:* vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO WFM binaries, SQL Server, SQL Server Data files
:* vDisk 2 = Optional - can be used to hold SQL Server Data files
|| 1 (with static MAC address) || Requires License MAC ([[License MAC Generation|click here for details]])

|-
! Unified CCX WFO QM Configuration (CR/QM/AQM)
| 2 || 2 GB ||
2x 146 GB
:* vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM binaries, SQL Server, SQL Server Data files
:* vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recordings (Size may vary depending upon usage )
|| 2 (with static MAC address) ||

Requires License MAC ([[License MAC Generation|click here for details]])
Capacities
:* 300 named users
:* 150 concurrent users
:* 150 voice recordings, for all recording types (desktop, server and network)
:* 150 voice+screen recordings, for all recording types (desktop, server and network)

|-
|- style="background:#E5E4E2"
! UC Management Suite (OM, SM, SSM, PM)
| || || || ||
|-

|-
! Small ("1S")
| 1 || 2 GB || 1x 30 GB || 1 (with static MAC address) ||
|-

|-
! HCS Small ("1")
| 1 || 4 GB || 1x 60 GB || 1 (with static MAC address) ||
|-

|-
! Medium 1 ("2")
| 2 || 4 GB || 1x 72 GB || 1 (with static MAC address) ||
|-

|-
! Medium 2 ("2L")
| 2 || 8 GB || 1x 72 GB || 1 (with static MAC address) ||
|-

|-
! Large 1 ("4")
| 4 || 4 GB || 2x 60 GB || 1 (with static MAC address) ||
|-

|-
! Large 2 ("4L")
| 4 || 8 GB || 2x 60 GB || 1 (with static MAC address) ||
|-

|-
! CUCMS Co-resident ("8")
| 8 || 16 GB || 1x 320 GB || 1 (with static MAC address) ||
|-

|-
|- style="background:#E5E4E2"
! [[Unified Contact Center Enterprise]]
| || || || || See also [[Unified Contact Center Enterprise#Unified_CCE_Component_Capacities_and_VM_Configuration_Requirements|Unified CCE OVA info here]].
|-

|-
! Router (8K agents)
| 2 || 4 GB || 1x 80 GB || 2 (with static MAC addresses) ||
|-

|-
! Logger (8K agents) or Rogger (4K agents)
| 4 || 4 GB || 1x 150 GB || 2 (with static MAC addresses) ||
|-

|-
! Agent PG (450 agents) or MR PG (1K agents, 5 PIMs)
| 1 || 2 GB || 1x 80 GB || 2 (with static MAC addresses) ||
|-

|-
! Agent PG (2K agents) or MR PG (2K agents, 10 PIMs)
| 2 || 4 GB || 1x 80 GB || 2 (with static MAC addresses) ||
|-

|-
! VRU PG (1200 ports, 4 PIMs)
| 1 || 2 GB || 1x 80 GB || 2 (with static MAC addresses) ||
|-

|-
! VRU PG (9600 ports, 10 PIMs)
| 2 || 2 GB || 1x 80 GB || 2 (with static MAC addresses) ||
|-

|-
! AW (25 clients)
| 1 || 2 GB || 1x 40 GB || 1 (with static MAC addresses) ||
|-

|-
! AW-CONFIG (50 clients)
| 1 || 2 GB || 1x 40 GB || 1 (with static MAC addresses) ||
|-

|-
! AW-HDS (200 reporters)
| 4 || 4 GB || 1x 500 GB || 1 (with static MAC addresses) ||
|-

|-
! AW-HDS-DDS (200 reporters)
| 4 || 4 GB || 1x 500 GB || 1 (with static MAC addresses) ||
|-

|-
! HDS-DDS (200 reporters)
| 4 || 4 GB || 1x 500 GB || 1 (with static MAC addresses) ||
|-

|-
! Client AW (1 user)
| 1 || 2 GB || 1x 40 GB || 1 (with static MAC addresses) ||
|-

|-
! Support Tools
| 1 || 2 GB || 1x 40 GB || 1 (with static MAC addresses) ||
|-

|-
|- style="background:#E5E4E2"
! [[Unified Customer Voice Portal]]
| || || || || See also [[Unified Customer Voice Portal#Unified_CVP_Component_Capacities_and_VM_Configuration_Requirements|Unified CVP OVA info here]].
|-

|-
! Call Server/VXML Server/co-located Call Server and VXML Server
| 4 || 4 GB || 1x 146 GB || 1 (with static MAC address) ||
|-

|-
! Reporting Server (Large)
| 4 || 4 GB || 1x 72 GB and 1x 438 GB || 1 (with static MAC address) ||
|-

|-
! Operations Console
| 2 || 2 GB || 1x 20 GB || 1 (with static MAC address) ||
|-

|-
|- style="background:#E5E4E2"
! [[Virtualization for Cisco MediaSense | Cisco MediaSense ]]
| || || || ||
|-

|-
! CMS_expansion_server_v8.5_vmv7
| 7 || 8 GB || 2 x 80 GB (thick provisioning)|| 1 (with static MAC address) ||
|-

|-
! CMS_6T_main_server_v8.5_vmv7
| 7 || 8 GB || 2 X 146 GB (thick provisioning)|| 1 (with static MAC address) ||
|-

|-
! CMS_12T_main_server_v8.5_vmv7
| 7 || 8 GB || 2 X 300 GB (thick provisioning)|| 1 (with static MAC address) ||
|-

|-
|- style="background:#E5E4E2"
! [[Cisco Unified Intelligence Center]]
| || || || || See also [[Cisco Unified Intelligence Center#Unified_IC_Component_Capacities_and_VM_Configuration_Requirements|Unified IC OVA info here]].
|-

|-
! Unified IC (200 Reporting Users)
| 4 || 6 GB || 1x 150 GB || 1 (with static MAC address)|| Requires License MAC ([[License MAC Generation|click here for details]])
|-

|-
|- style="background:#E5E4E2"
! [[Support for CCMP with UCCE on UCS Hardware|Cisco Unified Contact Center Management Portal]]
| || || || || See also [[Support for CCMP with UCCE on UCS Hardware#CCMP_Component_Capacities_and_VM_Configuration_Requirements|Unified CCMP OVA info here]].
|-

|-
! Unified CCMP (1500 Agents)
| 4 || 4 GB || 1x 100 GB || 1 (with static MAC address)||
|-

|-
! Unified CCMP (Web/App Srv Only) (8000 Agents)
| 4 || 4 GB || 1x 100 GB || 1 (with static MAC address)||
|-

|-
! Unified CCMP (DB Only) (8000 Agents)
| 8 || 4 GB || 1x 250 GB || 1 (with static MAC address)||
|-
|- style="background:#E5E4E2"
! [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| || || || ||
|-

|-
! Standard Production Server
| 4 || 12 GB || 1x 146 GB and 1x 256 GB || 1 (with static MAC address)||
|-

|}

----

Back to [[Unified Communications Virtualization|Unified Communications Virtualization main page]]

Unified Communications Virtualization Sizing Guidelines

2010-12-15T21:54:28Z

Wamaxwel: 1 revision

== Introduction ==

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

== Application Co-residency Support and Server/Storage Selection ==

All [[Unified Computing System Hardware|UCS tested reference configurations]] are sized for co-residency except for C210 M1 Tested Reference Configuration #1 (which is only sized to host a single VM of 7500 user capacity). Note that the tested reference configuration for UCS C200 M2 is sized for co-residency at a lower capacity per VM than UCS B200 or C210 so only supports a subset of Virtual Machine templates.

The max number of virtual machines supported per physical server depends on the hardware selected and the quantity and resource usage of selected virtual machine OVAs.

To determine which applications may share a physical server, use the following guidelines:

* Supported co-resident applications are "UC with UC only".
** Co-residency of UC with 3rd-party application VMs - such as TFTP/SFTP/DNS/DHCP servers, Directories, Groupware, File/print, CRM, etc. - is not supported at this time. These applications may be placed on a separate physical server from UC. For UCS B-series, this can be an adjacent blade in the same chassis.
** Co-residency of UC with non-UC VMs such as Nexus 1000V not supported at this time. These applications may be placed on a separate physical server from UC. For UCS B-series, this can be an adjacent blade in the same chassis.
** The following UC apps have product-specific co-residency rules [[Unified Communications Virtualization Supported Applications|on their web page]]. Product-specific rules take precedence over the support policy on this web page.
*** [[Unified Contact Center Enterprise]]
*** [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]]
*** [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]
*** [[Unified Customer Voice Portal]]
*** [[Virtualization for Unified CCX|Unified Contact Center Express]]
*** [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
*** [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
*** [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
** Note that Cisco Unity requires CPU Affinity which may not be desirable for other applications sharing the server.
** All applications that will be co-resident [[Unified Communications Virtualization Supported Applications|must support UC on UCS]]. Note that supported versions may vary by application. so check [http://www.cisco.com/go/unified-techinfo inter-product version compatibility].
** You must use a [[Unified Computing System Hardware|server/storage/network configuration]] that is supported by [[Unified Communications Virtualization Supported Applications|all the applications/versions]] that will be co-resident. E.g. some applications/versions do not support C200, or only support M2 generations but not M1.
** Otherwise you can mix and match UC apps on the same server.
* All applications must use a [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|supported virtual machine OVA template]].
** All applications require a 1:1 mapping of VM vCPU cores to physical CPU cores. Cisco Unity VMs also require VMware CPU Affinity.
** If there is at least one live Unity Connection VM on the server, then one CPU core per physical server must be idle/unused (it is actually being used by ESXi scheduler).
** The sum of virtual machines' vCPU cores may not exceed the total physical CPU cores on the physical server (less one if hosting at least one live Unity Connection VM).
** The sum of virtual machines' vRAM (plus 2GB for VMware overhead) may not exceed the total physical memory on the physical server.
** For supported DAS deployments, the sum of virtual machines' vDisk may not exceed the physical disk space of the physical servers' logical volume(s) (based on RAID configuration).
* For UCS B200 and C210, you may otherwise mix and match applications, versions and OVAs (of any size) in any quantity as long as you do not oversubscribe any physical server resources as described above.
* For UCS C200, you must align with these rules:
** The only [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|supported virtual machine OVA templates]] are:
*** CUCM - Unified Communications Manager 1000 users
*** CUC or UCxn - Unity Connection 500 users, 1000 users and 5000 users
*** CUP - Unified Presence 1000 users
*** CUCCX - Unified Contact Center Express 100 agents
*** Other unlisted OVA templates are not supported on C200 as they are sized too big.
** If C200 is used for [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]] then you must follow its co-residency rules.
** Otherwise at this time the following co-residency scenarios are supported:
*** Four VMs: CUCM 1000 users + CUC 1000 users + CUP 1000 users + CUCCX 100 users (the scenario used by [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]] )
*** Up to four VMs: 1 to 4 CUC of various user sizes provided you don't over-subscribe any physical server resources as described previously.
*** Four VMs: 4 CUP 1000 users
*** Three VMs: 3 CUCM 1000 users
*** Three VMs: 3 CUCCX 100 users

See the Sizing Examples at the bottom of this page for examples of using these guidelines.

== Redundancy and Failover Considerations ==
Application-layer considerations (such as Unified CM Cluster over WAN or Unified CCE Remote Redundancy) are the same for virtualized (UC on UCS) or non-virtualized (MCS 7800) deployments.

However, since there is no longer a 1:1 relationship between hardware and application instances, "placement logic" must be taken into account to minimize the impact of hardware unavailability or unreachability:
* Avoid placing a primary VM and a backup VM on the same server, chassis or site
* For failover groups, avoid placing all actives on the same server, chassis or site
* Avoid placing all VMs of the same role on the same server, chassis or site

== Shared Storage Considerations ==

Note that Fibre Channel SAN is currently mandatory for UC on UCS B200, optional for UC on UCS C210 and not supported for UC on UCS C200.

To get the IOPS per virtual machine OVA and other information required to properly design SAN connectivity and array, see [[IOPS]].

For more information on supported storage arrays, see the UCS page at http://www.cisco.com/go/swonly.

== Sizing Examples ==
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
:::* [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)#Unified_Communications_Manager_7500_User_Template|7500 User]]

::* Unity Connection
:::* Up to 10,000 users
:::* Two Servers in Active/Active configuration
:::* [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)#Cisco_Unity_Connection_10.2C000_User_Template|10,000 User]]

::* Unified Intelligence Center
:::* Up to 1200 users
:::* One Publisher, Seven Subscribers , database replicated among all 8 nodes
:::* [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)#Unified_Intelligence_Center_200_User_Template|200 Users]]

::* Unified Presence
:::* Up to 10,000 users
:::* Two servers supporting 5000 users each
:::* [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)#Cisco_Unified_Presence_Server_5000_User_Template|5000 Users]]

::* Unified Contact Center Express
:::* Up to 300 agents
:::* Two servers supporting 300 agents each; active/standby redundancy
:::* [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)#Cisco_Unified_Contact_Center_300_Agent_Template|300 Agent]]

::* Nexus 1000v
:::* Virtual machine access switch
:::* Refer to [http://www.cisco.com/go/nexus1000v 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.

[[Image: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 ===
[http://www.cisco.com/go/sx| 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 ===
[http://www.cisco.com/go/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 ===
[http://tools.cisco.com/cucst 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''' (need link here)''' 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.x releases are available for Cisco sales, partners, and customers.

-----
Back to [[Unified Communications Virtualization|Unified Communications Virtualization main page]]

Virtualization for Unified CCX

2010-12-15T21:54:27Z

Wamaxwel: 1 revision

2010-12-13T20:34:57Z

Wamaxwel:

This article describes VMware requirements, feature support, and services and support contracts for virtualized Unified Communications applications.

== VMware is Mandatory for UC on UCS ==

All UC on UCS servers require use of VMware ESXi 4.0 to be supported. See the other sections on this page for specific VMware product and version support, and specific VMware feature support.

Nonvirtualized, physical, or bare-metal installations are not supported with UCS servers.

UC on UCS requires Cisco Unified Communications 8.0(2) or higher - specific applications and versions are covered at http://www.cisco.com/go/uc-virtualized.

For "legacy" virtualization support of Version 7.x applications on VMware on 3rd-party servers, see the following documents:
:* [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html Cisco Unity Virtualization Design Guide]
:* [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_7_5/user/guide/VirtualizationGde753.pdf Virtualization Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted 7.5(3)]

== Required VMware Licensing and Customer Purchase Options ==
VMware licenses software on a per-physical-CPU-socket basis (not physical CPU cores or virtual CPUs or virtual CPU cores). Each populated CPU socket per server requires a VMware license (with VMware product and version that is supported by Cisco UC).

While VMware ESXi 4.0 is mandatory for UC to run on UCS servers, customers may purchase this license from any of the following sources:

:*From Cisco, as a preset “per-server” Cisco Collaboration part number. This part number is separate from server hardware part numbers. You can use the same part number for Cisco UCS B-Series and C‑Series deployments. Note that for the Cisco UCS B-Series, you need to add this part number to a group of data center part numbers ordered through the Netformx DesignXpert ordering tool UCS Advisor. Only VMware ESXi Standard Edition is available via this option. The part number is “hard-coded” for two CPU sockets (no more, no less) and one year service subscription (no multi-year or auto-renewals).
:*From Cisco, as an option under a build-to-order “per CPU socket” data center part number for the server: Note that for the Cisco UCS B-Series, you must order this option through the Netformx DesignXpert ordering tool UCS Advisor. Only VMware Advanced, Enterprise or Enterprise Plus Editions are available via this option. One year and three year service subscription options are available.
:*From VMware directly or other 3rd-party: With this option, you can order any VMware ESXi Edition you want, as well as take advantage of any existing customer licensing arrangement with VMware (such as a site or enterprise license).
:*When running Virtual machines with more than 4 vCPUs, VMWare ESXi Enterprise Plus license is required by VMWare.

For part number and SKU examples, see Table 1 of the UC on UCS page at www.cisco.com/go/swonly . Cisco employees and Channel Partners may also consult the UC on UCS chapter of the Cisco User Connect Licensing ordering guide on Cisco Partner Central.

Note: in all cases, the customer is required to have a valid service contract with VMware to be supported (see [[#Services and Support Contracts for VMware are Required|Services and Support Contracts for VMware are Required]])

== Hypervisor Support for Virtualized UC (Vendors, Products, Versions, Editions) ==

At this time, the only hypervisor vendor supported for virtualized UC is VMware.

VMware vSphere ESXi 4.0 is required for UC on UCS.
* VMware ESX, regardless of version, is not supported for servers hosting Cisco Unified Communications. This is due to technical reasons and [http://blogs.vmware.com/vsphere/2010/07/esx-41-is-the-last-esx-what-do-i-do-now.html VMware’s direction to transition from ESX to ESXi]. Note a VMware ESX cluster can contain VMware ESXi servers running Cisco Unified Communications.
* Versions of VMware ESXi prior to 4.0 are not supported due to technical reasons. Maintenance and patch versions and updates on 4.0 (such as 4.0 Update 1 or "4.0U1") are supported at the time of release from VMware. At this time ESXi 4.1 is only supported for CUCMS. Future ESXi minor and major releases (such as hypothetically 4.2 or 5.0) are not supported for Cisco Unified Communications until explicitly indicated on this site.

VMware ESXi is sold in several editions with different levels of feature support. A comparison of VMware ESXi 4.0 editions is available at https://www.vmware.com/products/vsphere/buy/editions_comparison.html and in the “A La Carte Features” chapter of https://www.vmware.com/files/pdf/vsphere_pricing.pdf.

[http://www.vmware.com/products/vsphere-hypervisor/ VMware vSphere Hypervisor] (formerly named VMware ESXi Single Server Edition or “free ESXi”) is the minimum edition required for most software to install, but an edition that supports robust, multihost management via VMware vCenter - Standard, Advanced, Enterprise, or Enterprise Plus - is strongly recommended. Enterprise Plus license is mandatory is required when installing virtual machines that use more than 4 vCPUs, e.g. is the 20,000 user Unity Connection overlay.

Also note that while any Edition may be used, Cisco Unified Communications may not yet support all the features in the desired Edition (such as vMotion). See [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]].

Any virtualized deployment that does not align with the above rules (even non-production labs) is not supported by Cisco TAC.

== Support of Cisco VN-Link and Cisco Nexus 1000V ==
Note that Cisco Unified Contact Center Enterprise does NOT support this – see [[UCS Network Configuration for UCCE|UCS Network Configuration for Unified CCE]].

Unless otherwise indicated above, Cisco VN-Link and Cisco Nexus 1000V are supported by UC applications that support the VMware vNetwork Distributed Switch (see [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]]).

Cisco VN-Link, Cisco Nexus® 1000V and VMware vNetwork Distributed Switch all require VMware ESXi Enterprise Plus Edition (see [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]]). Other editions do not support these capabilities.

For UC on UCS B-series, Cisco UCS 6100 does not currently support Layer 3 to Layer 2 COS markings. Additionally, the UC applications and operating systems cannot set the Layer 2 COS markings. Use of Cisco Nexus® 1000V is therefore strongly recommended as this is the only way to manage traffic congestion through the current UCS 6100. Please recall that traffic congestion risk will vary and is dependent on many factors such as UC vs. non-UC virtual machine count and their traffic characteristics across all blades, chassis and fabric extenders connected to the same UCS 6100.

For UC on UCS C-series, Cisco Nexus® 1000V is recommended but not mandatory as there is no intermediate UCS 6100 to design around.

For more information on Cisco VN-Link and Cisco Nexus 1000V, see http://www.cisco.com/en/US/netsol/ns894/index.html and http://www.cisco.com/en/US/products/ps9902/index.html.

== VMware Infrastructure Feature Support ==

'''NOTE: ''' VMware Infrastructure feature support for Cisco Unified Contact Center Enterprise varies by component - this section will give a summary support position, but for individual components see [[Unified Contact Center Enterprise|Support for Virtualization on the ESXi/UCS Platform]].

VMware vSphere and vCenter include a number of innovative features such as vMotion that are not available with traditional physical hardware installations. Not all of these features lend themselves to real-time streaming media applications such as Cisco Unified Communications. The table below lists VMware features and their current support status for use with Cisco Unified Communications application virtual machines.

As Cisco Unified Communications adds support for additional VMware features, this site will be updated as applicable.
For an authoritative description of each feature, see VMware collateral at http://www.vmware.com/products/vsphere/buy/editions_comparison.html. Note that virtualized UC usually only supports a subset of available VMware features as described in the table below. Feature support may vary by UC application, and features are usually supported only with conditions or caveats due to the real-time nature of UC.

Legend:
:* C = Supported with '''C'''aveats - see [[#Best Practices|Best Practices]] for details
:* P = '''P'''artial (limited) support only - see [[#Best Practices|Best Practices]] for details
:* No = the feature is not supported at this time - see [[#Best Practices|Best Practices]] for alternatives, if any.

{| border="1"

|-
|+ '''VMware Feature Support for Cisco Unified Communications 8.0(2) through 8.5(1)'''
! Feature !! Unified CM !! Unity Connection !! Unity !! Unified Presence !! Unified CCX !! Unified CCE !! Unified IC !! Cisco MediaSense !! CER !! SME !! Unified Attendant Consoles !! UC Management Suite (OM, SM, SSM, PM) !!

|- style="background:#E5E4E2"
! vSphere ESXi 4.0 Features
| || || || || || || || || || || || ||
|-

|- align="center"
! [[#Virtual Machine Templates (OVA Files)|VM Templates (OVAs)]]
| C || C || C || C || C || C || C || C || C || C || C || C ||
|-

|- align="center"
! [[#Copy Virtual Machine|Copy Virtual Machine]]
| C || C || C || C || C || C || C || No || C || C || No || No ||
|-

|- align="center"
! [[#Restart Virtual Machine on Different ESXi Host|Restart Virtual Machine on Different ESXi Host]]
| C || C || C || C || C || C || C || No || C || C || C || C ||
|-

|- align="center"
! [[#Resize Virtual Machine|Resize Virtual Machine]]
| P || P || P || P || P || No || P || No || P || P || No || No ||
|-

|- align="center"
! [[#VMware Hot Add|VMware Hot Add]]
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#Multiple Physical NICs and vNICs|Multiple Physical NICs and vNICs]]
| P || P || P || P || P || P || P || No || P || P || P || P
|-

|- align="center"
! [[#VMware High Availability (HA)|VMware High Availability (HA)]]
| C || C || C || C || No || No || No || No || C || C || No || C (PM only) ||
|-

|- align="center"
! [[#VMware Site Recovery Manager (SRM)|VMware Site Recovery Manager (SRM)]]
| C || No || No || No || No || No || No || No || C || C || No || No ||
|-

|- align="center"
! [[#VMware vNetwork Distributed Switch|VMware vNetwork Distributed Switch]]
| C || C || C || C || C || C || C || No || C || C || No || No ||
|-

|- align="center"
! [[#VMware vMotion|VMware vMotion]]
| P || P || No || P || P || No || No || No || P || No || No || P (PM only) ||
|-

|- align="center"
! [[#VMware Dynamic Resource Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#VMware Dynamic Power Management|VMware Dynamic Power Management]]
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#Long Distance vMotion|Long Distance vMotion]]
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#VMware Storage vMotion|VMware Storage vMotion]]
| C || No || No || No || C || No || No || No || C || No || No || No ||
|-

|- align="center"
! [[#VMware vCenter Update Manager|VMware vCenter Update Manager (VUM)]]
| No || No || C || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#VMware Consolidated Backup|VMware Consolidated Backup (VCB)]]
| No || No || C || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#VMware Data Recovery|VMware Data Recovery (DR, VDR)]]
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#VMware Snapshots|VMware Snapshots]]
| No || No || C || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#VMware Fault Tolerance|VMware Fault Tolerance (FT)]]
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#VMware vCenter Converter|VMware vCenter Converter]]
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#VMsafe|VMsafe]]
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#VMware vShield|VMware vShield]]
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#Virtual Appliance Packaging of UC apps|Virtual Appliance Packaging of UC apps]]
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#3rd-Party VM-based Backup Tools |3rd-Party VM-based Backup Tools (e.g. Veeam, Viziocore, esXpress)]]
| No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#3rd-Party VM-based Deployment Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! [[#3rd-Party Physical To Virtual (P2V) Migration Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No || No || No || No || No || No || No || No ||No || No || No || No ||
|-

|- align="center"
! All others not listed
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|-style="background:#E5E4E2"
! vSphere ESXi 4.1 Features
| || || || || || || || || || ||
|-

|- align="center"
! [[#Boot from SAN|Boot from SAN]]
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|- align="center"
! All other vSphere ESXi 4.1 Features
| No || No || No || No || No || No || No || No || No || No || No || No ||
|-

|}

== Best Practices ==

=== Virtual Machine Templates (OVA files) ===
NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]].

See www.dmtf.org for details on the Open Virtualization Format, which describes an OVF Package (a directory of files describing a virtual machine's configuration) and an OVA Package (single tar file containing an OVF Package).

“Template” in this context refers to an OVA file that defines the virtual server (but not the “workload”, i.e. the UC OS and application). Each virtualized UC product provides a set of predefined virtual machine templates (as OVA files) for supported Virtual Machine (VM) configurations. Customers must download and use these OVA template files for initial install, as they cover items such as supported capacity levels and any required OS/VM/SAN “alignment”. OVAs configured differently than the predefined templates are not supported at this time. To download the OVA files, refer to the [[Unified Communications Virtualization Sizing Guidelines|Unified Communications Virtualization sizing guidelines]].

=== Copy Virtual Machine ===
NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]].

Copying a Virtual Machine (VM) copies both the virtual server configuration and the workload (UC OS and application) running on that virtual server to a file on networked shared storage. This allows VMs to be copied, then subsequently modified or shut down. This feature effectively provides a method to do full system backup/restore, take system images or revert changes to software versions, user data and configuration changes.

:*Prior to copying, the VM must first be shutdown (which will shut down the virtual server, the UC OS and the UC application).
:*If uploading a VM copy as a “whole system restore”, clustered UC applications such as CUCM will probably require their replication to be manually “fixed” via a CLI command.

=== Restart Virtual Machine on Different ESXi Host ===
NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]].

A Virtual Machine (VM) file on network/shared storage can be booted on any physical server hosting ESXi that has access to that network shared storage. With multiple physical ESXi hosts connected to the same network shared storage, this can be used to perform:

:*Fast manual server moves, e.g. moving VM from ESXi host A to ESXi host B in another chassis, closet, building, etc.
:*Fast manual server recovery, e.g. moving VM from ESXi host A that has just had a server hardware or VMware failure to ESXi host B that is healthy. See also VMware High Availability and Site Recovery Manager.
:*Setting up software at a staging location to be later moved or deployed elsewhere. For multi-site scenarios, this may instead require “exporting” the VM.

=== Resize Virtual Machine ===
NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]].

Similar to adding/removing physical hardware to/from a physical server, you can add/remove virtual hardware (vCPU, vRAM, vDisk, vNIC, etc.) to/from a Virtual Machine (VM) via a software change in VMware’s configuration interfaces. Where supported, this provides the VM equivalent of migration to a more powerful or less powerful server.

:*Any changes to a VM must align with the best practices in [[#Virtual Machine Templates (OVA files)|Virtual Machine Templates (OVA files)]]. VM changes that result in an unsupported OVA configuration are not allowed. Even if you align with supported OVA configurations, desired VM changes may be prevented by one of the other caveats below.
:*Support for adding virtual hardware resources (similar to moving from a less powerful server to a more powerful server, such as MCS 7825 ⇒ MCS 7845) depends on which resource, and which UC product:
::*Adding vCPU is supported for all apps except Unity and Unity Connection, but requires VM to be shutdown first.
::*Adding vRAM is supported but requires VM to be shutdown first.
::*Adding vDisk is not supported as it would require re-partitioning by the application.
:*Adding vNIC is not supported unless the UC app supports multiple network connections with different IP addresses. See best practices for [[#Multiple Physical NICs and vNICs|Multiple Physical NICs and vNICs]].
:*For all other changes, it is recommended to backup the application, reinstall application on a new OVA file, and restore the application.
:*Removing virtual hardware resources (vCPU, vRAM, vDisk, etc.) is not supported (similar to moving from a more powerful server to a less powerful server, such as MCS 7845 ⇒ MCS 7825). These migrations require backing up the application, reinstalling on a new OVA file, and and restoring the application.
:*Live runtime resizing via the VMware Hot Add feature is not supported.

=== VMware Hot Add ===
Not supported. See [[#Resize Virtual Machine|Resize Virtual Machine ]] instead.

=== Multiple Physical NICs and vNICs ===
NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]].

Some virtualized UCS servers are configured with multiple physical NICs (see UCS page at http://www.cisco.com/go/swonly). Network traffic is switched from physical NICs to “vNIC’s” of the Virtual Machines (VM) via either VMware vSwitch or Cisco Nexus 1000V. Customers can use these multiple NICs for VM network traffic, VMware console access, or management “back-doors” for administrative access, backups, software updates or other traffic that is desired to be segregated from the VM network traffic. All these uses are supported for UC but note that UC apps like CUCM only support a single vNIC with a single IP address.

=== VMware High Availability (HA) ===
NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]].

This feature automatically restarts a Virtual Machine (VM) on the same physical server or a different physical server. It can be used to supplement software redundancy as a means of fast, automated Failed-server recovery when a VM (but not the application) is hung or if there is a fault with the physical host server or VMware software.

:*Failovers to other servers must not result in an unsupported deployment model (e.g. destination server must align with supported co-residency after failover occurs).
:*Does not protect vs. faults with the SAN or network hardware.

=== VMware Site Recovery Manager (SRM) ===
NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]].

This feature provides an automated disaster recovery solution that works on a “site to site” basis, where a “site” comprises physical servers, VMware and SAN storage. Refer to the VMware documentation for requirements to use this feature. There are no special requirements to use this feature with UC apps that support it.

=== VMware vNetwork Distributed Switch ===
NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]].

Supporting apps in UC on UCS may either use this feature, or the Cisco VN-Link technology (such as Cisco Nexus 1000V).

=== VMware vMotion ===
NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]].

This feature migrates a live, running Virtual Machine (VM) from one physical server to another. While used in general data centers for a variety of maintenance and cost savings activities, only a “maintenance mode” usage is supported at this time for UC:
:*VM must be installed on shared storage (SAN).
:*Source and destination physical servers must be connected to same SAN.
:*Destination physical server must not end up with over-subscribed hardware after the migration. Supported capacity and co-residency rules for UC must be followed before and after the migration.
:*VMware “Long Distance vMotion” (site to site) is not supported.
:*"Maintenance mode only" - VMware vMotion by definition operates on live VMs, but the VM running the UC app must be “live but quiescent”. I.e. in a maintenance window, not in production, not processing live traffic. This is because during the vMotion cutover, the system is paused, which for real-time UC apps creates service interruption which degrade voice quality after the migration for calls in progress.
:*The only supported scenario is a “live but quiescent” software move to a different server, e.g. for planned maintenance on the server or VMware software, or during troubleshooting to move software off of a physical server having issues.
:*Use of vMotion for real-time load-balancing of live UC VMs is not supported, whether alone or in conjunction with VMware Dynamic Resource Scheduler (DRS) or Dynamic Power Management (DPM).
:*Moving a shut down VM during a maintenance window, i.e. a "cold migration" or "host to host migration", is not vMotion and is supported.

=== VMware Dynamic Resource Scheduler ===
Not supported. See [[#VMware vMotion|vMotion]] for what is supported.

=== VMware Dynamic Power Management ===
Not supported. See [[#VMware vMotion|vMotion]] for what is supported.

=== Long Distance vMotion ===
Not supported. See [[#VMware vMotion|vMotion]] for what is supported. Long Distance vMotion is a joint Cisco and VMware validated architecture for using the vMotion feature across data centers. For more information, see http://blogs.cisco.com/datacenter/comments/cisco_and_vmware_validated_architecture_for_long_distance_vmotion/ and http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns836/white_paper_c11-557822.pdf.

=== Storage vMotion ===
NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]].

This “customer convenience” feature provides easy migration of a live system from one SAN to another SAN. For UC apps, an easier suggested alternative is to just perform manual VM shutdown and migration to the new SAN. However, if Storage vMotion must be used, it is only under the following conditions:
:*Requires SAN storage.
:*May only be done during a maintenance window with UC VMs shut down.

=== VMware vCenter Update Manager (VUM) ===
NOTE: Support varies by application and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature automates patching and updating of VMware vSphere hosts. Note that Cisco Unified Communications applications upgrades, patches and updates can not be delivered through vCenter Update Manager.

=== VMware Consolidated Backup (VCB) ===
NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

This feature provides integration with 3rd-party backup utilities so that they can non-disruptively backup the OS and application in a Virtual Machine (VM).
See also VMware Data Recovery and Copy Virtual Machine.

Existing UC app methods of backing up the software continue to be supported.

=== VMware Data Recovery ===
Not supported. See [[#VMware Consolidated Backup (VCB)|VMware Consolidated Backup]] for what is supported.

=== VMware Snapshots ===
NOTE: support varies by app and version. Before reading the best practices below, verify support at [[#VMware Infrastructure Feature Support|VMware Infrastructure Feature Support]]. For more details on Cisco Unity support, see http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html#wp82246.

Used to preserve the state of a VM without copying or creating additional VMs, effectively as a backup/restore or reversion technique.
See also VMware Data Recovery and Copy Virtual Machine.

=== VMware Fault Tolerance ===
Not supported. See [[#VMware High Availability (HA)|VMware High Availability]] for what is supported. Another alternative is manual Virtual Machine shutdown and migration.

=== VMware vCenter Converter ===
P2V tools are not supported. To migrate from bare-metal servers (e.g. Cisco 7800 Series Media Convergence Server) to UC on UCS, the supported procedure is:
:* upgrade to 8.x software version on the bare-metal server
:* take a software backup
:* fresh install 8.x software on VMware / UC on UCS
:* restore from backup

=== VMsafe ===
Not supported. See the documentation for the UC application software or UC appliance software to see what is supported.

=== VMware vShield ===
Not supported. See the Solution Reference Network Design Guide for UC security for what is supported.

=== Virtual Appliance Packaging of UC apps ===
Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party VM-based Backup Tools ===
Not supported. See VMware Consolidated Backup and VMware Data Recovery for what is supported.

=== 3rd-Party VM-based Deployment Tools ===
Not supported. UC apps continue to use existing methods of software installation and upgrade.

=== 3rd-Party Physical To Virtual (P2V) Migration Tools ===
Not supported. See VMware vCenter Converter for what is supported.

=== Boot from SAN ===
Not supported. Pre-requisite to support is UC certfication of VMware ESXi 4.1 which is not supported at this time.

== Services and Support Contracts for VMware are Required ==
Customers deploying virtualized UC must have a valid support contract for the VMware software in order to be supported by Cisco.

Customers purchasing VMware software licenses from Cisco must also purchase a subscription services part number from Cisco (for part number examples, see the UC on UCS page at www.cisco.com/go/swonly).

Customers purchasing VMware software from a 3rd-party must purchase subscription services from that 3rd-party or from VMware.

Customers should note that for VMware vSphere Hypervisor (formerly called “ESXi Single Server Edition” or “free ESXi”), VMware does not offer the same services options and terms as they do for their Standard, Advanced, Enterprise or Enterprise Plus Editions. Customers should take this into account when planning and pricing their support strategy.

Cisco Field and Channel Partners may consult the User Connect Licensing Ordering Guide for more information.

== Cisco TAC Support Expectations ==

The following table describes how TAC support works for VMware in a UC on UCS context, based on who VMware was purchased from.

{| border="1"
|-
! !! Buy from Cisco as Collaboration SKU !! Buy from Cisco as Data Center SKU !! Buy from 3rd-party, or enterprise/site license
|-
! Available VMware ESXi Editions
| Standard || Advanced, Enterprise or Enterprise Plus || Standard, Advanced, Enterprise, Enterprise Plus or vSphere Hypervisor (formerly "Single Server Edition" or "free ESXi"
|-
|-
! Mandatory Support Contracts
| ISV1 from Cisco as Collaboration Service SKU || ISV1 from Cisco as Data Center Service SKU || "SnS" subscription from VMware
|-
|-
! Who takes first call?
| Cisco || Cisco || VMware
|-

|}

'''TAC Responsibility:''' Note that multi-vendor triage is the norm in virtualized deployments, where the storage, server, hypervisor, OS and application are potentially all from different vendors. Cisco Voice TAC responsibility is the UC application, demarcated at the Virtual Machine. Cisco Server Virtualization TAC responsibility is for VMware (via triage), Cisco UCS, Cisco storage access (or triage with customer and their vendor) and storage array (via triage with customer and their vendor). Escalation to VMware, the customer, or the customer's storage vendors will be done as needed for solution components not produced by Cisco.

----

Back to [[Unified Communications Virtualization|Unified Communications Virtualization main page]]

2010-12-09T20:07:03Z

Wamaxwel:

Unified Communications cover a wide range to technologies. One can start with just controlling IP phones and making simple calls to others in the organization or outside your organization. Then there is a need t know the Presence information of other. How do I reach and interact with them? are they speaking on the phone? should one use Chat or are they traveling so one needs to reach them on their Mobile devices. How is Mobility accommodated in Unified Communication? Then there is Collaboration through Desktop application sharing or Conferencing with Voice and Video. This becomes complex as different technologies need to work with each other.

Cisco has its Solution Reference Network Design (SRND) guides that discuss Unified Communication for the Enterprise providing design guidance on how an Enterprise can bring the various technologies together for their users and provide them with a consolidated solution that takes into considerations some of their requirements and needs.

:* [http://www.cisco.com/en/US/docs/voice_ip_comm/uc_system/design/guides/UCgoList.html Cisco Unified Communication (UC) Solution Reference Network Design (SRND) guides]
:* [http://www.cisco.com/go/designzone UC SRNDs at Cisco Design Zone]

The following design tools for Cisco Unified Communications Systems are available on this wiki:

:* [[Cisco Unified Solution Capacity Sizing Tool Tutorial]]

[[Category:Unified Communications System Design]]

Unified Communications in a Virtualized Environment

2010-12-07T22:43:20Z

Wamaxwel:

Unified Communications in a Virtualized Environment

2010-12-07T22:42:21Z

Wamaxwel: