Table Of Contents
Installing Cisco CallManager Release 3.0(8)
Contents
Introduction
Server Hardware Specifications
Performing a 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
Performing Post-Installation Tasks
Changing Passwords for CCMAdmin and SQLSvc Accounts
Configuring Auto Registration
Configuring DNS
Configuring the Database
Activating Cisco CallManager Services
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
Migrating from Cisco CallManager Release 2.4 to Release 3.0
Full Migration
Migrating the MCS-7830
Migrating the MCS-7820
Database-Only Migration
Upgrading Cisco CallManager Release 3.0 from CD-ROM
Performing Post-Upgrade Tasks
Ongoing Server Management
Compaq Driver Update and Insight Management Agents
Re-creating Subscriber Connections
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Contacting TAC by Using the Cisco TAC Website
Contacting TAC by Telephone
Installing Cisco CallManager Release 3.0(8)
This document describes how to install and configure Cisco CallManager Release 3.0 on the Cisco Media Convergence Server or a customer-provided Compaq DL380 and DL320. Any CD-ROM purchased for installation on a customer-provided Compaq DL380 or DL320 must be installed on a server meeting approved Cisco configuration standards. For specific information on approved Cisco servers, see the "Server Hardware Specifications" section.
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 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
•Upgrading Cisco CallManager Release 3.0 from CD-ROM
•Ongoing Server Management
•Obtaining Documentation
•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 multiservice, open LAN systems.
Use the task roadmaps that follow to determine which sections of this document you need 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 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
•Performing Post-Installation Tasks
–Changing Passwords for CCMAdmin and SQLSvc Accounts
–Configuring Auto Registration
–Configuring DNS
–Configuring the Database
–Activating Cisco CallManager Services
•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
–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
•Performing Backup and Restore Procedures
–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
•Performing Backup and Restore Procedures
–Backing Up the Cisco CallManager Data
Upgrading Cisco CallManager 3.0
If you are upgrading your Cisco CallManager Release 3.0 to the current version, see the following section:
•Upgrading Cisco CallManager Release 3.0 from CD-ROM
Server Hardware Specifications
This section describes the system specifications for Cisco CallManager Release 3.0 and each of the Cisco Media Convergence Servers or third-party servers. Table 1 lists system hardware components included with each MCS product.
Table 1 Media Convergence Server Hardware Specifications
Component
|
|
|
MCS-7830
|
|
MCS-7822
|
MCS-7820
|
Intel Pentium III processor
|
733 MHz
|
1 GHz
|
500 MHz
|
800 MHz
|
550 MHz
|
500 MHz
|
Registered ECC SDRAM
|
1 GB
|
1 GB
|
512 MB 4
|
512MB
|
512 MB
|
512 MB 4
|
10/100BaseTX protocol control information unshielded twisted-pair (PCI UTP) controller
|
X
|
X
|
X
|
X
|
X
|
X
|
Integrated dual-channel wide Ultra SCSI-3 controller
|
X
|
X
|
X
|
|
|
|
Integrated Ultra ATA/100 Controller Module (ATA Models)
|
|
|
|
X
|
|
|
Integrated wide Ultra2 SCSI adapter
|
|
|
|
|
X
|
X
|
Dual 18.2-GB Ultra3 SCSI hot-plug drives
|
|
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
|
Single 20-GB Ultra ATA/100 7,200 rpm non-hot plug "1 drive
|
|
|
|
X
|
|
|
1.44-MB floppy disk
|
X
|
X
|
X
|
X
|
X
|
X
|
Preinstalled high-speed IDE CD-ROM drive
|
X
|
X
|
X
|
|
X
|
X
|
Removable CD-ROM/Diskette drive assembly
|
|
|
|
X
|
|
|
Hot-plug redundant 275 watt power supply
|
X
|
X
|
X
|
|
|
|
180-Watt PFC Power Supply
|
|
|
|
X
|
|
|
200-Watt power factor corrected, CE mark-compliant power supply
|
|
|
|
|
X
|
X
|
Integrated video card
|
X
|
X
|
X
|
X
|
X
|
X
|
RAID controller
|
X
|
X
|
X
|
|
|
|
12/24-GB internal DAT Drive
|
optional
|
optional
|
|
|
|
|
Note You do not receive a monitor with any Cisco Media Convergence Server. The MCS-7820 and MCS-7822 include a keyboard and mouse, but the MCS-7830, MCS-7825, and MCS-7835 do not. During initial startup and configuration of the Cisco Media Convergence Server and Cisco CallManager, you must supply a monitor and, if necessary, a keyboard and mouse.
Performing a 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, be sure to insert the Operating System Installation and Recovery CD-ROM 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.
Caution Cisco does not support third-party software installed on any Cisco Media Convergence Server (MCS).
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 MCS-7825 contains two Network Interface Cards (NIC), but only one is supported by Cisco CallManager. When you connect the server to the network, use the lower NIC connector because the upper connector is disabled during the installation.
Note Cisco CallManager Release 3.0 comes with a special, limited version of Microsoft Windows 2000. This version, intended for use with Cisco CallManager only, 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
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 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, ensure the server you are installing can connect to the publishing database server during the installation. This connection facilitates copying the publisher database from the publisher server to the local drive on the subscriber server. 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 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, ensure the lmhosts file is updated on the existing servers in the cluster before beginning the installation on the new subscriber server; then, the same information must be added to the lmhosts file on the new server during installation, as instructed in the procedure.
Cisco CallManager Release 3.0 is shipped on two CD-ROMs labeled the Operating System Installation and Recovery and the Cisco CallManager 3.0 Installation and Recovery.
To begin the installation process, you insert the Operating System Installation and Recovery CD-ROM into the CD-ROM drive. With this CD-ROM in place, the server automatically begins installing the operating system, Cisco CallManager, and other included software, prompting you to insert the Cisco CallManager 3.0 Installation and Recovery CD-ROM when necessary. 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. The following information applies:
Cisco Product Key
You are supplied with a Cisco Product Key when you purchase a Cisco IP Telephony product. The product key, based on a file encryption system, allows you to install only the components you have purchased, and it prevents other supplied software from being installed for general use. The product key comprises alphabetical letters only. It contains no numbers or special characters. Table 2 on page page 10 shows the product key in the "Before You Begin" section, and it also appears in each step procedure where you are prompted to enter it.
Note The product key provided in this document allows you to install Cisco CallManager Release 3.0 only. To install another Cisco IP Telephony product, you must purchase the product and obtain the appropriate product key.
User and organization name
Registering the software product you are installing requires user and organization name.
Computer name
Assign a unique network name of 15 characters or less for this server. 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, you cannot change the Windows 2000 computer name 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 comprises a collection of computers that have the same workgroup name. Ensure this entry of 15 characters or less follows the same naming conventions as the computer name.
Domain suffix
Always enter the Domain Name System (DNS) domain suffix 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 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, use the server's IP address 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 normally 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 whether 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, ensure the publishing database server is already 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 whether this server will be configured as a backup server or a backup target.
The backup server 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 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
|
|
Name of your organization
|
|
Computer name
|
|
Workgroup
|
|
NT domain (optional)
|
|
DNS Domain suffix
|
|
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
|
|
DNS servers (optional)
•Primary
•Secondary
WINS servers (optional)
•Primary
•Secondary
|
|
Database server (specify one)
•Publisher
•Subscriber
If you are configuring a subscriber server, 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
You do not receive a monitor with any Cisco Media Convergence Server. The MCS-7820 and MCS-7822 include a keyboard and mouse, but the MCS-7830, MCS-7825, 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.
Note The MCS-7825 contains two Network Interface Cards (NIC), but only one is supported by Cisco CallManager. When you connect the server to the network, use the lower NIC connector because the upper connector is disabled during the installation.
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.
To perform an 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.
Step 3 Depending on your server, perform the following procedure:
For an Existing Server
If you are installing a server that has had a previous installation, insert the CD-ROM into the CD-ROM drive and then restart the system immediately. Then go to Step 5.
For a New Server
If you are installing a new server, you will need to insert the CD-ROM into the CD-ROM drive as soon as you are able to do so. This means that you must power up the server and then insert the CD-ROM early in the startup process.
Once you insert the CD-ROM into the CD-ROM drive, complete the following task:
a. For the MCS-7820 or MCS-7822, go to Step 7.
b. For the MCS-7835 or MCS-7830, go to Step 9.
c. For the MCS-7825, go to Step 4.
Note The first time you start up a new server, you will not see any indication that the startup process is operating normally. The startup time on a new server is longer than on preinstalled servers. You may wait as long as 3 minutes before you receive a video connection.
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 If you are installing a new MCS-7825, the ROM Based Setup configuration begins prior to reading the Operating System Installation and Recovery CD-ROM.
Caution Cisco strongly recommends choosing the following selections from the ROM Based Setup Utility screens. Other selections may impact the stability of Cisco CallManager.
a. The first ROM Based Setup Utility screen offers a language selection menu. Press Enter to choose English. Choosing a language other than English does not change the language seen during the installation process. English remains the only supported language at this time.
b. The second ROM Based Setup Utility screen lists several operating system choices. Using the arrow keys, choose Windows 2000 from the operating systems selection menu. Press Enter. Windows 2000 remains the only supported operating system.
c. The third ROM Based Setup Utility screen is pre-set at the factory and cannot be altered. Press ESC to close the menu and continue.
d. On the fourth ROM Based Setup Utility screen, enter the correct date and time and then press Enter.
e. On the final ROM Based Setup Utility screen, a window states that the system configuration is complete. Press F10 to exit the utility and automatically reboot the system.
f. To proceed with the installation, go to Step 6.
Note If you inaccurately choose a selection from one of the ROM Based Setup Utility screens, press F9 during the bootup process to return to the ROM Based Setup Utility and correct the selection.
Step 5 If your server is not new (the hard drive is not blank), The Cisco Media Convergence Server QuickBuilder welcome window opens. Click Next.
Step 6 The Type of Installation window opens. Select New Installation or Server Replacement and then click Next.
On an existing MCS-7825, a second New Installation or Server Replacement window opens. Click Next.
Step 7 The next window displays a warning that your configuration and data will be overwritten. Click Next.
Step 8 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 9 If the New Installation and Replacement window opens, click Next.
Step 10 If the Configuration Process window opens with a message about hardware detection, click Next. The system reboots automatically.
Step 11 If you are installing the MCS-7820, MCS-7822, or MCS-7825, go to Step 13. If you are installing the MCS-7830 or 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 12 When a message prompts you to power off and on the server to complete the installation, turn the server off. Wait 10 seconds and then power up the server.
Step 13 Enter your product key BTOO VQES CCJU IEBI; then, click Next.
Note The Cisco product key comprises alphabetical letters only. It contains no numbers or special characters. Based on a file encryption system that allows you to install only the components you have purchased, it prevents other supplied software from being installed for general use.
Step 14 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 15 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 unchecked and then click Next. If this window does not appear, go to Step 16.
Step 16 Click Next on the Ready to Complete Installation window. This process takes about 5 minutes to complete.
Step 17 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 Ensure the computer name comprises 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, you cannot change the Windows 2000 computer name 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 Ensure the DNS domain suffix is 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 Choose 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 choose 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 the following
Step 9.
Step 8 If you are using DNS or WINS, enter the IP addresses of the primary and secondary DNS servers and primary and secondary WINS servers. Click Next and continue to Step 9.
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:
c. Choose File > Save.
d. Exit Notepad by choosing File > Exit.
e. On the configuration wizard window, click Next to continue.
Note The Windows 2000 SNMP agent provides security through the use of community names and authentication traps. All SNMP implementations universally accept the default name "public." You should change this name to limit access.
Step 10 To ensure security within the Windows 2000 SNMP agent, Cisco recommends that you change the default public community name. Enter a new name and then click Next.
Step 11 The installation process enables Telnet and Terminal services automatically. If you wish, you can disable these services; then, click Next.
Step 12 Click Next to complete the configuration process.
The server begins an installation and reboot process that takes about 6 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 automatically continues loading from the CD-ROM.
Step 2 Click Next at the Welcome to the Cisco CallManager Installation Wizard window.
Step 3 On the CallManager Components window, choose the services you want 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 to online help in the Cisco CallManager application.
Note The Cisco IP Voice Media Streamer contains the Media Termination Point (MTP) and Conference Bridge services.
Note If you are installing TFTP only, the database option is automatically chosen when you choose TFTP. Database installation is required for TFTP support.
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, check the Configure CiscoWorks2000 Syslog Collector check box and enter the domain host name in the form "myserver.mydomain.com." Otherwise, make sure the check box is unchecked. 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, choose I am upgrading/installing the CallManager Publisher.
If a publisher database already exists and you are configuring a subscriber database server, choose I am upgrading/installing the CallManager Subscriber 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. All servers except the publishing database server maintain subscriber databases, which are copies of the publisher database.
Step 6 If you chose I am upgrading/installing the CallManager Publisher in the previous step, go to Step 7. If you chose I am upgrading/installing the CallManager Subscriber, an authentication window opens and prompts you to enter usernames and passwords for a Windows 2000 user with administrative privileges and a SQL Server user with SQL Server administrative privileges on the publishing database server. Enter the account information in the appropriate fields as prompted and then click Next. The system connects to the publishing database server.
Step 7 You have completed the configuration of Cisco CallManager and the database server. The Cisco CallManager and other included software are ready to be installed. Click Next. This part of the installation takes about 30 minutes.
Step 8 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 actually performs the backup operation. It stores the backup data in the directory or tape drive destination that you specify. If a server is configured as a backup server, it automatically will be added to the backup target list.
A backup target is a server that contains data to be backed up. You can choose more than one target, but you can choose only one server.
Choose either Server or Target and then click OK.
Note Cisco strongly recommends that you use the Cisco 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, choose Start > Run, enter services.msc /s, choose the service in the main window, and click Stop Service.
Step 9 If you chose Target in the previous step, a message appears indicating that the setup is complete. You will need to configure this server as a CallManager target on the backup server. Click OK and then go to Step 16.
If you chose Server in the previous step, continue with Step 10.
Step 10 On the Backup Utility Configuration window, add the name of any additional Cisco CallManager 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 11 Click the Destination tab. Choose a destination location where the backup data will be stored. You must choose a destination for backups to be performed. No default destination setting exists.
Note If you choose a network directory as the backup destination, the directory must be shared in Windows 2000. To share a directory, log in on that server, right-click the directory folder icon you want to share, click Sharing..., click Share this folder, and then click OK.
Step 12 Choose Network directory, Local directory, or Tape device to specify where backup files will be backed up. To enter a network or local directory, you can enter the path and directory name or choose it from a browse box by clicking Browse. For network directories, you must supply a username and password with administrator access rights on that server. In the tape device box, only tape drives configured in Windows NT or Windows 2000 appear. To add new devices, click Add device....
Note Only the MCS-7835 has tape drives available.
Note You must choose Network directory or Tape device in order to use the Cisco MCS Restore Utility on your server.
Step 13 Click the Schedule tab.
Step 14 Choose the days and times you want the backup to run. The default is 2:00 am Tuesday through Saturday. You can also choose the length of the system log in days; then, click OK.
Caution Cisco CallManager backups should be timed to occur during off-peak hours because CPU utilization is high during the backup process.
Step 15 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 16 You are prompted to enter a new password for the local Administrator account. Enter the new password in the New Password field and then enter it in the Retype Password field. Click OK.
Caution When entering passwords for the local Administrator and SA (SQL Server system administrator) accounts, do not use the apostrophe (').
Step 17 You are prompted to enter a new password for the SA (SQL Server system administrator) account. Enter a new password of at least 5 characters in the New Password field and then enter it in the Retype Password field. Click OK.
Note Do not lose or forget this password. If you do, you will not be able to reconfigure the server.
Step 18 A message indicates that the password was changed successfully. Click OK.
Step 19 You can choose to remain a workgroup member or to join an NTdomain. If you want to join a domain, enter the NTdomain name and the username and password of a user with administrator privileges on this server; then, click OK.
Step 20 Eject the CD-ROM from the CD-ROM drive and click Yes when prompted if you want to reboot the system now.
Logging On to the Server
After you complete the server installation and Windows 2000 has rebooted, perform the following services to log on to the server:
Step 1 Press Ctrl+Alt+Del to display the logon window.
The logon window should already contain the user name Administrator.
Step 2 Enter the new password for the Administrator account and then click OK.
Performing Post-Installation Tasks
Installing and configuring a Cisco Media Convergence Server automatically installs Cisco CallManager. However, you must set some configuration parameters for Cisco CallManager and perform other post-installation tasks before you can begin using it. Perform these tasks for each server you install and complete them 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
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 receive a default password. To eliminate a security risk, change the passwords after installation.
Caution Make sure you 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. To have access to all servers in the cluster simultaneously, you must ensure the password for CCMAdmin is identical on every server in the cluster.
Perform the following steps to change the CCMAdmin password:
Step 1 Choose Start > Programs > Administrative Tools > Computer Management.
Step 2 Choose the Users folder located in the following path: System Tools/Local Users & Groups. The users display in the main window.
Step 3 Right-click on CCMAdmin and choose Set Password.
Step 4 Enter the new password in the New Password and Confirm Password fields and click OK.
SQLSvc
Only the Microsoft SQL Server service can use the SQLSvc account. The server uses it as the core account for server-to-server interaction by the CallManager system. For the service to function properly, ensure the password for the SQLSvc account is 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 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 Choose Start > Programs > Administrative Tools > Computer Management.
Step 2 Choose the Users folder located in the following path: System Tools/Local Users & Groups. The users display in the main window.
Step 3 Right-click SQLSvc and choose 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 was changed. Click OK.
Step 6 Click on the Services icon located in Services and Applications. The services display in the main window.
Step 7 Right-click MSSQLServer and choose Properties.
Step 8 Click 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 choose Properties.
Step 11 Click 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 Choose Start > Programs > Administrative Tools > Component Services.
Step 15 Choose the COM+Applications folder located in the following path: Component Services/Computers/My Computer. The applications display in the main window.
Step 16 Right-click DBL and choose Properties.
Step 17 Click 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 choose Shut Down.
Step 20 Right-click DBL and choose 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 number assignment occurs 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 about the reliability and availability of your DNS server and network structure.
If a DNS server is used, your call processing system depends 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 action is necessary 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 Choose Start > Settings > Network and Dial-up Connections.
Step 2 Right-click Local Area Connection and choose Properties.
Step 3 Choose Internet Protocol (TCP/IP).
Step 4 Click Properties.
Step 5 Click Advanced.
Step 6 Click the DNS tab.
Step 7 Remove any entries in the DNS server addresses list by choosing the entry and clicking Remove.
Step 8 Uncheck 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 Choose Start > Programs > Cisco CallManager 3.0 > CallManager Administration and log in with administrator privileges.
Step 2 From the CallManager Administration window, choose System > Server.
Step 3 From the list of Cisco CallManagers on the left, choose 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 chose 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 on page 47 for more information.
To activate additional Cisco CallManager services, or to deactivate existing services, perform the following steps:
Step 1 Choose Start > Programs > Cisco CallManager > Cisco Service Configuration.
Step 2 Choose the check box for each Cisco CallManager service you want to activate. If a service is currently activated and you uncheck 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, you must start it. For information on starting services, refer to the Cisco CallManager Administration Guide or online help in the Cisco CallManager application.
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.
Note If you want to recover your Cisco CallManager Release 3.0 data to a server configured with a later release of Cisco CallManager, you must first perform a normal recovery on the server, restoring it to its original version, and then perform an upgrade to the current release.
This section describes procedures for backing up the Cisco CallManager data and recovering from hardware and software failures. This section discusses the following topics:
•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
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 automatically backs 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 choose 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, not a local directory. If you choose a network directory as the backup destination, the directory must be shared in Windows 2000. To share a directory, log in on that server, right-click the directory folder icon you want to share, click Sharing..., click Share this folder, and then click OK.
Your Cisco CallManager cluster has only one publisher database, and no necessity exists 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, one file called MCS.tar stores all data backed up from the target servers in the target list. When you restore, you choose and restore data from one server at a time.
Note Each time a backup is performed, the new backup file overwrites the existing MCS.tar 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. If you rename the MCS.tar file, do not use any spaces in the new filename. If you move the MCS.tar file to another location, make sure you store it in a folder path that does not contain spaces.
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 the MCS Backup Utility icon in the Windows 2000 system tray and choose View status. If the MCS Backup Utility icon is not in the Windows 2000 system tray, choose Start > Programs > Cisco MCS Backup > Cisco MCS Viewer; then, click the MCS Backup Utility icon in the Windows 2000 system tray and choose 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 the MCS Backup Utility icon in the Windows 2000 system tray and choose 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 Only the MCS-7835 has tape drives available.
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 Schedule Cisco CallManager backups 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 the MCS Backup Utility icon in the Windows 2000 system tray and choose Start backup now.
Step 7 The Backup Utility Viewer displays the status of the backup operation by highlighting each task as it occurs. Use the information generated in the log window 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.
Note For information on preserving the server hard drive after a backup, see the "Before You Begin" section in Upgrading Cisco CallManager Release 3.0(8) from the Web.
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.
Performing a recovery on a server that contains a subscriber database is not necessary because that database is only a backup copy of the publisher database. For subscriber servers, performing a new installation is best. See the "Performing a 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.
During the recovery process, the system recovers IP information, computer name, and other configuration data from backup and populates the data entry fields. 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 10 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, choose 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 Choose 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 5 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 choose the same option that you chose in the original configuration. Click Next. If you chose Enter static IP information, the IP information for the server displays 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:
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 6 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, choose the services you want 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 If you are installing TFTP only, the database option is automatically chosen when you choose TFTP. Database installation is required for TFTP support.
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, choose the Configure CiscoWorks2000 Syslog Collector check box and enter the domain host name in the form "myserver.mydomain.com." Otherwise, make sure it is unchecked. Click Next.
Step 22 Choose I am upgrading/installing the CallManager Publisher 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 are 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.
Choose 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, choose Start > Run, enter services.msc /s, choose 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 chose Target in the previous window, go to Step 30. If you chose 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 Click the Destination tab.
Note If you choose a network directory as the backup destination, the directory must be shared in Windows 2000. To share a directory, log in on that server, right-click the directory folder icon you want to share, click Sharing..., click Share this folder, and then click OK
Step 28 Choose Network directory, Local directory, or Tape device to specify where backup files will be backed up. To enter a network directory, you can enter the path and directory name or choose it from a browse box by clicking Browse. For network directories, you must supply a username and password with administrator access rights on that server and then click Verify. In the tape device box, only tape drives configured in Windows NT or Windows 2000 display. 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.
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 30 You are prompted to enter a new password for the local Administrator account. Enter a new password in the New Password field and then enter 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. Enter a new password of at least 5 characters in the New Password field and then enter it in the Retype Password field. Click OK.
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 Enter the new password for the Administrator account and then click OK.
Step 36 When the Cisco MCS Restore Utility window opens, choose the location of the backup file that you want to restore by clicking Browse, choosing 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. Choose 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, one file called MCS.tar stores all data backed up from the target servers in the target list. When you restore, you choose 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 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 new server uses the IP information and computer name of the original machine. The operating system, Cisco CallManager, and other included software are 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, always enter the IP information, computer name, and other configuration data 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 10 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 7. Otherwise, choose 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 comprises alphabetical letters only. It contains no numbers or special characters. Based on a file encryption system that allows you to install only the components you have purchased, 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, choose 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 5 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, ensure the data entry fields are 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 Ensure the DNS domain suffix is 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 Choose 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 choose the same option that you chose in the original configuration. Click Next. If you chose 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:
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 6 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, choose the services you wish to activate in this initial installation and 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 If you are installing TFTP only, the database option is automatically chosen when you choose TFTP. Database installation is required for TFTP support.
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, check the Configure CiscoWorks2000 Syslog Collector check box and enter the domain host name in the form "myserver.mydomain.com." Otherwise, make sure it is unchecked. Click Next.
Step 28 Choose I am upgrading/installing the CallManager Publisher 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 are 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.
Choose 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, choose Start > Run, enter services.msc /s, choose 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 Click the Destination tab.
Note If you choose a network directory as the backup destination, the directory must be shared in Windows 2000. To share a directory, log in on that server, right-click the directory folder icon you want to share, click Sharing..., click Share this folder, and then click OK.
Step 33 Choose Network directory, Local directory, or Tape device to specify where backup files will be backed up. To enter a network directory, you can enter the path and directory name or choose it from a browse box by clicking Browse. For network directories, you must supply a username and password with administrator access rights on that server 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.
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 35 The Cisco Product Activation window opens and prompts you to enter a new password for the local administrator account. Enter the new password in the New Password field and then enter it in the Retype Password field. Click OK.
Step 36 A second window opens and prompts you to enter a new password for the SA (SQL Server system administrator) account. Enter a new password of at least 5 characters in the New Password field and then enter it in the Retype Password field. Click OK.
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 username Administrator.
Step 40 Enter 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. Choose 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. Choose the CallManager target that you want to restore and then click Next.
Note By default, one file called MCS.tar stores all data backed up from the target servers in the target list. When you restore, you choose 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 Verify the restored data.
Restoring the Cisco CallManager Data Only
This section describes the process of restoring the Cisco CallManager data only. This process does not restore the operating system, Cisco CallManager, and other included software. 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 Choose Start > Programs > CallManager MCS Backup > Cisco MCS Restore.
Step 2 Choose 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 choose and restore data from one server at a time.
Step 3 Choose 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.
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 that is generated 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 root directory of the local hard drive (c:\) contains the log file that 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 This process does not retain uOne data that is stored on the same server. 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:
•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.
•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 process copies and imports the Release 2.4 information 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; then, the Cisco CallManager Release 2.4 database is imported into SQL Server 7.
In a full migration, the process recovers the IP information, computer name, and other configuration data from the 2.4 system and populates them 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 10 in the "Before You Begin" section to record the data.
Caution During the migration process, call processing service stops. You should notify your users that telephone service will be interrupted during this time.
The following two procedures 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 comprises alphabetical letters only. It contains no numbers or special characters. Based on a file encryption system that allows you to install only the components you have purchased, 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 5 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, configuration parameters that were retained from the Cisco CallManager Release 2.4 system automatically populate the fields. These entries can be accepted as they are or changed.
Step 16 The username 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 you must enter the DNS domain name that was not migrated here. Click Next.
Note Enter the DNS domain suffix 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, you cannot change the Windows 2000 computer name 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 Choose 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 choose 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 that follows.
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:
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 6 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, choose 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, check the Configure CiscoWorks2000 Syslog Collector check box and enter the domain host name in the form "myserver.mydomain.com." Otherwise, make sure it is unchecked. 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, choose I am upgrading/installing the CallManager Publisher.
If your server is the MCS-7830, do not check the I am migrating 2.4 data check box because you are already using the full migration utility.
If your server is the MCS-7820, the software checks the I am migrating 2.4 data check box automatically and automatically populates the database path and filename field 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 are 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 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 contains data to back up. You can choose more than one target, but you can choose only one server.
Choose either Server or Target and then click OK.
Note Cisco strongly recommends that you use the Cisco 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, choose Start > Run, enter services.msc /s, choose 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 Click the Destination tab.
Note If you choose a network directory as the backup destination, the directory must be shared in Windows 2000. To share a directory, log in on that server, right-click the directory folder icon you want to share, click Sharing..., click Share this folder, and then click OK
Step 34 Choose Network directory, Local directory, or Tape device to specify where backup files will be backed up. To enter a network directory, you can enter the path and directory name or choose it from a browse box by clicking Browse. For network directories, you must supply a username and password with administrator access rights on that server 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.
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 36 You are prompted to enter a new password for the local Administrator account. Enter the new password in the New Password field and then enter it in the Retype Password field. Click OK.
Step 37 You are prompted to enter a new password for the SA (SQL Server system administrator) account. Enter a new password of at least 5 characters in the New Password field and then enter it in the Retype Password field. Click OK.
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 username Administrator.
Step 41 Enter 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 inserting a floppy diskette at the beginning of the migration process. The diskette stores 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
To achieve database-only migration, perform a basic new installation and then specify a 2.4 database filename to import. For this reason, ensure the server and network configuration properties are 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 10 in the "Before You Begin" section to record the data.
You can also use this method on an existing Release 2.4 server to migrate the Release 2.4 data and to assign a different computer name or IP than the original configuration. In this case, you must store the Release 2.4 database file 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, choose I am upgrading/installing the CallManager Publisher and choose 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.
Upgrading Cisco CallManager Release 3.0 from CD-ROM
Before you begin, make sure you have a good backup of the Cisco CallManager 3.0 data stored on tape or on a network directory. For instructions on backing up Cisco CallManager data, see the "Backing Up the Cisco CallManager Data" section.
Note If you are running a Cisco CallManager cluster, you must upgrade all the servers in the cluster. You must perform the upgrade on the publisher server first and then on each subscriber server.
Note Before the upgrade, remove any unused call detail records (CDRs) to prevent timeout of the upgrade and reduce upgrade time. Cisco recommends storing no more than 2.5 million CDRs in the database. For information on removing CDRs, see the Administrative Reporting Tool Guide for Cisco CallManager.
Note During the upgrade process, call processing service temporarily stops. You should notify your users that telephone service will be interrupted during this time.
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 If you are upgrading from Cisco CallManager 3.0(5a) to a later version of Cisco CallManager, skip to Step 16.
Note The following standard installation for Service Pack 1 contains general enhancements and performance improvements for Windows 2000 Server. Apply Service Pack 1 to all Cisco MCS and customer-provided Compaq DL380 servers running Cisco CallManager 3.0(5a) or later.
Step 4 Download the file win-servicpack1.exe from http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr. Make note of the location where you save the file.
Step 5 Double-click the downloaded file.
Step 6 Wait while the files load to your server.
Step 7 Read and accept the license agreement.
Step 8 Choose Install.
Step 9 After the installation completes, restart your computer for the update to take effect.
Note The following installation for the Windows 2000 Virtual Memory fix enhances the way virtual memory is allocated and deallocated. The result is a lower baseline of `used' virtual memory. Apply the Windows 2000 Virtual Memory fix to all Cisco MCS and customer-provided Compaq DL380 servers running Cisco CallManager 3.0(5a) or later.
Step 10 Install the Windows Virtual Memory fix after installing Service Pack 1.
Step 11 Download the file win-virtual-memory-fix.exe from http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr. Make note of the location where you save the file.
Step 12 Double-click the downloaded file.
Step 13 Wait while the files load to your server.
Step 14 After the installation completes, restart the server for the update to take effect.
Note After you have performed the upgrade 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.
Step 15 The Cisco Media Convergence Server QuickBuilder welcome window opens. Click Next.
Step 16 Choose the option to Upgrade your current CallManager release 3.0 with the latest 3.0 release and then click Next.
Step 17 On the Ready to Complete Upgrade on BIOS/Firmware window, click Next.
Step 18 When a message prompts you to power off and on the server to complete the installation, turn the server off. Wait 10 seconds and then power up the server.
Step 19 On the Ready to Complete Upgrade window, click Next.
Step 20 Follow the online instructions to eject the CD, restart Windows, login, and insert the CallManager CD-ROM.
Step 21 On the Cisco Product Activation popup window, click Yes.
Step 22 Go to Step 2 on page page 15 in the "Completing the Cisco CallManager 3.0 Installation" section and perform the remaining steps for a new Cisco CallManager installation.
Note For information on reverting to the previous configuration after an upgrade attempt, see Upgrading Cisco CallManager Release 3.0(8) from the Web.
Performing Post-Upgrade Tasks
To verify that the upgrade completed successfully, perform the following steps:
Step 1 Choose Start > Programs > Administrative Tools > Services.
Verify that all the services listed in your Services screen are running:
•Cisco CallManager
•Cisco Database Layer Monitor
•Cisco IP Voice Media Streaming App
•Cisco Messaging Interface
•Cisco SNMP Data Collector
•Cisco TFTP
•DC Directory Server
Step 2 Click the Close button in the upper right corner of the window.
Note Depending on which services you have installed on your system, some services shown in the preceding list may not appear in your Services window.
Ongoing Server Management
Compaq Driver Update and Insight Management Agents
The Compaq Driver Update utility that is installed automatically during the Cisco CallManager installation significantly improves the performance of your server.
The Compaq Insight Management Agent, a SNMP agent extension, 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 is installed automatically if your system uses CiscoWorks2000.
If you should need to reinstall the Compaq Driver Update or Compaq Insight Management Agents, the following location stores the install utility: C:\Cpqutil\Cpqdrv\Bp000005.cmd
Re-creating Subscriber Connections
If the connections between the publishing Cisco CallManager database and the subscribers within a cluster are broken for any reason, the database cannot be replicated to the subscribers. If you suspect a problem with subscriber connections, you should verify the status of the subscriptions or the jobs. On the publisher server, perform the following steps to verify the status of the subscribers and jobs:
Step 1 Open SQL Server Enterprise Manager by choosing Start > Programs > Microsoft SQL Server 7.0 > Enterprise Manager.
Step 2 To see the status of subscriptions, choose the Pull Subscriptions folder located in the following path: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Databases/<publication name>.
To see the status of jobs, choose the Jobs folder located in the following path: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Management/SQL Server Agent.
The Expired Subscription Cleanup service could display a red `x' under normal operation. However, if a red `x' appears next to a subscriber name or a job name other than Expired Subscription Cleanup, the subscriber connection has broken, and you must reinitialize it.
Note The event log on the subscriber server lists SQL Server Agent errors. To view the event log, choose Start > Programs > Administration tools > Event Viewer on the subscriber server.
If you determine that one or more subscription connections are broken, you must perform the following actions:
•On each subscriber server, delete and then re-create the subscriptions.
•On the publisher server, reinitialize the subscriptions and start the replication snapshot agent.
On each subscriber server, perform the following steps to delete and re-create the subscriptions:
Step 1 Open SQL Server Enterprise Manager by choosing Start > Programs > Microsoft SQL Server 7.0 > Enterprise Manager.
Step 2 In the following path, choose the Pull Subscriptions folder: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Databases/<the publisher database name>.
Step 3 In the main window, right-click the subscription name and choose Delete. Click Yes to confirm.
Step 4 Right-click the Pull Subscription folder and choose New Pull Subscription....
Step 5 The Welcome to the Pull Subscription Wizard window opens. Click Next.
Step 6 If your publisher server does not appear in the publication list, click Register Server. Enter the name of the publisher server in the Server field and choose 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 choose the publication name that matches the database you are configuring. Click Next.
Step 8 In the Specify Sychronization Agent Login window, choose By impersonating the SQL Server Agent account and then click Next.
Step 9 In the Specify Immediate-Updating Subscriptions window, choose 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, choose Yes, Initialize the schema at the Subscriber and click Next.
Step 12 In the Set Distribution Agent Schedule window, choose 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 choosing Start > Programs > Microsoft SQL Server 7.0 > Enterprise Manager.
Step 2 In the following path, choose the name of the publisher database that you are configuring: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Databases/<the publisher database name>Publications.
Step 3 In the main window, right-click the subscription name and choose Reinitialize all Subscriptions. Click Yes to confirm.
Step 4 In the following path, choose the Snapshot Agents folder: Microsoft SQL Servers/SQL Server Group/<this server's hostname>/Replication Monitor/Agents.
Step 5 Right-click the publication name that matches the database name you are configuring; then, click Start.
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following sites:
•http://www.cisco.com
•http://www-china.cisco.com
•http://www-europe.cisco.com
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
http://www.cisco.com/go/subscription
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
http://www.cisco.com
Technical Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
http://www.cisco.com/tac
P3 and P4 level problems are defined as follows:
•P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
Contacting TAC by Telephone
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
•P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
•P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.
AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, PIX, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0102R)
)Copyright ©2000, 2001. Cisco Systems, Inc.
All rights reserved.
Feedback
