Table Of Contents
Installing Cisco Unified Communications Manager Release 8.0(2)
Install Software from a DVD on the First Node
Install Software from a DVD on a Subsequent Node
Apply a Patch During Installation of the First Node
Apply a Patch During Installation of a Subsequent Node
Add a New Node to an Existing Cluster
Reusing the MCS-7828 After Installing Cisco Unified Communications Manager Business Edition
Parallel Installations of Cluster Nodes
Frequently Asked Questions About the Installation
What User Names and Passwords Do I Need to Specify?
Which Servers Does Cisco Support for this Installation?
May I Install Other Software on the Server?
Gathering Information for an Installation
New Cisco Unified Communications Manager Servers and Devices
Using the Cisco Unified Communications Answer File Generator
Handling Network Errors During Installation
Installing the New Operating System and Application
Navigating Within the Installation Wizard
Entering Preexisting Configuration Information
Upgrading from a Remote Server
Performing the Basic Installation
Changing the Default Application User Passwords
Accessing Cisco Unified Serviceability
Applying Security to a New Node in a Secure Cluster
Migrating To Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers
Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers External Media
Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers Licensing
Customer Impact from New Licensing Procedures
Supported Virtual Machine Configurations and Licensing
Installing Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server
Configuration Checklist for Installing and Configuring the Server
Aligning the Datastore Used for VMs
Downloading Virtual Machine Templates (OVA Templates)
Installing Cisco Unified Communications Manager On a VM
Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server Licensing
Customer Impact from New Licensing Procedures
Supported Virtual Machine Configurations and Licensing
Migrating To Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server
Monitoring Hardware from the VM
Monitoring from vSphere Client and vCenter
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco Product Security Overview
Installing Cisco Unified Communications Manager Release 8.0(2)
Revised: 8/20/2010This document includes information about installing Cisco Unified Communications Manager release 8.0(2). Review all installation instructions carefully before you install Cisco Unified Communications Manager.
This document includes information about installing Cisco Unified Communications Manager Release 8.0(2) on one server or many servers in a cluster environment.
For information about upgrading from a previous release of Cisco Unified Communications Manager, and for other installation and upgrade information, see the "Related Documentation" section.
Contents
This document contains the following topics:
–
Install Software from a DVD on the First Node
–
–
–
–
•
–
–
–
•
•
•
•
–
–
–
–
–
–
–
•
Related Documentation
For additional installation and upgrade information, refer to the following documents:
•
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guides_list.html
This document describes how upgrade Cisco Unified Communications Manager from a Windows-based release (4.x and older) to an appliance-based release.
•
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
This document describes how to upgrade Cisco Unified Communications Manager to a later appliance-based release.
•
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guides_list.html
This document describes how to replace a Cisco Unified Communications Manager server or a cluster of servers.
•
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
This document describes the Command Line Interface for Cisco Unified Communications Manager. Some of these commands perform upgrade and installation-related tasks.
For further information about Cisco Unified Communications Manager documentation, refer to the following URL:
http://cisco.com/en/US/products/sw/voicesw/ps556/products_documentation_roadmaps_list.html.
Table 1 lists URLs for software and additional documentation.
Table 1 Quick Reference for URLs
Cisco MCS data sheets
http://www.cisco.com/en/US/products/hw/voiceapp/ps378/index.html
Cisco Unified Communications Manager service releases
Installation Scenarios
You can use this document to perform the following different installation scenarios:
•
•
•
•
•
•
The following sections provide an overview of the high-level tasks that you must perform for each of these installation scenarios. Each high-level task also includes a link to another section of the document, which you can follow for detailed information about the task.
Note
Install Software from a DVD on the First Node
To install software that you have on a DVD on the first node in a cluster, follow the steps in Table 1.
Table 2 Installing Software from a DVD on the First Node
Step 1
Perform all pre-installation tasks that apply to your site.
For a list of pre-installation tasks, see Table 1.
Step 2
Follow the procedure to begin installing the software from the DVD to your server.
See the "Starting the Installation" section.
Step 3
Follow the procedure for performing a basic installation.
Step 4
When the First Node Configuration window displays, choose Yes to configure the new server as the first node.
See Step 10 in the "Performing the Basic Installation" section.
Step 5
Follow the procedure to configure the first node.
Step 6
Perform all post-installation tasks that apply to your site.
For a list of post-installation tasks, see Table 13.
Install Software from a DVD on a Subsequent Node
To install software that you have on a DVD, follow the steps in Table 1.
Table 3 Installing Software from a DVD on a Subsequent Node
Step 1
Perform all pre-installation tasks that apply to your site.
For a list of pre-installation tasks, see Table 1.
Step 2
Follow the procedure to begin installing the software from the DVD to your server.
Step 3
Follow the procedure for performing a basic installation.
Step 4
When the First Node Configuration displays, choose No to configure the new server as a subsequent node.
See Step 10 in the "Performing the Basic Installation" section.
Step 5
Follow the procedure to configure a subsequent node in the cluster.
Step 6
Perform all post-installation tasks that apply to your site.
For a list of post-installation tasks, see Table 13.
Apply a Patch During Installation of the First Node
You can upgrade to a later release by downloading and applying a patch during installation. To apply a patch during installation of the first node, follow the steps in Table 1.
Table 4 Applying a Patch During Installation of the First Node
Step 1
Perform all pre-installation tasks that apply to your site.
For a list of pre-installation tasks, see Table 1.
Step 2
Follow the procedure to begin installing the software from the DVD to your server.
Step 3
Follow the procedure to apply a software patch.
Step 4
Follow the procedure for performing a basic installation.
Step 5
When the First Node Configuration window displays, choose Yes to configure the new server as the first node.
See Step 10 in the "Performing the Basic Installation" section.
Step 6
Follow the procedure to configure the first node in the cluster.
See the "Configuring the First Node" section.
Step 7
Perform all post-installation tasks that apply to your site.
For a list of post-installation tasks, see Table 13.
Apply a Patch During Installation of a Subsequent Node
You can upgrade to a later release by downloading and applying a patch during installation. To apply a patch during installation of a subsequent node, follow the steps in Table 1.
Table 5 Applying a Patch During Installation of a Subsequent Node
Step 1
Perform all pre-installation tasks that apply to your site.
For a list of pre-installation tasks, see Table 1.
Step 2
Follow the procedure to begin installing the software from the DVD to your server.
Step 3
Follow the procedure to apply a software patch.
Step 4
Follow the procedure for performing a basic installation.
Step 5
When the First Node Configuration window displays, choose No to configure the new server as a subsequent node.
See Step 10 in the "Performing the Basic Installation" section.
Step 6
Follow the procedure to configure a subsequent node in the cluster.
Step 7
Perform all post-installation tasks that apply to your site.
For a list of post-installation tasks, see Table 13.
Add a New Node to an Existing Cluster
To add a new node to an existing cluster, follow the steps in Table 1.
Table 6 Adding a New Node to an Existing Cluster
Step 1
Before you make any changes to your existing cluster, be sure that you have a current backup file.
For more information, refer to the Disaster Recovery System Administration Guide.
Step 2
Perform all pre-installation tasks that apply to your site.
For a list of pre-installation tasks, see Table 1.
Step 3
Ensure that you have the appropriate number of licenses to support adding a new node.
For more information on specifying the required number of licenses, refer to the License Unit Calculator chapter in the Cisco Unified Communications Manager Administration Guide.
Step 4
Before you install the new node, ensure that you have configured it on the first node.
From Cisco Unified Communications Manager Administration on the first node, choose System > Server and configure the IP address for the subsequent nodes. For more information, see the Cisco Unified Communications Manager Administration Guide.
Step 5
Record the configuration settings for each server that you plan to install.
To record your configuration settings, see Table 10.
Step 6
You must install the same software version on all nodes in the cluster. If you do not have the correct version on DVD, you need to either download updated software from Cisco.com or follow the procedure for applying a patch during the installation procedure.
For more information on the different installation options, see the "Installation Overview" section.
Step 7
Follow the procedure to begin installing the software from the DVD to your server.
Step 8
If you need to upgrade the version of Cisco Unified Communications Manager that you have on DVD, continue with the procedure for applying a software patch.
See the "Applying a Patch" section.
Step 9
Follow the procedure for performing the basic installation.
Step 10
When the First Node Configuration displays, choose No to configure the new server as a subsequent node.
See Step 10 in the "Performing the Basic Installation" section.
Step 11
Follow the procedure for configuring a subsequent node.
Step 12
Perform all post-installation tasks that apply to your site.
See Table 13.
Step 13
If your cluster is running in mixed mode, ensure that you have your USB key and the latest CTL Client installed on the PC that you use to communicate with the first node. After you finish installing the new node, you will need to update the CTL file on all nodes.
For more information, see "Applying Security to a New Node in a Secure Cluster" section.
Reusing the MCS-7828 After Installing Cisco Unified Communications Manager Business Edition
If you have installed Cisco Unified Communications Manager Business Edition on an MCS-7828 server, and you decide that you need to migrate to separate Cisco Unified Communications Manager and Cisco Unity Connection environments for increased scalability and capacity, you can reuse that MCS-7828 server to run Cisco Unified Communications Manager in a MCS-7825 cluster. Although you can reuse the server, you must reenter your data on the server manually. You must also obtain another server to run Cisco Unity Connection.
Note
To migrate from Cisco Unified Communications Manager Business Edition to separate Cisco Unified Communications Manager and Cisco Unity Connection environments, follow the steps in Table 7:
Table 7 Reusing the MCS-7828 After Installing Cisco Unified Communications Manager Business Edition
Step 1
Order a single migration SKU (CUCM-BE-MIG). The migration SKU ships with software install media that is required to install Cisco Unified Communications Manager and Cisco Unity Connection. The SKU provides a node license for the Cisco Unified Communications Manager and enables you to migrate the DLUs to Cisco Unified Communications Manager.
For ordering information, refer to the Cisco Unified Communications Solutions Ordering Guide. To access the guide, go to www.cisco.com/go/unified-techinfo, choose the appropriate solution release version, choose the Resource Library tab, choose the Ordering Guides link, and choose Ordering Guide Cisco Unified Communications Management Solutions.
Step 2
Rehost all device licenses in the Cisco Unified Communications Manager environment by sending a request to licensing@cisco.com. You must include the MAC address and proof of purchase of your devices.
Step 3
Obtain a new server for Cisco Unity Connection.
Step 4
Rehost all voice-messaging and advanced user licenses by sending an email to licensing@cisco.com. You must include the MAC address and proof of purchase of the server on which you plan to install Cisco Unity Connection.
Step 5
Install Cisco Unified Communications Manager on the MCS-7828 server.
Make sure to read this document and the related release notes before beginning the installation.
Step 6
Install Cisco Unity Connection on a new server.
Refer to the Installation Guide for Unity Connection that is located at the following URL: http://www.cisco.com/en/US/products/ps6509/prod_installation_guides_list.html.
Parallel Installations of Cluster Nodes
When you install a cluster, you can begin the installation of the first node and subsequent nodes at the same time. When the installation program prompts you to designate the first node as the first node, stop installing on the subsequent nodes until the installation completes on the first node. Then configure the subsequent node(s) on the first node. You can then continue the installation on the subsequent nodes. For optimal performance, you should choose the Skip option rather than the Proceed option in the installation program.
Pre-Installation Tasks
Table 1 contains a list of pre-installation tasks that you need to perform to ensure that you can successfully install Cisco Unified Communications Manager.
Table 8 Pre-Installation Tasks
Step 1
Read this entire document to familiarize yourself with the installation procedure.
Step 2
Verify the integrity of any new server hardware (such as hard drives and memory) by running any manufacturer-provided utilities.
Step 3
Ensure that your servers are listed as supported hardware and sized appropriately to support the load of the cluster.
For information about the capacity of server models, refer to the documentation at the following URL:
http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html
Make sure to account for any growth that has occurred since initial system configuration.
Step 4
If you are installing a cluster or adding a node, verify that the links between servers meet the 80-ms round-trip time (RTT) requirement and that you have enough bandwidth to support database replication.
For more information on the 80-ms RTT requirement, refer to the Cisco Unified Communications Solution Reference Network Design (SRND) Based on Cisco Unified Communications Manager, which you can find at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guides_list.htmlStep 5
If you are getting the system time from an NTP server, verify that the first node can synchronize with the NTP server before you install a subsequent node.
To verify the NTP status of the first node, log into the Command Line Interface on the first node and enter the following command:
utils ntp status
Note
For more information, see the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions.
Caution
Step 6
If your firewall is not in the routing path, disable the firewall between nodes, if possible. Also, increase the firewall timeout settings until after you complete the installation.
To temporarily allow network traffic in and out of the nodes (for example, setting the firewall rule for these nodes to
IP any/any) does not always suffice. The firewall might still close necessary network sessions between nodes due to timeouts.Step 7
Do not run Network Address Translation (NAT) or Port Address Translation (PAT) between Cisco Unified Communications Manager nodes.
Step 8
Record the network interface card (NIC) speed and duplex settings of the switch port to which you will connect the new server.
You should configure the same NIC settings on the server and on the switch port. For GigE (1000/FULL), you should set NIC and switch port settings to Auto/Auto; do not set hard values.
Enable PortFast on all switch ports that are connected to Cisco servers. With Portfast enabled, the switch immediately brings a port from the blocking state into the forwarding state by eliminating the forwarding delay [the amount of time that a port waits before changing from its Spanning-Tree Protocol (STP) learning and listening states to the forwarding state].
Step 9
If you use DNS, verify that all servers on which you plan to install Cisco Unified Communications Manager are properly registered in DNS.
For more information, see the "Verifying DNS Registration" section.
Step 10
Obtain a Cisco Unified Communications Manager license file.
See "Obtaining a License File" section.
Note
Step 11
Record the configurations settings for each server that you plan to install.
To record your configuration settings, see Table 10.
Step 12
Configure any subsequent nodes on the first node before you install a subsequent node.
From Cisco Unified Communications Manager Administration on the first node, choose System > Server and configure the IP address for the subsequent nodes. For more information, see the Cisco Unified Communications Manager Administration Guide.
Important Considerations
Before you proceed with the installation, consider the following requirements and recommendations:
•
•
When you install Cisco Unified Communications Manager in a large subnet with a large number devices in that subnet, the Address Resolution Protocol (ARP) table can fill up quickly (maximum 1024 entries, by default). When the ARP table gets full, Cisco Unified Communications Manager can have difficulty talking to endpoints and cannot add more phones.
•
Note
If you want the Cisco Unified Communications Manager node to automatically monitor UPS signaling and automatically initiate a graceful shutdown upon power loss, you should use specific UPS and server models. For more information on supported models and configurations, refer to the Release Notes for Cisco Unified Communications Manager.
•
•
•
•
•
•
•
•
•
•
•
•
Frequently Asked Questions About the Installation
The following section contains information about commonly asked questions and responses. Review this section carefully before you begin the installation.
What User Names and Passwords Do I Need to Specify?
Note
During the installation, you must specify the following user names and passwords:
•
•
•
Administrator Account User Name and Password
You use the Administrator Account user name and password to log in to the following areas:
•
•
•
To specify the Administrator Account user name and password, follow these guidelines:
•
•
You can change the Administrator Account password or add a new Administrator account by using the command line interface. For more information, see the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions.
Application User Name and Password
You use the Application User name and password to access applications that are installed on the system, including the following areas:
•
•
•
•
To specify the Application User name and password, follow these guidelines:
•
•
You can change the Application User name and password by using the command line interface. For more information, see the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions.
Security Password
The system uses this password to authorize communications between nodes, and you must ensure that this password is identical on all nodes in the cluster.
The Security password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.
What is a Strong Password?
The installation wizard checks to ensure that you enter a strong password. To create a strong password, follow these recommendations:
•
•
•
•
Avoid the following types of passwords:
•
•
•
•
•
Which Servers Does Cisco Support for this Installation?
For information about supported server models, refer to the following documentation:
•
•
May I Install Other Software on the Server?
You must do all software installations and upgrades by using Cisco Unified Communications Operating System Administration. The system can upload and process only software that Cisco Systems approved.
You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco Unified Communications Manager with Cisco Unified Communications Manager 8.0(2).
Browser Requirements
You can access Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, Cisco Unified Reporting, Cisco Unified Communications Operating System Administration, and Disaster Recovery System by using the browsers and operating systems listed in Table 9. Cisco does not support or test other browsers.
Verifying DNS Registration
If you use DNS, verify that all servers to be added are registered in DNS properly by performing the following actions:
Procedure
Step 1
Step 2
Step 3
Gathering Information for an Installation
Use Table 10 to record the information about your server. Gather this information for each Cisco Unified Communications Manager server that you are installing in the cluster. You may not need to obtain all the information; gather only the information that is pertinent to your system and network configuration. You should make copies of this table and record your entries for each server in a separate table, even if you are planning to use the DMABackupInfo.inf file to configure your system.
Note
Caution
The last column in the table shows whether you can change a field after installation, and if you can, it provides the appropriate Command Line Interface (CLI) command.
Caution
Table 10 Node Configuration Data
Administrator ID
This field specifies the administrator account user ID that you use for secure shell access to the CLI, for logging into Cisco Unified Communications Operating System Administration and for logging into the Disaster Recovery System.
No, you cannot change the entry after installation.
Note
Your entry:
Administrator Password
This field specifies the password for the Administrator account, which you use for secure shell access to the CLI, for logging into Cisco Unified Communications Operating System Administration and for logging into the Disaster Recovery System.
Ensure the password is at least six characters long; it can contain alphanumeric characters, hyphens, and underscore.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set password admin
Your entry:
Application User Name
You use the Application User name as the default user name for applications that are installed on the system, including Cisco Unified Communications Manager and Cisco Unified Serviceability.
Caution
Yes, you can change the entry after installation by using the following CLI command:
CLI > utils reset_ui_administrator_name
Your entry:
Application User Password
You use the Application User password as the default password for applications that are installed on the system, including Cisco Unified Communications Manager and Cisco Unified Serviceability.
Yes, you can change the entry after installation by using the following CLI command:
CLI > utils reset_ui_administrator_password
Your entry:
Country
From the list, choose the appropriate country for your installation.
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > set web-security
Your entry:
DHCP
If you want to use DHCP to automatically configure the network settings on your server, choose Yes.
If you choose Yes, you do not get prompted for DNS or static configuration settings.
If you choose No, you must enter a hostname, IP Address, IP Mask, and Gateway.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network dhcp
Your entry:
DNS Enable
A DNS server resolves a hostname into an IP address or an IP address into a hostname. If you do not have a DNS server, enter No.
If you have a DNS server, Cisco recommends that you enter Yes to enable DNS.
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network dns
Your entry:
DNS Primary
Enter the IP address of the DNS server that you want to specify as the primary DNS server. Enter the IP address in dotted decimal format as ddd.ddd.ddd.ddd.
Consider this field mandatory if DNS is set to yes (DNS enabled).
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network dns
Your entry:
DNS Secondary (optional)
Enter the IP address of the DNS server that you want to specify as the optional secondary DNS server.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network dns
Your entry:
Domain
This field represents the name of the domain in which this machine is located.
Consider this field mandatory if DNS is set to yes.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network domain
Your entry:
Gateway Address
Enter the IP address of the network gateway.
If you do not have a gateway, you must still set this field to 255.255.255.255. Not having a gateway may limit you to only being able to communicate with devices on your subnet.
If DHCP is set to No, consider this field mandatory.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network gateway
Your entry:
Hostname
Enter a host name that is unique to your server.
The host name can comprise up to 64 characters and can contain alphanumeric characters and hyphens. The first character cannot be a hyphen.
If DHCP is set to No, consider this field mandatory.
Yes, you can change the entry after installation.
For information, refer to the document Changing the IP Address and Host Name for Cisco Unified Communications Manager for your product release at the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
Your entry:
IP Address
Enter the IP address of your server.
If DHCP is set to No, consider this field mandatory.
Yes, you can change the entry after installation.
For information, refer to the Changing the IP Address and Host Name for Cisco Unified Communications Manager 5.x, 6.x, and 7.x Servers document at the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
Your entry:
IP Mask
Enter the IP subnet mask of this machine.
If DHCP is set to No, consider this field mandatory.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network ip eth0
Your entry:
Location
Enter the location of the server.
The system uses this information to generate certificate signing requests (CSRs), which are used to obtain third-party certificates.
You can enter any location that is meaningful within your organization. Examples include the state or the city where the server is located.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set web-security
Your entry:
MTU Size
The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network.
Enter the MTU size in bytes for your network. If you are unsure of the MTU setting for your network, use the default value.
Default: 1500 bytes
The MTU setting must be the same on all nodes in a cluster.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network mtu
Your entry:
NIC Duplex
Choose the duplex mode for the network interface card (NIC), either Full or Half.
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network nic
Your entry:
NIC Speed
Choose the speed for the NIC, either 10 megabits per second or 100 megabits per second.
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network nic
Your entry:
NTP Server
Enter the hostname or IP address of one or more network time protocol (NTP) servers with which you want to synchronize.
You can enter up to five NTP servers.
Note
Note
Yes, you can change the entry after installation by using the Cisco Unified Communications Operating System:
Settings > NTP Servers
Your entry:
Organization
Enter the name of your organization.
TipNote
Yes, you can change the entry after installation by using the following CLI command:
CLI > set web-security
Your entry:
Security Password
Servers in the cluster use the security password to communicate with one another.
The password must contain at least six alphanumeric characters. It can contain hyphens and underscores, but it must start with an alphanumeric character.
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > set password security
Caution
Your entry:
SMTP Location
Enter the hostname or IP address for the SMTP server that is used for outbound e-mail.
The hostname can contain alphanumeric characters, hyphens, or periods, but it must start with an alphanumeric character.
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > set smtp
Your entry:
State
Enter the state where the server is located.
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > set web-security
Your entry:
Time Zone
This field specifies the local time zone and offset from Greenwich Mean Time (GMT).
Choose the time zone that most closely matches the location of your machine.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set timezone
Your entry:
Unit
Enter your unit.
Note
Yes, you can change the entry after installation by using the following CLI command:
CLI > set web-security
Your entry:
Obtaining a License File
Licensing helps manage Cisco Unified Communications Manager licenses and enforces the licenses for Cisco Unified Communications Manager applications and the number of IP phones. This section provides information on obtaining licenses for new Cisco Unified Communications Manager systems and/or phone installations as well as for Cisco Unified Communications Manager nodes that have been upgraded from various releases.
New Cisco Unified Communications Manager Servers and Devices
Use the following procedure to obtain a node license file for new Cisco Unified Communications Manager servers and to obtain device licenses for new devices that require additional device license units.
Each node in your cluster requires one node license unit. Each device type requires a fixed number of licenses units, depending on the type. For example, Cisco Unified IP Phone 7920 require four license units, and Cisco Unified IP Phone 7970 require five units. If you want licenses for four Cisco Unified IP Phones 7920 and four Cisco Unified IP Phones 7970 phones, you require 36 phone license units.
You use the Product Authorization Key (PAK) that came with your product to obtain the necessary permanent licenses, as described in the following procedure.
Procedure
Step 1
Step 2
Step 3
Note
The system sends the license file(s) to you via e-mail by using the E-mail ID that you provided. The format of a license file specifies CCM<timestamp>.lic. If you retain the .lic extension, you can rename the license file. You cannot use the license if you edit the contents of the file in any way.
Note
Step 4
You can use the licenses that are specified in the license file only within the cluster on which the license file is uploaded.
Using the Cisco Unified Communications Answer File Generator
Cisco Unified Communications Answer File Generator, a web application, generates answer files for unattended installations of Cisco Unified Communications Manager. Individual answer files get copied to the root directory of a USB key or a floppy diskette and are used in addition to the Cisco Unified Communications Manager DVD during the installation process.
The web application supports the following features:
•
•
•
The following usage requirements apply:
•
•
You can access the Cisco Unified Communications Answer File Generator at the following URL:
http://www.cisco.com/web/cuc_afg/index.html
The Cisco Unified Communications Answer File Generator supports Internet Explorer version 6.0 or higher and Mozilla version 1.5 or higher.
Note
Handling Network Errors During Installation
During the installation process, the installation program verifies that the server can successfully connect to the network by using the network configuration that you enter. If it cannot connect, a message displays, and you get prompted to select one of the following options:
•
•
Networking gets validated after you complete each networking window, so the message might display multiple times.
•
•
Installation Overview
The installation process allows you to perform a basic installation or upgrade to a newer service release during the installation.
For a more detailed description of the different installation types, see Table 11.
Installing the New Operating System and Application
This section describes how to install the operating system and Cisco Unified Communications Manager application. You install the operating system and application by running one installation program. This document divides the procedure for using this installation program into the following major topics:
•
•
•
•
Navigating Within the Installation Wizard
For instructions on how to navigate within the installation wizard, see Table 12.
Starting the Installation
To start the installation, follow this procedure.
Note
Procedure
Step 1
Note
Step 2
Step 3
The media check checks the integrity of the DVD. If your DVD passed the media check previously, you might choose to skip the media check.
Step 4
a.
b.
Step 5
•
No hard drives have been found. You probably need to manually choose device drivers for install to succeed. Would you like to select drivers now?To continue the installation, choose Yes.
•
•
Note
•
After the hardware checks complete, the Product Deployment Selection window displays.
Step 6
•
•
•
Note
Step 7
Caution
The Platform Installation Wizard window displays.
Step 8
•
•
–
–
–
Step 9
In the Apply Additional Release window, choose one of the options:
•
•
•
Step 10
Entering Preexisting Configuration Information
Start here if you have a server that has the product preinstalled or if you chose Skip in the Platform Installation Wizard window.
Procedure
Step 1
Step 2
Note
The Platform Installation Wizard window displays.
Step 3
Step 4
In the Apply Additional Release window, choose one of the options:
•
•
•
Step 5
Applying a Patch
If you choose Yes in the Apply a Patch window, the installation wizard installs the software version on the DVD first and then restarts the system. You must obtain the appropriate upgrade file from Cisco.com before you can upgrade during installation.
Note
For information about supported upgrades, see the Release Notes for your product release and the Cisco Unified Communications Manager Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html
You can access the upgrade file during the installation process from either a local disk (DVD) or from a remote FTP or SFTP server.
Procedure
Step 1
Step 2
•
•
•
Upgrading from a Local Disk
Before you can upgrade from a local disk, you must download the appropriate patch file from Cisco.com and use it to create an upgrade DVD. You must create an ISO image on the DVD from the upgrade file. Just copying the ISO file to a DVD will not work.
Procedure
Step 1
The Install Upgrade Patch Selection Validation window displays.
Step 2
Step 3
After the system restarts, the Preexisting Configuration Information window displays.
Step 4
The Platform Installation Wizard window displays.
Step 5
If you choose Proceed, the Apply Patch window displays. Continue with Step 6.
If you choose Cancel, the system halts, and you can safely power down the server.
Step 6
Step 7
Step 8
Upgrading from a Remote Server
Before you can upgrade from a remote server, you must download the appropriate patch file from Cisco.com to an FTP or SFTP server that the server can access.
If you are upgrading from release 5.1(3), you must download the appropriate patch file from Cisco.com, create an ISO image DVD from the patch file, then copy the contents of the DVD to a remote FTP or SFTP server that the server can access.
Cisco allows you to use any SFTP server product but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP). CTDP partners, such as GlobalSCAPE, certify their products with specified version of Cisco Unified Communications Manager. For information on which vendors have certified their products with your version of Cisco Unified Communications Manager, refer to http://developer.cisco.com/web/cdc/home. For information on using GlobalSCAPE with supported Cisco Unified Communications versions, refer to http://www.globalscape.com/gsftps/cisco.aspx.Cisco uses the following servers for internal testing. You may use one of the servers, but you must contact the vendor for support:
•
•
•
Note
If you chose to upgrade through an FTP or SFTP connection to a remote server, you must first configure network settings so that the server can connect to the network.
Procedure
Step 1
Step 2
Note
•
The MTU Configuration window displays. Continue with Step 4.
•
Step 3
The MTU Configuration window displays.
Step 4
The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network. If you are unsure of the MTU setting for your network, use the default value.
Caution
•
•
The DHCP Configuration window displays.
Step 5
•
•
Step 6
The DNS Client Configuration window displays.
Step 7
After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays.
Step 8
If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path. For example, if the upgrade file is in the patches directory, you must enter
/patchesIf the upgrade file is located on a Windows server, remember that you are connecting to an FTP or SFTP server, so use the appropriate syntax, including:
•
•
The Install Upgrade Patch Selection window displays.
Step 9
After the system restarts, the Preexisting Configuration Information window displays.
Step 10
The Platform Installation Wizard window displays.
Step 11
If you choose Proceed, the Apply Patch window displays. Continue with Step 12.
If you choose Cancel, the system halts, and you can safely power down the server.
Step 12
Step 13
Step 14
Performing the Basic Installation
Procedure
Step 1
The Auto Negotiation Configuration window displays.
Step 2
•
The MTU Configuration window displays.
Note
•
The NIC Speed and Duplex Configuration window displays.
Step 3
The MTU Configuration window displays.
Step 4
The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network. If you are unsure of the MTU setting for your network, use the default value, which is 1500 bytes.
Caution
•
•
The DHCP Configuration window displays.
Step 5
•
•
Step 6
The DNS Client Configuration window displays.
Step 7
The network restarts by using the new configuration information, and the Administrator Login Configuration window displays.
Step 8
Note
The Certificate Information window displays.
Step 9
The First Node Configuration window displays.
Step 10
•
•
Configuring the First Node
After you finish the basic installation, follow this procedure to configure the server as the first node in the cluster.
Procedure
Step 1
Note
Step 2
•
The system contacts an NTP server and automatically sets the time on the hardware clock.
Note
•
The Database Access Security Configuration window displays.
Step 3
Note
The SMTP Host Configuration window displays.
Step 4
Note
Step 5
Step 6
Step 7
Step 8
The system installs and configures the software. The DVD drive ejects, and the server reboots. Do not reinsert the DVD.
Step 9
Step 10
Configuring a Subsequent Node
To configure a subsequent node in the cluster, follow these steps.
Caution
Procedure
Step 1
Note
Step 2
The Network Connectivity Test Configuration window displays.
Step 3
•
•
The First Node Access Configuration window displays.
Step 4
The system checks for network connectivity.
If you chose to pause the system after the system successfully verifies network connectivity, the Successful Connection to First Node window displays. Choose Continue.
Note
The SMTP Host Configuration window displays.
Step 5
Note
The Platform Configuration Confirmation window displays.
Step 6
Step 7
Step 8
Post-Installation Tasks
After installing Cisco Unified Communications Manager on your server, you must set some configuration parameters and perform other post-installation tasks before you can begin using it. Perform these tasks for the server that you install and complete the tasks before other servers in the cluster are installed.
For post-installation tasks that you must complete after the installation, see Table 13.
Table 13 Post-Installation Tasks
Log in as the Cisco Unified Communications Manager Application User and change the Application User passwords.
See the "Changing the Default Application User Passwords" section.
Install Real Time Monitoring Tool.
You can use Real Time Monitoring Tool to monitor system health, and view and collect logs.
For installation instructions and more information about Real Time Monitoring Tool, see the Cisco Unified Real Time Monitoring Tool Administration Guide.
Configure the netdump utility, if you installed a cluster of servers.
The netdump utility allows you to send data and memory crash dump logs from one server on the network to another.
For instructions for configuring the netdump utility, refer to the Troubleshooting Guide
Upload your Cisco Unified Communications Manager license files to the first node.
See the "Uploading a License File" section.
Activate Cisco Unified Communications Manager feature services that you want to run.
Before you activate feature services, you must perform required preactivation tasks. For service activation requirements, refer to the Cisco Unified Serviceability Administration Guide.
Refer to Cisco Unified Serviceability Administration Guide.
Configure the backup settings.
Remember to back up your Cisco Unified Communications Manager data daily.
Refer to Disaster Recovery System Administration Guide.
The locale English_United_States installs automatically on the server; however, you can add new locales to the server, if required.
Refer to Cisco Unified Communications Operating System Administration Guide.
Install COP enabler files for any custom device types that you want to use that do not ship with Cisco Unified Communications Manager.
If applicable, configure any network management systems in use at your site.
Refer to the Cisco Unified Serviceability Administration Guide.
If you want to set up a secure cluster, you can run your Cisco IP Telephony network in mixed mode.
For more information, see the "Installing the CTL Client" and "Configuring the CTL Client" procedures in the Cisco Unified Communications Manager Security Guide.
Configure the system.
See the"Configuring the Database" section.
For more information, refer to the Cisco Unified Communications Manager System Guide.
Changing the Default Application User Passwords
The installation sets all Application User passwords to the same Application User password that you entered during installation. Cisco recommends that you log in to Cisco Unified Communications Manager Administration and change these passwords. Refer to Cisco Unified Communications Manager Administration Guide for the procedure for changing a password.
Accessing Cisco Unified Serviceability
To access Cisco Unified Communications Manager Administration or Cisco Unified Serviceability, you will need to use a web browser from a PC with network access to the Cisco Unified Communications Manager server.
Even though all services are installed on each server in the cluster, you must manually activate the services that you want to run on each server in the cluster through Cisco Unified Serviceability. For service recommendations and more information, refer to Cisco Unified Serviceability Administration Guide.
Uploading a License File
Use the following procedure to upload a license file to the Cisco Unified Communications Manager server with the matching MAC address that is provided when a license file is requested. For information about obtaining a license file, see the "Obtaining a License File" section. The Cisco Unified Communications Manager server where the license file is loaded takes on the functionality of the license manager.
Note
Procedure
Step 1
The License File Upload window displays.
Step 2
Note
Step 3
The Upload File pop-up window displays.
Step 4
Note
Step 5
After the upload process completes, the Upload Result file displays.
Step 6
In the License File Upload window, the status of the uploaded file displays.
Note
Step 7
Applying Security to a New Node in a Secure Cluster
Use the following procedure to apply security to a new node in a secure cluster after you have successfully added the node. For more information on adding a new node to a cluster, see the "Add a New Node to an Existing Cluster" section.
Note
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Configuring the Database
After installing Cisco Unified Communications Manager, you use Cisco Unified Communications Manager Administration to begin configuring the database. The Cisco Unified Communications Manager database contains information and parameters that relate to the system as a whole, to connected devices, and to individual users. The following list describes a few tasks that you must perform in Cisco Unified Communications Manager Administration or Cisco Unified Serviceability:
1.
2.
3.
4.
5.
6.
7.
8.
9.
For more information about configuring the Cisco Unified Communications Manager database, refer to the Cisco Unified Communications Manager Administration Guide, the Cisco Unified Communications Manager System Guide, or online help in the Cisco Unified Communications Manager application.
Examining Log Files
If you encounter problems with the installation, you may be able to examine the install log files by entering the following commands in Command Line Interface.
To obtain a list of install log files from the command line, enter
CLI>file list install *To view the log file from the command line, enter
CLI>file view install log_filewhere log_file is the log file name.
You can also view logs by using the Real Time Monitoring Tool. For more information on using and installing the Real Time Monitoring Tool, refer to theCisco Unified Real Time Monitoring Tool Administration Guide.
You can get more information about installation events by viewing or downloading the System History log. Refer to the following for more information:
•
•
Installing and Migrating to Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers
The following sections describe how to install and migrate to Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers:
•
•
•
System Requirements
To run Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers, your system must meet the requirements listed in Table 14.
Table 14 System Requirements
Supported Virtual Machine Configuration
vCPU: 2 vCPUs
RAM: 6 GB
vDisk: 2 x 80 GB: SCSI ID 0:0 and 0:1
vNIC: 1 "flexible" adapter
Note
IOPS per virtual machine (VM)
--
VM oversubscription per blade
None
VMware version
ESXi 4.0
Note
VMware - vMotion
No
Note
VMware - Site Recovery Manager
Yes1
VMware - High Availability
Yes
VMware - Snapshot
No
VMware - Consolidated Backup and Data Recovery Manager
No
VMware - Fault Tolerance
No
1 All servers associated with this parameter must be on the same server area network (SAN).
Migrating To Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers
Migrating from a Media Convergence Server (MCS server) to a Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade 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 Cisco Unified Communications Manager.
Table 15 provides an overview of the migration process and references to other pertinent documentation.
Table 15 Migrating to Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers Process Overview
Step 13
Review the document Replacing a Single Server or Cluster for Cisco Unified Communications Manager.
This document describes how to replace server hardware, which is very similar to migrating from an MCS server to a Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers server. You should perform the document's pre-replacement and post-replacement tasks, and review the procedures for installing Cisco Unified Communications Manager and migrating data.
Replacing a Single Server or Cluster for Cisco Unified Communications Manager
Step 14
Upgrade the MCS server to Cisco Unified Communications Manager Release 8.0(2).
Cisco Unified Communications Operating System Administration Guide
Step 15
If the UCS VM will use a different IP address or hostname than the MCS server, change the IP address and hostname of the MCS server to the values that the UCS VM will use.
This is required for DRS backup and restore to work.
Refer to the topic "Changing the Cluster IP Addresses for Publisher Servers That Are Defined by Host Name" in the Changing the IP Address and Host Name for Cisco Unified Communications Manager guide.
Step 16
Perform a DRS backup on the MCS server.
Note
Disaster Recovery System Administration Guide
Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers External Media
Step 17
Use the Answer File Generator to generate a license MAC for the Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers server. The license MAC is required to obtain licenses for the server.
Using the Cisco Unified Communications Answer File Generator
Customer Impact from New Licensing Procedures.
Installing Cisco Unified Communications Manager
Step 18
Create the virtual machines (VMs) on the Cisco UCS B-Series Blade Server that will be used as the replacements for the MCS nodes.
Use the OVA template "2 vCPU" as described in Table 14.
Step 19
Install Cisco Unified Communications Manager Release 8.0(2) on the Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers server.
Note
Installing Cisco Unified Communications Manager
Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers External Media
Step 20
Install Cisco Unified Communications Manager Release 8.0(2) on the Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers server.
Cisco Unified Communications Operating System Administration Guide
Step 21
Perform a DRS restore to restore the data backed up from the MCS server to the Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers server.
Note
Disaster Recovery System Administration Guide
Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers External Media
Step 22
Upload the new licenses to the Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers server.
If you did not obtain licenses for the new server already, you must request the licenses first.
Note
Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers Licensing
Cisco Unified Communications Operating System Administration Guide
Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers External Media
Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers uses "soft media" such as ISO or FLP (virtual floppy) for procedures that require external media (such as installation and upgrade, backup and recovery). Physical external devices such as USB drives are not supported.
Note
The virtual USB interface is not supported on VMware. The following are examples of differences in external media support between MCS servers andCisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers:
•
•
•
•
•
Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers Licensing
The following sections describe licensing for Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers:
•
•
Customer Impact from New Licensing Procedures
Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers uses a different licensing model than Cisco Unified Communications Manager on an MCS server. The MAC address of the NIC card is no longer used to associate the license to the server.
Instead, the license gets associated to a license MAC, which is a 12 digit HEX value created by hashing the following parameters that you configure on the server:
•
•
•
•
•
•
•
•
•
•
The ways to obtain the license MAC are as follows:
•
Note
•
•
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 get prompted to select the type of license that you want to obtain:
•
•
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. Contact the licensing team at licensing@cisco.com.
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, then change them back to the new values that you want to use. You will get another 30- day grace period.
Supported Virtual Machine Configurations and Licensing
The virtual machine configuration for running Cisco Unified Communications Manager on VMware on Cisco UCS B-Series Blade Servers must match the specifications described in the "System Requirements" section 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.
Installing and Migrating to Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server
This following sections describe the changes for installation, upgrade, and migration in Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server:
•
•
•
System Requirements
To run Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server, your system must meet the requirements listed in Table 16.
To operate Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server 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.
Note
Installing Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server
This following sections describe how to perform a fresh installation of a Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server server:
•
•
•
•
Configuration Checklist for Installing and Configuring the Server
Table 16 provides a checklist of the major steps required to install and configure Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server. The Related Documentation column contains references to documentation that is related to the step.
Preparing To Install
This section describes how to prepare to install a Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server server in a standalone configuration, meaning that it is not in a datacenter.
You should allocate the following resources before installation:
•
•
–
–
•
•
•
•
Configuring RAID
If you purchased the UCS C210 server separately from Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server, configure the RAID settings to the following specifications:
•
•
Follow this procedure to perform this task:
Step 1
Step 2
-ldinfo -l0 -a0
-ldinfo -l1 -a0
The required configuration is two drives in a RAID 1 array for logical drive 0, and four drives in a RAID 5 array for Logical drive 1. If the RAID configuration is wrong, continue with this procedure.
Note
Step 3
Caution
Step 4
-cfgldadd -r1 [252:0, 252:1] -a0
-cfgldadd -r5 [252:2, 252:3, 252:4, 252:5] -a0
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 5
-ldinit -start -full -l0 -a0 (l0 is the letter l and the number 0, not the number 10)
-ldinit -start -full -l1 -a0 (l1 is the letter l and the number 1, not the number 11)
This clears data on the drives and initializes the new array.
Step 6
-ldinit -showprog -l0 -a0
-ldinit -showprog -l1 -a0
When both commands report that no initialization is running, it is safe to quit the Preboot CLI.
Step 7
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.
Aligning the Datastore Used for VMs
When you install VMWare ESXi, the second logical volume is automatically imported unaligned. VMs have better disk performance when all partitions (physical, ESXi and VM) start on the same boundary. This prevents disk blocks being fragmented across the different boundaries.
To ensure that the ESXi partition used for VMs will be aligned, you should delete the unaligned datastore (the larger disk partition—407 GB), then recreate the datastore using vSphere client.
Creating Virtual Machines
Cisco provides a VM template for you to download and transfer to your Virtual Host. Use this template to create the VM for Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server installation.
Before you deploy the template and create the VM, you should have a hostname and IP address allocated for the new VM.
Follow these steps to create a VM and prepare to install Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server on it:
Step 1
See the "Downloading Virtual Machine Templates (OVA Templates)" section for more information.
Step 2
It is recommended to use the smaller datastore (with ESXi installed on it) for this.
Step 3
Step 4
•
•
Step 5
At this point a new VM has been created with the correct amount of RAM, number of CPUs, size and number of disks for the intended application.
Step 6
Downloading Virtual Machine Templates (OVA Templates)
The configuration of a Cisco Unified Communications Manager virtual machine must match a supported virtual machine template.
Perform the following procedure to obtain the virtual machine template for Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server:
Procedure
Step 1
http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Installing Cisco Unified Communications Manager On a VM
Follow this procedure to install Cisco Unified Communications Manager on a new VM:
Step 1
Step 2
Step 3
Step 4
The Cisco Unified Communications Manager installation program starts. For information about performing the installation, see the document Installing Cisco Unified Communications Manager.
Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server Licensing
The following sections describe licensing for Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server:
•
•
Customer Impact from New Licensing Procedures
Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server uses a different licensing model than Cisco Unified Communications Manager on an MCS server. The MAC address of the NIC card is no longer used to associate the license to the server.
Instead, the license gets associated to a license MAC, which is a 12 digit HEX value created by hashing the following parameters that you configure on the server:
•
•
•
•
•
•
•
•
•
•
The ways to obtain the license MAC are as follows:
•
Note
•
•
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 get prompted to select the type of license that you want to obtain:
•
•
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. Contact the licensing team at licensing@cisco.com.
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, then change them back to the new values that you want to use. You will get another 30- day grace period.
Supported Virtual Machine Configurations and Licensing
The virtual machine configuration for running Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server must match the specifications described in the "System Requirements" section 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.
Migrating To Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server
Migrating from a Media Convergence Server (MCS server) to a Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server 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 Cisco Unified Communications Manager.
Table 18 provides an overview of the migration process and references to other pertinent documentation.
Table 18 Migrating to Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server Process Overview
Step 12
Review the document Replacing a Single Server or Cluster for Cisco Unified Communications Manager.
This document describes how to replace server hardware, which is very similar to migrating from an MCS server to a Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server server. You should perform the document's pre-replacement and post-replacement tasks, and review the procedures for installing Cisco Unified Communications Manager and migrating data.
Replacing a Single Server or Cluster for Cisco Unified Communications Manager
Step 13
Upgrade the MCS server to Cisco Unified Communications Manager Release 8.0(2).
Cisco Unified Communications Operating System Administration Guide
Step 14
If the UCS VM will use a different IP address or hostname than the MCS server, change the IP address and hostname of the MCS server to the values that the UCS VM will use.
This is required for DRS backup and restore to work.
Refer to the topic "Changing the Cluster IP Addresses for Publisher Servers That Are Defined by Host Name" in the Changing the IP Address and Host Name for Cisco Unified Communications Manager guide.
Step 15
Perform a DRS backup on the MCS server.
Disaster Recovery System Administration Guide
Step 16
Use the Answer File Generator to generate a license MAC for the Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server server. The license MAC is required to obtain licenses for the server.
After you obtain the license MAC, you can rehost the licenses for your new server.
Customer Impact from New Licensing Procedures.
Installing Cisco Unified Communications Manager
Step 17
Create the virtual machine (VM) on the Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server server that will be used as the replacement for the MCS node.
Installing Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server
Step 18
Install Cisco Unified Communications Manager Release 8.0(2) on the Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server server.
Installing Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server
Installing Cisco Unified Communications Manager
Step 19
Perform a DRS restore to restore the data backed up from the MCS server to the Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server server.
Disaster Recovery System Administration Guide
Step 20
Upload the new licenses to the Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server server.
If you did not obtain licenses for the new server already, you must request the licenses first.
Note
Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server Licensing
Cisco Unified Communications Operating System Administration Guide
VMware Support
Consider the following, when using Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server:
•
•
•
•
•
•
•
•
•
•
For more information on the UCS C210 rack-mount server, go to the following URL:
To view the list of product installation and configuration guides for Cisco UCS C-Series Integrated Management Controller, go to the following URL:
http://www.cisco.com/en/US/products/ps10739/products_installation_and_configuration_guides_list.html
To view the list of product installation and configuration guides for Cisco UCS Manager, go to following URL:
http://www.cisco.com/en/US/products/ps10281/products_installation_and_configuration_guides_list.html
Performing Daily Operations on Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server
Daily operations for Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server software applications are identical to when the application is installed on an MCS server.
There are some differences in hardware management and monitoring, because Cisco Unified Communications Manager on the Cisco UCS C210 Rack-Mount Server operates in a virtual environment. The following sections describe how to perform these tasks:
•
•
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:
•
•
•
•
Monitoring from vSphere Client and vCenter
The vSphere Client provides the following monitoring features:
•
•
•
•
Related Documentation
The UCS RAID Controller SMI-S Reference Guide, which describes Storage Management Initiative Specification (SMI-S) support in the Cisco UCS Servers, is available at the following URL:
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html. If you require further assistance please contact us by sending email to export@cisco.com.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1002R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Copyright © 2010 Cisco Systems, Inc. All rights reserved.