At this point the application is installed and in operation. Daily operations for applications are similar to an installation on a physical server, including:
Application configuration and integration with other applications
RTMT performance monitoring
SNMP monitoring and alarms
DRS backup and restore
Device, trunk, gateway configuration and monitoring
The following sections describe how to perform these tasks.
Monitoring From Virtual Machine
Applications running in a VM have no ability to monitor the physical hardware. Any hardware monitoring must be done from the Cisco Integrated Management Controller, ESXi plugins, vCenter or by physical inspection (for flashing LEDs, and so on).
Monitoring of hardware is the customer's responsibility. It is assumed the customer is familiar with virtualized environments and knows how to manage hardware in these environments.
Monitoring From Cisco Integrated Management Controller
The Cisco Integrated Management Controller (Cisco IMC) 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, Voltage, and Current
A system event log that contains BIOS and Sensor entries
LSI MegaRAID controller information, which includes physical and virtual drive layout and Battery Backup Unit information from the Inventory > Storage tab. This information was usually accessible for earlier UCS servers only by installing the MegaRAID plugin from ESXi.
Monitoring From vSphere Client and vCenter
The vSphere Client provides the following monitoring:
Hardware and system alarms defined under the Alarms tab in the vSphere Client when logged in to vCenter.
VM resource usage under the Virtual Machines tab in the vSphere Client, as well as under the Performance tab for each VM.
Host performance and resource usage under the Performance tab for the host.
Server Health Monitoring From ESXi
You can monitor server health from ESXi by logging into the ESXi console and inspecting system /var/log/messages for telltale entries.
Disk Management for Cisco UCS Rack-Mount Servers
The Cisco UCS C260 M2 Rack-Mount Server comes with 16 hard drives. These drives were configured into two logical volumes and require no further management.
The Cisco UCS C240 M3 Rack-Mount Server TRC1 comes with 16 hard drives. These drives were configured as two 8-drive RAID-5 logical volumes and require no further management.
The Cisco UCS C240 M3 Rack-Mount Server TRC2 comes with 12 hard drives. These drives were configured as two 8-drive RAID-5 logical volumes and require no further management.
The Cisco UCS C220 M3 Rack-Mount Server TRC1 comes with 8 hard drives. These drives were configured as an 8-drive RAID-5 logical volume and require no further management.
The Cisco UCS C220 M3 Rack-Mount Server TRC2 comes with 4 hard drives. These drives were configured as a 4-drive RAID-10 logical volume and require no further management.
The Cisco UCS C220 M3 Rack-Mount Server TRC3 comes with eight hard drives. These drives were configured as an 8-drive RAID-5 logical volume and do not require further management.
Disks are hot-swappable. This does not mean that you will be able to swap drives ad-hoc after a failure. A process exists to swap drives. When a drive fails, you need to follow these steps:
Reboot and enter the Preboot CLI
Mark the defective drive for removal using -PdPrpRmv -physdrv [<encl>:<slot>] -a0
Replace the drive
The RAID array is rebuilt automatically when the replacement disk is inserted.
Although Preboot CLI is recommended, you can also perform this task through the LSI MegaRaid GUI, where you can swap drives out without having to power-cycle the server to get into the preboot CLI. However, this method requires you to procure a separate machine (Windows or Linux) on the same subnet as the ESXi host, installed with the LSI MegaRaid utility.
Automatic Update Statistics
Communications Manager uses Automatic Update Statistics, an intelligent statistics update feature that monitors the changes made in the database tables and updates only tables that need statistic updates. This feature saves considerable bandwidth, especially on VMware deployments of Communications Manager. Automatic Update Statistics is the default indexing method.
For more information about database services, see the Cisco Unified Serviceability Administration Guide.
Cisco supports the New Identity process for use with Cisco Unified Communications Manager. The New Identity process is designed to start with a Communications Manager application that is fully installed and configured with common settings. Often, the initial VM is saved as a VMware template and cloned as new Communications Manager publisher nodes come online.
The New Identity process copies the VMware template and changes a set of primary settings, such as the IP address and hostname, to give a new VM a unique identity in the network.
When prompted for the floppy/USB drive in the Pre-existing Configuration Information window, power down the VM.
Clone or convert the VM into a VM template.
For a new subscriber, deploy the template and mount a virtual floppy drive that contains the configuration file from the AFG tool.
New Identity Caveats
When you run the New Identity process, note the following:
Although you can provide a new OS administrator user ID in the XML file, you cannot change the OS administrator user ID during the New Identity process.
Each cloned VM has the same network configuration as the VMware template. The network must be functional during the New Identity process. If you run the cloned VMs on the same LAN there can be duplicate IP addresses. Ensure that you do not run the VMware template, or multiple VMs from the initial template, at the same time on the same LAN.
The NTP server must be accessible before you can configure it on the Unified CM application. Ensure that the VM has access to the new NTP server.
If DNS is used, DNS servers must be accessible when you run the New Identity process.
For Cisco Unity Connection, you must set the SMTP domain address after you run the New Identity process.
For Cisco Unified Presence, you must set the postinstallation steps that configure the Unified CM system with which Cisco Unified Presence communicates after you run the New Identity process.
Cisco Unified Communications Manager on Virtual Servers in Release 8.x uses a different licensing model than Cisco Unified Communications Manager on non-virtualized servers (including 7800 Series Media Convergence Servers). The MAC address of the physical NIC card is no longer used to associate the license to the server.
The license is associated to a license MAC, which is a 12 digit HEX value created by hashing the following parameters that you configure on the server:
NTP server 1 (or "none")
NIC speed (or "auto")
IP Address (or "dhcp")
IP Mask (or "dhcp")
Gateway Address (or "dhcp")
Primary DNS (or "dhcp")
SMTP server (or "none")
Certificate Information (Organization, Unit, Location, State, Country)
The ways to obtain the license MAC are as follows:
If you use this method, ensure that you enter the identical parameter values in the Answer File Generator and the Cisco Unified Communications Manager installation program, or the license will be invalid.
After installation, navigate to Show > System in Cisco Unified Communications Manager Administration.
After installation, use the CLI command show status.
Obtaining New Licenses
The process to redeem a Product Activation Key (PAK) for licenses at www.cisco.com/go/license is changed for a license MAC. When redeeming a PAK for a license MAC at this URL, you are prompted to select the type of license that you want to obtain:
A physical MAC address—used when Cisco Unified Communications Manager will be installed on an MCS server.
A license MAC address—used when Cisco Unified Communications Manager will be installed on Cisco Unified Communications Manager on Virtualized Servers.
After you make this selection, the generation and installation of the license file follows the same process.
Obtaining Rehosted Licenses When You Change License MAC Parameters
When you change any of the parameters that create the license MAC, the license that you obtained with it becomes invalid. You must request a rehosting of the license to obtain a valid license. The old license continues to work for a 30-day grace period.
To rehost your licenses, you must open a case with the licensing team to obtain a license for your replacement server. Contact the licensing team at firstname.lastname@example.org.
During the grace period, you can change the settings back to the licensed values to make your original license valid again. If you need more than 30 days of grace period, change your settings back to the licensed values, and then change them back to the new values that you want to use. You will get another 30-day grace period.
Virtual Machine Setup and Licensing Support
The virtual machine configuration for running Cisco Unified Communications Manager on Virtualized Servers must match the stated specifications to get support from Cisco.
While Cisco Unified Communications Manager can be installed and licensed in other virtual machine configurations, Cisco does not support these configurations.