 Feedback
|
Table Of Contents
Installing Cisco Unified CallManager Release 4.2(3)
Locating Related Cisco Unified CallManager Documentation
Frequently Asked Questions About the Cisco Unified CallManager Installation
How long does it take to perform the Cisco Unified CallManager installation?
How does the Cisco Unified CallManager installation work?
Which servers does Cisco support for this installation?
May I install other software besides Cisco Unified CallManager on the server?
May I run a web browser on the server?
May I add Cisco Unified CallManager servers as members of a Windows domain?
May I configure a server in the cluster as a Domain Controller?
What if I encounter problems during the installation?
Performing the Cisco Unified CallManager Release 4.2 Installation
Performing Preinstallation Tasks
Removing the Servers from a Domain and Join a Workgroup
Connecting the Server to the Network
Disabling Third-Party Applications, Antivirus Services, and Security Agents
Gathering Configuration Information
Installing Cisco Unified CallManager on the Publisher Database Server
Installing Cisco Unified CallManager on Subscriber Database Server(s)
Performing Postinstallation Tasks
Activating Cisco Unified CallManager Services
Downloading Service Releases and Hotfixes for Ongoing System Management
About Microsoft Patches and Hotfixes
Install the Cisco Unified CallManager Service Release (when available on cisco.com)
Viewing the Component Versions That Are Installed on the Server
Installing Cisco Security Agent for Cisco Unified CallManager.
Using the Cisco Unified CallManager Music On Hold Disk or Download
Reenabling Third-Party Applications, Antivirus Services, and Security Agents
Adding New Subscriber Servers to the Cluster After the Installation
Replacing the Publisher Database Server After the Installation
Requirement for Installation of Java Virtual Machine
Verifying and Reinitializing Subscriber Connections
Resolving Name Resolution Failures
Disabling the Restrict CD-ROM Access to Locally Logged-On User Only Security Policy
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Installing Cisco Unified CallManager Release 4.2(3)
Product Key for Cisco Unified CallManager: BTOO VQES CCJU IEBI
Note
The Cisco Unified CallManager product key, which you enter during the operating system installation, allows you to install Cisco Unified CallManager on a server that is dedicated solely to that application. If you want to install Cisco Unified CallManager with Cisco IP Contact Center Express Edition, or Cisco Unified CallManager with Cisco IP Interactive Voice Response on the same server, refer to the Cisco Customer Response Solutions (CRS) installation documentation for the product keys.
This document includes information about installing Cisco Unified CallManager for the first time and reinstalling Cisco Unified CallManager, if necessary.
This document applies if you have one server or many servers in a cluster environment.
Contents
This document contains the following topics:
Locating Documents and Information
•
•
–
–
–
–
–
–
–
Installation Tasks and Information
•
•
•
•
Postinstallation Tasks and Information
•
•
•
•
•
Verifying and Re-creating Subscription Connections
•
Installation Error Messages
Documentation Resources and Technical Assistance
•
Use this document in conjunction with the documents that are listed in the "Locating Related Cisco Unified CallManager Documentation" section.
Conventions
Consider the following documentation conventions as you review this installation document:
Blue Text—To quickly navigate to a section or URL, click text that appears in blue.
Note
Caution
Timesaver
(Required)
This convention indicates that you must perform the procedure. Failing to perform the procedure could cause a total system failure or a loss of data and configuration settings.
(Recommended)
This convention indicates that the procedure is strongly recommended, but not required.
Unless otherwise specified, this document uses base server model numbers. For example, references to the MCS-7835 apply to servers including the MCS-7835, the MCS-7835-1000, the MCS-7835-1266, the MCS 7835H-2.4, the MCS-7835I-2.4, MCS-7835H-3.0, MCS-7835I-3.0, the customer-provided DL380, and the customer-provided IBM xSeries 342 and 345.
Locating Related Cisco Unified CallManager Documentation
Cisco strongly recommends that you review the following documents before you perform the Cisco Unified CallManager installation:
•
This document lists and describes the system requirements, new features, changed information, documentation updates, and open caveats for Cisco Unified CallManager. Cisco provides versions of this document that match the version of the installation document.
•
This document, a companion guide to this installation document, provides information and procedures on installing the operating system on Cisco Unified Communications Applications Servers. This document does not provide Cisco IP telephony application installation procedures. Refer to this document before you install Cisco Unified CallManager, Cisco Personal Assistant, Cisco Conference Connection, or one of the products from the Cisco Customer Response Solutions (CRS) platform.
•
The Cisco Unified CallManager Administration Guide provides step-by-step instructions for configuring, maintaining, and administering the Cisco Unified CallManager voice over IP network.
The Cisco Unified CallManager System Guide provides descriptions of the Cisco Unified CallManager system and its components, configuration checklists, and links to associated Cisco Unified CallManager Administration Guide procedures.
•
This document describes how to configure features and services for Cisco Unified CallManager, including Cisco Music On Hold, Cisco Unified CallManager Extension Mobility, and so on.
•
This document provides descriptions of Cisco Unified CallManager serviceability and remote serviceability and step-by-step instructions for configuring alarms, traces, and other reporting.
•
This document provides information on using the Bulk Administration Tool (BAT) to perform bulk add, update, and delete operations on phones, users, gateways, and ports.
•
This document describes how to install the utility, configure the backup settings, back up Cisco Unified CallManager data, and restore the data.
•
This document provides step-by-step instructions on how to configure and troubleshoot authentication and encryption for Cisco Unified CallManager, Cisco Unified IP Phones, SRST references, and Cisco MGCP gateways.
•
To ensure continued functionality with interfacing Cisco IP telephony applications after the Cisco Unified CallManager installation, refer to the Cisco Unified CallManager Compatibility Matrix, which provides workarounds for applications that are integrated with Cisco Unified CallManager.
Affected applications may include Cisco Conference Connection, Cisco SoftPhone, Cisco 186 Analog Telephony Adapter, Cisco Personal Assistant, Cisco Response Solutions (CRS), Telephony Application Programming Interface and Java Telephony Application Programming Interface (TAPI/JTAPI) applications, including Cisco-supported and third-party applications, and Cisco Unified CallManager Telephony Service Provider (TSP).
If you use Cisco Unified CallManager and related Cisco IP telephony applications in a call-center environment, review this document before you begin any installation procedures.
•
This document provides information on the latest operating system, SQL server, and security support updates. Information in this document applies to servers that are running the following Cisco IP telephony applications: Cisco Unified CallManager, Conference Connection, Personal Assistant, Cisco Customer Response Applications/Solutions, and Cisco Emergency Responder.
•
Locate the release notes, installation/upgrade, and configuration guides for the applications that you want to integrate with Cisco Unified CallManager.
Table 1 lists URLs for software, product keys, and other related documentation.
Table 1 Quick Reference for URLs
Cisco MCS data sheets
http://www.cisco.com/en/US/products/hw/voiceapp/ps378/index.html
Software-only servers (IBM, HP, Compaq, Aquarius)
http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html
Cisco Unified Communications Operating System, SQL Server, Security Updates
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm
Operating system installation, Virtual Network Computing (VNC), and Cisco Media Convergence Server (MCS) Network Teaming Driver documentation
http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm
Cisco Unified CallManager Compatibility Matrix
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
Cisco Unified CallManager documentation
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm
Cisco Unified CallManager Security Guide
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/sec_vir/a
e/index.htm
Cisco Unified CallManager backup and restore documentation
http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm
Cisco Unified CallManager service releases
Related Cisco IP telephony application documentation
http://www.cisco.com/univercd/cc/td/doc/product/voice/index.htm
Important Considerations
Before you proceed with the Cisco Unified CallManager installation or upgrade, consider the following requirements and recommendations:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Frequently Asked Questions About the Cisco Unified CallManager Installation
The following section contains information about commonly asked questions and responses. Review this section carefully before you complete the Cisco Unified CallManager installation.
How long does it take to perform the Cisco Unified CallManager installation?
The entire installation process, excluding pre- and post-installation tasks, takes 45 to 90 minutes per server, depending on your server type. Before you install Cisco Unified CallManager, consider the size of your cluster.
How does the Cisco Unified CallManager installation work?
Review the following information before you install Cisco Unified CallManager.
Verifying the User Name, Organization Name, and Product Key
Cisco supplies you with a Cisco product key when you purchase a Cisco IP telephony product. The product key, based on a file encryption system, allows you to install only the components that you have purchased, and it prevents other supplied software from being installed for general use. The product key comprises alphabetical letters only.
During the operating system installation, you entered the Cisco Unified CallManager product key. The product key allows you to install Cisco Unified CallManager on a server that is designated for Cisco Unified CallManager only.
During the operating system installation, you registered the software product by entering a user and organization name.
During the Cisco Unified CallManager installation, verify that the correct User Name, Organization Name, and product key display. See the latest version of the operating system documentation for more information.
Entering Passwords
During the Cisco Unified CallManager installation, you must enter a valid password for the following accounts:
•
If you plan to install Cisco Unified CallManager on the Cisco Media Convergence Server (MCS), you established this password during the operating system installation. If you left the password blank during the operating system installation, or if you enter the wrong password during the Cisco Unified CallManager installation, you cannot install Cisco Unified CallManager on the server.
Tip
Caution
•
•
•
Caution
Installing the Publisher Database or Subscriber Server
When you install Cisco Unified CallManager, you must determine whether the server will be configured as a publishing database server or a subscriber database server. In a Cisco Unified CallManager distributed system, one server maintains the master, or publisher, database, and all other servers in the cluster maintain subscriber databases. Subscriber databases provide copies of the master database. During normal operation, all Cisco Unified CallManagers in the cluster read data from and write data to the publisher database. Periodically, Cisco Unified CallManager automatically updates the subscriber databases as needed.
Cisco requires that you first install the publisher database server, so authentication to the database occurs. This decision designates a permanent selection. If you want to reassign the database server type at a later date, you must reinstall Cisco Unified CallManager on the server and choose a different database server type.
Caution
You must install one server at a time, or the subscriber servers cannot receive copies of the database from the publisher database server.
Cisco Unified CallManager installs the following software packages:
•
•
•
•
•
Installing Cisco Unified CallManager Components and Services
The Cisco Unified CallManager installation automatically installs all services that display in the Service Activation window of Cisco Unified CallManager Serviceability. These services install on every server in the cluster. To review a list of installed services, service definitions, and service considerations, refer to the Cisco Unified CallManager Serviceability Administration Guide and the Cisco Unified CallManager Serviceability System Guide.
The Cisco Unified CallManager installation places services in an inactive state until the installation completes. After the installation completes, you must manually activate the service on each server in which you want the service to run. For information on activating services, refer to the Cisco Unified CallManager Serviceability Administration Guide and the Cisco Unified CallManager Serviceability System Guide.
Which servers does Cisco support for this installation?
Refer to the Cisco Unified CallManager Compatibility Matrix for a list of servers that Cisco Unified CallManager 4.2(3) supports. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
May I install other software besides Cisco Unified CallManager on the server?
Caution
Cisco supports a limited list of applications on the Cisco Media Convergence Server (MCS) or Cisco-approved, customer-provided server. Consider the following information before you install Cisco Unified CallManager:
•
For more information on supported software, click http://www.cisco.com/pcgi-bin/ecoa/Search. In the Solution pane, click IP Telephony. From the Solution Category drop-down list box, choose Operations, Administration, and Maintenance (OAM). Click Search.
•
•
•
•
May I run a web browser on the server?
Cisco strongly recommends that you do not run a web browser on the Cisco MCS or any Cisco-approved, customer-provided server. Running a web browser on the server causes CPU usage to surge.
To access Cisco Unified CallManager Administration, the web-based graphical user interface (GUI) that allows you to perform Cisco Unified CallManager configuration tasks, use a different PC to browse into the Cisco Unified CallManager server that is running Cisco Unified CallManager Administration and log in with administrative privileges.
Tip
May I add Cisco Unified CallManager servers as members of a Windows domain?
Cisco does not recommend adding Cisco Unified CallManager servers as members of a Microsoft Windows domain. However if your system architecture depends on servers joining a Windows domain, then you must disable the Network Time Protocol (NTP) software that is installed by Cisco Unified CallManager when you add the server as a member of a domain and use Microsoft time service. You must disable the NTP service on every server in your cluster.
Note
Note
To disable the Cisco-installed NTP software on a server:
Step 1
Step 2
Step 3
Step 4
Step 5
Caution
When you complete your upgrade and you are adding the server to the Windows domain, you must disable the Cisco-installed NTP services again.
If you are joining the server to a Microsoft Windows 4.0 domain, you must also perform an additional procedure for synchronizing time. Refer to How to Synchronize the Time on a Windows 2000-Based Computer in a Windows NT 4.0 Domain at http://www.microsoft.com.
May I configure a server in the cluster as a Domain Controller?
Cisco strongly recommends that you do not configure any server in the cluster as a Domain Controller. If you configure any server in the cluster as a Domain Controller, you cannot upgrade Cisco Unified CallManager on the server.
May I use Terminal Services, Virtual Network Computing, and Integrated Lights Out to remotely install the application?
Do not use Terminal Services or Integrated Lights Out (ILO) to install Cisco Unified CallManager Release 4.2(3). Cisco installs Terminal Services, so Cisco Technical Assistance Center (TAC) can perform remote administration and troubleshooting tasks. Cisco does not support upgrades through Terminal Services. Cisco supports ILO for remote management and configuration tasks only
Caution
After you upgrade the server, you must enable Terminal Services.
If you want to use Virtual Network Computing (VNC) to remotely install Cisco Unified CallManager, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm to obtain the latest version of the VNC document.
Caution
What if I encounter problems during the installation?
If you encounter problems during the installation, Cisco recommends that you take the following actions:
1.
2.
Be aware that not all error messages that display in the log file are catastrophic. MSI generates error messages in the log file for many reasons; for example, attempts to access a service that is not used by Cisco Unified CallManager.
Performing the Cisco Unified CallManager Release 4.2 Installation
This section contains information about the procedures that are used to complete the Cisco Unified CallManager installation. The section includes the following topics:
•
•
•
Performing Preinstallation Tasks
For preinstallation tasks that you must complete before the installation, see Table 2.
Table 2 Preinstallation Tasks
Step 1
Plan your system configuration.
Determine how many Cisco Unified CallManager servers the cluster will contain, which server will house the publisher database, and where backup tasks will be performed.
Determine whether each server will act as a dedicated or coresident server.
Step 2
This task applies for reinstallation.
Configure the server to the state of the original configuration.
If you have hot-swappable drives, make sure that you inserted the appropriate drives into the server and ensure that the drives are functional. Remove any additional hard drives that are in the server.
Step 3
Make sure that you installed the operating system version 2000.4.2sr10 (or later) on all dedicated and coresident servers.
Use the Cisco Unified Communications Server Operating System OS/BIOS Upgrade Disk that came with the software kit and upgrade the operating system to version 2000.4.2sr10 or later.
Refer to Installing the Operating System on the Cisco Unified Communications Applications Server. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm.
Before you perform the upgrade, be sure to read the operating system readme information that is posted on the operating system cryptographic software page. You can navigate to the site from the Cisco Unified CallManager software page at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.
Step 4
Download and install the latest Cisco Unified Communications Server Operating System service release (2000.4.2sr10 or later).
The operating system service releases post on the voice products operating system cryptographic software page. You can navigate to the site from the Cisco Unified CallManager software page.
For installation instructions, refer to the file-specific readme document, Cisco Unified Communications Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco Unified Communications Applications Server. To obtain the most recent version of these documents, go to http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.
Step 5
Before you install Cisco Unified CallManager, make sure that you removed all servers from a NT or an Active Directory Domain.
See the "Removing the Servers from a Domain and Join a Workgroup" section.
Step 6
Connect the server(s) to the network.
See the "Installing Cisco Unified CallManager on the Publisher Database Server" section.
Step 7
If your server supports the Cisco Media Convergence Server Network Teaming Driver, you can install and configure this driver, if you choose to do so.
Refer to the driver documentation by clicking the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm
Step 8
This step applies if you need to reinstall Cisco Unified CallManager.
You must disable and stop all third-party, Cisco-verified, and Cisco-provided, coresident applications that are installed on your server.
If you have Cisco-verified applications (Cisco Partner Applications) or platform agents that are installed on the server, you must disable and stop the services.
Cisco strongly recommends that you do not install any Cisco-verified applications until you have completed the installation on every server in the cluster.
See "Installing Cisco Unified CallManager on the Publisher Database Server" section.
Caution
Step 9
Close all web browser windows.
If you have an open browser window, Cisco Unified CallManager will reboot the server after the Sun Microsystems JRE package is installed.
Step 10
Locate specific information that you need to install Cisco Unified CallManager.
Planning your System
You can distribute the call-processing load for your system across multiple Cisco Unified CallManagers as a single cluster. A cluster comprises a set of Cisco Unified CallManagers that share the same database.
At a minimum, you should determine how many Cisco Unified CallManager servers the cluster will contain, which server will house the publisher database, and where backup tasks will be performed. Additional planning should include a strategy for distributing the devices (such as phones or gateways) among the Cisco Unified CallManagers in the cluster to achieve the type of distribution that you want.
Determine whether each server will act as a dedicated or coresident server.
In a Cisco Unified CallManager distributed system, one server maintains the master, or publisher, database, and all other servers in the cluster maintain subscriber databases. Subscriber databases provide copies of the master database. During normal operation, all Cisco Unified CallManagers in the cluster read data from and write data to the publisher database. Periodically, Cisco Unified CallManager automatically updates the subscriber copies of the database from the publisher database.
For more information on planning a Cisco Unified CallManager distributed system, refer to the Cisco Unified CallManager System Guide.
If you are installing a dedicated server, locate the Cisco Unified CallManager product key in this document. If you are installing Cisco Unified CallManager on a coresident server, refer to the specific Cisco IP telephony application installation documentation for the coresident product key.
Removing the Servers from a Domain and Join a Workgroup
Perform the following procedure to convert any servers that exist in the NT Domain or Microsoft Active Directory Domain:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Connecting the Server to the Network
Before you begin the installation, make sure that you connect your server to the network.
The servers in Table 3 contain two network interface cards (NIC), but the Cisco IP telephony application supports only one NIC. When you connect the server to the network, use the NIC connector that is listed in the table because the other NIC is automatically disabled during the installation.
Note
Table 3 Connecting to the Network
MCS-7825
Use the lower NIC connector.
MCS-7835 and MCS-7845
Use the NIC 1 connector.
IBM xSeries 330 server
Use the upper NIC connector.
Disabling Third-Party Applications, Antivirus Services, and Security Agents
The following applications/platform agents may interfere with the Cisco Unified CallManager installation:
•
•
•
•
•
•
•
•
About Disabling McAfee Antivirus Services
Before you perform Cisco Unified CallManager installation procedures, you must disable and stop all Cisco-approved McAfee antivirus services. You can enable and start all antivirus services after you complete the procedures.
About Disabling Security Agents
Before you perform Cisco Unified CallManager installation procedures, you must disable and stop all security agents, including Cisco Security Agent for Cisco Unified CallManager. You can enable and start the services after the installation.
For Cisco-Verified, Third-Party Applications
To review a list of Cisco-verified applications that you should disable and stop before the installation, click the following URL: http://www.cisco.com/pcgi-bin/ecoa/Search. In the Solution pane, click IP Telephony. From the Solution Category drop-down list box, choose Operations, Administration, and Maintenance (OAM). Click Search.
Use the following procedure to disable third-party applications, antivirus services, or security agents:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Gathering Configuration Information
Table 4 shows the information that is required for installing Cisco Unified CallManager on your server. Complete all fields unless otherwise noted. Gather this information for each Cisco Unified CallManager server that you are installing in the cluster. Make copies of this table and record your entries for each server in a separate table.
Note
Installing Cisco Unified CallManager on the Publisher Database Server
Items Needed: Cisco Unified CallManager Installation, Upgrade, and Recovery Disks 1 and 2
For the publisher database server, the installation takes 45 to 90 minutes, depending on the server type. Use the following procedure to perform the installation.
Note
Caution
Procedure
Step 1
Note
Step 2
Step 3
Step 4
Step 5
Step 6
Cisco automatically populates the product (CD) key fields with the product key that you entered during the operating system installation. Click Next.
Step 7
Cisco requires that you install Cisco Unified CallManager on the publisher database server first, so authentication can occur between the publisher database and subscriber servers.
Note
Caution
Step 8
a.
b.
The private password phrase contains 1 to 15 characters. This phrase may contain English lower-case letters, English upper-case letters, Westernized Arabic numerals, and the following nonalphanumeric special characters: { } . < > : ? / | \ ` ~ ! @ $ ^ & * ( ) _ - +.
c.
Step 9
a.
b.
Step 10
Step 11
Step 12
The installation starts. The Cisco Unified CallManager installation takes about 30 to 45 minutes, depending on your server type.
Note
Step 13
The installation program continues to install files on your server. Continue to wait while the installation completes.
Note
Step 14
Step 15
The restart server dialog box displays.
Step 16
Note
Step 17
Step 18
Step 19
Installing Cisco Unified CallManager on Subscriber Database Server(s)
Note
Note
Items Needed: Cisco Unified CallManager Installation, Upgrade, and Recovery Disks 1 and 2
After you install Cisco Unified CallManager on the publisher database server, you install the application on the subscriber database servers. For each subscriber database server, the installation takes 45 to 90 minutes, depending on the server type.
Caution
Caution
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Cisco automatically populates the product key fields with the product key that you entered during the operating system installation. Click Next.
Note
Step 7
a.
b.
Caution
c.
Caution
Step 8
a.
b.
c.
Step 9
a.
b.
Step 10
Step 11
Step 12
The installation starts. The Cisco Unified CallManager installation takes about 30 to 45 minutes, depending on your server type.
Note
Step 13
The installation program continues to install files on your server. Continue to wait while the installation completes.
Note
Step 14
Step 15
Step 16
Step 17
Step 18
Step 19
Performing Postinstallation Tasks
After installing Cisco Unified CallManager on your server, you must set some configuration parameters for Cisco Unified CallManager and perform other post-installation tasks before you can begin using it. Perform these tasks for each server that you install and complete them before or after the other servers in the cluster are installed.
For post-installation tasks that you must complete after the installation, see Table 5.
Table 5 Post-Installation Tasks
Activate Cisco CallManager services that you want to run on each server in the cluster.
Caution
Refer to the following documents:
•
•
See the "Activating Cisco Unified CallManager Services" section.
Configure DNS.
See the "Configuring DNS" section.
Configure the database.
See the "Configuring the Database" section.
To manage your system, install Cisco Unified CallManager Backup and Restore Utility Version 4.0(9) and configure the backup settings.
Remember to back up your Cisco Unified CallManager data daily.
Refer to Cisco Unified CallManager Backup and Restore Utility Administration Guide. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm.
To manage your system, install the latest service release and hotfixes that are available on CCO.
View the components that are installed on the server.
See the following sections:
•
•
If you want to do so, you can configure the F: drive on the higher end servers with four hard drives (such as the MCS-7845) for trace file collection.
See the Cisco Unified CallManager Serviceability Administration Guide.
Install additional music on hold selections via disk or the web.
See the "Viewing the Component Versions That Are Installed on the Server" section.
If you want to do so, install and configure Cisco Customer Response Solutions (CRS) on the server.
Refer to the compatible CRS installation documentation.
The locale, English_United_States, installs automatically on the server. To upgrade existing locales or to add new locales to the server, install the Cisco Unified CallManager Locale Installer.
Click the following URL to obtain the locale and the installer documentation:
http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-locale-40
Cisco strongly recommends that you install one of the following security agents to protect your servers against unauthorized intrusion:
•
•
Click the following URL to obtain the security agent documentation:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/sec_vir/index.htm
If you want to use Norton AntiVirus, install the application and perform post-installation tasks.
Refer to Using Symantec/Norton AntiVirus with Cisco Unified CallManager.
If you disabled any third-party application, antivirus services, or security agents prior to installing Cisco Unified CallManager, you must reenable it.
See the "Reenabling Third-Party Applications, Antivirus Services, and Security Agents" section.
If necessary, you can add a subscriber server to the cluster after the installation.
See the "Adding New Subscriber Servers to the Cluster After the Installation" section.
You cannot add a subscriber server to a cluster by installing a previous version of Cisco Unified CallManager and then upgrading the subscriber server to the same version that is running on the publisher server. If you are adding a new subscriber server or replacing a subscriber server on the cluster, you must use the installation CDs with the same Cisco Unified CallManager version that is running on the publisher server.
If you are adding a new server to a secure cluster, refer to the Cisco Unified CallManager Security Guide.
If necessary, you can replace the publisher database server.
See the "Replacing the Publisher Database Server After the Installation" section.
If you are administering Cisco Unified CallManager servers from a PC that does not have Microsoft Java Machine, you will need to install and configure Sun Microsystems Java Virtual Machine (JVM) on the PC to ensure that Cisco Unified CallManager Administration displays correctly.
MSJVM installs by default in all client workstation versions of the current Windows operating systems, except for the following versions:
•
•
See the "Requirement for Installation of Java Virtual Machine" section.
Activating Cisco Unified CallManager Services
Even though all Cisco CallManager services install on each server in the cluster, you must manually activate the services that you want to run on each server in the cluster. To do this, access Cisco Unified CallManager Serviceability by following this procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Caution
You must activate Cisco CallManager services through Cisco Unified CallManager Serviceability. For service recommendations and more information, refer to Cisco Unified CallManager Serviceability Administration Guide and Cisco Unified CallManager Serviceability System Guide.
Configuring DNS
Cisco strongly recommends that you configure DNS on every server in the cluster where Cisco Unified CallManager is installed. Cisco uses DNS to resolve the server name to an IP address, so servers can interact in the cluster.
Caution
The DNS suffix for the connection field must contain the DNS domain information where the server exists as a member.
When multiple DNS domains exist in a single Cisco Unified CallManager cluster or the Backup Network Directory Location exists in a different DNS domain, you must correctly enter the domain information in the Append these DNS suffixes (in order): field. If you need more information on domain naming conventions, refer to Installing the Operating System on the Cisco Unified Communications Applications Server. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm.
To configure DNS after installing Cisco Unified CallManager, perform the following steps:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Configuring the Database
After installing Cisco Unified CallManager, you use Cisco Unified CallManager Administration to begin configuring the database. The Cisco Unified CallManager database contains information and parameters that relate to the system as a whole, to connected devices, and to individual users. The following list describes tasks that you must perform in Cisco Unified CallManager Administration or Cisco Unified CallManager Serviceability:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
For more information about configuring the Cisco Unified CallManager database, refer to the Cisco Unified CallManager Administration Guide, the Cisco Unified CallManager System Guide, or online help in the Cisco Unified CallManager application.
Downloading Service Releases and Hotfixes for Ongoing System Management
For ongoing management, perform the following tasks:
•
•
About Microsoft Patches and Hotfixes
Refer to Installing the Operating System on the Cisco Unified Communications Applications Server for more information. To obtain this document, see Table 1.
Install the Cisco Unified CallManager Service Release (when available on cisco.com)
After you install this version of Cisco Unified CallManager on all servers in the cluster, Cisco strongly recommends that you install the latest Cisco Unified CallManager service release on all servers in the cluster. These service releases provide additional bug fixes for your system.
Be aware that Cisco Unified CallManager service releases are cumulative. Cisco rolls bug fixes into the next Cisco Unified CallManager release.
Tip
To obtain the latest Cisco Unified CallManager service release, perform the following procedure:
Procedure
Step 1
Step 2
The Cisco Unified CallManager 4.2 software window displays.
Step 3
The readme file provides procedures, caveats, and descriptive information for installing the files.
Step 4
Step 5
Viewing the Component Versions That Are Installed on the Server
The mcsver.exe program reports the current version of all installation components, including the operating system. Be aware that Cisco does not report the actual Cisco Unified CallManager version through this program. Most of these components, which run from the installation disks during the initial installation, no longer exist on the system.
The version for OS Image equals your operating system disk version number. The version of OS Image will change only if you do a new installation by using the Cisco Unified Communications Server Operating System Hardware Detection Disk.
Choose Start > Cisco OS Version to view the operating system image version that you have installed on your server
Installing Cisco Security Agent for Cisco Unified CallManager.
Cisco offers two security agent options. Both agents control system operations by using policies that allow or deny specific system actions before system resources are accessed.
Cisco Security Agent (CSA) for Cisco Unified CallManager
CSA for Cisco Unified CallManager provides a standalone agent and security policy that is designed to be used on all servers in the voice cluster. You cannot update or view the policy that is included with this agent, which is configured specifically for Cisco Unified CallManager and Customer Response Applications (CRA). You can download the agent from CCO at http://www.cisco.com/cgi-bin/tablebuild.pl/cmva-3des.
Management Center for Cisco Security Agent (CSA MC)
If you want to add, change, delete, or view rules and policies that CSA for Cisco Unified CallManager includes, or if you want to add support for non-Cisco approved, third-party applications, you must purchase and install the fully managed console, CSA MC. CSA MC requires a separate, dedicated server to be used as the management center. This management center allows you to create agent kits that are then distributed to agents that are installed on other network systems and servers.
Using the Cisco Unified CallManager Music On Hold Disk or Download
When you install Cisco Unified CallManager on your server, a default music on hold sample automatically installs for customer use. To increase your music on hold selection, you may also install the Cisco Unified CallManager Music On Hold Disk that ships with your Cisco Unified Communications Applications Server, or you may download one of the two following files via the web:
•
•
For information on the MOH feature, refer to the latest version of the Cisco Unified CallManager Features and Services Guide.
As a Cisco Unified CallManager user, you can use any contents of the disk/files with music on hold. Because of licensing restrictions, you must not distribute the Cisco Unified CallManager Music on Hold disk/files to anyone else, and you must not use it for any other purpose.
Reenabling Third-Party Applications, Antivirus Services, and Security Agents
Use the following procedure to reenable third-party applications, antivirus services, or security agents:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding New Subscriber Servers to the Cluster After the Installation
If you need to add servers to the cluster, perform the following tasks:
Caution
1.
2.
3.
Make sure that you enter the publisher database server name correctly, so authentication to the publisher database server can occur.
4.
5.
6.
Replacing the Publisher Database Server After the Installation
To replace an existing or failed server, perform the following steps:
1.
2.
3.
4.
5.
To restore the data, you must store backup data on tape or on a network directory, not on the local directory of the existing or failed server.
6.
7.
8.
Requirement for Installation of Java Virtual Machine
The Microsoft Java Virtual Machine (MSJVM) technology allows Java applications to run on Microsoft Windows-based computers. Some versions of Microsoft Internet Explorer (a component of the Windows operating systems) included MSJVM, but Microsoft discontinued distribution of MSJVM in its software and announced end of life support for the product.
MSJVM installed by default in all client workstation versions of the current Windows operating systems, except for the following version:
•
•
Note
If your client machine runs MSJVM, you can continue to use the existing configuration to browse into the Cisco Unified CallManager Administration windows and perform administration tasks.
If you do not have MSJVM installed on your client machine (or if you receive a message that states that Cisco Unified CallManager cannot detect JVM on the client machine) and you need to perform Cisco Unified CallManager Administration tasks, you must install and configure the Sun Microsystems Java Virtual Machine (JVM) on the client machine. (The Sun JVM is part of the Java 2 Runtime Environment—JRE.) In addition, you must configure the browser security to be Java-enabled. See the "JRE Installation" section for information about installing JRE on the client machine.
If you are not sure whether MSJVM is installed on the client machine, you can install the Sun J2RE anyway. You would then have two Java Runtime Environments installed and running on your machine.
Tip
JRE Installation
As part of the Cisco Unified CallManager installation, the system provides the Sun JRE client software in a zip file that is installed on the Cisco Unified CallManager server.
Note
To install the JRE software for the client PC, follow these steps:
Procedure
Step 1
The following example shows a zip file name:
J2RE_Client_1.4.2_08.zip
Note
Step 2
Step 3
Step 4
The following example shows an installation executable file name:
j2re-1_4_2_04-windows-i586-p.exe
Note
The JRE software installs in the C:\Program Files\Cisco\Java\JRE\j2re1.4.2_08 directory.
Verifying and Reinitializing Subscriber Connections
If the connections between the publisher database server and the subscriber servers within a cluster are broken for any reason, you cannot copy the database to the subscriber servers.
Verifying the Status of the Subscription
To determine whether the connections between the publisher database server and the subscriber servers within a cluster are broken, wait 35 minutes after you have installed the last subscriber server in the cluster. Then, open SQL Server Enterprise Manager. If a red X icon appears next to the subscription, it indicates that the subscription is broken.
Reinitializing the Subscription/Starting the Replication Snapshot Agent
If you determine that one or more subscription connections are broken, as indicated by the red X icon next to the subscriptions, reinitialize the subscriptions and start the replication snapshot agent on the publisher database server.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
In rare cases, the reinitialization of the subscriptions may not work. If you determine that the previous procedure did not work as expected, contact the team that provides technical assistance for this product; for example, your Cisco Partner or the Cisco Technical Assistance Center (TAC).
Analyzing Error Messages
This section includes information about resolving error messages and other failures. The section includes the following topics:
•
Installation Messages
The following messages may display in dialog boxes (not the log file) during the installation. You can obtain and review the log file, ccminst <data/time stamp>.log, from C:\Program Files\Common Files\Cisco\Logs.
Table 6 Installation Messages
During the installation process, you may be prompted, possibly multiple times, to reboot the server to install a critical component.
Follow the instructions in the dialog box:
(1) Reboot the server.
(2) Log in as the administrator.
Consider this to be an informational message only.
To continue the installation, Click OK.
You must provide the Computer Name of the publisher server. IP addresses or fully qualified DNS names are not allowed.
You must not enter periods (.) when you enter the publisher database server name.
Reenter the information correctly.
You must provide the publisher server name when installing a subscriber.
This message displays when you install Cisco Unified CallManager on the subscriber server and do not provide the publisher database server name.
Reenter the information correctly.
You have entered an invalid product key. Please re-enter the key.
You entered an invalid product key.
See the Cisco CRS installation documentation to obtain the Cisco CRS product keys. See this document for the Cisco Unified CallManager product key.
You must enter a password.
This message displays when you do not enter a password, but the application requires a password for the installation to occur.
Enter the correct password.
The passwords that you entered do not match.
This message displays when you enter a password more than one time, but the password that you enter does not match the password on the server.
Enter the same password on all servers in the cluster.
The password that you entered is not valid.
You entered an invalid password.
Enter the correct password.
You must enter a phrase from 1 to 15 characters in length. This phrase may contain English lower-case letters, English upper-case letters, Westernized Arabic numerals, and the following Non-alphanumeric "special characters" { } . < > : ? / | \ ` ~ ! @ $ ^ & * ( ) _ - +
You entered invalid characters for the private password phrase.
Enter valid characters.
The installation has detected pending file operations. You must reboot the server before continuing. The installation will now abort.
Pending file operations are occurring.
Reboot the server and then install Cisco Unified CallManager.
You are not logged on as `Administrator'. You must log in by using local Administrator user name and password to install Cisco Unified CallManager.
You did not log in to the server with the local Administrator user name and password.
Log in to the server with the local Administrator user name and password.
You do not have administrator privileges. You must have administrator privileges to install Cisco Unified CallManager.
You do not have administrative privileges.
Log in to the server with an account that has administrative privileges.
Windows 2000 Server is not installed. Install Windows 2000 Server before you install Cisco Unified CallManager.
You did not install the appropriate version of the operating system.
Make sure that you installed the operating system version 2000.4.2sr10 (or later) on all dedicated and coresident servers. Upgrade to 2000.4.2sr10 (or later) and install the latest service release (2000.4.2sr10 or later) before installing Cisco Unified CallManager.
Windows 2000 Service Pack 4 or later is not installed. You must have Windows 2000 Service Pack 4 or later installed before you install Cisco Unified CallManager.
You did not install the appropriate version of the operating system.
Make sure that you installed the operating system version 2000.4.2sr10 (or later) on all dedicated and coresident servers. Upgrade to 2000.4.2sr10 (or later) and install the latest service release (2000.4.2sr10 or later) before installing Cisco Unified CallManager.
You must install CallManager by double clicking CCMSetup.exe.
You tried to install Cisco Unified CallManager by double clicking the msi file that is part of the Cisco Unified CallManager package.
Double-click the file CCMSetup.exe.
Cisco Unified CallManager could not install the SUN Microsystems JRE component. Review the Cisco Unified CallManager installation logs to determine cause of failure, take appropriate action. For more information refer, to the Cisco Unified CallManager installation documents.
JRE installation failed.
Obtain and examine the log file.
Cisco Unified CallManager installation has detected JRE version <JREVERSION> installed at <JRELOCATION>. Uninstall this version of JRE from the server and rerun the installation. To continue the installation, you must disable or stop any anti-virus protection, intrusion detection software, and other third-party applications, and then rerun the installation program.
Installation detected a version of JRE that is not compatible or a version that may not have all necessary components installed
Uninstall the current JRE version and rerun the installation program.
Cisco Unified CallManager successfully installed Sun JRE and requires the server to be rebooted. To continue the installation, you must disable or stop any anti-virus protection, intrusion detection software, and other third-party applications, and then rerun the installation program.
Cisco Unified CallManager requires the server to be rebooted to continue the installation.
Reboot the server and rerun the installation program.
If you have installed intrusion detection or anti-virus protection software, you must stop and disable these applications from the Services Control console before you continue with the Cisco Unified CallManager installation. All other installed third-party applications must be uninstalled before proceeding with the Cisco Unified CallManager installation. Failure to follow these directives could result in un-recoverable errors. Would you like to proceed?
This message always displays to alert the administrator of the requirements.
If you have Cisco-verified applications (Cisco Partner Applications) or platform agents that are installed on the server, you must disable/uninstall them and stop the services.
Because the <BUILDVERSION> of this Cisco Unified CallManager MSI package is not compatible with the Cisco Unified CallManager setup file (ccmsetup.exe), make sure that you are using the ccmsetup.exe that was distributed with this version of Cisco Unified CallManager. The installation will now abort.
The MSI package is not compatible with the Cisco Unified CallManager setup file.
Use the ccmsetup.exe file that was distributed with this version of Cisco Unified CallManager.
The installation detected that the server exists in a domain. When a server exists in a domain, authentication between servers may fail, or the non-default domain security policies may be so restrictive that the Cisco Unified CallManager installation cannot build critical NT Accounts during an upgrade. If server is not removed from the domain and added to a workgroup, upgrade errors, upgrade failures, or a total system failure, which includes a loss of data and a complete reinstallation of Cisco Unified CallManager, could result. Would you like to proceed?
The server exists in a domain.
Before you continue the installation, Cisco strongly recommends that you remove all servers in the cluster from the domain.
This release of Cisco Unified CallManager is not supported on this server model. The installation will now abort.
You cannot install this version of Cisco Unified CallManager on this server.
Refer to the Cisco Unified CallManager Compatibility Matrix for a list of servers on which you can install this version of Cisco Unified CallManager. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
The installation program does not have enough disk space on the C drive to complete the installation. The installation program requires that you have 3.0 gigabytes of disk space available on your server. Make at least 3.0 gigabytes of disk space available and restart the installation.
You do not have enough disk space on the C: drive of your server to install Cisco Unified CallManager.
Create enough disk space on the C: drive and restart the installation.
The local security policy "Restrict CD-ROM access to locally logged-on user only" is enabled. This setting interferes with the Cisco Unified CallManager installation. Please disable this setting using the Local Security Policy utility, reboot, and rerun the Cisco Unified CallManager installation.
This message displays when the "Restrict CD-ROM access to locally logged-on user only" local security policy is enabled on your server.
Disable this setting by using the Local Security Policy utility, reboot, and rerun the Cisco Unified CallManager installation.
For more information, see the "Disabling the Restrict CD-ROM Access to Locally Logged-On User Only Security Policy" section.
This package is for upgrades of existing Cisco Unified CallManager installations only.
You attempted to use the Cisco Unified CallManager web download file to install Cisco Unified CallManager.
Use the disks that came with the software kit to install Cisco Unified CallManager
A newer version of Cisco Unified CallManager is already installed.
This message displays when you attempt to install a previous version of Cisco Unified CallManager after a successful installation of a later version.
Remove the disk from the drive.
Cisco Unified CallManager install did not complete successfully. Review the log file for more information.
The Cisco Unified CallManager installation failed.
Obtain and examine the log file.
Unable to locate MSI package associated with this bootstrapper.
You did not copy all the files that came with the Cisco Unified CallManager installation package to the server.
Copy the complete installation package to the server and rerun the Cisco Unified CallManager installation.
Error opening MSI package.
Cisco Unified CallManager Setup cannot find the MSI package.
This message displays if you encounter a media problem; insert the disk again.
This package has already been installed.
This message displays when you attempt to install the same version of Cisco Unified CallManager again after a successful installation.
Remove the disk from the drive.
An unexpected error occurred.
An error occurred during the Cisco Unified CallManager Setup.
Obtain and examine the log file.
An unexpected error occurred while creating the log directory.
The installation could not create the log file directory.
Verify that security policies on the server are not restrictive.
Failure occurred trying to get DBNAME value from registry. Aborting Cisco Unified CallManager installation.
The installation could not read DBNAME value from registry on the local machine.
Reboot the server and rerun the Cisco Unified CallManager installation.
Failure occurred trying to validate the format of DBNAME value. Aborting Cisco Unified CallManager installation.
The registry contains an invalid format of the DBNAME value. This only occurs if you manually modified this value.
Make sure that the DBNAME value is in the format CCM0xxx, where x stands for any digits.
Current OS version does not meet minimum requirements. This version of CallManager requires the minimum OS version to be <MinOSVersion>. The minimum baseline OS image version is <MinOSBaseVersion>.
For more information, refer to the "Installing the Operating System on the Cisco Unified Communications Applications Server and Upgrading Cisco Unified CallManager" documents. The installation will now abort.
This version of Cisco CallManger requires Cisco-provided operating system version 2000.4.2sr10 (or later) and the service release 2000.4.2sr10 (or later.)
Refer to Cisco Compatibility Matrix to review which versions are compatible for installation. To access the document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
Installing Cisco Unified CallManager using Terminal Services is not allowed. Install will now abort.
Cisco does not support Terminal Services for Cisco Unified CallManager installations, upgrades, or configuration tasks.
Cisco Technical Assistance Center (TAC) uses Terminal Services for remote management and troubleshooting tasks.If you want to use Virtual Network Computing (VNC), obtain the most recent version of the documentation at http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm.
Failed to launch <name of executable>, aborting install.
The installation attempted to launch the executable, and the launch failed.
Obtain and examine the log file. You may have a media problem.
Failure occurred during the Cisco Directory installation. Refer to the log file C:\Program Files\Common Files\Cisco\Directory\IntegratedSetup.trc for details. Aborting Cisco Unified CallManager install.
The DC Directory installation failed.
Obtain and examine the log file.
Failure occurred during the Cisco Unified CallManager installation. Please look at the Cisco Unified CallManager installation log file for details. Aborting Cisco Unified CallManager installation.
The Cisco Unified CallManager installation detected an error while copying files.
Stop all platform agents and Cisco-verified applications and restart the installation.
Obtain and examine the log file.
The Cisco Unified CallManager installation detected an error while copying files. Stop all platform agents and Cisco-verified applications, and restart the installation. For more information, refer to the Upgrading Cisco Unified CallManager document.
The Cisco Unified CallManager installation failed to copy files to your server.
Stop all platform agents and Cisco-verified applications and restart the installation. For more information, see the "Performing Preinstallation Tasks" section
Either passwords do not match or a network connectivity error occurred.
During the subscriber server installation, one of the following errors occurred:
•
•
•
Do all the following tasks:
•
•
•
The password of [X] does not match the password on the publisher [servername]. For details, review the log file [Z].
The username and/or password of the user who is installing Cisco Unified CallManager on the subscriber server does not match the username and/or password on the publisher database server.
Make sure that you entered the correct publisher server name and that the username and password on the publisher and subscriber match.
Because no network connectivity exists or you entered the incorrect publisher server name, the installation could not verify the password of [username] against the publisher [servername]. For details, review the log file [X].
During Subscriber installation, this message occurs if no network connection exists between the subscriber and publisher database servers or you did not enter the correct name of the publisher database server.
Verify the connection between the publisher database server and subscriber server and make sure that you entered the correct publisher database server name.
Either the password of [X] does not match the password on the publisher [Y], or a network connectivity error occurred. For details, review the log file [Z].
One of the following problems occurred:
•
•
•
Do each of the following tasks:
•
•
•
The private password phrase does not match the private password phrase on the publisher [servername]. For details, review the log file [Y].
During the subscribe server installation, one of the following problems occurred:
•
•
•
Do each of the following tasks:
•
•
•
The installation failed to verify the Cisco Unified CallManager version that runs on the publisher database server. Cancel the installation, and review the log file at C:\Program Files\ Common Files\Cisco\Logs\ CCMUIInst.log.
During subscriber server installation, this error occurs if no network connection exists between the subscriber and publisher database servers or if you did not enter the correct name of the publisher database server.
Verify the connection between the publisher database server and subscriber database server and make sure that you entered the correct publisher database server name.
The Cisco Unified CallManager version that you are installing on this subscriber does not match the version running on the publisher database server. Cancel the installation and ensure the publisher is upgraded to this Cisco Unified CallManager version before you continue.
You attempted to install a different version of Cisco Unified CallManager on the subscriber database server than the version that you installed on the publisher database server.
Install the same version of Cisco Unified CallManager on the subscriber database server that you installed on the publisher database server.
Configuration changes to the Cisco Unified CallManager server do not take effect until you restart your system. Click Yes to restart the computer now or No if you plan to restart the computer later.
This message displays when you make configurational changes to Cisco Unified CallManager during installation.
You do not need to take any corrective action.
Cisco Unified CallManager installation detected a service control file from a previous failed installation. This may have resulted in incorrect service Startup Type settings. Click: "Yes" to continue installing with the current settings, "No" to reset service startup types to the original settings and exit the installation program, or "Cancel" to exit the installation program with no further action.
This message displays when the installation program detects a previous failed installation.
Cisco recommends that you choose Yes and continue installing Cisco Unified CallManager with the current settings.
To proceed, the installation program must update the configuration and restart the server. To continue the installation with these changes and restart the server now, click OK. To abort the installation, click Cancel.
Consider this to be an informational message only.
Cisco recommends that you click OK to continue the installation.
UMX.dll failed to register. After you complete the installation, review the log file.
UMX.dll failed to register because the process creation failed, the process terminated abnormally, or an error occurred when regsvr32 was executing.
Verify that you rebooted the server after the installation. Execute a command prompt, enter regsvr32 C:\dcdsrvr\lib\UMX.dll, and press Enter.
To verify that you corrected the problem, try to add a new user in Cisco Unified CallManager Administration on this server.
Indexing directory data did not finish. After you complete the installation, review the log file. C:\dcdsrvr\log\DirInstallValidation.log.
The installation could not determine whether the DC Directory completed the indexing of its data.
Continue with installation. At the end of the installation, reboot the server when prompted to do so. After you reboot the server, bring up the services control and wait for DC Directory Server to have a status of started.
If this is a publisher database server, you can install Cisco Unified CallManager on the subscriber database servers.
If this is a subscriber database server, go to a command window and enter dcdrepcl trigger all. Depending on the number of users that are configured in your system, the service may be in the starting state for a long time before changing to a started state.
The Cisco Unified CallManager installation failed to stop <list of services> service(s). Please reboot the server, manually stop the service(s), and rerun the Cisco Unified CallManager installation program.
The installation program failed to stop the services during installation.
Reboot the server, manually stop the service(s), and rerun the Cisco Unified CallManager installation program.
The installation encountered an unknown error while trying to resolve the Publisher server name [X]. For more information, review the log file CCMInstUI.log.
The name resolution of the publisher server failed.
Verify that you correctly entered the publisher server name. To verify the hosts file, see the "Resolving Name Resolution Failures" section.
The installation could not resolve the Publisher server name [X] to a valid IP address. Verify that you entered the correct publisher server name, and review the log file CCMInstUI.log for more information.
You entered the wrong publisher server name, or the hosts file has the wrong information.
Verify that you correctly entered the publisher server name. To verify the hosts file, see the "Resolving Name Resolution Failures" section.
The installation successfully resolved the Publisher server name [X] to IP address [Y] but could not resolve the IP address back to a host name.
The reverse name resolution of the Cisco Unified CallManager publisher server failed.
Verify that you correctly entered the publisher server name. To verify the hosts file, see the "Resolving Name Resolution Failures" section.
The installation successfully resolved the Publisher server name [X] to IP address [Y] and resolved the IP address back to the host name [Z]. The resolved host name does not match the server name that you entered.
The publisher server name that you entered does not match the server name that the installation program retrieved after completing forward and reverse name resolution.
Verify that you correctly entered the publisher server name. To verify the hosts file, see the "Resolving Name Resolution Failures" section.
Because mapped network drives exist on the server, the installation could not verify the password of [username] against the publisher [servername]. Disconnect all the mapped drives, reboot the system, and rerun the installation. For details, review the log file [x].
The installation could not verify that the password on the subscriber server matches the password on the publisher database server.
Disconnect all the mapped drives, reboot the system, and rerun the installation.
Because mapped network drives exist on the server, the installation could not verify the private password phrase against the publisher [servername]. Disconnect all the mapped drives, reboot the system, and rerun the installation. For details, review the log file [z].
The installation could not verify that the private password phrase on the subscriber server matches the private password phrase on the publisher database server.
Disconnect all the mapped drives, reboot the system, and rerun the installation.
The installation could not verify the private password phrase on the publisher <server name>, because the user does not have permission to access the publisher server over the network. For details, review the log file <log file name>.
The installation could not verify the private password phrase on the publisher <server name> because the user does not have permission to access the publisher server over the network. For details, review the log file <log file name>.
During the installation of a subscriber server, the installation program could not verify the private password phrase against the publisher server because of the security settings on either the publisher or the subscriber server.
The following probable causes exist:
•
•
Cisco Unified CallManager installation failed while installing Microsoft SQL 2000. Review the Cisco Unified CallManager installation logs to determine the cause of failure. Take appropriate action and reinstall both the Cisco Unified Communications Operating System and Cisco Unified CallManager program. For more information refer, to the Cisco Unified CallManager installation documents.
The following items comprise the probable causes:
•
•
Review the Cisco Unified CallManager installation to determine the cause of failure. Take appropriate action to either remove the virus or disable the specified software and then reinstall both the Cisco Unified Communications Operating System and Cisco Unified CallManager program.
Cisco Unified CallManager successfully installed Microsoft SQL 2000 and requires the server to be rebooted. To continue the installation, you must disable or stop any anti-virus protection, intrusion detection software, and other third-party software, and then rerun the installation program. When the server reboots, you must rerun the installation program to continue your installation.
Antivirus, intrusion detection, or other third-party application was installed and running
To continue the installation, you must do the following tasks:
a.
b.
c.
Cisco Unified CallManager installation failed while installing Microsoft SQL 2000 SP4. Review the Cisco Unified CallManager installation logs to determine cause of failure, take appropriate action. Download Microsoft SQL 2000 service pack 4 (or later) from Cisco.com, install it on the server, and rerun the Cisco Unified CallManager installation program. For more information refer, to the Cisco Unified CallManager installation documents.
The following items comprise the probable causes:
•
•
Download Microsoft SQL 2000 service pack 4 (or later) from Cisco.com, install the service pack on the server, and then rerun the Cisco Unified CallManager installation program.
Cisco Unified CallManager successfully installed Microsoft SQL 2000 SP3A and requires the server to be rebooted. To continue the installation, you must disable or stop any antivirus protection, intrusion detection software, and other third-party applications, and then rerun the installation program. When the server reboots, you must rerun the installation program to continue your installation. The installation program automatically reboots the server and the installation will continue.
Antivirus, intrusion detection, or other third-party application was installed and running
To continue the installation, you must do the following tasks:
a.
b.
c.
Cisco Unified CallManager could not install the Microsoft MDAC Hotfix MS04-003 at this time.
When the installation has finished, please reapply the latest Cisco OS Upgrade Service Release.
For more information refer to the Cisco Unified CallManager installation documents
The hotfix timeout of 1800 seconds expired.
This condition does not affect the Cisco Unified CallManager installation, but when the installation finishes, reapply the latest Cisco OS Upgrade Service Release.
Cisco Unified CallManager could not install the Microsoft SQL 2000 Hotfix MS03-031.
When the installation has finished, download the SQL 2000 Hotfix MS03-031 from cisco.com, and manually install it.
For more information refer to the Cisco Unified CallManager installation documents
The Microsoft SQL Hotfix MS03-031 installation failed, possibly because Cisco CSA or an antivirus software was installed and running.
This situation does not affect the Cisco Unified CallManager installation. When the installation finishes, disable Cisco CSA or the antivirus software, download the SQL 2000 Hotfix MS03-031 from cisco.com, and manually install it. You can reenable Cisco CSA and the antivirus software after installing the hotfix.
You can download the file SQL2K-MS03-031.exe at http://www.cisco.com/cgi-bin/tablebuild.pl/cmva-3des-archive
The installation program detected an insufficient amount of memory for this version of Cisco Unified CallManager to function properly on this server. You may continue installing this version on a subscriber server, but you must increase the amount of memory on this server to a minimum of 1 GB after the installation to avoid any system problems.
The server does not meet the minimum memory requirement.
You may continue the installation, but Cisco recommends that you increase the memory on this server to a minimum of 1 GB after the installation to avoid system problems.
The installation program detected an insufficient amount of memory for this version of Cisco Unified CallManager to function properly on this server. Please increase the amount of memory you have on this server to a minimum of 1 GB before you install this version of the program.
The server does not meet the minimum memory requirement.
Increase the memory on this server to a minimum of 1 GB before you install Cisco Unified CallManager.
DBAccess Failure
Attempt to access the database has failed.
Collect c:\install\dbinstall\dbinstallxxx.txt for diagnosis.During subscriber server installation, this error occurs if issues exist in the replication of databases between the subscriber and publisher database servers or if you did not enter the correct name of the publisher database server.
Verify the replication between the publisher database server and subscriber server and make sure that you entered the correct publisher database server name. To verify the hosts and lmhosts files, see the "Resolving Name Resolution Failures" section.
Resolving Name Resolution Failures
Cisco Unified CallManager requires NetBIOS and IP name resolution. An incorrect WINS (NetBIOS) or DNS (IP) configuration could result in a service outage.
To resolve name resolution failures, consult with your network administrator to confirm NetBIOS and IP name resolution within the entire network, which includes local device IP configurations, local device name resolution (LMHOSTS and HOSTS), network-based name resolution systems (WINS and DNS), and DHCP systems.
Note
Note
Note
Procedure
Step 1
Step 2
The following example illustrates a hosts file where cm1 represents the hostname and mydomain.com represents the default DNS suffix or connection-specific DNS suffix from the ipconfig /all command output.
127.0.0.1 localhost
1.3.5.9 cm1 cm1.mydomain.com
1.2.4.8 cm2 cm2.mydomain.comStep 3
The following example illustrates a lmhosts file where cm1 represents the hostname.
1.3.5.9 cm1 #PRE
1.2.4.8 cm2 #PREStep 4
ipconfig /flushdns
nbtstat -R
Note
Step 5
a.
The names of all other servers in the cluster should appear with a life of -1. The names appear multiple times.
The following example represents the output of the nbtstat -c command:
CM2
<03>
UNIQUE
1.3.5.9
-1
CM2
<00>
UNIQUE
1.3.5.9
-1
CM2
<20>
UNIQUE
1.3.5.9
-1
CM1
<03>
UNIQUE
1.2.4.8
-1
CM1
<00>
UNIQUE
1.2.4.8
-1
CM1
<20>
UNIQUE
1.2.4.8
-1
b.
Forward Entries
cm1.mydomain.com.------------------------------------------------------Record Name . . . . . : cm1.mydomain.comRecord Type . . . . . : 1Time To Live . . . . : 30682708Data Length . . . . . : 4Section . . . . . . . : AnswerA (Host) Record . . . :> 1.2.4.8cm1.------------------------------------------------------Record Name . . . . . : cm1Record Type . . . . . : 1Time To Live . . . . : 30682708Data Length . . . . . : 4Section . . . . . . . : AnswerA (Host) Record . . . :> 1.2.4.8Reverse Entries
8.4.2.1.in-addr.arpa.------------------------------------------------------
Record Name . . . . . : 8.4.2.1.in-addr.arpaRecord Type . . . . . : 12Time To Live . . . . : 30682708Data Length . . . . . : 4Section . . . . . . . : AnswerPTR Record . . . . . :> cm1Record Name . . . . . : 8.4.2.1.in-addr.arpaRecord Type . . . . . : 12Time To Live . . . . : 30682708Data Length . . . . . : 4Section . . . . . . . : AnswerPTR Record . . . . . :cm1.mydomain.com
Disabling the Restrict CD-ROM Access to Locally Logged-On User Only Security Policy
If you receive the message that the local security policy "Restrict CD-ROM access to locally logged-on user only" is enabled, you must disable the setting, reboot the server, and rerun the Cisco Unified CallManager installation. Use the following procedure to disable the security policy.
Procedure
Step 1
Step 2
Step 3
The Local Security Policy dialog box displays.
Step 4
Step 5
Step 6
Step 7
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .PDF versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you will find information about how to:
•
•
•
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of the network is impaired, while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/en/US/learning/index.html
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. 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. (0601R)
Copyright © 2006. Cisco Systems, Inc. All rights reserved
.
