Guest

Cisco Unified Communications Manager (CallManager)

Installing Cisco CallManager Release 3.0 on the Cisco Media Convergence Server

 Feedback

Table Of Contents

Installing Cisco CallManager Release 3.0 on the Cisco Media Convergence Server

Contents

Introduction

Server Hardware Specifications

Performing a New Cisco CallManager Release 3.0 Installation

Before You Begin

Connecting a Monitor, Keyboard, and Mouse to the Server

Starting the Cisco CallManager Release 3.0 Installation Utility

Entering the Server Configuration Data

Completing the Cisco CallManager 3.0 Installation

Logging On to the Server

Installing the Compaq Driver Update

Performing Post-Installation Tasks

Changing Passwords for CCMAdmin and SQLSvc Accounts

Configuring Auto Registration

Configuring DNS

Configuring the Database

Activating Cisco CallManager Services

Changing the SNMP Community Name

Installing Compaq Insight Management Agents

Performing Backup and Restore Procedures

Backing Up the Cisco CallManager Data

Performing a Recovery on the Same Cisco CallManager Server

Performing a Recovery on a Replacement Cisco CallManager Server

Restoring the Cisco CallManager Data Only

Performing Post-Recovery Tasks

Migrating from Cisco CallManager Release 2.4 to Release 3.0

Full Migration

Migrating the MCS-7830

Migrating the MCS-7820

Database-Only Migration

Important Notes

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Obtaining Technical Assistance

Cisco Connection Online

Technical Assistance Center

Documentation Feedback


Installing Cisco CallManager Release 3.0 on the Cisco Media Convergence Server


This document describes how to install and configure Cisco CallManager Release 3.0 on the Cisco Media Convergence Server. Use this document in conjunction with the Cisco CallManager Administration Guide or online help in the Cisco CallManager application and the Cisco Documentation CD-ROM.

Contents

This document contains the following topics:

Introduction

Server Hardware Specifications

Performing a New Cisco CallManager Release 3.0 Installation

Performing Post-Installation Tasks

Performing Backup and Restore Procedures

Migrating from Cisco CallManager Release 2.4 to Release 3.0

Important Notes

Obtaining Documentation

Obtaining Technical Assistance

Introduction

Cisco CallManager on the Cisco Media Convergence Server (MCS) is a network business communications system providing high-quality telephony over IP networks. Cisco CallManager and the MCS enable the conversion of conventional, proprietary circuit-switched telecommunication systems to multi-service, open LAN systems.

Use the task roadmaps that follow to determine which sections of this document you need in order to accomplish a desired task.

New Installation

If you are installing Cisco CallManager Release 3.0 for the first time, see the following sections:

Server Hardware Specifications

Performing a New Cisco CallManager Release 3.0 Installation

Before You Begin

Connecting a Monitor, Keyboard, and Mouse to the Server

Starting the Cisco CallManager Release 3.0 Installation Utility

Entering the Server Configuration Data

Completing the Cisco CallManager 3.0 Installation

Logging On to the Server

Installing the Compaq Driver Update

Performing Post-Installation Tasks

Changing Passwords for CCMAdmin and SQLSvc Accounts

Configuring Auto Registration

Configuring DNS

Configuring the Database

Activating Cisco CallManager Services

Changing the SNMP Community Name

Installing Compaq Insight Management Agents

Performing Backup and Restore Procedures

Backing Up the Cisco CallManager Data

Same-Server Recovery

If you are recovering an existing Cisco CallManager server, see the following sections:

Server Hardware Specifications

Performing Backup and Restore Procedures

Performing a Recovery on the Same Cisco CallManager Server

Performing Post-Recovery Tasks

Backing Up the Cisco CallManager Data

Replacement Server Recovery

If you are replacing an existing Cisco CallManager server and recovering data to a new server, see the following sections:

Server Hardware Specifications

Performing Backup and Restore Procedures

Performing a Recovery on a Replacement Cisco CallManager Server

Performing Post-Installation Tasks

Changing Passwords for CCMAdmin and SQLSvc Accounts

Configuring DNS

Activating Cisco CallManager Services

Changing the SNMP Community Name

Installing Compaq Insight Management Agents

Performing Backup and Restore Procedures

Performing Post-Recovery Tasks

Backing Up the Cisco CallManager Data

Migrating from Cisco CallManager 2.4 to 3.0

If you are upgrading your system from Cisco CallManager Release 2.4 to Release 3.0 and migrating an existing 2.4 database to 3.0, see the following sections:

Server Hardware Specifications

Migrating from Cisco CallManager Release 2.4 to Release 3.0

Performing Post-Installation Tasks

Changing Passwords for CCMAdmin and SQLSvc Accounts

Configuring DNS

Activating Cisco CallManager Services

Changing the SNMP Community Name

Installing Compaq Insight Management Agents

Performing Backup and Restore Procedures

Backing Up the Cisco CallManager Data

Server Hardware Specifications

This section describes the system specifications for Cisco CallManager Release 3.0 and each of the Cisco Media Convergence Servers. System hardware components included with each MCS product are listed in Table 1. Your server must be one of the models listed in this table.

Table 1 Media Convergence Server Hardware Specifications

Component
MCS-7835
MCS-7830
MCS-7822
MCS-7820

Intel Pentium III processor

733-MHz

500-MHz

550-MHz

500-MHz

Registered ECC SDRAM

1 GB

512 MB 1

512 MB

512 MB 1

10/100BaseTX protocol control information unshielded twisted-pair (PCI UTP) controller

X

X

X

X

Integrated dual-channel wide Ultra SCSI-3 controller

X

X

   

Integrated wide Ultra2 SCSI adapter

   

X

X

Dual 18.2-GB Ultra2 SCSI hot-plug drives

X

     

Dual 9.1-GB Ultra2 SCSI hot-plug drives

 

X

   

Single 9.1-GB Ultra2 SCSI non-hot-plug drive

   

X

X

1.44-MB floppy disk

X

X

X

X

Preinstalled high-speed IDE CD-ROM drive

X

X

X

X

Hot-plug redundant 275 watt power supply

X

X

   

200-Watt power factor corrected, CE mark-compliant power supply

   

X

X

Integrated 1024 x 768, 256-color video

X

X

X

X

RAID controller

X

X

   

12/24-GB internal DAT Drive

optional

     

1 The MCS-7830 and MCS-7820 require memory upgrades to meet the 512 MB RAM minimum specification. The MCS-7830 is optionally upgradable to 1 GB.



Note A monitor is not supplied with any of the Cisco Media Convergence Servers. The MCS-7820 and MCS-7822 include a keyboard and mouse, but the MCS-7830 and MCS-7835 do not. You must supply a monitor, and if necessary, a keyboard and mouse, to use during initial startup and configuration of the Cisco Media Convergence Server and Cisco CallManager.


Performing a New Cisco CallManager Release 3.0 Installation

This section describes the basic procedures for installing Cisco CallManager Release 3.0 on SQL database publisher and subscriber servers.

The Cisco Media Convergence Server is shipped with a blank hard drive. Before you power up the server for the first time, the Operating System Installation and Recovery CD-ROM must be inserted into the CD-ROM drive. After the system boots, the MCS QuickBuilder installation utility, located on the CD-ROM, loads automatically and guides you through the installation process. MCS QuickBuilder performs several preinstallation tasks including preparing your server's hard drive and loading server configuration information. If necessary, your system BIOS is upgraded to a recommended version to support Windows 2000. MCS QuickBuilder then automatically installs the following software applications:

Microsoft Windows 2000 Server

Microsoft SQL Server 7.0 Standard Edition, Service Pack 2

DC Directory 2.4

Cisco CallManager Release 3.0


Caution Installing or using Netscape Navigator on the Cisco CallManager server can cause severe performance problems. Cisco strongly recommends against installing Netscape Navigator or any other application software on the Cisco CallManager server.

Make sure your server is connected to the network before you begin the installation. Windows 2000 will not install if the server is not connected to the network.


Note The version of Microsoft Windows 2000 included with Cisco CallManager Release 3.0 is a special limited version. It is intended for use with Cisco CallManager only, and is not fully functional for general use.



Note For instructions on how to mount the server and connect it to a power source, refer to the documentation shipped with the server.


To install the Cisco CallManager software, you must perform the following procedures in the order indicated:

Before You Begin

Connecting a Monitor, Keyboard, and Mouse to the Server

Starting the Cisco CallManager Release 3.0 Installation Utility

Entering the Server Configuration Data

Completing the Cisco CallManager 3.0 Installation

Logging On to the Server

Installing the Compaq Driver Update

The entire installation process takes 60 to 90 minutes per server.

Before You Begin

Beginning with Release 3.0, Cisco CallManager provides support for distributed call processing. You can distribute the call processing load for your system across multiple Cisco CallManagers as a single cluster. A cluster is a set of Cisco CallManagers that share the same database.

In a Cisco CallManager distributed system, one server maintains the master, or publisher, database and all others in the cluster maintain subscriber databases. Subscriber databases are backup copies of the master database. During normal operation, all of the Cisco CallManagers in the cluster read data from and write data to the publisher database. Periodically, the subscriber copies of the database are updated automatically from the publisher database.

Before you begin installing Cisco CallManager for a distributed call processing system, you should plan your system configuration. At a minimum, you should determine how many Cisco CallManager servers the cluster will contain, which server will house the publisher database, and where backup tasks will be performed. Additional planning should include a strategy for distributing the devices (such as phones or gateways) among the Cisco CallManagers in the cluster to achieve the type of distribution you want. For more information on planning a Cisco CallManager distribution system, refer to Part 1, "System Description", in the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.

When configuring a subscriber database server, the server you are installing must be able to connect to the publishing database server during the installation. This connection is necessary because the publisher database is copied from the publisher server to the local drive on the subscriber server. This means that the publisher database server for that cluster must be installed, connected to the network, and configured properly, and the subscriber server you are configuring must be able to connect to it.


Caution If you are installing Cisco CallManager on an existing server, make sure the hard drive does not contain any non-default partitions. If a non-default partition exists, you must delete it before beginning the installation procedure.


Caution If you are configuring a subscriber database server, the publishing database server for that cluster must be installed, connected to the network, and configured properly to work as a distributed system. If the publisher server cannot be authenticated during the installation for any reason, the installation will not continue. For more information on configuring the publishing database server, refer to Part 1, "System Description", in the Cisco CallManager Administration Guide or to online help in the Cisco CallManager application.


Caution Before you begin installing multiple servers in a cluster, you must have a name resolution method in place, such as Domain Name System (DNS), Windows Internet Name Server (WINS), or local naming using a configured lmhosts file. If you use DNS, make sure the DNS server contains a mapping of the IP address and hostname of the server you are installing before you begin the installation. If you use local name resolution, the lmhosts file must be updated on the existing servers in the cluster before beginning the installation on the new subscriber server, and then the same information must be added to the lmhosts file on the new server during installation, as instructed in the procedure.

To begin the installation process, you insert the Operating System Installation and Recovery CD-ROM into the CD-ROM drive and then power up the server. With the Operating System Installation and Recovery CD-ROM in place, the server automatically begins installing the operating system, Cisco CallManager, and other included software. During this initial installation process, you are prompted to enter important configuration information about the server, such as the server name and IP address. You can complete the initial power-up more efficiently if you gather all the necessary configuration information before beginning the installation process. Configuration information consists of the following:

Cisco Product Key

You are supplied with a Cisco Product Key when you purchase a Cisco IP Telephony product. The product key is based on a file encryption system. It allows you to install only the components you have purchased, and it prevents other supplied software from being installed for general use. The product key is comprised of alphabetical letters only. It contains no numbers or special characters. The product key is printed in Table 2 on page page 9 in the "Before You Begin" section and in each step procedure where you are prompted to enter it.

User and organization name

A user and organization name are required to register the software product you are installing.

Computer name

Assign a name for this server. The name must be a unique network name of 15 characters or less. It may contain alpha and numeric characters, hyphens (-), and underscores (_), and it must begin with an alphabetical character. You should follow your local naming conventions, if applicable.


Caution Due to a restriction in Microsoft SQL Server 7.0, the Windows 2000 computer name cannot be changed after installation. If the computer name is changed, the server must be reinstalled. Make sure the name you assign is the permanent server name.

Workgroup

This entry records the name of the workgroup of which this computer is a member. A workgroup is a collection of computers that have the same workgroup name. This entry must be 15 characters or less and follows the same naming conventions as the computer name.

Domain suffix

The Domain Name System (DNS) domain suffix must be entered in the format "mydomain.com" or "mycompany.mydomain.com". If you are not using DNS, use a fictitious domain suffix, such as cisco.com.

TCP/IP properties

Assign an IP address, subnet mask, and default gateway. The IP addresses you assign are permanent properties and should not be changed after installation.


Note Cisco recommends using static IP information instead of DHCP because the server must have a fixed IP address so that the Cisco IP phones can register with Cisco CallManager when you plug the phones into the network. If DHCP is used, the server may be assigned a different IP address in the event that the server is disconnected from, and then reconnected to, the network. Returning the server to its original IP address would then require reprogramming the IP addresses of the other devices on the network.


Domain Name System (DNS)

Identify a primary DNS server. This is an optional field.


Note By default, the phones attempt to connect to the Cisco CallManager using DNS. Therefore, if you use DNS, make sure the DNS contains a mapping of the IP address and the fully qualified domain name of the Cisco CallManager server. If you do not use DNS, the server's IP address must be used instead of a server name in order for the phones to register with the Cisco CallManager. If you choose not to use DNS, install Cisco CallManager as normal, and then refer to the "System Configuration" section in the Cisco CallManager Administration Guide or online help in the Cisco CallManager application for information on changing the server name.


Database server

Determine if this server will be configured as a publishing database server or a subscriber database server. This is a permanent selection. If you want to reassign the database server type at a later date, you must reinstall the Cisco CallManager server.

If you are configuring a subscriber database server, the publishing database server must already be installed, configured, and on the network. You must supply the name of the publishing database server and a username and password with administrator access rights on that server.

Backup server or target

Determine if this server will be configured as a Backup Server or a Backup Target.

The Backup Server is the server that actually performs the backup operation. It stores the backup data in the local directory, local tape drive, or network destination that you specify. If you select a network area as the Backup Server, the directory must be shared in Windows 2000. A Backup Target is a server that contains the data to be backed up. You can select more than one Target, but only one Server. If a server is configured as a Backup Server, it will automatically be added to the backup target list.

New password for the system administrator

At the end of the installation you are asked to supply a new password for the system administrator.


Note Cisco CallManager Release 3.0 and later supports password protection.


Table 2 shows the configuration information required for installing software on your server. All fields are required unless otherwise noted. Gather this information for each Cisco CallManager server you are installing in the cluster. Make copies of this table and record your entries for each server in a separate table. Have the completed lists with you when you begin the installation.

Table 2 Configuration Data for Cisco Media Convergence Server

Configuration Data
Your Entry

Cisco Product key

BTOO VQES CCJU IEBI

User name

 

The name of your organization

 

Computer name

 

Workgroup

 

DNS Domain suffix. (The DNS domain suffix must be entered in the format "mydomain.com" or "company.mydomain.com". If you are not using DNS, use a fictitious domain suffix, such as cisco.com.)

 

Current time zone, date, and time

 

DHCP parameters

Cisco recommends that you program a fixed IP address in TCP/IP properties for the server instead of using DHCP.

TCP/IP properties (required if DHCP is not used)

IP address

Subnet mask

Default gateway

 

Primary DNS server (optional)

 

Database server (specify one)

Publisher

Subscriber

If you are configuring a subscriber server, you must supply the username and password of the publishing database server:

username of publisher

password of publisher

 

Backup (specify one or both)

Server

Target

 

New system administrator password

 

Connecting a Monitor, Keyboard, and Mouse to the Server

A monitor is not supplied with any of the Cisco Media Convergence Servers. The MCS-7820 and MCS-7822 include a keyboard and mouse, but the MCS-7830 and MCS-7835 do not. You must supply a monitor, and if necessary, a keyboard and mouse, to use during initial startup and configuration of the Cisco Media Convergence Server and Cisco CallManager.

Plug the mouse and keyboard into the standard mouse and keyboard connectors marked on the back of the server. Plug the monitor cable into the monitor connector on the back of the server.

Starting the Cisco CallManager Release 3.0 Installation Utility

During the MCS QuickBuilder installation process, the server performs several system reboots.


Caution Before installation, the server's hard drive and all data and configuration information, if present, is erased. If you are installing Cisco CallManager on an existing server and you want to preserve the data on the hard drive, do not perform this procedure.


Note If you want to migrate your existing Cisco CallManager Release 2.4 data from Release 2.4 to Release 3.0, see the "Migrating from Cisco CallManager Release 2.4 to Release 3.0" section


To perform a new installation, make sure the server is turned off and perform the following steps:


Step 1 If necessary, connect a monitor, keyboard, and mouse to the server as described in "Connecting a Monitor, Keyboard, and Mouse to the Server" section.

Step 2 Locate the Operating System Installation and Recovery CD-ROM supplied with the server, and insert it into the CD-ROM drive.

Step 3 Power up the server.


Caution During installation, the server reboots several times. Do not power off the server any time during this process, unless instructed. Any unexpected power interruption during the installation process could prevent proper completion of the configuration and might prevent the operating system from restarting.

Step 4 The Cisco Media Convergence Server QuickBuilder welcome window opens. Click Next.

Step 5 If your server is new and has never had Cisco CallManager 3.0 installed on it, go to Step 6. If your server is not new (the hard drive is not blank), the Type of Installation window opens. Select New Installation or Server Replacement and then click Next.

Step 6 The next window displays a warning that your configuration and data will be overwritten. Click Next.

Step 7 When a message prompts you to cycle the system power, turn the server off. Wait 10 seconds, and then power up the server. The startup may take several minutes.

Step 8 If the New Installation and Replacement window opens, click Next.

Step 9 The Configuration Process window opens with a message about hardware detection. Click Next. The system reboots automatically.

Step 10 If you are installing the MCS-7820, MCS-7822, or MCS-7830, go to Step 11. If you are installing the MCS-7835, a second Configuration Process window opens with a message about conducting an initial hardware configuration. Click Next. The system reboots again automatically.

Step 11 Enter your product key BTOO VQES CCJU IEBI, then click Next.


Note The Cisco product key is comprised of alphabetical letters only. It contains no numbers or special characters. It is based on a file encryption system that allows you to install only the components you have purchased, and it prevents other supplied software from being installed for general use.


Step 12 The Cisco MCS Server License Agreement window opens. Read through the contents of the agreement. If you consent to the terms of the agreement, click I Agree. If you do not consent, you must terminate the installation by clicking Exit.

Step 13 Depending on the state of your server, the Server Replacement Option window may or may not appear. If it does appear, make sure the I am recovering a system from backup check box is deselected, and then click Next. If this window does not appear, go to Step 14.

Step 14 Click Next on the Ready to Complete Installation window. This process takes about five minutes to complete.

Step 15 When prompted by the system to do so, eject the CD-ROM and press any key to reboot the server.


Note If the CD-ROM is not ejected and the server reboots, the installation process loads again and will start over from the beginning.



Continue configuring the server by completing the steps in "Entering the Server Configuration Data" section.

Entering the Server Configuration Data

After Windows 2000 starts up, you are prompted to enter configuration information using the data you collected in Table 2. Complete the following steps to configure each server:


Step 1 The Cisco MCS Configuration Wizard begins. Click Next to continue.

Step 2 Enter your user name and the name of your organization, then click Next.

Step 3 Enter a computer name, workgroup, and DNS domain suffix and click Next.


Note The computer name must be a unique network name of 15 characters or less. It may contain alpha and numeric characters, hyphens (-), or underscores (_), and must begin with an alphabetical character. The workgroup name follows the same naming conventions as the computer name.



Caution Due to a restriction in Microsoft SQL Server 7.0, the Windows 2000 computer name cannot be changed after installation. If the computer name is changed, the server must be reinstalled. Make sure the name you assign is the permanent server name.


Note The DNS domain suffix must be entered in the format "mydomain.com" or "company.mydomain.com". If you are not using DNS, use a fictitious domain suffix, such as cisco.com.


Step 4 Select the appropriate time zone for the server, then click Next.

Step 5 Set the current date and time, then click Next.

Step 6 Cisco recommends that you select Enter static IP information when prompted about the method used to configure the IP information. Click Next.


Note Cisco recommends using static IP information because the server must have a fixed IP address so that the Cisco IP phones can register with Cisco CallManager when you plug the phones into the network. If DHCP is used, the server may be assigned a different IP address in the event that the server is disconnected from, and then reconnected to, the network. Returning the server to its original IP address would then require reprogramming the IP addresses of the other devices on the network.


Step 7 Enter the server IP address, subnet mask, and default gateway in the appropriate fields, and then click Next.


Caution If you are installing multiple servers in a cluster, you must have a name resolution method in place. If you are not using DNS or WINS, you must configure local name resolution by updating the lmhosts file with IP address and hostname information for every server in your cluster, as instructed in Step 9 below.

Step 8 If you are using DNS or WINS, enter the IP addresses of the primary DNS server and primary WINS server. If you are not using DNS, leave the DNS and WINS fields empty. Click Next.

Step 9 If you did not enter DNS or WINS server information in the previous window, and if you are installing multiple servers in a cluster, you must configure local name resolution by updating the lmhosts file so that it contains a mapping of the IP address and hostname of each server in the cluster. Perform the following steps to configure the lmhosts file:

a. Click Edit lmhosts. Notepad loads and opens the lmhosts file.

b. At the end of the file, append a new line for each remote server in the cluster. Use the following format, entering a space or tab character between the IP and hostname:

<IP address> <hostname>

For example:

172.16.0.10 dallascm1

c. Choose File > Save.

d. Exit Notepad by choosing File > Exit.

e. On the configuration wizard window, click Next to continue.

Step 10 Click Next to complete the configuration process.

The server begins an installation and reboot process that takes about six minutes to complete


Continue configuring the server by following the steps in "Completing the Cisco CallManager 3.0 Installation" section.

Completing the Cisco CallManager 3.0 Installation

The last part of the installation process installs Cisco CallManager and related applications. Perform the following steps to complete the installation:


Step 1 When prompted to do so, insert the Cisco CallManager 3.0 Installation and Recovery CD-ROM. The installation script will continue loading from the CD-ROM automatically.

Step 2 Click Next at the Welcome to the Cisco CallManager Installation Wizard window.

Step 3 On the CallManager Components window, select the services you wish to activate in this initial installation, then click Next. When Cisco CallManager services are activated, they are placed in a stopped state. To start services after the installation is complete, refer to the "Control Center" chapter in the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.


Note The Cisco IP Voice Streaming Application contains the Media Termination Point (MTP) and Conference Bridge services.



Note To add or remove services later, see the "Activating Cisco CallManager Services" section.


Step 4 If you have CiscoWorks2000 installed on a server on your network, select the Configure CiscoWorks2000 Syslog Collector check box and enter the domain host name in the form "myserver.mydomain.com." Otherwise, make sure it is deselected. Click Next.


Caution If you are configuring a subscriber database server, the server you are installing must be able to connect to the publishing database server before the installation can continue. This connection is necessary because the subscriber server attempts to connect to the publisher server so that 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 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 If the server you are configuring will contain the publisher database, select Create a publishing database on this machine.

If a publisher database already exists and you are configuring a subscriber database server, select Specify a server with an existing publishing database and enter the computer name of the publishing database server.

Click Next.


Note The publisher database is the master database for all servers in the cluster. Subscriber databases are copies of the publisher database and are maintained on all servers except the publishing database server.


Step 6 If you selected Create a publishing database on this machine in the previous step, go to Step 7. If you selected Specify a server with an existing publishing database, an authentication window opens and prompts you to enter passwords for the Administrator and SA (the SQL Server system administrator user) accounts on the publishing database server. Enter the passwords in the appropriate fields as prompted, and then click Next. The system connects to the publishing database server.

Step 7 You have completed the configuration of Cisco CallManager and the database server. The Cisco CallManager and other included software is ready to be installed. Click Next. This part of the installation takes about 30 minutes.

Step 8 The Cisco MCS 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.

The Backup Server is the server that 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 will automatically be added to the backup target list.

A Backup Target is a server that contains data to be backed up. You can select more than one Target, but you can select only one Server.

Select either Server or Target, and then click OK.


Note Cisco strongly recommends that you use the Cisco MCS Backup Utility to perform backups and that no third party backup software is used. However, if you do not want to use the Cisco MCS Backup Utility, complete the installation as instructed, and then stop the service called "stiBack for Cisco MCS". To stop the service, select Start > Run, enter services.msc /s, select the service in the main window, and click Stop Service.


Step 9 On the Backup Utility Configuration window, add the name of any additional servers 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. You are prompted to enter a username and password with administrator access rights on the remote server, and 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 10 Select the Destination tab. Select a destination location where the backup data will be stored. You must select a destination for backups to be performed. There is no default destination setting.


Note If you select 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 on the directory folder icon you want to share, click Sharing..., click Share this folder, and then click OK


Step 11 Select 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 type in the path and directory name or select 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...


Note Tape drives are available on the MCS-7835 only.


Step 12 Select the Schedule tab.

Step 13 Select the days and times you want the backup to run. The default is 2:00 am Tuesday through Saturday. You can also select the length of the system log in days. Then click OK.


Caution Cisco CallManager backups should be timed to occur during off-peak hours because CPU utilization is high during the backup process.

Step 14 Click OK to save your settings and exit the Backup Utility Configuration. For more information on the Backup Utility, see the "Performing Backup and Restore Procedures" section.


Caution When entering passwords for the local Administrator and SA (SQL Server system administrator) accounts in the next steps, do not use the apostrophe (`).

Step 15 You are prompted to enter a new password for the local Administrator account. Type the new password in the New Password field, and then retype it in the Retype Password field. Click OK.

Step 16 You are prompted to enter a new password for the SA (SQL Server system administrator) account. Type a new password of at least 5 characters in the New Password field, and then retype it in the Retype Password field. Click OK.


Note Do not lose or forget this password. If you do, you will not be able to reconfigure the server.


Step 17 A message indicates that the password was changed successfully. Click OK.

Step 18 Eject the CD-ROM from the CD-ROM drive and click Yes when prompted if you want to reboot the system now.



Caution After you have completed this portion of the Cisco_CallManager Release 3.0 installation, do not insert the Operating System Installation and Recovery CD-ROM again unless you want to reinstall. Inserting the CD-ROM after installation may cause the Administrator password to be reset to a blank password. If this occurs, Refer to the procedure in "Changing Passwords for CCMAdmin and SQLSvc Accounts" section.

Logging On to the Server

After you complete the server installation and Windows 2000 has rebooted, you can log on to the server. To log on:


Step 1 Press Ctrl+Alt+Del to display the logon window.

The logon window should already contain the user name Administrator.

Step 2 Type the new password for the Administrator account, and then click OK.

Installing the Compaq Driver Update

Installing the Compaq Driver Update significantly improves the performance of your server and should be run on all servers after the Cisco CallManager installation is complete. Perform the following steps to run the Compaq Driver Update:


Step 1 Double-click the Compaq Driver Update Setup icon located on the desktop.

Step 2 The packages to be installed are listed. Click Install.

Step 3 When the process is complete, click Close.

Step 4 Restart your server.


Performing Post-Installation Tasks

When you install and configure a Cisco Media Convergence Server, Cisco CallManager is installed automatically. However, you must set some configuration parameters for Cisco CallManager and perform other post-installation tasks before you can begin using it. These tasks are performed for each server you install, and can be completed before or after the other servers in the cluster are installed.

This section explains how to perform the following operations:

Changing Passwords for CCMAdmin and SQLSvc Accounts

Configuring Auto Registration

Configuring DNS

Configuring the Database

Activating Cisco CallManager Services

Changing the SNMP Community Name

Installing Compaq Insight Management Agents

After you have performed these tasks and your Cisco CallManager is operational, you should back up your Cisco CallManager data. For information on backing up Cisco CallManager data, see the "Backing Up the Cisco CallManager Data" section.

Changing Passwords for CCMAdmin and SQLSvc Accounts

During the Cisco CallManager Release 3.0 installation, two user accounts are created: CCMAdmin and SQLSvc.

At installation, these user accounts are set up with a default password. To eliminate a security risk, the passwords should be changed after installation. However, you should set the same password for all the CCMAdmin accounts and the same password for all the SQLSvc accounts for each server in the cluster.

CCMAdmin

The CCMAdmin user provides a common administrator login account for all Cisco CallManagers in the cluster. For example, if you are logged in as CCMAdmin, you can view all the services in all the servers in the cluster in one Control Center window. In order to have access to all servers in the cluster simultaneously, the password for CCMAdmin must be identical on every server in the cluster.

Perform the following steps to change the CCMAdmin password:


Step 1 Select Start > Programs > Administrative Tools > Computer Management.

Step 2 Select the Users folder located in the following path: System Tools/Local Users & Groups. The users are displayed in the main window.

Step 3 Right-click on the name of the user whose password you want to change, and select Set Password.

Step 4 Enter the new password in the New Password and Confirm Password fields, and click OK.

SQLSvc

The SQLSvc account is reserved for use only by the Microsoft SQL Server service. It is the core account used for server to server interaction by the CallManager system. For the service to function properly, the password for the SQLSvc account must be identical on all servers in the cluster.

The default SQLSvc password that is set up during installation is an encrypted password that is unique to the cluster. It is identical on all servers in the cluster. If you change the password, make sure the passwords are identical on all servers in the cluster.


Caution Each time you upgrade Cisco CallManager, the SQLSvc passwords are reset to the original default. To retain your custom password, you must change the passwords again after each upgrade on all servers in the cluster.

Perform the following steps to change the SQLSvc password:


Step 1 Select Start > Programs > Administrative Tools > Computer Management.

Step 2 Select the Users folder located in the following path: System Tools/Local Users & Groups. The users are displayed in the main window.

Step 3 Right-click SQLSvc and select Set Password.

Step 4 Enter the new password in the New Password and Confirm Password fields, and click OK.

Step 5 A window confirms that the password has been changed. Click OK.

Step 6 Select on the Services icon located in Services and Applications. The services are displayed in the main window.

Step 7 Right-click MSSQLServer and select Properties.

Step 8 Select the Log On tab.

Step 9 Enter the same password as in Step 4 in the Password and Confirm Password fields, and click OK.

Step 10 Right-click SQLServerAgent and select Properties.

Step 11 Select the Log On tab.

Step 12 Enter the same password as in Step 4 in the Password and Confirm Password fields, and click OK.

Step 13 Close the Computer Management window.

Step 14 Select Start > Programs > Administrative Tools > Component Services.

Step 15 Select the COM+Applications folder located in the following path: Component Services/Computers/My Computer. The applications are displayed in the main window.

Step 16 Right-click DBL and select Properties.

Step 17 Select the Identity tab.

Step 18 Enter the same password as in Step 4 in the Password and Confirm Password fields, and click OK.

Step 19 Right-click DBL and select Shut Down.

Step 20 Right-click DBL and select Start.

Step 21 Close the Computer Management window.


Configuring Auto Registration

Cisco CallManager can be configured to assign directory numbers automatically to the phones. Directory numbers are assigned sequentially starting with the number you specify as the starting directory number and ending with the number you specify as the ending directory number. For example, if the range of directory numbers you specify is 1000 through 2000, the phones are assigned directory numbers of 1000, 1001, 1002, and so on until the ending directory number of 2000 is reached. For more information about configuring Auto Registration, refer to the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.

Configuring DNS

Although DNS or WINS should be used during the installation of multiple Cisco CallManagers, Cisco strongly recommends against using a DNS name resolution server in a Cisco CallManager production environment unless you are confident in the reliability and availability of your DNS server and network structure.

If a DNS server is used, your call processing system is dependent on the accessibility of that server. For example, if the DNS server goes down or the connection between it and the Cisco CallManager is broken, the phones must rely on cached server name information. If the phones have been reset and have lost their cached information, they might be unable to resolve the DNS name of the Cisco CallManager server, and call processing may be interrupted.

To prevent this situation, Cisco recommends that you disable DNS after installation, and change the Cisco CallManager server name to an IP address using the procedures that follow.


Caution If you want to use DNS on your Cisco CallManager system, make sure that the Reverse DNS Lookup function is configured and enabled. This is necessary regardless of whether you use the IP address or the DNS name for your Cisco CallManager server name.

To disable DNS after installing Cisco CallManager, perform the following steps:


Step 1 Select Start > Settings > Network and Dial-up Connections.

Step 2 Right-click on Local Area Connection and select Properties.

Step 3 Select Internet Protocol (TCP/IP).

Step 4 Click Properties.

Step 5 Click Advanced.

Step 6 Select the DNS tab.

Step 7 Remove any entries in the DNS server addresses list by selecting the entry and clicking Remove.

Step 8 Deselect the Register the connection's address with DNS check box.

Step 9 Click OK.


To change the Cisco CallManager server name to the IP address, perform the following steps:


Step 1 Select Start > Programs > Cisco CallManager 3.0 > CallManager Administration and log in with administrator privileges.

Step 2 From the CallManager Administration window, select System > Server.

Step 3 From the list of Cisco CallManagers on the left, select the server you are configuring.

Step 4 Edit the contents of the DNS or IP Address field so that it contains the server's IP address. Click Update.


Configuring the Database

After installing Cisco CallManager, you can use Cisco CallManager Administration to begin configuring the database. The Cisco CallManager database contains information and parameters relating to the system as a whole, to connected devices, and to individual users. For more information about configuring the Cisco CallManager database, refer to the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.

Activating Cisco CallManager Services

Cisco CallManager services are installed on your server during the installation process, but only those that you selected during the installation were activated.


Caution Do not deactivate the Cisco CallManager service using the following procedure. If it is inadvertently deactivated, contact the Cisco Technical Assistance Center (TAC). See the "Technical Assistance Center" section for more information.

To activate additional Cisco CallManager services, or to deactivate existing services, perform the following steps:


Step 1 Select Start > Programs > Cisco CallManager > Cisco CallManager Service Configuration.

Step 2 Select the check box for each Cisco CallManager service you want to activate. If a service is currently activated and you deselect it, it is shut down, removed from the service registration table, and unavailable for use. Click Apply.

Step 3 Click Exit.

Step 4 After you activate a service, it must be started. For information on starting services, refer to the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.


Changing the SNMP Community Name

The Windows 2000 SNMP agent is a Windows NT-based service which is enabled when the operating system is installed. The Cisco CallManager SNMP agent supplements the Windows 2000 SNMP agent by acting as an extension agent.


Caution The Windows 2000 SNMP agent provides security through the use of community names and authentication traps. The default name "public" is universally accepted in all SNMP implementations. You should change this name to limit access.

To change the SNMP agent community name:


Step 1 Select Start > Programs > Administrative Tools > Services.

Step 2 Right-click on SNMP Service and select Properties.

Step 3 Select the Security tab, then click Edit, enter the new community name, and click OK.


Installing Compaq Insight Management Agents

The Compaq Insight Management Agent is a SNMP agent extension that allows you to monitor and manage the specific components of your server, such as CPU, virtual memory, and disk usage. It also monitors server temperature, fan status, power supplies, and NIC information. It should be installed only if your system uses CiscoWorks2000.

Perform the following steps to run the Compaq Insight Management Setup:


Step 1 Double-click the Compaq Insight Management Agents Setup icon located on the desktop.

Step 2 The packages to be installed are listed. Click Install.

Step 3 When the process is complete, click Close.


Performing Backup and Restore Procedures

Cisco CallManager comes with a backup and restore utility called Cisco MCS Backup and Restore. This utility provides a reliable and convenient way to perform regularly scheduled automatic backups of your Cisco CallManager data.


Note Cisco strongly recommends against using any third party backup utilities.


In the unlikely event of a server failure, or if a server is being replaced, you can use the Installation and Recovery CD-ROMs and the most recent backup information to restore the Cisco CallManager server. The Recovery option on the Installation and Recovery CD-ROMs restores the operating system, Cisco CallManager, and other included software, and then restores the backup data using the Cisco MCS Restore Utility. Of course, you must have a good backup of the Cisco CallManager data for the recovery to be successful.

This section describes procedures for backing up the Cisco CallManager data and recovering from hardware and software failures. The following topics are discussed:

Backing Up the Cisco CallManager Data

Performing a Recovery on the Same Cisco CallManager Server

Performing a Recovery on a Replacement Cisco CallManager Server

Restoring the Cisco CallManager Data Only

Performing Post-Recovery Tasks

Backing Up the Cisco CallManager Data

The Cisco CallManager database contains all the information you configure with Cisco CallManager Administration and the database is updated each time you make a change. Directory and configuration information is also updated periodically. Cisco strongly recommends that you make a backup of the Cisco CallManager database, configuration, and directory information using the Cisco MCS Backup Utility every time you make changes through Cisco CallManager Administration. The Cisco MCS Backup Utility is designed to automatically back up the following information:

Cisco CallManager database on SQL Server 7

DC Directory LDAP directory

SAenvProperties.ini, if present

Computer name

Server workgroup

Server IP address and subnet mask

To configure the Cisco MCS Backup Utility, you select a destination location and one or more target servers. The destination location can be a local directory, a local tape drive, or a network directory. Cisco strongly recommends that you specify a tape drive or a network directory as the backup destination, and not a local directory. If you select 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 on the directory folder icon you want to share, click Sharing..., click Share this folder, and then click OK.

Your Cisco CallManager cluster has only one publisher database, and it is not necessary to back up multiple servers containing backup copies of the same database. However, you can configure the Cisco MCS Backup Utility to back up more than one Cisco MCS server, such as publishing database servers of other Cisco CallManager clusters or uOne servers.

By default, all data backed up from the target servers in the target list is stored in one file called MCS.tar. When you restore, you select and restore data from one server at a time.


Note Each time a backup is performed, the existing MCS.tar file is overwritten with the new backup file. If you want to retain previous backup data, you must archive or rename the existing MCS.tar file before the next backup is performed.


Backups occur automatically according to the settings in the Schedule window of the Cisco MCS Backup Utility. However, you can also perform a backup at any time, as instructed in the procedure that follows.

Perform the following steps to back up the Cisco CallManager data:


Step 1 Click on the MCS Backup Utility icon in the Windows 2000 system tray and select View status. If the MCS Backup Utility icon is not in the Windows 2000 system tray, select Start > Programs > Cisco MCS Backup > Cisco MCS Viewer, then click on the MCS Backup Utility icon in the Windows 2000 system tray and select View status. Verify that the current status is "Waiting until <time> on <date>". You can keep this window open to view the progress of the Backup Utility.

Step 2 Click on the MCS Backup Utility icon in the Windows 2000 system tray and select Configure settings.

Step 3 Verify that the servers listed in the target field are the ones you want to include in this backup. If necessary, add additional targets by clicking Add and following the online instructions. 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. Enter a username and password with administrator access rights on the remote server, and 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 4 Click the Destination tab. Make sure that the destination directory or tape device is configured.


Note Tape drives are available on the MCS-7835 only.


Step 5 Click the Schedule tab. Select the days and times when you want an automatic backup to occur. The default is set to 2:00 am Tuesday through Saturday. Click OK


Caution Cisco CallManager backups should be timed to occur during off-peak hours because CPU utilization is high during the backup process.

Step 6 If you want to start a backup now, click on the MCS Backup Utility icon in the Windows 2000 system tray and select Start backup now.

Step 7 The Backup Utility Viewer displays the status of the backup operation by highlighting each task as it occurs. The information generated in the log window can be used to help identify problems. When the current status returns to "Waiting until <time> on <date>", the backup is complete. The last line in the log file indicates that the log is closed.


Performing a Recovery on the Same Cisco CallManager Server

This section describes how to restore the hard drive, operating system, software, and data onto the same Cisco Media Convergence Server in the event of a catastrophe.

The recovery utility performs an installation of the operating system, Cisco CallManager, and other included software, and then incorporates system recovery information. After this operation completes and the system restarts, the Cisco MCS Restore Utility prompts you to verify the location of the backup file (MCS.tar). Then it automatically executes a restore operation to restore the Cisco CallManager backup data from the specified tape or network directory.

It is not necessary to perform a recovery on a server that contains a subscriber database, since that database is only a backup copy of the publisher database. For subscriber servers, it is best to perform a new installation. See the "Performing a New Cisco CallManager Release 3.0 Installation" section for more information.


Caution You must have a good backup of the Cisco CallManager data stored on tape or on a network directory, not on the server's local directory.

IP information, computer name, and other configuration data is recovered from backup and populated in the data entry fields during the recovery process. However, as a security measure, you should make sure you have the configuration information for this server available before you begin. You can use Table 2 on page page 9 in the "Before You Begin" section to record the data.

To restore the operating system and software to the server, perform the following steps:


Step 1 Connect a monitor, keyboard, and mouse to the server as described in the "Connecting a Monitor, Keyboard, and Mouse to the Server" section.

Step 2 Locate the Operating System Installation and Recovery CD-ROM supplied with the server, and insert it into the CD-ROM drive.

Step 3 Shut down and restart the server by pressing Ctrl+Alt+Del. Click Shutdown, select Restart, and then click OK. If this method does not work, turn the server off. Wait 10 seconds, and then power up the server. The server takes several minutes to shut down and restart.


Note During recovery, the server reboots several times. Do not power off the server any time during this process, unless instructed. Any power interruption during the recovery process could prevent proper completion of the configuration and might prevent the operating system from restarting.


Step 4 The Welcome window opens. Click Next.

Step 5 Select Same Server Recovery, then click Next.

Step 6 The Perform a Recovery window displays a warning that all data will be overwritten except for recovery information. Click Next.

Step 7 Click Next on the Ready to Complete Installation window. This process takes about five minutes to complete.

Step 8 When prompted by the system to do so, eject the CD-ROM and press any key to reboot the server.


Note If the CD-ROM is not ejected and the server reboots, the installation process loads again and will start over from the beginning.


Step 9 The Cisco MCS Configuration Wizard begins. Click Next to continue.


Caution On the configuration entry windows that follow, the data entry fields are automatically populated with configuration data that was recovered from the backup. Do not change IP addresses or the computer name during the recovery.

Step 10 The user name and the name of your organization appear in the appropriate fields. Click Next.

Step 11 The computer name, workgroup, and DNS domain suffix appear. Click Next.

Step 12 The time zone for the server appears. Click Next.

Step 13 Reset the current date and time, then click Next.

Step 14 When prompted about how to obtain the IP information, make sure you select the same option that you selected in the original configuration. Click Next. If you selected Enter static IP information, the IP information for the server appears in the next window. Do not change any entries on this window. Click Next.

Step 15 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, the IP addresses fields are empty. Click Next.

Step 16 If your server was configured with local name resolution, you must update the lmhosts file so that it contains a mapping of the IP address and hostname of each server in the cluster. Perform the following steps to configure the lmhosts file:

a. Click Edit lmhosts. Notepad loads and opens the lmhosts file.

b. At the end of the file, append a new line for each remote server in the cluster. Use the following format, entering a space or tab character between the IP and hostname:

<IP address> <hostname>

For example:

172.16.0.10 dallascm1

c. Choose File > Save.

d. Exit Notepad by choosing File > Exit.

e. On the configuration wizard window, click Next to continue.

Step 17 Click Next to complete the configuration. The server begins an installation and reboot process that takes about six minutes to complete.

Step 18 When prompted to do so, insert the Cisco CallManager 3.0 Installation and Recovery CD-ROM. The installation script will continue loading from the CD-ROM automatically.

Step 19 Click Next at the Welcome to the Cisco CallManager Installation Wizard window.

Step 20 On the CallManager Components window, select the services you wish to activate, then click Next. When Cisco CallManager services are activated, they are placed in a stopped state. To start services after the installation is complete, refer to the "Control Center" chapter in the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.


Note The Cisco IP Voice Streaming Application contains the Media Termination Point (MTP) and Conference Bridge services.



Note To add or remove services later, see the "Activating Cisco CallManager Services" section.


Step 21 If you have CiscoWorks2000 installed on a server on your network, select the Configure CiscoWorks2000 Syslog Collector check box and enter the domain host name in the form "myserver.mydomain.com." Otherwise, make sure it is deselected. Click Next.

Step 22 Select Create a publishing database on this machine, and then click Next.

Step 23 You have completed the configuration of Cisco CallManager and the database server. The Cisco CallManager and other included software is ready to be installed. Click Next. This part of the recovery takes about 30 minutes.

Step 24 The Cisco MCS 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.

Select backup Server or Target. Make sure this selection matches the server's original configuration. Click OK.


Note Cisco strongly recommends that you use the Cisco MCS Backup Utility to perform backups and that no third party backup software is used. However, if you do not want to use the Cisco MCS Backup Utility, complete the installation as instructed, and then stop the service called "stiBack for Cisco MCS". To stop the service, select Start > Run, enter services.msc /s, select the service in the main window, and click Stop Service.


Step 25 When you are asked to confirm the backup settings on the following screens, click OK

Step 26 If you selected Backup Target in the previous window, go to Step 30. If you selected Backup Server, add the name of any additional servers you want to back up on the Backup Utility Configuration window 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. You are prompted to enter a username and password with administrator access rights on the remote server, and 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 27 Select the Destination tab.


Note If you select 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 on the directory folder icon you want to share, click Sharing..., click Share this folder, and then click OK


Step 28 Select Network directory, Local directory, or Tape device to specify where backup files will be backed up. To enter a network directory, you can type in the path and directory name or select 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, and then click Verify. In the tape device box, only tape drives configured in Windows NT or Windows 2000 appear. To add new devices, click Add device...

When you are finished configuring the destination, click OK.

Step 29 Click Yes to save your settings and exit the Backup Utility Configuration. For more information on the Backup Utility, see the "Performing Backup and Restore Procedures" section.

Step 30 You are prompted to enter a new password for the local Administrator account. Type the new password in the New Password field, and then retype it in the Retype Password field. Click OK.

Step 31 You are prompted to enter a new password for the SA (SQL Server system administrator) account. Type a new password of at least 5 characters in the New Password field, and then retype it in the Retype Password field. Click OK.


Note Do not lose or forget this password. If you do, you will not be able to reconfigure the server.


Step 32 A message indicates that the password was changed successfully. Click OK.

Step 33 Eject the CD-ROM from the CD-ROM drive and click Yes when prompted if you want to reboot the system now.

Step 34 After the system reboots, press Ctrl+Alt+Del to display the logon window.

The logon window should already contain the user name Administrator.

Step 35 Type the new password for the Administrator account, and then click OK.

Step 36 When the Cisco MCS Restore Utility window opens, select the location of the backup file that you want to restore by clicking Browse, selecting the file, and clicking Open. If the backup file is located on a network drive, you must enter the username and password for authentication and click Verify. When a message notifies you of successful authentication, click OK. Click Next to continue.


Note If the backup file is located on a network drive, the restore utility must authenticate with that server and verify that the backup file exists before the restore operation can continue.


Step 37 When the backup file is detected, the target files it contains display in the CallManager target list. Select the Cisco CallManager target that you want to restore. Enter the username and password for that server, and then click Verify. Once you have successfully authenticated to that server, click Next to continue.


Note By default, all data backed up from the target servers in the target list is stored in one file called MCS.tar. When you restore, you select and restore data from one target server at a time.


Step 38 You are warned that if you proceed you will overwrite the target server. Click Yes to continue.

Step 39 The restore utility restores the Cisco CallManager data. During the restore process, the Cisco MCS Restore Utility log window displays each event that occurs, and can be used to help identify errors. When the operation is complete, click OK to close the utility.

Step 40 Cisco CallManager services must be stopped and then restarted before Cisco CallManager is operational. For information on stopping and starting services, refer to the "Control Center" chapter in the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.

Step 41 You must reassign the SNMP community name. See the "Changing the SNMP Community Name" section for more information.

Step 42 If your Cisco CallManager system consists of a publisher and subscriber servers, the connections between the servers must be reset. Follow the procedures in the "Performing Post-Recovery Tasks" section to recreate the subscriptions.

Step 43 Verify the restored data.


Performing a Recovery on a Replacement Cisco CallManager Server

This section describes how to replace an existing or failed Cisco Media Convergence Server with a different one. You must have the Cisco CallManager data from the original server backed up on tape or in a network area so that it can be restored to the new server.

When one server is configured to replace an existing or failed server, the IP information and computer name of the original machine is employed on the new server. The operating system, Cisco CallManager, and other included software is installed as if it were a new installation, and then the Cisco CallManager backup data is restored on the new server.


Note You must have a good backup of the Cisco CallManager data stored on tape or on a network directory, not on the existing server's local directory.


When you perform a server replacement, the IP information, computer name, and other configuration data must be entered manually exactly as it was on the original server. Make sure you have the configuration information for this server available before you begin. You can use Table 2 on page page 9 in the "Before You Begin" section to record the data.

To replace an existing server, perform the following steps:


Step 1 Connect a monitor, keyboard, and mouse to the server as described in "Connecting a Monitor, Keyboard, and Mouse to the Server" section.

Step 2 Locate the Operating System Installation and Recovery CD-ROM supplied with the server, and insert it into the CD-ROM drive.

Step 3 Power up the server.


Note During this process, the server reboots several times. Do not power off the server any time during this process, unless instructed. Any unexpected power interruption during the installation process could prevent proper completion of the configuration and might prevent the operating system from restarting.


Step 4 The Cisco Media Convergence Server QuickBuilder welcome window opens. Click Next.

Step 5 If your server is new and has never had Cisco CallManager 3.0 installed on it, go to Step 6. Otherwise, select New Installation or Server Replacement on the Type of Installation window, and then click Next.

Step 6 The next window displays a warning that your configuration and data will be overwritten. Click Next.

Step 7 When a message prompts you to cycle the system power, turn the server off. Wait 10 seconds, and then power up the server. The startup may take several minutes.

Step 8 The New Installation and Replacement window opens. Click Next.

Step 9 The Configuration Process window opens. Click Next. The system reboots automatically.

Step 10 Enter your product key BTOO VQES CCJU IEBI, then click Next.


Note The Cisco product key is comprised of alphabetical letters only. It contains no numbers or special characters. It is based on a file encryption system that allows you to install only the components you have purchased, and it prevents other supplied software from being installed for general use.


Step 11 The Cisco MCS Server License Agreement window opens. Read through the contents of the agreement. If you consent to the terms of the agreement, click I Agree. If you do not consent, you must terminate the installation by clicking Exit.

Step 12 On the Server Replacement window, select the I am recovering a system from backup check box.

Step 13 Click Next on the Ready to Complete Installation window. This process takes about five minutes to complete.

Step 14 When prompted by the system to do so, eject the CD-ROM and press any key to reboot the server.


Note If the CD-ROM is not ejected and the server reboots, the installation process loads again and will start over from the beginning.


Step 15 The Cisco MCS Configuration Wizard begins. Click Next to continue.


Caution On the configuration entry windows that follow, the data entry fields must be populated with the same configuration data that was used on the server that is being replaced.

Step 16 Enter the user name and the name of your organization in the appropriate fields. Click Next.

Step 17 Enter the computer name, workgroup, and DNS domain suffix. Click Next.


Note The DNS domain suffix must be entered in the format "mydomain.com" or "company.mydomain.com". If you are not using DNS, use a fictitious domain suffix, such as cisco.com.


Step 18 Select the time zone for the server. Click Next.

Step 19 Set the current date and time, then click Next.

Step 20 When prompted about how to obtain the IP information, make sure you select the same option that you selected in the original configuration. Click Next. If you selected Enter static IP information, enter the IP information in the next window. Make sure the information you enter is the same data that was used on the original server. Click Next.

Step 21 If your server was configured with DNS or WINS, enter the IP addresses of the primary DNS server and primary WINS server. If you are not using DNS, leave the DNS and WINS fields empty. Click Next.

Step 22 If your server was configured with local name resolution, you must update the lmhosts file so that it contains a mapping of the IP address and hostname of each server in the cluster. Perform the following steps to configure the lmhosts file:

a. Click Edit lmhosts. Notepad loads and opens the lmhosts file.

b. At the end of the file, append a new line for each remote server in the cluster. Use the following format, entering a space or tab character between the IP and hostname:

<IP address> <hostname>

For example:

172.16.0.10 dallascm1

c. Choose File > Save.

d. Exit Notepad by choosing File > Exit.

e. On the configuration wizard window, click Next to continue.

Step 23 Click Next to complete the configuration process. The server begins an installation and reboot process that takes about six minutes to complete.

Step 24 When prompted to do so, insert the Cisco CallManager 3.0 Installation and Recovery CD-ROM. The installation script will continue loading from the CD-ROM automatically.

Step 25 Click Next at the Welcome to the Cisco CallManager Installation Wizard window.

Step 26 On the CallManager Components window, select the services you wish to activate in this initial installation, then click Next. When Cisco CallManager services are activated, they are placed in a stopped state. To start services after the installation is complete, refer to the "Control Center" chapter in the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.


Note The Cisco IP Voice Streaming Application contains the Media Termination Point (MTP) and Conference Bridge services.



Note To add or remove services later, see the "Activating Cisco CallManager Services" section.


Step 27 If you have CiscoWorks2000 installed on a server on your network, select the Configure CiscoWorks2000 Syslog Collector check box and enter the domain host name in the form "myserver.mydomain.com." Otherwise, make sure it is deselected. Click Next.

Step 28 Select Create a publishing database on this machine, and then click Next.

Step 29 You have completed the configuration of Cisco CallManager and the database server. The Cisco CallManager and other included software is ready to be installed. Click Next. This part of the installation takes about 30 minutes.

Step 30 The Cisco MCS 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.

Select backup Server or Target. Make sure this selection matches the server's original configuration. Click OK.


Note Cisco strongly recommends that you use the Cisco MCS Backup Utility to perform backups and that no third party backup software is used. However, if you do not want to use the Cisco MCS Backup Utility, complete the installation as instructed, and then stop the service called "stiBack for Cisco MCS". To stop the service, select Start > Run, enter services.msc /s, select the service in the main window, and click Stop Service.


Step 31 On the Backup Utility Configuration window, add the name of any additional servers 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. You are prompted to enter a username and password with administrator access rights on the remote server, and 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 32 Select the Destination tab.


Note If you select 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 on the directory folder icon you want to share, click Sharing..., click Share this folder, and then click OK


Step 33 Select Network directory, Local directory, or Tape device to specify where backup files will be backed up. To enter a network directory, you can type in the path and directory name or select 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, and then click Verify. In the tape device box, only tape drives configured in Windows NT or Windows 2000 appear. To add new devices, click Add device...

When you are finished configuring the destination, click OK.

Step 34 Click Yes to save your settings and exit the Backup Utility Configuration. For more information on the Backup Utility, see the "Performing Backup and Restore Procedures" section.

Step 35 The Cisco Product Activation window opens and prompts you to enter a new password for the local administrator account. Type the new password in the New Password field, and then retype it in the Retype Password field. Click OK.

Step 36 A second window opens and prompts you to enter a new password for the SA (SQL Server system administrator) account. Type a new password of at least 5 characters in the New Password field, and then retype it in the Retype Password field. Click OK.


Note Do not lose or forget this password. If you do, you will not be able to reconfigure the server.


Step 37 A message indicates that the password was changed successfully. Click OK.

Step 38 Eject the CD-ROM from the CD-ROM drive and click Yes when prompted if you want to reboot the system now.

Step 39 After the system reboots, press Ctrl+Alt+Del to display the logon window.

The logon window should already contain the user name Administrator.

Step 40 Type the new password for the Administrator account, and then click OK.

Step 41 After you log in to the server, the Cisco MCS Restore Utility window opens. Select the location and name of the backup file that you want to restore. Click Next.


Note The restore utility must verify that the file exists before the restore operation continues. If the file is not found, you must specify the correct destination location of the backup file in the Destination window.


Step 42 When the backup file is detected, the target files it contains display in the CallManager target list. Select the CallManager target that you want to restore, and then click Next.


Note By default, all data backed up from the target servers in the target list is stored in one file called MCS.tar. When you restore, you select and restore data from one target server at a time.


Step 43 You are warned that if you proceed you will overwrite the target server. Click Yes to continue.

Step 44 The restore utility restores the Cisco CallManager data. During the restore process, the Cisco MCS Restore Utility log window displays each event that occurs, and can be used to help identify errors. When the operation is complete, click OK to close the utility.

Step 45 Cisco CallManager services must be stopped and then restarted before Cisco CallManager is operational. For information on stopping and starting services, refer to the "Control Center" chapter in the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.

Step 46 You must reassign the SNMP community name. To change the SNMP community name, follow the procedure in the "Changing the SNMP Community Name" section.

Step 47 If your Cisco CallManager system consists of a publisher and subscriber servers, the connections between the servers must be reset. Follow the procedures in the "Performing Post-Recovery Tasks" section to recreate the subscriptions.

Step 48 Verify the restored data.


Restoring the Cisco CallManager Data Only

This section describes the process of restoring the Cisco CallManager data only. The operating system, Cisco CallManager, and other included software are not restored using this process. To restore the entire server, including operating system and software, see the following sections:

Performing a Recovery on the Same Cisco CallManager Server

Performing a Recovery on a Replacement Cisco CallManager Server

Perform the following steps to restore the Cisco CallManager database, directory information, and configuration files:


Step 1 Select Start > Programs > CallManager MCS Backup > Cisco MCS Restore.

Step 2 Select the location and name of the backup file that you want to restore, and then click Next.


Note By default, all data backed up from the target servers in the target list is stored in one file called MCS.tar. When you restore, you select and restore data from one server at a time.


Step 3 Select the target server where you want this backup to be restored. Click Next.

Step 4 You are warned that all existing data will be lost, and you will overwrite the target server. Click Next.

Step 5 During the restore process, the Cisco MCS Restore Utility log window displays each event that occurs. It can be used to help identify errors. When the restore is complete, click OK.

Step 6 Verify the restored data.


Performing Post-Recovery Tasks

Follow the procedure in this section if the server you are recovering contains the publisher database in a Cisco CallManager cluster.

When the publishing Cisco CallManager database of a cluster is recovered, the connections it had with the subscriber servers prior to recovery are broken. After the recovery is complete, you must do the following:

On each subscriber server, delete and then recreate the subscriptions

On the publisher server, reinitialize the subscriptions and start the replication snapshot agent

Use the following procedures to perform these steps.

On each subscriber server, perform the following steps to delete and recreate the subscriptions:


Step 1 Open SQL Server Enterprise Manager by selecting Start > Programs > Microsoft SQL Server 7.0 > Enterprise Manager.

Step 2 Select the Pull Subscriptions folder located in the following path: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Databases/<the database name you are restoring>

Step 3 In the main window, right-click the subscription name and select Delete. Click Yes to confirm.

Step 4 Right-click on the Pull Subscription folder, and select New Pull Subscription....

Step 5 The Welcome to the Pull Subscription Wizard window opens. Click Next.

Step 6 If your publisher server doesn't appear in the publication list, click Register Server. Enter the name of the publisher server in the Server field and select Use SQL Server authentication. Enter the SQL Server system administrator username (sa) and the password in the appropriate fields, and then click OK. When your server appears in the list, go to Step 7.

Step 7 Double click the publisher server and select the publication name that matches the database you are restoring. Click Next.

Step 8 In the Specify Sychronization Agent Login window, select By impersonating the SQL Server Agent account, and then click Next.

Step 9 In the Specify Immediate-Updating Subscriptions window, select Yes, make this an immediate-updating subscription, and click Next.

Step 10 Enter the password for the SA (SQL Server system administrator) user in the Password and Confirm password fields.

Step 11 In the Initialize Subscription window, select Yes, Initialize the schema at the Subsriber and click Next.

Step 12 In the Set Distribution Agent Schedule window, select Continuously and click Next.

Step 13 In the Start Required Services window, click Next.

Step 14 Click Finish.


On the publisher server, perform the following steps to reinitialize the subscriptions and start the replication snapshot agent:


Step 1 Open SQL Server Enterprise Manager by selecting Start > Programs > Microsoft SQL Server 7.0 > Enterprise Manager.

Step 2 Select the name of the Cisco CallManager database that you are restoring in the following path: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Databases/<the database name you are restoring>Publications.

Step 3 In the main window, right-click the subscription name and select Reinitialize all Subscriptions. Click Yes to confirm.

Step 4 Select the Snapshot Agents folder located in the following path: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Replication Monitor/Agents.

Step 5 Right click on the publication name that matches the database name you are restoring, then click Start.


Migrating from Cisco CallManager Release 2.4 to Release 3.0

This section describes how to upgrade your Cisco CallManager Release 2.4 to Release 3.0 and migrate the existing 2.4 database. This process also upgrades your operating system from Windows NT 4.0 to Windows 2000 and installs other included software.

Because Release 3.0 is engineered differently than Release 2.4 and has more built-in features, not all the data in your 2.4 configuration will translate to the 3.0 configuration. The relevant 2.4 data is migrated into 3.0 and any extraneous data is omitted. During the migration process, a log file is generated that will help you identify and understand any records that did not migrate. The log file also lists any error messages that occurred during the migration. The log file is located in the root directory of the local hard drive (c:\) and is called dbconvert.txt.


Note If you have Cisco CallManager Release 2.3, you must upgrade to Release 2.4 before you can perform the migration to Release 3.0.



Caution uOne data that is stored on the same server is not retained during this process. If you are running uOne data on this server, you should back up your uOne data onto a tape device or a network directory before performing this procedure. Refer to "The Automated Installer" chapter in the uOne Installation & Configuration, Corporate Edition 4.1 Manual.

You can perform a migration in one of two ways:

A Full Migration allows you to upgrade an existing Release 2.4 server to Release 3.0 and migrate the database as well as server and network configuration information.

A Database-Only Migration allows you to install a new server and migrate only the Release 2.4 data, stored on a network drive, onto the new server. This method can also be used to upgrade an existing Release 2.4 server, migrate the Release 2.4 data only, and assign a different computer name or IP than the original configuration.


Caution The Release 2.4 information is copied and imported into Release 3.0 during the migration. However, you should always have a good backup of the Cisco CallManager 2.4 data stored on tape or on a network directory before you begin a migration.


Note If you want to migrate your server back to Release 2.4 after performing the Release 3.0 migration, refer to the Configuration Notes for Cisco Media Convergence Server 7830 or the Configuration Notes for Cisco Media Convergence Server 7820 for details on restoring Cisco CallManager Release 2.4.


Full Migration

The Full Migration process backs up your Cisco CallManager Release 2.4 data and server configuration information onto a special partition that is reserved for recovery. It performs an installation of the Windows 2000 operating system, Cisco CallManager Release 3.0, and other included software, and then the Cisco CallManager Release 2.4 database is imported into SQL Server 7.

In a Full Migration, the IP information, computer name, and other configuration data is recovered from the 2.4 system and populated into the data entry fields during the recovery process. However, as a security measure, you should make sure you have the configuration information for this server available before you begin. You can use Table 2 on page page 9 in the "Before You Begin" section to record the data.


Caution During the migration process, call processing service is stopped. You should notify your users that telephone service will be interrupted during this time.

The two procedures below provide instructions for migrating the MCS-7830 and the MCS-7820, respectively.

Migrating the MCS-7830

To perform a full migration of Cisco CallManager Release 2.4 system to Release 3.0 on the MCS-7830, perform the following steps:


Step 1 If the server is not on, power it up and log in.

Step 2 Locate the Operating System Installation and Recovery CD-ROM supplied with the server, and insert it into the CD-ROM drive. The CD-ROM software loads automatically.

Step 3 If the procedure requires you to install a newer version of Java Virtual Machine (JVM), follow the online instructions.

Step 4 The Cisco MCS Migration Wizard window opens. Click Next.

Step 5 A message notifies you that call processing service will be stopped. Click Next.

Step 6 The next window displays a warning that the next step cannot be undone. Click Next to continue the migration.

Step 7 When a message appears indicating that this phase is complete, click Next to reboot the system.

Step 8 The Migration Process window opens. Click Next.

Step 9 A window opens warning you that your operating system volume will be replaced. Click Yes.

Step 10 Several windows and messages appear, and then the system reboots. This process takes several minutes.

Step 11 When the Product Key window opens, enter your product key BTOO VQES CCJU IEBI, and then click Next.


Note The Cisco product key is comprised of alphabetical letters only. It contains no numbers or special characters. It is based on a file encryption system that allows you to install only the components you have purchased, and it prevents other supplied software from being installed for general use.


Step 12 The Cisco MCS Server License Agreement window opens. Read through the contents of the agreement. If you consent to the terms of the agreement, click I Agree. If you do not consent, you must terminate the migration by clicking Exit.

Step 13 Click Next on the Ready to Complete the Migration window. This process takes about five minutes to complete.

Step 14 When prompted by the system to do so, eject the CD-ROM and press any key to reboot the server.


Note If the CD-ROM is not ejected and the server reboots, the installation process loads again and will start over from the beginning.


Step 15 After the system has rebooted, the Cisco MCS Configuration Wizard window opens. Click Next.


Note In the configuration windows that follow, the fields are automatically populated with configuration parameters that were retained from the Cisco CallManager Release 2.4 system. These entries can be accepted as they are or changed.


Step 16 The user name and the name of your organization should appear in the appropriate fields. Click Next.

Step 17 The values for the computer name and workgroup appear, but the DNS domain name was not migrated, and must be entered here. Click Next.


Note The DNS domain suffix must be entered in the format "mydomain.com" or "company.mydomain.com". If you are not using DNS, use a fictitious domain suffix, such as cisco.com.



Note If you want to change the computer name, remember that it must be a unique network name of 15 characters or less. It may contain alpha and numeric characters, the hyphen (-), and the underscore (_), but it must begin with an alphabetical character.



Caution Due to a restriction in Microsoft SQL Server 7.0, the Windows 2000 computer name cannot be changed after installation. If the computer name is changed, the server must be reinstalled. Make sure the name you assign is the permanent server name.

Step 18 Select the appropriate time zone for the server, then click Next.

Step 19 Set the current date and time, then click Next.

Step 20 Cisco recommends that you select Enter static IP information when prompted about the method used to configure the IP information. Click Next.


Note Cisco recommends using static IP information because the server must have a fixed IP address so that the Cisco IP phones can register with Cisco CallManager when you plug the phones into the network. If DHCP is used, the server may be assigned a different IP address in the event that the server is disconnected from, and then reconnected to, the network. Returning the server to its original IP address would then require reprogramming the IP addresses of the other devices on the network.


Step 21 Enter the server IP address, subnet mask, and default gateway in the appropriate fields, and then click Next.


Caution If the server you are migrating will be part of a cluster, you must have a name resolution method in place. If you are not using DNS, configure local name resolution by updating the lmhosts file with IP address and hostname information for every server in your cluster, as instructed in Step 22 below.

Step 22 If you are using DNS or WINS, enter the IP addresses of the primary DNS server and primary WINS server. If you are not using DNS, leave the DNS and WINS fields empty. Click Next.

Step 23 If you did not enter DNS or WINS server information in the previous window, and if the server you are migrating will be part of a cluster, you must configure local name resolution by updating the lmhosts file so that it contains a mapping of the IP address and hostname of each server in the cluster. Perform the following steps to configure the lmhosts file:

a. Click Edit lmhosts. Notepad loads and opens the lmhosts file.

b. At the end of the file, append a new line for each remote server in the cluster. Use the following format, entering a space or tab character between the IP and hostname:

<IP address> <hostname>

For example:

172.16.0.10 dallascm1

c. Choose File > Save.

d. Exit Notepad by choosing File > Exit.

e. On the configuration wizard window, click Next to continue.

Step 24 Click Next to complete the configuration process. The server begins an installation and reboot process that takes about six minutes to complete.

Step 25 When prompted to do so, insert the Cisco CallManager 3.0 Installation and Recovery CD-ROM.

Step 26 Click Next at the Welcome to the Cisco CallManager Installation Wizard window.

Step 27 On the CallManager Components window, select the services you wish to activate in this initial installation, then click Next. When Cisco CallManager services are activated, they are placed in a stopped state. To start services after the installation is complete, refer to the "Control Center" chapter in the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.


Note The Cisco IP Voice Streaming Application contains the Media Termination Point (MTP) and Conference Bridge services.



Note To activate or deactivate services later, see the "Activating Cisco CallManager Services" section.


Step 28 If you have CiscoWorks2000 installed on a server on your network, select the Configure CiscoWorks2000 Syslog Collector check box and enter the domain host name in the form "myserver.mydomain.com." Otherwise, make sure it is deselected. Click Next.

Step 29 Your Cisco CallManager Release 2.4 database will become a publisher Cisco CallManager Release 3.0 database after migration. On the CallManager Database Distribution window, select Create a publishing database on this machine.

If your server is the MCS-7830, do not select the I am migrating 2.4 data check box, since you are already using the full migration utility.

If your server is the MCS-7820, the I am migrating 2.4 data check box is automatically selected and the database path and filename field is automatically populated with the necessary information.

Click Next.

Step 30 You have completed the configuration of Cisco CallManager and the database server. The Cisco CallManager and other included software is ready to be installed. Click Next. This part of the installation takes about 30 minutes.

Step 31 After the system restarts, the Cisco MCS 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.

The Backup Server is the server that 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 will automatically be added to the backup target list.

A Backup Target is a server that contains data to back up. You can select more than one Target, but you can select only one Server.

Select either Server or Target, and then click OK.


Note Cisco strongly recommends that you use the Cisco MCS Backup Utility to perform backups and that no third party backup software is used. However, if you do not want to use the Cisco MCS Backup Utility, complete the installation as instructed, and then stop the service called "stiBack for Cisco MCS". To stop the service, select Start > Run, enter services.msc /s, select the service in the main window, and click Stop Service.


Step 32 On the Backup Utility Configuration window, add the name of any additional servers 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. You are prompted to enter a username and password with administrator access rights on the remote server, and 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 33 Select the Destination tab.


Note If you select 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 on the directory folder icon you want to share, click Sharing..., click Share this folder, and then click OK


Step 34 Select Network directory, Local directory, or Tape device to specify where backup files will be backed up. To enter a network directory, you can type in the path and directory name or select 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, and then click Verify. In the tape device box, only tape drives configured in Windows NT or Windows 2000 appear. To add new devices, click Add device...

When you are finished configuring the destination, click OK.

Step 35 Click OK to save your settings and exit the Backup Utility Configuration. For more information on the Backup Utility, see the "Performing Backup and Restore Procedures" section.

Step 36 You are prompted to enter a new password for the local Administrator account. Type the new password in the New Password field, and then retype it in the Retype Password field. Click OK.

Step 37 You are prompted to enter a new password for the SA (SQL Server system administrator) account. Type a new password of at least 5 characters in the New Password field, and then retype it in the Retype Password field. Click OK.


Note Do not lose or forget this password. If you do, you will not be able to reconfigure the server.


Step 38 A message indicates that the password was changed successfully. Click OK.

Step 39 Eject the CD-ROM from the CD-ROM drive and click Yes when prompted if you want to reboot the system now.

Step 40 After the system reboots, press Ctrl+Alt+Del to display the logon window.

The logon window should already contain the user name Administrator.

Step 41 Type the new password for the Administrator account, and then click OK.

Step 42 Cisco CallManager services must be stopped and then restarted before Cisco CallManager is operational. For information on stopping and starting services, refer to the "Control Center" chapter in the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.

Step 43 Verify the migrated data.


Migrating the MCS-7820

The MCS-7820 migration requires a floppy diskette to be inserted at the beginning of the migration process. The diskette is used to store information necessary to create the migration partition. Make sure you have a blank diskette on hand before you begin.

To perform a Full Migration of Cisco CallManager Release 2.4 system to Release 3.0 on the MCS-7820, perform the following steps:


Step 1 If the server is not on, power it up and log in with administrator privileges.

Step 2 Locate the Operating System Installation and Recovery CD-ROM supplied with the server, and insert it into the CD-ROM drive. The CD-ROM software loads automatically.

Step 3 If the procedure requires you to install a newer version of Java Virtual Machine (JVM), follow the online instructions.

Step 4 When prompted, click OK to restart the system. The CD-ROM ejects automatically.

Step 5 After the system restarts, you are prompted to insert the CD-ROM. Insert the CD-ROM again.

Step 6 Follow the online instructions to create a floppy diskette and format it. During this process, a partition is created using information saved on the diskette, and migration data is then stored on the partition.

Step 7 When you are prompted to remove the diskette and reboot the system, eject the diskette and press Ctrl+Alt+Del to restart the server.

Step 8 After the system restarts, insert the Operating System Installation and Recovery CD-ROM again. Follow the online instructions until the Cisco MCS Migration Wizard window opens.

Step 9 When the MCS Migration Wizard window opens, go to Step 4 on page page 35, and continue performing the remaining steps in the section "Migrating the MCS-7830".


Database-Only Migration

The database-only migration is achieved by performing a basic new installation, and then specifying a 2.4 database filename to import. For this reason, the server and network configuration properties must be entered just as you would on a new installation. Make sure you have the configuration information for this server available before you begin. You can use Table 2 on page page 9 in the "Before You Begin" section to record the data.

This method can also be used on an existing Release 2.4 server to migrate the Release 2.4 data and assign a different computer name or IP than the original configuration. In this case, the Release 2.4 database file must be stored on the network before migration begins.

To migrate the 2.4 data onto a new server, perform the following steps:


Step 1 Perform a New Installation by completing the steps in the following sections:

Before You Begin

Starting the Cisco CallManager Release 3.0 Installation Utility

Entering the Server Configuration Data

Completing the Cisco CallManager 3.0 Installation. In Step 5, when the CallManager Database Distribution window opens, select Create a publishing database on this machine and select the I am migrating 2.4 data check box. Enter the path and filename of the 2.4 database file, and then click Next. Enter a username and password when prompted. Continue performing the remaining installation steps in this section.

Logging On to the Server

Step 2 Cisco CallManager services must be stopped and then restarted before Cisco CallManager is operational. For information on stopping and starting services, refer to the "Control Center" chapter in the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.

Step 3 Verify the migrated data.


Important Notes

Cisco Year 2000 product compliance information can be found at:

http://www.cisco.com/warp/public/752/2000/

A local copy of the Help is installed with Cisco CallManager and is available by clicking Help in the Cisco CallManager Administration window. However, current Cisco CallManager documentation can be found on the Web at:

http://www.cisco.com/univercd/cc/td/doc/product/voice/index.htm

You should perform regular backups as described in "Backing Up the Cisco CallManager Data" section.

Obtaining Documentation

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or 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. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.

Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).

Obtaining Technical Assistance

Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.

Cisco Connection Online

Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online 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.

CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, 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 CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.

You can access CCO in the following ways:

WWW: www.cisco.com

Telnet: cco.cisco.com

Modem using standard connection rates and the following terminal settings: VT100 emulation; 8 data bits; no parity; and 1 stop bit.

From North America, call 408 526-8070

From Europe, call 33 1 64 46 40 82

You can e-mail questions about using CCO to cco-team@cisco.com.

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.

To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.

To contact by e-mail, use one of the following:

Language
E-mail Address

English

tac@cisco.com

Hanzi (Chinese)

chinese-tac@cisco.com

Kanji (Japanese)

japan-tac@cisco.com

Hangul (Korean)

korea-tac@cisco.com

Spanish

tac@cisco.com

Thai

thai-tac@cisco.com


In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.

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, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate and value your comments.