DocWiki - User contributions [en]

General: HTTP Status 500 message displays when opening Cisco MediaSense Administration after system restart

2012-09-27T17:59:36Z

Rshroyer: Removed link to wrong page in category area.

== HTTP Status 500 message displays when opening Cisco MediaSense Administration after system restart ==

{| border="1"
|-
! '''Problem Summary'''
| This exception message displays for the first few minutes after restarting Cisco MediaSense Release 9.0(1a) in a Cisco Services Ready Engine (SRE) deployment.
|-
! '''Error Message'''
| HTTP Status 500 The server encountered an internal error that prevented it from fulfilling this request.
|-
! '''Possible Cause'''
| Resources of an SRE are relatively limited and MediaSense runs much slower on them than on other types of nodes. Because of this some resources will not be ready for a few minutes.
|-
! '''Recommended Action'''
| Wait a few minutes and try again.
|-
! '''Release'''
| 9.0(1a)
|-
! '''Associated CDETS #'''
| None
|}
[[Category:Troubleshooting]]

Troubleshooting Tips for Cisco MediaSense

2012-09-26T19:30:01Z

Rshroyer: /* General */

'''Add Tip''': [[Create Contact Center Troubleshooting Tips|Create Troubleshooting Tip]]

'''Print PDF:''' [[Print Troubleshooting Tips for Cisco MediaSense]]

 

== API ==

*[http://docwiki-dev.cisco.com/wiki/API:_API_request_returns_Error_405#API.C2.A0request_returns.C2.A0Error_405:_Method_not_supported..C2.A0 API: API request returns Error 405: Method not supported]
*[[API: Incorrect participant duration]]
*[[API: MediaSense application sign-in fails with administration credentials]]
*[[API: Missing events and closed subscription]]
*[[API: Incorrect session or participant duration]]

== Administration ==

*[[Administration: Administration Login returns unexpected error]]
*[[Administration: Unable to access Administration and Serviceability UI on a newly installed system]]
*[[Administration: Unknown request error display]]
*[[Administration: Saving an AXL service provider configuration will result in an incorrect error message under certain pre-conditions]]

== Configuration ==

*[[Configuration: Call between two RT phones is not recorded]]
*[[Configuration: Calls using g.722 codec are not recorded]]
*[[Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers]]
*[[Configuration: Conversation after a transfer is not recorded on RT-Lite phones]]
*[[Configuration: Failure to playback audio or video when using RT video phone]]
*[[Configuration: MediaSense application does not record even if recording is enabled]]
*[[Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state]]

== Database ==

*[[Database: Database not updated after event forwarding]]
*[[Database: Database no longer accepts data]]
*[[Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information]]

== General ==

*[[General: HTTP Status 500 message displays when opening Cisco MediaSense Administration after system restart]]
*[[General: Performance issues as a result of hardware failure|General: Check and repair MediaSense file system Installation]]
*[[General: Performance issues as a result of hardware failure]]
*[[General: RTSP live monitoring sessions fail when using CUBE]]

== Installation ==

*[[Installation: Installation halts with an unrecoverable error|Installation: Installation halts with an unrecoverable error]]

== Upgrade ==

*[[Upgrade: Sync after switch version failed]]
*[[Upgrade: Data out of sync after upgrade]]

== Recording ==

*[[Recording: QuickTime does not playback G.729 recording, but status bar keep moving]]
*[[Recording: CUBE disconnects Cisco MediaSense right after recording begins]]
*[http://docwiki-dev.cisco.com/wiki/Recording:_Unified_CM_drops_MediaSense_recording_as_soon_as_recording_begins Recording: Unified CM drops MediaSense recording as soon as recording begins]
*[[Recording: Recordings from CUBE fail with SIP error 488 Not Acceptable Here]]

== RTMT ==

*[[RTMT: Unable to login to RTMT from the primary server]]
*[[RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down]]

== Runtime ==

*[[Runtime: MediaSense server is unable to keep up with incoming recordings]]
*[[Runtime: Media server rejects open RTSP session]]
*[[Runtime: Open RTSP session to MediaSense failed with timeout]]
*[[Runtime: Close recording session failed with timeout]]

General: HTTP Status 500 message displays when opening Cisco MediaSense Administration after system restart

2012-09-26T19:25:39Z

Rshroyer: Add the new categories.

Troubleshooting Tips for Cisco MediaSense

2012-09-26T18:37:27Z

Rshroyer: Removed link to create new page; put this only on dev wiki.

'''Print PDF:''' [[Print Troubleshooting Tips for Cisco MediaSense]]

 

== API ==

*[http://docwiki-dev.cisco.com/wiki/API:_API_request_returns_Error_405#API.C2.A0request_returns.C2.A0Error_405:_Method_not_supported..C2.A0 API: API request returns Error 405: Method not supported]
*[[API: Incorrect participant duration]]
*[[API: MediaSense application sign-in fails with administration credentials]]
*[[API: Missing events and closed subscription]]
*[[API: Incorrect session or participant duration]]

== Administration ==

*[[Administration: Administration Login returns unexpected error]]
*[[Administration: Unable to access Administration and Serviceability UI on a newly installed system]]
*[[Administration: Unknown request error display]]
*[[Administration: Saving an AXL service provider configuration will result in an incorrect error message under certain pre-conditions]]

== Configuration ==

*[[Configuration: Call between two RT phones is not recorded]]
*[[Configuration: Calls using g.722 codec are not recorded]]
*[[Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers]]
*[[Configuration: Conversation after a transfer is not recorded on RT-Lite phones]]
*[[Configuration: Failure to playback audio or video when using RT video phone]]
*[[Configuration: MediaSense application does not record even if recording is enabled]]
*[[Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state]]

== Database ==

*[[Database: Database not updated after event forwarding]]
*[[Database: Database no longer accepts data]]
*[[Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information]]

== General ==

*[[General: Performance issues as a result of hardware failure|General: Check and repair MediaSense file system Installation]]
*[[General: Performance issues as a result of hardware failure]]
*[[General: RTSP live monitoring sessions fail when using CUBE]]

== Installation ==

*[[Installation: Installation halts with an unrecoverable error|Installation: Installation halts with an unrecoverable error]]

== Upgrade ==

*[[Upgrade: Sync after switch version failed]]
*[[Upgrade: Data out of sync after upgrade]]

== Recording ==

*[[Recording: QuickTime does not playback G.729 recording, but status bar keep moving]]
*[[Recording: CUBE disconnects Cisco MediaSense right after recording begins]]
*[http://docwiki-dev.cisco.com/wiki/Recording:_Unified_CM_drops_MediaSense_recording_as_soon_as_recording_begins Recording: Unified CM drops MediaSense recording as soon as recording begins]

== RTMT ==

*[[RTMT: Unable to login to RTMT from the primary server]]
*[[RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down]]

== Runtime ==

*[[Runtime: MediaSense server is unable to keep up with incoming recordings]]
*[[Runtime: Media server rejects open RTSP session]]
*[[Runtime: Open RTSP session to MediaSense failed with timeout]]
*[[Runtime: Close recording session failed with timeout]]

Troubleshooting Tips for Cisco MediaSense

2012-09-26T18:35:33Z

Rshroyer: Added link to template for creating new tip; removed obsolete "back" link.

'''Create New Tip''': [[Create Contact Center Troubleshooting Tips|Create Troubleshooting Tip]]

'''Print PDF:''' [[Print Troubleshooting Tips for Cisco MediaSense]]

 

== API ==

*[http://docwiki-dev.cisco.com/wiki/API:_API_request_returns_Error_405#API.C2.A0request_returns.C2.A0Error_405:_Method_not_supported..C2.A0 API: API request returns Error 405: Method not supported]
*[[API: Incorrect participant duration]]
*[[API: MediaSense application sign-in fails with administration credentials]]
*[[API: Missing events and closed subscription]]
*[[API: Incorrect session or participant duration]]

== Administration ==

*[[Administration: Administration Login returns unexpected error]]
*[[Administration: Unable to access Administration and Serviceability UI on a newly installed system]]
*[[Administration: Unknown request error display]]
*[[Administration: Saving an AXL service provider configuration will result in an incorrect error message under certain pre-conditions]]

== Configuration ==

*[[Configuration: Call between two RT phones is not recorded]]
*[[Configuration: Calls using g.722 codec are not recorded]]
*[[Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers]]
*[[Configuration: Conversation after a transfer is not recorded on RT-Lite phones]]
*[[Configuration: Failure to playback audio or video when using RT video phone]]
*[[Configuration: MediaSense application does not record even if recording is enabled]]
*[[Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state]]

== Database ==

*[[Database: Database not updated after event forwarding]]
*[[Database: Database no longer accepts data]]
*[[Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information]]

== General ==

*[[General: Performance issues as a result of hardware failure|General: Check and repair MediaSense file system Installation]]
*[[General: Performance issues as a result of hardware failure]]
*[[General: RTSP live monitoring sessions fail when using CUBE]]

== Installation ==

*[[Installation: Installation halts with an unrecoverable error|Installation: Installation halts with an unrecoverable error]]

== Upgrade ==

*[[Upgrade: Sync after switch version failed]]
*[[Upgrade: Data out of sync after upgrade]]

== Recording ==

*[[Recording: QuickTime does not playback G.729 recording, but status bar keep moving]]
*[[Recording: CUBE disconnects Cisco MediaSense right after recording begins]]
*[http://docwiki-dev.cisco.com/wiki/Recording:_Unified_CM_drops_MediaSense_recording_as_soon_as_recording_begins Recording: Unified CM drops MediaSense recording as soon as recording begins]

== RTMT ==

*[[RTMT: Unable to login to RTMT from the primary server]]
*[[RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down]]

== Runtime ==

*[[Runtime: MediaSense server is unable to keep up with incoming recordings]]
*[[Runtime: Media server rejects open RTSP session]]
*[[Runtime: Open RTSP session to MediaSense failed with timeout]]
*[[Runtime: Close recording session failed with timeout]]

Troubleshooting Tips for Cisco MediaSense

2012-09-26T18:32:11Z

Rshroyer:

'''Back:''' [[Troubleshooting Cisco MediaSense]]

'''Create New Tip''': [[Create Contact Center Troubleshooting Tips|Create Troubleshooting Tip]]

'''Print PDF:''' [[Print Troubleshooting Tips for Cisco MediaSense]]

 

== API ==

*[http://docwiki-dev.cisco.com/wiki/API:_API_request_returns_Error_405#API.C2.A0request_returns.C2.A0Error_405:_Method_not_supported..C2.A0 API: API request returns Error 405: Method not supported]
*[[API: Incorrect participant duration]]
*[[API: MediaSense application sign-in fails with administration credentials]]
*[[API: Missing events and closed subscription]]
*[[API: Incorrect session or participant duration]]

== Administration ==

*[[Administration: Administration Login returns unexpected error]]
*[[Administration: Unable to access Administration and Serviceability UI on a newly installed system]]
*[[Administration: Unknown request error display]]
*[[Administration: Saving an AXL service provider configuration will result in an incorrect error message under certain pre-conditions]]

== Configuration ==

*[[Configuration: Call between two RT phones is not recorded]]
*[[Configuration: Calls using g.722 codec are not recorded]]
*[[Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers]]
*[[Configuration: Conversation after a transfer is not recorded on RT-Lite phones]]
*[[Configuration: Failure to playback audio or video when using RT video phone]]
*[[Configuration: MediaSense application does not record even if recording is enabled]]
*[[Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state]]

== Database ==

*[[Database: Database not updated after event forwarding]]
*[[Database: Database no longer accepts data]]
*[[Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information]]

== General ==

*[[General: Performance issues as a result of hardware failure|General: Check and repair MediaSense file system Installation]]
*[[General: Performance issues as a result of hardware failure]]
*[[General: RTSP live monitoring sessions fail when using CUBE]]

== Installation ==

*[[Installation: Installation halts with an unrecoverable error|Installation: Installation halts with an unrecoverable error]]

== Upgrade ==

*[[Upgrade: Sync after switch version failed]]
*[[Upgrade: Data out of sync after upgrade]]

== Recording ==

*[[Recording: QuickTime does not playback G.729 recording, but status bar keep moving]]
*[[Recording: CUBE disconnects Cisco MediaSense right after recording begins]]
*[http://docwiki-dev.cisco.com/wiki/Recording:_Unified_CM_drops_MediaSense_recording_as_soon_as_recording_begins Recording: Unified CM drops MediaSense recording as soon as recording begins]

== RTMT ==

*[[RTMT: Unable to login to RTMT from the primary server]]
*[[RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down]]

== Runtime ==

*[[Runtime: MediaSense server is unable to keep up with incoming recordings]]
*[[Runtime: Media server rejects open RTSP session]]
*[[Runtime: Open RTSP session to MediaSense failed with timeout]]
*[[Runtime: Close recording session failed with timeout]]

Deployment Scenarios for Cisco MediaSense

2012-09-19T22:22:12Z

Rshroyer:

This page provides links to the various deployment models for Cisco MediaSense. 

*[[Call Flow Details for CUBE Inbound Dial Peer Recording|'''Call Flow Details for CUBE Inbound Dial Peer Recording''']]
*[[Call Flow Details for CUBE and CVP|'''Call Flow Details for CUBE and CVP''']]
*[[Call Flow Details for CUBE using Unified CM Phone|'''Call Flow Details for CUBE using Unified CM Phone''']]
*[[Call Flow Details for CUBE with Mid-call Codec Change|'''Call Flow Details for CUBE with Mid-call Codec Change''']]

 

----

 

[[Category:Cisco_MediaSense]]

Virtualization for Cisco MediaSense

2012-09-19T20:59:25Z

Rshroyer:

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

= Updates to this Page =

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

{| class="wikitable FCK__ShowTableBorders"
|-
! Date
! Update
|-
| September 2012
| Updated link to go to Cisco MediaSense OVA Template for Release 9.0(1a).
|-
| August 2012
| Removed outdated information about hardware requirements.
|-
| July 2012
| Added information about Release 9.0(1).
|-
| May 2012
| Added information about MediaSense support for high disk count and high disk size for C210 M1/M2 servers.
|-
| January 2012
| Updated page with information on support for Release 8.5(4).
|-
| October 2011
| Added support for Release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
| June 2011
| Updated all links to align with the new Virtualization structure at [[Unified Communications in a Virtualized Environment]].
|-
| April 2011
| Added support for Release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
| November 2010
| Virtualization of Cisco MediaSense on Unified CS C-Series hardware.
|-
| December 2010
| Updated OVA template download link.
|}

= Information for Partners about MediaSense Deployments =

See [[Unified Communications in a Virtualized Environment]].

= Cisco MediaSense-Specific Details for VMware Requirements =

See [[Unified Communications VMWare Requirements]]

*Cisco UCS C-Series Servers, Cisco MediaSense ISO, and ESXi must be installed prior to the Cisco MediaSense installation.
*For other third-party software requirements and for a list of approved UCS servers, see the server requirements and version compatibility with Unified CM sections in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense]. 

== Cisco MediaSense, Release 8.5(1)  and 8.5(2) ==

All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS).

*Cisco MediaSense only supports UCS C210 M1 and M2 servers for Release 8.5(1).
*If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.

 

== Cisco MediaSense, Release 8.5(3) ==

{{note| Cisco MediaSense has stringent requirements for the media disk size for any deployment. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] for more information.}}

Up to 60 terabytes of media storage is supported per cluster, divided into up to six 2TB virtual disks in each of five servers. This assumes that all nodes are B-series servers, for which Cisco MediaSense supports SAN storage. C-series servers, for which only direct attached drives are currently supported, are limited to two 2TB media storage partitions each. Also, no single media partition may be smaller than 200GB.

See the following links for more information:

*See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications
*See the Compatibility Matrix section in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] guide for more information. 

== Cisco MediaSense, Release 8.5(4) ==

In addition to approved UCS servers, Cisco MediaSense 8.5(4) can also be installed on a Services Ready Engine (SRE) module inside a router. An SRE module is a router blade that has its own processors, storage, network interfaces, and memory. Support for SRE requires SRE v2.0 software. For more information about approved SRE models, see the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(4)]. 

If you are using ESXi 5.0, make sure that you [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 5.0 host.

== Cisco MediaSense, Release 9.0(1) ==

Specification-based Virtualization enables Cisco MediaSense to run on Cisco Unified Computing System (Unified CS) servers that are also running other virtual machines. Specification-based Virtualization also enables Cisco MediaSense to run on select HP servers (Note that IBM servers are currently not supported.)

A new Open Virtualization Archive Virtual Machine (OVA-VM) template enables Cisco MediaSense to simplify the deployment of virtual machines in new installations. This template has deployment options for Services Ready Engines, primary servers, secondary servers, and expansion servers.

= Cisco MediaSense-Specific Information for OVA Templates =

If your partitions (VM disk configuration) are not aligned, your data replication between the primary and secondary servers may get congested and result in your data being out of sync. To avoid these problems, only use the VM templates provided by Cisco MediaSense. 

See the following websites for more information: 

*[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_MediaSense Unified Communications Virtualization Downloads (including OVA/OVF Templates).]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=9.0(1a)&relind=AVAILABLE&rellifecycle=&reltype=latest Download OVA Template for Cisco MediaSense, Release 9.0(1a)]

 

{{caution| If your VM template or VM configuration does not meet the Cisco MediaSense requirements, it is possible for your installation to halt due to an unrecoverable error. See [[Installation: Installation halts with an unrecoverable error]].}}

 

{{note| Configure the primary server and secondary server in your Cisco MediaSense deployment to have identical hardware in terms of CPU configuration (number of CPUs and speed of the CPU), storage configuration (number of disks, speed of disk, and RAID setup), and memory. Be sure to keep both servers in the same network and run the same version of VMWare Hypervisor on both servers.}}

= Cisco MediaSense-Specific Information for Sizing Guidelines =

The VM-specific sizing informaton required for Cisco MediaSense is additional virtual disks for media storage. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense] for further information.

= How to Dump Install Logs to the VM Serial Port =

See [[How to Dump Install Logs to the Serial Port of the Virtual Machine]].

 

----

{| 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]]
|}

[[Category:Cisco_MediaSense]]

Virtualization for Cisco MediaSense

2012-09-12T19:01:01Z

Rshroyer:

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

= Updates to this Page =

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

{| class="wikitable FCK__ShowTableBorders"
|-
! Date
! Update
|-
| September 2012
| Updated link to go to Cisco MediaSense OVA Template for Release 9.0(1a).
|-
| August 2012
| Removed outdated information about hardware requirements.
|-
| July 2012
| Added information about Release 9.0(1).
|-
| May 2012
| Added information about MediaSense support for high disk count and high disk size for C210 M1/M2 servers.
|-
| January 2012
| Updated page with information on support for Release 8.5(4).
|-
| October 2011
| Added support for Release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
| June 2011
| Updated all links to align with the new Virtualization structure at [[Unified Communications in a Virtualized Environment]].
|-
| April 2011
| Added support for Release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
| November 2010
| Virtualization of Cisco MediaSense on Unified CS C-Series hardware.
|-
| December 2010
| Updated OVA template download link.
|}

= Information for Partners about MediaSense Deployments =

See [[Unified Communications in a Virtualized Environment]].

= Cisco MediaSense-Specific Details for VMware Requirements =

See [[Unified Communications VMWare Requirements]]

*Cisco UCS C-Series Servers, Cisco MediaSense ISO, and ESXi must be installed prior to the Cisco MediaSense installation.
*For other third-party software requirements and for a list of approved UCS servers, see the server requirements and version compatibility with Unified CM sections in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense]. 

== Cisco MediaSense, Release 8.5(1)  and 8.5(2) ==

All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS).

*Cisco MediaSense only supports UCS C210 M1 and M2 servers for Release 8.5(1).
*If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.

 

== Cisco MediaSense, Release 8.5(3) ==

{{note| Cisco MediaSense has stringent requirements for the media disk size for any deployment. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] for more information.}}

Up to 60 terabytes of media storage is supported per cluster, divided into up to six 2TB virtual disks in each of five servers. This assumes that all nodes are B-series servers, for which Cisco MediaSense supports SAN storage. C-series servers, for which only direct attached drives are currently supported, are limited to two 2TB media storage partitions each. Also, no single media partition may be smaller than 200GB.

See the following links for more information:

*See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications
*See the Compatibility Matrix section in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] guide for more information. 

== Cisco MediaSense, Release 8.5(4) ==

In addition to approved UCS servers, Cisco MediaSense 8.5(4) can also be installed on a Services Ready Engine (SRE) module inside a router. An SRE module is a router blade that has its own processors, storage, network interfaces, and memory. Support for SRE requires SRE v2.0 software. For more information about approved SRE models, see the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(4)]. 

If you are using ESXi 5.0, make sure that you [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 5.0 host.

== Cisco MediaSense, Release 9.0(1a) ==

Specification-based Virtualization enables Cisco MediaSense to run on Cisco Unified Computing System (Unified CS) servers that are also running other virtual machines. Specification-based Virtualization also enables Cisco MediaSense to run on select HP servers (Note that IBM servers are currently not supported.)

A new Open Virtualization Archive Virtual Machine (OVA-VM) template enables Cisco MediaSense to simplify the deployment of virtual machines in new installations. This template has deployment options for Services Ready Engines, primary servers, secondary servers, and expansion servers.

= Cisco MediaSense-Specific Information for OVA Templates =

If your partitions (VM disk configuration) are not aligned, your data replication between the primary and secondary servers may get congested and result in your data being out of sync. To avoid these problems, only use the VM templates provided by Cisco MediaSense. 

See the following websites for more information: 

*[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_MediaSense Unified Communications Virtualization Downloads (including OVA/OVF Templates).]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=9.0(1a)&relind=AVAILABLE&rellifecycle=&reltype=latest Download OVA Template for Cisco MediaSense, Release 9.0(1a)]

 

{{caution| If your VM template or VM configuration does not meet the Cisco MediaSense requirements, it is possible for your installation to halt due to an unrecoverable error. See [[Installation: Installation halts with an unrecoverable error]].}}

 

{{note| Configure the primary server and secondary server in your Cisco MediaSense deployment to have identical hardware in terms of CPU configuration (number of CPUs and speed of the CPU), storage configuration (number of disks, speed of disk, and RAID setup), and memory. Be sure to keep both servers in the same network and run the same version of VMWare Hypervisor on both servers.}}

= Cisco MediaSense-Specific Information for Sizing Guidelines =

The VM-specific sizing informaton required for Cisco MediaSense is additional virtual disks for media storage. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense] for further information.

= How to Dump Install Logs to the VM Serial Port =

See [[How to Dump Install Logs to the Serial Port of the Virtual Machine]].

 

----

{| 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]]
|}

[[Category:Cisco_MediaSense]]

Unified Communications Virtualization Downloads (including OVA/OVF Templates)

2012-09-12T18:51:24Z

Rshroyer:

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

----

 

= Supported Virtual Machine OVA Templates =

'''What is an OVA?'''  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".

 '''Do Cisco UC VMs require these OVAs? ''' To be TAC-supported, Virtual Machines for Cisco Unified Communications applications '''must''' use one of the provided OVA templates on this page.

*They represent what the UC apps have been tested with
*It is the only way to ensure UC apps are deployed on "aligned" disks for SAN deployments (i.e. pre-aligned filesystem disk partitions for the OVA's vDisks). 
*OVA configurations are summarized in the tables below for convenience, but authoritative information is on OVA file's release notes on Download Software on www.cisco.com.

  

'''What does "users" mean in tables below?'''   "U'''sers"''' refers to the indicated user count at a particular BHCA, number of devices per user, device mix per VM, etc. 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] . Actual user capacity and total supported devices will be design-dependent; please follow all rules in the design guides and sizing tools for what your application can actually support.

 '''Where do I download these OVAs from?'''  See [[Downloading OVA Templates for UC Applications]] for more information on how to download OVA templates for UC Applications.

{{note |
* UC apps do not support CPU oversubscription. One VM vCPU must map to one physical core (not one logical core) ([[Unified Communications Virtualization Sizing Guidelines | click here]] for details).
* "One vCPU to one physical core" applies for all supported CPU architectures with equivalent performance for UC ([[Unified Communications Virtualization Sizing Guidelines | click here]] for details). E.g. one physical core on E5-2600 at 2.53+ GHz and one physical core on E7-2800 at 2.4+ GHz are equivalent for purposes of UC VM OVAs, sizing and co-residency planning.
* Each VM OVA is only for use on certain CPU architectures. See the notes column for which CPUs are allowed.
**E.g. the CUCM 1K user OVA is only for use on E5-2609/2.4 GHz (only found in UCS C220 M3S TRC#2) and E5506/2.13GHz (only found in UCS C220 M2 TRC#1).
** All other OVAs (such as CUCM 2.5K user, 7.5K user, or 10K user) are only for use on CPUs with minimum core speed of 2.53 GHz [[UC Virtualization Supported Hardware#Processors / CPUs | click here for details]], such as E5-2643/3.3 GHz or E5640 / 2.66 GHz.
}}

For '''Specifications-based''' deployments (non TRC deployments), the CPU core count AND the CPU core speed 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 Template Download Location] 
*[[OVA Template Details for Unified CM Release 8.0]] 
*[[OVA Template Details for Unified CM Release 8.5]] 
*[[OVA Template Details for Unified CM Release 8.6]] 
*[[OVA Template Details for Unified CM Release 9.0]] 

 

== Cisco Emergency Responder ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Emergency Responder 8.5 and 8.6'''
|- 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

|}

 

{| style="width: 1077px; height: 416px" border="1"
|+ '''Supported OVA Templates: Cisco Emergency Responder 8.7 and 9.0'''
|- style="background: rgb(229,228,226)"
! rowspan="2" | VM OVA Capacity 
! colspan="5" | VM OVA Parameters 
! rowspan="2" | Notes 
|- style="background: rgb(229,228,226)"
! vCPU Cores (= Physical Cores)
! Physical CPU Load was Calibrated To
! vRAM (=Physical Memory)
! vDisk (=Physical space)
! vNIC
|-
!
Emergency Responder 12,000 users Only for C200M2 TRC#1

| 2 (with 800 MHz reservation) 
| E5506 2.13 GHz
| 4 GB (with all 4 GB reserved)
| 1x 80 GB disk
| 1
| For use only on UCS C200M2 TRC#1. 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

|-
!
Emergency Responder 20,000 users Not for C200M2 TRC#1

| 1 (with 800 MHz reservation) 
| E5540 2.53 GHz
| 4 GB (with all 4 GB reserved)
| 1x 80 GB disk with pre-aligned disk partitions
| 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

|-
!
Emergency Responder 30,000 users Not for C200M2 TRC#1

| 2 (with 3600 MHz reservation) 
| E5540 2.53 GH
| 6 GB (with all 6 GB reserved)
| 2x 80 GB disk
| 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

|-
!
Emergency Responder 40,000 users Not for C200M2 TRC#1

| 4 (with 7200 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 2x 80 GB disk
| 1
| Not for use on C200 M2 TRC#1. Limits:
:*40,000 IP phones
:*12,500 analog phones
:*4,000 roaming phones (per Emergency Responder cluster)
:*2,500 LAN switches
:*150,000 switch ports
:*12,500 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
! 
|-
! [[#Unified_Communications_Manager|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 Intercompany Media Engine ==

*[http://www.cisco.com/cisco/software/release.html?mdfid=282822890&softwareid=283088407&release=9.0%281%29&relind=AVAILABLE&rellifecycle=&reltype=latest General OVA Template Download Location] 

 

{| style="width: 712px; height: 416px" border="1"
|+ '''Supported OVA Templates: Cisco Intercompany Media Engine, Release 8.6(2)'''
|- style="background: rgb(229,228,226)"
! rowspan="2" | VM OVA Capacity 
! colspan="5" | VM OVA Parameters 
! rowspan="2" | Notes 
|- style="background: rgb(229,228,226)"
! vCPU Cores (= Physical Cores)
! Physical CPU Load was Calibrated To
! vRAM (=Physical Memory)
! vDisk (=Physical space)
! vNIC
|-
!
CIME 5 peer IDs node Only for non-BE6K / certain TRCs - see notes

| 2 (with 3600 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with 6 GB reservation)
| 1x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or C220M3 TRC#2 or BE6000. Up to 5 peer IDs.
 

|-
!
CIME 10 peer IDs node Only for non-BE6K / certain TRCs - see notes

| 4 (with 7200 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with 6 GB reservation)
| 2x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or C220M3 TRC#2 or BE6000. Up to 10 peer IDs.
 

|}

 

 

== Cisco Unity Connection ==

*[http://www.cisco.com/cisco/software/type.html?mdfid=283062758&flowid=5455 General Unity Connection OVA Template Download Location] 
*[[OVA Template Details for Unity Connection Release 8.0]] 
*[[OVA Template Details for Unity Connection Release 8.5]] 
*[[OVA Template Details for Unity Connection Release 8.6.1]] 
*[[OVA Template Details for Unity Connection Release 8.6.2]] 
*[[OVA Template Details for Unity Connection Release 9.0.1]] 

 

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

{{Note| Cisco Unified Presence is referred to as IM and Presence in Release 9.0(1) and later.}}

See also:

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=280448682&i=rs General OVA Template Download Location]
*[[OVA Template Details for Unified Presence Release 8.0(x)]] 
*[[OVA Template Details for Unified Presence Release 8.5(x)]] 
*[[OVA Template Details for Unified Presence Release 8.6(1)]] 
*[[OVA Template Details for Unified Presence Release 8.6(2)]] 
*[[OVA Template Details for Unified Presence Release 8.6(3)]] 
*[[OVA Template Details for Unified Presence Release 8.6(4)]] 
*[[OVA Template Details for IM and Presence Release 9.0(1)]] 

 

== Cisco Unified Contact Center Express/Cisco Unified IP Intelligent Voice Response (IP IVR) ==

{{Note| The information for Unified IP IVR is the same as Unified CCX.}}

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| Unified CCX OVA version 2 is for use with ESXi 4.1. Please follow [[Unified Communications VMware Requirements]] 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 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 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 Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

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

| 1
| rowspan="3" | See [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_5/installation/guide/uccx851ig.pdf Installing Cisco Unified Contact Center Express Release 8.5(1) guide]for more information on vDisk space.
|-
! 300 agents
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

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

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

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

| 1
| rowspan="3" | See [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_5/installation/guide/uccx851ig.pdf Installing Cisco Unified Contact Center Express Release 9.0(1) guide]for more information on vDisk space.
|-
! 300 agents
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

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

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.3&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 9.0]
| 2
| 4 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 • 900 named users • 300 concurrent users 
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.3&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 9.0 Base Server Configuration (CR/QM/AQM)]
| 2
| 4 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 )
| 1
| Capacities • 3600 named users • 1200 concurrent users
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.3&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 9.0 Recording Server Configuration (CR/QM/AQM)]
| 4
| 4 GB
| vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM recording service binaries, vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recording cache
| 1
| Capacities • 300 concurrent voice recordings for Server (SPAN) and Network recording • 150 concurrent voice and screen recordings, recordings for Server (SPAN) and Network recording
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.2]
| 2
| 4 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

:*900 named users
:*300 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Base Server Configuration (CR/QM/AQM)]
| 2
| 4 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)

| 1
|
Capacities

:*3600 named users
:*1200 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Recording Server Configuration (CR/QM/AQM)]
| 4
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM recording service binaries
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recording cache

| 1
|
Capacities

:*300 concurrent voice recordings for Server (SPAN) and Network recording
:*150 concurrent voice and screen recordings, recordings for Server (SPAN) and Network recording
:*'''Virtualizing''' the Monitor server for Server (SPAN) recording is '''not '''supported on the UCS platform

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.1]
| 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.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.1 Base Server 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)

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|
|}

== 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
| 6
| 15
| 1
| 
|-
! CUOM 45K phones (VM-CUCMS_4L)
| 4
| 8 GB
| 2x 60 GB
| 6
| 15
| 1
| 
|-
! CUSM 10K Phones (VM-CUCMS_2)
| 2
| 4 GB
| 1x 72 GB
| 6
| 15
| 1
| 
|-
! CUSM 45K Server (VM-CUCMS_4)
| 4
| 4 GB
| 2x 60 GB
| 6
| 15
| 1
| 
|-
! CUSSM 10K phones (VM-CUCMS_1)
| 1
| 4 GB
| 1x 60 GB
| 6
| 15
| 1
| 
|-
! CUSSM 45K Phones
| 2
| 4 GB
| 1x 72 GB
| 6
| 15
| 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 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
| 
|}

== 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]
*[http://docwiki.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE#Unified_CCE_Scalability_Impacts Scalability Impacts]
*[[OVA Template Details for Unified Contact Center Enterprise Release 8.x]]
*[[OVA Template Details for Unified Contact Center Enterprise Release 9.x]]

 

== Cisco Packaged Contact Center Enterprise ==

Supported OVA templates are documented in the Install and Configuration Guide and in the Packaged CCE Specifications Guide. Both guides are on the Cisco documentation web page.

*[https://www.cisco.com/cisco/software/type.html?mdfid=284360381&i=rm Software Download] - Download OVA files
*[http://www.cisco.com/en/US/products/ps12586/prod_technical_reference_list.html User Guides]

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

*[http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_MediaSense Virtualization for Cisco MediaSense]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=9.0(1a)&relind=AVAILABLE&rellifecycle=&reltype=latest Download OVA Template for Cisco MediaSense, Release 9.0(1a])
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.4&rellifecycle=&relind=AVAILABLE&reltype=all Download OVA Template for Cisco MediaSense, Release 8.5(4)]

 To promote ease of use, Cisco MediaSense, Release 9.0(1a) has only one template. This template contains several deployment options as shown in the following table.   

{| border="1" cellspacing="1" cellpadding="1" width="812"
|+ '''Supported OVA Template: Cisco MediaSense, Release 9.0(1a)''' 
|-
! valign="baseline" scope="col" align="center" | Deployment  
! valign="baseline" scope="col" align="center" |   vCPU   
! valign="baseline" scope="col" align="center" |
CPU      reservation  

! valign="baseline" scope="col" align="center" |  vRAM 
! valign="baseline" scope="col" align="center" |    vDisk    
! valign="baseline" scope="col" align="center" | Notes            
|-
! valign="baseline" align="center" | SRE 
| valign="baseline" align="center" |
 2

| valign="baseline" align="center" |
  2200 MHz

| valign="baseline" align="center" |
 6 GB

| valign="top" align="left" |
Disk 1: 80 GB for OS Disk 2: 80 GB for DB  Disk 3: 200 GB for media               

| valign="top" align="left" |
Includes a fixed 200 GB disk for media storage. No expansion nodes supported. No additional media storage supported. 

|-
! valign="baseline" align="center" |  Primary/Secondary    
| valign="baseline" align="center" |    7 
| valign="baseline" align="center" |   15000 MHz 
| valign="baseline" align="center" |  8 GB 
| valign="top" align="left" |
Disk 1: 80 GB for OS  Disk 2: 600 GB for DB 

| valign="top" align="left" |
User must add media disks prior to installation. 

|-
! valign="baseline" align="center" | Expansion
| valign="baseline" align="center" |    7
| valign="baseline" align="center" | 10000 MHz 
| valign="baseline" align="center" | 8 GB 
| valign="top" align="left" |
Disk 1: 80 GB for OS Disk 2: 80 GB

| valign="top" align="left" |
User must add media disks prior to installation.

|}

 

{| border="1"
|+ '''Supported OVA Templates: Cisco MediaSense, Release 8.5'''
|-
! 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)

Release 8.5(3)

Release 8.5(4)

|-
! 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
|-
! CMS_SRE_v8.5_vmv7
| 2
| 6 GB
| 2 x 80 GB (thick provisioning) 1 x 200 GB (thick provisioning) for Media storage
| 1 (with static MAC address)
| Release 8.5(4)
|}

 

== 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 CUIC (200 Reporting Users)]
| 4
| 6 GB
| 1x 146 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 Porta '''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! CCMP Single Server Deployment (<1500 Agents)
| 4
| 4 GB
| 1x 100 GB
| 1
| 
|-
! CCMP Web Server (< 8000 Agents) 
| 4 
| 4 GB 
| 1x 100 GB 
| 1 
| 
|-
! CCMP DB Server (< 8000 Agents)
| 8
| 8 GB
| 2x 100 GB
| 1
| 
|-
! CCMP Web/App Server Large Deployment (> 8000 Agents)
| 8
| 16 GB
| 1x 100 GB
| 1
| 
|-
! CCMP DB Server Large Deployment (> 8000 Agents) 
| 8 
| 16 GB 
| 1 x 100 GB, 1 x 250 GB 
| 1 
| 
|}

== Cisco SocialMiner ==

See also:

*[[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613136&release=9.0.1&relind=AVAILABLE&softwareid=283733464&rellifecycle=&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
|-
! Large deployment option
| 4
| 12 GB
| 1x 146 GB and 1x 256 GB
| 1
|-
! Small deployment option
| 2
| 8 GB
| 2x 80GB
| 1
|}

== Cisco Unified Email Interaction Manager and Web Interaction Manager ==

  

{| border="1" cellspacing="1" cellpadding="1"
|-
! scope="col" | Application, OVA Capacity and Notes+Download Link
! scope="col" | Contents
! scope="col" | No of VM's to deploy of each component
! scope="col" | vCPU
! scope="col" | vDisk
! scope="col" | vRAM/Memory
|-
|
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_1_v2.0] 

Deployment Option:

100 agents - Email Only 

| Application, Services Server ,File server Messaging Server ,Web Server and Database server
| 1
| 2 
| 1 x 80GB
| 4
|-
| rowspan="2" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_2_v2.0] 

Deployment Option:

140 agents - Email Only

 

| Application, Services Server ,File server Messaging Server and Web server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 2
| 1 x 80GB
| 4
|-
| rowspan="2" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_3_v2.0] 

Deployment Option:

100 agents - Chat only or

100 agents - Email and Chat  

| Application, Services Server ,File server Messaging Server and Database server
| 1
| 2
| 1 x 80GB
| 4
|-
| Web Server
| 1
| 1
| 1 x 80GB
| 2 
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_4_v2.0] 

Deployment Option:

250 Agents - Email and Chat or 120 Agents - BC and CallBack

 

 

| Web Server
| 1
| 1
| 1 x 80GB
| 1 
|-
| Application server
| 1
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 2 
| 1 x 80 GB for OS, 1 x 150 GB for DB
| 4
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_5_v2.0] 

Deployment Option:

500 Agents - Email and Chat or 240 Agents - BC and CallBack 

 

| Web Server
| 2 
| 1
| 1 x 80GB
| 1 
|-
| Application server
| 2
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 8
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 1
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_6_v2.0] 

Deployment Option:

750 Agents - Email and Chat or 360 Agents - BC and CallBack 

| Web Server
| 3
| 1
| 1 x 80GB
| 1
|-
| Application server
| 3
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 16 
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_7_v2.0] 

Deployment Option:

1000 Agents - Email and Chat or 480 Agents - BC and CallBack 

| Web Server
| 4
| 1
| 1 x 80GB
| 1
|-
| Application server
| 4 
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 8
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_8_v2.0] 

Deployment Option:

1250 Agents - Email and Chat or 600 Agents - BC and CallBack 

| Web Server
| 5 
| 1
| 1 x 80GB
| 1 
|-
| Application server
| 5
| 2
| 1 x 80GB
| 2 
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 8
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|}

 

== Cisco Media Blender ==

{| style="width: 1054px; height: 102px" border="1" cellspacing="1" cellpadding="1" width="1054" align="center"
|-
|
 '''Application, OVA Capacity and Notes+Download Link'''

|         '''Contents    '''  
| '''No of VM's to deploy of each component'''
| '''vCPU'''
| '''vDisk'''
| '''vRAM/Memory'''
|-
|
 [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all Cisco Media Blender]

|
 

Cisco Media Blender

|
 1

|
 2

|
 1 x 80GB

|
 2

|}

 

== Cisco Finesse ==

See also:

*[[Virtualization for Cisco Finesse|Cisco Finesse]]
*[http://www.cisco.com/cisco/software/type.html?mdfid=283613135&flowid=30701 Cisco Finesse OVA Templates] 

{| border="1"
|+ '''Supported OVA Templates: Cisco Finesse'''
|- style="background: rgb(229,228,226)"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Finesse_2000_agents_v9.0.1_vm8
| 4
| 8 GB
| 1x 146 GB
| 1
| Release 9.0(1)
|-
! Finesse_2000_agents_v1.0_vmv7 
| 4
| 8 GB
| 1x 146 GB
| 1
| Release 8.5(3)
|}

  

== TelePresence Applications ==

{| border="1"
|+ '''Supported OVA Templates: TelePresence Applications'''
|- 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=284132721&flowid=29922&softwareid=280887004&release=1.8.0%28582%29 Cisco TelePresence Manager] 
| align="center" | 2
| align="center" | 8 GB (4 GB reserved)
| align="center" | 1 x 200 GB
| align="center" | 1
|
1.9.0 Supported Co-residency Configurations:

*Up to 4 CTS-Manager instances can be installed on a single server, for service provider deployments with no more than 50 endpoints under management per instance of CTS-Manager. 
*1 CTS-Manager and 1 CTMS can be installed on a single UCS server. 

 

|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=281043620&flowid=20525&softwareid=281149680&release=1.8.0%281026%29 Cisco TelePresence Multipoint Switch] 
| align="center" | 4
| align="center" | 6 GB (2.304 GB reserved)
| align="center" | 1 x 100 GB
| align="center" | 1
|
1.9.0 Supported Co-residency Configurations:

:*2 CTMS instances can be installed on a single UCS server.
:*1 CTMS and 1 CTS-Manager can be installed on a single UCS server.

 

|}

{| 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 Sizing Guidelines

2012-09-07T18:34:36Z

Rshroyer: Updated "Co-Residency Supported" column of "Contact Center Applications" table for MediaSense 9.0(1+).

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

----

 

== Introduction ==

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

 

 

== Application Co-residency Support Policy ==

Cisco UC virtualization only supports application co-residency under the specific conditions described below and as clarified [http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml in TAC Technote Document ID: 113520.].

 This policy only covers the rules for physical/virtual hardware sizing, co-resident application mix and maximum VM count per physical server. All other UC virtualization rules still apply (e.g supported VMware vSphere ESXi versions or hardware options). Co-residency rules apply equally to all hardware options:

*[[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configuration]]
*[[Specification-Based Hardware Support|UC on UCS Specs-based]]
*[[Specification-Based Hardware Support|HP/IBM Specs-based]]

 

{{note | UC app VM performance is only guaranteed when installed on a [[Tested Reference Configurations (TRC) | UC on UCS Tested Reference Configuration]], and only if all other conditions in this policy are followed.}} 

"Application co-residency" in this UC support policy is defined as VMs sharing the same physical server and the same virtualization software host:

*E.g. VMs running on the same VMware vSphere ESXi host on the same physical rack-mount server, such as Cisco UCS C-Series.
*E.g. VMs running on the same VMware vSphere ESXi host on the same physical blade server in the same blade server chassis, such as Cisco UCS B-Series.
*"Co-resident application mix" in this UC support policy refers to the set of VMs sharing a physical server and a virtualization software host.
*VMs running on different virtualization hosts and different physical servers are not co-resident.
**E.g. VMs running on two different Cisco UCS C-Series rack-mount servers are not co-resident.
**E.g. VMs running on two different Cisco UCS B-Series blade servers in the same UCS 5100 blade server chassis are not co-resident.

[[Image:UConUCS co-res 1 whatis.JPG|600px|Co-residency defined]] 

 Virtual Machines (VMs) are categorized as follows for purposes of this UC support policy:

*Cisco UC app VMs (or simply '''UC app VMs'''): a VM for one of the Cisco UC apps at [[Unified Communications Virtualization Supported Applications]].
*Cisco non-UC app VMs (or simply '''non-UC VMs'''): a VM for a Cisco application not listed at [[Unified Communications Virtualization Supported Applications]], such as the VM for Cisco Nexus 1000V's VSM.
*3rd-party application VMs (or simply '''3rd-party app VMs'''): a VM for a non-Cisco, application, such as VMware vCenter, 3rd-party Cisco Technology Developer Program applications, non-Cisco-provided TFTP/SFTP/DNS/DHCP servers, Directories, Groupware, File/print, CRM, customer home-grown applications, etc.

 

{{note | Cisco does not support non-UC or 3rd-party applications VMs running on "Cisco UC Virtualization Hypervisor" or "Cisco UC Virtualization Foundation" (as described at [[Unified Communications VMware Requirements]]). If you want to deploy non-U / 3rd-party applications, you must deploy on VMware vSphere Standard, Advanced, Enterprise or Enterprise Plus Edition. }} 

Each Cisco UC app supports one of the following four types of co-residency: 

{{note | Troubleshooting UC VMs co-resident with non-UC/3rd-party app VMs may require the changes described at <<in this TAC Technical Tip>>. . To be supported by Cisco TAC, customers must agree to these changes if required by Cisco TAC.}} 

#'''None:''' Co-residency is not supported. The UC app only supports a single instance of itself in a single VM on the virtualization host / physical server. No co-residency with ANY other VM is allowed, whether Cisco UC app VM, Cisco non-UC VM, or 3rd-party application VM.
#'''Limited:''' The co-resident application mix is restricted to specified VM combinations only. Click on the "Limited" entry in the tables below to see which VM combinations are allowed. Co-residency with any VMs outside these combinations - including other Cisco VMs - is not supported (these applications must be placed on a separate physical server). The deployment must also follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] listed below.
#'''UC with UC only:''' The co-resident application mix is restricted to VMs for UC apps listed at [[Unified Communications Virtualization Supported Applications]]. Co-residency with Cisco non-UC VMs and/or 3rd-party application VMs is not supported; those VMs must be placed on a separate physical server. The deployment must also follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] rules below.
#'''Full:''' The co-resident application mix may contain UC app VMs with Cisco non-UC VMs with 3rd-party application VMs. The deployment must follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]] rules below. The deployment must also follow the [[#Special_Rules_for_non-UC_and_3rd-party_Co-residency|Special Rules for non-UC and 3rd-party Co-residency]] below.

 

[[Image:UConUCS co-res 2 types.JPG|500px|Types of Co-residency]] 

 

==== General Rules for Co-residency and Physical/Virtual Hardware Sizing ====

See the tables after the rules for the co-residency policy of each UC app. 

{{note | Remember that virtualization and co-residency support varies by UC app '''version''', so don't forget to double-check inter-UC-app version compatibility, see [http://www.cisco.com/go/unified-techinfo Cisco Unified Communications System Documentation].}} 

:'''"Matching" Support Policies'''

All co-resident applications must "match" in the following areas:

*Same "server" support for compute/network/storage hardware (see [[Unified Communications Virtualization Supported Applications]])
**E.g. if you want to host co-resident apps on UCS C260 M2 TRC#1, all co-resident apps must have a hardware support policy that permits this.
**E.g. if you want to deploy instead as [[Specification-Based Hardware Support|UC on UCS Specs-based]] with a diskless UCS C260 M2 and a SAN/NAS storage array, all co-resident apps must support this.
**You must pick a hardware option that all the co-resident apps can support. For example, some UC apps do not support [[Specification-Based Hardware Support]] | Specs-based for UC on UCS or HP/IBM]], some UC apps do not support certain Tested Reference Configurations such as UC on UCS C200 M2 TRC#1 (as opposed to [[Specification-Based Hardware Support|UC on UCS C200 M2 specs-based]]).
*Same support for virtualization software product and version.
**E.g. one app supports vSphere 5.0, the other app only supports vSphere 4.1. vSphere 5.0 may not be used for this co-resident application mix.
*All apps must support a co-residency policy that permits the desired co-resident application mix.
**E.g. one app has a "Full" policy, another app has "UC with UC" policy. Co-resident non-UC or 3rd-party app VMs are not allowed.
**E.g. one app has a "UC with UC" policy, another app has "Limited" policy. Even though all apps will be UC, the desired combination may not be allowed by the "Limited" app.
**E.g. one app has "None" policy. No other apps can be co-resident with this app regardless of their policies.
*If support policies of a given co-resident app mix do not match, then the "least common denominator" is required.

 

:'''Virtual Machine Templates'''

All UC applications must use a supported virtual machine OVA template from [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)]]. 

:'''No Hardware Oversubscription'''

All VMs require a one to one mapping between virtual hardware and physical hardware. See specifics below. 

::'''CPU'''

*Must map 1 VM vCPU core to 1 physical CPU core.
**For example, if you have a host with 12 total physical cores, then you can deploy any combination of virtual machines where the total number of vCPU on those virtual machines adds up to 12.
**The requirement is based on ''physical'' cores, not ''logical'' cores.
*** Logical cores may exceed physical cores if CPU hyperthreading is used. See [[UC Virtualization Supported Hardware]] for recommendation on hyperthreading and other BIOS settings. See screenshot below for physical cores vs. logical cores (as viewed from either VMware vCenter or vSphere Client) for a UCS C220 M3S server with CPU hyperthreading DISABLED. If hyperthreading is ENABLED, you will see 16 logical cores despite only 8 physical cores, but UC sizing rules are still limited by 8 physical cores.

::[[Image:UConUCS_co-res_3b_hyperthreading.jpg|500px|Physical Cores vs. Logical Cores in VMware management screens]]

**The requirement is based on physical cores on CPU architectures that Cisco has verified have equivalent performance ([[UC Virtualization Supported Hardware#Processors_.2F_CPUs|click here for details]]). E.g. for UC sizing purposes, one core on E5-2600 at 2.5+ GHz is equivalent to one core on E7-2800 at 2.4+ GHz, which are both equivalent to one core on 5600 at 2.53+ GHz.
*Cisco Unity VMs also require VMware CPU Affinity.
*If there is at least one live Unity Connection VM on the physical server, then one CPU core per physical server must be left unused (it is actually being used by ESXi scheduler).
**For example, if you have a host with 12 total physical cores and one or more of the VMs on that host will be Unity Connection, then you can deploy any combination of virtual machines where the total number of vCPU on those virtual machines adds up to 11, with the 12th core left unused. This is regardless of how many Unity Connection VMs are on that host.

::[[Image:UConUCS co-res 3 UCxn 1core unused.JPG|400px|Leaving 1 core unused for Cisco Unity Connection]]

*CPU reservations on the VMs are not required. Use of CPU reservations in lieu of one-to-one CPU core mappings is not supported.
**Even if some of the virtual machines have a reservation, the above one-to-one vCPU to physical core rule still applies – it overrides the reservation.
**For example, if you have a host with a total of 4 physical cores, and you want to run the CUCM 2500 user OVA (which has 800 MHz reservation and requires 1 vCPU) along with other virtual machines, you still must deploy the VMs with a one to one mapping of vCPU to physical core. If you do not follow this rule, your deployment is unsupported.

 

::'''Memory/RAM'''

*Must map 1 GB of VM vRAM to 1 GB of physical RAM. Memory oversubscription is not supported for Cisco UC VMs.
*The sum of virtual machines' vRAM may not exceed the total physical memory on the physical server.
*Additional 2 GB of physical RAM must be provisioned for VMware ESXi itself (this is to cover ESXi overhead to run VMs; for more details see [http://pubs.vmware.com/vsp40_e/resmgmt/wwhelp/wwhimpl/common/html/wwhelp.htm#href=r_overhead_memory_on_virtual_machines.html&single=true "Understanding Memory Overhead" on vmware.com]).

 

 

::'''Storage'''

The following apply to supported DAS, SAN and NAS storage

*Must map 1 GB of VM vDisk to 1 GB of physical storage.
**Storage thin provisioning is not supported (whether at VM layer or storage array layer).
**Any other form of storage oversubscription is not supported.
**The sum of virtual machines' vDisks may not exceed the physical disk space of the physical server's logical volume capacity (i.e. capacity net of overhead for the VM itself, VMFS in vSphere and physical RAID configuration).
**Cisco recommends 10% buffer on top of vDisk values to handle overhead within the VM (such as swap files which are the size of the VM's vRAM). See [[Shared Storage Considerations]] for more details.
*The DAS, NAS or SAN storage solution must also supply enough performance to handle the total load of the VMs.
**Must provide enough IOPS to handle sum of the VMs.
**Kernel command latency must not exceed 2-3 milliseconds.
**Physical device command latency must not exceed 15-20 milliseconds.
**See [[Shared Storage Considerations]] and [[IO Operations Per Second (IOPS)|Storage Performance Requirements]] for more details.
*If the above capacity or performance requirements are not met, the storage system is overloaded and must be "fixed" by either moving virtual machines to alternate storage, or improving storage hardware.

 

::'''Network/LAN'''

*The aggregate networking load of the co-resident virtual machines must be met with the physical networking interface(s) on the host.
*See the UC application design guides (http://www.cisco.com/go/srnd) to size network utilization by UC app VMs. In general, most UC app VMs will not saturate a 1GbE link. Deployments leveraging non-FC-storage (iSCSI, NFS or Unified Fabric/FCoE including UCS B-Series FEX) must account for network traffic from both VM LAN access and VM storage access.
*For other network hardware best practices, see [[QoS Design Considerations for Virtual UC with UCS]].
*If the above capacity or performance requirements are not met, the networking hardware is congested and must be "fixed" by either moving virtual machines to a host with different network access, or provisioning more physical network interfaces.

 

::'''Maximum VM Count per Physical Server'''

*For hardware other than UCS C200 M2 TRC#1, you may mix and match Cisco UC app VM size and quantity as long as you follow all of the sizing rules described above. The maximum number of virtual machines per physical server that can be supported depends on several factors:
*"Capacity" of physical server hardware vs. the quantity and resource usage of [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|VM OVA templates]].
**E.g. using the above physical/virtual sizing rules for CPU, a physical server with 8 total physical cores can only host 4 of the "CUCM 7.5K user OVAs" since those are 2 vCPU each. If the physical server instead had 20 total physical cores, it could host 10 of these VMs (assuming memory, network and storage hardware are also sufficient using the UC sizing rules immediately below).
**All [[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configurations]] are sized for co-residency except for UCS C210 M1 Tested Reference Configuration #1 (which is only sized to host a single CUCM VM of 7500 user capacity). Note UCS C200 M2 Tested Reference Configuration #1 has special restrictions on choice of UC VM, and its allowed VMs are at lower capacity per VM than for other Tested Reference Configurations.
**[[Specification-Based Hardware Support|UC on UCS Specs-based and HP/IBM Specs-based]] deployments allow hardware options that may support a higher or lower max VM count than a [[Tested Reference Configurations (TRC)|UC on UCS Tested Reference Configuration]]. E.g. UCS C210 M2 TRC#1 is a dual-4-core CPU, but UCS C210 M2 specs-based could be configured with dual-6-core (for possibly more VMs) or a single 4-core (for possibly a single VM).
*Note the max VM count may also be further restricted by UC apps that only support "Limited" co-residency as described in the tables after the rules.

[[Image:UConUCS co-res 4 max VM count.JPG|500px|Maximum VM count per physical server]] 

 

::'''Special Requirements for UCS C200 M2 TRC#1 Hardware'''

{{note | This section is only for [[Tested Reference Configurations (TRC)|UC on UCS C200 M2 Tested Reference Configuration #1 which uses Intel E5506 / 2.13 GHz CPU]]. UCS C200 M2 configured with a faster CPU (via [[Specification-Based Hardware Support]]) does not need to follow the rules in this section.}}

*For UCS C200 M2 TRC #1, there are additional TRC-specific restrictions since it uses a slower CPU than other TRCs or specs-based (i.e. E5506 / 2.13 GHz instead of CPU with 2.53 GHz speed or higher). A C200 M2 configured with a different CPU allowed by [[Specification-Based Hardware Support|UC on UCS Specs-based]] does not have these TRC-specific restrictions. Follow these rules for UCS C200M2 TRC#1 with E5506 / 2.13 GHz CPU:
**The only [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|supported virtual machine OVA templates]] are:
***CUCM - Unified Communications Manager 1000 users
***CER - Emergency Responder 12,000 users
***CUC or UCxn - Unity Connection 500 users, 1000 users and 5000 users
***CUP - Unified Presence 1000 users
***CUCCX - Unified Contact Center Express 100 agents
***CUxAC - Unified Department, Business and Enterprise Attendant Consoles
***Other unlisted OVA templates are not supported on C200 M2 TRC #1.
**Otherwise at this time the following co-residency scenarios are supported:
***Any combination allowed by [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]].
***Any other combination provided you follow the [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], and only use the above OVA templates supported for UCS C200 M2 TRC#1.

 

 

==== Special Rules for non-UC and 3rd-party Co-residency ====

See the tables after these rules for the co-residency policy of each Cisco UC app.

Non-UC VMs and 3rd-party app VMs that will be co-resident with Cisco UC app VMs are required to align with all of the following:

*[http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml TAC Technote Document ID: 113520.] For other details on co-resident application performance troubleshooting, see [[Troubleshooting and Performance Monitoring Virtualized Environments]].
*[[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]
*All of the special rules below.

 

 

:'''"Matching" Support Policies'''
:All co-resident VMs must follow the '''"Matching" Support Polices''' rule in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. www.cisco.com/go/uc-virtualized does not describe policies for Cisco non-UC apps or 3rd-party apps

 

:'''Virtual Machine Templates'''
:Cisco non-UC VMs and 3rd-party app VMs own definition of their supported VM OVA templates (or specs for one to be created), similar to what Cisco UC app VMs require in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. http://www.cisco.com/go/uc-virtualized does not describe VM templates for Cisco non-UC apps or 3rd-party apps.

 

:'''CPU'''
:All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''CPU''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]].

 

:'''Memory/RAM'''
:*To enforce "no memory oversubscription", each co-resident VM - whether UC, non-UC or 3rd-party - must have a reservation for vRAM that includes all the vRAM of the virtual machine. For example, if you have a virtual machine that is configured with 4GB of vRAM, then that virtual machine must also have a reservation of 4 GB of vRAM.
:*Otherwise all co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Memory/RAM''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]]. The 2 GB for VMware vSphere is in addition to the sum of the vRAM reservations for the VMs.

 

:'''Storage'''
:*Non-UC VMs and 3rd-party app VMs must define their storage capacity requirements (ideally in an OVA template) and storage performance requirements. These requirements are not captured at http://www.cisco.com/go/uc-virtualized.
:*All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Storage''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], including provisioning sufficient disk space, IOPS and low latency to handle the total VM load.
:*If DAS storage is to be used with non-UC / 3rd-party app VMs, it is highly recommended that pre-deployment testing be conducted, where all VMs are pushed to their highest level of IOPS generation. This is due to DAS environments being more capacity/performance-constrained in general, more dependent on adapter caches in RAID controllers, and Cisco DAS testing only done for UC apps on UCS Tested Reference Configurations.

 

:'''Network/LAN'''
:*Non-UC VMs and 3rd-party app VMs must define the network capacity/performance requirements of their VM OVA templates. These requirements are not captured at http://www.cisco.com/go/uc-virtualized.
:*All co-resident VMs - including non-UC VMs and 3rd-party app VMs - must follow the '''No Hardware Oversubscription''' rules for '''Network/LAN''' in [[#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|General Rules for Co-residency and Physical/Virtual Hardware Sizing]], including provisioning sufficient physical interfaces.

 

 

=== Table of Co-residency Support Policy by Cisco UC Application ===

==== Call Processing and System Management Applications ====

{| style="width: 1076px" class="wikitable FCK__ShowTableBorders"
|-
! UC Application
! Co-residency Support
|-
| Unified Communications Manager (1)
|
*8.6(2)+: Full
*8.0(2) to 8.6(1): UC with UC only

|-
| [[Cisco Unified Communications Manager Business Edition 6000|Unified Communications Manager Business Edition 6000]]
| [[Cisco Unified Communications Manager Business Edition 6000|Limited]]
|-
| Cisco Emergency Responder
| UC with UC only
|-
| Session Manager Edition
|
*8.6(2)+: Full
*8.5(1) to 8.6(1): UC with UC only

|-
| Intercompany Media Engine
| Full
|-
| Unified Attendant Consoles
| Full
|-
| UC Management Suite (OM, SM, SSM, PM)
| Full
|}

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

==== Messaging and Presence Applications ====

{| style="width: 1076px" class="wikitable FCK__ShowTableBorders"
|-
! UC Application
! Co-residency Support
|-
| Cisco Unity Connection
|
*8.6(2)+: Full
*8.0(2) to 8.6(1): UC with UC only

|-
| Cisco Unity
| Full 
{{note|Cisco Unity requires CPU Affinity which may not be desirable for other applications co-resident with Unity.}}

|-
| [[Virtualization for Cisco Unified Presence|Cisco Unified Presence]]
|
*8.6(1)+: Full
*8.0(2) to 8.5: UC with UC only

|}

 

==== Contact Center Applications ====

{| style="width: 726px; height: 345px" class="wikitable FCK__ShowTableBorders"
|-
! UC Application
! Co-residency Support
|-
| [[Virtualization for Unified CCX|Unified Contact Center Express / IP IVR]] 
|
*8.5(x)+,9.0(x)+: Full
*8.0(x): UC with UC only

|-
| [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) components (WFM, QM, AQM, CR, etc.)]
|
*8.5(2)+: Full
*8.0(2) to 8.5(1): UC with UC only

|-
| [[Unified Contact Center Enterprise]] components and deployment models 
|
*8.0(2+), 8.5(x): [[Virtualization for Unified CCE|Limited]]
*9.0(1+): UC with UC only

|-
| [[Virtualization for Unified Intelligence Center|Unified Intelligence Center]] 
|
*UC with UC only

|-
| [[Support for CCMP with UCCE on UCS Hardware|Unified Contact Center Management Portal]] 
|
*UC with UC only

|-
| [[Unified Customer Voice Portal]] (all components)
|
*UC with UC only 

|-
| [[Virtualization for Cisco MediaSense|Cisco MediaSense]]
|
*8.5(X): Not supported
*9.0(1+): Full

|-
| [[Virtualization for Cisco SocialMiner|Cisco SocialMiner]]
|
*UC with UC only

|-
| [[Virtualization for Cisco Finesse|Cisco Finesse]]
|
*UC with UC only

|-
| [[Virtualization for Unified Email Interaction Manager - Web Interaction Manager|Cisco Unified Email Interaction Manager and Web Interaction Manager]]
|
*UC with UC only

|}

==== TelePresence Applications ====

{| style="width: 1076px" class="wikitable FCK__ShowTableBorders"
|-
! UC Application
! Co-residency Support
|-
| Cisco TelePresence Manager
|
1.9.0:

*Up to 4 CTS-Manager instances can be installed on a single server, for service provider deployments with no more than 50 endpoints under management per instance of CTS-Manager.
*1 CTS-Manager and 1 CTMS can be installed on a single UCS server.

|-
| Cisco TelePresence Multipoint Switch 
| 1.9.0: 
*2 CTMS instances can be installed on a single UCS server.
*1 CTMS and 1 CTS-Manager can be installed on a single UCS server.

 

 

|}

== Redundancy and Failover Considerations ==

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

However, since there is no longer a 1:1 relationship between hardware and application instances, "placement logic" must be taken into account to minimize the impact of hardware unavailability or unreachability:

*Avoid placing a primary VM and a backup VM on the same server, chassis or site
*For failover groups, avoid placing all actives on the same server, chassis or site
*Avoid placing all VMs of the same role on the same server, chassis or site

 

== Network, QoS and Shared Storage Design Considerations ==

See [[QoS Design Considerations for Virtual UC with UCS|'''QoS Design Considerations for Virtual UC with UCS''']] and '''[[Shared Storage Considerations]]'''.

 

== Sizing Examples ==

This section shows a sample system configuration based on following the [[High-level Checklist for Design and Implementation]] for the following set of customer requirements:

*'''General Requirements'''
**Three sites - Headquarters (HQ) and two Branches (A and B)
**CUCM and Applications located at each site
**Up to 30,000 lines per sites
**100+ sites
**Transparent use of PSTN if IP WAN unavailable
*'''Headquarters (HQ) Requirements'''
**12K Phones, use Cisco TFTP server
**10K Messaging users
**10K users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 240 agents and 10 supervisors
*'''Branch A Requirements'''
**2K Phones, use Cisco TFTP server
**2K Messaging users
**2K users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 145 agents and 5 supervisors
*'''Branch B Requirements'''
**500 Phones, use Cisco TFTP server
**500 Messaging users
**500 users equipped with Cisco Unified Personal Communicator (CUPC)
**Contact Center with 45 agents and 5 supervisors

 After going through the design process, the following servers were selected to host the virtualized UC applications:

*Six Cisco UCS B200 Blade Servers for HQ (running in a UCS 5100 Chassis connected to UCS 6100 Fabric Interconnect Switches), using TRC#1 (UCS-B200M2-VCS1).
*Three Cisco UCS C210 General-Purpose Rack-Mount Servers for Branch A, using TRC#1 (UCS-C210M2-VCD2)
*Two Cisco UCS C200 General-Purpose Rack-Mount Servers for Branch B, using TRC#1 UCS-C200M2-VCD2)
*Note this example does not include non-UC applications (such as [http://www.cisco.com/go/nexus1000v Cisco Nexus 1000V] or Cisco Network Registrar) or 3rd-party applications such as customer-provided DNS / DHCP / TFTP servers, directories, email, groupware or other business applications. These applications need to run on separate physical servers and are not allowed to be co-resident with UC at this time. See the Co-residency section on this page for more details.

[[Image:UCVirtualSizingEx1.jpg]]

 See below for details on the server layout and application/VM placement at each site. Note that Branch B is using UCS C200 M2 TRC #1 so has restrictions on which VM OVAs were able to be used.

'''HQ server detail:'''

[[Image:UCVirtualSizingEx2.jpg]]

'''Branch A server detail:'''

[[Image:UCVirtualSizingEx3.jpg]]

'''Branch B server detail:'''

[[Image:UCVirtualSizingEx4.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. The UCS B-series Blade Servers and VMWare ordered as Collaboration SKUs can be quoted when ordering separate from the Unified Computing System. Other UCS B-series components must be configured via UCS Advisor below.
::*UCS Advisor - a design and quoting solution for all UCS B-series components including Blade Servers ordered as Collaboration or Data Center SKUs, UCS 5100 Blade Server Chassis, UCS 2100 Fabric Extender and UCS 6100 Fabric Interconnect Switch.

=== Cisco Unified Communications Sizing Tool ===

[http://tools.cisco.com/cucst Cisco Unified Communications Sizing Tool] delivers hardware sizing for complex Enterprise Unified Communications solutions, including Cisco Unified Contact Center Enterprise. The Sizing Tool delivers the virtual machine requirements for Unified Communications applications on the Unified Computing System platform.

=== Cisco Configuration Tool ===

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

=== Ordering Guides ===

Ordering Guides for Unified Communications System 8.x releases are available for Cisco sales, partners, and customers.

 

----

{| 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]]
|}

Create Contact Center Troubleshooting Tips

2012-08-14T20:28:07Z

Rshroyer:

Welcome to Contact Center's Create Troubleshooting Tips Page!

To contribute to this collection, follow this procedure:

#Log into DocWiki-dev using your CEC credentials.
#Enter the name of your new tip in the input box below and click '''Create Troubleshooting Tip'''. A new page opens. <inputbox>
type=create
bgcolor=#FFE0C8
width=100
preload=Template:CCBU Troubleshooting Tip/Preload
buttonlabel=Create Contact Center Troubleshooting Tip
</inputbox>
#Change the ''<Tip Title>'' and the information for each field as required.
#Copy the required category (or categories) from the following list and add it to the bottom of your new page and click '''Save'''.

:*Unified CCE
::*[[[[:Category:Unified CCE, Release 8.0]]]]
::*[[[[:Category:Unified CCE, Release 8.5]]]]
::*[[[[:Category:Unified CCE, Release 9.0]]]]
:*Unified ICM/CCE & Hosted
::*[[[[:Category:Unified ICM/CCE & Hosted, Release 7.5]]]]
:*Unified System CCE
::*[[[[:Category:System CCE, Release 7.5]]]]
:*Cisco Finesse
::*[[[[:Category:Cisco Finesse, Release 8.5]]]]
::*[[[[:Category:Cisco Finesse, Release 9.0|Category:Cisco Finesse, Release 9.0]]]]
:*Cisco MediaSense
::*[[[[:Category:Cisco MediaSense, Release 8.5]]]]
::*[[[[:Category:Cisco MediaSense, Release 9.0]]]]

:*Cisco SocialMiner
::*[[[[:Category:Cisco SocialMiner, Release 8.5]]]]
::*[[[[:Category:Cisco SocialMiner, Release 9.0]]]]

:*CTI OS option
::*[[[[:Category:CTI OS, Release 7.5]]]]
::*[[[[:Category:CTI OS, Release 8.0]]]]
:*Unified CVP
::*[[[[:Category:Unified CVP, Release 7.0(2)]]]]
::*[[[[:Category:Unified CVP, Release 8.0]]]]
::*[[[[:Category:Unified CVP, Release 8.5]]]]
:*Unified Expert Advisor (direct or option)
::*[[[[:Category:Unified Expert Advisor, Release 7.6(1)]]]]
:*Unified IS/IC
::*[[[[:Category:Unified IS, Release 7.5]]]]
::*[[[[:Category:Unified IC, Release 8.0]]]]
::*[[[[:Category:Unified IC, Release 9.0]]]]

:*Unified CCX
::*[[[[:Category:Unified CCX, Release 7.0]]]]
::*[[[[:Category:Unified CCX, Release 8.0]]]]
::*[[[[:Category:Unified CCX, Release 8.5]]]]
::*[[[[:Category:Unified CCX, Release 9.0]]]]
:*Unified IP IVR option
::*[[[[:Category:Unified IP IVR, Release 7.0]]]]
::*[[[[:Category:Unified IP IVR, Release 8.0]]]]
:*Cisco Mobile Supervisor option
::*[[[[:Category:Cisco Mobile Supervisor, Release 1.0]]]]
::*[[[[:Category:Cisco Mobile Supervisor, Release 2.0]]]]
:*CAD, CSD, IP Phone Agent options
::*[[[[:Category:CAD, Release 6.6]]]]
:*Support tools
::*[[[[:Category:Cisco Support Tools, Release 2.x]]]]
:*CRM connector options (SAP, Microsoft, Peoplesoft, Salesforce)
::*[[[[:Category:Unified CRM Connector, Release 1.x]]]]
:*Management portal option
::*[[[[:Category:Unified CCMP, Release 7.5]]]]
::*[[[[:Category:Unified CCMP, Release 8.0]]]]
:*EIM/WIM option
::*For Unified CCE: [[[[:Category:Unified EIM/WIM for Unified CCE, Release 4.2]]]]
::*For Unified CCX: [[[[:Category:Unified EIM/WIM for Unified CCX, Release 4.2]]]]
:*WFO option (QM and WFM)
::*[[[[:Category:Cisco Unified Workforce Optimization]]]]

 

'''Tip 1:''' Contact [mailto:dosproul@cisco.com Doris Sproul] or [mailto:karrande@cisco.com Karrie Anderson] if you need help with setting up a new Category.

'''Tip 2:''' If your category and pages are set up accurately, your newly-created tip will automatically show up in the required product/release category.

'''Tip 3:''' See the [[Guidelines to Create Contact Center Tips]] page for a list of mandatory requirements to make this community page effective for all.

Runtime: Media server rejects open RTSP session

2012-08-14T02:11:55Z

Rshroyer: Added Categories 8.5 and 9.0.

== Media server rejects request to open RTSP session ==

{| border="1"
|-
! '''Problem Summary'''
| The Media Service rejects an RTSP request to open a session, if the DESCRIBE request is received before the first RTP packet.
|-
! '''Error Message'''
| In response to the RTSP DESCRIBE request, you receive the following error:
<code>500 Server Error (Unable to open proxy)<code></code>

|-
! '''Possible Cause'''
| In response to a DESCRIBE request, the Media Service should return the codec details. The codec details will only be known after the Media Service receives the first RTP packet.
|-
! '''Recommended Action'''
| Repeat the DESCRIBE request.
|-
! '''Release'''
| All.
|-
! '''Associated CDETS #'''
| None.
[[Category:Cisco_MediaSense,_Release_8.5]]
[[Category:Cisco_MediaSense,_Release_9.0]]
|}

Runtime: MediaSense server is unable to keep up with incoming recordings

2012-08-14T02:10:28Z

Rshroyer: Added Categories 8.5 and 9.0.

== MediaSense server is unable to keep up with incoming recordings ==

{| border="1"
|-
! '''Problem Summary'''
| The Cisco MediaSense server is unable to keep up with the number of recordings it's supposed to capture.
|-
! '''Error Message'''
| None.
|-
! '''Possible Cause'''
| By default, if the battery backup is not present or not operational, the write cache is disabled on the RAID controllers in the C-Series. When the write cache is disabled, write throughput is lowered.
|-
! '''Recommended Action'''
| The RAID controllers in the C-Series have an optional battery backup for the write cache. Add the battery backup cache to achieve better performance.
|-
! '''Release'''
| All. 
|-
! '''Associated CDETS #'''
| None.
[[Category:Cisco_MediaSense,_Release_8.5]]
[[Category:Cisco_MediaSense,_Release_9.0]]
|}

RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down

2012-08-14T02:09:00Z

Rshroyer: Added Categories 8.5 and 9.0.

== RTMT does not show alarm info if the primary node is down ==

{| border="1"
|-
! '''Problem Summary'''
| The Unified Real Time Monitoring Tool (Unified RTMT) is connected to the secondary node, but after logging in to RTMT, alarm information is not shown. Instead, an error is reported.
|-
! '''Error Message'''
| Error polling alert status - AMC service is down
|-
! '''Possible Cause'''
| By default, the Primary Collector for the Alert Manager and Collector Service (AMC) is configured on the primary node, and the Failover Collector is not active. If the primary node is down, there is no available collector to which RTMT can connect. 
|-
! '''Recommended Action'''
|
 

#When both nodes are in service, sign in to MediaSense Administration on the Primary node, and then enter: '''<nowiki>https://<ip address>:8443/ccmadmin/serviceParamEdit.do</nowiki> '''in the browser address field to access the Unified CM server parameter configuration page.
#Activate the Failover Collector for the Cisco AMC service.

|-
! '''Release'''
|  All.
|-
! '''Associated CDETS #'''
|  CSCtx41763
[[Category:Cisco_MediaSense,_Release_8.5]]
[[Category:Cisco_MediaSense,_Release_9.0]]
|}

RTMT: Unable to login to RTMT from the primary server

2012-08-14T02:06:57Z

Rshroyer: /* Unable to login to RTMT from the primary server */

== Unable to login to RTMT from the primary server ==

{| border="1"
|-
! '''Problem Summary'''
| Logging into RTMT from the Cisco MediaSense primary server fails with an error message.
|-
! '''Error Message'''
| <code>A request to determine the product installed on this cluster has failed. By default, RTMT will display all possible options, however some may not function correctly due to this error.</code>
|-
! '''Possible Cause'''
| You may not have properly uninstalled the previous version of RTMT thus preventing the product verification process.
|-
! '''Recommended Action'''
|
#Uninstall the existing version of RTMT.
#Delete the <userprofile>\.jrtmt folder.
#Re-install RTMT.

|-
! '''Release'''
| All.
|-
! '''Associated CDETS #'''
| None.
[[Category:Cisco_MediaSense,_Release_8.5]]
[[Category:Cisco_MediaSense,_Release_9.0]]
|}

Recording: CUBE disconnects Cisco MediaSense right after recording begins

2012-08-14T02:04:55Z

Rshroyer: Added Categories 8.5 and 9.0.

== CUBE disconnects Cisco MediaSense right after recording begins ==

{| border="1"
|-
! '''Problem Summary'''
| CUBE sends BYE to MediaSense while call is still active. Only the brief beginning of the call gets recorded.
|-
! '''Error Message'''
| Call Control Service log contains BYE request from CUBE with “Reason: Q.850;cause=102” header
|-
! '''Possible Cause'''
| See CSCtz41118. CUBE terminates the forked media because it inappropriately detects media inactivity from MediaSense.
|-
! '''Recommended Action'''
| For now, disable RTP and RTCP media inactivity timers in IOS. Once CSCtz41118 is resolved in a version of IOS which is supported by MediaSense, upgrade your version of IOS and re-enable media inactivity timers if desired.
|-
! '''Release'''
| Release 8.5(4), Release 9.0(1)
|-
! '''Associated CDETS #'''
| CSCtz41118
[[Category:Cisco_MediaSense,_Release_8.5]]
[[Category:Cisco_MediaSense,_Release_9.0]]
|}

Recording: QuickTime does not playback G.729 recording, but status bar keep moving

2012-08-14T02:01:18Z

Rshroyer: Added Categories 8.5 and 9.0.

== QuickTime does not playback G.729 recording, but status bar keep moving ==

{| border="1"
|-
! '''Problem Summary'''
| QuickTime ''appears'' to start playing a G.729 audio recording. The QuickTime slider bar continues to move along as if it were actually playing the file. But you do not hear any sound.
|-
! '''Error Message'''
| None.
|-
! '''Possible Cause'''
| QuickTime does not support playback of G.729 Audio.
|-
! '''Recommended Action'''
| Use an alternate player which supports this codec, if available.
|-
! '''Release'''
| Releases 8.5(1), 8.5(2), 8.5(3), 8.5(4), 9.0(1)
|-
! '''Associated CDETS #'''
| CSCtk11000

[[Category:Cisco_MediaSense,_Release_8.5]]
[[Category:Cisco_MediaSense,_Release_9.0]]
|}

Upgrade: Data out of sync after upgrade

2012-08-14T01:59:12Z

Rshroyer: Added Categories 8.5 and 9.0.

= Data out of sync after upgrade =

{| border="1"
|-
! '''Problem Summary'''
|
The primary server starts taking calls after the switch verson process completes and the secondary server is still runnning the older version of the software. After you switch the secondary server to the newer version of the software, the data may not be synchronized between the primary and secondary servers.

|-
! '''Error Message'''
|
Data is not synchronized between the primary database and secondary database.

|-
! '''Possible Cause'''
|
Mismatched software versions on the primary and secondary servers may cause this issue if the upgrade process is not completed on both servers.

|-
! '''Recommended Action'''
|
Issue the '''run db_reset_replication '''CLI command on the secondary server to synchronize data between both servers. Use the '''show db_synchronization status''' CLI command to check the data synchronization status.

|-
! '''Release'''
|
Release 8.5(3), Release 8.5(4), Release 9.0(1). 

|-
! '''Associated CDETS #'''
|
None.

[[Category:Cisco_MediaSense,_Release_8.5]]
[[Category:Cisco_MediaSense,_Release_9.0]]
|}

Installation: Installation halts with an unrecoverable error

2012-08-14T01:56:37Z

Rshroyer: Added Categories 8.5 and 9.0.

== The installation halts with an unrecoverable error ==

{| border="1"
|-
! '''Problem Summary'''
| The installation fails with an unrecoverable error. 
|-
! '''Error Message'''
| Installation has encountered an unrecoverable internal error. 
|-
! '''Possible Causes'''
|
1) The VM Template or the VM configuration does not meet the requirements. See the [http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all Software Download page] for a list of supported VM templates.

See the ''Unified MCP-Specific Information for OVA Templates'' section in the [[Virtualization for Cisco MediaSense]] website. 

2) You did not create any media disks before starting the installation. These need to be created in your virtual machine after installing the VM template and before installing MediaSense. Please read the installation instructions carefully in the Installation and Administration Guide.  (Note: the SRE template already includes this disk. If you have used the SRE template, then this is not the reason for failure.) 

|-
! '''Recommended Action'''
|
1) Verify that the VM configuration meets the minimum system requirements such as number of CPUs and other requirements specified in the read-me file for each supported VM template. 

Cisco MediaSense, beginning with Release 8.5(2), only supports the VM templates listed in [http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all the Software Download page]. 

2) Verify that you have provisioned at least one media disk, at least 200 GB in size. 

After verifying the above, begin the Mediasense installation again. 

|-
! '''Release'''
| Release 8.5(2), Release 8.5(3), Release 8.5(4), Release 9.0(1). 
|-
! '''Associated CDETS #'''
| None. 
[[Category:Cisco_MediaSense,_Release_8.5]]
[[Category:Cisco_MediaSense,_Release_9.0]]
|}

General: Performance issues as a result of hardware failure

2012-08-14T01:49:30Z

Rshroyer: Added Categories 8.5 and 9.0.

== Performance issues as a result of hardware failure ==

{| border="1"
|-
! '''Problem Summary'''
| You may see performance issues (like recording errors) when a hardware failure has occurred.
|-
! '''Error Message'''
| None. You start seeing recording errors more frequently.
|-
! '''Possible Cause'''
| Hardware failures: For example, the disk drives attached to your host begin failing (most frequently seen). 
|-
! '''Recommended Action'''
|
Perform the following checks: 

#Check the vSphere client.
#Look for alarms generated against the VM host where you see the failure.
#Replace the faulty hardware using the instructions applicable to your failure.

|-
! '''Release'''
| Release 8.5(1), Release 8.5(2), Release 8.5(3), Release 8.5(4), and Release 9.0(1).
|-
! '''Associated CDETS #'''
| None.

[[Category:Cisco_MediaSense,_Release_8.5]]
[[Category:Cisco_MediaSense,_Release_9.0]]
|}

Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information

2012-08-14T01:47:20Z

Rshroyer: Added Categories 8.5 and 9.0.

== The “show db_synchronization status [db_ora_meta|db_ora_config]” command does not show information when executed on the primary ORA DB server ==

{| border="1"
|-
! '''Problem Summary'''
| When both ORA DB servers are up and you execute the CLI command “show db_synchronization status [db_ora_meta|db_ora_config]” on the primary ORA DB server, the command returns no status information and shows a CLI command prompt only.
 

|-
! '''Error Message'''
| None. 
|-
! '''Possible Cause'''
| When you execute the command, the results come from Informix, and Informix will populate the data from either server.
 

|-
! '''Recommended Action'''
| If both ORA primary and secondary DB servers are up, and you do not get any information by executing the command on the primary ORA DB, execute the command on the secondary ORA DB. If no information is returned by either server, the data is already in sync between the servers and no sync job needs to run. 
|-
! '''Release'''
| Release 8.5(1), Release 8.5(2), Release 8.5(3), Release 8.5(4), and Release 9.0(1). 
|-
! '''Associated CDETS #'''
| None. 

[[Category:Cisco_MediaSense,_Release_8.5]]
[[Category:Cisco_MediaSense,_Release_9.0]]
|}

Database: Database not updated after event forwarding

2012-08-14T01:45:15Z

Rshroyer: Added Categories 8.5 and 9.0.

== Database not updated after event forwarding ==

{| border="1"
|-
! '''Problem Summary'''
|
When a client receives an event that was forwarded from the other application server and immediately issues a query to the forwarding server to get additional data related to the event, it does not see the updates that were reported in the event.

|-
! '''Error Message'''
|
None.

|-
! '''Possible Cause'''
|
The client is querying the wrong server. If the event is forwarded from the other server, there will be a flag in the event that indicates this. Whenever the client receives such a message and it wishes to immediately query for information related to that event, it must issue the query to the other server, not the forwarding server.

Event forwarding takes place in parallel with database replication. When an event is forwarded from the server in which a database change occurred, the recipient can be sure that the data on that server has already been updated. However, there is no guarantee that the forwarding server's database was also updated.

{{note| The forwarding node's database will be updated and the data will eventually be replicated.}}

|-
! '''Recommended Action'''
|
If the recipient (client) needs to query the metadata immediately after receiving an event, then the client should issue that query to the server which originated the event--not to the server which forwarded the event.

|-
! '''Release'''
| Release 8.5(1), Release 8.5(2), Release 8.5(3), Release 8.5(4), and Release 9.0(1).
|-
! '''Associated CDETS #'''
| None.
|}

[[Category:Cisco_MediaSense,_Release_8.5]] [[Category:Cisco_MediaSense,_Release_9.0]]

Configuration: MediaSense application does not record even if recording is enabled

2012-08-14T01:41:08Z

Rshroyer:

== MediaSense application does not record even if recording is enabled ==

{| border="1"
|-
! '''Problem Summary'''
| Cisco MediaSense does not record a call even if the recording feature is enabled on the audio forking device.
|-
! '''Error Message'''
| None.
|-
! '''Possible Cause'''
| This happens because Cisco MediaSense does not receive a SIP invite from Unified CM. The software on this device may not be compatible with the minimum software required by the Unified CM server.
|-
! '''Recommended Action'''
|
#The phone devices must use Unified CM software, Release 8.5(2) or later for the recording feature to work. See the [http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html Unified CM compatibility matrix] for further details.
#Check the phone firmware via phone GUI (usually from one of the option under Settings) against Unified CM phone firmware default table. The phone firmware default table is listed in the Unified CM Admin page under "Device - Device Settings - Device Defaults". If the phone firmware does not match the default table, some of the features on the phone may not work--Call recording is one of these features.

|-
! '''Release'''
| Release 8.5(1), 8.5(2), 8.5(3), 8.5(4), and 9.0(1).
|-
! '''Associated CDETS #'''
| None.
|}

[[Category:Cisco_MediaSense,_Release_8.5]] [[Category:Cisco_MediaSense,_Release_9.0]]

Configuration: Conversation after a transfer is not recorded on RT-Lite phones

2012-08-14T01:32:21Z

Rshroyer:

== Conversation after a transfer is not recorded on RT-Lite phones ==

{| border="1"
|-
! '''Problem Summary'''
| No media streams are recorded after a transfer is completed using the RT-Lite (6961) phone with G.729.
|-
! '''Error Message'''
| None.
|-
! '''Possible Cause'''
| Phone load version is not supported.
|-
! '''Recommended Action'''
| Upgrade to the latest phone load.
|-
! '''Release'''
| Release 8.5(1), Release 8.5(2), Releae 8.5(3), Release 8.5(4) and Release 9.0(1).
|-
! '''Associated CDETS #'''
| CSCti71342.
 

|}

[[Category:Cisco_MediaSense,_Release_8.5]] [[Category:Cisco_MediaSense,_Release_9.0]]

Administration: Unknown request error display

2012-08-14T01:27:44Z

Rshroyer: Added Categories 8.5 and 9.0.

== Unknown request error display ==

{| border="1"
|-
! '''Problem Summary'''
| Once you successfully login to the Cisco MediaSense Administration, an unknown request error displays in the UI.
|-
! '''Error Message'''
| <pre>You have reached this page in error. Most likely you typed a wrong URL in the address bar of your browser.
If the problem persists, please contact your Administrator.</pre>
|-
! '''Possible Cause'''
|
This error is known to display if you login to the Cisco MediaSense Administration immediately after implementing the post-installation setup procedure. 

If you wait for a few minutes after the post-installation setup and then login to the Cisco MediaSense Administration, you may not see this error. 

|-
! '''Recommended Action'''
| Ignore this error and continue with your configuration. You only see this error once. You will not see this error when you login again.
|-
! '''Release'''
| Release 8.5(3), 8.5(4), 9.0(1). 
|-
! '''Associated CDETS #'''
| None.

[[Category:Cisco_MediaSense,_Release_8.5]]
[[Category:Cisco_MediaSense,_Release_9.0]]
|}

API: Incorrect session or participant duration

2012-08-14T01:23:28Z

Rshroyer: Added Categories 8.5 and 9.0.

== Incorrect session or participant duration ==

{| border="1"
|-
! '''Problem Summary'''
| Track, participant, or session duration is incorrect or negative (for example: "sessionDuration":-4776).
|-
! '''Error Message'''
| from /var/log/active/syslog/messages: <pre>Aug 23 02:51:05 pauems01 user 6 ilog_impl: Restarting NTP as time offset is -185.215622 msec.

Aug 23 02:51:07 pauems01 user 6 ilog_impl: NTP servers list: 10.192.254.11 10.192.254.1</pre><pre>Aug 23 02:51:07 pauems01 user 6 ilog_impl: ntpdate query response: server 10.192.254.11, \
stratum 1, '''offset -185.225332''', delay 0.04140 23

Aug 02:51:07 ntpdate[17992]: step time server 10.192.254.11 ''offset -185.225332 sec'' (rc=0).</pre><pre>Aug 23 02:51:07 pauems01 user 6 ilog_impl: ntpdate query response: server 10.192.254.1, \
stratum 2, '''offset 0.054938''', delay 0.02736 23

Aug 02:51:07 ntpdate[18001]: adjust time server 10.192.254.1 offset 0.054938 sec (rc=0). </pre>
|-
! '''Possible Cause'''
|
Incorrect duration could have several causes, unsynchronized NTP servers is a known possibility.

The Cisco MediaSense publisher server uses two NTP servers to synchronize time. However, the time on these NTP servers may not be synchronized. As a result, Cisco MediaSense servers switch their times based on the currently-synchronized NTP server.

|-
! '''Recommended Action'''
|
Verify that both NTP servers provide synchronized times.

|-
! '''Release'''
|
Release 8.5(1), Release 8.5(2), Release 8.5(3), Release 8.5(4), and Release 9.0(1).

|-
! '''Associated CDETS #'''
|
None.

[[Category:Cisco_MediaSense,_Release_8.5]]
[[Category:Cisco_MediaSense,_Release_9.0]]
|}

API: MediaSense application sign-in fails with administration credentials

2012-08-14T01:09:02Z

Rshroyer:

==  MediaSense application sign-in fails with administration credentials ==

{| border="1"
|-
! '''Problem Summary'''
| When using administration credentials to access the MediaSense APIs, the sign-in fails.
|-
! '''Error Message'''
| Your login credentials (username or password ) are invalid
|-
! '''Possible Cause'''
| The user attempts an application sign-in using administration credentials.
|-
! '''Recommended Action'''
|
MediaSense application sign-in requires a separate API User with credentials that are different from the Administration Credentials. An API user can be specified using the MediaSense Administration interface (API users can be imported from the list of Unified CM users). 

In Unified CM you should choose (or configure) one or more ''end users ''that will be used as MediaSense API users. After you do this, use the following steps to specify the Unified CM end users as API users in MediaSense:

#Sign in to Cisco MediaSense administration by pointing your browser to'''<nowiki>http://servername/oraadmin</nowiki>''', where servername is the IP address of the MediaSense server
#Choose Administration > MediaSense User Configuration
#Click '''Manage MediaSense Users''', to display the ''Unified CM Users ''list and the ''MediaSense API Users'' list
#Select and import the Unified CM users that you want to specify as API users

|-
! '''Release'''
| Release 8.5(1), 8.5(2), 8.5(3), 8.5(4), 9.0(1).
|-
! '''Associated CDETS #'''
| None
|}

[[Category:Cisco_MediaSense,_Release_8.5]] [[Category:Cisco_MediaSense,_Release_9.0]]

API: API request returns Error 405

2012-08-13T23:56:43Z

Rshroyer:

== API request returns Error 405: Method not supported.  ==

{| border="1"
|-
! '''Problem Summary'''
|
An API request returns a Redirect 302 message. When the request is re-issued, it returns Error 405: Method not supported. This pattern occurs when the request is issued to Port 8443 and MediaSense Release 9.0(1) cannot redirect the request to Port 8440. In Release 9.0(1), the port for API requests changed to Port 8440. MediaSense used Port 8443 in previous releases. Release 9.0(1) features an automatic redirect so that older clients can issue API requests to Port 8443 and be prompted by a Redirect 302 message to re-issue these requests to Port 8440. The RFC-specified response to a Redirect 302 message states that the client should re-issue its API request with the same method. However, many older clients do not conform to this RFC specification. These non-conforming clients change the method before they re-issue the API request. When a client changes the method before it re-issues API the request, the client receives an Error 405: Method Not Supported. Newer clients that conform to the RFC specification re-issue the API request with the same method. These requests with the same method do not return Error 405.

|-
! '''Error Message'''
| Error 405: Method not supported.
|-
! '''Possible Cause'''
|
Clients issue an API request and receive Redirect 302. They change the method of the API request before re-issuing it and receive Error 405. 

|-
! '''Recommended Action'''
|
Update your client so that it issues its API requests to Port 8440 instead of Port 8443. Or, update your client to respond to Redirect 302 by re-issuing the API request with the same method.

If you are trying to simulate the API request using a browser tool such as Poster for Firefox, then issue your request to Port 8440 instead of Port 8443. 

|-
! '''Release'''
| 9.0(1) 
|-
! '''Associated CDETS #'''
| None.
|}

 

[[Category:Cisco_MediaSense,_Release_9.0]]

Troubleshooting Tips for Cisco MediaSense

2012-08-13T23:49:36Z

Rshroyer: Added link to API returns Error 405: Method not supported

'''Back:''' [[Troubleshooting Cisco MediaSense]]

'''Print PDF:''' [[Print Troubleshooting Tips for Cisco MediaSense]]

 

== API ==

*[http://docwiki-dev.cisco.com/wiki/API:_API_request_returns_Error_405#API.C2.A0request_returns.C2.A0Error_405:_Method_not_supported..C2.A0 API: API request returns Error 405: Method not supported]
*[[API: Incorrect participant duration]]
*[[API: MediaSense application sign-in fails with administration credentials]]
*[[API: Missing events and closed subscription]]
*[[API: Incorrect session or participant duration]]

== Administration ==

*[[Administration: Administration Login returns unexpected error]]
*[[Administration: Unable to access Administration and Serviceability UI on a newly installed system]]
*[[Administration: Unknown request error display]]
*[[Administration: Saving an AXL service provider configuration will result in an incorrect error message under certain pre-conditions]]

== Configuration ==

*[[Configuration: Call between two RT phones is not recorded]]
*[[Configuration: Calls using g.722 codec are not recorded]]
*[[Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers]]
*[[Configuration: Conversation after a transfer is not recorded on RT-Lite phones]]
*[[Configuration: Failure to playback audio or video when using RT video phone]]
*[[Configuration: MediaSense application does not record even if recording is enabled]]
*[[Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state]]

== Database ==

*[[Database: Database not updated after event forwarding]]
*[[Database: Database no longer accepts data]]
*[[Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information]]

== General ==

*[[General: Performance issues as a result of hardware failure|General: Check and repair MediaSense file system Installation]]
*[[General: Performance issues as a result of hardware failure]]
*[[General: RTSP live monitoring sessions fail when using CUBE]]

== Installation ==

*[[Installation: Installation halts with an unrecoverable error|Installation: Installation halts with an unrecoverable error]]

== Upgrade ==

*[[Upgrade: Sync after switch version failed]]
*[[Upgrade: Data out of sync after upgrade]]

== Recording ==

*[[Recording: QuickTime does not playback G.729 recording, but status bar keep moving]]
*[[Recording: CUBE disconnects Cisco MediaSense right after recording begins]]
*[http://docwiki-dev.cisco.com/wiki/Recording:_Unified_CM_drops_MediaSense_recording_as_soon_as_recording_begins Recording: Unified CM drops MediaSense recording as soon as recording begins]

== RTMT ==

*[[RTMT: Unable to login to RTMT from the primary server]]
*[[RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down]]

== Runtime ==

*[[Runtime: MediaSense server is unable to keep up with incoming recordings]]
*[[Runtime: Media server rejects open RTSP session]]
*[[Runtime: Open RTSP session to MediaSense failed with timeout]]
*[[Runtime: Close recording session failed with timeout]]

Troubleshooting Tips for Cisco MediaSense

2012-08-13T23:44:42Z

Rshroyer: Added link to API returns Error 405: Method not supported

'''Back:''' [[Troubleshooting Cisco MediaSense]]

'''Print PDF:''' [[Print Troubleshooting Tips for Cisco MediaSense]]

 

== API ==

*[http://docwiki-dev.cisco.com/wiki/API:_API_request_returns_Error_405#API.C2.A0request_returns.C2.A0Error_405:_Method_not_supported..C2.A0 API: API returns Error 405: Method not supported]
*[[API: Incorrect participant duration]]
*[[API: MediaSense application sign-in fails with administration credentials]]
*[[API: Missing events and closed subscription]]
*[[API: Incorrect session or participant duration]]

== Administration ==

*[[Administration: Administration Login returns unexpected error]]
*[[Administration: Unable to access Administration and Serviceability UI on a newly installed system]]
*[[Administration: Unknown request error display]]
*[[Administration: Saving an AXL service provider configuration will result in an incorrect error message under certain pre-conditions]]

== Configuration ==

*[[Configuration: Call between two RT phones is not recorded]]
*[[Configuration: Calls using g.722 codec are not recorded]]
*[[Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers]]
*[[Configuration: Conversation after a transfer is not recorded on RT-Lite phones]]
*[[Configuration: Failure to playback audio or video when using RT video phone]]
*[[Configuration: MediaSense application does not record even if recording is enabled]]
*[[Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state]]

== Database ==

*[[Database: Database not updated after event forwarding]]
*[[Database: Database no longer accepts data]]
*[[Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information]]

== General ==

*[[General: Performance issues as a result of hardware failure|General: Check and repair MediaSense file system Installation]]
*[[General: Performance issues as a result of hardware failure]]
*[[General: RTSP live monitoring sessions fail when using CUBE]]

== Installation ==

*[[Installation: Installation halts with an unrecoverable error|Installation: Installation halts with an unrecoverable error]]

== Upgrade ==

*[[Upgrade: Sync after switch version failed]]
*[[Upgrade: Data out of sync after upgrade]]

== Recording ==

*[[Recording: QuickTime does not playback G.729 recording, but status bar keep moving]]
*[[Recording: CUBE disconnects Cisco MediaSense right after recording begins]]
*[http://docwiki-dev.cisco.com/wiki/Recording:_Unified_CM_drops_MediaSense_recording_as_soon_as_recording_begins Recording: Unified CM drops MediaSense recording as soon as recording begins]

== RTMT ==

*[[RTMT: Unable to login to RTMT from the primary server]]
*[[RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down]]

== Runtime ==

*[[Runtime: MediaSense server is unable to keep up with incoming recordings]]
*[[Runtime: Media server rejects open RTSP session]]
*[[Runtime: Open RTSP session to MediaSense failed with timeout]]
*[[Runtime: Close recording session failed with timeout]]

Virtualization for Cisco MediaSense

2012-08-08T22:52:32Z

Rshroyer:

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

= Updates to this Page =

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

{| class="wikitable FCK__ShowTableBorders"
|-
! Date
! Update
|-
| August 2012
| Removed outdated information about hardware requirements.
|-
| July 2012
| Added information about Release 9.0(1).
|-
| May 2012
| Added information about MediaSense support for high disk count and high disk size for C210 M1/M2 servers.
|-
| January 2012
| Updated page with information on support for Release 8.5(4).
|-
| October 2011
| Added support for Release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
| June 2011
| Updated all links to align with the new Virtualization structure at [[Unified Communications in a Virtualized Environment]].
|-
| April 2011
| Added support for Release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
| November 2010
| Virtualization of Cisco MediaSense on Unified CS C-Series hardware.
|-
| December 2010
| Updated OVA template download link.
|}

= Information for Partners about MediaSense Deployments =

See [[Unified Communications in a Virtualized Environment]].

= Cisco MediaSense-Specific Details for VMware Requirements =

See [[Unified Communications VMWare Requirements]]

*Cisco UCS C-Series Servers, Cisco MediaSense ISO, and ESXi must be installed prior to the Cisco MediaSense installation.
*For other third-party software requirements and for a list of approved UCS servers, see the server requirements and version compatibility with Unified CM sections in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense]. 

== Cisco MediaSense, Release 8.5(1)  and 8.5(2) ==

All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS).

*Cisco MediaSense only supports UCS C210 M1 and M2 servers for Release 8.5(1).
*If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.

 

== Cisco MediaSense, Release 8.5(3) ==

{{note| Cisco MediaSense has stringent requirements for the media disk size for any deployment. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] for more information.}}

Up to 60 terabytes of media storage is supported per cluster, divided into up to six 2TB virtual disks in each of five servers. This assumes that all nodes are B-series servers, for which Cisco MediaSense supports SAN storage. C-series servers, for which only direct attached drives are currently supported, are limited to two 2TB media storage partitions each. Also, no single media partition may be smaller than 200GB.

See the following links for more information:

*See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications
*See the Compatibility Matrix section in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] guide for more information. 

== Cisco MediaSense, Release 8.5(4) ==

In addition to approved UCS servers, Cisco MediaSense 8.5(4) can also be installed on a Services Ready Engine (SRE) module inside a router. An SRE module is a router blade that has its own processors, storage, network interfaces, and memory. Support for SRE requires SRE v2.0 software. For more information about approved SRE models, see the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(4)]. 

If you are using ESXi 5.0, make sure that you [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 5.0 host.

== Cisco MediaSense, Release 9.0(1) ==

Specification-based Virtualization enables Cisco MediaSense to run on Cisco Unified Computing System (Unified CS) servers that are also running other virtual machines. Specification-based Virtualization also enables Cisco MediaSense to run on select HP servers (Note that IBM servers are currently not supported.)

A new Open Virtualization Archive Virtual Machine (OVA-VM) template enables Cisco MediaSense to simplify the deployment of virtual machines in new installations. This template has deployment options for Services Ready Engines, primary servers, secondary servers, and expansion servers.

= Cisco MediaSense-Specific Information for OVA Templates =

If your partitions (VM disk configuration) are not aligned, your data replication between the primary and secondary servers may get congested and result in your data being out of sync. To avoid these problems, only use the VM templates provided by Cisco MediaSense. 

See the following websites for more information: 

*[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_MediaSense Unified Communications Virtualization Downloads (including OVA/OVF Templates).]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=9.0.1&rellifecycle=&relind=AVAILABLE&reltype=all Download OVA Template for Cisco MediaSense, Release 9.0(1)]

 

{{caution| If your VM template or VM configuration does not meet the Cisco MediaSense requirements, it is possible for your installation to halt due to an unrecoverable error. See [[Installation: Installation halts with an unrecoverable error]].}}

 

{{note| Configure the primary server and secondary server in your Cisco MediaSense deployment to have identical hardware in terms of CPU configuration (number of CPUs and speed of the CPU), storage configuration (number of disks, speed of disk, and RAID setup), and memory. Be sure to keep both servers in the same network and run the same version of VMWare Hypervisor on both servers.}}

= Cisco MediaSense-Specific Information for Sizing Guidelines =

The VM-specific sizing informaton required for Cisco MediaSense is additional virtual disks for media storage. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense] for further information.

= How to Dump Install Logs to the VM Serial Port =

See [[How to Dump Install Logs to the Serial Port of the Virtual Machine]].

 

----

{| 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]]
|}

[[Category:Cisco_MediaSense]]

Virtualization for Cisco MediaSense

2012-08-06T19:38:52Z

Rshroyer: Updated changes table.

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

= Updates to this Page =

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

{| class="wikitable FCK__ShowTableBorders"
|-
! Date
! Update
|-
| August 2012
| Removed outdated information about hardware requirements.
|-
| July 2012
| Added information about Release 9.0(1).
|-
| May 2012
| Added information about MediaSense support for high disk count and high disk size for C210 M1/M2 servers.
|-
| January 2012
| Updated page with information on support for Release 8.5(4).
|-
| October 2011
| Added support for Release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
| June 2011
| Updated all links to align with the new Virtualization structure at [[Unified Communications in a Virtualized Environment]].
|-
| April 2011
| Added support for Release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
| November 2010
| Virtualization of Cisco MediaSense on Unified CS C-Series hardware.
|-
| December 2010
| Updated OVA template download link.
|}

= Information for Partners about MediaSense Deployments =

See [[Unified Communications in a Virtualized Environment]].

= Cisco MediaSense-Specific Details for VMware Requirements =

See [[Unified Communications VMWare Requirements]]

*Cisco UCS C-Series Servers, Cisco MediaSense ISO, and ESXi must be installed prior to the Cisco MediaSense installation.
*For other third-party software requirements and for a list of approved UCS servers, see the server requirements and version compatibility with Unified CM sections in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense]. 

== Cisco MediaSense, Release 8.5(1)  and 8.5(2) ==

All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS).

*Cisco MediaSense only supports UCS C210 M1 and M2 servers for Release 8.5(1).
*If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.

 

== Cisco MediaSense, Release 8.5(3) ==

{{note| Cisco MediaSense has stringent requirements for the media disk size for any deployment. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] for more information.}}

Up to 60 terabytes of media storage is supported per cluster, divided into up to six 2TB virtual disks in each of five servers. This assumes that all nodes are B-series servers, for which Cisco MediaSense supports SAN storage. C-series servers, for which only direct attached drives are currently supported, are limited to two 2TB media storage partitions each. Also, no single media partition may be smaller than 200GB.

See the following links for more information:

*See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications
*See the Compatibility Matrix section in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] guide for more information. 

== Cisco MediaSense, Release 8.5(4) ==

In addition to approved UCS servers, Cisco MediaSense 8.5(4) can also be installed on a Services Ready Engine (SRE) module inside a router. An SRE module is a router blade that has its own processors, storage, network interfaces, and memory. Support for SRE requires SRE v2.0 software. For more information about approved SRE models, see the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(4)]. 

If you are using ESXi 5.0, make sure that you [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 5.0 host.

== Cisco MediaSense, Release 9.0(1) ==

Specification-based Virtualization enables Cisco MediaSense to run on Cisco Unified Computing System (Unified CS) servers that are also running other virtual machines. Specification-based Virtualization also enables Cisco MediaSense to run on select HP servers (Note that IBM servers are currently not supported.)

A new Open Virtualization Archive Virtual Machine (OVA-VM) template enables Cisco MediaSense to simplify the deployment of virtual machines in new installations. This template has deployment options for Services Ready Engines, primary servers, secondary servers, and expansion servers.

= Cisco MediaSense-Specific Information for OVA Templates =

If your partitions (VM disk configuration) are not aligned, your data replication between the primary and secondary servers may get congested and result in your data being out of sync. To avoid these problems, only use the VM templates provided by Cisco MediaSense. 

See the following websites for more information: 

*[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_MediaSense Unified Communications Virtualization Downloads (including OVA/OVF Templates).]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=9.0.1&rellifecycle=&relind=AVAILABLE&reltype=all Download OVA Template for Cisco MediaSense, Release 9.0(1)]

 

{{caution| If your VM template or VM configuration does not meet the Cisco MediaSense requirements, it is possible for your installation to halt due to an unrecoverable error. See [[Installation: Installation halts with an unrecoverable error]].}}

 

{{note| Configure the primary server and secondary server in your Cisco MediaSense deployment to have identical hardware in terms of CPU configuration (number of CPUs and speed of the CPU), storage configuration (number of disks, speed of disk, and RAID setup), and memory. Be sure to keep both servers in the same network and run the same version of VMWare Hypervisor on both servers.}}

= Cisco MediaSense-Specific Information for Sizing Guidelines =

The VM-specific sizing informaton required for Cisco MediaSense is additional virtual disks for media storage. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense] for further information.

= How to Dump Install Logs to the VM Serial Port =

See [[How to Dump Install Logs to the Serial Port of the Virtual Machine]].

 

----

{| 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]]
|}

[[Category:Cisco_MediaSense]]

Virtualization for Cisco MediaSense

2012-08-03T21:19:42Z

Rshroyer: Updated download for Cisco MediaSense, Release 9.0(1).

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

= Updates to this Page =

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

{| class="wikitable FCK__ShowTableBorders"
|-
! Date
! Update
|-
| July 2012
| Added information about Release 9.0(1).
|-
| May 2012
| Added information about MediaSense support for high disk count and high disk size for C210 M1/M2 servers.
|-
| January 2012
| Updated page with information on support for Release 8.5(4).
|-
| October 2011
| Added support for Release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
| June 2011
| Updated all links to align with the new Virtualization structure at [[Unified Communications in a Virtualized Environment]].
|-
| April 2011
| Added support for Release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
| November 2010
| Virtualization of Cisco MediaSense on Unified CS C-Series hardware.
|-
| December 2010
| Updated OVA template download link.
|}

= Information for Partners about MediaSense Deployments =

See [[Unified Communications in a Virtualized Environment]].

= VM-Specific Cisco MediaSense Hardware Requirements =

See [[Tested Reference Configurations (TRC)]].

Before you install the Cisco MediaSense software in any server, you must address the following requirements:

*Only Cisco MediaSense must be running on this VM host. No other product can be installed on this server.
*If you are performing a fresh install of Cisco MediaSense in any deployment, be sure to verify that the virtual machine is also fresh (no previously-installed OS is present in the VM).
*On the C210 M1/M2 servers, MediaSense supports higher disk count and size than the disk count and size that is supported by the Tested Reference Configurations for the C210 M1/M2 servers, without requiring specs-based virtualization.

= Cisco MediaSense-Specific Details for VMware Requirements =

See [[Unified Communications VMWare Requirements]]

*Cisco UCS C-Series Servers, Cisco MediaSense ISO, and ESXi must be installed prior to the Cisco MediaSense installation.
*For other third-party software requirements and for a list of approved UCS servers, see the server requirements and version compatibility with Unified CM sections in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense]. 

== Cisco MediaSense, Release 8.5(1)  and 8.5(2) ==

All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS).

*Cisco MediaSense only supports UCS C210 M1 and M2 servers for Release 8.5(1).
*If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.

 

== Cisco MediaSense, Release 8.5(3) ==

{{note| Cisco MediaSense has stringent requirements for the media disk size for any deployment. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] for more information.}}

Up to 60 terabytes of media storage is supported per cluster, divided into up to six 2TB virtual disks in each of five servers. This assumes that all nodes are B-series servers, for which Cisco MediaSense supports SAN storage. C-series servers, for which only direct attached drives are currently supported, are limited to two 2TB media storage partitions each. Also, no single media partition may be smaller than 200GB.

See the following links for more information:

*See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications
*See the Compatibility Matrix section in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] guide for more information. 

== Cisco MediaSense, Release 8.5(4) ==

In addition to approved UCS servers, Cisco MediaSense 8.5(4) can also be installed on a Services Ready Engine (SRE) module inside a router. An SRE module is a router blade that has its own processors, storage, network interfaces, and memory. Support for SRE requires SRE v2.0 software. For more information about approved SRE models, see the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(4)]. 

If you are using ESXi 5.0, make sure that you [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 5.0 host.

== Cisco MediaSense, Release 9.0(1) ==

Specification-based Virtualization enables Cisco MediaSense to run on Cisco Unified Computing System (Unified CS) servers that are also running other virtual machines. Specification-based Virtualization also enables Cisco MediaSense to run on select HP servers (Note that IBM servers are currently not supported.)

A new Open Virtualization Archive Virtual Machine (OVA-VM) template enables Cisco MediaSense to simplify the deployment of virtual machines in new installations. This template has deployment options for Services Ready Engines, primary servers, secondary servers, and expansion servers.

= Cisco MediaSense-Specific Information for OVA Templates =

If your partitions (VM disk configuration) are not aligned, your data replication between the primary and secondary servers may get congested and result in your data being out of sync. To avoid these problems, only use the VM templates provided by Cisco MediaSense. 

See the following websites for more information: 

*[http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_MediaSense Unified Communications Virtualization Downloads (including OVA/OVF Templates).]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=9.0.1&rellifecycle=&relind=AVAILABLE&reltype=all Download OVA Template for Cisco MediaSense, Release 9.0(1)]

 

{{caution| If your VM template or VM configuration does not meet the Cisco MediaSense requirements, it is possible for your installation to halt due to an unrecoverable error. See [[Installation: Installation halts with an unrecoverable error]].}}

 

{{note| Configure the primary server and secondary server in your Cisco MediaSense deployment to have identical hardware in terms of CPU configuration (number of CPUs and speed of the CPU), storage configuration (number of disks, speed of disk, and RAID setup), and memory. Be sure to keep both servers in the same network and run the same version of VMWare Hypervisor on both servers.}}

= Cisco MediaSense-Specific Information for Sizing Guidelines =

The VM-specific sizing informaton required for Cisco MediaSense is additional virtual disks for media storage. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense] for further information.

= How to Dump Install Logs to the VM Serial Port =

See [[How to Dump Install Logs to the Serial Port of the Virtual Machine]].

 

----

{| 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]]
|}

[[Category:Cisco_MediaSense]]

Unified Communications Virtualization Downloads (including OVA/OVF Templates)

2012-08-03T20:57:59Z

Rshroyer: Added links to download pages for Release 9.0(1) and Release 8.5(4).

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

----

 

= Supported Virtual Machine OVA Templates =

'''What is an OVA?'''  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".

'''Do Cisco UC VMs require these OVAs? ''' To be TAC-supported, Virtual Machines for Cisco Unified Communications applications '''must''' use one of the provided OVA templates on this page.

*They represent what the UC apps have been tested with
*It is the only way to ensure UC apps are deployed on "aligned" disks for SAN deployments (i.e. pre-aligned filesystem disk partitions for the OVA's vDisks). 
*OVA configurations are summarized in the tables below for convenience, but authoritative information is on OVA file's release notes on Download Software on www.cisco.com.

  

'''What does "users" mean in tables below?'''   "U'''sers"''' refers to the indicated user count at a particular BHCA, number of devices per user, device mix per VM, etc. 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] . Actual user capacity and total supported devices will be design-dependent; please follow all rules in the design guides and sizing tools for what your application can actually support.

 '''Where do I download these OVAs from?'''  See [[Downloading OVA Templates for UC Applications]] for more information on how to download OVA templates for UC Applications.

{{note |
* UC apps do not support CPU oversubscription. One VM vCPU must map to one physical core (not one logical core) ([[Unified Communications Virtualization Sizing Guidelines | click here]] for details).
* "One vCPU to one physical core" applies for all supported CPU architectures with equivalent performance for UC ([[Unified Communications Virtualization Sizing Guidelines | click here]] for details). E.g. one physical core on E5-2600 at 2.53+ GHz and one physical core on E7-2800 at 2.4+ GHz are equivalent for purposes of UC VM OVAs, sizing and co-residency planning.
* Each VM OVA is only for use on certain CPU architectures. See the notes column for which CPUs are allowed.
**E.g. the CUCM 1K user OVA is only for use on E5-2609/2.4 GHz (only found in UCS C220 M3S TRC#2) and E5506/2.13GHz (only found in UCS C220 M2 TRC#1).
** All other OVAs (such as CUCM 2.5K user, 7.5K user, or 10K user) are only for use on CPUs with minimum core speed of 2.53 GHz [[UC Virtualization Supported Hardware#Processors / CPUs | click here for details]], such as E5-2643/3.3 GHz or E5640 / 2.66 GHz.
}}

For '''Specifications-based''' deployments (non TRC deployments), the CPU core count AND the CPU core speed 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 Template Download Location] 
*[[OVA Template Details for Unified CM Release 8.0]] 
*[[OVA Template Details for Unified CM Release 8.5]] 
*[[OVA Template Details for Unified CM Release 8.6]] 
*[[OVA Template Details for Unified CM Release 9.0]] 

 

== Cisco Emergency Responder ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Emergency Responder 8.5 and 8.6'''
|- style="background: none repeat scroll 0% 0% 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

|}

 

{| border="1" style="width: 1077px; height: 416px;"
|+ '''Supported OVA Templates: Cisco Emergency Responder 8.7 and 9.0'''
|- style="background: none repeat scroll 0% 0% rgb(229, 228, 226);"
! rowspan="2" | VM OVA Capacity 
! colspan="5" | VM OVA Parameters 
! rowspan="2" | Notes 
|- style="background: none repeat scroll 0% 0% rgb(229, 228, 226);"
! vCPU Cores (= Physical Cores)
! Physical CPU Load was Calibrated To
! vRAM (=Physical Memory)
! vDisk (=Physical space)
! vNIC
|-
!
Emergency Responder 12,000 users Only for C200M2 TRC#1

| 2 (with 800 MHz reservation) 
| E5506 2.13 GHz
| 4 GB (with all 4 GB reserved)
| 1x 80 GB disk
| 1
| For use only on UCS C200M2 TRC#1. 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

|-
!
Emergency Responder 20,000 users Not for C200M2 TRC#1

| 1 (with 800 MHz reservation) 
| E5540 2.53 GHz
| 4 GB (with all 4 GB reserved)
| 1x 80 GB disk with pre-aligned disk partitions
| 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

|-
!
Emergency Responder 30,000 users Not for C200M2 TRC#1

| 2 (with 3600 MHz reservation) 
| E5540 2.53 GH
| 6 GB (with all 6 GB reserved)
| 2x 80 GB disk
| 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

|-
!
Emergency Responder 40,000 users Not for C200M2 TRC#1

| 4 (with 7200 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with all 6 GB reserved)
| 2x 80 GB disk
| 1
| Not for use on C200 M2 TRC#1. Limits:
:*40,000 IP phones
:*12,500 analog phones
:*4,000 roaming phones (per Emergency Responder cluster)
:*2,500 LAN switches
:*150,000 switch ports
:*12,500 ERLs

 

|}

 

 

== Session Manager Edition ==

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

*[http://www.cisco.com/cisco/software/release.html?mdfid=282822890&softwareid=283088407&release=9.0%281%29&relind=AVAILABLE&rellifecycle=&reltype=latest General OVA Template Download Location] 

 

{| border="1" style="width: 712px; height: 416px;"
|+ '''Supported OVA Templates: Cisco Intercompany Media Engine, Release 8.6(2)'''
|- style="background: none repeat scroll 0% 0% rgb(229, 228, 226);"
! rowspan="2" | VM OVA Capacity 
! colspan="5" | VM OVA Parameters 
! rowspan="2" | Notes 
|- style="background: none repeat scroll 0% 0% rgb(229, 228, 226);"
! vCPU Cores (= Physical Cores)
! Physical CPU Load was Calibrated To
! vRAM (=Physical Memory)
! vDisk (=Physical space)
! vNIC
|-
!
CIME 5 peer IDs node Only for non-BE6K / certain TRCs - see notes

| 2 (with 3600 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with 6 GB reservation)
| 1x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or C220M3 TRC#2 or BE6000. Up to 5 peer IDs.
 

|-
!
CIME 10 peer IDs node Only for non-BE6K / certain TRCs - see notes

| 4 (with 7200 MHz reservation) 
| E5540 2.53 GHz
| 6 GB (with 6 GB reservation)
| 2x 80 GB disk with pre-aligned disk partitions
| 1
| Not for use with UCS C200M2 TRC#1 or C220M3 TRC#2 or BE6000. Up to 10 peer IDs.
 

|}

 

 

== Cisco Unity Connection ==

*[http://www.cisco.com/cisco/software/type.html?mdfid=283062758&flowid=5455 General Unity Connection OVA Template Download Location] 
*[[OVA Template Details for Unity Connection Release 8.0]] 
*[[OVA Template Details for Unity Connection Release 8.5]] 
*[[OVA Template Details for Unity Connection Release 8.6.1]] 
*[[OVA Template Details for Unity Connection Release 8.6.2]] 
*[[OVA Template Details for Unity Connection Release 9.0.1]] 

 

== Cisco Unity ==

{| border="1"
|+ '''Supported OVA Templates: Cisco Unity'''
|- style="background: none repeat scroll 0% 0% 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 (referred to as IM and Presence from Release 9.0(1) and later) ==

See also:

*[http://www.cisco.com/cisco/software/navigator.html?mdfid=280448682&i=rs General OVA Template Download Location]
*[[OVA Template Details for Unified Presence Release 8.0(x)]] 
*[[OVA Template Details for Unified Presence Release 8.5(x)]] 
*[[OVA Template Details for Unified Presence Release 8.6(1)]] 
*[[OVA Template Details for Unified Presence Release 8.6(2)]] 
*[[OVA Template Details for Unified Presence Release 8.6(3)]] 
*[[OVA Template Details for Unified Presence Release 8.6(4)]] 
*[[OVA Template Details for IM and Presence Release 9.0(1)]] 

 

== Cisco Unified Contact Center Express/Cisco Unified IP Intelligent Voice Response (IP IVR) ==

{{Note| The information for Unified IP IVR is the same as Unified CCX.}}

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| Unified CCX OVA version 2 is for use with ESXi 4.1. Please follow [[Unified Communications VMware Requirements]] for ESXi 4.1 requirements (VMware Tools upgrade, LRO disabling, etc.)}}

 

{| border="1"
|+ '''Supported OVA Templates: Cisco Unified Contact Center Express'''
|- style="background: none repeat scroll 0% 0% 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 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 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 Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

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

| 1
| rowspan="3" | See [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_5/installation/guide/uccx851ig.pdf Installing Cisco Unified Contact Center Express Release 8.5(1) guide]for more information on vDisk space.
|-
! 300 agents
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

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

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

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

| 1
| rowspan="3" | See [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_5/installation/guide/uccx851ig.pdf Installing Cisco Unified Contact Center Express Release 9.0(1) guide]for more information on vDisk space.
|-
! 300 agents
| 2
| 4 GB
|
2x 146 GB

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

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

:*vDisk 1 = Operating System and Unified CCX binaries
:*vDisk 2 = RAID 1 mirror will be setup between vDisk 1 and vDisk 2

| 1
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.3&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 9.0]
| 2
| 4 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 • 900 named users • 300 concurrent users 
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.3&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 9.0 Base Server Configuration (CR/QM/AQM)]
| 2
| 4 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 )
| 1
| Capacities • 3600 named users • 1200 concurrent users
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.3&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 9.0 Recording Server Configuration (CR/QM/AQM)]
| 4
| 4 GB
| vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM recording service binaries, vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recording cache
| 1
| Capacities • 300 concurrent voice recordings for Server (SPAN) and Network recording • 150 concurrent voice and screen recordings, recordings for Server (SPAN) and Network recording
|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.2]
| 2
| 4 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

:*900 named users
:*300 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Base Server Configuration (CR/QM/AQM)]
| 2
| 4 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)

| 1
|
Capacities

:*3600 named users
:*1200 concurrent users

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=2.1&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.2 Recording Server Configuration (CR/QM/AQM)]
| 4
| 4 GB
|
:*vDisk 1 = 40 GB Minimum Operating system, Cisco Unified Contact Center Express WFO QM recording service binaries
:*vDisk 2 = 146 GB Cisco Unified Contact Center Express WFO QM recording cache

| 1
|
Capacities

:*300 concurrent voice recordings for Server (SPAN) and Network recording
:*150 concurrent voice and screen recordings, recordings for Server (SPAN) and Network recording
:*'''Virtualizing''' the Monitor server for Server (SPAN) recording is '''not '''supported on the UCS platform

|-
! colspan="2" | [http://www.cisco.com/cisco/software/release.html?mdfid=270569179&flowid=5217&softwareid=283733053&release=1.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFM 8.5.1]
| 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.0&rellifecycle=&relind=AVAILABLE&reltype=all Unified CCX WFO QM 8.5.1 Base Server 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)

| 1
|
Capacities

:*300 named users
:*150 concurrent users

|
|}

== 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: none repeat scroll 0% 0% 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: none repeat scroll 0% 0% 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
| 
|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=283884662&flowid=28561&softwareid=282773197&release=8.6&relind=AVAILABLE&rellifecycle=&reltype=latest OM, SM, SSM OVAs] CPU/Memory in table above.
|
|
|
| 1
| 
|}

 

{| border="1"
|+ '''Supported OVA Templates: UC Management Suite (PM, OM, SM, SSM) for Hosted Collaboration Solution'''
|- style="background: none repeat scroll 0% 0% 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]
*[http://docwiki.cisco.com/w/index.php?title=Virtualization_for_Unified_CCE#Unified_CCE_Scalability_Impacts Scalability Impacts]
*[[OVA Template Details for Unified Contact Center Enterprise Release 8.x]]
*[[OVA Template Details for Unified Contact Center Enterprise Release 9.x]]

== 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: none repeat scroll 0% 0% 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:

*[http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_MediaSense Virtualization for Cisco MediaSense]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=9.0.1&rellifecycle=&relind=AVAILABLE&reltype=all Download OVA Template for Cisco MediaSense, Release 9.0(1)]
*[http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.4&rellifecycle=&relind=AVAILABLE&reltype=all Download OVA Template for Cisco MediaSense, Release 8.5(4)]

 To promote ease of use, Cisco MediaSense, Release 9.0(1) has only one template. This template contains several deployment options as shown in the following table.   

{| border="1" cellspacing="1" cellpadding="1" width="812"
|+ '''Supported OVA Template: Cisco MediaSense, Release 9.0(1)''' 
|-
! valign="baseline" scope="col" align="center" | Deployment  
! valign="baseline" scope="col" align="center" |   vCPU   
! valign="baseline" scope="col" align="center" |
CPU      reservation  

! valign="baseline" scope="col" align="center" |  vRAM 
! valign="baseline" scope="col" align="center" |    vDisk    
! valign="baseline" scope="col" align="center" | Notes            
|-
! valign="baseline" align="center" | SRE 
| valign="baseline" align="center" |
 2

| valign="baseline" align="center" |
  2200 MHz

| valign="baseline" align="center" |
 6 GB

| valign="top" align="left" |
Disk 1: 80 GB for OS Disk 2: 80 GB for DB  Disk 3: 200 GB for media               

| valign="top" align="left" |
Includes a fixed 200 GB disk for media storage. No expansion nodes supported. No additional media storage supported. 

|-
! valign="baseline" align="center" |  Primary/Secondary    
| valign="baseline" align="center" |    7 
| valign="baseline" align="center" |   15000 MHz 
| valign="baseline" align="center" |  8 GB 
| valign="top" align="left" |
Disk 1: 80 GB for OS  Disk 2: 600 GB for DB 

| valign="top" align="left" |
User must add media disks prior to installation. 

|-
! valign="baseline" align="center" | Expansion
| valign="baseline" align="center" |    7
| valign="baseline" align="center" | 10000 MHz 
| valign="baseline" align="center" | 8 GB 
| valign="top" align="left" |
Disk 1: 80 GB for OS Disk 2: 80 GB

| valign="top" align="left" |
User must add media disks prior to installation.

|}

 

{| border="1"
|+ '''Supported OVA Templates: Cisco MediaSense, Release 8.5'''
|-
! 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)

Release 8.5(3)

Release 8.5(4)

|-
! 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
|-
! CMS_SRE_v8.5_vmv7
| 2
| 6 GB
| 2 x 80 GB (thick provisioning) 1 x 200 GB (thick provisioning) for Media storage
| 1 (with static MAC address)
| Release 8.5(4)
|}

 

== 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: none repeat scroll 0% 0% 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 CUIC (200 Reporting Users)]
| 4
| 6 GB
| 1x 146 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: none repeat scroll 0% 0% 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&release=9.0.1&relind=AVAILABLE&softwareid=283733464&rellifecycle=&reltype=all| Cisco SocialMiner OVA Templates]

{| border="1"
|+ '''Supported OVA Templates: Cisco SocialMiner'''
|- style="background: none repeat scroll 0% 0% rgb(229, 228, 226);"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
|-
! Large deployment option
| 4
| 12 GB
| 1x 146 GB and 1x 256 GB
| 1
|-
! Small deployment option
| 2
| 8 GB
| 2x 80GB
| 1
|}

== Cisco Unfied Email Interaction Manager and Web Interaction Manager ==

  

{| cellspacing="1" cellpadding="1" border="1"
|-
! scope="col" | Application, OVA Capacity and Notes+Download Link
! scope="col" | Contents
! scope="col" | No of VM's to deploy of each component
! scope="col" | vCPU
! scope="col" | vDisk
! scope="col" | vRAM/Memory
|-
|
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_1_v2.0] 

Deployment Option:

100 agents - Email Only 

| Application, Services Server ,File server Messaging Server ,Web Server and Database server
| 1
| 2 
| 1 x 80GB
| 4
|-
| rowspan="2" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_2_v2.0] 

Deployment Option:

140 agents - Email Only

 

| Application, Services Server ,File server Messaging Server and Web server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 2
| 1 x 80GB
| 4
|-
| rowspan="2" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_3_v2.0] 

Deployment Option:

100 agents - Chat only or

100 agents - Email and Chat  

| Application, Services Server ,File server Messaging Server and Database server
| 1
| 2
| 1 x 80GB
| 4
|-
| Web Server
| 1
| 1
| 1 x 80GB
| 2 
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_4_v2.0] 

Deployment Option:

250 Agents - Email and Chat or 120 Agents - BC and CallBack

 

 

| Web Server
| 1
| 1
| 1 x 80GB
| 1 
|-
| Application server
| 1
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 2 
| 1 x 80 GB for OS, 1 x 150 GB for DB
| 4
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_5_v2.0] 

Deployment Option:

500 Agents - Email and Chat or 240 Agents - BC and CallBack 

 

| Web Server
| 2 
| 1
| 1 x 80GB
| 1 
|-
| Application server
| 2
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 4
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 8
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 1
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_6_v2.0] 

Deployment Option:

750 Agents - Email and Chat or 360 Agents - BC and CallBack 

| Web Server
| 3
| 1
| 1 x 80GB
| 1
|-
| Application server
| 3
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 4
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 16 
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_7_v2.0] 

Deployment Option:

1000 Agents - Email and Chat or 480 Agents - BC and CallBack 

| Web Server
| 4
| 1
| 1 x 80GB
| 1
|-
| Application server
| 4 
| 2
| 1 x 80GB
| 2
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 8
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|-
| rowspan="6" |
[http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all EIMWIM_Template_8_v2.0] 

Deployment Option:

1250 Agents - Email and Chat or 600 Agents - BC and CallBack 

| Web Server
| 5 
| 1
| 1 x 80GB
| 1 
|-
| Application server
| 5
| 2
| 1 x 80GB
| 2 
|-
| Services Server
| 1
| 2
| 1 x 80GB
| 8
|-
| Database Server
| 1
| 8
| 1 x 80 GB for OS, 1 x 400 GB for DB
| 16
|-
| File Server
| 1
| 2
| 1 x 80GB
| 2
|-
| Messaging Server
| 1
| 2
| 1 x 80GB
| 2
|}

 

== Cisco Media Blender ==

{| width="1054" cellspacing="1" cellpadding="1" border="1" align="center" style="width: 1054px; height: 102px;"
|-
|
 '''Application, OVA Capacity and Notes+Download Link'''

|         '''Contents    '''  
| '''No of VM's to deploy of each component'''
| '''vCPU'''
| '''vDisk'''
| '''vRAM/Memory'''
|-
|
 [http://www.cisco.com/cisco/software/release.html?mdfid=280970910&catid=278875240&softwareid=283929858&release=2.0&rellifecycle=&relind=AVAILABLE&reltype=all Cisco Media Blender]

|
 

Cisco Media Blender

|
 1

|
 2

|
 1 x 80GB

|
 2

|}

 

== Cisco Finesse ==

See also:

*[[Virtualization for Cisco Finesse|Cisco Finesse]]
*[http://www.cisco.com/cisco/software/type.html?mdfid=283613135&flowid=30701 Cisco Finesse OVA Templates] 

{| border="1"
|+ '''Supported OVA Templates: Cisco Finesse'''
|- style="background: none repeat scroll 0% 0% rgb(229, 228, 226);"
! Application, OVA Capacity and Notes+Download Link
! vCPU Cores
! vRAM / Memory
! vDisk
! vNIC
! Notes
! 
|-
! Finesse_2000_agents_v9.0.1_vm8
| 4
| 8 GB
| 1x 146 GB
| 1
| Release 9.0(1)
|-
! Finesse_2000_agents_v1.0_vmv7 
| 4
| 8 GB
| 1x 146 GB
| 1
| Release 8.5(3)
|}

  

== TelePresence Applications ==

{| border="1"
|+ '''Supported OVA Templates: TelePresence Applications'''
|- style="background: none repeat scroll 0% 0% 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=284132721&flowid=29922&softwareid=280887004&release=1.8.0%28582%29 Cisco TelePresence Manager] 
| align="center" | 2
| align="center" | 8 GB (4 GB reserved)
| align="center" | 1 x 200 GB
| align="center" | 1
|
1.9.0 Supported Co-residency Configurations:

*Up to 4 CTS-Manager instances can be installed on a single server, for service provider deployments with no more than 50 endpoints under management per instance of CTS-Manager. 
*1 CTS-Manager and 1 CTMS can be installed on a single UCS server. 

 

|-
! [http://www.cisco.com/cisco/software/release.html?mdfid=281043620&flowid=20525&softwareid=281149680&release=1.8.0%281026%29 Cisco TelePresence Multipoint Switch] 
| align="center" | 4
| align="center" | 6 GB (2.304 GB reserved)
| align="center" | 1 x 100 GB
| align="center" | 1
|
1.9.0 Supported Co-residency Configurations:

:*2 CTMS instances can be installed on a single UCS server.
:*1 CTMS and 1 CTS-Manager can be installed on a single UCS server.

 

|}

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

Print Troubleshooting Tips for Cisco MediaSense

2012-08-03T19:58:11Z

Rshroyer: Added topic

'''Back:''' [[Troubleshooting Tips for Cisco MediaSense]]

=== Create PDF for Troubleshooting Tips for Cisco MediaSense ===

{{Template:PDF_Print_Form|ROWS=45|DEFAULT_FILENAME=troubleShooting-tips-cisco-mediaSense.pdf|BUTTON_LABEL=Create PDF|DEFAULT_TEXT=Troubleshooting Tips for Cisco MediaSense
API: Incorrect participant duration
API: Missing events and closed subscription
API: Incorrect session or participant duration
Administration: Administration Login returns unexpected error
Administration: Unable to access Administration and Serviceability UI on a newly installed system
Administration: Unknown request error display
Configuration: Call between two RT phones is not recorded
Configuration: Calls using g.722 codec are not recorded
Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers
Configuration: Conversation after a transfer is not recorded on RT-Lite phones
Configuration: Failure to playback audio or video when using RT video phone
Configuration: MediaSense application does not record even if recording is enabled
Database: Database not updated after event forwarding
Database: Database no longer accepts data
Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information
General: Performance issues as a result of hardware failure
General: RTSP live monitoring sessions fail when using CUBE
Installation: Installation halts with an unrecoverable error
Upgrade: Sync after switch version failed
Upgrade: Data out of sync after upgrade
Recording: QuickTime does not playback G.729 recording, but status bar keep moving
RTMT: Unable to login to RTMT from the primary server
Runtime: MediaSense server is unable to keep up with incoming recordings
Runtime: Media server rejects open RTSP session
Runtime: Open RTSP session to MediaSense failed with timeout
Runtime: Close recording session failed with timeout
}}

Troubleshooting Tips for Cisco MediaSense

2012-08-03T19:29:34Z

Rshroyer:

'''Back:''' [[Troubleshooting Cisco MediaSense]]

'''Print PDF:''' [[Print Troubleshooting Tips for Cisco MediaSense]]

 

== API ==

*[[API: Incorrect participant duration]]
*[[API: MediaSense application sign-in fails with administration credentials]]
*[[API: Missing events and closed subscription]]
*[[API: Incorrect session or participant duration]]

== Administration ==

*[[Administration: Administration Login returns unexpected error]]
*[[Administration: Unable to access Administration and Serviceability UI on a newly installed system]]
*[[Administration: Unknown request error display]]
*[[Administration: Saving an AXL service provider configuration will result in an incorrect error message under certain pre-conditions]]

== Configuration ==

*[[Configuration: Call between two RT phones is not recorded]]
*[[Configuration: Calls using g.722 codec are not recorded]]
*[[Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers]]
*[[Configuration: Conversation after a transfer is not recorded on RT-Lite phones]]
*[[Configuration: Failure to playback audio or video when using RT video phone]]
*[[Configuration: MediaSense application does not record even if recording is enabled]]
*[[Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state]]

== Database ==

*[[Database: Database not updated after event forwarding]]
*[[Database: Database no longer accepts data]]
*[[Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information]]

== General ==

*[[General: Performance issues as a result of hardware failure|General: Check and repair MediaSense file system Installation]]
*[[General: Performance issues as a result of hardware failure]]
*[[General: RTSP live monitoring sessions fail when using CUBE]]

== Installation ==

*[[Installation: Installation halts with an unrecoverable error|Installation: Installation halts with an unrecoverable error]]

== Upgrade ==

*[[Upgrade: Sync after switch version failed]]
*[[Upgrade: Data out of sync after upgrade]]

== Recording ==

*[[Recording: QuickTime does not playback G.729 recording, but status bar keep moving]]
*[[Recording: CUBE disconnects Cisco MediaSense right after recording begins]]
*[http://docwiki-dev.cisco.com/wiki/Recording:_Unified_CM_drops_MediaSense_recording_as_soon_as_recording_begins Recording: Unified CM drops MediaSense recording as soon as recording begins]

== RTMT ==

*[[RTMT: Unable to login to RTMT from the primary server]]
*[[RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down]]

== Runtime ==

*[[Runtime: MediaSense server is unable to keep up with incoming recordings]]
*[[Runtime: Media server rejects open RTSP session]]
*[[Runtime: Open RTSP session to MediaSense failed with timeout]]
*[[Runtime: Close recording session failed with timeout]]

Troubleshooting Cisco MediaSense

2012-08-03T18:56:59Z

Rshroyer:

:'''View Tips and FAQs for Cisco MediaSense:'''

::*[[Troubleshooting Tips for Cisco MediaSense]]

::*[[FAQs for Cisco MediaSense]]

 

----

[[Category:Cisco_MediaSense]] [[Category:Troubleshooting]]

Runtime: Media server rejects open RTSP session

2012-08-02T03:58:35Z

Rshroyer: Changed release to "all".

Runtime: MediaSense server is unable to keep up with incoming recordings

2012-08-02T03:57:29Z

Rshroyer: Changed release to "all".

RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down

2012-08-02T03:56:44Z

Rshroyer: Added release 9.0(1)

RTMT: Unable to login to RTMT from the primary server

2012-08-02T03:55:51Z

Rshroyer: Changed release to "all".

Recording: CUBE disconnects Cisco MediaSense right after recording begins

2012-08-02T03:54:34Z

Rshroyer: Added release 9.0(1)

Recording: QuickTime does not playback G.729 recording, but status bar keep moving

2012-08-02T03:53:15Z

Rshroyer: Added release 9.0(1)

Upgrade: Data out of sync after upgrade

2012-08-02T03:52:05Z

Rshroyer: Added release 9.0(1)

Installation: Installation halts with an unrecoverable error

2012-08-02T03:51:12Z

Rshroyer: Added release 9.0(1)

== The installation halts with an unrecoverable error ==

{| border="1"
|-
! '''Problem Summary'''
| The installation fails with an unrecoverable error. 
|-
! '''Error Message'''
| Installation has encountered an unrecoverable internal error. 
|-
! '''Possible Causes'''
|
1) The VM Template or the VM configuration does not meet the requirements. See [http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all the Software Download page] for a list of supported VM templates.

See the ''Unified MCP-Specific Information for OVA Templates'' section in the [[Virtualization for Cisco MediaSense]] website. 

2) You did not create any media disks before starting the installation. These need to be created in your virtual machine after installing the VM template and before installing MediaSense. Please read the installation instructions carefully in the Installation and Administration Guide.  (Note: the SRE template already includes this disk. If you have used the SRE template, then this is not the reason for failure.) 

|-
! '''Recommended Action'''
|
1) Verify that the VM configuration meets the minimum system requirements such as number of CPUs and other requirements specified in the read-me file for each supported VM template. 

Cisco MediaSense, beginning with Release 8.5(2), only supports the VM templates listed in [http://www.cisco.com/cisco/software/release.html?mdfid=283613140&softwareid=283733468&release=8.5.1&rellifecycle=&relind=AVAILABLE&reltype=all the Software Download page]. 

2) Verify that you have provisioned at least one media disk, at least 200 GB in size. 

After verifying the above, begin the Mediasense installation again. 

|-
! '''Release'''
| Release 8.5(2), Release 8.5(3), Release 8.5(4), Release 9.0(1). 
|-
! '''Associated CDETS #'''
| None. 
|}

General: RTSP live monitoring sessions fail when using CUBE

2012-08-02T03:50:26Z

Rshroyer: Added release 9.0(1)

== RTSP live monitoring sessions fail when using CUBE ==

{| border="1"
|-
! '''Problem Summary'''
| When using a mixed load in a CUBE deployment, multiple RTSP live monitoring sessions failed (RTSP packets were dropped). Recordings may also sound very choppy on playback.
|-
! '''Error Message'''
| None.
|-
! '''Possible Cause'''
| CUBE may be using a lower Ethernet cable connection (for example, 100 MB connection) instead of the suggested 1 GB Ethernet cable connection. Under a heavy load, this connection may cause multiple IP packets to drop.
|-
! '''Recommended Action'''
| If your CUBE deployment is running heavy loads, verify that the Ethernet cable connecting CUBE to the switch is 1 GB. 
|-
! '''Release'''
| Release 8.5(3), Release 8.5(4), Release 9.0(1).
|-
! '''Associated CDETS #'''
| None.
|}

General: Performance issues as a result of hardware failure

2012-08-02T03:49:01Z

Rshroyer: Added release 9.0(1)

Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information

2012-08-02T03:48:03Z

Rshroyer: Added release 9.0(1)

Database: Database not updated after event forwarding

2012-08-02T03:47:05Z

Rshroyer: Added release 9.0(1)

Configuration: MediaSense application does not record even if recording is enabled

2012-08-02T03:46:13Z

Rshroyer: