Table Of Contents
Upgrading Cisco CallManager Release 3.1(1)
Contents
Before You Begin the Cisco CallManager Release 3.1 Upgrade
Obtaining Device Default Load Information for Cisco CallManager Release 3.0
Backing Up Your Cisco CallManager System and Preserving Your Hard Drives
Upgrading Cisco CallManager Release 3.1
Upgrading the BIOS and Operating System via CD-ROM
Upgrading the BIOS and Operating System via the Web
Upgrading Cisco CallManager via CD-ROM or the Web
Performing Post-Upgrade Tasks
Verifying Services
Drive Mirroring for the MCS-7830, MCS-7835, and IBM xSeries 340 Server
Using the Cisco CallManager Music On Hold CD-ROM 3.1
Reverting to the Previous Configuration after an Upgrade Attempt
Reverting a 3.1 Cisco Device Load to a 3.0 Cisco Device Load
Reconfiguring the MCS-7820, MCS-7822, MCS-7825, or IBM xSeries 330 Server After an Upgrade Attempt
Reconfiguring the MCS-7830, MCS-7835, or IBM xSeries 340 Server After an Upgrade Attempt
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Contacting TAC by Using the Cisco TAC Website
Contacting TAC by Telephone
Upgrading Cisco CallManager Release 3.1(1)
Note 
Cisco CallManager Release 3.1 Upgrade provides a full version of Cisco CallManager and an upgrade of previous releases of 3.0. To upgrade to Cisco CallManager Release 3.1, you must have a version of Cisco CallManager 3.0 running on your server. If your server runs Cisco CallManager Release 2.2, 2.3, or 2.4, you must upgrade to a version of Cisco CallManager Release 3.0 before you can upgrade to Cisco CallManager Release 3.1.
Perform all the steps to ensure a successful install. If you are running a Cisco CallManager cluster, you must upgrade all the servers in the cluster. You must perform the upgrade on the publisher server first, the TFTP server second, if it does not act as the publisher, and then any other subscribers in the cluster. Make sure to upgrade only one server in the cluster at a time. This document assumes that all servers in your cluster are currently in an operational state. For information on recommended cluster configuration and redundancy groups, refer to the Cisco IP Telephony Network Design Guide. You can view this document by clicking the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/ip_tele/network/index.htm
Use this document in conjunction with the latest versions of the Cisco CallManager Administration Guide, the Cisco CallManager System Guide, the Cisco CallManager Serviceability Administration Guide, online help in the Cisco CallManager application, and the Cisco Documentation CD-ROM. For a list of new features, compatibility caveats, and enhancements in Cisco CallManager Release 3.1, refer to the version of Release Notes for Cisco CallManager Release 3.1 that matches your upgrade document. You can view this document by clicking the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_1/rel_note/index.htm
Unless otherwise specified in this document, all further references to the Cisco Media Convergence Server 7835 (MCS-7835) apply to the MCS-7835, which contains a 733-MHz processor, the MCS-7835-1000, which contains a 1-GHz processor, and the customer-provided DL380.
Contents
This document contains the following topics:
•Before You Begin the Cisco CallManager Release 3.1 Upgrade
•Upgrading Cisco CallManager Release 3.1
•Performing Post-Upgrade Tasks
•Reverting to the Previous Configuration after an Upgrade Attempt
•Obtaining Documentation
Before You Begin the Cisco CallManager Release 3.1 Upgrade
Using this document, you can upgrade via CD-ROM or the web. To upgrade via CD-ROM, locate the Cisco IP Telephony Server Operating System OS/BIOS Upgrade CD-ROM (CD #2) and the appropriate version of the Cisco CallManager 3.1 Installation and Recovery CD-ROM. The Cisco IP Telephony Server Operating System OS/BIOS Upgrade CD-ROM (CD #2) performs the following tasks, as seen in Table 1, when used properly during the upgrade:
Table 1 Tasks of Cisco IP Telephony Operating System OS/BIOS Upgrade CD-ROM
Tasks
|
Notes
|
Installs Windows 2000 Service Pack 2
|
Windows 2000 Service Pack 2 detects the previous installation, changes the system to 128-bit encryption, and includes hotfixes for virtual memory management. It will not install if it detects a previous installation of Windows 2000 Service Pack 2.
|
Installs IIS Security Update
|
IIS Security Update addresses MS01-026 and reinstalls automatically with each upgrade.
|
Installs IIS Security Update 2
|
IIS Security Update 2 addresses MSO1-033 and reinstalls automatically with each upgrade.
|
Changes Simple Network Management Protocol (SNMP) service to Automatic
|
This action occurs automatically with each upgrade.
|
Changes Event Viewer maximum size settings to 10240K and "overwrite as needed"
|
This action occurs automatically with each upgrade.
|
Changes Print Spooler service to Automatic
|
This action occurs automatically with each upgrade.
|
Updates Telnet registry settings and sets the service to Automatic
|
This action occurs automatically with each upgrade.
|
Updates Terminal Services to Automatic and sets the idle session timeout to 30 minutes
|
This action occurs automatically with each upgrade.
|
Sets Remote Access Service (RAS) to Disabled
|
This action occurs automatically with each upgrade.
|
Installs Microsoft Paint
|
This action occurs automatically with each upgrade.
|
Installs Hyper Terminal
|
With each upgrade, Cisco CallManager saves the current configuration, if applicable.
|
Installs Network Monitor
|
With each upgrade, Cisco CallManager saves the current configuration, if applicable.
|
Installs Domain Name System (DNS)
|
This action occurs if DNS is not already installed.
|
Removes Windows NetMeeting files and services
|
This action occurs automatically with each upgrade.
|
Installs Compaq utilities on Compaq servers
|
This action occurs automatically with each upgrade.
|
Removes Compaq web agent and survey utility from Compaq servers
|
This action occurs automatically with each upgrade.
|
Before you begin the upgrade, complete the following tasks:
•Write down the default load information for all devices associated with your current Cisco CallManager 3.0 system.
•Back up your Cisco CallManager 3.0 data, and, if applicable, preserve the hard drives.
•Purge any unused call detail records (CDRs) to prevent timeout of the upgrade and to reduce upgrade time. Cisco recommends storing no more than 2.5 million CDRs in the database. For information on purging CDRs, refer to the latest version of Administrative Reporting Tool Guide for Cisco CallManager.
Note If you changed the default value of a service parameter while running Cisco CallManager 3.0, the default value does not change during the Cisco CallManager 3.1 upgrade process. If you never changed the default value while running Cisco CallManager 3.0, Cisco CallManager updates the parameter value during the Cisco CallManager 3.1 upgrade to match the suggested value seen in Cisco CallManager 3.1 Administration.
Obtaining Device Default Load Information for Cisco CallManager Release 3.0
Caution If you want to revert from Cisco CallManager Release 3.1 to Cisco CallManager Release 3.0, you must have the device default load information for Cisco CallManager Release 3.0.
To obtain the device default load information associated with your Cisco CallManager 3.0 system, perform the following procedure:
Procedure
Step 1 On the publisher server, choose Start > Programs > Cisco CallManager 3.0 > Cisco CallManager 3.0 Administration and log in with administrator privileges.
Step 2 From the CallManager Administration window, choose System > Device Defaults.
Step 3 While viewing the Device Defaults Configuration screen, write the load information for the devices currently associated with your Cisco CallManager 3.0 system in Table 2, which already includes the first four digits of the eight-digit load. This information reflects the device default load information associated with the Cisco CallManager 3.0 version currently running on your system.
Step 4 File this information, so it is easily accessible in the future.
Note To revert from Cisco CallManager Release 3.1 to a previous Cisco CallManager 3.0 release, you must retain the device default load information associated with the Cisco CallManager 3.0 version running on your system. See the "Reverting to the Previous Configuration after an Upgrade Attempt" section for more information.
Use Table 2 in conjunction with the "Obtaining Device Default Load Information for Cisco CallManager Release 3.0" section. Fill in the device default load information for Cisco CallManager Release 3.0. The first four digits of an eight-digit load have been inserted for you. Make sure to file this information after you complete the table.
Table 2 Device Default Load Information
Device Type
|
Load Information
|
IP Phones 7960/7940
|
P003
|
IP Phone 7910
|
P004
|
IP Phones 12 S/SP/12SP+/30VIP
|
P002
|
IP Phone 30 SP+
|
P001
|
IP Phone 7935
|
P005
|
Analog Access
|
A001
|
Analog Access WS-X6624
|
A002
|
Digital Access+
|
D003
|
Digital Access WS-X6608
|
D004
|
Conference Bridge WS-X6608
|
C001
|
Media Termination Point WS-X6608
|
M001
|
14-Button Line Expansion Module
|
S001
|
Backing Up Your Cisco CallManager System and Preserving Your Hard Drives
After you write down the device default load information, you perform the backup. Cisco CallManager comes with the Cisco IP Telephony Applications Backup Utility. This utility provides a reliable and convenient way to perform regularly scheduled, automatic backups of Cisco CallManager data.
Note Cisco recommends obtaining a spare hard drive before completing the following procedure; however, a separate drive is not necessary to preserve the hard drive.
Perform the following steps to back up Cisco CallManager data and preserve the hard drives:
Procedure
Step 1 Perform a Cisco CallManager backup on the publisher server.
For instructions on backing up Cisco CallManager data, refer to the latest version of Backing Up and Restoring Cisco CallManager Release 3.1.
Step 2 Save the MCS.sti file from the backup server to a tape drive or network directory.
Step 3 If you are backing up the MCS-7820, MCS-7822, MCS-7825, or customer-provided IBM xSeries 330 server, begin the upgrade by completing the steps in the "Upgrading Cisco CallManager Release 3.1" section.
If you are backing up the MCS-7830, MCS-7835, or customer-provided IBM xSeries 340 server, power off the publisher server and continue to Step 4.
Step 4 Remove the hard drive from Slot 1 and label the drive with the machine name, slot number, and current version of Cisco CallManager.
Step 5 Power on the system. If you have the MCS-7830 or MCS-7835, the system automatically prompts you to press F1 or F2. If you have the customer-provided IBM xSeries 340 server, the system automatically prompts you to press F2, F4, F5, or F10.
Step 6 To enable interim recovery mode on the MCS-7830 or MCS-7835, press F2 and go to Step 7; to enable interim recovery mode on the customer-provided IBM xSeries 340 server, press F5 and go to Step 8.
Step 7 This step applies only for the MCS-7830 or MCS-7835. When prompted, press F1 to continue.
Step 8 If a spare hard drive is not available, go to Step 10. If a spare hard drive is available, perform the following steps:
a. After Windows 2000 finishes booting, insert the spare hard drive in Slot 1.
b. For the MCS-7830 or MCS-7835, choose Start > Programs > Compaq Systems Tools > Compaq Array Configuration Utility. When the Array Configuration Utility Warning window opens, click OK.
For the customer-provided IBM xSeries 340 server, choose Start > Programs > ServeRaid Manager> ServeRaid Manager.
c. Watch the status bar in the lower, right corner to determine when the drive-mirroring process completes.
Note This note applies only for the MCS-7830 or MCS-7835. If the Compaq Systems Tools folder is not present on the Programs menu, double-click the Compaq Driver Update Setup icon on the desktop to install it; then, complete Step 8.
Step 9 Repeat Step 3 through Step 8 for each server in the cluster.
Step 10 Begin the upgrade by completing the steps in the "Upgrading Cisco CallManager Release 3.1" section.
Upgrading Cisco CallManager Release 3.1
This section describes how to upgrade from any Cisco CallManager Release 3.0 to Release 3.1(1). You can only use this upgrade utility to upgrade Cisco CallManager Release 3.0. This procedure does not support releases prior to 3.0.
If you are running a Cisco CallManager cluster, you must upgrade all the servers in the cluster. You must perform the upgrade on the publisher server first, the TFTP server second, if it does not act as the publisher, and then any other subscribers in the cluster. Make sure to upgrade only one server in the cluster at a time. If you have three servers with 900 devices and no call detailed records (CDRs), the upgrade process takes approximately 3 hours. The size of your database may increase the time it takes to complete the upgrade process.
Note During the upgrade process, Cisco CallManager services automatically stop, so the software can be upgraded. The services then restart at the end of the process. Because of this brief interruption, call-processing services temporarily stop. You should notify your users that telephone service will be interrupted during this time. Close all programs before proceeding.
After you finish the Cisco IP Telephony Applications backup, you choose to upgrade via the web or CD-ROM. The following sections apply to the upgrade:
•Upgrading the BIOS and Operating System via CD-ROM
•Upgrading the BIOS and Operating System via the Web
•Upgrading Cisco CallManager via CD-ROM or the Web
•Performing Post-Upgrade Tasks
Upgrading the BIOS and Operating System via CD-ROM
Note If you have an IBM xSeries 330 or 340 server, you will not upgrade the BIOS when you insert the Cisco IP Telephony Server Operating System OS/BIOS Upgrade CD-ROM (CD #2); however, the Windows 2000 operating system upgrades after you insert the CD-ROM. For BIOS upgrades on the IBM xSeries server, contact the hardware manufacturer directly.
Caution You must perform the upgrade on the publisher server first, the TFTP server second, if it does not act as the publisher, and then any other subscribers in the cluster. Make sure to upgrade only one server in the cluster at a time.
Using the Cisco IP Telephony Server Operating System OS/BIOS Upgrade CD-ROM (CD #2), upgrade the BIOS and the operating system by completing the following steps:
Procedure
Step 1 To upgrade the BIOS, you need to insert the Cisco IP Telephony Server Operating System OS/BIOS Upgrade CD-ROM (CD #2) into the CD-ROM drive as soon as you are able to do so. This means that you must power up the server and then insert CD #2 early in the startup process.
Step 2 When the BIOS upgrade completes, remove CD #2 and press any key to continue. The system automatically reboots.
Step 3 Log in to the server and enter the password for the Administrator account; then, click OK.
Step 4 To upgrade the operating system, insert Cisco IP Telephony Server Operating System OS/BIOS Upgrade CD-ROM (CD #2) into the CD-ROM drive. The operating system upgrade begins.
Step 5 When the Operating Systems Upgrade window opens, click OK. This upgrade process takes about 6 to 15 minutes to complete, depending on your server type.
Step 6 After the process completes, CD #2 automatically pops out of the CD-ROM drive; then, the system automatically reboots.
Step 7 Log in to the server and enter the password for the Administrator account; then, click OK.
To continue the upgrade, see the "Upgrading Cisco CallManager via CD-ROM or the Web" section.
Upgrading the BIOS and Operating System via the Web
Note If you have an IBM xSeries 330 or 340 server, you will not upgrade the BIOS if you download 7835-BIOS-04-02-01.exe or 7825-BIOS-04-11-01 from the web; however, the Windows 2000 operating system upgrades when you download win-OS-BIOS-upgrade.3-1-3.exe. For BIOS upgrades on the IBM xSeries server, contact the hardware manufacturer directly.
Via the web, upgrade the BIOS and the operating system by completing the following steps:
Procedure
Step 1 If necessary, connect a monitor, keyboard, and mouse to the server as described in the "Connecting a Monitor, Keyboard, and Mouse to the Server" section in the latest version of Installing Cisco CallManager Release 3.1.
Caution You must perform the upgrade on the publisher server first, the TFTP server second, if it does not act as the publisher, and then any other subscribers in the cluster. Make sure to upgrade only one server in the cluster at a time.
Step 2 To upgrade the BIOS on the MCS-7835 or MCS-7825, obtain a formatted 1.44 diskette and perform the following procedure:
a. To upgrade the BIOS on the MCS-7835, download the Softpaq file 7835-BIOS-04-02-01.exe from http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr to your hard drive. To upgrade the BIOS on the MCS-7825, download the Softpaq file 7825-BIOS-04-11-01.
b. Make note of the location where you save the downloaded file.
c. Double-click the downloaded file.
d. When prompted, insert the formatted 1.44 MB diskette into a floppy drive.
e. After the diskette is created, you may delete the downloaded BIOS file.
f. Leave the diskette in the drive. Shut down the server and then power it off. Wait 10 seconds and power the server on. The upgrade starts automatically.
Note Do not power off or restart during the BIOS update process. Created using the preceding steps, the README.TXT file on the BIOS diskette provides further instructions.
g. Follow the prompts on the screen.
h. After the BIOS update completes, remove the 1.44 MB diskette and restart the server.
Step 3 To upgrade the Windows 2000 operating system, download the file win-OS-upgrade.3-1-1.exe or a later version of this file from http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr. Make note of the location where you save the file.
Step 4 Double-click the downloaded file.
Step 5 Wait while the files load to your server.
Step 6 Read and accept the license agreement.
Step 7 Choose Install.
Step 8 After the installation completes, restart your computer for the update to take effect.
Step 9 Log in to the server as the Administrator.
Caution You must log in using the username Administrator. If the Administrator username has been changed, change it back to Administrator.
To continue the upgrade, see the "Upgrading Cisco CallManager via CD-ROM or the Web" section.
Upgrading Cisco CallManager via CD-ROM or the Web
Via CD-ROM or the web, perform the upgrade by completing the following steps:
Procedure
Step 1 Depending on your upgrade method (via CD-ROM or the web), perform the following procedure:
a. If you want to upgrade via CD-ROM, locate the Cisco CallManager 3.1(1) Installation and Recovery CD-ROM and insert it into the CD-ROM drive; then, go to Step 2.
b. If you want to upgrade via the web, download the Cisco CallManager 3.1(1) upgrade file from http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr to your hard drive. Make note of the location where you save the downloaded file. Double-click the downloaded file to begin the installation; then, go to Step 2.
Step 2 If the Cisco Product Activation popup window appears, click Yes.
Step 3 In the Welcome to the Cisco CallManager Installation Wizard window, click Next.
Step 4 In the CallManager Components window, choose the services that you want to activate; then, click Next. This window displays the default selections. You must choose the services that you want activated on this server. For a description of the available services, refer to the "Before You Begin" section of the version of Installing Cisco CallManager Release 3.1 that matches this upgrade document.
Note The following statements apply to the services in the CallManager Components window. The Cisco IP Voice Media Streamer contains the Media Termination Point (MTP), music on hold (MOH), and conference bridge services. To add or remove services later, refer to the "Activating Cisco CallManager Services" section in the latest version of Installing Cisco CallManager Release 3.1.
Caution You automatically install the database with any selection from the CallManager Components window. If you want a standalone database server only (does not have Cisco CallManager installed), check the Cisco CallManager Web Components check box. With this selection, only Cisco CallManager Web Components, such as Cisco CallManager 3.1 Administration, and the database install on the standalone database server.
Figure 1 shows an example of the CallManager Components window.
Figure 1 CallManager Components Window
Note The publisher database serves as the master database for all servers in the cluster. All servers except the publishing database server maintain subscriber databases, which are copies of the publisher database. If you are configuring a subscriber database server, make sure the server you are installing can connect to the publishing database server before the installation can continue. The installation process necessitates this connection because the subscriber server attempts to connect to the publisher server, so the publisher database can be copied from that server to the local drive on the subscriber server. To make sure a good connection exists between the servers, issue a ping command from the subscriber server to the publisher server before you try to authenticate to it. If you are using Domain Name System (DNS), use a fully qualified domain name (for example, `hostname.cisco.com') with the ping command. If the ping command is not successful, you must exit the installation program, fix the problem, and begin the installation process again
Step 5 .Cisco CallManager autodetects whether you are upgrading the publisher database server or subscriber database server. If you are upgrading the publisher database server, Cisco CallManager automatically chooses I am upgrading/installing the CallManager Publisher. Click Next and go to Step 6.
Figure 2 demonstrates Cisco CallManager autodetection of the publisher.
Figure 2 Cisco CallManager Publisher Autodetection
If a publisher database already exists and you are configuring a subscriber database server, Cisco CallManager automatically chooses I am upgrading/installing the CallManager Subscriber. By default, the publisher database server associated with the subscriber displays in the hostname publisher field. You may choose another publisher by clicking Browse. After you choose the appropriate publisher, click Next and go to Step 6.
Step 6 Either the Directory Server Configuration window or the Authentication to the Publishing Database window opens, depending on which server Cisco CallManager chose in Step 5. If Cisco CallManager chose I am upgrading/installing the CallManager Publisher, the Directory Server Configuration window opens and prompts you for the Directory Manager password. Enter the password in the Password field; then, enter the same password again in the Confirm Password field. Click Next, and go to Step 7.
If Cisco CallManager chose I am upgrading/installing the CallManager Subscriber, an authentication window opens and prompts you to enter usernames and passwords for a Windows 2000 user with administrative privileges and a SQL Server user with SQL Server administrative privileges on the publishing database server. Enter the account information in the appropriate fields as prompted and then click Next. The system connects to the publishing database server.
Figure 3 shows an example of the authentication window.
Figure 3 Authentication to Publishing Database Window
Step 7 You have completed the configuration of Cisco CallManager and the database server. Now that the Cisco CallManager and other included software are ready to be installed, click Next. This part of the installation takes about 30 minutes.
Step 8 If you require no update to the backup utility, a window displays prompting you to enter a new password for the local Administrator; enter the new password in the New Password field and then enter it in the Retype Password field. Click OK and then skip to Step 19.
Caution Enter the same Administrator password for the publisher and all subscribers in the cluster, so that Cisco CallManager database replication occurs.
Step 9 If you need to update the backup utility, the Cisco IP Telephony Applications Backup Utility Setup loads automatically. You must specify whether this server will act as a backup target or the backup server during the backup and restore operation. For information on the latest Cisco IP Telephony Applications Backup Utility, refer to the latest version of Backing Up and Restoring Cisco CallManager Release 3.1.
The backup server actually performs the backup operation. It stores the backup data in the directory or tape drive destination that you specify. If a server is configured as a backup server, it automatically gets added to the backup target list.
A backup target server contains data to be backed up. You can choose more than one target, but you can choose only one server.
Choose either Server or Target and then click OK.
Note Cisco strongly recommends that you use the Cisco IP Telephony Applications Backup Utility to perform backups and that no third-party backup or other software is used. However, if you do not want to use the Cisco IP Telephony Applications Backup Utility, complete the installation as instructed and then stop the service called "stiBack for Cisco IP Telephony Applications." To stop the service, choose Start > Run, enter services.msc /s, choose the service in the main window, and click Stop Service.
Step 10 If you chose Target in the previous step, a message appears indicating that the setup is complete. You need to configure this server as a CallManager target on the backup server. Click OK and then go to Step 18.
If you chose Server in the previous step, continue with Step 11.
Step 11 In the Backup Utility Configuration window, add the name of any additional Cisco CallManager servers that you want to back up by clicking Add, entering the server name, and then clicking OK. Click Delete to remove servers from the target list. If you want to add a remote server, you must install it and connect it to the network before you add it to the target list. A prompt asks you to enter a username and password with administrator access rights on the remote server; then, click Verify.
Note The Backup Utility attempts to connect to the remote server. If the remote server is not found, the authentication fails. The server name remains in the target list but may not be accessible.
Step 12 Click the Destination tab. You must choose a destination for backups to be performed. No default destination setting exists.
Figure 4 shows an example of the Destination tab in the Cisco IP Telephony Applications Backup Utility.
Figure 4 Destination Tab in the Cisco IP Telephony Applications Backup Utility Configuration Window
Note If you choose a network directory as the backup destination, 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.
You may click the Tape device radio button only if you have a MCS-7835 or IBM xSeries 340 server. Only the MCS-7835 and IBM xSeries 340 servers have a tape drive available. You must click Network directory or Tape device to use the Cisco IP Telephony Applications Restore Utility on your server.
Step 13 Choose Network directory, Local directory, or Tape device to specify where backup files will be backed up. To enter a network or local directory, you can enter the path and directory name or choose it from a browse box by clicking Browse. For network directories, you must supply a username and password with administrator access rights on that server. In the tape device box, only tape drives configured in Windows NT or Windows 2000 appear. To add new devices, click Add device....
Step 14 Click the Schedule tab. Figure 5 shows an example of the Schedule tab in the Cisco IP Telephony Applications Backup Utility Configuration window.
Figure 5 Schedule Tab in Cisco IP Telephony Applications Backup Utility Configuration Window
Step 15 Choose the days and times that you want the backup to run. The default sets the backup time for
2:00 am Tuesday through Saturday. You can also choose the length of the system log in days; then, click OK.
Caution Cisco CallManager backups should occur during off-peak hours because CPU utilization is high during the backup process.
Step 16 The Performance tab allows the operating system to modify the allocation of CPU resources during the backup process. Click the Performance tab to prioritize when the backup service (stiBack.exe) will run during the next backup. Three options, Low, Normal, and Below Normal appear in the window. Before you click one of the three options, consider the following information:
a. Clicking the Normal radio button accepts the default priority associated with the Windows 2000 or Windows NT 4.0 server.
b. Clicking the Below Normal radio button ensures that configured services remain responsive while the backup occurs. When you click this option, which is available only on a Windows 2000 server, be aware that your backup may take longer than the Normal setting.
c. Clicking the Low radio button ensures that configured services remain completely responsive during the backup. Be aware that your backup may take longer than the Normal of Below Normal setting.
If you do not click one of the performance radio buttons, the Normal radio button serves as the default priority for the backup service (sti.Back.exe) that runs on the Windows 2000 or Windows NT 4.0 server during the next backup.
Step 17 To save your settings and exit the Backup Utility Configuration, click OK. For more information on the Backup Utility, refer to the latest version of Backing Up and Restoring Cisco CallManager Release 3.1.
Step 18 A prompt asks you to enter a new password for the local Administrator account. Enter the new password in the New Password field and then enter it in the Retype Password field. Click OK.
Caution When entering passwords for the local Administrator and SA (SQL Server system administrator) accounts, do not use the apostrophe. Enter the same Administrator password for the publisher and all subscribers in the cluster, so Cisco CallManager database replication occurs.
Step 19 A prompt asks you to enter a new password for the SA (SQL Server system administrator) account. Enter a new password of at least 5 characters in the New Password field and then enter it in the Retype Password field. Click OK.
Step 20 A message indicates that both passwords changed successfully. Click OK.
Step 21 When prompted, click Yes if you want to reboot the system.
Step 22 After you perform the upgrade and your Cisco CallManager is operational, you should back up your Cisco CallManager data. For information on backing up Cisco CallManager data, refer to the latest version of Backing Up and Restoring Cisco CallManager Release 3.1.
Caution Backing up your Cisco CallManager data after an upgrade is essential. Refer to the latest version of Backing Up and Restoring Cisco CallManager Release 3.1 for implications and scenarios associated with not backing up your data.
See the "Performing Post-Upgrade Tasks" section to complete post-upgrade tasks.
Performing Post-Upgrade Tasks
After you complete the upgrade, you should verify that services are running, and if applicable, reinsert the hard drives into your server. You may also want to perform the appropriate steps to use the latest version of the Cisco CallManager Music On Hold CD-ROM 3.1.
Besides verifying services, you need to verify that you have the latest Microsoft patches and hotfixes running on your system. To verify and download these items, click the following URL:
http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr
Note If you have upgraded to Cisco CallManager 3.1, you must upgrade the 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.
Verifying Services
To confirm that the upgrade completed successfully, verify that all the services listed in your Services window are running. Choose Start > Programs > Administrative Tools > Services and verify the following services:
•Cisco CallManager
•Cisco Database Layer Monitor
•Cisco IP Voice Media Streaming Application
•Cisco Messaging Interface
•Cisco SNMP Data Collector
•Cisco TFTP
•DC Directory Server
Depending on which services you have installed on your system, some services shown in the preceding list may not appear in your Services window.
Drive Mirroring for the MCS-7830, MCS-7835, and IBM xSeries 340 Server
Perform the following procedure only if you did not use a spare hard drive during the backup of Cisco CallManager data. Make sure that the system functions properly before performing the following procedure. Run your Cisco CallManager system for several days to verify that no problems exist. After you verify the services, you must reinsert the hard drives that you removed prior to installation.
To reinsert the hard drives, complete the following steps:
Note Cisco recommends that you perform the drive-mirroring process after regular business hours. You should notify your users that telephone service will be interrupted during this time.
Procedure
Step 1 Start with the publisher server. Place the hard drive that was removed during the preinstallation steps back into Slot 1.
Step 2 Perform the following tasks:
a. For the MCS-7830 or MCS-7835, choose Start > Programs > Compaq Systems Tools > Compaq Array Configuration Utility. When the Array Configuration Utility Warning window opens, click OK.
For the customer-provided IBM xSeries 340 server, choose Start > Programs > ServeRaid Manager> ServeRaid Manager.
b. Watch the status bar in the lower, right corner to determine when the drive-mirroring process completes.
Step 3 Repeat Step 1 and Step 2 for each server in the cluster.
Using the Cisco CallManager Music On Hold CD-ROM 3.1
When you upgrade to Cisco CallManager Release 3.1 on your server, a default music on hold sample automatically installs for customer use. To increase your music on hold (MOH) selection, you may also install the Cisco CallManager Music On Hold CD-ROM 3.1 that ships with your Cisco IP Telephony Applications Server, or you may download one of two zip files via the web. You may download the file, ciscocm-MusicOnHold.3-1.zip, which is a set of wav files providing the entire music selection from the CD-ROM; or, you may download the file, ciscocm-MusicOnHoldSampler.3.1.zip, which is a small set of files offering a sample of music available on the CD-ROM. Cisco recommends that you store these files locally on a server that does not run Cisco CallManager. For information on creating audio sources through the Music On Hold feature, refer to the latest version of the Cisco CallManager Administration Guide and the latest version of the Cisco CallManager System Guide.
The Cisco CallManager Music On Hold CD-ROM 3.1 contains ready-to-use MOH loops, music, and voice prompts designed for use with the music on hold (MOH) feature. All music samples and voice prompts on the CD-ROM are 16-bit PCM sampled at 16 KHz. All samples and prompts can play with good audio quality in 7960/7940 wideband mode.
As a Cisco CallManager user, you can use any of the contents of the CD-ROM with music on hold. Due to licensing restrictions, you may not distribute the Cisco CallManager Music on Hold CD-ROM to anyone else, nor may you use it 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 in effect prior to the upgrade.
Reverting a 3.1 Cisco Device Load to a 3.0 Cisco Device Load
If you want to revert from Cisco CallManager Release 3.1 to Cisco CallManager Release 3.0, perform the following procedure:
Procedure
Step 1 Locate the device default load information associated with the Cisco CallManager Release 3.0 previously running on your system before the upgrade attempt. See Table 2 for more information.
Step 2 On the publisher server, choose Start > Programs > Cisco CallManager 3.1 > CallManager Administration and log in with administrator privileges.
Step 3 From the CallManager Administration window, choose System > Device Defaults.
Step 4 On the Device Defaults Configuration screen, enter the device default load information from Table 2 into the appropriate Load Information fields.
Step 5 To reset the devices, click Update.
To continue the reversion, see the "Reconfiguring the MCS-7820, MCS-7822, MCS-7825, or IBM xSeries 330 Server After an Upgrade Attempt" section or the "Reconfiguring the MCS-7830, MCS-7835, or IBM xSeries 340 Server After an Upgrade Attempt" section for information on how to reconfigure your server.
Reconfiguring the MCS-7820, MCS-7822, MCS-7825, or IBM xSeries 330 Server After an Upgrade Attempt
To reconfigure the MCS-7820, MCS-7822, MCS-7825, or IBM xSeries 330 server after an upgrade attempt, perform the following procedure:
Procedure
Step 1 Reinstall Cisco CallManager. For installation instructions, refer to the latest version of Installing Cisco CallManager Release 3.1. You can view this document by clicking on the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_1/install/index.htm
Step 2 Perform the necessary upgrade(s) to match the most recent Cisco IP Telephony Applications backup.
Step 3 Revert the system to the pre-upgrade configuration by using the Cisco IP Telephony Applications Restore Utility. For more information on the Cisco IP Telephony Applications Restore Utility, refer to latest version of Backing Up and Restoring Cisco CallManager Release 3.1 or the Cisco CallManager installation guide that matches your Cisco CallManager installation CD-ROM.
Reconfiguring the MCS-7830, MCS-7835, or IBM xSeries 340 Server After an Upgrade Attempt
To reconfigure the MCS-7830, MCS-7835, or IBM xSeries 340 server after an upgrade attempt, perform the following procedure:
Procedure
Step 1 Shut down the server.
Step 2 Remove the hard drive from Slot 0. Place the hard drive that was removed prior to the upgrade into Slot 1.
Step 3 Power on the system. If you have the MCS-7830 or MCS-7835, the system automatically prompts you to press F1 or F2. If you have the customer-provided IBM xSeries 340 server, the system automatically prompts you to press F2, F4, F5, or F10.
Step 4 To enable interim recovery mode on the MCS-7830 or MCS-7835, press F2 and go to Step 5; to enable interim recovery mode on the customer-provided IBM xSeries 340 server, press F5 and go to Step 6.
Step 5 This step applies only for the MCS-7830 or MCS-7835. When prompted to do so, press F1 to continue.
Step 6 Repeat Step 1 through Step 5 for each server in the cluster.
Step 7 Verify that all services in your Services window are running properly. See the "Performing Post-Upgrade Tasks" section for information on verifying services.
Step 8 Replace the hard drive in Slot 0 and allow the drive-mirroring process to complete.
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following sites:
•http://www.cisco.com
•http://www-china.cisco.com
•http://www-europe.cisco.com
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships 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.
Ordering Documentation
Cisco documentation is available in the following ways:
•Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
http://www.cisco.com/go/subscription
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
http://www.cisco.com
Technical Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
http://www.cisco.com/tac
P3 and P4 level problems are defined as follows:
•P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
Contacting TAC by Telephone
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
•P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
•P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.
AccessPath, AtmDirector, Browse with Me, CCIP, CCSI, CD-PAC, CiscoLink, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, 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 Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site 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. (0106R)
Copyright © 2001. Cisco Systems, Inc.
All rights reserved.
Feedback
