Note Ensure that you use ESXi, rather than ESX, to run UC Applications on Cisco UCS C200 Rack-Mount Servers. However, the rack server can be part of a VMware vCenter that includes ESX hosts. Refer to [1]VMware Requirements

To operate UC Applications on Cisco UCS C200 Rack-Mount Servers successfully, you should have the experience and skills to manage a host server running VMware ESXi. If you do not have this experience and want to obtain the required information quickly, consider using VMware GO, a Web-based application that facilitates VMware installations. For more information, refer to the VMware GO documentation.

UC Applications on Cisco UCS C200 Rack-Mount Servers External Media

UC Applications on Cisco UCS C200 Rack-Mount Servers uses "soft media" such as ISO or FLP (virtual floppy) for procedures that require external media (such as installation and upgrade). Physical external devices such as USB drives are not supported.

Note:

Backup and restore are not supported on soft media.

The virtual USB interface is not supported on VMware. The following are examples of differences in external media support between MCS servers and UC Applications on Cisco UCS C200 Rack-Mount Servers:

Install logs cannot get dumped to a USB key. These logs get dumped to a file through the serial port of the VM.

The answer file generated by the Answer File Generator (platformConfig.xml) cannot get read from a USB key to perform an unattended installation. Instead, you must put the answer file into a FLP image to be mounted in the floppy drive.

USB tape drive backup is not supported. Use SFTP instead.

Music On Hold through a USB connection is not supported. Use a Cisco 7800 Series Media Convergence Server instead.

Cisco Messaging Interface (CMI) for Message Waiting Indication (MWI) is not supported over the serial port. Use a Cisco 7800 Series Media Convergence Server instead.

Installing UC Applications on Cisco UCS C200 Rack-Mount Servers

This following sections describe how to perform a fresh installation of UC Applications on Cisco UCS C200 Rack-Mount Servers:

Configuration Checklist for Installing and Configuring the Server

Table 7 provides a checklist of the major steps required to install and configure UC Applications on Cisco UCS C200 Rack-Mount Servers. The Related Documentation column contains references to documentation that is related to the step.

Table 7 Configuration Checklist for Installing and Configuring the Server

Step 11 If the hard drives did not have a RAID configuration previously, you are done configuring RAID. If the hard drives had a RAID configuration before, continue with this procedure.

Step 12 Enter the following command to initialize the logical volumes.

-ldinit -start -full -l0 -a0 (l0 is the letter l and the number 0, not the number 10)

This clears data on the drives and initializes the new array. Allow this command to finish running before exiting the Preboot CLI.

Step 13 If you want to do so, you can enter the following command to display the progress of the command you entered in Step 12:

-ldinit -showprog -l0 -a0

When the display command in Step 13 reports that no initialization is running, it is safe to quit the Preboot CLI.

Step 14 After configuring the two logical volumes, you can exit the Preboot CLI by entering q.

Tip If you can't get to the Preboot CLI even after Quiet Boot is disabled (in other words, if you have no Ctrl+Y option and that key sequence isn't working), you can configure RAID 10 by using the WebBios (Ctrl+H). To use the Web Bios, you must have a USB Keyboard and a USB mouse, rather than a PS2 keyboard and mouse. Use 2 drive groups (DGs) with DG0 containing Disks 0,1 and DG1 containing Disks 2,3.

Installing vSphere Client

When the virtual host is available on the network, you can browse to its IP address to bring up a web-based interface. The vSphere Client is Windows-based, so the download and install must be performed from a Windows PC.

Once the vSphere Client is installed, you can run it and log into the virtual host using the virtual host's name or IP address, the root login ID, and the password you configured.

You can join the host to a vCenter if you want to manage it through vCenter.

Creating Virtual Machines

Cisco provides a VM template for you to download and transfer to your virtual host. Use this template to create the VMs for UC Applications on Cisco UCS C200 Rack-Mount Servers installation.

Before you deploy the template and create VMs, you should have a hostname and IP address allocated for each new VM.

Follow these steps to create a VM and prepare to install UC Applications on Cisco UCS C200 Rack-Mount Servers on it:

BIOS boot order: read the Release Notes for the OVA that you are deploying for instructions on how to set the BIOS boot order.

Migrating To UC Applications on Cisco UCS C200 Rack-Mount Servers

Migrating from a Media Convergence Server (MCS server) to a UC Applications on Cisco UCS C200 Rack-Mount Servers server follows a procedure that is very similar to replacing server hardware, which is described in the document Replacing a Single Server or Cluster for UC Applications.

Table 8 provides an overview of the migration process and references to other pertinent documentation.

This document describes how to replace server hardware, which is very similar to migrating from an MCS server to a UC Applications on Cisco UCS C200 Rack-Mount Servers server. You should perform the document's pre-replacement and post-replacement tasks, and review the procedures for installing UC Applications and migrating data.

Daily operations for UC Applications on Cisco UCS C200 Rack-Mount Servers software applications are identical to when the application is installed on an MCS server.

There are some differences in hardware management and monitoring, because UC Applications on Cisco UCS C200 Rack-Mount Servers operates in a virtual environment. For more information, see the "Related Documentation" section.

Monitoring Hardware from the VM

Applications running in a VM have no ability to monitor the physical hardware. Any hardware monitoring must be done from the CIMC, ESXi plugins, vCenter, or by physical inspection (for flashing LEDs, etc.).

Monitoring from CIMC

The CIMC provides the following hardware monitoring:

An overview of CPU, memory and power supply health

An overview of hardware inventory, including CPUs, memory, power supplies and storage

Monitoring of sensors for power supplies, fans, temperature and voltage

A system event log that contains BIOS and sensor entries

Monitoring from vSphere Client and vCenter

The vSphere Client provides the following monitoring features:

When you are logged into vCenter, the vSphere Client displays hardware and system alarms defined on the Alarms tab.

VM resource usage displays on the Virtual Machines tab, and on the Performance tab for each VM.

Host performance and resource usage display on the Performance tab for the Host.

When ESXi is used standalone (without vCenter), hardware status and resource usage are available, but alarming is not possible.