Virtualization for Cisco MediaSense

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Updated changes table.)
m (1 revision)

Revision as of 19:03, 7 August 2012

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

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 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, Release 8.5(3)

Note Note: Cisco MediaSense has stringent requirements for the media disk size for any deployment. See the 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:

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 Solution Reference Network Design for Cisco MediaSense, Release 8.5(4).

If you are using ESXi 5.0, make sure that you 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:

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

Back to: Unified Communications in a Virtualized Environment

Rating: 4.6/5 (5 votes cast)

Personal tools