Upgrading Cisco Unified CallManager Release 4.3(1)
Replacing Servers During the Upgrade
Downloads: This chapterpdf (PDF - 218.0KB) | Feedback

Replacing Servers During the Upgrade

Table Of Contents

Replacing Servers During the Upgrade

Replacing the Cisco Unified CallManager Publisher Database Server During the Cisco Unified CallManager 4.3(1) Upgrade

Replacing the Cisco Unified CallManager Subscriber Server(s) During the Cisco Unified CallManager 4.3(1) Upgrade

Troubleshooting Hardware Replacements During Upgrades


Replacing Servers During the Upgrade


This document assumes that Cisco Unified CallManager is the only application that runs on the server. This document does not provide procedures for replacing coresident servers where Cisco Unified 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 These procedures cause call-processing interruptions. Cisco strongly recommends that you perform this procedure during a maintenance window. After you perform a backup, do not make any changes to the existing publisher database server. Any changes that you make after a backup will not exist in the new database.

Replacing the Cisco Unified CallManager Publisher Database Server During the Cisco Unified CallManager 4.3(1) Upgrade

Perform the following procedure:

Procedure


Step 1 Perform Step 2 through Step 6 for the existing Cisco Unified CallManager publisher database server.

Performing Tasks on the Existing Cisco Unified CallManager Publisher Database Server (Required)

Step 2 Record all network configuration settings, including the computer name, network card speed and duplex, IP address, subnet mask, gateway, DNS, and WINS for the current system. Record the configuration of the servers in the existing cluster; record all software versions, Cisco CallManager services, coresident applications, and plugins, so you can reinstall them after the upgrade. Record the information in Table 6-1

Table 6-1 Server Configuration Settings 

Server Configuration Settings
Your Entry

Computer Name

 

NIC Speed/Duplex settings

 

IP Address

 

Subnet Mask

 

Default Gateway

 

DNS Settings

 

WINS Settings

 

Cisco CallManager services

(See Cisco Unified CallManager Serviceability.)

 

Installed locales

 

Coresident applications

(Note the application type and version.)

 

Cisco verified, third-party applications

(Note the application type and version.)

 

Plugins from Cisco Unified CallManager Administration

 

Other Pertinent Information

 

Step 3 If you are replacing a server with four drives, Cisco recommends that you set the trace directory path on the server to the default C: drive. Refer to Cisco Unified CallManager Serviceability Administration Guide.

Step 4 Refer to the document, Cisco IP Telephony Backup and Restore System (BARS) Administration Guide, to perform the following tasks. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm.

a. Install and configure BARS 4.0(12) (or later) on the publisher database server; reboot the server.

b. Back up the existing Cisco Unified CallManager data.


Caution Make sure that you back up the data to a network directory or a local tape device.

After you perform a backup, do not make any changes to the existing publisher database server. Any changes that you make after a backup will not exist in the new database.

Step 5 Copy the HOST and/or LMHOST files from C:\WINNT\SYSTEM32\DRIVERS\ETC to the network directory where the backed-up data is stored. You can perform this task on a floppy drive.

Step 6 Power off the Cisco Unified CallManager publisher database server and disconnect it from the network.

Preparing the New Publisher Database Server

Step 7 Connect the new server to the network and power on the server. By using the Cisco-provided operating system disks, install operating system version 2003.1.1 on the new publisher database server that has no data on it. To obtain the operating system documentation, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm.


Caution During the operating system installation, make sure that you choose the New Installation or Server Replacement option. You must enter the exact computer name and network configuration information as the publisher database server that runs Cisco Unified CallManager. Do not check the I am recovering a system from backup check box. Do not join the new publisher database server to a Windows domain. Joining the domain causes the Cisco Unified CallManager installation to fail.

Step 8 Use Cisco Unified Communications Server Operating System OS Upgrade Disk that ships with Cisco Unified CallManager to upgrade the Cisco-provided operating system to version 2003.1.1. Before you perform the upgrade, be sure to read the operating system readme information that is posted on the operating system cryptographic software page. You can navigate to the site from the Cisco Unified CallManager software page at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Step 9 Download and install the latest Cisco Unified Communications Server Operating System service release. The operating system service releases post on the voice products operating system cryptographic software page. You can navigate to the site from the Cisco Unified CallManager software page.

For installation instructions, refer to the file-specific readme document, Cisco Unified Communications Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco Unified Communications Applications Server. To obtain the most recent version of these documents, go to http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Step 10 Download and install the latest OS-related security hotfixes, if any.

The operating system related security hotfixes post on the voice products operating system cryptographic software page. You can navigate to the site from the Cisco Unified CallManager software page.

For installation instructions, refer to the file-specific readme document, Cisco Unified Communications Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco Unified Communications Applications Server. To obtain the most recent version of these documents, go to http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Step 11 Copy the HOST and/or LMHOST files to C:\WINNT\SYSTEM32\DRIVERS\ETC on the new publisher database server; reboot the server.

Step 12 Manually install and configure Cisco IP Telephony Backup and Restore System (BARS) version 4.0(12) (or later).


Note The operating system installation removes the version of BARS that you previously installed.


For more detailed instructions, refer to Cisco IP Telephony Backup and Restore System (BARS) Administration Guide. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/index.htm.

Step 13 Copy the backup tar file from the remote location where you stored the file to the local hard disk of the Cisco Unified CallManager server so that you can easily access the backup file during the restore process.

Step 14 Using the Cisco Unified CallManager Installation, Upgrade, and Recovery disks, install Cisco Unified CallManager 4.3(1) on the new server, and configure the new server with the same settings as the old server. For detailed instructions on installing Cisco Unified CallManager, see the "Upgrading Related Cisco CallManager Services and Detecting the Server (Required)" section on page 2-15

Step 15 Install all locales on the new server that were installed on the old server.


Tip Verify that the new server behaves as expected. Review post-upgrade tasks and perform the necessary tasks as you verify. To review post-upgrade tasks, see the "Performing Post-Upgrade Tasks" section on page 3-1.



Replacing the Cisco Unified CallManager Subscriber Server(s) During the Cisco Unified CallManager 4.3(1) Upgrade

You must install Cisco Unified CallManager on subscriber servers serially, that is, on one server at a time.


Caution If you are replacing the publisher database server and subscriber server(s), make sure that you have replaced the publisher database server first and that the data migrated and services started as expected.

Perform these procedures on a live network with a live publisher database server.


Timesaver If you choose to do so, you may perform the operating system installation simultaneously on all new servers if the new hardware is not connected to the same network as the current system. Make sure that you install the operating system on a physically isolated network by using the procedures in this document. Installing the operating system in this manner saves you about 1 hour per server when you perform the actual hardware migration to the production network.



Tip After you install the first subscriber server, verify that the server and application behave as expected. If the server does not behave as expected, power off the live (new) publisher database server and the subscriber server, power on the publisher database server, and rebuild the subscriber server to its original state. If this was a hardware replacement for the subscriber server, restore power to the old subscriber server.

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 Record all network configuration settings, including the computer name, network card speed and duplex settings, IP address, subnet mask, gateway, DNS, and WINS for the current system. Record the configuration of the servers in the existing cluster; record all software versions, Cisco CallManager services, coresident applications, and plugins, so you can reinstall them after the upgrade. Use Table 6-1 to record the information.

Step 2 Power off the Cisco Unified CallManager subscriber server and disconnect it from the network.

Step 3 Connect the new server to the network and power on the server.

Step 4 Using the Cisco-provided Operating System disks, install operating system 2003.1.1 (or later) on the new server that has no data on it.


Caution During the operating system installation, make sure that you choose the New Installation or Server Replacement option.

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 Unified CallManager installation to fail.

Step 5 Use Cisco Unified Communications Server Operating System OS Upgrade Disk that ships with Cisco Unified CallManager to upgrade the Cisco-provided operating system to version 2003.1.1. Before you perform the upgrade, be sure to read the operating system readme information that is posted on the operating system cryptographic software page. You can navigate to the site from the Cisco Unified CallManager software page at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Step 6 Download and install the latest Cisco Unified Communications Server Operating System service release. The operating system service releases post on the voice products operating system cryptographic software page. You can navigate to the site from the Cisco Unified CallManager software page.

For installation instructions, refer to the file-specific readme document, Cisco Unified Communications Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco Unified Communications Applications Server. To obtain the most recent version of these documents, go to http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Step 7 Download and install the latest OS-related security hotfixes, if any.

The operating system related security hotfixes post on the voice products operating system cryptographic software page. You can navigate to the site from the Cisco Unified CallManager software page.

For installation instructions, refer to the file-specific readme document, Cisco Unified Communications Operating System, SQL Server, Security Updates, and Installing the Operating System on the Cisco Unified Communications Applications Server. To obtain the most recent version of these documents, go to http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Step 8 Using the Cisco Unified CallManager Installation, Upgrade, and Recovery disks, install Cisco Unified CallManager on the new server where you installed the operating system. For detailed procedures, see the "Upgrading Related Cisco CallManager Services and Detecting the Server (Required)" section on page 2-23.


Tip After you install Cisco Unified CallManager on the server, verify that the new server behaves as expected. Review post-upgrade tasks and perform the necessary tasks as you verify. To obtain the Cisco Unified CallManager 4.3(1) installation document for post-installation tasks, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm. To review post-upgrade tasks, see the "Performing Post-Upgrade Tasks" section on page 3-1.



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, and rebuild the subscriber server to its original state. If you replaced the subscriber server, restore power to the subscriber server.