- Article History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
- Cisco Community
- :
- Technology and Support
- :
- Collaboration, Voice and Video
- :
- Collaboration, Voice and Video Documents
- :
- Installing Cisco Unified CallManager Release 5.1
Installing Cisco Unified CallManager Release 5.1
Installing Cisco Unified CallManager Release 5.1(1)
Because the 5.0(x) release of Cisco Unified CallManager has a different installation framework than previous releases of Cisco Unified CallManager, review all installation instructions carefully before you install Cisco Unified CallManager 5.1(1).
This document includes information about installing Cisco Unified CallManager Release 5.1(1) on one server or many servers in a cluster environment.
Contents
- This document contains the following topics:
- • Installation Overview
- • Important Considerations
- • Frequently Asked Questions About the Cisco Unified CallManager Installation
- • Browser Requirements
- • Configuring the Hardware
- • Installing Cisco Unified CallManager
- • Gathering Information for an Installation
- • Installing the New Operating System and Application
- • Post-Installation Tasks
- • Examining Log Files
- • Obtaining Documentation
- • Documentation Feedback
- • Obtaining Technical Assistance
- • Obtaining Additional Publications and Information
Installation Overview
- Cisco Unified CallManager 5.0(x) uses a different installation framework than previous releases. The installation process allows you to perform a basic installation, upgrade from Cisco Unified CallManager 4.x to Cisco Unified CallManager 5.1(1), and upgrade to a newer service release during the installation.
- For a more detailed description of the different installation types, see Table 1.
- Table 1 Installation Options
- INSERT TABLE HERE
Note: This document describes only the first two installation types: Basic Install and Upgrade During Install. For information on performing a Windows Upgrade, refer to Upgrading Cisco Unified CallManager.
Important Considerations
- Before you proceed with the Cisco Unified CallManager installation, consider the following requirements and recommendations:
- • Be aware that when you install Cisco Unified CallManager 5.1(1) on an existing server, the hard drive gets formatted, and all existing data on the drive gets overwritten.
- • Install the Cisco Unified CallManager software on the first node or publisher server first and then on the subsequent nodes.
- • Make sure that the subsequent node servers that you are installing can connect to the first node server during the installation.
- • Enter the same security password on all servers in the cluster.
- • Install the Cisco Unified CallManager software during off-peak hours or a maintenance window to avoid impact from call-processing interruptions.
- • Configure the server by using static IP addressing to ensure that the server obtains a fixed IP address and that the Cisco Unified IP Phones can register with the application when you plug the phones into the network.
- • Do not attempt to perform any configuration tasks during the installation.
- • Do not install any Cisco-verified applications until you complete installing Cisco Unified CallManager on every server in the cluster.
- • Carefully read the instructions that follow before you proceed with the installation
Frequently Asked Questions About the Cisco Unified CallManager Installation
- The following section contains information about commonly asked questions and responses. Review this section carefully before you complete the Cisco Unified CallManager installation.
- How long does it take to perform the Cisco Unified CallManager installation?
- The entire installation process, excluding pre- and post-installation tasks, takes 45 to 90 minutes per server, depending on your server type. Before you install Cisco Unified CallManager, consider the size of your cluster.
- What Passwords do I Need to Specify?
- During the Cisco Unified CallManager installation, you must specify the following user names and passowords:
- • Administrator account
- You use the Administrator username and password to log in to the following areas:
- – Cisco Unified Communications Operating System Administration
- – Disaster Recovery System
- – Command Line Interface
- The Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. You can change the Administrator password or add a new Administrator account by using the command line interface. See the Cisco Unified Communications Operating System Administration Guide for more information.
- • Application User password
- You use the Application User password for the following default application user names:
- – CCMAdministrator
- – CCMSysUser
- – WDSysUser
- – CCMQRTSysUser
- – IPMASysUser
- – WDSecureSysUser
- – CCMQRTSecureSysUser
- – IPMASecureSysUser
- You can change the application user password for each application through Cisco Unified CallManager Administration. See the Cisco Unified CallManager Administration Guide for more information.
- • Database Access Security Password
- The system uses this password to authorize communications between nodes, and you must ensure that this password is identical on all nodes in the cluster.
- The Database Access Security password must start with an alphanumeric character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores.
- Which servers does Cisco support for this installation?
- For information about the supported servers, refer to the release notes for your version of Cisco Unified CallManager. Click here for Cisco Product Release Notes
- May I install other software besides Cisco Unified CallManager on the server?
- For Cisco Unified CallManager 5.1(1), you must do all software installations and upgrades by using the Software Upgrades menu options in Cisco Unified Communications Operating System Administration. The system can upload and process only software that Cisco Systems approved. You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco Unified CallManager with Cisco Unified CallManager 5.1(1).
- What are the Installation Options?
- • Basic Install
- This option represents the basic installation and does not use any imported data.
- • Upgrade During Install
- This option allows you to upgrade the preinstall software with the latest service release prior to configuring your system. You can also choose Upgrade During Install followed by a Windows Upgrade and perform both during the installation process.
- • Upgrade During Install
- Note: Ensure that you have the software image available on DVD or on a remote server prior to choosing this option.
- • Windows Upgrade
- This option allows you to import the TAR file that the DMA tool produced while upgrading an existing Cisco Unified CallManager server.
- • Windows Upgrade
- Note: 'For more information on performing a Windows Upgrade, see' Upgrading Cisco Unified CallManager.
Browser Requirements
- You can access Cisco Unified CallManager Administration, Cisco Unified CallManager Serviceability, and Cisco Unified Communications Administration by using the following browsers:
- • Microsoft Internet Explorer version 6.0 or later
- • Netscape Navigator version 7.1 or later
Note: Cisco does not support or test other browsers, such as Mozilla Firefox.
Configuring the Hardware
- As a part of software installation, the system installer configures the system BIOS and RAID settings for the new operating system and Cisco Unified CallManager application. See Table 2 for the BIOS settings and Table 3 for the RAID settings that are set up during installation.
Note: If the hardware configuration process fails during installation, you can use boot-time utilities that are found on both the IBM and HP servers to manually configure the RAID and BIOS settings, as shown in Table 2 and Table 3.
Table 2 BIOS Configuration Settings for HP and IBM Servers
| HP Servers | IBM Servers |
| OS Selection: Linux (not applicable on newer models) | OS Selection: Not Applicable |
| Boot Order: CD, C:, Floppy | Boot Order: CD, C:, Floppy |
| Post F1 prompt: Delayed | Post F1 prompt: Delayed |
| Hyperthreading: Enabled | Hyperthreading: Enabled |
Table 3 RAID Settings
| MCS 7825 Servers (HP and IBM) | MCS 7835 Servers (HP and IBM) | MCS 7845 Servers (HP and IBM) |
| Software Raid | Logical Drives: 1 | Logical Drives: 2 |
| Software Raid Note For the HP 7825H1 and the IBM 7825I1, SATA RAID is enabled, and the RAID type specifies 1(1+0), with one logical drive | RAID type: 1(1+0) | RAID type: 1(1+0) |
Installing Cisco Unified CallManager
- The next sections contain the procedures for installing the first and subsequent nodes. Review the following sections carefully before you perform the installation:
- • Gathering Information for an Installation
- • Handling Network Errors During Installation
- • Installing the New Operating System and Application
Gathering Information for an Installation
- Use Table 4 to record the information about your Cisco Unified CallManager server. Gather this information for each Cisco Unified CallManager server that you are installing in the cluster. You may not need to obtain all the information; gather only the information that is pertinent to your system and network configuration. You should make copies of this table and record your entries for each server in a separate table, even if you are planning to use the DMABackupInfo.inf file to configure your system.
- Note: Because some of the fields are optional, they may not apply to your configuration. For example, you choose not to set up an SMTP host.
- Caution: You cannot change some of the fields after installation without reinstalling the software, so be sure to enter the values that you want.
- The last column in the table shows whether a field can be changed after installation, and if so, whether you can change it through Cisco Unified Communications Operating System Administration or through the Command Line Interface (CLI).
Table 4 Configuration Data
| Configuration Data | Your Entry | Can Entry Be Changed After Installation |
| Administrator Password | Yes. CLI> set password admin | |
| Application User Password | Yes. CLI> set password | |
| Country | Yes. CLI> set web-security | |
| DHCP | Yes. CLI> set network dhcp | |
| DNS Primary | Yes. CLI> set network dns | |
| DNS Secondary | Yes. CLI> set network dns | |
| Domain | Yes. CLI> set network domain | |
| Domain Name Service DNS Enable | NO. | |
| Gateway Address | Yes Use OS Adminstration > Settings>IP set network gateway | |
| Host Name | NO. | |
| IP Address | Yes Use OS Adminstration > Settings>IP | |
| IP Mask | Yes Use OS Adminstration > Settings>IP | |
| Location | Yes. CLI> set web-security | |
| Master Administrator ID | NO. | |
| NTP Server IP Address Note You can enter up to five NTP servers. | Yes Use OS Administration > Settings>NTP Servers | |
| Organization | Yes CLI> set web-security | |
| Security Password | Yes CLI> set password security | |
| SMTP Location | Yes CLI> set smtp | |
| State | Yes CLI> set web-security | |
| Time Zone | Yes CLI> set timezone | |
| Unit | Yes CLI> set web-security |
For more detailed descriptions of each installation field, see Table 5.
Table 5 Installation Field Definitions
| Field | Description | Usage |
| Administrator ID | This field specifies the name that you want to assign to this account. | Ensure the name is unique; it can contain lowercase, alphanumeric characters, hyphens, and underscores. It must start with a lowercase alphanumeric character. |
| Administrator Password | This field specifies the password that you use for logging into the the CLI on the platform and for logging into Cisco Unified Communications Operating System Administration. | Ensure the password is at least six characters long; it can contain alphanumeric characters, hyphens, and underscore. |
| DHCP | Dynamic Host Configuration Protocol | Choose Yes if you want to use DHCP to automatically configure the network settings on your server. |
| DNS Enabled | A DNS server represents a device that resolves a hostname into an IP address or an IP address into a hostname. | If you do not have a DNS server, enter No. When DNS is not enabled, you should only enter IP addresses (not hostnames) for all network devices in your Cisco Unified Communications network. |
| DNS Primary | The server contacts this DNS server first when it attempts to resolve host names. | Enter the IP address of the DNS server that you want to specify as the primary DNS server. Enter the IP address in dotted decimal format as ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0). |
| DNS Secondary | When a primary DNS server fails, the server will attempt to connect to the secondary DNS server. | In this optional field, enter the IP address of the secondary DNS. Enter the IP address in dotted decimal format as ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0). |
| Domain | This field represents the name of the domain in which this machine is located. | Consider this field mandatory if DNS is set to yes. |
| First Cisco Unified Communications Manager Node | This field specifies the first Cisco Unified Communications Manager node that contains the database. | Choose Yes if you are configuring the first Cisco Unified Communications Manager node in the cluster. |
| Gateway Address | A gateway represents a network point that acts as an entrance to another network. Outbound packets get sent to the gateway that will forward them to their final destination. | Enter the IP address of the gateway in the format ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0) |
| Host Name | A host name represents an alias that is assigned to an IP address to identify it. | Enter a host name that is unique to your network. |
| IP Address | This field specifies the IP address of this machine. It will uniquely identify the server on this network. Ensure another machine in this network does not use this IP address. | Enter the IP address in the form ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0). |
| IP Mask | This field specifies the IP subnet mask of this machine. The subnet mask together with the IP address define the network address and the host address. | Enter the IP mask in the form ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0). |
| NIC Speed | This field specifies the speed of the server network interface card (NIC) in megabits per second. | The possible speeds include 10 or 100. |
| NIC Duplex | This field specifies the duplex setting of the server NIC. | The possible settings include half and full. |
| NTP Server | This field identifies the NTP servers with which you want to synchronize. | Enter the hostname or IP address of one or more NTP server(s). |
| NTP Server Enable | When enabled, this server will act as a NTP server and provide time updates to the subsequent nodes in the cluster. | Choose Yes if you want to enable this machine to be an NTP server. |
| Security Password | Servers in the cluster use the security password to communicate with one another. | Enter the security password. Enter the same password in the confirm password field. Caution You must enter the same password for all nodes in the cluster. |
| Set Hardware Clock | This field specifies the date and local time for the machine. Note If you set the hardware clock manually, the node does not use an external NTP server for time synchronization. | Choose Yes if you want to set the date and local time for the time zone that you chose. |
| SMTP | This field specifies the name of the SMTP host that is used for outbound e-mail. | Enter the hostname or dotted IP address for the SMTP server. For a host, it can contain alphanumeric characters, hyphens, or periods. For a host name, it must start with an alphanumeric character. You must fill in this field if you plan to use electronic notification. If not, you can leave it blank. |
| Subnet IP Address | By entering a subnet address, you can specify a range of IP Addresses that will be granted access to query this NTP server. | Enter an IP subnet that will be granted access to the NTP server |
| Subnet Mask | This field specifies the subnet mask for the subnet address. | Enter the subnet mask for the IP subnet. |
| Time zone | This field specifies the local time zone and offset from Greenwich Mean Time (GMT). | Choose Yes if you want to change the time zone. |
Handling Network Errors During Installation
- During the installation process, the installation program verifies that the server can successfully connect to the network by using the network configuration you enter. If it cannot, a message displays, and you get prompted to select one of the following options:
- • RETRY — The installation program tries to validate networking again. If validation fails again, the error dialog box displays again.
- • REVIEW (Check Install)— Allows you to review and modify the networking configuration. The installation program returns to the network configuration windows.
- • HALT — The installation halts. You can copy the installation log files to a USB disk to aid troubleshooting of your network configuration.
- • IGNORE — The installation continues. The networking error gets logged. In some cases, the installation program validates networking multiple times, so this error dialog box might display multiple times.
- Note: Networking is validated after you complete each networking window, so the message might display multiple times. If the message displays while you are reviewing the
network configuration windows, choose IGNORE to move to the next window. If you choose REVIEW, the first network configuration window appears again.
- Note: Networking is validated after you complete each networking window, so the message might display multiple times. If the message displays while you are reviewing the
- • IGNORE — The installation continues. The networking error gets logged. In some cases, the installation program validates networking multiple times, so this error dialog box might display multiple times.
Installing the New Operating System and Application
Use this procedure to begin installing the operating system and Cisco Unified CallManager application:
Procedure
- Step 1 Insert the installation DVD into the tray and restart the server, so it boots from the DVD. After the server completes the boot sequence, the Media Check window displays.
- Note: If you have a new server with Cisco Unified CallManager preinstalled, you do not need to install from a DVD. Go directly to the "If You Choose Skip" procedure.
- Step 2 Verify that the checksum that displays on the Media Check matches the checksum for the release on Cisco.com.
- When the media check completes, the Media Check Result window displays.
- Step 3 If the Media Check Result displays Pass, choose OK to continue the installation.
- If the media fails the Media Check, either download another copy from Cisco.com or obtain another disc directly from Cisco Systems.
- After you choose OK, the system installer performs various hardware checks to ensure you system is correctly configured for Cisco Unified CallManager 5.1(1), including the following checks:
- – First, the installation process checks for the correct drivers, and you may see the following warning:
-
Drivers not found, do you want to install manually? - To continue the installation, choose Yes.
-
- – The installation next checks to see whether you have a supported hardware platform. If your server does not meet the exact hardware requirements, the installation process fails with a critical error. If you think this is not correct, capture the error and report it Cisco support.
- – The installation process next verifies RAID configuration and BIOS settings. If the installation process makes any changes to your hardware configuration settings, you will get prompted to restart your system.
- After the hardware checks complete, the Overwrite Hard Drive window displays.
- Step 4 The Overwrite Hard Drive window indicates the current software version on your hard drive, if any, and the version on the DVD. Choose Yes to continue with the installation or No to cancel.
- Caution If you choose Yes on the Overwrite Hard Drive window, all existing data on your hard drive gets overwritten and destroyed.
- The Platform Installation Wizard window displays.
- Step 5 To configure the platform now, choose Proceed. If you want to configure the platform later, choose Skip.
- – If you want to install and configure the software at this time, choose Proceed and skip to the "If You Choose Proceed" section.
- – If you want to install the software now and configure it later, choose Skip and continue with the "If You Choose Skip" section.
- If You Choose Skip
- Start here if you have a server that has Cisco Unified CallManager preinstalled or if you chose Skip on Platform Installation Wizard window.
- Step 6 After the system restarts, the Preexisting Installation Configuration window displays. If you have configuration information on a USB drive or on a diskette, insert it now.
Note If a popup window states that the system detected new hardware, press any key and then choose Install from the next window. Note If you have a file that the Data Migration Assistant created, see the Data Migration Assistant User Guide for more information.
- Step 7 To continue, choose OK.
- The Platform Installation Wizard window displays.
- Step 8 To continue with the installation, choose Proceed.
- The Upgrade During Install window displays. Continue with the "If You Choose Proceed" section.
- If You Choose Proceed
- Step 9 Choose the type of installation to perform by doing the following steps. See Table 3 for more information on installation options:
- a. In the Upgrade During Install window, choose one of the options:
- • To upgrade to a later Service Release of the software during installation, choose Yes. Continue with the "Upgrade During Install" section.
- • To skip this step, choose No.
- • To return to the previous window, choose Back.
- b. In the Windows Upgrade window, choose No.
Note To perform a Windows Upgrade, that is, to upgrade from a Windows version of Cisco Unified CallManager to Cisco Unified CallManager 5.1(1), see Upgrading to Cisco Unified CallManager for more information.
- c. In the Basic Install window, choose Continue to install the software version on the DVD or configure the preinstalled software. Continue with the "Basic Installation" section.
Upgrade During Install
If you choose Yes in the Upgrade During Install window, the installation wizard installs the software version on the DVD first and then restarts the system. You then get prompted to enter certain network configuration parameter values and the location of the upgrade file.
- Step 10 After the system restarts, the Platform Installation Wizard window displays. To continue the installation, choose Proceed.
- The Upgrade During Install window displays.
Note If the installer pops up a window that states that it detected new hardware, press any key and then choose Install from the next window.
- Step 11 Choose Yes.
- The Install Upgrade Retrieval Mechanism Configuration window displays.
- Step 12 Choose the upgrade retrieval mechanism to use to retrieve the upgrade file:
- – SFTP — Retrieves the upgrade file from a remote server by using the Secure File Transfer Protocol (SFTP). Skip to the "Upgrade From a Remote Server" section.
- – FTP — Retrieves the upgrade file from a remote server by using File Transfer Protocol (FTP). Skip to the "Upgrade From a Remote Server" section.
- – LOCAL — Retrieves the upgrade file from a local CD or DVD. Continue with the "Upgrade From a Local Disc" section.
Upgrade From a Local Disc
Before you can upgrade from a local drive, you must download the appropriate patch file from Cisco.com and copy the file to a CD or DVD. Because of the size of the patch files, you will need to copy it to a DVD in most cases.
- The patch-file name has the following format:
-
cisco-ipt-k9-patchX.X.X.X-X.tar.gz.sgn - Where X.X.X.X-X represents the release and build number
-
Note Do not rename the patch file before you install it because the system will not recognize it as a valid file.
- Step 13 When the Local Patch Configuration window displays, enter the patch directory and patch name, if required, and choose OK.
Note You only need to enter the patch directory when the patch is not stored in the root directory of the CD or DVD.
- The Install Upgrade Patch Selection Validation window displays.
- Step 14 The window displays the patch file that is available on the CD or DVD. To update the system with this patch, choose Continue.
Upgrade From a Remote Server
If you chose to upgrade through an FTP or SFTP connection to a remote server, you must first configure the network settings.
- The Auto Negotiation Configuration window displays.
- Step 15 The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) by using automatic negotiation. You can change this setting after installation.
- – To enable automatic negotiation, choose Yes. The DHCP Configuration window displays.
Note: To use this option, your hub or Ethernet switch must support automatic negotiation.
- – To disable automatic negotiation, choose No. The NIC Speed and Duplex Configuration window displays.
- Step 16 If you chose to disable automatic negotiation, manually choose the appropriate NIC speed and duplex settings now and choose OK to continue.
- The DHCP Configuration window displays.
- Step 17 For network configuration, you can choose to either set up static network IP addresses for the node and gateway or to use Dynamic Host Configuration Protocol (DHCP).
- – If you have a DHCP server that is configured in your network and want to use DHCP, choose Yes. The system restarts and checks for network connectivity. Skip to the "Retrieving the Remote Patch" section.
- – If you want to configure static IP addresses for the node, choose No. The Static Network Configuration window displays.
- Step 18 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 7 for field descriptions.
- The DNS Client Configuration window displays.
- Step 19 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 7 for field descriptions.
- After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays.
Retrieving the Remote Patch
- Step 20 Enter the location and login information for the remote file server. See Table 7 for field descriptions. After the network restarts, the system connects to the remote server and retrieves a list of available upgrade patches.
- If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path. For example, if the upgrade file is in the patches directory, you must enter /patches. If the upgrade file is located on a Windows server, check with your system administrator for the correct directory path.
- The Install Upgrade Patch Selection window displays.
- Step 21 Choose the upgrade patch to install. The system downloads, unpacks, and installs the patch and then restarts the system running the upgraded software version.
- After the system restarts, the Preexisting Configuration Information window displays.
Using Preexisting Configuration Information
- Step 22 If you have preexisting configuration information that is stored on a floppy disc or a USB key, insert the disc or the USB key now and choose Continue. The installation wizard will read the configuration information during the installation process.
- The Platform Installation Wizard window displays.
- Step 23 To continue with the Platform Installation Wizard, choose Proceed.
- The Product Installation Configuration window displays.
- Step 24 To configure the platform now, choose Proceed.
- Step 25 In the Upgrade During Install window, choose No.
- Step 26 In the Windows Upgrade window, choose No.
- Step 27 In the Basic Install window, choose Continue. Continue with the "Basic Installation" section.
Basic Installation
- Step 28 When the Timezone Configuration displays, choose the appropriate time zone for the server and then choose OK.
- The Auto Negotiation Configuration window displays.
- Step 29 The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) by using automatic negotiation. You can change this setting after installation.
- – To enable automatic negotiation, choose Yes. The DHCP Configuration window displays.
- Note To use this option, your hub or Ethernet switch must support automatic negotiation.
- – To disable automatic negotiation, choose No. The NIC Speed and Duplex Configuration window displays.
- Step 30 If you chose to disable automatic negotiation, manually choose the appropriate NIC speed and duplex settings now and choose OK to continue.
- The DHCP Configuration window displays.
- Step 31 For network configuration, you can choose to either set up static network IP address for the node or to use Dynamic Host Configuration Protocol (DHCP).
- – If you have a DHCP server that is configured in your network and want to use DHCP, choose Yes. The network restarts, and the Administrator Login Configuration window displays.
- – If you want to configure static IP address for the node, choose No. The Static Network Configuration window displays.
- Step 32 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 7 for field descriptions.
- The DNS Client Configuration window displays.
- Step 33 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 7 for field descriptions.
- The network restarts by using the new configuration information, and the Administrator Login Configuration window displays.
- Step 34 Enter your Administrator login and password from Table 6.
- Note The Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. You will need the Administrator login to log in to Cisco Unified Communications Operating System Administration, the command line interface, and the Disaster Recovery System.
- The Certificate Signing Request Information window displays.
- Step 35 Enter your certificate signing request information from Table 6 and choose OK.
- The First Node Configuration window displays.
- Step 36 You can configure this server as either the first node in a Cisco Unified CallManager cluster or as a subsequent node.
- – To configure this server as the first Cisco Unified CallManager node, choose Yes and continue with the "Configure the First Node" section.
- – To configure this server as a subsequent node in the cluster, choose No and continue with the "Configure a Subsequent Node" section.
Configure the First Node
If you chose to configure the server as the first node in the cluster, the Network Time Protocol Client Configuration window displays. Cisco recommends that you use an external NTP server to ensure accurate system time on the first node. Ensure the external NTP server is stratum 9 or higher (meaning stratums 1-9). Subsequent nodes in the cluster will get their time from the first node.
- Step 37 Choose whether you want to configure an external NTP server or manually configure the system time.
- – To set up an external NTP server, choose Yes and enter the IP address, NTP server name, or NTP server pool name for at least one NTP server. You can configure up to five NTP servers, and Cisco recommends that you use at least three. Choose Proceed to continue with the installation.
- The system contacts an NTP server and automatically sets the time on the hardware clock.
- Note If the Test button displays, you can choose Test to check whether the NTP servers are accessible.
- – To manually configure the system time, choose No and enter the appropriate date and time to set the hardware clock. Choose OK to continue with the installation.
- The Database Access Security Configuration window displays.
- Step 38 Enter the Database Access Security password from Table 6.
- Note The Database Access Security password must start with an alphanumeric character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. The system uses this password to authorize communications between nodes, and you must ensure this password is identical on all nodes in the cluster.
- The SMTP Host Configuration window displays.
- Step 39 If you want to configure an SMTP server, choose Yes and enter the SMTP server name.
- Note You must configure an SMTP server to use certain platform features; however, you can also configure an SMTP server later by using the platform GUI or the command line interface.
- The Platform Configuration Confirmation window displays.
- Step 40 To continue with the installation, choose OK; or to modify the platform configuration, choose Back.
- When you choose OK, the Application User Password Configuration window displays.
- Step 41 Enter the Application User Password from Table 6 and confirm the password by entering it again.
- Step 42 Choose OK.
- The Cryptographic Export Warning window displays, and the systems installs and configures the software.
- Step 43 When the installation process completes, you get prompted to log in by using the Administrator account and password.
- Step 44 Complete the post-upgrade tasks that are listed in the "Post-Installation Tasks" section.
Configure a Subsequent Node
To configure a subsequent node in the cluster, follow these steps.
Caution You must configure a subsequent node on the first node before you install it. From Cisco Unified CallManager Administration on the first node, choose System>Server. For more information, see the Cisco Unified CallManager Administration Guide''.
- The First Node Access Configuration window displays.
- Step 45 Enter the First Node Access Configuration information from Table 5.
- The SMTP Host Configuration window displays.
- Step 46 If you want to configure an SMTP server, choose Yes and enter the SMTP server name.
- NOTE: You must configure an SMTP server to use certain platform features. However, you can also configure an SMTP server later by using the platform GUI or the command line interface.
- The Platform Configuration Confirmation window displays.
- Step 47 To start installing the software, choose OK, or, if you want to change the configuration, choose Back.
- Step 48 When the installation process completes, you get prompted to log in by using the Administrator account and password.
- Step 49 Complete the post-upgrade tasks that are listed in the "Post-Installation Tasks" section.
Post-Installation Tasks
After installing Cisco Unified CallManager on your server, you must set some configuration parameters for Cisco Unified CallManager and perform other post-installation tasks before you can begin using it. Perform these tasks for the server that you install and complete the tasks before other servers in the cluster are installed.
For post-installation tasks that you must complete after the installation, see Table 6.
- INSERT TABLE
Changing the Default Cisco Unified CallManager Application User Passwords
Cisco Unified CallManager installation sets all Application User passwords to the same Application User password that you entered during installation. Cisco recommends that you log in to Cisco Unified CallManager Administration and change these passwords. Refer to Cisco Unified CallManager System Guide for the procedure for changing a password.
Accessing Cisco Unified CallManager Serviceability
To access Cisco Unified CallManager Administration or Cisco Unified CallManager Serviceability, you will need to use a web browser from a PC with network access to the Cisco Unified CallManager server.
Even though all Cisco Unified CallManager services are installed on each server in the cluster, you must manually activate the services that you want to run on each server in the cluster through Cisco Unified CallManager Serviceability. For service recommendations and more information, refer to Cisco Unified CallManager Serviceability Administration Guide and Cisco Unified CallManager Serviceability System Guide.
To activate services through Cisco Unified CallManager Serviceability, follow this procedure:
Procedure
- Step 1 Open a web browser on a computer with network access to the Cisco Unified CallManager server.
- Step 2 Enter the following url:
- where ccm_server specifies the IP address or hostname of the Cisco Unified CallManager server.
- Step 3 Enter the Cisco Unified CallManager Application user name and password.
- Step 4 From the Navigation menu, choose Cisco Unified CallManager Serviceability and click Go.
- Step 5 From the menu bar, click Tools > Service Activation.
- Step 6 Choose a server from the drop-down menu.
- Step 7 Check the Service Names check boxes for the services to activate.
- Step 8 Click Save.
Configuring the Database
After installing Cisco Unified CallManager, you use Cisco Unified CallManager Administration to begin configuring the database. The Cisco Unified CallManager database contains information and parameters that relate to the system as a whole, to connected devices, and to individual users. The following list describes a few tasks that you must perform in Cisco Unified CallManager Administration or Cisco Unified CallManager Serviceability:
- 1. In Cisco Unified CallManager Serviceability, activate the services that you want to run on each server in the cluster.
- 2. Configure system-level settings, such as Cisco Unified CallManager Groups.
- 3. Design and configure your dialing plan.
- 4. Configure media resources for conferences, music on hold, and so on.
- 5. Configure systemwide features, Cisco Unified IP Phone services, Cisco Unified CallManager Extension Mobility, Cisco Unified CallManager Attendant Console, and Cisco Unified CallManager Assistant.
- 6. Install and configure the gateways.
- 7. Enable computer telephony integration (CTI) application support; then, install and configure the desired CTI applications.
- 8. Configure the users.
- 9. Configure and install the phones; then, associate users with the phones.
For more information about configuring the Cisco Unified CallManager database, refer to the Cisco Unified CallManager Administration Guide, the Cisco Unified CallManager System Guide, or online help in the Cisco Unified CallManager application.
Examining Log Files
If you encounter problems with the installation, you can obtain and examine the install log files by entering the following commands in Command Line Interface.
- To obtain a list of install log files from the command line, enter
-
CLI>file list install
-
- To view the log file from the command line, enter
-
CLI>file view install log_file
-
- where log_file is the log file name.
You can also view logs by using the Cisco Unified CallManager Real-Time Monitoring Tool (RTMT). For more information on using and installing the Cisco Unified CallManager RTMT, refer to the Cisco Unified CallManager Serviceability Administration Guide.
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. This section explains the product documentation resources that Cisco offers.
Cisco.com
You can access the most current Cisco documentation at this URL:
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
Product Documentation DVD
The Product Documentation DVD is a library of technical product documentation on a portable medium. The DVD enables you to access installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the HTML documentation and some of the PDF files found on the Cisco website at this URL:
The Product Documentation DVD is created and released regularly. DVDs are available singly or by subscription. Registered Cisco.com users can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation Store at this URL:
Ordering Documentation
You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order Cisco documentation at the Product Documentation Store at this URL:
If you do not have a user ID or password, you can register at this URL:
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
From this site, you will find information about how to do the following:
- C• Report security vulnerabilities in Cisco products
- • Obtain assistance with security incidents that involve Cisco products
- • Register to receive security information from Cisco
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
- • For emergencies only — security-alert@cisco.com
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
- • For nonemergencies — psirt@cisco.com
In an emergency, you can also reach PSIRT by telephone:
- • 1 877 228-7302
- • 1 408 525-6532
- Tip
- - We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.
- - Never use a revoked encryption key or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
- The link on this page has the current PGP key ID in use.
- - If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending any sensitive material.
[edit] Product Alerts and Field Notices
Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive Cisco Product Alerts and Cisco Field Notices by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information.
To access the Product Alert Tool, you must be a registered Cisco.com user. (To register as a Cisco.com user, go to this URL: http://tools.cisco.com/RPF/register/register.do) Registered users can access the tool at this URL:
[edit] Obtaining Technical Assistance
[edit] Obtaining Additional Publications and Information
