DocWiki - User contributions [en]

Unified Communications VMware Requirements

2011-08-19T09:32:47Z

Rpandara:

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

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 to be supported. See the other sections on this page for specific VMware product, version and feature support.

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

UC on UCS requires Cisco Unified Communications 8.0(2) and later - 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)]

See [[Before You Buy or Deploy - Considerations for Design and Procurement]] for information on customer purchase options and VMware license activation.

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 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 a major release (such as 4.0 Update 1 or "4.0U1") are supported at the time of release from VMware.
*Supported versions of VMware ESXi are listed below. Unlisted versions are not supported for Cisco Unified Communications until explicitly indicated on this site.

{{note| The minimum version may also be dependent on hardware - see the relevant supported applications matrix for the required product.}} 

 

=== ESXi Support for Call Processing and System Management Applications ===

{| class="wikitable FCK__ShowTableBorders"
|-
!
Application 

! VMware vSphere ESXi 4.0 and 4.0 Updates 
! VMware vSphere ESXi 4.1 and 4.1 Updates 
|-
| Unified Communications Manager
| 8.0(2)+, 8.5(1)+
| 8.0(2)+, 8.5(1)+
|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| 8.5(1)+
| 8.5(1)+
|-
| Cisco Emergency Responder
| 8.5(1)+, 8.6(1)+
| 8.5(1)+, 8.6(1)+
|-
| Session Manager Edition
| 8.5(1)+
| 8.5(1)+
|-
| Unified Attendant Consoles
| 8.0.3+, 8.5.1+
| 8.6.1+
|-
| UC Management Suite (OM, SM, SSM, PM)
| 7.1 and later
| 7.1 and later
|}

=== ESXi Support for Messaging and Presence Applications ===

{| style="width: 812px; height: 108px" class="wikitable FCK__ShowTableBorders"
|-
! Application 
! VMware vSphere ESXi 4.0 or 4.0 Update 1 
! VMware vSphere ESXi 4.1
|-
| Cisco Unity Connection
| 8.0(2) and later
| 8.0(3) and later
|-
| Cisco Unity
| 7.x and later
| 7.x and later
|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
| 8.0(2) and later
| 8.0(2) and later
|}

 

=== ESXi Support for Contact Center Applications ===

{{Note| For Virtual Machines that need '''more than 4 vCPUs''', the VMware vSphere ESXi '''Enterprise Plus''' licensing is required (8 way virtual SMP capability). The VMware vSphere Enterprise Plus license can be procured from the Cisco build-to-order or directly from the VMware (see VMware Purchasing section above.)}}

{| style="width: 816px; height: 396px" class="wikitable FCK__ShowTableBorders"
|-
! Application
! VMware vSphere ESXi 4.0 or 4.0 Update 1
! VMware vSphere ESXi 4.1
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]]
| 8.0(2) and later or 8.5(1) and later
| 8.0(2) SU2 and later or 8.5(1) and later
|-
| [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Workforce Optimization (WFO), Quality Manager (QM), and WorkForce Management (WFM)]
| 8.5(1) and later
| 8.5(2) and later
|-
| [[Unified Contact Center Enterprise]] 
| See below
| See below
|-
| - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tools
| 8.0(2) and later or 8.5(1) and later
| 8.0(2) and later or 8.5(1) and later
|-
| - Progger, Unified ICME/CCH/ICMH, Outbound Option with SCCP Dialer, Webview, EIM/WIM, Expert Advisor, RSM, Unified CRM Connector
| Not supported
| Not supported
|-
| [[Virtualization for Unified Intelligence Center|Cisco Unified Intelligence Center]] 
| 8.0(3) and later
| 8.5(2) and later
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]]
| 8.0(2) and later or 8.5(1) and later
| Not supported
|-
| [[Unified Customer Voice Portal]] (all components) 
| 8.0(1) and later or 8.5(1) and later
| Not supported
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| 8.5(1) and later
| 8.5(2) and later
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| 8.5(1) and later
| 8.5(1) and later
|}

=== Additional Information ===

This section provides additional information on ESXi features and support: 

*To upgrade from ESX 4.0 to ESX 4.1, see the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022140 Instructional Video] available at VMware's Knowledge Base website.
*VMware ESXi is sold in several editions with different levels of feature support. A comparison of VMware ESXi 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 when installing virtual machines that use more than 4 vCPUs, e.g. the 20,000 user Unity Connection overlay.
*While any Edition may be used, Cisco Unified Communications may not yet support all the features in the desired Edition (such as VMware Data Recovery). 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 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 for Feature Support Tables ===

:*Y(C) = Supported with '''C'''aveats - see [[#Best_Practices|Best Practices]] for details
:*Y(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.

=== VMware Feature Support for Call Processing and System Management 8.0(2) through 8.6(1) ===

{| border="1"
|+ ''' '''
|-
! Feature
! Unified CM
! CER
! SME
! Unified Attendant Consoles
! UC Management Suite (OM, SM, SSM, PM) 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C)
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C)
| Y(C)
|  Y(C)
| No
| No 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(P)
| Y(P)
| No 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)  
| Y(P)  
| Y(P)  
| Y(P)  
| Y(P) 
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C) (PM only) 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| Y(C) 
| Y(C)
| Y(C)
| No
| No 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C) 
| Y(C) 
| Y(C) 
| No
| No 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(C)
| Y(C) 
| No
| No 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C) 
| No
| No
| No 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| 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 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No 
|- align="center"
! All others not listed
| No
| No
| No
| No
| No 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C)
| No 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| No
| No 
|}

=== VMware Feature Support for Messaging and Presence 8.0(2) through 8.6(1) ===

{| border="1"
|+ '
|-
! Feature
! Unity Connection
! Unity
! Unified Presence
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P)
| Y(PP
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P)
| Y(P) 
| Y(P)
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| Y(C)
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| Y(C) 
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(P)
| No
| Y(P)
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| Y(C) 
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| Y(C)
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| No
| No
| No
| 
|- align="center"
! [[#Virtual_Appliance_Packaging_of_UC_apps|Virtual Appliance Packaging of UC apps]]
| 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
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
|- align="center"
! [[#Identity|Identity]]
| No  
| No  
| Y(C) 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| No
| No
| No
| 
|}

 

=== VMware Feature Support for Contact Center 8.0(2) through 8.6(1) ===

{| style="width: 906px; height: 823px" border="1"
|+ '
|-
! Feature
! Unified CCX
! Cisco WFO, QM, and WFM
! Unified CCE
! Unified IC
! Cisco MediaSense
! SocialMiner
! 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.0 Features
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Virtual_Machine_Templates_.28OVA_Files.29|VM Templates (OVAs)]]
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| Y(C) 
| 
|- align="center"
! [[#Copy_Virtual_Machine|Copy Virtual Machine]]
| Y(C) 
| Y(C)
| Y(C) 
| Y(C) 
| No
| Y(C) 
| 
|- align="center"
! [[#Restart_Virtual_Machine_on_Different_ESXi_Host|Restart Virtual Machine on Different ESXi Host]]
| Y(C) 
| Y(C) 
| Y(C)
| Y(C) 
| No
| Y(C) 
| 
|- align="center"
! [[#Resize_Virtual_Machine|Resize Virtual Machine]]
| Y(P)
| Y(P) 
| No
| Y(P) 
| No
| No
| 
|- align="center"
! [[#VMware_Hot_Add|VMware Hot Add]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Multiple_Physical_NICs_and_vNICs|Multiple Physical NICs and vNICs]]
| Y(P) 
| Y(P) 
| Y(P) 
| Y(P) 
| No
| No
|- align="center"
! [[#VMware_High_Availability_.28HA.29|VMware High Availability (HA)]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Site_Recovery_Manager_.28SRM.29|VMware Site Recovery Manager (SRM)]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vNetwork_Distributed_Switch|VMware vNetwork Distributed Switch]]
| Y(C)
| Y(C)
| No
| Y(C) 
| Y(C)
| No
| 
|- align="center"
! [[#VMware_vMotion|VMware vMotion]]
| Y(C) 
| Y(P) 
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Resource_Scheduler|VMware Dynamic Resource Scheduler (DRS)]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Dynamic_Power_Management|VMware Dynamic Power Management]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#Long_Distance_vMotion|Long Distance vMotion]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Storage_vMotion|VMware Storage vMotion]]
| Y(C) 
| Y(C)
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Update_Manager|VMware vCenter Update Manager (VUM)]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Consolidated_Backup|VMware Consolidated Backup (VCB)]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Data_Recovery|VMware Data Recovery (DR, VDR)]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Snapshots|VMware Snapshots]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_Fault_Tolerance|VMware Fault Tolerance (FT)]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vCenter_Converter|VMware vCenter Converter]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMsafe|VMsafe]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#VMware_vShield|VMware vShield]]
| 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
| 
|- 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
| 
|- align="center"
! [[#3rd-Party_VM-based_Deployment_Tools|3rd-Party VM-based Deployment Tools (e.g. rPath, Platespin)]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! [[#3rd-Party_Physical_To_Virtual_.28P2V.29_Migration_Tools|3rd-Party Physical To Virtual (P2V) Migration Tools]]
| No
| No
| No
| No
| No
| No
| 
|- align="center"
! All others not listed
| No
| No
| No
| No
| No
| No
| 
|- style="background: rgb(229,228,226)"
! vSphere ESXi 4.1 Features
| 
| 
| 
| 
| 
| 
|- align="center"
! [[#Boot_from_SAN|VMware Boot from SAN]]
| Y(C) 
| No
| Y(C) 
| Y(C)
| Y(C) 
| No
| 
|- align="center"
! All other vSphere ESXi 4.1 Features
| 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_.28OVA_files.29|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 Identity ===

The VMware identity feature allows you to copy an existing instance of a virtual Cisco Unified Presence, and change its identity. The identity of a system is made up of every setting that you usually configure during a fresh install (such as IP address, hostname, passwords).

You can then use this new identity for another instance of a Cisco Unified Presence on a virtual machine. This avoids you having to perform a complete installation each time you deploy a new Cisco Unified Presence.

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

The following applies to any use of vMotion with UC apps:

:*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.
:*The only supported scenario is a manual 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.

If the UC app is listed as "Supported with Caveats", then support is as described below:

:*Migration of UC VMs that are live and processing live traffic is supported, but note that Cisco testing cannot cover every possible operational scenario. Testing has shown there is a slight risk of calls in progress being impacted for a few seconds as the migration occurs, with worst case result of the affected calls being dropped. If vMotion is suspected as the cause of dropped calls, customers should gather appropriate application logs as well as performance data from VMware vCenter and send to Cisco TAC for analysis.

If the UC app is listed as "Partial" support, then support is “maintenance mode only” as described below:

:*"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.

 

=== 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_.28VCB.29|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_.28HA.29|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.

=== VMware Boot from SAN ===

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

VMware ESXi 4.1 is required for this feature. Even it works with 4.0, VMware's official support is only for 4.1 and later. Requires use of a "diskless" server - see Supported Hardware for tested reference configurations. Both VMware ESXi and UC apps are installed on, and boot from, the fibre channel SAN. See UCS page at www.cisco.com/go/swonly for storage support policy.

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

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Unified Communications Virtualization Supported Applications

2011-08-19T09:30:55Z

Rpandara:

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

Version compatibility of virtualized Cisco Unified Communications applications with various server/storage hardware options are listed below.

*Support information below is as of the release date of '''Cisco Unified Communications 8.6(1)''', which updated '''8.0, 8.5 and 8.6''' support policies.

*Ensure your deployment follows the rules listed [[High-level Checklist for Design and Implementation|here]].

*Click on the application name for additional product-specific requirements and information (if any).

*"TRC" = "Tested Reference Configuration" as described [[Unified Computing System Hardware|here]].

 

== Call Processing and System Management Applications ==

{| style="width: 1076px; height: 476px" class="wikitable FCK__ShowTableBorders"
|-
! Application
! [[Specification-Based Hardware Support]]
! B200 M2 TRC #1 (DAS+FC SAN)
! B200 M2 TRC #2 (Diskless, ESXi 4.1+ only)
! B200 M1 TRC #1 (DAS+FC SAN)
! B200 M1 TRC #2 (Diskless, ESXi 4.1+ only)
! C210 M2 TRC #1 (DAS)
! C210 M2 TRC #2 (DAS+FC SAN)
! C210 M2 TRC #3 (Diskless, ESXi 4.1+ only)
! C210 M1 TRC #1 (DAS, single-VM)
! C210 M1 TRC #2 (DAS)
! C210 M1 TRC #3 (DAS+FC SAN)
! C210 M1 TRC #4 (Diskless, ESXi 4.1+ only)
! C200 M2 TRC #1 (DAS)
 

|-
| Unified Communications Manager (1)
|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.0(2+)
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
|
*8.5(x)
*8.6(x)

 

|-
| Cisco Emergency Responder
|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|-
| Session Manager Edition
|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

|
*8.5(x)
*8.6(x)

| Not supported
|-
| Unified Attendant Consoles
|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.0(3)
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|
*8.6(x)

|-
| UC Management Suite (OM, SM, SSM, PM)
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
| 7.1 and later
|}

 (1) Applicable for publishers, subscribers, standalone TFTP and standalone multicast MOH nodes.

== Messaging and Presence Applications ==

{| class="wikitable FCK__ShowTableBorders"
|-
! Application
! [[Specification-Based Hardware Support]]
! B200 M2 TRC #1 (DAS+FC SAN)
! B200 M2 TRC #2 (Diskless, ESXi 4.1+ only)
! B200 M1 TRC #1 (DAS+FC SAN)
! B200 M1 TRC #2 (Diskless, ESXi 4.1+ only)
! C210 M2 TRC #1 (DAS)
! C210 M2 TRC #2 (DAS+FC SAN)
! C210 M2 TRC #3 (Diskless, ESXi 4.1+ only)
! C210 M1 TRC #1 (DAS, single-VM)
! C210 M1 TRC #2 (DAS)
! C210 M1 TRC #3 (DAS+FC SAN)
! C210 M1 TRC #4 (Diskless, ESXi 4.1+ only)
! C200 M2 TRC #1 (DAS) 
|-
| Cisco Unity Connection
| 8.0(2) and later
| 8.0(2) and later
| 8.0(3) and later
| 8.0(2) and later
| 8.0(3) and later
| 8.0(2) and later
| 8.0(2) and later
| 8.0(3) and later
| 8.0(2) and later
| 8.0(2) and later
| 8.0(2) and later
| 8.0(3) and later
| 8.0(2) and later
|-
| Cisco Unity
| 7.0(2) and later
| 7.0(2) and later
| Not supported
| 7.0(2) and later
| Not supported
| Not Supported
| 7.0(2) and later
| Not supported
| Not Supported
| Not Supported
| 7.0(2) and later
| Not Supported
| Not supported
|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
| 8.6(1) and later
| 8.5 and later
| 8.5 and later
| 8.0(2) and later
| 8.5 and later
| 8.5 and later
| 8.5 and later
| 8.5 and later
| 8.0(2) and later
| 8.0(2) and later
| 8.0(2) and later
| 8.5 and later
| 8.5 and later
|}

 

== Contact Center Applications ==

{| class="wikitable FCK__ShowTableBorders"
|-
! Application
! [[Specification-Based Hardware Support]]
! B200 M2 TRC #1 (DAS+FC SAN)
! B200 M2 TRC #2 (Diskless, ESXi 4.1+ only)
! B200 M1 TRC #1 (DAS+FC SAN)
! B200 M1 TRC #2 (Diskless, ESXi 4.1+ only)
! C210 M2 TRC #1 (DAS)
! C210 M2 TRC #2 (DAS+FC SAN)
! C210 M2 TRC #3 (Diskless, ESXi 4.1+ only)
! C210 M1 TRC #1 (DAS, single-VM)
! C210 M1 TRC #2 (DAS)
! C210 M1 TRC #3 (DAS+FC SAN)
! C210 M1 TRC #4 (Diskless, ESXi 4.1+ only)
! C200 M2 TRC #1 (DAS)
 

|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] 
| 8.5(1) and later 
|
*8.0(2) and later
*8.5(1) and later

| 8.0(2)SU2 and later
|
*8.0(2) and later
*8.5(1) and later

| 8.0(2)SU2 and later
|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

| 8.0(2)SU2 and later
|
*8.0(2) and later
*8.5(1) and later 

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

| 8.0(2)SU2 and later
| 8.5(1) and later
|-
| [http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX#Virtualization_Support_for_Cisco_Unified_Workforce_Optimization_.28WFO.29_in_Unified_CCX_8.5 Cisco Unified Workforce Optimization (WFO), Quality Management (QM), and WorkForce Management (WFM)]
| Not supported 
| Not supported
| Not supported
| Not supported
| Not supported
| 8.5(1) and later
| 8.5(1) and later
| Not supported
| 8.5(1) and later
| 8.5(1) and later
| 8.5(1) and later
| Not supported
| Not supported
|-
| [[Unified Contact Center Enterprise]] 
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
| See below
|-
| - Router, Logger, Rogger, Agent PG, MR PG, VRU PG, Administration and Data Server (AW, AW-CONFIG, AW-HDS, AW-HDS-DDS, HDS-DDS), Administration Client, Outbound Option with SIP Dialer, Support Tool, limited/hybrid support for Unified ICME/CCH/ICMH
| Not supported 
|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

|
*8.0(2) and later
*8.5(1) and later

| Not supported
|
*8.0(2) and later
*8.5(1) and later

| Not supported
|
*8.0(2) and later
*8.5(1) and later

| Not supported
|
*8.0(2) and later
*8.5(1) and later

| Not supported
|-
| - Progger, Outbound Option with SCCP Dialer, Webview, EIM/WIM, Expert Advisor, RSM, Unified CRM Connector
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
|-
| [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]] 
| Not supported 
| 8.0(3) and later
| 8.5(2) and later 
| 8.0(3) and later
| 8.5(2) and later
| 8.0(3) and later
| 8.0(3) and later
| 8.5(2) and later
| 8.0(3) and later
| 8.0(3) and later
| 8.0(3) and later
| 8.5(2) and later
| Not supported
|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]] 
| Not supported 
|
*8.0(2) and later
*8.5(1) and later

| Not supported 
|
*8.0(2) and later
*8.5(1) and later

| Not supported
|
*8.0(2) and later
*8.5(1) and later

| Not supported
| Not supported
| Not supported
|
*8.0(2) and later
*8.5(1) and later

| Not supported
| Not supported
| Not supported
|-
| [[Unified Customer Voice Portal]] (all components) 
| Not supported 
|
*8.0(1) and later
*8.5(1) and later

| Not supported
|
*8.0(1) and later
*8.5(1) and later

| Not supported
|
*8.0(1) and later
*8.5(1) and later

| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
| Not supported 
| 8.5(2) and later
| 8.5(2) and later
| 8.5(2) and later
| 8.5(2) and later
| 8.5(1) and later
| Not supported
| Not supported
| 8.5(1) and later
| 8.5(1) and later
| Not supported
| Not supported
| Not supported
|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
| Not supported 
| 8.5(2) and later
| Not supported
| Not supported
| Not supported
| 8.5(1) and later
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
| Not supported
|}

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Troubleshooting Tips for Unified IC 8.0

2011-08-18T12:01:50Z

Rpandara:

'''Back:''' [[Troubleshooting Unified Intelligence Center]]

'''Add tip:''' [[Create Troubleshooting Tips]]

'''Print PDF:''' [[Print Troubleshooting Tips for Unified IC 8.0]]

The following tips were added by Cisco Documentation:

= Installation =
* [[Installation: Locating Installation Log Files]]

= Migration =
* [[Migration: Collections do not appear in the filter page]]
* [[Migration: Report Filter page does not list any values]]
* [[Migration: Value list does not get Migrated]]
* [[Migration: Value list values are blank]]
* [[Migration: Gauge value update failed]]

= System =
* [[System: Checking Replication Status]]
* [[System: Checking the status of services]]
* [[System: Deleting the NTP Server in Cisco Unified OS Administration ]]
* [[System: Low Disk Space error at login to the Administation application]]
* [[System: Two Users on the Same Client Must use Different Browsers]]

= Reporting=
==== Accessibility ====
* [[Accessibility: Selecting items on a dropdown using the keyboard ]]
* [[Accessibility: JAWS Screenreader and Category "trees" ]]
* [[Accessibility: JAWS Screenreader Shortens Button Names to First Letter]]

==== Charts and Gauges ====

*[[Charts and Gauges: Gauge value update failed. The footer is null or not a number.]]
*[[Charts and Gauges: Printing]]
*[[Charts and Gauges: The Report View is Blank]]
*[[Charts and Gauges: The Chart Save Fails]]
*[[Charts and Gauges: Unexpected JavaScript exception]]

==== Dashboards ====
* [[Dashboards: Creating URL Items with Invalid URLs]]
==== Data Sources ====
* [[Data Sources: Causes of database connection failure]]
==== Report Definitions ====
* [[Report Definitions: Changing Display Name does not Change Display Name in the Report View ]]
==== Reports ====

*[[Reports: Export Errors]]
*[[Reports: Field content in wrapping in grid view]]
*[[Reports: Import button is disabled]]
*[[Reports: Import errors]]
*[[Reports: Unable to perform a SaveAs on Stock Reports]]
*[[Reporting: Right-click on field in Grid Editor does not work]]
*[[Reporting: Running reports that span daylight savings time changes]]
*[[Reporting: Super Header does not appear in the report viewer]]
*[[Reporting: The Imported Report is Associated with the Wrong Data Source]]
*[[Reporting: Script slows down the Filter page in Internet Explorer]]

==== Schedules ====
* [[Schedules: A scheduled job is unable to process at the scheduled time]]
* [[Schedules: The Schedule option is disabled when I right-click a report name]]
* [[Schedules: I do not see all scheduled reports on the Schedule List page]]
==== Security Center ====
* [[Security Center: Updating User Roles]]

==== Value Lists and Collections ====
* [[Value Lists and Collections: Cannot refresh value list]]
* [[Value Lists and Collections: Wildcard Collections and Java Regex Expressions]]

= Administration (OAMP)=

==== Admin User Management ====
==== Command Line Interface ====
==== Control Center ====
==== Device Configuration ====
==== License Management ====
==== Log and Trace Settings ====
==== RTMT ====
==== SNMP ====
==== Unified CCE User Integration ====

Reports: Unable to perform a SaveAs on Stock Reports

2011-08-18T12:00:50Z

Rpandara: moved Reports: Not able to perform a SaveAs on Stock Reports to Reports: Unable to perform a SaveAs on Stock Reports: Inputs from the engineering team

== Reports: Unable to perform a SaveAs on Stock Reports ==

{| border="1"
|-
! '''Problem Summary'''
| In CUIC 8.5.x, users other than the System Administrators are not able to perform a SaveAs on STOCK reports. The SaveAs option appears disabled.
|-
! '''Error Message'''
| Various
|-
! '''Possible Cause'''
| The user or the user group to which the user belongs to, does not have Write permission on the stock report that the user wants to do a SaveAs.
|-
! '''Recommended Action'''
|
Grant Write permissions to the user or the group, for the specific report, that the user/group wants to do a SaveAs. To achieve this, do the following: 

#From the CUIC Home Page, click Security > User Permissions.
#If you want to assign permissions to a user group, select the '''Assigned Group Permissions''' tab.
#If you want to assign permissions to a user, select the '''Assigned User Permissions''' tab.
#Select Reports as the category in the '''Permissions For''' box and browse to locate the specific report for which you want to modify the permissions.
#Select the user or the user group for which you want to modify the permissions. In case of user groups, you can selectively modify the permissions of specific users in the group by selecting only those users.
#Click '''Set Permissions'''.
#In the '''Set Permissions '''page, select '''Read''', '''Excecute''', and '''Write'''.
#Click '''OK'''.

|-
! '''Release'''
| Release 8.5(x)
|-
! '''Associated CDETS #'''
| None
|}

[[Category:Unified_IS,_Release_8.0]]

Unified Communications Virtualization Downloads (including OVA/OVF Templates)

2011-07-15T06:49:53Z

Rpandara:

'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]''' 

----

 

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

Recall that virtual MAC addresses may be auto-configured by VMware, or manually configured by you. If you manually configure them, remember to ensure each VM has a unique MAC address.

Note that vDisks are for "thick provisioning" at the VM level. For "Thick" vs. "Thin" provisioning and UC support policy, see Shared Storage Considerations.

Note that '''users''' is in the context of using the [http://tools.cisco.com/cucst/faces/login.jsp Cisco Unified Communications Sizing Tool] and the [http://www.cisco.com/go/ucsrnd design guides] for the indicated user count at a particular BHCA, number of devices per user, device mix per VM, etc. Actual capacity and total supported devices will be design-dependent; please follow all rules in the design guides and sizing tools.

Note that '''virtualization support details may vary by UC app'''. Make sure your deployment follows all the rules in the "Useful Links Summary" [[High-level Checklist for Design and Implementation|here]].

See [[Downloading OVA Templates for UC Applications]] for more information on how to download OVA templates for UC Applications.

For Specifications-based deployments, please note both the CPU core count AND the CPU core speed both of which correspond to physical CPU cores and physical CPU core speeds. Both are required to be met to support a full load VM OVA. At this time, only core speed for full load is defined. Do not use lower physical CPU core speeds until Cisco defines minimum speed for lower load levels. Cisco TAC will not troubleshoot a VM that is not receiving sufficient CPU cycles.

== Unified Communications Manager ==

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=268439621&catid=278875240 General OVA Download Location] 
*[[OVA Template Details for Unifed CM Release 8.0]] 
*[[OVA Template Details for Unifed CM Release 8.5]] 
*[[OVA Template Details for Unifed CM Release 8.6]] 

 

== Cisco Emergency Responder ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Emergency Responder'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 12,000 users (C200 only)]
| 2 @ 2.13 GHz each (600 MHz reserved)
| 4 GB (4 GB reserved)
| 1 x 80 GB
| 1
|
Use on C200 M2 TRC#1 only.

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

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 20,000 users]
| 1 @ 2.55 MHz (600 MHz reserved)
| 2.25 GB (2.304 GB reserved)
| 1 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

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

|-
! [http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=283314470&flowid=24901&softwareid=283831649 30,000 users]
| 2 @ 2.55 MHz each
| 6 GB
| 2 x 80 GB
| 1
|
Not for use on C200 M2 TRC#1.

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

|}

 

== Session Manager Edition ==

{| border="1"
|+ '''Supported OVA Templates: Session Manager Edition'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores and Speed per Core
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [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"
|
|}

 

== Unified Attendant Consoles ==

{| border="1"
|+ '''Supported OVA Templates: Unified Attendant Consoles'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! OVA for CUxAC
| 1 @ 2.55 GHz
| 2 GB
| 1x 80GB
| 1
| 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]
|}

 

== Cisco Unity Connection ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Unity Connection'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [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
| For version 8.5 or lesser - 2 GB 
For version 8.6(1) or higher - 4 GB

| 1x 160 GB
| 1
|
Requires reserving one physical core per physical server - see [[Unified Communications Virtualization Sizing Guidelines|co-residency policy]].

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
|
Requires reserving one physical core per physical server - see [[Unified Communications Virtualization Sizing Guidelines|co-residency policy]].

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

For use on CUCM-BE 6000.

|-
! [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
| For version 8.5 or lesser - 4 GB 
For version 8.6(1) or higher - 6 GB

| 1x 200 GB
| 1
|
Requires reserving one physical core per physical server - see [[Unified Communications Virtualization Sizing Guidelines|co-residency policy]].

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
| For version 8.5 or lesser - 4 GB 
For version 8.6(1) or higher - 6 GB

| 2x 146 GB or 
2x 300 GB or 2x 500 GB

| 1
|
For the larger 300GB or 500 GB disks, the datastore where the Connection virtual machine will reside must be formatted with a VMware VMFS block size of 2MB or more. A block size of 1MB limits the maximum virtual hard disk size to 256GB. A block size of 2MB allows 512GB virtual disks.

Requires reserving one physical core per physical server - see [[Unified Communications Virtualization Sizing Guidelines|co-residency policy]].

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 or 2x 500 GB
| 1
|
Require ESXi Enterprise Plus Licensing since it uses over 4 vCPUs for the Virtual Machine.

The datastore where the Connection virtual machine will reside must be formatted with a VMware VMFS block size of 2MB or more. A block size of 1MB limits the maximum virtual hard disk size to 256GB. A block size of 2MB allows 512GB virtual disks.

Requires reserving one physical core per physical server - see [[Unified Communications Virtualization Sizing Guidelines|co-residency policy]].

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

|}

== Cisco Unity ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Unity'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! 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
|
*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
|
*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

|}

 

== Cisco Unified Presence ==

See also:

*[[Virtualization for Cisco Unified Presence|Virtualization for Cisco Unified Presence]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&rellifecycle=&relind=AVAILABLE&reltype=latest OVA Template Download Page]

 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Presence'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 1000 users]
| 1 (800 MHz reserved)
| 2 GB
| 1x 80 GB
| 1
|
For use on CUCM-BE 6000.

|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 2500 users]
| 2 (2000 MHz reserved)
| 4 GB
| 1x 80 GB
| 1
| Use when migrating from MCS 7825 with disks smaller than 80 GB.
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283736431&flowid=23181&softwareid=282074312&release=8.0%20-%208.5&relind=AVAILABLE&rellifecycle=&reltype=latest 5000 users]
| 4 (4000 MHz reserved)
| 6 GB
| 2x 80 GB
| 1
| Use when migrating from MCS 7845.
|}

 

== Cisco Unified Contact Center Express ==

See also:

*[[Virtualization for Unified CCX]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest| Unified CCX OVA Templates]: Note that Unified CCX OVA version 2 is for use with ESXi 4.1. Please follow Unified Communications VMware Requirements page for ESXi 4.1 requirements (VMware Tools upgrade, LRO disabling, etc.)

 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Express'''
|- style="background: rgb(229,228,226)"
! colspan="2" | Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 100 agents] (Release 8.5(1))
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System, Unified CCX binaries, and Unified CCX logs

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 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
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest 400 agents] (Release 8.5(1))
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and CUCCX binaries
:*vDisk 2 = UCCX logs

| 1
|
|-
! rowspan="3" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.0&relind=AVAILABLE&rellifecycle=&reltype=latest Single OVA] (Release 8.5 (1) or later)
! 100 agents
| 2
| 4 GB
| 1x 146 GB
:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = Unified CCX logs

| 1
|
|-
! 300 agents
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = Unified CCX logs

| 1
|
|-
! 400 agents
| 4
| 8 GB
|
2x 146 GB

:*vDisk 1 = Operating System and CUCCX binaries
:*vDisk 2 = UCCX logs

| 1
|
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.1&rellifecycle=&relind=AVAILABLE&reltype=all 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
|
Capacities

:*300 named users
:*150 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.1&rellifecycle=&relind=AVAILABLE&reltype=all 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
|
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)

|}

== UC Management Suite (PM, OM, SM, SSM) ==

There are different OVAs for premise UC on UCS deployments vs. Hosted Collaboration Solution deployments.

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise UC on UCS Deployments'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! IOPS (avg) (1)
! IOPS (max) (1)
! vNIC
! Notes
! 
|-
! CUPM up to 1K phones (VM-CUCMS_1S)
| 1
| 2 GB
| 1x 30 GB
| 100
| 500
| 1
| 
|-
! CUPM 1K to 10K phones
| 4
| 4 GB
| 1x 40 GB (2)
| 100
| 500
| 1
| 
|-
! CUPM 10K to 60K phones app server
| 4
| 4 GB
| 1x 30 GB(3)
| 100
| 500
| 1
| requires DB VM
|-
! CUPM 10K to 60K phones database server
| 4
| 8 GB
| 1x 120 GB(3)
| 100
| 500
| 1
| requires App VM
|-
! CUOM/SM 1K phones
| 1
| 3 GB
| 1x 50 GB
| 6
| 15
| 1
| 
|-
! CUOM 10K phones (VM-CUCMS_2L)
| 2
| 8 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUOM 45K phones (VM-CUCMS_4L)
| 4
| 8 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSM 10K Phones (VM-CUCMS_2)
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUSM 45K Server (VM-CUCMS_4)
| 4
| 4 GB
| 2x 60 GB
|
|
| 1
| 
|-
! CUSSM 10K phones (VM-CUCMS_1)
| 1
| 4 GB
| 1x 60 GB
|
|
| 1
| 
|-
! CUSSM 45K Phones
| 2
| 4 GB
| 1x 72 GB
|
|
| 1
| 
|-
! CUCMS 10K phones Co-resident (VM_CUCMS_8)
| 8
| 16 GB
| 1x 320 GB (2)
| 100
| 500
| 1
| 
|}

Notes: (1) IOPS are for each CM publisher synced in parallel. If only one CM publisher then IOPS are 100/500. The maximum figures would be expected during nightly Infrastructrure or Subscriber syncs. (2) PM requires SAS or SCSI drives for deployments over 1K phones up to 10k phones (Disks must be aligned) (3) PM requires FC SAS for deployments over 10K phones (Disks must be aligned)

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Premise Systems'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K Server OVA]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 1K to 10K Server OVA]
| 4
| 4 GB
| 1x 40 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K App/Web Server OVA]
| 4
| 4 GB
| 1x 30 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283749794&release=8.5&relind=AVAILABLE&flowid=24181&softwareid=281934350&rellifecycle=&reltype=latest PM 10K to 60K Database Server OVA]
| 4
| 8 GB
| 1x 120 GB
| 1
| 
|}

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Hosted Collaboration Solution'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283112898&flowid=20421&softwareid=282773197&release=8.0&rellifecycle=&relind=AVAILABLE&reltype=latest CUOM+CUSM 1K phones for HCS (HCS_OM&SM_1K)]
| 1
| 3 GB
| 1x 50 GB
| 1
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283315737&flowid=19121&softwareid=281934350&release=2.2&rellifecycle=&relind=AVAILABLE&reltype=latest CUPM 1K phones for HCS (HCS_PM_1K)]
| 1
| 2 GB
| 1x 30 GB
| 1
| 
|}

== Unified Contact Center Enterprise ==

See also:

*[[Unified Contact Center Enterprise]]
*[http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Capacities_and_VM_Configuration_Requirements Unified CCE OVA Templates]
*See also [http://docwiki.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE#Unified_CCE_Scalability_Impacts Scalability Impacts]

Templates are available for Windows Server 2003 and Windows Server 2008 R2. [http://www.cisco.com/cisco/software/release.html?mdfid=268439622&release=1.1&relind=AVAILABLE&flowid=5210&softwareid=283914286&rellifecycle=&reltype=latest Download] the appropriate OVA file for the Windows OS that you are configuring. When you deploy the OVA, a drop-down list of the configurations are presented allowing you to select the appropriate configuration for the UCCE sized component that you are installing.

 

{| border="1" cellspacing="3" cellpadding="3"
|- style="background: rgb(229,228,226)"
! Configuration Name
! vCPU Cores
! vRAM / Memory (GB)
! vDisk (GB)
! vNIC 
! Notes
|-
| colspan="7" | '''Note: Windows Server 2008 R2 configurations are contained in the UCCE_8.5_win2008_vmv7_v1.1.ova file, Windows Server 2003 configurations are contained in the UCCE_8.5_win2003_vmv7_v1.1.ova file'''
|-
| '''Router 8000 agents'''
| 2
| 4
| 1 x80
| 2
|  
|-
| '''Logger 8000 agents'''
| 4
| 4
| 1x 80 for OS 1x 150 for DB
| 2
| The two vDisks can be in the same datastore 
|-
| '''Rogger 4000 agents'''
| 4
| 4
| 1x 80 for OS 1x 150 for DB
| 2
| The two vDisks can be in the same datastore 
|-
| '''Agent PG – CTIOS 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''Agent PG – CAD 1000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''Agent PG – CTIOS 450 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Agent PG – CAD 297 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''MR PG 2000 agents 10 pims'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''MR PG 1000 agents 5 pims'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''VRU PG 9600 ports 10 pims'''
| 2
| 2
| 1x 80
| 2
|  
|-
| '''VRU PG 1200 ports 4 pims'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Avaya ACD PG'''
| 2
| 4
| 1x 80
| 2
| See the [http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_technical_reference_list.html Hardware and System Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise and Hosted] for capacity information.
|-
| '''TDM ACD PG 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''TDM ACD PG 250 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''UCC Gateway PG 2000 agents'''
| 2
| 4
| 1x 80
| 2
|  
|-
| '''UCC Gateway PG 450 agents'''
| 1
| 2
| 1x 80
| 2
|  
|-
| '''Administration Client'''
| 1
| 2
| 1x 40
| 1
|  (Client AW)
|-
| '''Administration Server - AW'''
| 1
| 2
| 1x 40
| 1
|  
|-
| '''AW-HDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
|  (200 reporters.) The two vDisks can be in the same datastore
|-
| '''AW-HDS-DDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
|  (200 reporters.) The two vDisks can be in the same datastore
|-
| '''HDS-DDS'''
| 4
| 4
| 1x 80 for OS 1x 500 for DB
| 1
| (200 reporters.) The two vDisks can be in the same datastore  
|-
| '''CCMP single box 1500 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP Web/App Svr 8000 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP with Config AW 1500 agents'''
| 4
| 4
| 1x 100
| 1
|  
|-
| '''CCMP DB only 8000 agents'''
| 8
| 4
| 1x 250
| 1
|  
|}

== Unified Customer Voice Portal ==

See also:

*[[Unified Customer Voice Portal]]
*[[Unified Customer Voice Portal#Unified_CVP_Component_Capacities_and_VM_Configuration_Requirements|Unified CVP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Unified Customer Voice Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CVP Call Server + VXML Server (co-located Call Server and VXML Server) (Media Server is optionally included depending on the conditions. See CVP co-residency section for detail)
| 4
| 4 GB
| 1x 146 GB
| 1
| Template Name: Cisco Unified CVP Call Server-VXML Server.ova
|-
! Unified CVP Reporting Server (Large)
| 4
| 4 GB
| Disk 1 - 72 GB, Disk 2 - 438 GB
| 1
| Template Name: Cisco Unified CVP Reporting Server.ova
|-
! Unified CVP Operations Console
| 2
| 2 GB
| 1x 20 GB
| 1
| Template Name: Cisco Unified CVP Operations Console.ova
|}

== Cisco MediaSense ==

See also:

*[[Virtualization for Cisco MediaSense]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco MediaSense OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco MediaSense'''
|-
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
|-
! CMS_6T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 146 GB (thick provisioning)
| 1
| rowspan="3" | Release 8.5(1)
|-
! CMS_12T_main_server_v8.5_vmv7
| 7
| 8 GB
| 2 X 300 GB (thick provisioning)
| 1
|-
! CMS_expansion_server_v8.5_vmv7
| 7 
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|-
! CMS_12T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 150 GB (thick provisioning) 
| 1
| rowspan="4" | Release 8.5(2)
|-
! CMS_24T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 300 GB (thick provisioning) 
| 1
|-
! CMS_60T_primary_secondary_servers_v8.5.2_vmv7 
| 7 
| 8 GB 
| 2 X 600 GB (thick provisioning) 
| 1
|-
! CMS_expansion_server_v8.5.2_vmv7
| 7
| 8 GB
| 2 x 80 GB (thick provisioning)
| 1
|}

== Cisco Unified Intelligence Center ==

See also:

*[[Cisco Unified Intelligence Center]]
*[[Cisco Unified Intelligence Center#Unified_IC_Component_Capacities_and_VM_Configuration_Requirements|Cisco Unified Intelligence Center OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Intelligence Center'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=282163829&flowid=5228&softwareid=283776220&release=8.0(3)&relind=AVAILABLE&rellifecycle=&reltype=latest Unified IC (200 Reporting Users)]
| 4
| 6 GB
| 1x 150 GB
| 1
|
|}

== Cisco Unified Contact Center Management Portal ==

See also:

*[[Support for CCMP with UCCE on UCS Hardware|Cisco Unified Contact Center Management Portal]]
*[[Support for CCMP with UCCE on UCS Hardware#CCMP_Component_Capacities_and_VM_Configuration_Requirements|Unified CCMP OVA Templates]]

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Management Portal'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Unified CCMP (1500 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (Web/App Srv Only) (8000 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! Unified CCMP (DB Only) (8000 Agents)
| 8
| 4 GB
| 1x 250 GB
| 1
| 
|}

== Cisco SocialMiner ==

See also:

*[[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613136&softwareid=283733464&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all| Cisco SocialMiner OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco SocialMiner'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Standard Production Server
| 4
| 12 GB
| 1x 146 GB and 1x 256 GB
| 1
| 
|}

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

VMware Tools

2011-07-06T05:44:23Z

Rpandara:

'''Go to: [[Implementing Virtualization Deployments]]''' 

'''Go to: '''[[Ongoing Virtualization Operations and Maintenance|'''Ongoing Virtualization Operations and Maintenance''']]

 

VMware Tools are specialized drivers for virtual hardware that is installed in the UC applications when they are running virtualized. ''It is very important that the VMware tools version running in the UC application be in sync with the version of ESXi being used''.

If VMware tools status does not show "OK" from the viClient, the VMware Tools must be upgraded.

It is important to understand that the UC application is ''not ''tied to the version of ESXi it is running on. For example, initial deployment of the OVA and UC application may have been done on ESXi 4.0 update 1. Then at a later time, you may upgrade the ESXi software to version 4.1 or migrate the vm to a host running ESXi 4.1 - once running on the different ESXi version, you will need to upgrade the VMware Tools running in your UC application to match the host it is running on. Software upgrades of the UC application will preserve the version of VMware Tools currently running. 

 

= Which method to use =

Early versions of the UC applications required a COP file in order to upgrade the VMware Tools. Later, a CLI command was created to make the upgrades easier. Finally once the application was running on a RHEL 5 base, it was possible to support automatic tools upgrades.

For a given application/release ONLY the supported method(s) to upgrade the tools. The use of the wrong method almost certainly will fail and at worst may corrupt your virtual machine

 

{| style="width: 763px; height: 220px" border="1" cellspacing="1" cellpadding="1" align="center"
|-
! scope="col" | Application
! scope="col" | Release
! scope="col" | Method
|-
| rowspan="4" | Unified CM
| 8.0(x)
| 1
|-
| 8.5
| 2
|-
| 8.6.1 
| 3
|-
| 8.6.2 and later
| 3 and 4
|-
| rowspan="3" | Cisco Unity Connection
| 8.0
| 1
|-
| 8.5
| 2
|-
| 8.6 and later 
| 3
|-
| rowspan="3" | Cisco Unified Presence
| 8.0
| 1
|-
| 8.5
| 2
|-
| 8.6
| 2
|-
| rowspan="2" | Unified CCX
| 8.0(2) and later 
| 1
|-
| 8.5(1) and later 
| 2
|-
| rowspan="2" | Unified CCE
| 8.0(2) and later
| 3
|-
| 8.5(1) and later
| 3
|-
| Cisco MediaSense
| 8.5(1) and later
| 3
|-
| Cisco Social Miner
| 8.5(1) and later
| 3
|-
| Cisco Unified Intelligence Center
| 8.5(2) and later
| 1
|}

 

= Method 1: Using a COP file. =

----

'''Step 1'''    Download the VMware Tools Upgrade COP file located at the following location and and copy it to your SFTP/FTP server:   [http://www.cisco.com/cisco/software/release.html?mdfid=282827095&flowid=5329&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest http://www.cisco.com/cisco/software/release.html?mdfid=282827095&flowid=5329&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest], 

'''Step 2'''    From the vSphere Client log in to vCenter, or your ESXi host, and go to the '''Hosts and Clusters''' view ('''Ctrl+Shift+H''').

'''Step 3   '''To mount the correct version of the VMware Tools software in the Guest virtual CD/DVD drive, perform the following sub-steps.

:'''a. ''' Right-click the virtual machine that you are upgrading, and choose '''Guest > Install/Upgrade VMware Tools'''.

:'''b.'''  In the popup window, choose '''Interactive Tools Upgrade'''

 '''Step 4'''    Log in to the Unified CM Operating System Administration GUI, and choose '''Software Installation/Upgrade'''.

:'''a.  '''To install the VMware Tools Upgrade COP file that you downloaded in Step 1, enter the required information in the first page of the install/upgrade wizard.

:'''b.  '''To install the COP file, continue with the install/upgrade wizard. Installation of the COP file installs the VMware Tools software that you mounted in the virtual CD/DVD drive in Step 3 above.
 '''Note:''' Cisco Unified Intelligence Center supports upgrading using the COP file, only through the Command Line Interface(CLI). For more details, refer to the CUIC release notes.

 '''Step 5'''    To unmount the VMware Tools software from the virtual CD/DVD drive, after the COP file installation is complete, from the vSphere Client right-click the virtual machine that you upgraded, and choose '''VM > Guest > End VMware Tools Install'''.

 '''Step 6'''    From the Unified CM CLI, enter the CLI command '''utils system restart''', or choose '''Settings''' '''> Version > Restart'''  from the Unified CM Operating System Administration GUI. The system restart completes the installation of the new version of VMware Tools. The virtual machine reboots twice. Monitor the virtual machine console from the vSphere Client to see the system status.

'''Step 7'''    When the system is back up, the tools status is updated to '''OK '''from the vCenter Summary tab for the virtual machine that you upgraded. 

----

= Method 2: CLI command =

----

'''Step 1''' From the vSphere Client log in to vCenter, or your ESXi host, and go to the '''Hosts and Clusters''' view ('''Ctrl+Shift+H'''). 

'''Step 2'''   To mount the correct version of the VMware Tools software in the Guest virtual CD/DVD drive, perform the following sub-steps.

:'''a.''' Right-click the virtual machine that you are upgrading, and choose '''Guest > Install/Upgrade VMware Tools'''.

:'''b.''' In the popup window choose '''Interactive Tools Upgrade'''.

'''Step 3''' From the Unified CM CLI, enter the CLI command '''utils vmtools upgrade'''.

The system reboots twice. Monitor the virtual machine console from the vSphere Client to see the system status.

'''Step 4'''When the system is back up, the tools status is updated to '''OK '''from the vCenter Summary tab for the virtual machine that you upgraded.

'''Step 5''' After installation of the new version of VMware Tools is complete, remove the VMware Tools tar file from the virtual CD/DVD drive. (Usually, the VMware Tools tar file is called linux.iso). To remove the VMware Tools tar file, perform the following substeps.

:'''a.'''Right-click the virtual machine that you are upgrading, and choose '''VM > Edit Settings > CD/DVD drive'''.

:'''b.'''Choose '''Device Type''' as '''Client Device'''. 
<blockquote></blockquote>
 

----

= Method 3: Upgrade from viClient =

----

Use the following procedure to perform this upgrade.

 '''Step 1'''    From the viClient, Initiate the tools upgrade by clicking on '''VM > Guest > Install / Upgrade VMware Tools '''(this can also be done by right-clicking on the VM).

'''Step 2'''    Choose the automatic tools update and press '''OK'''. 

'''Step 3'''    The process will take a few minutes. The task should then be complete and the tools should be shown as "OK". No reboot is required. 

----

= Method 4: Automatically check and upgrade VMware Tools at boot time =

If the software release you are running supports Method 3 above (Automatic Upgrade),  then you can configure your virtual machine to automatically check the tools version during each VM power-on and automatically upgrade the tools if they are not up-to-date. Use the following procedure to perform this upgrade.

 '''Step 1''' Edit the VM settings by clicking on the Options tab, and select '''VMware tools'''. Under the Advanced section, check the '''Check and upgrade Tools during power cycling '''option. 

 

::A check will now be performed each time the VM powers on to determine if the tools need to be updated. Updates are performed automatically.

 {{note| Note, if the tools do need to be updated the VM may go through an additional boot cycle to update the tools (which will be done automatically).}}

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

VMware Tools

2011-06-20T06:10:41Z

Rpandara:

'''Go to: [[Implementing Virtualization Deployments]]''' 

'''Go to: '''[[Ongoing Virtualization Operations and Maintenance|'''Ongoing Virtualization Operations and Maintenance''']]

 

VMware Tools are specialized drivers for virtual hardware that is installed in the UC applications when they are running virtualized. ''It is very important that the VMware tools version running in the UC application be in sync with the version of ESXi being used''.

If VMware tools status does not show "OK" from the viClient, the VMware Tools must be upgraded.

It is important to understand that the UC application is ''not ''tied to the version of ESXi it is running on. For example, initial deployment of the OVA and UC application may have been done on ESXi 4.0 update 1. Then at a later time, you may upgrade the ESXi software to version 4.1 or migrate the vm to a host running ESXi 4.1 - once running on the different ESXi version, you will need to upgrade the VMware Tools running in your UC application to match the host it is running on. Software upgrades of the UC application will preserve the version of VMware Tools currently running. 

 

= Which method to use =

Early versions of the UC applications required a COP file in order to upgrade the VMware Tools. Later, a CLI command was created to make the upgrades easier. Finally once the application was running on a RHEL 5 base, it was possible to support automatic tools upgrades.

For a given application/release ONLY the supported method(s) to upgrade the tools. The use of the wrong method almost certainly will fail and at worst may corrupt your virtual machine

 

{| style="width: 763px; height: 220px" border="1" cellspacing="1" cellpadding="1" align="center"
|-
! scope="col" | Application
! scope="col" | Release
! scope="col" | Method
|-
| rowspan="4" | Unified CM
| 8.0(x)
| 1
|-
| 8.5
| 2
|-
| 8.6.1 
| 3
|-
| 8.6.2 and later
| 3 and 4
|-
| rowspan="3" | Cisco Unity Connection
| 8.0
| 1
|-
| 8.5
| 2
|-
| 8.6 and later 
| 3
|-
| rowspan="3" | Cisco Unified Presence
| 8.0
| 1
|-
| 8.5
| 2
|-
| 8.6
| 2
|-
| rowspan="2" | Unified CCX
| 8.0(2) and later 
| 1
|-
| 8.5(1) and later 
| 2
|-
| rowspan="2" | Unified CCE
| 8.0(2) and later
| 3
|-
| 8.5(1) and later
| 3
|-
| Cisco MediaSense
| 8.5(1) and later
| 3
|-
| Cisco Social Miner
| 8.5(1) and later
| 3
|-
| Cisco Unified Intelligence Center
| 8.5(2) and later
| 1
|}

 

= Method 1: Using a COP file. =

----

'''Step 1'''    Download the VMware Tools Upgrade COP file located at the following location and and copy it to your SFTP/FTP server:   [http://www.cisco.com/cisco/software/release.html?mdfid=282827095&flowid=5329&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest http://www.cisco.com/cisco/software/release.html?mdfid=282827095&flowid=5329&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest], 

'''Step 2'''    From the vSphere Client log in to vCenter, or your ESXi host, and go to the '''Hosts and Clusters''' view ('''Ctrl+Shift+H''').

'''Step 3   '''To mount the correct version of the VMware Tools software in the Guest virtual CD/DVD drive, perform the following sub-steps.

:'''a. ''' Right-click the virtual machine that you are upgrading, and choose '''Guest > Install/Upgrade VMware Tools'''.

:'''b.'''  In the popup window, choose '''Interactive Tools Upgrade'''

 '''Step 4'''    Log in to the Unified CM Operating System Administration GUI, and choose '''Software Installation/Upgrade'''.

:'''a.  '''To install the VMware Tools Upgrade COP file that you downloaded in Step 1, enter the required information in the first page of the install/upgrade wizard.

:'''b.  '''To install the COP file, continue with the install/upgrade wizard. Installation of the COP file installs the VMware Tools software that you mounted in the virtual CD/DVD drive in Step 3 above.

 '''Step 5'''    To unmount the VMware Tools software from the virtual CD/DVD drive, after the COP file installation is complete, from the vSphere Client right-click the virtual machine that you upgraded, and choose '''VM > Guest > End VMware Tools Install'''.

 '''Step 6'''    From the Unified CM CLI, enter the CLI command '''utils system restart''', or choose '''Settings''' '''> Version > Restart'''  from the Unified CM Operating System Administration GUI. The system restart completes the installation of the new version of VMware Tools. The virtual machine reboots twice. Monitor the virtual machine console from the vSphere Client to see the system status.

'''Step 7'''    When the system is back up, the tools status is updated to '''OK '''from the vCenter Summary tab for the virtual machine that you upgraded. 

----

= Method 2: CLI command =

----

'''Step 1''' From the vSphere Client log in to vCenter, or your ESXi host, and go to the '''Hosts and Clusters''' view ('''Ctrl+Shift+H'''). 

'''Step 2'''   To mount the correct version of the VMware Tools software in the Guest virtual CD/DVD drive, perform the following sub-steps.

:'''a.''' Right-click the virtual machine that you are upgrading, and choose '''Guest > Install/Upgrade VMware Tools'''.

:'''b.''' In the popup window choose '''Interactive Tools Upgrade'''.

'''Step 3''' From the Unified CM CLI, enter the CLI command '''utils vmtools upgrade'''.

The system reboots twice. Monitor the virtual machine console from the vSphere Client to see the system status.

'''Step 4'''When the system is back up, the tools status is updated to '''OK '''from the vCenter Summary tab for the virtual machine that you upgraded.

'''Step 5''' After installation of the new version of VMware Tools is complete, remove the VMware Tools tar file from the virtual CD/DVD drive. (Usually, the VMware Tools tar file is called linux.iso). To remove the VMware Tools tar file, perform the following substeps.

:'''a.'''Right-click the virtual machine that you are upgrading, and choose '''VM > Edit Settings > CD/DVD drive'''.

:'''b.'''Choose '''Device Type''' as '''Client Device'''. 
<blockquote></blockquote>
 

----

= Method 3: Upgrade from viClient =

----

Use the following procedure to perform this upgrade.

 '''Step 1'''    From the viClient, Initiate the tools upgrade by clicking on '''VM > Guest > Install / Upgrade VMware Tools '''(this can also be done by right-clicking on the VM).

'''Step 2'''    Choose the automatic tools update and press '''OK'''. 

'''Step 3'''    The process will take a few minutes. The task should then be complete and the tools should be shown as "OK". No reboot is required. 

----

= Method 4: Automatically check and upgrade VMware Tools at boot time =

If the software release you are running supports Method 3 above (Automatic Upgrade),  then you can configure your virtual machine to automatically check the tools version during each VM power-on and automatically upgrade the tools if they are not up-to-date. Use the following procedure to perform this upgrade.

 '''Step 1''' Edit the VM settings by clicking on the Options tab, and select '''VMware tools'''. Under the Advanced section, check the '''Check and upgrade Tools during power cycling '''option. 

 

::A check will now be performed each time the VM powers on to determine if the tools need to be updated. Updates are performed automatically.

 {{note| Note, if the tools do need to be updated the VM may go through an additional boot cycle to update the tools (which will be done automatically).}}

 

----

{| class="wikitable" border="1"
|-
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}

Migration: Collections do not appear in the filter page

2011-05-30T13:47:39Z

Rpandara: Created page with "== Migration: Collections do not appear in the filter page == {| border="1" |- ! '''Problem Summary''' | After performing a migration from CUIS Release 7.x to CUIC Release 8.x w..."

== Migration: Collections do not appear in the filter page ==

{| border="1"
|-
! '''Problem Summary'''
| After performing a migration from CUIS Release 7.x to CUIC Release 8.x when you launch a UCCE Report, you can see values in selection list but cannot see any collection in collection drop down.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
|
* There is a custom value list created for this report before the migration.
* The stock value list ID was edited or modified the original value that was set during the installation of CUIS Release 7.5(4)

|-
! '''Recommended Action'''
| Edit the report definition for such reports and associate the key criteria field to CUIC 8.5(2) stock value list by typing "stock" in value list manager.
|-
! '''Release'''
| Release 8.0(x)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Unified IS, Release 8.0]]

Troubleshooting Tips for Unified IC 8.0

2011-05-30T13:39:41Z

Rpandara: /* Migration */

'''Back:''' [[Troubleshooting Unified Intelligence Center]]

'''Add tip:''' [[Create Troubleshooting Tips]]

'''Print PDF:''' [[Print Troubleshooting Tips for Unified IC 8.0]]

The following tips were added by Cisco Documentation:

= Installation =
* [[Installation: Locating Installation Log Files]]

= Migration =
* [[Migration: Collections do not appear in the filter page]]
* [[Migration: Report Filter page does not list any values]]
* [[Migration: Value list does not get Migrated]]
* [[Migration: Value list values are blank]]
* [[Migration: Gauge value update failed]]

= System =
* [[System: Checking Replication Status]]
* [[System: Checking the status of services]]
* [[System: Deleting the NTP Server in Cisco Unified OS Administration ]]
* [[System: Low Disk Space error at login to the Administation application]]
* [[System: Two Users on the Same Client Must use Different Browsers]]

= Reporting=
==== Accessibility ====
* [[Accessibility: Selecting items on a dropdown using the keyboard ]]
* [[Accessibility: JAWS Screenreader and Category "trees" ]]
* [[Accessibility: JAWS Screenreader Shortens Button Names to First Letter]]

==== Charts and Gauges ====
* [[Charts and Gauges: Gauge value update failed. The footer is null or not a number. ]]
* [[Charts and Gauges: Printing]]
* [[Charts and Gauges: The Report View is Blank]]
* [[Charts and Gauges: The Chart Save Fails]]
* [[Charts and Gauges: Unexpected JavaScript exception]]
==== Dashboards ====
* [[Dashboards: Creating URL Items with Invalid URLs]]
==== Data Sources ====
* [[Data Sources: Causes of database connection failure]]
==== Report Definitions ====
* [[Report Definitions: Changing Display Name does not Change Display Name in the Report View ]]
==== Reports ====
* [[Reports: Export Errors]]
* [[Reports: Field content in wrapping in grid view]]
* [[Reports: Import button is disabled]]
* [[Reports: Import errors]]
* [[Reporting: Right-click on field in Grid Editor does not work]]
* [[Reporting: Running reports that span daylight savings time changes]]
* [[Reporting: Super Header does not appear in the report viewer]]
* [[Reporting: The Imported Report is Associated with the Wrong Data Source]]
* [[Reporting: Script slows down the Filter page in Internet Explorer]]

==== Schedules ====
* [[Schedules: A scheduled job is unable to process at the scheduled time]]
* [[Schedules: The Schedule option is disabled when I right-click a report name]]
* [[Schedules: I do not see all scheduled reports on the Schedule List page]]
==== Security Center ====
* [[Security Center: Updating User Roles]]

==== Value Lists and Collections ====
* [[Value Lists and Collections: Cannot refresh value list]]
* [[Value Lists and Collections: Wildcard Collections and Java Regex Expressions]]

= Administration (OAMP)=

==== Admin User Management ====
==== Command Line Interface ====
==== Control Center ====
==== Device Configuration ====
==== License Management ====
==== Log and Trace Settings ====
==== RTMT ====
==== SNMP ====
==== Unified CCE User Integration ====

Migration: Gauge value update failed

2011-05-17T13:39:52Z

Rpandara: Created page with "== Migration: Gauge value update failed == {| border="1" |- ! '''Problem Summary''' | After the migration, when you launch a view the system displays an error message. |- ! '''..."

== Migration: Gauge value update failed ==

{| border="1"
|-
! '''Problem Summary'''
| After the migration, when you launch a view the system displays an error message.
|-
! '''Error Message'''
| Gauge value update failed. The footer value is null or not a number.
|-
! '''Possible Cause'''
| The CUIS 7.x report field to which the gauge view is applied does not have a footer formula set.
|-
! '''Recommended Action'''
| Set the footer formula in the CUIC 8.x system using the '''Report definition field properties''' screen.
|-
! '''Release'''
| Release 8.0(x)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Unified IS, Release 8.0]]

Migration: Value list does not get Migrated

2011-04-18T09:34:34Z

Rpandara:

== Migration: Value list does not get Migrated ==

{| border="1"
|-
! '''Problem Summary'''
| After performing the migration, a particular value list does not appear in CUIC Release 8.x.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| The value lists are not referred by any of the imported reports.
|-
! '''Recommended Action'''
| None.
If a report field in CUIS Release 7.x refers to a value list, then the migration tool extracts the value list also as part of the report migration. For easy identification, the migration tool changes the value list description as "Migrated Value list". If the name of the value list contains special characters, the migration tool removes these before migrating the list into the CUIC Release 8.x machine. For example a value list by name Enterprise SkillGroup (special) will be renamed as Enterprise SkillGroup special. Note that if a value list is not referred by any of the reports then that value list is not be migrated.

|-
! '''Release'''
| Release 8.0(x)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Unified IS, Release 8.0]]

Migration: Value list values are blank

2011-04-18T09:32:56Z

Rpandara: Created page with "== Migration: Value list values are blank == {| border="1" |- ! '''Problem Summary''' | After performing the migration, the migrated value list values are blank. |- ! '''Error ..."

== Migration: Value list values are blank ==

{| border="1"
|-
! '''Problem Summary'''
| After performing the migration, the migrated value list values are blank.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| The value list or the query is incorrect.
|-
! '''Recommended Action'''
| If the value list values are blank, try editing the value list and validating the query. If value list query is valid, check the data source and ensure that the query can execute fine on the corresponding data source.
|-
! '''Release'''
| Release 8.0(x)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Unified IS, Release 8.0]]

Migration: Report Filter page does not list any values

2011-04-18T09:23:49Z

Rpandara: Created page with "== Migration: Report Filter page does not list any values == {| border="1" |- ! '''Problem Summary''' | After performing a migration from CUIS Release 7.x to CUIC Release 8.x, t..."

== Migration: Report Filter page does not list any values ==

{| border="1"
|-
! '''Problem Summary'''
| After performing a migration from CUIS Release 7.x to CUIC Release 8.x, the Report Filter page does not list any values.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| Value list query format in CUIS Release 7.x and and 8.x are different. Migration tool takes care of converting all possible SQL query format to 8.x compatible format. In a rare case when query is having many aliases or joins, query may not have been formatted according to 8.x. In such case, Reports that refers to a particular value list, may not show any values in the Report Filter page after launching this report.

|-
! '''Recommended Action'''
| Do one of the following:
* Edit the value list and click on the value list Query Validation button.
* If query is invalid, correct the query and re-launch the report.
|-
! '''Release'''
| Release 8.0(x)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Unified IS, Release 8.0]]

Virtualization for Unified Intelligence Center

2010-12-09T07:53:24Z

Rpandara: /* Installing VMware Tools */

= Updates to this Page =

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

{| class="wikitable"

|-
! Date
! Update

|-
| November 20, 2010
| Initial version of virtualization information for Cisco Unified Intelligence Center (Unified IC).

|-
|}

= Information for Partners about Unified IC Deployment Certification and Ordering =
'''It is important that partners who are planning to sell UCS products on Unified Intelligence Center, read the [[Unified Contact Center Enterprise]] DocWiki page.

This page contains essential information for partners about the following:

:* Partner Certification Requirements
:* UCS Server Ordering Information
:* Important Notes on Cisco UCS Service and Support

= Unified IC Details for VMWare Requirements=
See [[Unified Communications VMWare Requirements]] for supported/non-supported VMware features with Unified IC.

== Unified IC, Release 8.0(3) Support for Virtualization on the ESXi/UCS Platform ==
Starting with Release 8.0(3), virtualization of Unified IC on Cisco Unified Computing Systems (UCS) B200 Series and C210 Series hardware is supported on the following reference configurations:
* Unified IC is supported with Unified CCE on UCS B-Series solution B200-M1 (UCS-B200M1-VCS1) and B200-M2(UCS-B200M2-VCS1)
* UCS C-Series C210-M1 Reference Configuration 1(UCS-C210M1-VCD1) and Reference Configuration 2 (UCS-C210M1-VCD2)
* UCS C-Series C210-M2 Reference Configuration 1 and Reference Configuration 2

= UCS Hardware Requirements =

Requirements for Cisco Unified Contact Center Enterprise systems using UCS B200 M1 hardware are located
[http://docwiki.cisco.com/wiki/Unified_Computing_System_Hardware#B-200_M1_Requirements here].

Requirements for Cisco Unified Contact Center Enterprise systems using UCS C210 M1 hardware are located
[http://docwiki.cisco.com/wiki/Unified_Computing_System_Hardware#C-210_M1_Requirements here].

= VMware and Application Software Requirements=

The following software requirements apply specifically to Unified IC:
* VMWare ESXi 4.0 only, minimum version 4.0U1. Versions of ESXi prior to 4.0U1 and all versions of ESX are unsupported.
* Informix, and other third party software requirements for the Unified IC applications in the ESXi/UCS platform are the same as in the physical server. For such information, refer to the Hardware and System Software Specification for Unified IC available in the ''Hardware and System Software Specification (Bill of Materials) Guide'' at [http://www.cisco.com/en/US/products/ps9755/products_user_guide_list.html].

See [[Unified Communications VMWare Requirements]] for more information.

== Configuring the ESXi Host Network for the Virtual Machines ==
To configure the network for VMs, you create a virtual switch connected to an Ethernet port on the server, and then associate the virtual machine's network adapter to this virtual switch.
To Add a vSwitch
# Login to the ESXi host using VMware Infrastructure Client
# Select the ESXi host
# Click on the Configuration tab
# Click on Hardware/Networking
# Click on Add Networking...
# Select Connection Types: Virtual Machine. Click Next.
# Select "Create a virtual switch" and select an associated VM NIC.
# Enter Port Group Properties/Network label: VM Network n, where n is an integer.(Example: "VM Network 1")
# Click on Finish.

To Associate a VM Network Adapter to Network Connection
# Edit virtual machine settings.
# Select the Network Adapter.
# Select a virtual switch from the Network Connection/network label. (Example: "VM Network 1")
# Click OK.
# Click on Hardware/Networking
# Click on Add Networking...
# Select Connection Types: Virtual Machine. Click Next.
# Select "Create a virtual switch" and select an associated VM NIC.
# Enter Port Group Properties/Network label: VM Network n, where n is an integer.(Example: "VM Network 1")
# Click on Finish.

To Associate a VM Network Adapter to Network Connection
# Edit virtual machine settings.
# Select the Network Adapter.
# Select a virtual switch from the Network Connection/network label. (Example: "VM Network 1")
# Click OK.

== B-Series Considerations ==

When deploying Clustering Over the WAN with B-Series hardware, use of the Cisco UCS M81KR Virtual Interface Card is mandatory.

New B-Series deployments using Clustering Over the WAN must use a Nexus 7000 Series / Nexus 5000 Series vPC infrastructure, or a Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720-10G.

See the configuration guidelines for UCS B-Series Network Configuration at [[Unified Communications VMWare Requirements]] .

== C-Series Considerations ==
If deploying Clustering Over the WAN with C-Series hardware, do not trunk public and private networks. You must use separate physical interfaces off of the C-Series servers to create the public and private connections. See the configuration guidelines below.

=== Cisco Unified Intelligence Center on C-Series Network Configuration ===
This section provides instructions on performing the network configuration needed to deploy Cisco Unified Contact Center Enterprise (Unified CCE) on UCS C-Series servers.

=== Network Requirements for C-210 M1 Servers ===
When you install ESXi 4.0, connect the VMKernel port for the ESX Management Network to the virtual switch that is connected to the public network.

During the ESXi 4.0 installation, be sure to enable the second Network Interface Card so you can use it to connect to the private network.

You are required to configure the Unified IC public and private networks on the C-210 M1 servers the same as on the MCS servers.

To configure the network for the VMs using the vSphere client, do the following:
# Create a virtual switch connected to a 1GB physical port on the server.
# Connect this physical port to the public network, and associate the virtual machine's network adapter to this virtual switch.
# You need to do the same for the private network as required by Cisco Unified Intelligence Service components, such as Cisco Unified Intelligence Center Reporting server and OAMP.

== Installing Cisco Unified Intelligence Center components on Virtual Machines ==
Follow the steps and references below to install OR migrate the Unified IC components on Virtual Machines.
# Install setup and configure the UCS Hardware
# Configure the UCS Network. Follow the link UCS Network Configuration.
# Install and Boot VMWare ESXi. Refer to the following installation guide:
#*[http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/vmware/install/bseries-vmware-install.html|Cisco UCS B-Series Blade Servers VMware Installation Guide.]
#*[http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C210M1/install/C210M1.html|Cisco UCS C-Series VMware Installation Guide.]
# Create the Cisco Unified Intelligence Center Virtual Machines from the OVA template. OVA templates are available [http://www.cisco.com/cisco/software/release.html?mdfid=282163829&flowid=5228&softwareid=282377062| on Cisco.com.]

= Creating Virtual Machines from OVA VM Template =

See [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]] for more information.

[http://www.cisco.com/cisco/software/release.html?mdfid=282163829&softwareid=282377062&i=rm| Unified IC OVA Templates download]

=== Downloading OVA Template ===
:*Proceed to the [http://www.cisco.com/cisco/software/release.html?mdfid=282163829&softwareid=282377062 Release 8.0(3) Cisco download page].

:*To download a OVA file, click the '''Download File''' button next to that file. click the '''Add to Cart''' button next to file, then click on the '''Download Cart''' link. A Download Cart page appears.

:*Click the '''Proceed with Download''' button on this page. A Software License Agreement page appears.

:*Read the Software License Agreement, then click the '''Agree''' button

:*On the next page, click on either the '''Download Manager''' link (requires Java) or the '''Non Java Download Option''' link. A new browser window appears.

:*If you selected Download Manager, a Select Location dialog box appears. Specify the location where you want to save the file, and click '''Open''' to save the file to your local machine.

:*If you selected Non Java Download Option, click the '''Download''' link on the new browser window. Specify the location and save the file to your local machine.

===Creating Virtual Machines by Deploying the OVA Templates===
In the vSphere client, perform the following steps to deploy the Virtual machines.
# Highlight the host or cluster to which you wish the VM to be deployed.
# Select File > Deploy OVF Template.
# Click the Deploy from File radio button and specify the name and location of the file you downloaded in the previous section OR click the Deploy from URL radio button and specify the complete URL in the field, then click Next.
# Verify the details of the template, and click Next.
# Give the VM you are about to create a name, and choose an inventory location on your host, then click Next.
# Choose the datastore on which you would like the VM to reside - be sure there is sufficient free space to accommodate the new VM, then click Next.
# Choose a virtual network for the VM, then click Next.
# Verify the deployment settings, then click Finish.

{{note |
* VM CPU affinity is not supported. You don't need to set CPU affinity for the VMs that are running Cisco Unified Intelligence Center applications on the VMware ESXi on UCS platform.
* VM resource Reservation - VM resource reservation is not supported for the VMs that are running Cisco Unified Intelligence Center applications on the VMware ESXi on UCS platform. The VM computing resources should have a default reservation setting, which is no resource reservations.
* You cannot change the computing resource configuration of your VM at any time.
* You can never go below the minimum VM computing resource requirements as defined in the OVA templates.
* ESXi Server hyperthread is enabled by default.}}

==Unified IC Component Capacities and VM Configuration Requirements==
This table shows the supported Unified IC components, their capacities, and the VM computing resource requirements. You must use the OVA virtual machine templates to create the Cisco Unified Intelligence Center component VMs.

{| border="1" cellpadding="2"
!align="left" style="background:#99CCFF;" |'''Unified IC components'''
!align="left" style="background:#99CCFF;" |'''virtual CPU'''
!align="left" style="background:#99CCFF;" |'''RAM(GB)'''
!align="left" style="background:#99CCFF;" |'''vDisk(GB)'''
!align="left" style="background:#99CCFF;" |'''vNIC'''
!align="left" style="background:#99CCFF;" |'''Template Name'''
|-
| Reporting and OAMP
| 4
| 6
| 150
| 1
| CUIC_Reporting_200_v1.0_vmv7.ova
|-
|}

== Unified IC Component Co-Residency ==
* You can have one or more Cisco Unified Intelligence Center VMs co-residing on the same ESXi server, however you must follow the rules described below:
* You must not have CPU overcommitted on the ESXi server that is running Cisco Unified Intelligence Center application. The total number of vCPUs among all the virtual machines on an ESXi host must not greater than the total number of CPUs available on the ESXi server. In the case of the Cisco UCS B-200 M1, the total number of CPUs available is 8.
* You must not have memory overcommitted on the ESXi host that is running UC realtime applications. You must allocate minimum 6 GB of memory for the ESXi kernel. For example, if an ESXi server on B-200 M1 hardware has 36 GB of memory, after you allocate 2 GB for the ESXi kernel, you have 34 GB available for the virtual machines. The total memory allocated for all the virtual machines on an ESXi server must not be greater than 34 GB in this case.

== Performance Requirements ==
* CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM.
* Memory usage (average) should not exceed 80% for the ESXi Server and for each of the VMs.
* VM snapshots are not supported in production since they have significant impact on system performance.
* The SAN must be able to handle the following Cisco Unified Intelligence Center application disk I/O characteristics.
* Enable hyper threading on all ESXi servers.

{| border="1" cellpadding="2"
!align="left" style="background:#99CCFF;" |'''Details'''
!align="right" style="background:#99CCFF;" |'''Write (Kilobytes/Sec)'''
!align="right" style="background:#99CCFF;" |'''Read (Kilobytes/Sec)'''
!align="right" style="background:#99CCFF;" |'''IOPS'''
|-
| Maximum
| 7758.00
| 466.00
| 781.40
|-
| 95 Percentile
| 6446.30
| 433.10
| 628.34
|-
| Average
| 5727.44
| 74.32
| 460.17
|-
| Minimum
| 4897.00
| 0.00
| 288.75
|-
|}

== Installation ==

==Installing VMware Tools==
The VMware Tools must be installed on each of the VMs and all of the VMware Tools default settings should be used. Refer to the [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003806 VMware documentation] for instructions on installing or upgrading VMware Tools on the VM with Windows operating system.

==Installing Cisco Unified Intelligence Center Components on Virtual Machines==
You can install the Cisco Unified Intelligence Center components after the configuration of the VMs. Installation of these Cisco Unified Intelligence Center components on a VM is the same as the installation of these components on physical hardware.
Refer to the [http://www.cisco.com/en/US/products/ps9755/prod_installation_guides_list.html ''Unified IC Install Guide''] for the steps to install Unified IC components.

== Migrating ==
* You can upgrade/migrate the Unified Intelligence Center components from physical hardware or another virtual machine after the configuration of the VMs. Upgrade/Migration of these Unified IC software components to a VM is the same as the migration of these components to new physical hardware

* Refer to the [http://www.cisco.com/en/US/products/ps9755/prod_installation_guides_list.html ''Unified IC Install Guide''] for the steps to install Unified IC components.

-----

Back to [[Unified Communications Virtualization]]

[[Category:Unified Intelligence Suite]]

Unified Communications Virtualization Sizing Guidelines

2010-12-08T09:53:50Z

Rpandara:

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

{| class="wikitable"
|-
! Application
! Number Of CPUs
! Memory
! OVA Template
! Notes

|-
| [[Unified Communications Manager]]
| 2 vCPU
| 6 GB
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Communications_Manager_7500_User_Template 7500 User]
| none

|-
| [[Cisco Unity Connection]]
| 1 vCPU
| 2 GB
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_500_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_5000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_10.2C000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_20.2C000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_15.2C000_User_Template 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 [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html Design Guide for Cisco Unity Virtualization].

|-
|
| 2 vCPU
| 4 GB
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_5000_User_Template 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 [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html Design Guide for Cisco Unity Virtualization].

|-
| [[Cisco Unified Presence]]
| 2 vCPU
| 4 GB
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unified_Presence_Server_2500_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unified_Presence_Server_5000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unified_Contact_Center_300_Agent_Template 300 Agent]
| none

|-
| [[Unified Contact Center Enterprise]]
|
|
|
| Multiple templates and configurations exist for Unified Contact Center Enterprise based on system component. Refer to [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Capacities_and_VM_Configuration_Requirements Unified CCE Component Capacities and VM Configuration Requirements] for full details.

|-
| [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_IC Unified Intelligence Center]
|
|
|
| Refer to the following link for full details [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_IC#Unified_IC-Specific_Information_for_Sizing_Guidelines 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 [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications 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.

{| class="wikitable"
|-
! Application
! Number Of CPUs
! Memory
! OVA Template
! Notes

|-
| [[Unified Communications Manager]]
| 2 vCPU
| 6 GB
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Communications_Manager_7500_User_Template 7500 User]
| none

|-
| [[Cisco Unity Connection]]
| 1 vCPU
| 2 GB
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_500_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_5000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_10.2C000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_20.2C000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unified_Contact_Center_300_Agent_Template 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 [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications 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 [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Co-Residency_and_Examples 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
:::* [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Communications_Manager_7500_User_Template 7500 User]

::* Unity Connection
:::* Up to 10,000 users
:::* Two Servers in Active/Active configuration
:::* [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_10.2C000_User_Template 10,000 User]

::* Unified Presence
:::* Up to 10,000 users
:::* Two servers supporting 5000 users each
:::* [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unified_Presence_Server_5000_User_Template 5000 Users]

::* Unified Intelligence Center
:::* Up to 1200 users
:::* One Publisher, Seven Subscribers , database replicated among all 8 nodes
:::* [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Intelligence_Center_200_User_Template 200 Users]

::* Unified Contact Center Express
:::* Up to 300 agents
:::* Two servers suping 300 agents each; active/standby redundancy
:::* [http://docwiki-dev.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#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 ===
[https://apps.cisco.com/qtc/config/jsp/configureHome.jsp 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 [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization Unified Communications Virtualization main page]

Unified Communications Virtualization Sizing Guidelines

2010-12-08T09:52:17Z

Rpandara:

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

{| class="wikitable"
|-
! Application
! Number Of CPUs
! Memory
! OVA Template
! Notes

|-
| [[Unified Communications Manager]]
| 2 vCPU
| 6 GB
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Communications_Manager_7500_User_Template 7500 User]
| none

|-
| [[Cisco Unity Connection]]
| 1 vCPU
| 2 GB
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_500_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_5000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_10.2C000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_20.2C000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_15.2C000_User_Template 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 [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html Design Guide for Cisco Unity Virtualization].

|-
|
| 2 vCPU
| 4 GB
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_5000_User_Template 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 [http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html Design Guide for Cisco Unity Virtualization].

|-
| [[Cisco Unified Presence]]
| 2 vCPU
| 4 GB
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unified_Presence_Server_2500_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unified_Presence_Server_5000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unified_Contact_Center_300_Agent_Template 300 Agent]
| none

|-
| [[Unified Contact Center Enterprise]]
|
|
|
| Multiple templates and configurations exist for Unified Contact Center Enterprise based on system component. Refer to [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Capacities_and_VM_Configuration_Requirements Unified CCE Component Capacities and VM Configuration Requirements] for full details.

|-
| [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_IC Unified Intelligence Center]
|
|
|
| Refer to the following link for full details [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_IC#Unified_IC-Specific_Information_for_Sizing_Guidelines 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 [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications 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.

{| class="wikitable"
|-
! Application
! Number Of CPUs
! Memory
! OVA Template
! Notes

|-
| [[Unified Communications Manager]]
| 2 vCPU
| 6 GB
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Communications_Manager_7500_User_Template 7500 User]
| none

|-
| [[Cisco Unity Connection]]
| 1 vCPU
| 2 GB
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_500_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_5000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_10.2C000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_20.2C000_User_Template 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
| [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unified_Contact_Center_300_Agent_Template 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 [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications 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 [http://docwiki.cisco.com/wiki/Unified_Contact_Center_Enterprise#Unified_CCE_Component_Co-Residency_and_Examples 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
:::* [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Communications_Manager_7500_User_Template 7500 User]

::* Unity Connection
:::* Up to 10,000 users
:::* Two Servers in Active/Active configuration
:::* [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unity_Connection_10.2C000_User_Template 10,000 User]

::* Unified Presence
:::* Up to 10,000 users
:::* Two servers supporting 5000 users each
:::* [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unified_Presence_Server_5000_User_Template 5000 Users]

::* Unified Intelligence Center
:::* Up to 1200 users
:::* One Publisher, Seven Subscribers , database replicated among all 8 nodes
:::* [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Unified_Intelligence_Center_200_User_Template]

::* Unified Contact Center Express
:::* Up to 300 agents
:::* Two servers suping 300 agents each; active/standby redundancy
:::* [http://docwiki-dev.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#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 ===
[https://apps.cisco.com/qtc/config/jsp/configureHome.jsp 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 [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization Unified Communications Virtualization main page]

Unified Communications in a Virtualized Environment

2010-12-08T08:35:26Z

Rpandara:

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Custom Search</title>



<style type="text/css">

</style>
</head>
<body>
<table width="850" border="0">
<tr>
<td> </td>
<td> </td>
<td>Custom Search:</td>
</tr>
<tr>
<td> </td>
<td> </td>
<td><form action="http://vtg-india/search/search-results.htm" id="cse-search-box">
<div>
<input type="hidden" name="cx" />
<input type="hidden" name="cof" />
<input type="hidden" name="ie" value="UTF-8" />
<input type="text" name="q" size="31" />
<select name="sysversion" id="sysversion" onchange="ValueAssign()">
<option value="000" selected="selected">All</option>
<option value="001">System DocWiki</option>
<option value="701">Release 7.0(1)</option>
<option value="611">Release 6.1(1)</option>
<option value="601">Release 6.0(1)</option>
<option value="513">Release 5.1(3)</option>
<option value="512">Release 5.1(2)</option>
<option value="511">Release 5.1(1)</option>
<option value="502">Release 5.0(2)</option>
<option value="501">Release 5.0(1)</option>
</select>
<input type="submit" name="sa" value="Search" />
</div>
</form>
<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en">
</script>
</tr>
</table>
</body>
<script>
function ValueAssign()
{
//var 7VersionValue='006593089695086678066:0kl2h5qj840';
if(document.getElementById("sysversion").value=="000")
{
document.forms[0].cx.value='006593089695086678066:0kl2h5qj840';
document.forms[0].cof.value='FORID:9';
}
if(document.getElementById("sysversion").value=="001")
{
document.forms[0].cx.value='006593089695086678066:lzag0lfme8o';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="701")
{
document.forms[0].cx.value='006593089695086678066:kfddvkpdjrs';
document.forms[0].cof.value='FORID:10';
}

if(document.getElementById("sysversion").value=="611")
{
document.forms[0].cx.value='006593089695086678066:nqrs5zeblvi';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="601")
{
document.forms[0].cx.value='006593089695086678066:kwqrd9thjqm';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="513")
{
document.forms[0].cx.value='006593089695086678066:aepwjocyk7k';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="512")
{
document.forms[0].cx.value='006593089695086678066:4zzx60m1sqa';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="511")
{
document.forms[0].cx.value='006593089695086678066:nuz7v4v8vyy';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="502")
{
document.forms[0].cx.value='006593089695086678066:uwk4-ptfgxe';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="501")
{
document.forms[0].cx.value='006593089695086678066:pphx2va8kka';
document.forms[0].cof.value='FORID:10';
}
}
</script>
</html>

----
Cisco Unified Communications Virtualization refers to Unified Communications applications running on a virtual machine on a Unified Computing System (UCS). At the system level, this capability is supported for select applications starting with the Unified Communications Release 8.0(2).

This wiki area contains the following information about Unified Communications Virtualization:

:* [[Unified Computing System Hardware]]

:* [[Unified Communications VMWare Requirements]]

:* [[Unified Communications Virtualization Sizing Guidelines]]

:* [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]

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

:* [[Unified Communications Virtualization Supported Applications]]
::* [[Unified Communications Manager]]
::* [[Unified Contact Center Express/IPIVR]]
::* [[Unified Contact Center Enterprise]]
::* [[Unified Customer Voice Portal]]
::* [[Cisco Unified Intelligence Center]]
::* [[Cisco Unified Presence]]
::* [[Cisco Unity]]
::* [[Cisco Unity Connection]]

:* [[Unified Communications Virtualization Related Documentation and Links]]

Topics will be added and updated on a regular basis, with an emphasis on applying, expanding, and clarifying the content contained in the documentation highlighted above. Articles will be clearly marked with the system release(s) to which the information applies. For instructions on editing or adding articles, refer to [[DocWiki:About|About DocWiki]].

To suggest a new topic or for any inquiries or comments, send email to [mailto:sysdocwiki@cisco.com sysdocwiki@cisco.com].

[[Category:Systems]]
[[Category:Technologies]]

Unified Communications in a Virtualized Environment

2010-12-08T08:33:58Z

Rpandara:

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Custom Search</title>



<style type="text/css">

</style>
</head>
<body>
<table width="850" border="0">
<tr>
<td> </td>
<td> </td>
<td>Custom Search:</td>
</tr>
<tr>
<td> </td>
<td> </td>
<td><form action="http://vtg-india/search/search-results.htm" id="cse-search-box">
<div>
<input type="hidden" name="cx" />
<input type="hidden" name="cof" />
<input type="hidden" name="ie" value="UTF-8" />
<input type="text" name="q" size="31" />
<select name="sysversion" id="sysversion" onchange="ValueAssign()">
<option value="000" selected="selected">All</option>
<option value="001">System DocWiki</option>
<option value="701">Release 7.0(1)</option>
<option value="611">Release 6.1(1)</option>
<option value="601">Release 6.0(1)</option>
<option value="513">Release 5.1(3)</option>
<option value="512">Release 5.1(2)</option>
<option value="511">Release 5.1(1)</option>
<option value="502">Release 5.0(2)</option>
<option value="501">Release 5.0(1)</option>
</select>
<input type="submit" name="sa" value="Search" />
</div>
</form>
<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en">
</script>
</tr>
</table>
</body>
<script>
function ValueAssign()
{
//var 7VersionValue='006593089695086678066:0kl2h5qj840';
if(document.getElementById("sysversion").value=="000")
{
document.forms[0].cx.value='006593089695086678066:0kl2h5qj840';
document.forms[0].cof.value='FORID:9';
}
if(document.getElementById("sysversion").value=="001")
{
document.forms[0].cx.value='006593089695086678066:lzag0lfme8o';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="701")
{
document.forms[0].cx.value='006593089695086678066:kfddvkpdjrs';
document.forms[0].cof.value='FORID:10';
}

if(document.getElementById("sysversion").value=="611")
{
document.forms[0].cx.value='006593089695086678066:nqrs5zeblvi';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="601")
{
document.forms[0].cx.value='006593089695086678066:kwqrd9thjqm';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="513")
{
document.forms[0].cx.value='006593089695086678066:aepwjocyk7k';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="512")
{
document.forms[0].cx.value='006593089695086678066:4zzx60m1sqa';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="511")
{
document.forms[0].cx.value='006593089695086678066:nuz7v4v8vyy';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="502")
{
document.forms[0].cx.value='006593089695086678066:uwk4-ptfgxe';
document.forms[0].cof.value='FORID:10';
}
if(document.getElementById("sysversion").value=="501")
{
document.forms[0].cx.value='006593089695086678066:pphx2va8kka';
document.forms[0].cof.value='FORID:10';
}
}
</script>
</html>

----
Cisco Unified Communications Virtualization refers to Unified Communications applications running on a virtual machine on a Unified Computing System (UCS). At the system level, this capability is supported for select applications starting with the Unified Communications Release 8.0(2).

This wiki area contains the following information about Unified Communications Virtualization:

:* [[Unified Computing System Hardware]]

:* [[Unified Communications VMWare Requirements]]

:* [[Unified Communications Virtualization Sizing Guidelines]]

:* [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]

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

:* [[Unified Communications Virtualization Supported Applications]]
::* [[Unified Communications Manager]]
::* [[Unified Contact Center Express/IPIVR]]
::* [[Unified Contact Center Enterprise]]
::* [[Unified Customer Voice Portal]]
::* [[Virtualization for Unified Intelligence Center | Unified Intelligence Center]]
::* [[Cisco Unified Intelligence Center]]
::* [[Cisco Unified Presence]]
::* [[Cisco Unity]]
::* [[Cisco Unity Connection]]

:* [[Unified Communications Virtualization Related Documentation and Links]]

Topics will be added and updated on a regular basis, with an emphasis on applying, expanding, and clarifying the content contained in the documentation highlighted above. Articles will be clearly marked with the system release(s) to which the information applies. For instructions on editing or adding articles, refer to [[DocWiki:About|About DocWiki]].

To suggest a new topic or for any inquiries or comments, send email to [mailto:sysdocwiki@cisco.com sysdocwiki@cisco.com].

[[Category:Systems]]
[[Category:Technologies]]

Reporting: Script slows down the Filter page in Internet Explorer

2010-10-20T01:59:38Z

Rpandara: /* Reporting: Script slows down the Filter page in Internet Explorer */

== Reporting: Script slows down the Filter page in Internet Explorer ==

{| border="1"
|-
! '''Problem Summary'''
| The Filter page, when open in Internet Explorer, is slow and displays a warning when there are more than 1500 system collections with about 15,000 values in them.
|-
! '''Error Message'''
| [[Image:IE_Warning.jpg]]
|-
! '''Possible Cause'''
| You have exceeded the maximum number of scripts that can be run on the Internet Explorer page.
|-
! '''Recommended Action'''
| Do the following:
1) Go to '''Start''' menu > '''Run'''.

2) Type '''regedit'''.

3) Open the registry key: ''HKEY_CURRENT_USER\Software\Microsoft\InternetExplorer\Styles''. If the Styles key is not present, create a new key that is called Styles.

4) Right click anywhere in the right pane and create a new '''DWORD''' value called "'''MaxScriptStatements'''".

5) Copy and paste that in to the name box and set the value to the desired number of script statements, for example 8000000.

|-
! '''Release'''
| Release 8.0(x)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Unified IS, Release 8.0]]

File:IE Warning.jpg

2010-10-20T01:56:21Z

Rpandara: Warning message in Internet Explorer about slow running scripts

Warning message in Internet Explorer about slow running scripts

Troubleshooting Tips for Unified IC 8.0

2010-09-22T03:59:26Z

Rpandara: /* User Interface and Sign on */

'''Back:''' [[Troubleshooting Unified Intelligence Center]]

'''Add tip:''' [[Create Troubleshooting Tips]]

'''Print PDF:''' [[Print Troubleshooting Tips for Unified IC 8.0]]

The following tips were added by Cisco Documentation:

= Installation =
* [[Installation: Locating Installation Log Files]]

= System =
* [[System: Checking Replication Status]]
* [[System: Checking the status of services]]
* [[System: Deleting the NTP Server in Cisco Unified OS Administration ]]
* [[System: Low Disk Space error at login to the Administation application]]
* [[System: Two Users on the Same Client Must use Different Browsers]]

= Reporting=
==== Accessibility ====
* [[Accessibility: Selecting items on a dropdown using the keyboard ]]
* [[Accessibility: JAWS Screenreader and Category "trees" ]]
* [[Accessibility: JAWS Screenreader Shortens Button Names to First Letter]]

==== Charts and Gauges ====
* [[Charts and Gauges: Gauge value update failed. The footer is null or not a number. ]]
* [[Charts and Gauges: Printing]]
* [[Charts and Gauges: The Report View is Blank]]
* [[Charts and Gauges: The Chart Save Fails]]
* [[Charts and Gauges: Unexpected JavaScript exception]]
==== Dashboards ====
* [[Dashboards: Creating URL Items with Invalid URLs]]
==== Data Sources ====
* [[Data Sources: Causes of database connection failure]]
==== Report Definitions ====
* [[Report Definitions: Changing Display Name does not Change Display Name in the Report View ]]
==== Reports ====
* [[Reports: Export Errors]]
* [[Reports: Field content in wrapping in grid view]]
* [[Reports: Import button is disabled]]
* [[Reports: Import errors]]
* [[Reporting: Right-click on field in Grid Editor does not work]]
* [[Reporting: Running reports that span daylight savings time changes]]
* [[Reporting: Super Header does not appear in the report viewer]]
* [[Reporting: The Imported Report is Associated with the Wrong Data Source]]

==== Schedules ====
* [[Schedules: A scheduled job is unable to process at the scheduled time]]
* [[Schedules: The Schedule option is disabled when I right-click a report name]]
* [[Schedules: I do not see all scheduled reports on the Schedule List page]]
==== Security Center ====
* [[Security Center: Updating User Roles]]

==== Value Lists and Collections ====
* [[Value Lists and Collections: Cannot refresh value list]]
* [[Value Lists and Collections: Wildcard Collections and Java Regex Expressions]]

= Administration (OAMP)=

==== Admin User Management ====
==== Command Line Interface ====
==== Control Center ====
==== Device Configuration ====
==== License Management ====
==== Log and Trace Settings ====
==== RTMT ====
==== SNMP ====
==== Unified CCE User Integration ====

Reporting Configuration: Configure LDAP/AD

2010-09-21T09:01:31Z

Rpandara:

'''This page has been moved to [http://docwiki.cisco.com/wiki/Reporting_Configuration:_Configure_LDAP_%28Active_Directory%29_for_user_authentication Reporting Configuration: Configure LDAP (Active Directory) for user authentication]'''

Troubleshooting Tips for Unified IC 8.0

2010-09-21T08:54:55Z

Rpandara: /* Reporting Configuration */

'''Back:''' [[Troubleshooting Unified Intelligence Center]]

'''Add tip:''' [[Create Troubleshooting Tips]]

The following tips were added by Cisco Documentation:

= Installation =
* [[Installation: Locating Installation Log Files]]
= System =
* [[System: Checking Replication Status]]
* [[System: Checking the status of services]]
* [[System: Deleting the NTP Server in Cisco Unified OS Administration ]]
* [[System: Low Disk Space error at login to the Administation application]]
* [[System: Two Users on the Same Client Must use Different Browsers]]

= Reporting=
==== Accessibility ====
* [[Accessibility: Selecting items on a dropdown using the keyboard ]]
* [[Accessibility: JAWS Screenreader and Category "trees" ]]
* [[Accessibility: JAWS Screenreader Shortens Button Names to First Letter]]

==== Charts and Gauges ====
* [[Charts and Gauges: Gauge value update failed. The footer is null or not a number. ]]
* [[Charts and Gauges: Printing]]
* [[Charts and Gauges: The Report View is Blank]]
* [[Charts and Gauges: The Chart Save Fails]]
* [[Charts and Gauges: Unexpected JavaScript exception]]
==== Dashboards ====
* [[Dashboards: Creating URL Items with Invalid URLs]]
==== Data Sources ====
* [[Data Sources: Causes of database connection failure]]
==== Report Definitions ====
* [[Report Definitions: Changing Display Name does not Change Display Name in the Report View ]]
==== Reports ====
* [[Reports: Export Errors]]
* [[Reports: Field content in wrapping in grid view]]
* [[Reports: Import button is disabled]]
* [[Reports: Import errors]]
* [[Reporting: Right-click on field in Grid Editor does not work]]
* [[Reporting: Running reports that span daylight savings time changes]]
* [[Reporting: Super Header does not appear in the report viewer]]
* [[Reporting: The Imported Report is Associated with the Wrong Data Source]]

==== Schedules ====
* [[Schedules: A scheduled job is unable to process at the scheduled time]]
* [[Schedules: The Schedule option is disabled when I right-click a report name]]
* [[Schedules: I do not see all scheduled reports on the Schedule List page]]
==== Security Center ====
* [[Security Center: Updating User Roles]]
==== User Interface and Sign on ====
==== Value Lists and Collections ====
* [[Value Lists and Collections: Cannot refresh value list]]

= Administration (OAMP)=

==== Admin User Management ====
==== Command Line Interface ====
==== Control Center ====
==== Device Configuration ====
==== License Management ====
==== Reporting Configuration ====
* [[Reporting Configuration: Change LDAP/AD]]
* [[Reporting Configuration: Configure LDAP (Active Directory) for user authentication]]

==== Log and Trace Settings ====
==== RTMT ====
==== SNMP ====
==== Unified CCE User Integration ====

Reporting Configuration: Configure LDAP/AD

2010-09-21T08:54:34Z

Rpandara: Removing all content from page

Reporting Configuration: Configure LDAP (Active Directory) for user authentication

2010-09-21T08:52:23Z

Rpandara:

== Configure LDAP (Active Directory) for user authentication ==

{| border="1"
|-
! '''Problem Summary'''
| Domain user cannot log in through LDAP server
|-
! '''Error Message'''
| Invalid username or password. Please try again.
|-
! '''Possible Cause'''
| The LDAP parameters are incorrect or incomplete
|-
! '''Recommended Action'''
|Sample parameters:
Host Address for Active Directory Server: 192.168.1.2
port: 389
"Use SSL" is not checked
Host Address for Redundant Active Directory Server:
Manager Distinguished Name: CN=Administrator, CN=Users, DC=myCompany, DC=com
Manager Password: <password for user administrator>
User Search Base: CN=Users, DC=myCompany, DC=com
Attribute for User ID: sAMAccountName

Sample value 2 for Manager Distinguished Name: CN=user1,OU=icm8,OU=UCCE80,OU=Cisco_ICM_domain,DC=UCCE80,DC=cisco,DC=com
Sample value 3 for Manager Distinguished Name: CN=testuser,OU=Employees,OU=Cisco Users,DC=cisco,DC=com

Tip 1: The values of OU could be case sensitive.
Tip 2: The max number of characters for Manager Distinguished Name field cannot exceed 85.

'''Action Plan-1:''' Verify following in CUIC setup
1. Verify the users credentials are correct in Active Directory
2. Verify the user is logging in with the correct Domain pre-pended to their Active Directory username. Verify they have not been locked out in Active Directory for too many failed login attempts.
3. Verify that the Active Directory server configured in OAMP is the same one used by UCCE/ICM. Verify the Manager Distinguished Name has the correct Domain name as that used by the ICM Server: CN=Administrator, CN=users, DC=MYDOMAIN, DC=COM

'''Action Plan-2:''' If Domain user is not able to login to CUIC yet, do the following:

Step-1: In OAMP Active Directory configuration page, check if User Search Base has 'CN=Users' in it. This is needed except incase User Search Base is already CN=Domain Users. Try To login to CUIC with supervisor name prepended with proper domain name
Step-2: If Step-1 doesn’t work, If user is not able to login still, modify to 'CN=Domain Users' in User Search Base and try to login
Step-3: If Step-2 doesn’t work, change following
Attribute for User ID = userPrincipalName
User Search Base search base, modify to = CN=Domain Users
And then try to login to CUIC with user id as testuser@bioscripinc.net (for this to work Ldap should be configured to accept both UserPrincipleName for login)

'''If AD user is still not able to login
'''
1.Login to Active directory using 'Active Directory Explorer by Microsoft' or Softerra LDAP browser
2.Navigate to the AD account name
3.Look for attribute distinguishedName, it would be something like "CN=UserName,DC=Users,DC=CompanyName,DC=COM...."
4.Copy every thing from distinguishedName except CN=UserName to 'User Search Base' element in OAMP Active directory configuration page
5.Make 'User ID Attribute' to userPrincipleName and from LDAP browser findout the userPrincipleName Attibute
Use the same thing to login to CUIC, login name would be like testuser@company.com
6.If user is not able to login to CUIC, then problem might be with Active directory LDAP authentication, then
Make 'User ID Attribute' to samAccountName and from LDAP browser find out the samAccountName Attibute
Use the same thing to login to CUIC, login name would be like 'company\testuser'

|-
! '''Release'''
| Release 8.0(1)
|-
! '''Associated CDETS#/ Similar SRs '''
| 614786193,615387559,614830251, cdets-defectid:CSCth62535 '''
|-
|}
[[Category:Unified IC, Release 8.0]]

Reporting Configuration: Change LDAP/AD

2010-09-21T08:51:58Z

Rpandara:

== Change the current LDAP (Active Directory) to a different one ==

{| border="1"
|-
! '''Problem Summary'''
| To Change the current LDAP/AD to a different one causes a number of issues:
|-
! '''Error Message'''
| Warning: You have changed the LDAP server configuration which will impact user logons, access to reports, dashboards, collections and other objects created by users not in the new LDAP server and may affect users synchronization. Are you sure you want to make the change?
|-
! '''Possible Cause'''
| When CUIC changes its LDAP parameters, it will change the CUIC user authentication provider. The following issues may affect the CUIC server:
1) All domain users which were authenticated by the old LDAP/AD server will not be able to log in any more.
2) All the CUIC objects created/owned by those domain users will become orphans. i.e. The objects' original owners cannot modify or delete them since they cannot log in.
3) If originally UCCE user synchronization is enabled and the old LDAP server is the one used by the original UCCE supervisors, the new LDAP server will be out of sync with the original UCCE. And all users and collections created through UCCE synchronization will be orphans as well.
|-
! '''Recommended Action'''
| Make sure the change of LDAP server is necessary. If so, click "OK", otherwise, click "Cancel".
Once the LDAP server change is made, CUIC security admin user should "clean" up the orphan objects. Please follow this order when deleting these objects:
a) All the dashboards created by those orphan users.
b) All the dashboard categories created by those orphan users.
c) All the collections created by those orphan users or created by UCCE synchronization.
d) All the value lists created by those orphan users.
e) All the reports created by those orphan users.
f) All the report categories created by those orphan users.
g) All the report definitions created by those orphan users.
h) All the report definition categories created by those orphan users.
a) All the data sources created by those orphan users and not useful any more.
b) All those orphan users.
'''Note''':
i) If any object that is created by those orphan users is still used or referenced by other CUIC users, you can either recreate it or by editing and save as to a different object, and you have to reset the appropriate sharing permissions.
ii) You cannot delete a CUIC object if it is still referenced by any other object.
iii) You cannot delete a CUIC user if any object that created by the user still exists in CUIC database.
iv) When deleting a category, make sure all the subcategories, and all the objects in the category and subcategories are the ones that need be deleted. Once a CUIC object is deleted, there is no way to undelete !!

|-
! '''Release'''
| Release 8.0(2)
|-
! '''Associated CDETS #'''
| CSCtf76504'''
|-
|}
[[Category:Unified IC, Release 8.0]]

Reporting Configuration: Configure LDAP/AD

2010-09-21T08:51:01Z

Rpandara:

Reporting Configuration: Configure LDAP (Active Directory) for user authentication

2010-09-21T08:00:24Z

Rpandara: New page: == Configure LDAP (Active Directory) for user authentication == {| border="1" |- ! '''Problem Summary''' | Domain user cannot log in through LDAP server |- ! '''Error Message''' | Invali...

Troubleshooting Tips for Unified IC 8.0

2010-09-21T07:59:09Z

Rpandara: /* Reporting Configuration */

'''Back:''' [[Troubleshooting Unified Intelligence Center]]

'''Add tip:''' [[Create Troubleshooting Tips]]

The following tips were added by Cisco Documentation:

= Installation =
* [[Installation: Locating Installation Log Files]]
= System =
* [[System: Checking Replication Status]]
* [[System: Checking the status of services]]
* [[System: Deleting the NTP Server in Cisco Unified OS Administration ]]
* [[System: Low Disk Space error at login to the Administation application]]
* [[System: Two Users on the Same Client Must use Different Browsers]]

= Reporting=
==== Accessibility ====
* [[Accessibility: Selecting items on a dropdown using the keyboard ]]
* [[Accessibility: JAWS Screenreader and Category "trees" ]]
* [[Accessibility: JAWS Screenreader Shortens Button Names to First Letter]]

==== Charts and Gauges ====
* [[Charts and Gauges: Gauge value update failed. The footer is null or not a number. ]]
* [[Charts and Gauges: Printing]]
* [[Charts and Gauges: The Report View is Blank]]
* [[Charts and Gauges: The Chart Save Fails]]
* [[Charts and Gauges: Unexpected JavaScript exception]]
==== Dashboards ====
* [[Dashboards: Creating URL Items with Invalid URLs]]
==== Data Sources ====
* [[Data Sources: Causes of database connection failure]]
==== Report Definitions ====
* [[Report Definitions: Changing Display Name does not Change Display Name in the Report View ]]
==== Reports ====
* [[Reports: Export Errors]]
* [[Reports: Field content in wrapping in grid view]]
* [[Reports: Import button is disabled]]
* [[Reports: Import errors]]
* [[Reporting: Right-click on field in Grid Editor does not work]]
* [[Reporting: Running reports that span daylight savings time changes]]
* [[Reporting: Super Header does not appear in the report viewer]]
* [[Reporting: The Imported Report is Associated with the Wrong Data Source]]

==== Schedules ====
* [[Schedules: A scheduled job is unable to process at the scheduled time]]
* [[Schedules: The Schedule option is disabled when I right-click a report name]]
* [[Schedules: I do not see all scheduled reports on the Schedule List page]]
==== Security Center ====
* [[Security Center: Updating User Roles]]
==== User Interface and Sign on ====
==== Value Lists and Collections ====
* [[Value Lists and Collections: Cannot refresh value list]]

= Administration (OAMP)=

==== Admin User Management ====
==== Command Line Interface ====
==== Control Center ====
==== Device Configuration ====
==== License Management ====
==== Reporting Configuration ====
* [[Reporting Configuration: Configure LDAP/AD]]
* [[Reporting Configuration: Change LDAP/AD]]
* [[Reporting Configuration: Configure LDAP (Active Directory) for user authentication]]

==== Log and Trace Settings ====
==== RTMT ====
==== SNMP ====
==== Unified CCE User Integration ====

Reporting: Data Source Failover

2010-09-06T07:49:39Z

Rpandara: New page: {{Template:Required Metadata}} == Reporting: Data Source Failover == {| border="1" |- ! '''Problem Summary''' | The data source from which a report retrieves information becomesunavailabl...

{{Template:Required Metadata}}
== Reporting: Data Source Failover ==

{| border="1"
|-
! '''Problem Summary'''
| The data source from which a report retrieves information becomesunavailable (for example, if the HDS on Unified ICM Side A is down).
|-
! '''Error Message'''
| Not applicable.
|-
! '''Possible Cause'''
| The system cannot find the license file or the license file cannot be opened.
|-
! '''Recommended Action'''
| 1. Select '''Administrative''' > '''Data Sources''' to open the '''Data Sources''' window.

2. Select the data source and click '''Edit''' to open the '''Edit Data Source''' window.

3. Edit the Server (IP or DNS: port) field to enter an IP address for an available data source.

4. Click '''Test Connection'''.
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Troubleshooting Tips for Unified IS 7.5

2010-09-06T06:48:57Z

Rpandara:

'''Back:''' [[Troubleshooting Unified Intelligence Suite]]

'''Add tip:''' [[Create Troubleshooting Tips]]

The following tips were added by Cisco Documentation:

= Archiver=
:* [[Archiver: Data Retrieval]]
:* [[Archiver: Free Space and Emergency Purge]]
:* [[Archiver: How to Point to Another Server]]
:* [[Archiver: Load Archiver Fails]]
:* [[Archiver: LoadArchiver Fails with "Primary key constraint violations"]]
:* [[Archiver: Performance and Memory Space]]
:* [[Archiver: Scheduled Events Do Not Run]]

= Configuration=
:* [[Configuration: Configuring IIS Failed]]
:* [[Configuration: Configuring the CUIC Scheduler Service Failed]]
:* [[Configuration: Creating CUIC Database Failed]]
:* [[Configuration: Port 80 Error]]
:* [[Configuration: Server Not Responding to Ping Command]]
:* [[Configuration: Setting Folder Permissions Failed]]
:* [[Configuration: Setting Up Permissions for CUIS SQL Server Login Failed]]

= Installation=
:* [[Installation: SQL Hardening]]

= Licensing=
:* [[Licensing: Exceeded the Number of Licensed Users]]
:* [[Licensing: Error Code in Event Viewer: -1]]
:* [[Licensing: Error Code in Event Viewer: -2]]
:* [[Licensing: Error Code in Event Viewer: -4]]

= Logging In=
:* [[Logging In: Cannot Access CUIS Using IP Address]]
:* [[Logging In: User Cannot log In]]

= Reporting =
:* [[Reporting: Connection Dropped Message]]
:* [[Reporting: Data Source Failover]]
:* [[Reporting: Deleting Users]]
:* [[Reporting: Effect of IIS Recycle on Reports]]
:* [[Reporting: SQL Validation for Unified IC]]
:* [[Reporting: Error while rendering reports]]

= System =
:* [[System: Location of Unified IC Files]]
:* [[System: Purge the CUIC Database]]
:* [[System: Release Notes for Maintenance Releases]]
:* [[System: Retrieve Size for CUIC Database Tables]]
:* [[System: SQL Hardening Failure]]

= Upgrading =
:* [[Upgrading : Scheduler does not start after an upgrade]]

Logging In: User Cannot log In

2010-09-06T06:41:37Z

Rpandara: New page: {{Template:Required Metadata}} == Logging In: User Cannot Log In == {| border="1" |- ! '''Problem Summary''' | User is not able to log in to the Unified IS system. |- ! '''Error Message''...

{{Template:Required Metadata}}
== Logging In: User Cannot Log In ==

{| border="1"
|-
! '''Problem Summary'''
| User is not able to log in to the Unified IS system.
|-
! '''Error Message'''
| Not applicable.
|-
! '''Possible Cause'''
| This can happen because of any of the following reasons:
- User is not a member of the CUISLocalUserGroup.

- The environment requires a domain name or machine name at login, that was not specified.
|-
! '''Recommended Action'''
| Make sure the user has been added as a member of the CUISLocalUserGroup. For more information, see Adding Unified IC Users section in the Intelligence Center User Guide For Cisco Unified Intelligence Suite 7.5(x).
If the environment requires a domain name or machine name, make sure it is prepended to the user name (AD_NAME\user01).
If you are prompted with an ActiveDirectory login prompt, re-enter your Windows login information.
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Logging In: Cannot Access CUIS Using IP Address

2010-09-06T06:35:42Z

Rpandara: New page: {{Template:Required Metadata}} == Logging In: Cannot Access CUIS Using IP Address == {| border="1" |- ! '''Problem Summary''' | You are not able to access the Unified IC server using the ...

{{Template:Required Metadata}}
== Logging In: Cannot Access CUIS Using IP Address ==

{| border="1"
|-
! '''Problem Summary'''
| You are not able to access the Unified IC server using the URL http://<CUIC Server IP>.
|-
! '''Error Message'''
| Not applicable.
|-
! '''Possible Cause'''
| The browser is using a proxy server.
|-
! '''Recommended Action'''
| If the browser is using a proxy server, you need exclude the Unified IC IP address from Proxy settings.
To do this:

1. In your browser window, select '''Tools''', '''Internet Options'''.

2. Click the '''Connections''' tab. Then click '''LAN Settings'''.

3. In the '''LAN settings''' windows, '''Proxy server''' section, click '''Advanced'''.

4. In the '''Exceptions''' section, type in the IP address for Unified IC.

5. Click '''OK''' to close all open windows.

5. Reload ''http://<CUIC Server IP>''.

|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Troubleshooting Tips for Unified IS 7.5

2010-09-06T06:29:27Z

Rpandara:

'''Back:''' [[Troubleshooting Unified Intelligence Suite]]

'''Add tip:''' [[Create Troubleshooting Tips]]

The following tips were added by Cisco Documentation:

= Archiver=
:* [[Archiver: Data Retrieval]]
:* [[Archiver: Free Space and Emergency Purge]]
:* [[Archiver: How to Point to Another Server]]
:* [[Archiver: Load Archiver Fails]]
:* [[Archiver: LoadArchiver Fails with "Primary key constraint violations"]]
:* [[Archiver: Performance and Memory Space]]
:* [[Archiver: Scheduled Events Do Not Run]]

= Configuration=
:* [[Configuration: Configuring IIS Failed]]
:* [[Configuration: Configuring the CUIC Scheduler Service Failed]]
:* [[Configuration: Creating CUIC Database Failed]]
:* [[Configuration: Port 80 Error]]
:* [[Configuration: Server Not Responding to Ping Command]]
:* [[Configuration: Setting Folder Permissions Failed]]
:* [[Configuration: Setting Up Permissions for CUIS SQL Server Login Failed]]

= Installation=
:* [[Installation: SQL Hardening]]

= Licensing=
:* [[Licensing: Exceeded the Number of Licensed Users]]
:* [[Licensing: Error Code in Event Viewer: -1]]
:* [[Licensing: Error Code in Event Viewer: -2]]
:* [[Licensing: Error Code in Event Viewer: -4]]

= Logging In=
:* [[Logging In: Cannot Access CUIS Using IP Address]]
:* [[Logging In: User Cannot log In]]

= Reporting =
:* [[Reporting: Connection Dropped Message]]
:* [[Reporting: Deleting Users]]
:* [[Reporting: Effect of IIS Recycle on Reports]]
:* [[Reporting: SQL Validation for Unified IC]]
:* [[Reporting: Error while rendering reports]]

= System =
:* [[System: Location of Unified IC Files]]
:* [[System: Purge the CUIC Database]]
:* [[System: Release Notes for Maintenance Releases]]
:* [[System: Retrieve Size for CUIC Database Tables]]
:* [[System: SQL Hardening Failure]]

= Upgrading =
:* [[Upgrading : Scheduler does not start after an upgrade]]

Licensing: Error Code in Event Viewer: -4

2010-09-06T05:41:07Z

Rpandara: New page: {{Template:Required Metadata}} == Licensing: Error Code in Event Viewer: -4 == {| border="1" |- ! '''Problem Summary''' | Event viewer displays error code(-4) indicating that the system h...

{{Template:Required Metadata}}
== Licensing: Error Code in Event Viewer: -4 ==

{| border="1"
|-
! '''Problem Summary'''
| Event viewer displays error code(-4) indicating that the system has reached the licensed number of users already.
|-
! '''Error Message'''
| Not applicable.
|-
! '''Possible Cause'''
| Lab license only, the system may display this error code in the event viewer if the system has reached the licensed number of users.
|-
! '''Recommended Action'''
| NFR/LAB license is limited to 5 users.Contact Cisco to purchase an ENTERPRISE license.
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Licensing: Error Code in Event Viewer: -2

2010-09-06T05:37:57Z

Rpandara: New page: {{Template:Required Metadata}} == Licensing: Error Code in Event Viewer: -2 == {| border="1" |- ! '''Problem Summary''' | Event viewer displays error code(-2) indicating that license file...

{{Template:Required Metadata}}
== Licensing: Error Code in Event Viewer: -2 ==

{| border="1"
|-
! '''Problem Summary'''
| Event viewer displays error code(-2) indicating that license file syntax is invalid.
|-
! '''Error Message'''
| Not applicable.
|-
! '''Possible Cause'''
| The system cannot apply the license because license file syntax is invalid.
|-
! '''Recommended Action'''
| 1) Feature name is >MAX_FEATURE_LEN, or daemon name is > MAX_DAEMON_LEN, or server name is >MAX_SERVER_NAME, or a feature specifies no hostid and # of licenses is <= 0.

2) Verify that license file has not been altered/modified or has an extra carriage return at the end.
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Licensing: Error Code in Event Viewer: -1

2010-09-06T05:33:35Z

Rpandara: New page: {{Template:Required Metadata}} == Licensing: Error Code in Event Viewer: -1 == {| border="1" |- ! '''Problem Summary''' | Event viewer displays error code(-1) indicating that the system c...

{{Template:Required Metadata}}
== Licensing: Error Code in Event Viewer: -1 ==

{| border="1"
|-
! '''Problem Summary'''
| Event viewer displays error code(-1) indicating that the system cannot find license file or the license file cannot be opened.
|-
! '''Error Message'''
| Not applicable.
|-
! '''Possible Cause'''
| The system cannot find the license file or the license file cannot be opened.
|-
! '''Recommended Action'''
| 1) Verify that the '''%CUIS_HOME%''' environment variable is set.

2) Verify that ''license.lic'' exists and is in '''%CUIS_HOME%/license''' directory.

3) Verify that the system or IIS has been restarted after it has been configured to allow environment variable to propagate to IIS.
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Troubleshooting Tips for Unified IS 7.5

2010-09-06T05:29:15Z

Rpandara: /* Licensing */

'''Back:''' [[Troubleshooting Unified Intelligence Suite]]

'''Add tip:''' [[Create Troubleshooting Tips]]

The following tips were added by Cisco Documentation:

= Archiver=
:* [[Archiver: Data Retrieval]]
:* [[Archiver: Free Space and Emergency Purge]]
:* [[Archiver: How to Point to Another Server]]
:* [[Archiver: Load Archiver Fails]]
:* [[Archiver: LoadArchiver Fails with "Primary key constraint violations"]]
:* [[Archiver: Performance and Memory Space]]
:* [[Archiver: Scheduled Events Do Not Run]]

= Configuration=
:* [[Configuration: Configuring IIS Failed]]
:* [[Configuration: Configuring the CUIC Scheduler Service Failed]]
:* [[Configuration: Creating CUIC Database Failed]]
:* [[Configuration: Port 80 Error]]
:* [[Configuration: Server Not Responding to Ping Command]]
:* [[Configuration: Setting Folder Permissions Failed]]
:* [[Configuration: Setting Up Permissions for CUIS SQL Server Login Failed]]

= Installation=
:* [[Installation: SQL Hardening]]

= Licensing=
:* [[Licensing: Exceeded the Number of Licensed Users]]
:* [[Licensing: Error Code in Event Viewer: -1]]
:* [[Licensing: Error Code in Event Viewer: -2]]
:* [[Licensing: Error Code in Event Viewer: -4]]

= Reporting =
:* [[Reporting: Connection Dropped Message]]
:* [[Reporting: Deleting Users]]
:* [[Reporting: Effect of IIS Recycle on Reports]]
:* [[Reporting: SQL Validation for Unified IC]]
:* [[Reporting: Error while rendering reports]]

= System =
:* [[System: Location of Unified IC Files]]
:* [[System: Purge the CUIC Database]]
:* [[System: Release Notes for Maintenance Releases]]
:* [[System: Retrieve Size for CUIC Database Tables]]
:* [[System: SQL Hardening Failure]]

= Upgrading =
:* [[Upgrading : Scheduler does not start after an upgrade]]

Licensing: Exceeded the Number of Licensed Users

2010-09-06T05:27:01Z

Rpandara: New page: {{Template:Required Metadata}} == Licensing: Exceeded the Number of Licensed Users == {| border="1" |- ! '''Problem Summary''' | The system displays an error message that you have exceede...

{{Template:Required Metadata}}
== Licensing: Exceeded the Number of Licensed Users ==

{| border="1"
|-
! '''Problem Summary'''
| The system displays an error message that you have exceeded the allowed number of concurrent licensed users.
|-
! '''Error Message'''
| You have exceeded the allowed number of concurrent licensed users.
|-
! '''Possible Cause'''
| Some users may be having more than one browser sessions open.
|-
! '''Recommended Action'''
| Stop and restart IIS on the web server.
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Troubleshooting Tips for Unified IS 7.5

2010-09-06T05:05:54Z

Rpandara:

'''Back:''' [[Troubleshooting Unified Intelligence Suite]]

'''Add tip:''' [[Create Troubleshooting Tips]]

The following tips were added by Cisco Documentation:

= Archiver=
:* [[Archiver: Data Retrieval]]
:* [[Archiver: Free Space and Emergency Purge]]
:* [[Archiver: How to Point to Another Server]]
:* [[Archiver: Load Archiver Fails]]
:* [[Archiver: LoadArchiver Fails with "Primary key constraint violations"]]
:* [[Archiver: Performance and Memory Space]]
:* [[Archiver: Scheduled Events Do Not Run]]

= Configuration=
:* [[Configuration: Configuring IIS Failed]]
:* [[Configuration: Configuring the CUIC Scheduler Service Failed]]
:* [[Configuration: Creating CUIC Database Failed]]
:* [[Configuration: Port 80 Error]]
:* [[Configuration: Server Not Responding to Ping Command]]
:* [[Configuration: Setting Folder Permissions Failed]]
:* [[Configuration: Setting Up Permissions for CUIS SQL Server Login Failed]]

= Installation=
:* [[Installation: SQL Hardening]]

= Licensing=
:* [[Licensing: Exceeded the Number of Licensed Users]]
:* [[Licensing: Error Code (-1] in Event Viewer]]
:* [[Licensing: Error Code (-2] in Event Viewer]]
:* [[Licensing: Error Code (-4] in Event Viewer]]

= Reporting =
:* [[Reporting: Connection Dropped Message]]
:* [[Reporting: Deleting Users]]
:* [[Reporting: Effect of IIS Recycle on Reports]]
:* [[Reporting: SQL Validation for Unified IC]]
:* [[Reporting: Error while rendering reports]]

= System =
:* [[System: Location of Unified IC Files]]
:* [[System: Purge the CUIC Database]]
:* [[System: Release Notes for Maintenance Releases]]
:* [[System: Retrieve Size for CUIC Database Tables]]
:* [[System: SQL Hardening Failure]]

= Upgrading =
:* [[Upgrading : Scheduler does not start after an upgrade]]

Troubleshooting Tips for Unified IS 7.5

2010-09-03T08:48:19Z

Rpandara:

'''Back:''' [[Troubleshooting Unified Intelligence Suite]]

'''Add tip:''' [[Create Troubleshooting Tips]]

The following tips were added by Cisco Documentation:

= Archiver=
:* [[Archiver: Data Retrieval]]
:* [[Archiver: Free Space and Emergency Purge]]
:* [[Archiver: How to Point to Another Server]]
:* [[Archiver: Load Archiver Fails]]
:* [[Archiver: LoadArchiver Fails with "Primary key constraint violations"]]
:* [[Archiver: Performance and Memory Space]]
:* [[Archiver: Scheduled Events Do Not Run]]

= Configuration=
:* [[Configuration: Configuring IIS Failed]]
:* [[Configuration: Configuring the CUIC Scheduler Service Failed]]
:* [[Configuration: Creating CUIC Database Failed]]
:* [[Configuration: Port 80 Error]]
:* [[Configuration: Server Not Responding to Ping Command]]
:* [[Configuration: Setting Folder Permissions Failed]]
:* [[Configuration: Setting Up Permissions for CUIS SQL Server Login Failed]]

= Installation=
:* [[Installation: SQL Hardening]]

= Reporting =
:* [[Reporting: Connection Dropped Message]]
:* [[Reporting: Deleting Users]]
:* [[Reporting: Effect of IIS Recycle on Reports]]
:* [[Reporting: SQL Validation for Unified IC]]
:* [[Reporting: Error while rendering reports]]

= System =
:* [[System: Location of Unified IC Files]]
:* [[System: Purge the CUIC Database]]
:* [[System: Release Notes for Maintenance Releases]]
:* [[System: Retrieve Size for CUIC Database Tables]]
:* [[System: SQL Hardening Failure]]

= Upgrading =
:* [[Upgrading : Scheduler does not start after an upgrade]]

Configuration: Setting Up Permissions for CUIS SQL Server Login Failed

2010-09-03T08:47:52Z

Rpandara: New page: {{Template:Required Metadata}} == Configuration: Setting Up Permissions for CUIS SQL Server Login Failed == {| border="1" |- ! '''Problem Summary''' | Setting Up Permissions for CUIS SQL ...

{{Template:Required Metadata}}
== Configuration: Setting Up Permissions for CUIS SQL Server Login Failed ==

{| border="1"
|-
! '''Problem Summary'''
| Setting Up Permissions for CUIS SQL Server Login Failed
|-
! '''Error Message'''
| Setting Up Permissions for CUIS SQL Server Login Failed
|-
! '''Possible Cause'''
| The CUIS Configuration program did not create the SQL login with the necessary permissions.
|-
! '''Recommended Action'''
| If you see this message, look at the CuisConfigTool.Log file and make every effort to resolve the error based on the information in that file.
Only if it is not possible to resolve the matter from information in the CuisConfigTool log, manually create a login as follows:

1. Open MS SQL Server.
Make sure you are connected as a user who is an administrator in SQL Server and to the master database.

2. Open a '''New Query''' window.

3. Type the following: '''CREATE LOGIN "<domain>\<username>" FROM WINDOWS'''
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Configuration: Setting Folder Permissions Failed

2010-09-03T08:42:09Z

Rpandara: New page: {{Template:Required Metadata}} == Configuration: Setting Folder Permissions Failed== {| border="1" |- ! '''Problem Summary''' | Failed to set the CUIS folder permissions. |- ! '''Error Me...

{{Template:Required Metadata}}
== Configuration: Setting Folder Permissions Failed==

{| border="1"
|-
! '''Problem Summary'''
| Failed to set the CUIS folder permissions.
|-
! '''Error Message'''
| Setting Folder Permissions Failed
|-
! '''Possible Cause'''
| The configuration program did not set the folder permissions.
|-
! '''Recommended Action'''
| If you see this message, look at the CuisConfigTool.Log file and make every effort to resolve the error based on the information in that file.
Only if it is not possible to resolve the matter from information in the CuisConfigTool log, set folder permissions as follows:

1. In Windows Explorer, navigate to the directory where the web application is stored(''<CUIS_HOME>\CuisWeb'').

2. Make sure that the only permissions that this folder has are the following. (''Permissions should apply to the directory and to all subdirectories and files within it.'')

– For users in the '''CuisLocalUserGroup''': ''read'', ''read and execute'', and ''list directory contents''.

– For users in the '''Administrators group''': ''full control''.

– For the '''CUIC windows user''': ''read'', ''write'', ''execute'', and ''list directory contents''.
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Configuration: Server Not Responding to Ping Command

2010-09-03T08:35:58Z

Rpandara: New page: {{Template:Required Metadata}} == Configuration: Server Not Responding to Ping Command == {| border="1" |- ! '''Problem Summary''' | There are several configuration actions that direct th...

{{Template:Required Metadata}}
== Configuration: Server Not Responding to Ping Command ==

{| border="1"
|-
! '''Problem Summary'''
| There are several configuration actions that direct the Configuration tool to ping a server. At times, you may receive an error message that indicates that a server did not respond to the Ping command.
|-
! '''Error Message'''
| Server did not respond to the ping command.
|-
! '''Possible Cause'''
| The server might have ping disabled.
|-
! '''Recommended Action'''
| It is safe to ignore these messages, as the Ping is done only to detect typos in the entry of thehost name.
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Configuration: Port 80 Error

2010-09-03T08:31:01Z

Rpandara: New page: {{Template:Required Metadata}} == Configuration: Port 80 Error== {| border="1" |- ! '''Problem Summary''' | During the Web Server configuration, you will see this error if Port 80 is alre...

{{Template:Required Metadata}}
== Configuration: Port 80 Error==

{| border="1"
|-
! '''Problem Summary'''
| During the Web Server configuration, you will see this error if Port 80 is already being used.
|-
! '''Error Message'''
| Port 80 Error
|-
! '''Possible Cause'''
| Port 80 is already being used by the Default Web Site that the IIS installs.
|-
! '''Recommended Action'''
| 1. Navigate to Internet Information Services. ('''My Computer''' > '''Manage''' > '''Service and Applications''' > '''IIS''' > '''Web sites''').

2. Right-click the Default Web site and select '''Properties'''.

3. Change the '''TCP port number''' to something other than 80. Then click '''OK'''.
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Configuration: Creating CUIC Database Failed

2010-09-03T08:26:57Z

Rpandara: New page: {{Template:Required Metadata}} == Configuration: Creating CUIC Database Failed== {| border="1" |- ! '''Problem Summary''' | Failed to create the CUIC database |- ! '''Error Message''' | N...

{{Template:Required Metadata}}
== Configuration: Creating CUIC Database Failed==

{| border="1"
|-
! '''Problem Summary'''
| Failed to create the CUIC database
|-
! '''Error Message'''
| Not applicable.
|-
! '''Possible Cause'''
| The SQL script did not auto run or the database was not created for some other reason.
|-
! '''Recommended Action'''
| If you see this message, look at the CuisConfigTool.Log file and make every effort to resolve the error based on the information in that file.
Only if it is not possible to resolve the matter from information in the CuisConfigTool log, you can manually run the SQL script as follows:

1. Open '''MS SQL Server'''. Make sure you are connected as a user who has administrative rights in the SQL Server and on the master database.

2. Open a '''New Query''' window.

3. Copy and paste the contents of the following file into the query window:''<CUIS_HOME>\CuisSqlScripts\CUIC\CUIC_DB_INSTALL.SQL''.

4. Do a search-and-replace on the text that was pasted from the file. Search for ''cuic_data'',and replace with ''cuic_data_<ip or hostname of CUIC web server>''.

5. Execute the query.

6. Open '''Object Explorer''' > '''Databases''' to verify that the database was created.
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Configuration: Configuring the CUIC Scheduler Service Failed

2010-09-03T08:20:10Z

Rpandara: New page: {{Template:Required Metadata}} == Configuration: Configuring the CUIC Scheduler Service Failed == {| border="1" |- ! '''Problem Summary''' | Configuring the CUIC Scheduler Service Fails |...

{{Template:Required Metadata}}
== Configuration: Configuring the CUIC Scheduler Service Failed ==

{| border="1"
|-
! '''Problem Summary'''
| Configuring the CUIC Scheduler Service Fails
|-
! '''Error Message'''
| Configuring the CUIC Scheduler Service Failed
|-
! '''Possible Cause'''
| The CUIC Scheduler Service is not auto-configured
|-
! '''Recommended Action'''
| If you see this message, look at the CuisConfigTool.Log file and make every effort to resolvethe error based on the information in that file.
Only if it is not possible to resolve the matter from information in the CuisConfigTool log, configure the Scheduler as follows:

1. Open a command windows.

2. Go to the directory ''<CUIS_HOME>\CuisScheduler''.

3. Run the following command: '''installutil CuisScheduler.exe'''

4. From '''Windows Administrative Tools''' > '''Services''', ensure that this service is set to ''startup automatically''.

5. Set the configuration file. To do this, locate the '''CuisScheduler.exe.config''' file. It is in the same directory as the Schedulerservice executable.

6. Replace its contents with the contents of the web.config file located in ''<CUIS_HOME>\CuisWeb''.

7. Change the credentials under which the scheduler service runs.

8. Locate the CUIS Scheduler Service in the '''Services''' control panel.

9. Right-click the '''Service''' and select '''Properties'''.

10. In the '''LogOn''' tab, enter information so that the CUIS Scheduler Service runs with the credentials of the Unified IC internal user.

11. Start the Scheduler service.
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Configuration: Configuring IIS Failed

2010-09-03T06:31:25Z

Rpandara: New page: {{Template:Required Metadata}} == Configuration: Configuring IIS Failed == {| border="1" |- ! '''Problem Summary''' | During Unified IS configuration, you get an error message indicating ...

{{Template:Required Metadata}}
== Configuration: Configuring IIS Failed ==

{| border="1"
|-
! '''Problem Summary'''
| During Unified IS configuration, you get an error message indicating that the Configuration of Internet Information Services (IIS) server failed.
|-
! '''Error Message'''
| Configuring IIS failed.
|-
! '''Possible Cause'''
| IIS failed to add and configure CUIS as an application pool.
|-
! '''Recommended Action'''
| If you see this message, look at the CuisConfigTool.Log file and make every effort to resolvethe error based on the information in that file.
Only if it is not possible to resolve the matter from information in the CuisConfigTool log,manually configure IIS as follows:

1. Create an application pool. To do this, open the IIS management console. Right-click on '''Application Pools'''. Click '''New'''. Select '''Application Pool'''.

2. Enter the name as ''CUIS application pool''.

3. Leave the '''Use default settings for application pools''' radio buttons selected and click '''OK'''.

4. Right-click the new application pool and select '''Properties'''.

5. In the '''Identity''' tab, select the '''Configurable''' radio button and enter the credentials of the Unified IC internal user.

6. Create a web application. To do this, open the IIS management console. Right-click on '''Web Sites'''. Click '''New'''; then '''Web Site'''.

7. For '''Description''', enter '''CUIS Website'''.

8. For '''Path''', browse to the CuisWeb directory inside the ''<CUIS_HOME>'' directory.

9. For '''Allow Anonymous Access''', select False.

10. Allow the following permissions: '''Read''', '''Run Scripts''', '''Execute'''.

11. Accept the defaults for all other fields.

12. Right-click on the newly created web application and select '''Properties'''.

13. In the '''Home Directory''' tab, for the Application pool, select the '''CUIS application pool'''.

14. In the '''Directory Security''' tab, in '''Authentication and Access Control''', click '''Edit'''.

15. Check only the '''Integrated Windows Authentication''' checkbox.

16. Under '''Web Service Extensions''' in the IIS management console, make sure that ''ASP.NETv2.0.50727'' is allowed.

|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]

Troubleshooting Tips for Unified IS 7.5

2010-09-03T06:14:26Z

Rpandara:

'''Back:''' [[Troubleshooting Unified Intelligence Suite]]

'''Add tip:''' [[Create Troubleshooting Tips]]

The following tips were added by Cisco Documentation:

= Archiver=
:* [[Archiver: Data Retrieval]]
:* [[Archiver: Free Space and Emergency Purge]]
:* [[Archiver: How to Point to Another Server]]
:* [[Archiver: Load Archiver Fails]]
:* [[Archiver: LoadArchiver Fails with "Primary key constraint violations"]]
:* [[Archiver: Performance and Memory Space]]
:* [[Archiver: Scheduled Events Do Not Run]]

= Configuration=
:* [[Configuration: Configuring IIS Failed]]
:* [[Configuration: Configuring the CUIC Scheduler Service Failed]]
:* [[Configuration: Creating CUIC Database Failed]]
:* [[Configuration: Port 80 Error]]
:* [[Configuration: Rerunning the Configuration]]
:* [[Configuration: Server Not Responding to Ping Command]]
:* [[Configuration: Setting Folder Permissions Failed]]
:* [[Configuration: Setting Up Permissions for CUIS SQL Server Login Failed]]

= Installation=
:* [[Installation: SQL Hardening]]

= Reporting =
:* [[Reporting: Connection Dropped Message]]
:* [[Reporting: Deleting Users]]
:* [[Reporting: Effect of IIS Recycle on Reports]]
:* [[Reporting: SQL Validation for Unified IC]]
:* [[Reporting: Error while rendering reports]]

= System =
:* [[System: Location of Unified IC Files]]
:* [[System: Purge the CUIC Database]]
:* [[System: Release Notes for Maintenance Releases]]
:* [[System: Retrieve Size for CUIC Database Tables]]
:* [[System: SQL Hardening Failure]]

= Upgrading =
:* [[Upgrading : Scheduler does not start after an upgrade]]

Troubleshooting Tips for Unified IS 7.5

2010-09-03T06:13:20Z

Rpandara:

'''Back:''' [[Troubleshooting Unified Intelligence Suite]]

'''Add tip:''' [[Create Troubleshooting Tips]]

The following tips were added by Cisco Documentation:

= Archiver=
:* [[Archiver: Data Retrieval]]
:* [[Archiver: Free Space and Emergency Purge]]
:* [[Archiver: How to Point to Another Server]]
:* [[Archiver: Load Archiver Fails]]
:* [[Archiver: LoadArchiver Fails with "Primary key constraint violations"]]
:* [[Archiver: Performance and Memory Space]]
:* [[Archiver: Scheduled Events Do Not Run]]

= Configuration=
:* [[Configuration: Configuration Tool and Fully Qualified Domain Names]]
:* [[Configuration: Configuring IIS Failed]]
:* [[Configuration: Configuring the CUIC Scheduler Service Failed]]
:* [[Configuration: Creating CUIC Database Failed]]
:* [[Configuration: Port 80 Error]]
:* [[Configuration: Rerunning the Configuration]]
:* [[Configuration: Server Not Responding to Ping Command]]
:* [[Configuration: Setting Folder Permissions Failed]]
:* [[Configuration: Setting Up Permissions for CUIS SQL Server Login Failed]]

= Installation=
:* [[Installation: SQL Hardening]]

= Reporting =
:* [[Reporting: Connection Dropped Message]]
:* [[Reporting: Deleting Users]]
:* [[Reporting: Effect of IIS Recycle on Reports]]
:* [[Reporting: SQL Validation for Unified IC]]
:* [[Reporting: Error while rendering reports]]

= System =
:* [[System: Location of Unified IC Files]]
:* [[System: Purge the CUIC Database]]
:* [[System: Release Notes for Maintenance Releases]]
:* [[System: Retrieve Size for CUIC Database Tables]]
:* [[System: SQL Hardening Failure]]

= Upgrading =
:* [[Upgrading : Scheduler does not start after an upgrade]]

Installation: SQL Hardening

2010-09-03T06:02:59Z

Rpandara: New page: {{Template:Required Metadata}} == Installation: SQL Hardening == {| border="1" |- ! '''Problem Summary''' | During installation SQL hardening fails |- ! '''Error Message''' | Not applicab...

{{Template:Required Metadata}}
== Installation: SQL Hardening ==

{| border="1"
|-
! '''Problem Summary'''
| During installation SQL hardening fails
|-
! '''Error Message'''
| Not applicable.
|-
! '''Possible Cause'''
| It is possible for the Cisco Unified IC SQL Hardening to fail if it is preempted by yourorganization's SQL Hardening policy.
|-
! '''Recommended Action'''
| None. During the installation, SQL Hardening is applied to the Archiver and the CUIC databases. SQL Hardening is the process of allowing connection to SQL Server by Windows authenticationonly.
Should SQL Hardening fail for any reason, there is no effect on functionality.
In the of the failure of SQL Hardening, it will be possible to connect to SQL Server using both Windows authentication and SQL authentication.
|-
! '''Releases'''
| Release 7.5(x)
|-
! '''Associated CDETS #'''
| None
|-
|}

[[Category:Unified IS, Release 7.5]]