{{note| Cisco MediaSense product documentation reflects the fields and names used in the application user interfaces and application programming interfaces of this product. Effective Release 8.5(2), these names are restricted to Cisco MediaSense and Open Recording Architecture (ORA/ora).}}

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

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

-

{{note| If you are using ESXi 4.1, be sure to 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.

-

# Select the host > Configuration > Advanced Settings.

+

-

# Select Net and scroll down slightly more than half way.

+

-

# Set the following parameters from 1 to 0:

+

-

#* Net.VmxnetSwLROSL

+

-

#* Net.Vmxnet3SwLRO

+

-

#* Net.Vmxnet3HwLRO

+

-

#* Net.Vmxnet2SwLRO

+

-

#* Net.Vmxnet2HwLRO

+

-

# Reboot the ESXi host to activate these changes.

+

-

= VM-Specific Cisco MediaSense Software Requirements =

+

<br>

-

See [[Unified Communications VMWare Requirements]].

+

-

The following software requirements apply specifically to Cisco MediaSense:

+

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

-

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

+

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

-

= VM-Specific Cisco MediaSense Hardware Requirements =

+

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.

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>

-

The VM-specific sizing information required for Cisco MediaSense is additional virtual disks for media storage. See the SRND for Cisco MediaSense for further information.

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.

-

Back to [[Unified Communications Virtualization]]

+

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 =

+

+

If your partitions (VM&nbsp;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&nbsp;templates provided by Cisco MediaSense.<br>

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

+

+

<br>

+

+

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

+

+

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

Cisco MediaSense, Release 8.5(3)

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.

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

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.

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.