Virtualization for Cisco MediaSense

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Cisco MediaSense-Specific Information for Sizing Guidelines)
m (1 revision)
(23 intermediate revisions not shown)
Line 9: Line 9:
! Date  
! Date  
! Update
! Update
 +
|-
 +
| February 2013
 +
| Added deployment table for release 9.1(1) and removed comment saying 'IBM servers are not supported at this time'.
 +
|-
 +
| 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  
| October 2011  
-
| Added support for Release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
+
| Added support for release 8.5(3) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
|-
| June 2011  
| June 2011  
-
| Updated all links to align with the new Virtualization strucutre at [[Unified Communications in a Virtualized Environment]].
+
| Updated all links to align with the new Virtualization structure at [[Unified Communications in a Virtualized Environment]].
|-
|-
| April 2011  
| April 2011  
-
| Added support for Release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
+
| Added support for release 8.5(2) in the relevant links below, OVA template guidelines, and serial port log dump procedure.
|-
|-
| November 2010  
| November 2010  
-
| Virtualization of Cisco MediaSense on UCS C Series hardware.
+
| Virtualization of Cisco MediaSense on Unified CS C-Series hardware.
|-
|-
| December 2010  
| December 2010  
Line 26: Line 44:
|}
|}
-
= Information for Partners about Cisco MediaSense Deployments  =
+
= Information for Partners about MediaSense Deployments  =
See [[Unified Communications in a Virtualized Environment]].  
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).
 
= Cisco MediaSense-Specific Details for VMware Requirements  =
= Cisco MediaSense-Specific Details for VMware Requirements  =
Line 46: Line 55:
*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]. <br>
*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]. <br>
-
== Cisco MediaSense, Release 8.5(1)&nbsp; and 8.5(2) ==
+
== Cisco MediaSense, Release 8.5(1)&nbsp; and 8.5(2) ==
All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS).  
All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS).  
Line 53: Line 62:
*If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.
*If you are using ESXi 4.1, be sure to [[Disable LRO|disable Large Receive Offload (LRO)]] on the ESXi 4.1 host.
-
 
+
<br>
== Cisco MediaSense, Release 8.5(3)  ==
== Cisco MediaSense, Release 8.5(3)  ==
Line 59: Line 68:
{{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.}}  
{{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.
+
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 following links for more information:  
Line 65: Line 74:
*See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications  
*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.<br>
*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.<br>
 +
 +
== 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)].<br>
 +
 +
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 and IBM servers.
 +
 +
A new Open Virtualization Archive Virtual Machine (OVA-VM)&nbsp;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&nbsp;servers, and expansion servers.
 +
 +
==Cisco MediaSense, Release 9.1(1) ==
 +
 +
For this release, there is again only one VM template. The template provides a selection for which deployment type is being installed.
= Cisco MediaSense-Specific Information for OVA Templates  =
= Cisco MediaSense-Specific Information for OVA Templates  =
Line 73: Line 98:
*[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://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=8.5.2&relind=AVAILABLE&rellifecycle=&reltype=latest Cisco MediaSense OVA 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)]
 +
*[http://software.cisco.com/download/release.html?mdfid=283613140&amp;softwareid=283733468&amp;release=9.1.1&amp;relind=AVAILABLE&amp;rellifecycle=&amp;reltype=latest Download OVA Template for Cisco MediaSense, Release 9.1(1)]
<br>
<br>
Line 85: Line 111:
= Cisco MediaSense-Specific Information for Sizing Guidelines  =
= 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.
+
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<br> =
= How to Dump Install Logs to the VM Serial Port<br> =

Revision as of 19:35, 15 March 2013

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

Contents

Updates to this Page

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

Date Update
February 2013 Added deployment table for release 9.1(1) and removed comment saying 'IBM servers are not supported at this time'.
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 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 and IBM servers.

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, Release 9.1(1)

For this release, there is again only one VM template. The template provides a selection for which deployment type is being installed.

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.3/5 (3 votes cast)

Personal tools