Virtualization for Cisco MediaSense
m (1 revision)
Revision as of 22:46, 8 October 2011
Updates to this Page
The following is a list of significant updates to this page:
|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 strucutre 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 UCS C Series hardware.|
|December 2010||Updated OVA template download link.|
Information for Partners about Cisco MediaSense Deployments
VM-Specific Cisco MediaSense Hardware Requirements
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 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 only supports UCS C210 M1 and M2 servers for Release 8.5(1).
- If you are using ESXi 4.1, be sure to 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 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 Solution Reference Network Design for Cisco MediaSense, Release 8.5(3) guide for more information.
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:
- Unified Communications Virtualization Downloads (including OVA/OVF Templates).
- Cisco MediaSense OVA Templates
|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.|
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
|Back to: Unified Communications in a Virtualized Environment|