 Feedback
|
Table Of Contents
Upgrading Cisco CallManager Release 3.3(4)
Locating Related Documentation
Frequently Asked Questions About Cisco CallManager 3.3 Upgrades
From which versions of Cisco CallManager can I upgrade to Cisco CallManager Release 3.3(4)?
What disks and information do I need to gather before I upgrade?
Which server in the cluster do I upgrade first?
How does a co-resident upgrade work if I have CRS installed with Cisco CallManager?
How long does it take to upgrade the cluster?
Will I experience call-processing interruptions and a loss of services during the upgrade?
May I configure a server in the cluster as a Domain Controller?
May I perform configuration tasks during the upgrade?
May I remove a drive before I upgrade?
Which third-party, Cisco-verified applications may I install on the Cisco CallManager server?
Which Cisco IP telephony applications may I install on the Cisco CallManager server?
What additional information should I know before I upgrade?
Which tasks should I perform on all servers at the same time?
What pre-upgrade tasks should I perform?
What upgrade tasks should I perform serially, that is, on one server at a time?
What post-upgrade tasks should I perform?
What if I encounter problems during the upgrade?
Upgrading From Cisco CallManager 3.1 or 3.2 (If You Are Not Replacing Hardware)
Performing Tasks on All Servers at the Same Time
Disable and Stop Third-Party, Cisco-Verified Applications and Reboot the Server (Required)
Run the Cisco CallManager Upgrade Assistant Utility (Strongly Recommended)
Upgrading the Cisco CallManager 3.1 or 3.2 Publisher Database Server
Disable and Stop Third-Party, Cisco-Verified Applications and Reboot the Server (Required)
Back Up Existing Data (Required)
Removing a Drive, Inserting a Replacement Drive, and Drive Mirroring (Strongly Recommended)
Install the Operating System by Using Same Server Recovery (Required)
Upgrade the Operating System to Cisco-Provided Version 2000.2.5 (or Later) (Required)
Download and Install the Latest OS Related Security Hotfixes (If Any) (Recommended)
Install Cisco CallManager (Required)
Back Up the Current Database (Required)
Upgrading Cisco CallManager 3.1 or 3.2 Subscriber Servers
Run the ServPrep Utility (Required)
Installing Cisco CallManager on Subscriber Database Server(s)
Upgrading From Cisco CallManager 3.3(3) (If You Are Not Replacing Hardware)
Upgrading the Cisco CallManager 3.3(3) Publisher Database Server
Upgrading the Cisco CallManager 3.3(3) Subscriber Server(s)
Tasks for the Cisco CallManager 3.3 Upgrade
Inserting the Disk or Downloading the Web File
Upgrading Related Cisco CallManager Services and Detecting the Server
Enabling Cisco-Verified McAfee Antivirus Services
Verifying and Reinitializing Subscriber Connections
Verifying Services, Patches, and Hotfixes
Viewing the Component Versions That Are Installed on the Server
Upgrading TAPI, JTAPI, and Cisco Telephony Service Provider (TSP)
Upgrading the Cisco TAPI/TSP for Cisco SoftPhone
Using the Cisco CallManager Music On Hold Disk or Download
Reverting to the Previous Configuration After an Upgrade Attempt
Reconfiguring If You Did Not Pull a Drive Before the Upgrade
Reconfiguring If You Removed a Drive Before the Upgrade
Reverting the Hard Drive After Drive Mirroring Completes
Reverting Upgraded Cisco IP Telephony Applications After You Revert Cisco CallManager
Resolving Name Resolution Failures
Disabling the Restrict CD-ROM Access to Locally Logged-On User Only Security Policy
Replacing Servers During the Upgrade
Replacing Cisco CallManager 3.1/3.2 Subscriber Server(s) During a Cisco CallManager 3.3 Upgrade
Troubleshooting Hardware Replacements During Upgrades
Upgrading the Cisco ICS 7750 to Cisco CallManager 3.3(4)
Obtaining Technical Assistance
Cisco Technical Support Website
Obtaining Additional Publications and Information
Upgrading Cisco CallManager Release 3.3(4)
CautionWith Cisco CallManager Release 3.3(4), Cisco significantly changed upgrade and installation procedures. You must perform all installation/upgrade procedures as stated in the Cisco CallManager installation/upgrade documentation. Failure to do so may cause installation errors, installation failures, and, during upgrades, a total system failure, including a loss of Cisco CallManager data/configuration settings.
Purpose of Document
This document provides Cisco CallManager upgrade procedures and requirements for the Cisco Media Convergence Server and the customer-provided server that meets approved Cisco configuration standards.
This document contains information on the following topics:
•
•
•
•
•
•
•
Tip
Conventions
Consider the following documentation conventions as you review this upgrade document:
Using the Cisco IP Telephony Applications Backup Utility, Version 3.5.53 (or later) replaces the document, Backing Up and Restoring Cisco CallManager Release 3.3.
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.
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.
Locating Related Documentation
Cisco strongly recommends that you review the following documents before you upgrade:
•
Cisco provides a version of this document that matches the version of the upgrade document. Use this document as a companion guide to the upgrade document.
•
To ensure continued functionality with interfacing Cisco IP telephony applications after the Cisco CallManager upgrade, refer to the Cisco CallManager Compatibility Matrix, which provides information and workarounds for applications that are integrated with Cisco CallManager.
Affected applications may include Cisco Conference Connection, Cisco SoftPhone, Cisco uOne, Cisco 186 Analog Telephony Adaptor, Cisco Personal Assistant, Cisco Customer Response Solutions (CRS), Telephony Application Programming Interface and Java Telephony Application Programming Interface (TAPI/JTAPI) applications, including Cisco- provided and third-party applications, and Cisco Telephony Service Provider (TSP).
If you use Cisco CallManager and related Cisco IP telephony applications in a call-center environment, review this document before you begin any upgrade 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 CallManager, Conference Connection, Personal Assistant, and Cisco Customer Response Applications/Solutions, and so on.
•
This document describes how to install the utility, configure the backup settings, back up Cisco CallManager data, and restore the data/server.
This document also provides a list of files that the utility backs up. This utility does not back up operating system files, except for Hosts/LMHosts files, if those files exist on the server.
•
Locate the release notes, installation/upgrade, and configuration guides for the applications that you have integrated with Cisco CallManager.
Click the URLs in Table 1 to navigate to the appropriate documentation.
Table 1 Quick Reference for URLs
Operating system documentation and Virtual Network Computing (VNC) documentation
(not readme documentation)
http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm
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 CallManager Compatibility Matrix
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm
Cisco CallManager documentation
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm
Cisco CallManager backup and restore documentation
http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm
Cisco CallManager, SQL Server, and operating system service releases, upgrades, and readme documentation
http://www.cisco.com/public/sw-center/sw-voice.shtml
See the "Verifying Services, Patches, and Hotfixes" section.
Note
Related Cisco IP telephony application documentation
http://www.cisco.com/univercd/cc/td/doc/product/voice/index.htm
Cisco Integrated Communications System (ICS) 7750
http://www.cisco.com/univercd/cc/td/doc/product/voice/ics/index.htm
Contents
This document contains the following topics:
Information That Applies for All Cisco CallManager 3.3 Upgrades
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Upgrading from Cisco CallManager 3.1 or 3.2 (If You Are Not Replacing Hardware)
•
•
•
–
–
–
–
–
–
•
Upgrading from Cisco CallManager 3.3(3) (If You Are Not Replacing Hardware)
•
•
•
•
Post-Upgrade Tasks (For all Cisco CallManager 3.3 Upgrades)
•
•
•
•
•
•
•
Reversion Tasks
•
•
•
•
Upgrade Error Messages
Replacing Servers During the Upgrade (For All Upgrades to Cisco CallManager 3.3(4))
•
•
Upgrading the Cisco ICS 7750 to Cisco CallManager 3.3(4)
•
Frequently Asked Questions About Cisco CallManager 3.3 Upgrades
The following frequently asked questions apply for all Cisco CallManager 3.3 upgrades. For information that is specific to the version upgrade, see the following sections:
•
•
Tip
If you are upgrading the Cisco ICS 7750, skip to the "Upgrading the Cisco ICS 7750 to Cisco CallManager 3.3(4)" section.
From which versions of Cisco CallManager can I upgrade to Cisco CallManager Release 3.3(4)?
To verify which versions of Cisco CallManager are compatible for upgrade, refer to the Cisco CallManager Compatibility Matrix. To obtain the most recent version of this document, see Table 1.
If your server runs Cisco CallManager Release 2.4 or 3.0, you must upgrade every server in the cluster to the latest version of Cisco CallManager Release 3.1 before you can upgrade to a version of Cisco CallManager Release 3.3. For information on upgrading to Cisco CallManager Release 3.1, refer to the latest version of Upgrading Cisco CallManager Release 3.1.
Caution
Which servers, operating system versions, and server configurations does Cisco support for this upgrade?
For Cisco CallManager Release 3.3(4), Cisco supports the servers that are listed in the Cisco CallManager Compatibility Matrix. To obtain the most recent version of this document, click the appropriate URL in Table 1.
Cisco requires that you install Cisco-provided operating system version 2000.2.5 with service release 2 (2000.2.5sr2) (or later) before you upgrade to Cisco CallManager Release 3.3(4).
For Cisco CallManager 3.1/3.2 Upgrades to 3.3(4)
You must perform a same server recovery by using the operating system disks that ship with this version of Cisco CallManager to install operating system version 2000.2.4 before you upgrade to 2000.2.5sr2. You cannot upgrade to Cisco-provided operating system version 2000.2.5sr2 (or later) from a previous version of the operating system. For detailed instructions, refer to "Upgrading From Cisco CallManager 3.1 or 3.2 (If You Are Not Replacing Hardware)" section.
For Cisco CallManager 3.3 Upgrades to 3.3(4)
If your server runs Cisco CallManager 3.3 and operating system version 2000.2.3 (or later), you can use the operating system upgrade CD-ROM or the operating system upgrade web download to upgrade the operating system to 2000.2.5sr2 or later. For detailed instructions, refer to "Upgrading From Cisco CallManager 3.3(3) (If You Are Not Replacing Hardware)" section.
What disks and information do I need to gather before I upgrade?
If you are upgrading from Cisco CallManager 3.1 or 3.2, you must upgrade via the disks that come in the software kit.
When you upgrade Cisco CallManager from Cisco CallManager 3.1 or 3.2, the following software installs:
•
•
•
•
Caution
Before you upgrade from Cisco CallManager 3.1 or 3.2, locate the following disks.
•
•
If you are upgrading to Cisco CallManager 3.3 from 3.1 or 3.2, you must use the server-specific 2000.2.4 operating system disk that comes in the software kit. During the operating system installation, you receive a prompt to insert the appropriate disk into the drive.
•
This disk upgrades the operating system on existing (not new) servers in the cluster.
•
You use this disk to start the publisher database server upgrade. This disk installs the backup utility that you must use prior to the upgrade.
•
You use this disk to start all subscriber server upgrades. This disk installs the ServPrep utility.
•
You use this disk to complete all Cisco CallManager upgrades from 3.1 or 3.2. You can use this disk if you are upgrading from Cisco CallManager 3.3(3). This disk installs Cisco CallManager, Microsoft SQL Server 2000, and DC Directory. If you are upgrading from Cisco CallManager 3.1 or 3.2, the disk also installs Microsoft SQL Server 2000 Service Pack 3a (or later).
About Information That You Enter During the Upgrade
Before the upgrade, obtain the local Administrator account password, the SQL server SA password, the Private Password Phrase, and the computer name of the publisher database server.
Caution
The upgrade prompts you for a Private Password Phrase. The upgrade uses the string that you enter to create a unique, encrypted password. You must enter the same phrase on all servers in the cluster.
Use the information in Table 2 when you perform the upgrade procedures.
Which server in the cluster do I upgrade first?
Timesaver
You must perform the Cisco CallManager installation serially.
Caution
Caution
You must upgrade all the servers in the cluster. See Table 3, which describes the upgrade order for the following cluster configurations:
•
•
How does a co-resident upgrade work if I have CRS installed with Cisco CallManager?
For information on how to perform the upgrade on a co-resident server, refer to the CRS documentation that is compatible with this version of Cisco CallManager.
How long does it take to upgrade the cluster?
To minimize call-processing downtime, Cisco strongly recommends that you perform all upgrade procedures for the Cisco CallManager and all upgrades/reinstallations for Cisco IP telephony applications within a consecutive time period (within one maintenance window).
Before you perform an upgrade, consider the time that it takes to perform pre-/post-upgrade tasks, Cisco IP telephony application upgrades/reinstallations, and Cisco-verified application upgrades/reinstallations.
For the time that it takes to perform specific tasks on the publisher database server, see the following sections:
•
•
Will I experience call-processing interruptions and a loss of services during the upgrade?
Review the following information before you upgrade.
About Minimizing Call-Processing Interruptions
When you upgrade a cluster, two separate versions of Cisco CallManager run in the cluster at the same time. Be aware that the different Cisco CallManager versions that are running in the cluster will not interact and may cause call-processing interruptions to occur.
If you configured your Cisco CallManager cluster by using approved Cisco configuration standards, which include configuring four primary servers and two backup servers in the cluster, you can minimize call-processing interruptions if you register all devices to servers that are running the same version of Cisco CallManager during the entire upgrade process; that is, you register all devices to the backup Cisco CallManager servers or the primary Cisco CallManager servers, but not to both types of servers.
About a Loss of Services
During the upgrade, Cisco CallManager places Cisco CallManager-related services that display in Cisco CallManager Serviceability in an inactive state. After the upgrade completes, migrated services activate and start after the server reboots. To use additional services, you must activate the service on each server on which you want the service to run. For information on activating services, refer to the Cisco CallManager Serviceability Administration Guide or to online help in the Cisco CallManager application.
Caution
May I use Terminal Services, Virtual Network Computing, and Integrated Lights Out to remotely upgrade the server?
Do not use Terminal Services to upgrade to Cisco CallManager Release 3.3(4). 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.
Caution
After you upgrade the server, you must enable Terminal Services.
If you want to use Virtual Network Computing (VNC) to remotely upgrade the publisher database server, see Table 1 to obtain the latest version of the VNC document.
Caution
Do not use Integrated Lights Out (ILO) to perform upgrade or installation tasks. Cisco supports ILO for remote management and configuration tasks only.
May I configure a server in the cluster as a Domain Controller?
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 or reinstall Cisco CallManager on the server.
May I perform configuration tasks during the upgrade?
Caution
Notify all users that the upgrade is occurring, so users do not browse into the server during the upgrade.
Performing configuration tasks during the upgrade causes an upgrade failure.
May I remove a drive before I upgrade?
Caution
Removing a Drive If the Server Runs Cisco CallManager 3.1 or 3.2—Replacement Drive Required
After you verify that you have a good backup of the data, you can remove a drive to save configured data; however, you must insert a replacement drive into the server before you begin the operating system procedures. The "Removing a Drive, Inserting a Replacement Drive, and Drive Mirroring (Strongly Recommended)" section describes how to properly perform this task.
This task may require that you purchase a new drive.
Before you begin the operating system installation, make sure that you have all drives in the server and verify that the drives are functional. For example, insert two drives for the MCS-7835 and four drives for the MCS-7845. Neglecting to perform these tasks causes the failure of the Cisco CallManager installation and the loss of data/configuration settings from drive-mirroring.
Removing a Drive If the Server Runs Cisco CallManager 3.3(3)—Inserting a Replacement Drive and Drive Mirroring Prior to the Upgrade
The "Removing a Drive, Inserting a Replacement Drive, and Drive Mirroring (Strongly Recommended)" section describes how to properly perform this task.
Removing a Drive If the Server Runs Cisco CallManager 3.3(3)—Upgrading With One Drive In the Server
Perform the following procedure if you plan to remove a drive and upgrade with one hard drive in the server.
Step 1
Step 2
For the MCS-7845, remove the drives from Slot 0 and Slot 2 and label them with the appropriate information.
Step 3
Cisco MCS
Step 4
a.
Note
b.
Step 5
IBM xSeries Server
Step 6
Step 7
Which third-party, Cisco-verified applications may I install on the Cisco CallManager server?
Caution
Caution
Disabling Third-Party, Cisco-Verified Applications (Required)
Caution
Disabling platform agents and services, such as performance monitoring (for example, NetIQ), antivirus (Cisco-verified McAfee services), intrusion detection, and remote management services, ensures that the installation does not encounter issues that are associated with these services.
Which Cisco IP telephony applications may I install on the Cisco CallManager server?
Consider the following information before you install other software besides Cisco CallManager on the Cisco MCS or the customer-provided server:
•
•
•
CSA for Cisco CallManager designates a standalone agent and security policy that is designed to be used on all servers in the voice cluster. The policy that is included with this agent gets configured specifically for Cisco CallManager and Customer Response Applications (CRA), and you cannot update or view it. You can download the agent from CCO at http://www.cisco.com/pcgi-bin/tablebuild.pl/cmva-3des.
If you want to add, change, delete, or view rules and policies that CSA for Cisco 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.
To access information on Cisco Security Agent, see http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/sec_vir/index.htm
Caution
What additional information should I know before I upgrade?
This document assumes that all servers in your cluster are currently in an operational state.
About Security and Account Policies
Caution
About Service and Enterprise Parameters in Cisco CallManager Administration
Cisco CallManager always updates service parameters with nonnumeric values to the suggested value.
For service parameters with numeric values, Cisco CallManager uses the following information to update the service parameters:
•
•
•
During the upgrade, some non-servicewide parameters may change to clusterwide parameters (formerly known as servicewide parameters).
About H.323 Intercluster Trunks
A registration problem occurs when multiple Cisco CallManager clusters have the same device name assigned to H.323 intercluster trunks in Cisco CallManager Administration. You must assign a unique device name to each H.323 intercluster trunk. Refer to the Cisco CallManager Administration Guide for information on the trunk configuration procedure.
About H.323 Gateways
Cisco no longer provides the Run H.225D On Every Node option in Cisco CallManager Administration for H.323 gateways. Before you upgrade, verify that all H.323 dial-peer(s) point to a Cisco CallManager server in the device profile for which they are assigned. If the session target statements in the dial-peer(s) do not point to the appropriate Cisco CallManager server, calls fail.
About Migrating Cisco CallManager Attendant Console
For your migrated version of Cisco CallManager Attendant Console to work, you must check the Call Park Retrieval Allowed check box for the "ac" user that you configured in the Global Directory. The attendant console does not initialize if you do not check this check box. For more information on how to perform this task, refer to the Cisco CallManager Administration Guide.
About Integrating the Enterprise Directory
If you have integrated your enterprise directory with Cisco CallManager, you must reinstall the Cisco Customer Directory Configuration Plugin on all servers in the cluster after the upgrade, starting with the publisher database server. Reinstalling the plugin populates your enterprise directory with any additional schema extensions and data entries that Cisco CallManager needs. For more information, refer to Installing the Cisco Customer Directory Configuration Plugin for Cisco CallManager.
About the Database
After you upgrade Cisco CallManager, the database name automatically increments; for example, from CCM0300 to CCM0301. Third-party CDR software may have SQL triggers that are hard coded to the original database name. The triggers may point to the previous database name and cause all CDR flat files to write to the BAD directory on the publisher database server. If you need technical assistance with this issue, directly contact the third-party software vendor.
About Cisco CallManager Extension Mobility
If you run Cisco CallManager Extension Mobility and Cisco CallManager 3.1/3.2 before the upgrade, you must perform additional configuration tasks after the upgrade, so Cisco CallManager Extension Mobility runs as expected. For more information on configuration tasks, refer to the Cisco CallManager Extension Mobility upgrade section of the Cisco CallManager Features and Services Guide. To obtain the most recent version of this document, see Table 1.
Which tasks should I perform on all servers at the same time?
Caution
Table 4 describes pre-upgrade tasks that you should perform on all servers at the same time.
Table 4 Pre-Upgrade Tasks That You Should Perform on All Servers at the Same Time
Remove the system from the NT Domain or Microsoft Active Directory Domain and reboot the servers. (Required, If Configured)
Caution
Disable Cisco-verified applications before the upgrade and reboot the servers. (Required, If Installed)
Disable and Stop Third-Party, Cisco-Verified Applications and Reboot the Server (Required)
Caution
What pre-upgrade tasks should I perform?
Table 5 describes additional pre-upgrade tasks that you should perform.
Table 5 Additional Pre-Upgrade Tasks
Make sure that you run a recommended version of Cisco CallManager on all servers in the cluster.
From which versions of Cisco CallManager can I upgrade to Cisco CallManager Release 3.3(4)?
Make sure that you understand the order in which you must upgrade the cluster.
Upgrading From Cisco CallManager 3.1 or 3.2 (If You Are Not Replacing Hardware)
How does a co-resident upgrade work if I have CRS installed with Cisco CallManager?
In Cisco CallManager Administration, make sure that you only add each server once on the Server Configuration window (System > Server). If you add a server using the host name and add the same server using the IP address, Cisco CallManager cannot accurately determine component versions for the server after a Cisco CallManager upgrade. If you have two entries in Cisco CallManager Administration for the same server, delete one of the entries before you upgrade.
Refer to the Cisco CallManager Administration Guide.
Make sure you have enough available disk space on each of your servers for the Cisco CallManager upgrade.
If you use the Cisco CallManager disks to upgrade, you need 2.0 gigabytes of disk space.
If you use the web file to upgrade, you need 3.0 gigabytes of disk space.
Make sure that you obtain disks for the Cisco-provided version operating system installation and upgrade.
Make sure that your server configuration supports this upgrade.
You may need to perform pre-upgrade configuration tasks for the Cisco IP telephony products to work after the upgrade.
See the "What additional information should I know before I upgrade?" section.
Locate information that you must provide during the upgrade.
See Table 2.
Back up co-resident software applications by referring to the documentation that supports the backup procedure.
Upgrading From Cisco CallManager 3.1 or 3.2 (If You Are Not Replacing Hardware)
How does a co-resident upgrade work if I have CRS installed with Cisco CallManager?
What upgrade tasks should I perform serially, that is, on one server at a time?
Cisco strongly recommends that you perform the following tasks serially:
•
•
Caution
•
Caution
•
Caution
•
Caution
The service release may post to the web after the Cisco CallManager upgrade.
What post-upgrade tasks should I perform?
Do not perform any post-upgrade tasks until you complete the upgrade on all servers in the cluster. See the "Performing Post-Upgrade Tasks" section for more information.
What if I encounter problems during the upgrade?
Cisco recommends that if you encounter problems during the upgrade, 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 Cisco CallManager does not use.
Upgrading From Cisco CallManager 3.1 or 3.2 (If You Are Not Replacing Hardware)
Caution
Caution
The Cisco IP Telephony Applications Backup Utility does not back up any operating system files except for Host/LMhost, if these files exist on the server. For a list of files that the utility backs up, refer to Using Cisco IP Telephony Applications Backup Utility, Version 3.5.53 (or later). To obtain the latest version of the document, see Table 1.
This section contains procedures and information on the following topics:
•
•
•
Performing Tasks on All Servers at the Same Time
You must perform the following tasks on all servers at the same time:
2.
3.
Remove the System From the NT Domain or Microsoft Active Directory Domain and Reboot the Server (Required, If Configured)
Tip
The reboot may cause call-processing interruptions.
Caution
Convert any servers that exist in the NT Domain or Microsoft Active Directory Domain by performing the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Disable and Stop Third-Party, Cisco-Verified Applications and Reboot the Server (Required)
Tip
The reboot may cause call-processing interruptions.To review a list of Cisco-verified applications that Cisco supports and that you should disable and stop before the installation, 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.
The following platform agents may interfere with the Cisco CallManager installation: antivirus services, intrusion detection services, OEM server agents, server management agents, VOIP monitoring/performance monitoring, or remote access/remote management agents. Disabling platform agents and services, such as performance monitoring (for example, NetIQ), antivirus (Cisco-verified McAfee services), intrusion detection, and remote management services, ensures that you do not encounter issues that are associated with these services.
This document provides procedures for disabling Cisco-verified McAfee antivirus services only. If you need assistance with disabling other services or applications, refer to the corresponding documentation that accompanies the product.
To disable the McAfee antivirus services, perform the following tasks:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Caution
Caution
Run the Cisco CallManager Upgrade Assistant Utility (Strongly Recommended)
Tip
The reboot may cause call-processing interruptions.Item Needed: Web download of utility
Run the Cisco CallManager Upgrade Assistant Utility to verify that your server is in a healthy state before the upgrade. The document that posts next to the utility on the web provides detailed information about the utility. To obtain the utility and the document, perform the following procedure:
Procedure
Step 1
Step 2
The Cisco CallManager 3.3 software page displays.
Step 3
Step 4
Upgrading the Cisco CallManager 3.1 or 3.2 Publisher Database Server
Table 6 includes the entire upgrade process on the publisher database server if you do not need to replace server.
Table 6 Required Upgrade Tasks for the Publisher Database Server
Verify that you have removed all servers in the cluster from the NT Domain or Microsoft Active Directory Domain.
Depends on the size of the cluster
Verify that you have manually disabled and stopped all platform agents and Cisco-verified applications (Cisco AVVID Partner Applications) that run on the servers in the cluster. Reboot the server.
Disabling and stopping platform agents and services, such as performance monitoring (for example, NetIQ), antivirus (Cisco-approved McAfee services), intrusion detection, and remote management services, ensures that the upgrade does not encounter issues that are associated with these services.
20 minutes
Manually remove previous versions of the Cisco IP Telephony Applications Backup, if possible.
Cisco recommends that you perform this task before you insert Cisco CallManager Publisher Upgrade Disk 1. If the backup utility installation detects a previous version of the utility, verify that no backup utility exists under the Add/Remove Programs option in Microsoft Windows. Then, continue the installation, even if an error message states that a previous version is detected.
Note
5 minutes
Manually install and configure Cisco IP Telephony Applications Server Backup, Version 3.5.53 (or later).
The Cisco CallManager Publisher Upgrade Disk 1 contains the utility that you must install.
About Backup Utility Configuration
When the installation software prompts you to configure the Cisco IP Telephony Applications Backup Utility, be aware that you must configure the publisher database server as the Backup Server, so data and configuration migration can occur.
About the Network Directory
If you choose a network directory as the destination for the backup server, the directory must be shared in Windows 2000. To share a directory, log in on that server, right-click the directory folder icon that you want to share, click Sharing..., click Share this folder, and then click OK.
About the Files That the Utility Backs Up
The Cisco IP Telephony Applications Backup Utility does not back up any operating system files except for Host/LMhost, if these files exist on the server. For a list of files that the utility backs up, refer to Using Cisco IP Telephony Applications Backup Utility, Version 3.5.53 (or later). To obtain the latest version of the document, see Table 1.
15 minutes
Manually back up the data that is on the publisher database server to either a network directory or local tape drive.
Consider the following information before you back up the server:
About the Backup Utility Version
To back up the data, you must use Cisco IP Telephony Applications Backup Utility, Version 3.5.53 or later, with this release of Cisco CallManager.
About Data Deletion
Do not back up the data to a local directory; the operating system installation erases all data that is stored on the local directory.
About Temporary Disk Space
If the server does not have enough temporary disk space to complete the backup, the backup fails.
About Data Preservation
Only data that is contained on the publisher database server restores.
For example, if Cisco Trivial File Transfer Protocol (TFTP) does not reside on the publisher database server, the restoration at the end of the upgrade erases all customized TFTP information, such as specific phone or gateway loads. If you want to retain this information, you must reconfigure the system, so the loads exist on the publisher database server, or you must manually save this data before the restoration.
After the backup, verify that no errors exist. Failure to successfully troubleshoot any problems could cause a total loss of data.
Tip30 to 60 minutes, depending on the size of the Cisco CallManager and Call Detail Record (CDR) database
After you verify that the backup completed successfully, verify that the dbname.ini and backup.ini files exist. Copy the files to the network directory or tape device where the MCS.sti file is stored.
5 minutes
Run Cisco CallManager Upgrade Assistant Utility 3.3(4) on all servers in the cluster.
You must perform this task on one server in the cluster at a time, beginning with the publisher database server.
See the "Run the Cisco CallManager Upgrade Assistant Utility (Strongly Recommended)" section.
1 to 20 minutes per server
If the server supports drive removal, remove a drive, insert a replacement drive, and mirror the drives.
See the Removing a Drive, Inserting a Replacement Drive, and Drive Mirroring (Strongly Recommended).
15 to 60 minutes, depending on the server type
Using the Cisco-provided operating system disks (Cisco IP Telephony Server Operating System Hardware Detection Disk and Cisco IP Telephony Server Operating System Installation and Recovery Disk), install operating system version 2000.2.4 or later.
You must install Cisco-provided operating system 2000.2.4 or later via the Same Server Recovery method.
If you are currently running Cisco-provided operating system version 2000.2.4 or later, you must install the operating system again by using same server recovery method with disks that ship with this version of Cisco CallManager.
You cannot upgrade to Cisco-provided operating system version 2000.2.4 (or later) from a previous version of the operating system.
About Removing Drives
After you verify that you have a good backup of data, you can remove a drive to save configured data; however, you must insert a replacement drive into the server before you begin the operating system procedures.
Before you begin the operating system installation, make sure that you have all drives in the server and verify that the drives are functional. For example, insert two drives for the MCS-7835 and four drives for the MCS-7845.
You must also remove additional hard drives from the server. Neglecting to perform these tasks causes the failure of the Cisco CallManager installation and the loss of data/configuration settings from drive mirroring.
About Name Resolution
After installing the operating system and before installing Cisco CallManager, you must configure name resolution for the backup location.
About NT and Microsoft Active Directory Domains
Cisco requires that you remove and do not add any servers to the NT Domain or the Microsoft Active Directory Domain until you complete all installation procedures on all servers in the cluster. The installation fails if you do not perform this task.
About Data Recovery
Make sure that you choose Same Server Recovery during the operating system installation. Choosing this option ensures that the server retains the current network configuration data.
About Passwords
Make sure that you enter an Administrator password at the end of the operating system installation. If you leave the Administrator password blank, you cannot install Cisco CallManager on the server.
Ensure that this password is the same on every server in the cluster.
About Operating System Service Releases
Cisco strongly recommends that you do not install any operating system service releases until you complete the upgrade on every server in the cluster.
45 to 75 minutes, depending on the server type
Use Cisco IP Telephony Server Operating System OS/BIOS Upgrade Disk that ships with Cisco CallManager to upgrade the Cisco-provided operating system to version 2000.2.5 (or later).
Before you perform the upgrade, be sure to read the operating system readme information that is posted on the operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site at http://www.cisco.com/public/sw-center/sw-voice.shtml.
45 to 75 minutes, depending on the server type
Download and install the latest Cisco IP Telephony Server Operating System service release (2000-2-5sr2 or later). (Required)
The operating system service releases post on the voice products operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site.
For installation instructions, refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, go to Table 1.
15 minutes, depending on the Internet connection
Download and install the latest OS-related security hotfixes, if any. (Recommended)
The operating system related security hotfixes post on the voice products operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site.
Refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, go to Table 1.
5 minutes
Use Cisco CallManager Installation and Recovery Disk to install Cisco CallManager.
Microsoft SQL Server 2000, Microsoft SQL Server 2000 Service Pack 3a (or later), and DC Directory automatically install when you install Cisco CallManager via the disk.
About Configuring Name Resolution on the Backup Location
After installing the operating system installation and before installing Cisco CallManager, you must configure name resolution for the backup location.
About Data Restoration
The disk that you insert for the Cisco CallManager installation also restores the data that you backed up by using backup utility version 3.5.53 or later.
The restoration retains all TCP/IP configuration settings, but you lose all NIC settings that you have manually configured; for example, hard-coded Speed/Duplex settings. You must manually configure these settings after you install all servers in the cluster.
Only the data that is contained on the publisher database server restores to the destination that you specify.
For example, if Cisco TFTP does not reside on the publisher database server, the restoration at the end of the upgrade erases all customized TFTP information, such as specific phone or gateway loads. If you want to retain this information, you must reconfigure the system, so the loads exist on the publisher database server, or you must manually save this data before the restoration. Be aware that the restoration launches automatically.
During the restoration, if your location is a network directory, you must click the Browse button and manually highlight the MCS.sti file. Failure to highlight the file causes the upgrade to fail.
About Installed Services
All services that display in the Service Activation window of Cisco CallManager Serviceability install, but only the services that you configured prior to the upgrade activate after the upgrade completes and the server reboots.
If you want to run additional services, you must activate the service on each server in which you want the service to run. You must perform this task by browsing into Cisco CallManager Serviceability from a PC that does not have Cisco CallManager installed. For more information on how to activate services and for service considerations, refer to the Cisco CallManager Serviceability Administration Guide.
Cisco CallManager places services in an inactive state until the upgrade completes.
Restoring the Data— up to 70 minutes, depending on the size of the Cisco CallManager and CDR database
Installing Cisco CallManager—45 to 90 minutes
To successfully upgrade the publisher database server, you must perform all procedures exactly as stated in this document. To migrate data and upgrade the publisher database server, perform the following procedures in the indicated order:
Tasks That You Perform to Upgrade the Cisco CallManager 3.1 or 3.2 Publisher Database Server
2.
4.
6.
7.
8.
9.
11.
12.
13.
Remove the System From the NT Domain or Microsoft Active Directory Domain and Reboot the Server (Required, If Configured)
Tip
The reboot may cause call-processing interruptions.
Disable and Stop Third-Party, Cisco-Verified Applications and Reboot the Server (Required)
Tip
The reboot may cause call-processing interruptions.See the "Disable and Stop Third-Party, Cisco-Verified Applications and Reboot the Server (Required)" section.
Install and Configure Cisco IP Telephony Applications Server Backup Utility, Version 3.5.53 or Later (Required)
Caution
Item Needed: Cisco CallManager Publisher Upgrade Disk 1 or the backup utility that is available on the web
Perform the following procedure to remove the existing backup utility, install the new backup utility, and configure the utility:
Procedure
Step 1
a.
b.
c.
d.
e.
Step 2
Tip
To install via disk, continue with Step 3.Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Note
Step 9
Step 10
Step 11
a.
b.
Step 12
Step 13
Step 14
The installation occurs, as indicated in the status bar. Do not click Cancel. Continue to wait while the installation completes.
Step 15
a.
b.
c.
Caution
Step 16
Step 17
Step 18
To configure a network directory, see Step 19 through Step 22.
To configure a tape device, see Step 23 through Step 25.
Caution
To Configure a Network Directory
If you choose a network directory as the destination for the backup server, the directory must be shared in Windows 2000. To share a directory, log in on that server, right-click the directory folder icon that you want to share, click Sharing..., click Share this folder, and then click OK.
Step 19
Step 20
Step 21
Step 22
To Configure a Tape Device
Step 23
Step 24
Step 25
Step 26
Step 27
Step 28
Step 29
Step 30
Back Up Existing Data (Required)
Caution
You must back up the publisher database before you install the operating system. Perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
You can obtain the StiBack.log from C:\Program Files\Common Files\Cisco\Logs on the backup server. If you receive the following error messages or other error messages in the log file, the process did not successfully back up the data:
•
•
•
•
•
•
Step 5
Caution
Verify That the dbname.ini and backup.ini Files Exist for the STI_DATA Drive; Copy the Files to the Network Directory Where the MCS.sti File Exists (Strongly Recommended)
Caution
The files exist in the Recover directory on the STI_Data drive. Depending on the system, these files exist on the D: or E: drive (on the Cisco ICS 7750, the C: drive). For example, the files may exist on the publisher database server in one of the following locations: D:\recover\<name of file> or E:\recover\<name of file>.
After you locate the files, Cisco recommends that you copy the files to the network directory where the MCS.sti file exists.
Run the Cisco CallManager Upgrade Assistant Utility on All Servers in the Cluster (Strongly Recommended)
Tip
The reboot may cause call-processing interruptions.See the "Run the Cisco CallManager Upgrade Assistant Utility (Strongly Recommended)" section.
Removing a Drive, Inserting a Replacement Drive, and Drive Mirroring (Strongly Recommended)
Item Needed: Newly Purchased Hard Drive
You cannot remove a drive if you have the MCS-7815, MCS-7820, MCS-7822, MCS-7825, Cisco ICS 7750, or the customer-provided IBM xSeries 330 server.
After you verify that you have a good backup of the data, you can remove a drive to save configured data; however, you must insert a replacement drive into the server before you begin the operating system procedures. This task may require that you purchase a new drive.
This process may take between 30 minutes to 60 minutes, depending on the size of the drive.
Perform the following steps to remove a drive, to insert a replacement drive, and to mirror the drives:
Procedure
Step 1
Step 2
For the MCS-7845, remove the drives from Slot 0 and Slot 2.
Step 3
Cisco MCS
Step 4
a.
Note
b.
When prompted, press F1 to continue.
c.
Note
d.
e.
f.
After the mirroring process completes in Slot 0, insert the next drive into Slot 2. The mirroring process launches automatically after you insert the drive into Slot 2.
IBM xSeries Server
Step 5
a.
b.
c.
Install the Operating System by Using Same Server Recovery (Required)
Item Needed: Cisco IP Telephony Server Operating System Hardware Detection Disk
Before you install the operating system, carefully review Table 2.
Tip
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Caution
If the server does not belong to a Workgroup, join a Workgroup during this operating system installation. The Cisco CallManager installation requires joining a workgroup.
Likewise, to successfully complete the upgrade, you must configure Domain Name System (DNS) or Windows Internet Name Service (WINS), if you have not already done so.
Step 8
Step 9
a.
b.
Step 10
Step 11
If your server was configured for DNS or WINS, the IP addresses of the primary DNS and WINS servers display. If DNS or WINS was not configured, empty IP addresses fields display.
Click Next.
Step 12
a.
b.
For example:
172.16.0.10 dallascm1c.
d.
Note
Step 13
Step 14
Step 15
Step 16
Windows 2000 setup begins and takes about 10 minutes to complete. Do not power down the server or press any keys during setup.
Caution
Step 17
If you leave the password fields blank, you cannot install any Cisco IP telephony applications on the server.
Tip
Step 18
Caution
Upgrade the Operating System to Cisco-Provided Version 2000.2.5 (or Later) (Required)
Before you perform the upgrade, be sure to read the operating system readme information that is posted on the operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site at http://www.cisco.com/public/sw-center/sw-voice.shtml.
Perform the upgrade on the publisher database server first; complete the Cisco CallManager upgrade on the publisher database server before you upgrade the operating system on the subscriber servers.
Download and Install the Latest Cisco IP Telephony Server Operating System Service Release (Required)
Download and install the latest Cisco IP Telephony Server Operating System service release (2000-2-5sr2 or later). The operating system service releases post on the voice products operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site.
For installation instructions, refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, see Table 1.
Download and Install the Latest OS Related Security Hotfixes (If Any) (Recommended)
The operating system related security hotfixes post on the voice products operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site.
For installation instructions, refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, see Table 1.
Install Cisco CallManager (Required)
Item Needed: Cisco CallManager 3.3 Installation and Recovery Disk
Perform the following procedure to install the directory, the database, and Cisco CallManager via disk. The disk also prompts you to restore the data that the backup utility stored to a network directory or tape device.
Caution
Procedure
Step 1
The installation process automatically starts.
To acknowledge that you disabled/uninstalled Cisco-verified applications, click Yes.
Note
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.
Step 7
Step 8
Caution
Step 9
Step 10
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: { } . < > : ? / | \ ` ~ ! @ $ ^ & * ( ) _ - +.
Step 11
a.
b.
c.
Step 12
The status bar indicates the progression of the installation. Continue to wait while the installation completes.
Microsoft SQL Server 2000, Microsoft SQL Server 2000 Service Pack 3a (or later), and DC Directory install. This process takes 15 to 20 minutes.
Step 13
Step 14
Step 15
Step 16
Step 17
a.
If you chose a network directory, you must browse to and manually highlight the MCS.sti file. Failure to highlight the file causes the upgrade to fail.
b.
c.
d.
Step 18
a.
b.
c.
d.
Step 19
The utility restores the files to the server where you want the utility to send the files.
Step 20
•
•
•
•
Step 21
The Cisco CallManager installation takes approximately 45 to 90 minutes. Although you may see no indication that the installation is progressing, continue to wait while the installation completes.
Step 22
Step 23
Step 24
Step 25
Step 26
Step 27
If you have subscriber servers that you need to install, see the "Upgrading Cisco CallManager 3.1 or 3.2 Subscriber Servers" section.
Back Up the Current Database (Required)
Caution
For procedures and more information on backing up the database, refer to Using the Cisco IP Telephony Backup Utility, Version 3.5.53 (or later).
Upgrading Cisco CallManager 3.1 or 3.2 Subscriber Servers
To complete installation tasks on each subscriber server, you should allot 60 to 120 minutes, depending on the server type. Consider the time that it takes to perform pre-/post upgrade tasks.
Table 7 describes how to upgrade the subscriber database servers.
Table 7 Required Upgrade Tasks for the Subscriber Servers
Step 1
Perform pre-upgrade tasks.
See the following sections:
•
Step 2
Verify that you removed all servers from the NT or Microsoft Active Directory Domain.
Step 3
Verify that you have disabled and stopped all third-party, Cisco-verified applications that run on the server. Make sure that you have rebooted the server.
See the "Disable and Stop Third-Party, Cisco-Verified Applications and Reboot the Server (Required)" section.
Step 4
Run the ServPrep utility.
Step 5
Using the Cisco-provided operating system disk, install Cisco-provided operating system 2000.2.4 (or later).
Caution
See the "Install the Operating System by Using Same Server Recovery (Required)" section. Consider the same guidelines for the subscriber servers that you used for the publisher database server.
Step 6
Use Cisco IP Telephony Server Operating System OS/BIOS Upgrade Disk that ships with Cisco CallManager to upgrade the Cisco-provided operating system to version 2000.2.5 (or later).
Before you perform the upgrade, be sure to read the operating system readme information that is posted on the operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site at http://www.cisco.com/public/sw-center/sw-voice.shtml.
Step 7
Download and install the latest Cisco IP Telephony Server Operating System service release (2000-2-5sr2 or later). (Required)
The operating system service releases post on the voice products operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site.
For installation instructions, refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, go to Table 1.
Step 8
Download and install the latest OS-related security hotfixes, if any. (Recommended)
The operating-system-related security hotfixes post on the voice products operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site.
Refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, go to Table 1.
Step 9
Task That You Perform Serially
Perform the Cisco CallManager installation on one server at a time.
See the "Installing Cisco CallManager on Subscriber Database Server(s)" section.
Caution
Step 10
Task That You Should Perform Serially
After each subscriber upgrade, verify that the subscriber server pulled the subscription from the publisher database server.
See the "Verifying and Reinitializing Subscriber Connections" section.
Step 11
After you complete the installation on all servers in the cluster, perform post-upgrade tasks.
Run the ServPrep Utility (Required)
Item Needed: Cisco CallManager Subscriber Upgrade Disk 1
Before you install Cisco CallManager, you must run the ServPrep Utility and install Cisco-provided operating system version 2000.2.4 or later by using the Cisco-provided operating system disks.
The ServPrep utility, which you run on subscriber servers, updates the network configuration by creating the file, STISys.inf, which contains network information. The utility saves TCP/IP settings, but you lose manually configured NIC settings; for example, hard-coded Speed/Duplex settings. After you complete the installation on all servers in the cluster, you must manually configure previous NIC settings.
Caution
Procedure
Step 1
Step 2
Step 3
Step 4
Installing Cisco CallManager on Subscriber Database Server(s)
Item Needed: Cisco CallManager Installation and Recovery Disk
After you install Cisco 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
The Preparing to Install window displays while the installation program copies files to your server. This process takes approximately 10 minutes. Do not click Cancel.
Step 3
Step 4
Step 5
Cisco automatically populates the product key fields with the product key that you entered during the operating system installation. Click Next.
Note
Step 6
Step 7
a.
b.
Caution
c.
Caution
Step 8
This password must match the Windows administrator password that is used on the publisher database server.
Click Next.
Step 9
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: { } . < > : ? / | \ \Q ~ ! @ $ ^ & * ( ) _ - +.
This password must match the Private Password Phrase that you entered on the publisher database server.
Step 10
a.
This password must match the SA password that you entered on the publisher database server.
b.
c.
Step 11
Continue to wait while the installation completes.
Step 12
Step 13
Step 14
Step 15
Step 16
Upgrading From Cisco CallManager 3.3(3) (If You Are Not Replacing Hardware)
Tip
Upgrading the Cisco CallManager 3.3(3) Publisher Database Server
Review Table 8, which includes the upgrade tasks, designated time to perform the task, and the location where you obtain the procedure:
Table 8 Recommended Upgrade Tasks for the Publisher Database Server
Verify that you have removed all servers in the cluster from the NT Domain or Microsoft Active Directory Domain.
Depends on the size of the cluster
Verify that you have manually disabled and stopped all platform agents and Cisco-verified applications (Cisco AVVID Partner Applications) that run on the servers in the cluster. Reboot the server.
Disabling and stopping platform agents and services, such as performance monitoring (for example, NetIQ), antivirus (Cisco-approved McAfee services), intrusion detection, and remote management services, ensures that the upgrade does not encounter issues that are associated with these services.
Tip20 minutes
Manually install and configure the CIPT Backup and Restore System (BARS), version 4.0(2) (or later).
If you have not already done so, Cisco recommends that you install and configure the backup utility on the publisher database server.
The CIPT Backup and Restore System (BARS) does not back up any operating system files except Host/LMhost, if these files exist on the server. For a list of files that the utility backs up, refer to Cisco IP Telephony Backup and Restore System (BARS) Administration Guide. To obtain the most recent version of this document, see Table 1.
15 minutes
Using the Backup and Restore System (BARS), version 4.0(2) (or later), manually back up the Cisco CallManager data to either a network directory or tape drive.
For information on backing up your system, refer to Cisco IP Telephony Backup and Restore System (BARS) Administration Guide. To obtain the most recent version of this document, see Table 1.
Tip30 to 60 minutes, depending on the size of the Cisco CallManager and Call Detail Record (CDR) database
Run the Cisco CallManager Upgrade Assistant Utility on all servers in the cluster.
You must perform this task on one server in the cluster at a time, beginning with the publisher database server.
See the "Run the Cisco CallManager Upgrade Assistant Utility (Strongly Recommended)" section.
1 to 20 minutes for the publisher database server; 1 to 5 minutes for the subscriber server
If the server supports drive removal, remove a drive from the server to save your data and configuration.
15 to 60 minutes, depending on the server type
Use the operating system upgrade CD-ROM or the operating system upgrade web download to upgrade the operating system to Cisco-provided version 2000.2.5 (or later).
Before you perform the upgrade, be sure to read the operating system readme information that is posted on the operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site at http://www.cisco.com/public/sw-center/sw-voice.shtml .
45 to 75 minutes per server, depending on the server type
Download and install the latest Cisco IP Telephony Server Operating System service release (2000-2-5sr2 or later). (Required)
The operating-system-service releases post on the voice products operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site.
For installation instructions, refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, go to Table 1.
15 minutes
Download and install the latest OS-related security hotfixes, if any. (Recommended)
The operating system related security hotfixes post on the voice products operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site.
For installation instructions, refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, go to Table 1.
Verify that you installed Microsoft SQL Server 2000, Service Pack 3a (or later).
Refer to the readme documentation that accompanies the service pack.
20 minutes
Upgrade Cisco CallManager.
See the "Inserting the Disk or Downloading the Web File" section.
45 to 90 minutes per server, depending on the server type
Upgrading the Cisco CallManager 3.3(3) Subscriber Server(s)
Table 9 describes how to upgrade the subscriber servers.
Table 9 Recommended Upgrade Tasks for the Subscriber Servers
Perform pre-upgrade tasks.
See the following sections:
•
Verify that you removed all servers from the NT or Microsoft Active Directory Domain.
Verify that you have disabled and stopped all third-party, Cisco-verified applications that run on the server. Make sure that you have rebooted the server.
See the "Disable and Stop Third-Party, Cisco-Verified Applications and Reboot the Server (Required)" section.
Optional Task
Run the ServPrep utility.
You can only run the utility via Subscriber Upgrade Disk 1. Cisco does not provide this utility on the web.
Use the operating system upgrade CD-ROM or the operating system upgrade web download to upgrade the operating system to Cisco-provided version 2000.2.5 (or later).
Caution
If the server runs 2000.2.3, you can upgrade the operating system via disk or via the web. Refer to Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of this document, see Table 1.
Download and install the latest Cisco IP Telephony Server Operating System service release (2000-2-5sr2 or later). (Required)
The operating system service releases post on the voice products operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site.
For installation instructions, refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, see Table 1.
Download and install the latest OS-related security hotfixes, if any. (Recommended)
The operating-system-related security hotfixes post on the voice products operating system cryptographic software site. You can navigate to the site from the Cisco CallManager software site.
For installation instructions, refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, see Table 1.
Verify that you installed Microsoft SQL Server 2000, Service Pack 3a (or later).
For information on how to verify install the service pack, refer to the readme documentation that accompanies the service pack.
Caution
Task That You Should Perform Serially
Perform the Cisco CallManager upgrade on one server at a time.
Caution
TipSee the "Inserting the Disk or Downloading the Web File" section.
Task That You Should Perform Serially
After each subscriber upgrade, verify that the subscriber server pulled the subscription from the publisher database server.
See the "Verifying and Reinitializing Subscriber Connections" section.
After you complete the installation on all servers in the cluster, perform additional post-upgrade tasks.
Tasks for the Cisco CallManager 3.3 Upgrade
This section describes how to upgrade Cisco CallManager only. To upgrade Cisco CallManager, perform the following procedure:
Inserting the Disk or Downloading the Web File
Items Needed: Cisco CallManager 3.3(4) Installation and Recovery Disk or web download of Cisco CallManager 3.3(4)
Perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
•
•
Using the Disk
Step 8
Tip
Step 9
Using the Web File
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
The extraction window opens.
Step 16
Upgrading Related Cisco CallManager Services and Detecting the Server
Perform the following procedure to upgrade Cisco CallManager:
Step 1
Step 2
Step 3
Tip
If you are upgrading Cisco CallManager via the web and just installed the service pack, you must double-click the executable after the service pack installs and the server reboots; continue to wait while the Cisco IP telephony application prepares to install.Step 4
Step 5
Step 6
Step 7
The status window displays. Do not click Cancel.
Step 8
Step 9
Tip
Performing Post-Upgrade Tasks
After you complete the upgrade, perform the appropriate tasks as described in Table 10:
Table 10 Post-Upgrade Tasks
Enable all Cisco-verified applications/program agents that you previously disabled on the server.
Refer to the following information:
•
If you have not already done so, verify that the subscriber servers pulled the copy of the database.
See the "Verifying and Reinitializing Subscriber Connections" section.
Verify that all services started.
Verify that you can make internal calls.
Verify that you can place and receive a call across gateways.
See the "Verifying Services, Patches, and Hotfixes" section.
See the "Viewing the Component Versions That Are Installed on the Server" section.
Caution
If you have CRS and Cisco CallManager installed on the same server, complete the upgrade by referring to the appropriate documentation.
See the "How does a co-resident upgrade work if I have CRS installed with Cisco CallManager?" section.
After you complete the Cisco CallManager upgrade on every server in the cluster, reinstall all Cisco-verified applications and all plugins that were previously installed on the server.
For example, if you have integrated your enterprise directory with Cisco CallManager, you must reinstall the Cisco Customer Directory Configuration Plugin on all servers in the cluster after the upgrade, starting with the publisher database server. Reinstalling the plugin populates your enterprise directory with any additional schema extensions and data entries that Cisco CallManager needs.
Refer to the appropriate documentation that accompanies the applications.
Upgrade Cisco TAPI, Cisco JTAPI, Cisco TSP (for the voice-messaging system), and the Cisco TSP for Cisco SoftPhone.
See the following sections for more information:
•
You may need to perform additional configuration tasks for the Cisco IP telephony products to work.
See the "What additional information should I know before I upgrade?" section.
Verify that all Cisco IP telephony applications that are integrated with Cisco CallManager run properly. If you need to do so, upgrade the Cisco IP telephony applications that are integrated with your Cisco CallManager system.
Refer to the Cisco CallManager Compatibility Matrix by clicking the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm
If the application is compatible with this version of Cisco CallManager, refer to the appropriate Cisco IP telephony application documentation.
If you want to use Norton AntiVirus, install the application and perform post-installation tasks.
Refer to Using Symantec/Norton AntiVirus with Cisco CallManager.
The locale, English_United_States, installs automatically on the server. To upgrade existing locales or to add additional locales to the server, install the Cisco IP Telephony Locale Installer.
Note
Click the following URL to obtain the locale and the installer documentation:
http://www.cisco.com/pcgi-bin/tablebuild.pl/callmgr-locale-33
You must configure the Network Interface Card (NIC) Speed and Duplex settings of the Cisco CallManager server to match the configuration of the LAN switch port to which the server is connected. Failure to match these settings between the server and switch may cause degraded network performance and unexpected errors to occur. Contact your network administrator or see the Cisco IOS configuration documentation to determine your current settings of the LAN switch port to which the Cisco CallManager NIC is connected.
Some administrators have found that the 100/Full setting works well.
Review the post-installation tasks section of the Cisco CallManager installation document for additional tasks/requirements that apply to your system; for example, configuring DNS.
Review operating system recommendations in the document, Installing the Operating System on the Cisco IP Telephony Application Server. To obtain the most recent version of the document, see Table 1.
Refer to Installing Cisco CallManager Release 3.3(4). To obtain the most recent version of the document, see Table 1.
Ongoing System Management Practice
Back up your Cisco CallManager data.
Refer to Using the Cisco IP Telephony Applications Backup Utility, Version 3.5.53 (or later). To obtain the most recent version of this document, see Table 1.
Ongoing System Management Practice
Verify the version of hotfixes and service packs that are installed on the server.
Download the latest hotfixes, service packs, and Cisco CallManager service release that are available on the web.
This task requires a reboot of the server after you install the files.
Verifying Services, Patches, and Hotfixes
Tip
Enabling Cisco-Verified McAfee Antivirus Services
To enable the Cisco-verified McAfee antivirus services, perform the following tasks:
Procedure
Step 1
a.
b.
c.
d.
e.
f.
Step 2
Verifying and Reinitializing Subscriber Connections
If the connections between the publisher database server and the subscribers within a cluster are broken for any reason, you cannot replicate the database to the subscribers.
Verifying the Status of the Subscription
In the Enterprise Manager, a red X icon next to the subscription 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 AVVID Partner or the Cisco Technical Assistance Center (TAC).
Verifying Services, Patches, and Hotfixes
Perform the following tasks:
•
•
•
About Services
Open Cisco CallManager Serviceability and verify that all migrated services are running. To review service activation procedures and service recommendations, refer to the Cisco CallManager Serviceability Administration Guide and the Cisco CallManager Serviceability System Guide.
Caution
About Microsoft Patches and Hotfixes
Refer to the file-specific readme document, Cisco IP Telephony Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco IP Telephony Applications Server. To obtain the most recent version of these documents, see Table 1.
About Cisco CallManager Service Releases
After you install this version of Cisco CallManager on all servers in the cluster, Cisco strongly recommends that you install the latest Cisco CallManager service release on all servers in the cluster. These service releases provide bug fixes for your system.
Be aware that Cisco CallManager service releases are cumulative. Cisco rolls these bug fixes into the next Cisco CallManager release.
Tip
To obtain the latest Cisco CallManager service release, perform the following procedure:
Step 1
Step 2
The Cisco CallManager 3.3 software site displays.
Step 3
The readme file provides procedures, caveats, and descriptive information for installing the files.
Step 4
Viewing the Component Versions That Are Installed on the Server
The mcsver.exe program reports the current version of all installation components, including such components as the operating system. Be aware that Cisco does not report the actual Cisco CallManager version through this program. Recognize that 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 with the Cisco IP Telephony Server Operating System Hardware Detection disk.
The version for stiOSUpg.exe equals the version of the operating system upgrade that you last ran either via disk or via the web. When Cisco updates and releases the Cisco IP Telephony Server Operating System OS/BIOS Upgrade disk (Disk 2), the version of stiOSUpg changes.
Perform the following procedure to view the component versions that are installed on the server:
Procedure
Step 1
C:\utils\mcsver
Step 2
Upgrading TAPI, JTAPI, and Cisco Telephony Service Provider (TSP)
You must upgrade the Telephony Application Programming Interface and Java Telephony Application Programming Interface (TAPI/JTAPI) client software on any application server or client workstation on which TAPI/JTAPI applications are installed. If you do not upgrade the TAPI/JTAPI client, your application will fail to initialize.
The following information applies if you have integrated a Cisco Unity system with Cisco CallManager. TSP makes the voice-mail ports available to Cisco Unity. To ensure that Cisco Unity integrates properly with Cisco CallManager, you may need to upgrade the TSP that is integrated with the voice-messaging system. To ensure that you upgrade to the appropriate TSP release, refer to the Cisco CallManager Compatibility Matrix.
Upgrading the Cisco TAPI/TSP for Cisco SoftPhone
Perform the following procedure to upgrade the Cisco SoftPhone TAPI/TSP to the version that is stated in the Cisco CallManager Compatibility Matrix.
Procedure
Step 1
Tip
Step 2
Step 3
Step 4
Step 5
Using the Cisco CallManager Music On Hold Disk or Download
Note
When you initially install Cisco CallManager on your server, a default music on hold audio file sample automatically installs for customer use. To increase your music on hold (MOH) selection, you may download one of the following two files via the web:
•
•
For information on the MOH feature, refer to the latest version of the Cisco CallManager Administration Guide and the latest version of the Cisco CallManager System Guide.
As a Cisco CallManager user, you can use any disk/file with music on hold. Because of licensing restrictions, you must not distribute the Cisco CallManager Music on Hold disk/files to anyone else, and you must not use the files for any other purpose.
Reverting to the Previous Configuration After an Upgrade Attempt
In the unlikely event of an upgrade failure, or if you prefer an earlier version of Cisco CallManager, perform the following steps to return the Cisco IP Telephony Applications Server to the configuration that was in effect prior to the upgrade.
Reconfiguring If You Did Not Pull a Drive Before the Upgrade
Tip
This procedure assumes that you have a good backup file (MCS.sti file) on a tape device or network directory. For a list of files that the utility backs up and for more information on the MCS.sti file, refer to Using Cisco IP Telephony Applications Backup Utility, Version 3.5.53 (or later). To obtain the latest version of the document, see Table 1.
Perform the following procedure:
Procedure
Step 1
Publisher Database Server
Step 2
You must perform this task by using the Cisco-provided disks that shipped with Cisco CallManager Release 3.3(4).
Step 3
Do not install or configure the backup utility that automatically displays during the installation.
Step 4
Step 5
Note
Step 6
Subscriber Server(s)
Step 7
You must perform this task by using the Cisco-provided disks that shipped with Cisco CallManager Release 3.3(4).
Step 8
Do not install or configure the backup utility that automatically displays during the installation.
Step 9
You install and configure the backup utility on the subscriber when a Cisco IP telephony application, for example, CRS, exists on the subscriber server.
Reconfiguring If You Removed a Drive Before the Upgrade
This process may take from 15 minutes to 60 minutes, depending on the size of the drive.
Perform the following procedure:
Procedure
Step 1
Step 2
Note
Step 3
Step 4
Cisco MCS
Step 5
a.
Note
b.
c.
d.
e.
f.
g.
IBM xSeries Server
Step 6
Step 7
Step 8
Step 9
Step 10
Processing begins.
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Note
This process takes about 35 to 40 minutes, depending on the server.
Step 17
Step 18
Reverting the Hard Drive After Drive Mirroring Completes
If you want to revert a hard drive after drive mirroring and you have made changes that affect the domain trust relationship, you must remove the server from the domain and then add it back to the domain. You must have rights to join the server to the domain before you perform this procedure.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Reverting Upgraded Cisco IP Telephony Applications After You Revert Cisco CallManager
After you revert the entire cluster to a previous version of Cisco CallManager, you must revert integrated Cisco IP telephony applications. You must revert these integrated applications to the version that is compatible with the reverted Cisco CallManager. To revert the application, perform the following procedure:
Procedure
Step 1
Step 2
Tip
Step 3
Step 4
•
•
Step 5
Step 6
Error Messages
The following error messages may display in dialog boxes (not the log file) during the upgrade. You can obtain and review the log file, ccminst <data/time stamp>.log, from C:\Program Files\Common Files\Cisco\Logs.
Table 11 Installation Error Messages
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 error message displays when you install Cisco 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 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 you entered do not match.
This error 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.
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 CallManager installation. All other installed third-party applications must be uninstalled before proceeding with the 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 AVVID (Architecture for Voice, Video and Integrated Data) Partner Applications] or platform agents that are installed on the server, you must disable/uninstall and stop the services.
Because the <BUILDVERSION> of this Cisco CallManager MSI package is not compatible with the Cisco CallManager setup file (ccmsetup.exe), make sure that you are using the ccmsetup.exe that was distributed with this version of Cisco CallManager. The installation will now abort.
This message indicates that the MSI package is not compatible with the Cisco CallManager setup file.
Use the ccmsetup.exe file that was distributed with this version of Cisco CallManager.
You are attempting to upgrade Cisco CallManager <InstalledBUILDVERSION> to version <UpgradeBUILDVERSION>. Direct upgrades from this version of Cisco CallManager are not supported. You must first upgrade to a compatible Cisco CallManager version before upgrading to this version. The installation will now abort.
You tried to upgrade from a version other than Cisco CallManager 3.1, Cisco CallManager 3.2, or Cisco CallManager 3.3(3).
Upgrade to Cisco CallManager 3.1, Cisco CallManager 3.2, or Cisco CallManager 3.3(3) before attempting to upgrade to Cisco CallManager 3.3(4).
You are attempting to upgrade Cisco CallManager <InstalledBUILDVERSION> to version <UpgradeBUILDVERSION>. Upgrades from this version of Cisco CallManager require using the Same-Server Recovery method. Please refer to the Upgrading Cisco CallManager Release 3.3(4) documentation for more information. The installation will now abort.
You attempted upgrade directly from Cisco CallManager 3.2 to Cisco CallManager 3.3(4) without following the Same Server Recovery procedures.
You must perform a Same Server Recovery by using the operating system disks that ship with this version of Cisco CallManager to install operating system.
For publisher servers, see the "Install the Operating System by Using Same Server Recovery (Required)" section.
For subscriber servers, see the "Install the Operating System by Using Same Server Recovery (Required)" section.
Error opening MSI package
Cisco CallManager Setup cannot find the MSI package.
This message displays if you encounter a media problem; insert the disk again.
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. For information, refer to the Upgrading Cisco CallManager guide.
You attempted an upgrade with a Cisco CallManager web file and do not have enough free disk space.
Make 3.0 gigabytes of disk space available and restart the installation program.
The installation program does not have enough disk space on the C drive to complete the installation. The installation program requires that you have 2.0 gigabytes of disk space available on your server. Make at least 2.0 gigabytes of disk space available and restart the installation. For information, refer to the Upgrading Cisco CallManager guide.
You attempted an upgrade With a Cisco CallManager CD and do not have enough free disk space.
Make 2.0 gigabytes of disk space available and restart the installation program.
The local security policy "Restrict CD-ROM access to locally logged-on user only" is enabled. This setting interferes with the Cisco CallManager installation. Please disable this setting using the Local Security Policy utility, reboot, and rerun the Cisco CallManager installation.
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 CallManager installation.
For more information, see the "Disabling the Restrict CD-ROM Access to Locally Logged-On User Only Security Policy" section.
Failure occurred trying to get DBNAME value from registry. Aborting Cisco CallManager installation.
The installation could not read DBNAME value from registry on the local machine.
Reboot the server and rerun the Cisco CallManager installation.
Failure occurred trying to validate the format of DBNAME value. Aborting Cisco CallManager installation.
The registry contains an invalid format of the DBNAME value. This error only occurs if you have manually modified this value.
Make sure that the DBNAME value is in the format CCM0xxx, where x stands for any digits.
This version of Cisco CallManager is currently installed.
This message displays when you attempt to install the same version of Cisco CallManager that is currently on the server.
Remove the disk from the drive.
This package has already been installed.
This message displays when you attempt to install the same version of Cisco CallManager again after a successful installation.
Remove the disk from the drive.
A newer version of this package has already been installed.
This message displays when you attempt to install a previous version of Cisco CallManager after a successful installation of a later version.
Remove the disk from the drive.
Cisco CallManager install did not complete successfully. Review the log file for more information.
The Cisco 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 CallManager installation package to the server.
Copy the complete installation package to the server and rerun the Cisco CallManager installation.
An unexpected error occurred.
An error occurred during the Cisco CallManager Setup.
Obtain and examine the log file.
An unexpected error occurred while constructing package name.
An error occurred during the Cisco 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.
Current OS version does not meet minimum requirements. Aborting Cisco CallManager install.
Cisco CallManager Release 3.3(4) requires Cisco-provided operating system version 2000.2.4 or later.
Refer to Cisco IP Telephony Operating System, SQL Server, Security Updates to review which versions are compatible for installation.
Installing Cisco CallManager using Terminal Services is not allowed. Install will now abort.
Cisco does not support Terminal Services for Cisco 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), see Table 1 to obtain the most recent version of the VNC documentation.
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 trying to determine if Cisco Directory install succeeded. Aborting Cisco CallManager install.
The DC Directory installation failed.
Obtain and examine the log file.
The Cisco 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 CallManager document.
The Cisco 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 "Disable and Stop Third-Party, Cisco-Verified Applications and Reboot the Server (Required)" section
The password of [X] does not match the password on the publisher [Y]. For details, review the log file [Z].
The username and/or password of the user installing Cisco 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 [X] against the publisher [Y]. For details, review the log file [Z].
During Subscriber installation, this error 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 [X]. For details, review the log file [Y].
During the subscribe server installation, one of the following problems occurred:
•
•
•
Do each of the following tasks:
•
•
•
Indexing directory data did not finish. After you complete the installation, review the log file. 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 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 CallManager installation failed to stop <list of services> service(s). Please reboot the server, manually stop the service(s), and rerun the Cisco 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 CallManager installation program.
The installation failed to verify the Cisco 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 installation, this error 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 database server and make sure that you entered the correct publisher database server name.
The Cisco CallManager version 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 CallManager version before you continue.
You attempted to install a different version of Cisco CallManager on the subscriber database server than you installed on the publisher database server.
Install the same version of Cisco CallManager on the subscriber database server that you installed on the publisher database server.
Failure occurred during the CallManager install. Please look at the CallManager install log file for detail. Aborting Cisco CallManager install.
The Cisco CallManager installation failed.
Obtain and examine the log file.
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.
Pending file operations are occurring. Reboot the server and then install Cisco CallManager.
Pending file operations are occurring.
Reboot the server and then install Cisco CallManager.
You are not logged on as `Administrator'. You must log in by using local Administrator user name and password to install Cisco 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 CallManager.
You do not have administrative privileges.
Log in to the server with an account that has administrative privileges.
You must install CallManager by double clicking CCMSetup.exe.
You tried to install Cisco CallManager by double clicking the msi file that is part of the Cisco CallManager package.
Double-click the CCMSetup.exe.
You must apply SQL 2000 Service Pack 3 (or later) before proceeding with this installation.
You did not install Microsoft SQL 2000 Service Pack 3.
Install Microsoft SQL 2000 Service Pack 3, and perform the Cisco CallManager upgrade.
The installation has 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 too restrictive for the Cisco CallManager installation to build critical NT Accounts during an upgrade. Failure to remove the server from the domain and add to a workgroup may cause upgrade errors, upgrade failures, or a total system failure, which includes a loss of data and a complete reinstallation of Cisco CallManager. Would you like to proceed?
The server exists in a domain.
Caution
This release of Cisco CallManager is not supported on this server model. The installation will now abort.
You cannot install this version of Cisco CallManager on this server.
Refer to the Cisco CallManager Compatibility Matrix for a list of servers on which you can install this version of Cisco CallManager. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm.
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 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 [x] against the publisher [y]. 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 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 [y]. 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.
Resolving Name Resolution Failures
Cisco 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
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:
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.comDisabling the Restrict CD-ROM Access to Locally Logged-On User Only Security Policy
If you receive the error 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 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
Replacing Servers During the Upgrade
This document assumes that Cisco CallManager is the only application that runs on the server. This document does not provide procedures for replacing co-resident servers where Cisco CallManager, Cisco Customer Response Solutions (CRS), and Cisco-verified, third-party applications are installed on the same server.
By using these procedures, you can replace the publisher database server only, a subscriber server only, multiple subscriber servers, or both the publisher database server and the subscriber server(s) during the upgrade. Unless otherwise indicated in the document, remember to perform all procedures serially; that is, on one server at a time.
Caution
Replacing the Cisco CallManager 3.1/3.2 Publisher Database Server During the Cisco CallManager 3.3 Upgrade
Caution
If you are performing installation procedures on a dead net, you must have network or media access to the backup file, MCS.sti file, or a tape drive and the tape if you originally backed up to a tape device. You must have network or media access to the Recovery folder and contents from the STI_DATA drive of the publisher database server. Before you start the Cisco CallManager installation, verify file access and DNS name resolution to the MCS.sti file in the dead net through the computer browser.
Procedure
Step 1
Performing Tasks on the Existing Cisco CallManager 3.1/3.2 Publisher Database Server (Required)
Step 2
Step 3
Step 4
a.
b.
c.
Caution
Caution
Step 5
Caution
Step 6
Preparing the New Publisher Database Server
Step 7
Step 8
Step 9
Caution
You must enter the exact computer name and network configuration information as the publisher database server that runs Cisco CallManager 3.1 or 3.2.
Do not join the new publisher database server to a Windows domain. Joining the domain causes the Cisco CallManager installation to fail.
During the operating system installation, check the I am recovering a system from backup check box (to ensure that the Recover flag is created in the STI_DATA drive).
Step 10
Step 11
Step 12
Step 13
Caution
Moving the New Publisher Database Server to the Live Network
Step 14
Step 15
Step 16
Step 17
Tip
Replacing Cisco CallManager 3.1/3.2 Subscriber Server(s) During a Cisco CallManager 3.3 Upgrade
You must install Cisco CallManager on subscriber servers serially; that is, on one server at a time.
Caution
Perform these procedures on a live network with a live publisher database server.
Timesaver
Tip
After you install the second subscriber server and verify that it behaves as expected, you may experience call-processing interruptions if you choose to revert the cluster to the original state.Procedure
Step 1
Step 2
Step 3
Step 4
Caution
Do not check the I am recovering a system from backup check box.
Do not join the server to a Windows Domain during the operating system installation. Joining the domain causes the Cisco CallManager installation to fail.
Step 5
Tip
Replacing the Cisco CallManager 3.3(3) Publisher Database Server During the Cisco CallManager 3.3(4) Upgrade
Perform the following procedure:
Procedure
Step 1
Performing Tasks on the Existing Cisco CallManager 3.3(3) Publisher Database Server (Required)
Step 2
Step 3
Step 4
a.
b.
Caution
After you perform a backup, do not make any changes to the existing publisher database server that runs Cisco CallManager 3.3(3). Any changes that you make after a backup will not exist in the new database.
Step 5
Step 6
Preparing the New Publisher Database Server
Step 7
Caution
Step 8
Step 9
Step 10
Step 11
Tip
Step 12
Step 13
Tip
Replacing the Cisco CallManager 3.3(3) Subscriber Server(s) During the Cisco CallManager 3.3(4) Upgrade
You must install Cisco CallManager on subscriber servers serially; that is, on one server at a time.
Caution
Perform these procedures on a live network with a live publisher database server.
Timesaver
Tip
After you install the second subscriber server and verify that it behaves as expected, you may experience call-processing interruptions if you choose to revert the cluster to the original state.Procedure
Step 1
Step 2
Step 3
Step 4
Caution
Do not check the I am recovering a system from backup check box.
Do not join the server to a Windows Domain during the operating system installation. Joining the domain causes the Cisco CallManager installation to fail.
Step 5
Tip
Troubleshooting Hardware Replacements During Upgrades
If the server does not behave as expected, power off the live (new) publisher database server and the subscriber server, if applicable, power on the publisher database server that runs Cisco CallManager 3.1/3.2/3.3(3), and rebuild the subscriber server to its original state. If you replaced the subscriber server, restore power to the subscriber server that runs Cisco CallManager 3.1/3.2/3.3(3).
Upgrading the Cisco ICS 7750 to Cisco CallManager 3.3(4)
This section describes the procedure for upgrading the Cisco ICS 7750 from the latest version of Cisco CallManager 3.1 or 3.2 or Cisco CallManager 3.3(3) to Cisco CallManager 3.3(4). For detailed instructions on performing system software tasks on the Cisco ICS 7750, refer to Upgrading to Cisco CallManager Release 3.3(x) on the Cisco ICS 7750. To obtain the most recent version of this document, see the Table 1.
Procedure
Step 1
•
•
Caution
a.
b.
c.
d.
e.
f.
g.
Caution
h.
i.
j.
Step 2
•
•
Tip
Step 3
Step 4
•
•
•
•
•
•
Obtaining Documentation
Cisco provides several ways to obtain documentation, 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 on the World Wide Web at this URL:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
You can access the Cisco website at this URL:
International Cisco web sites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:
http://www.cisco.com/go/subscription
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.
You can email your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems, Inc.
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com, which includes the Cisco Technical Support Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco Technical Support Website. Cisco.com registered users have complete access to the technical support resources on the Cisco Technical Support Website, including TAC tools and utilities.
Cisco.com
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
•
•
•
•
•
To obtain customized information and service, you can self-register on Cisco.com at this URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco Technical Support Website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
•
•
•
•
Cisco Technical Support Website
You can use the Cisco Technical Support Website to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco Technical Support Website, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco Technical Support Website. Some services on the Cisco Technical Support Website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://tools.cisco.com/RPF/register/register.do
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco Technical Support Website, you can open a case online at this URL:
http://www.cisco.com/en/US/support/index.html
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco Technical Support Website so that you can describe the situation in your own words and attach any necessary files.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
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/en/US/products/products_catalog_links_launch.html
•
•
http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html
•
http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html
•
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, 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 Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO 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. (0402R)
Copyright © 2004. Cisco Systems, Inc. All rights reserved.
