Virtualization for Cisco MediaSense

From DocWiki

Revision as of 20:48, 7 June 2011 by Cchetty (Talk | contribs)
Jump to: navigation, search
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
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

See High-level Checklist for Design and Implementation.

VM-Specific Cisco MediaSense Hardware Requirements

See Unified Computing System Hardware.

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

See Unified Communications VMWare Requirements

Cisco UCS C-Series Servers, Cisco MediaSense ISO, and ESXi must be installed prior to the Cisco MediaSense installation.

Cisco MediaSense, Release 8.5(1)

All Cisco MediaSense servers run on VMs using the Unified Communications Operating System (Unified OS or UCOS).
Note Note: If you are using ESXi 4.1, be sure to disable Large Receive Offload (LRO) on the ESXi 4.1 host.

To disable LRO, follow this procedure:

  1. Log into the ESXi host or its vCenter with vSphere Client.
  2. Select the host > Configuration > Advanced Settings.
  3. Select Net and scroll down slightly more than half way.
  4. Set the following parameters from 1 to 0:
    • Net.VmxnetSwLROSL
    • Net.Vmxnet3SwLRO
    • Net.Vmxnet3HwLRO
    • Net.Vmxnet2SwLRO
    • Net.Vmxnet2HwLRO
  5. Reboot the ESXi host to activate these changes.

VM-Specific Cisco MediaSense Software Requirements

See Unified Communications VMWare Requirements.

The following software requirements apply specifically to Cisco MediaSense:

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

VM-Specific Cisco MediaSense Hardware Requirements

See Unified Computing System Hardware.

Cisco MediaSense only supports UCS C210 M1 and M2 servers for Release 8.5(1).

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

  1. Configure a serial port on the VM (refer to the VMware Knowledge Base for more information).
    1. While the VM is powered off, edit the VM settings, and add a serial port to the VM.
      Note Note: You cannot add a serial port while the VM is running.
    2. Attach the serial port to a TMP file. When you attach a TMP file to the serial port during the Linux boot-up stage a few garbage characters (terminal escape sequences) are output to this serial port. These characters corrupt the TAR format of the file when you dump the logs to this file. To create a valid TAR file, you must attach the serial port to a new, empty file just before you dump logs to this file (see Step 2).
    3. Power on the VM and start your installation.
  2. When you are ready to dump the log files, attach a new, empty file to the serial port.
    1. If the system halts due to an installation failure, the system may provide the option of dumping logs at that point. Before you respond to this question, be sure to edit the VM settings first.
    2. You can edit the VM settings by providing the correct file name where the logs can be dumped.
  3. Return to the VM console and proceed to dump the logs to the serial port.
  4. After the file is dumped, open it using 7-zip:
    http://www.7-zip.org/download.html
  5. Once you have successfully dumped the logs to a file, power off the VM, edit the VM settings, and remove the serial port from the VM.
    Caution Caution: Leaving the serial port (or any other unnecessary virtual hardware) can negatively impact performance of the VM. Other than to dump install logs, there is no other use for the serial port in a UCM VM. Consequently, you will not need the serial port again until you do a fresh install.


Back to: Unified Communications in a Virtualized


Rating: 4.5/5 (2 votes cast)

Personal tools