Cisco Unified CallManager 4.x Clean Installation Process

A clean installation of Cisco CallManager has always been an extremely simple process. As you perform the Cisco CallManager installation, the automated setup process prompts you for the information that is necessary to build Windows 2000, Microsoft SQL Server 2000, and Cisco CallManager with a base configuration. The entire operating system installation process, excluding preinstallation tasks, takes approximately 25 to 45 minutes per server, depending on your server type. Installing Cisco CallManager, excluding pre- and postinstallation tasks, takes 45 to 90 minutes per server, depending on your server type.

Installation Disks

All Cisco MCSs and customer-provided servers that meet approved Cisco configuration standards ship with a blank hard drive. When you purchase a Cisco IP telephony application, you use the appropriate disks to install or upgrade the operating system and application:

You might also receive a Cisco IP Telephony Server Operating System Upgrade Disk. Use this disk to upgrade the operating system on existing (not new) servers in the cluster. You do not need to use this disk if you are performing a new operating system installation.

Installation Configuration Data

As mentioned previously, the installation process for Cisco CallManager is automated by a step-by-step wizard. You will initially boot off the Hardware Detection CD-ROM, which will walk you through a wizard prompting you for the basic configuration data to get the server running. The process erases all data on the server hard disk. During the installation, you are prompted for the following items:

Sample Configuration Data Worksheet

Table 3-1 shows the configuration information that you need to install the Cisco CallManager software on your server. You should complete all of the fields in the table, unless otherwise noted. You must gather this information for each Cisco CallManager server that you are installing in the cluster. Make copies of this table, and record your entries for each server in a separate table. Table 3-1 summarizes the data you should have available when you begin the installation.

Table 3-1. Configuration Data for Cisco MCS

Configuration

Data

Cisco product key

 

Username

 

Name of your organization

 

Computer name

 

Workgroup

 

Microsoft NT domain (optional)

 

DNS domain suffix

 

Current time zone, date, and time

 

DHCP parameters

It is recommended 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
  • LMHOSTS file (optional)
 

Database server (choose one):

  • Publisher
  • Subscriber

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

  • Publisher username
  • Publisher password
 

Backup (choose one or both):

  • Server
  • Target
 

New Windows 2000 administrator password

 

 

Postinstallation Procedures

After you complete the Cisco CallManager software installation, the installation wizard will prompt you to change all passwords used in the Cisco CallManager cluster. These passwords should be the same on all servers you install into the cluster. In addition, many supporting services are running on your server that you might be able to stop. The fewer services you have running on your server, the more server resources you will have available to support the IP telephony network. In addition, running more services on the Cisco CallManager server introduces more security vulnerabilities for the underlying Windows operating system. You should stop all of the following services on both the Publisher and Subscriber servers in your cluster and set them to manual-start status unless they are otherwise needed on the system:

By default, the installation wizard configures all Subscribers with Internet Information Server (IIS) Services running. This allows you to make changes to the cluster by accessing the web interface on your subscriber servers. Even though you are accessing the web interface on the Subscriber server, the changes are actually being made on the Publisher server (because it has the only writable copy of the database). In addition, allowing the web services to run on all Subscriber servers introduces more security risk as there are now multiple points of access for the Cisco CallManager administration interface. Because of this, it is usually best to save the Subscriber resources by stopping the web services on all servers except the Publisher. You can accomplish this by stopping the following services:

You can stop all of these services through the Windows 2000 Services console. To open this console, click Start > Programs > Administrative Tools > Services. When the console opens, Windows lists all services in alphabetic order. Right-click on the service you want to disable and choose Properties. In the Properties window shown in Figure 3-1, use the drop-down box to select either a Manual startup or to Disable the service. These will take effect the next time you reboot the Cisco CallManager server. You can also choose to stop the service without restarting the server from this page.

Figure 3-1. Windows 2000 Service Properties

Tip

Because Cisco CallManager requires these services to be active when upgrading to new Cisco CallManager versions, setting them to a state of Manual is suggested.

 

Activating Cisco Unified CallManager Services

If you are installing Cisco CallManager for the first time, all services that are required to run Cisco CallManager automatically install on the system; however, none of the services are activated at the completion of the installation (except for the Cisco Database Layer Monitor service). Cisco CallManager Serviceability provides a web-based Service Activation tool that is used to activate or deactivate multiple services and to select default services to activate.

It is recommended that you activate only the required components for each server in the cluster. Each component that you activate adds to the server load.

If you are upgrading Cisco CallManager, the services that you have already started on your system will start after the upgrade.

Each service performs specific functions for the IP telephony network. Some services might need to run on a single Cisco CallManager server in a cluster; other services might need to run on all of the Cisco CallManager servers in the cluster.

Caution

Be sure to activate at least the Cisco CallManager service before you apply any configuration to your Cisco CallManager server. Failure to do so can lead to unpredictable results, potentially leading to a server reinstall.

The following information briefly describes each available Cisco CallManager service:

You must activate the Cisco CallManager services from the Service Activation web interface rather than the Windows 2000 Services control panel. To access this interface, perform the following steps:

Step 1.

Open Internet Explorer, and go to https:///ccmadmin. The is the IP address of the Cisco CallManager server that is running IIS web services. Enter the administrative username and password information.

 

Step 2.

From the Application menu, choose Cisco CallManager Serviceability. The Cisco CallManager Serviceability interface appears.

 

Step 3.

From the Tools menu, choose Service Activation. A window similar to the window shown in Figure 3-2 appears.

 

Figure 3-2. Cisco CallManager Service Activation Interface

 

Step 4.

Click the server that you want to configure from the Servers column. Next click the services that you want to activate, and click the Update button. (You will experience a slight delay.) The Service Activation window will refresh when the process is complete.

 

Tip

The method shown is just one way to access the Cisco CallManager Serviceability pages. If you are working on the Cisco CallManager itself, you can get there quicker by using the Windows 2000 Start menu (Start > Programs > Cisco CallManager > Cisco CallManager Serviceability) or by accessing https:///CCMService.

Caution

Remember to activate the Cisco CallManager services from the Service Activation web interface. Activating the services through the Windows 2000 Services console will produce unpredictable and unstable results.

When you click the Set Default button in the web interface, the Service Activation tool chooses the services required to run Cisco CallManager based on a single-server configuration. This is the bare minimum to have a working Cisco CallManagerbased IP telephony network. Because Cisco highly advises against single-server installations, you will most likely use the Set Default button in a lab environment.

Категории