Feedback
Contents
- Cisco Unified Communications Manager installation
- Installation scenarios
- Install software from a DVD on the first node
- Install software from a DVD on a subsequent node
- Apply a patch during installation of the first node
- Apply a patch during installation of a subsequent node
- Install a new node in an existing cluster
- Reuse the MCS-7828
- Parallel installations of cluster nodes
- Pre-installation tasks
- Important considerations
- Frequently asked questions
- Installation time
- User name and password requirements
- Password considerations
- Server support
- Software restrictions
- Browser requirements
- Verify DNS registration
- Node Server Installation Information
- Licensing
- Answer file generator
- Network errors during installation
- Installation overview
- Install new operating system and application
- Installation wizard
- Install software
- Enter preexisting configuration information
- Apply a patch
- Upgrade from a local disk
- Upgrade from a remote server
- Basic software installation
- Set up first node
- Set up subsequent node
- Post-installation tasks
- Change default application user passwords
- Cisco Unified Serviceability
- Services activation
- Install licenses
- Apply security
- Set up database
- Log files
- COP files, dial plans, and locales
- COP file installation
- Dial plan installation
- Locale installation
- Install locales
- Locale files
- Error messages
- Supported products
Cisco Unified Communications Manager installation
Installation scenarios
You can use this document to perform the following different installation scenarios:
- Install software from a DVD on the first node
- Install software from a DVD on a subsequent node
- Apply a patch during installation of the first node
- Apply a patch during installation of a subsequent node
- Add a new node to an existing cluster
- Add a new node to an existing cluster
- Reuse the MCS-7828
This document provides an overview of the high-level tasks that you must perform for each of these installation scenarios. Each high-level task also includes a link to another section of the document, which you can follow for detailed information about the task.
Note
For information about replacing a server or cluster, refer to Replacing a Single Server or Cluster for Cisco Unified Communications Manager.
- Install software from a DVD on the first node
- Install software from a DVD on a subsequent node
- Apply a patch during installation of the first node
- Apply a patch during installation of a subsequent node
- Install a new node in an existing cluster
- Reuse the MCS-7828
- Parallel installations of cluster nodes
Install software from a DVD on the first node
Procedure
Install software from a DVD on a subsequent node
Procedure
Apply a patch during installation of the first node
ProcedureYou can upgrade to a later release by downloading and applying a patch during installation of the first node.
Apply a patch during installation of a subsequent node
ProcedureYou can upgrade to a later release by downloading and applying a patch during installation of a subsequent node.
Install a new node in an existing cluster
Procedure
After you install a new node in an existing cluster, all phones that are registered to the cluster are reset.
Reuse the MCS-7828
ProcedureIf you have installed Cisco Business Edition 5000 on an MCS-7828 server, and you decide that you need to migrate to separate Cisco Unified Communications Manager and Cisco Unity Connection environments for increased scalability and capacity, you can reuse that MCS-7828 server to run Cisco Unified Communications Manager in a MCS-7825 cluster. Although you can reuse the server, you must reenter your data on the server manually. You must also obtain another server to run Cisco Unity Connection.
Note
You cannot install Cisco Unified Communications Manager on an MCS-7828 server unless you have previously installed Cisco Business Edition 5000.
To migrate from Cisco Business Edition 5000 to separate Cisco Unified Communications Manager and Cisco Unity Connection environments, perform the following steps.
Parallel installations of cluster nodes
When you install a cluster, you can begin the installation of the first node and subsequent nodes at the same time. When the installation program prompts you to designate the first node as the first node, stop installing on the subsequent nodes until the installation completes on the first node. Then configure the subsequent node(s) on the first node. You can then continue the installation on the subsequent nodes. For optimal performance, you should choose the Skip option rather than the Proceed option in the installation program.
Pre-installation tasks
ProcedurePerform all pre-installation tasks to ensure that you can successfully install the Cisco Unified Communications Manager.
Step 1 Read this entire document to familiarize yourself with the installation procedure. Step 2 Verify the integrity of any new server hardware (such as hard drives and memory) by running any manufacturer-provided utilities. Step 3 Ensure that your servers are listed as supported hardware and sized appropriately to support the load of the cluster. Make sure to account for any growth that has occurred since initial system configuration. For information about the capacity of server models, refer to the documentation at http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html. Step 4 If you are installing a cluster or adding a node, verify that the links between servers meet the 80-ms round-trip time (RTT) requirement and that you have enough bandwidth to support database replication. For more information on the 80-ms RTT requirement, refer to the Cisco Unified Communications Solution Reference Network Design (SRND) based on Cisco Unified Communications Manager, which you can find at http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guides_list.html. Step 5 If you are getting the system time from an NTP server (mandatory for VMware deployments), verify that the first node can synchronize with the NTP server before you install a subsequent node. Log into the Command Line Interface on the first node and enter the following command: utils ntp status
Note To avoid potential compatibility, accuracy, and network jitter problems, the external NTP servers that you specify for the primary node must be NTP v4 (version 4). If you are using IPv6 addressing, external NTP servers must be NTP v4.
For more information, see the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions.
Caution If the first node fails to synchronize with an NTP server, installation of a subsequent node can also fail.
Step 6 If your firewall is not in the routing path, disable the firewall between nodes, if possible. Also, increase the firewall timeout settings until after you complete the installation. To temporarily allow network traffic in and out of the nodes (for example, setting the firewall rule for these nodes to IP any/any) does not always suffice. The firewall might still close necessary network sessions between nodes due to timeouts. Step 7 Do not run Network Address Translation (NAT) or Port Address Translation (PAT) between Cisco Unified Communications Manager nodes. Step 8 Record the network interface card (NIC) speed and duplex settings of the switch port to which you will connect the new server. You should configure the same NIC settings on the server and on the switch port. For GigE (1000/FULL), you should set NIC and switch port settings to Auto/Auto; do not set hard values.
Enable PortFast on all switch ports that are connected to Cisco servers. With Portfast enabled, the switch immediately brings a port from the blocking state into the forwarding state by eliminating the forwarding delay [the amount of time that a port waits before changing from its Spanning-Tree Protocol (STP) learning and listening states to the forwarding state].
Step 9 If you use DNS, verify that all servers on which you plan to install Cisco Unified Communications Manager are properly registered in DNS. Step 10 Obtain a license file.
Note For more information on specifying the required number of licenses, refer to the Cisco Unified Communications Manager Administration Guide.
Step 11 Record the configurations settings for each server that you plan to install. Step 12 If the server is running VMware EX/ESXi and the motherboard has an ICH10 onboard SATA controller, you must disable the SATA controller in the BIOS. The ICH10 onboard SATA controller is not supported by EX/ESXi. Step 13 For Cisco Unified Communications Manager, configure any subsequent nodes on the first node before you install a subsequent node. From Cisco Unified Communications Manager Administration on the first node, choose and configure the IP address for the subsequent nodes. For more information, see the Cisco Unified Communications Manager Administration Guide.
Important considerations
Before you proceed with the installation, consider the following requirements and recommendations:
- Be aware that when you install on an existing server, the hard drive gets formatted, and all existing data on the drive gets overwritten.
- Do not install Cisco Unified Communications Manager in a large Class A or Class B subnet that contains a large number of devices. When you install Cisco Unified Communications Manager in a large subnet with a large number devices in that subnet, the Address Resolution Protocol (ARP) table can fill up quickly (maximum 1024 entries, by default). When the ARP table gets full, Cisco Unified Communications Manager can have difficulty talking to endpoints and cannot add more phones.
- Ensure that you connect each Cisco Unified Communications Manager node to an uninterruptible power supply (UPS) to provide backup power and protect your system. Failure to do so may result in damage to physical media and require a new installation.
If you want the Cisco Unified Communications Manager node to automatically monitor UPS signaling and automatically initiate a graceful shutdown upon power loss, you should use specific UPS and server models. For more information on supported models and configurations, refer to the Release Notes for Cisco Unified Communications Manager.
Note
You must connect MCS-7816 and MCS-7825 servers to a UPS in order to prevent file system corruption during power outages.
- Install the Cisco Unified Communications Manager software on the first node 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.
- When you enter the Security password on the first node, be sure that you write it down and save it. You must enter the same password on each subsequent node that you install in the cluster. Install the software during off-peak hours or a maintenance window to avoid impact from interruptions.
- All servers in a cluster must run the same release of Cisco Unified Communications Manager. The only exception is during a cluster software upgrade, during which a temporary mismatch is allowed.
- 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.
- The MTU size that you configure for a node must not exceed the lowest MTU size that is configured on any link in your network and must be the same on all nodes in a cluster. The default server MTU size is 1500 bytes. You can change the MTU size using the cli command .
NoteWhen packets on UDP port 8500 that have the DF bit set are exchanged between nodes, if there is any policy on the WAN router to clear the DF bit and fragment large packets, this may cause dbreplication issues.
- Do not attempt to perform any configuration tasks during the installation.
- Do not install any Cisco-verified applications until you complete the installation.
- Be aware that directory names and filenames that you enter while you are running the installation program are case-sensitive.
- Disk mirroring on server model 7825 I3 with 160 GB SATA disk drives takes approximately 3 hours.
- Disk mirroring on server model 7828 I3 with 250 GB SATA disk drives takes approximately 4 hours.
- For a short period of time after you install Cisco Unified Communications Manager or switch over after upgrading to a different product version, settings changes made by phone users might get unset. Examples of phone user settings include call forwarding and message waiting indication light settings. This can occur because Cisco Unified Communications Manager synchronizes the database after an installation or upgrade, which can overwrite phone user settings changes.
- Boot the Cisco Unified CM server with the Cisco Unified CM 9.0 or later recovery disc.
- When prompted, choose option C to wipe off all data from the system. Option C indicates "Cleaning the system to set to bare metal state." You can now proceed with the installation of the earlier versions of Cisco Unified CM.
- When you insert or remove a USB drive, you might see error messages on the console similar to "sdb: assuming drive cache: write through." You can safely ignore these messages.
- Carefully read the information that follows before you proceed with the installation.
- If the server is running VMware EX/ESXi and the motherboard has an ICH10 onboard SATA controller, you must disable the SATA controller in the BIOS. The ICH10 onboard SATA controller is not supported by EX/ESXi. See the pre-installation tasks for more information.
Related Tasks
Frequently asked questions
The following section contains information about commonly asked questions and responses. Review this section carefully before you begin the installation.
- Installation time
- User name and password requirements
- Password considerations
- Server support
- Software restrictions
User name and password requirements
Note
The system checks your passwords for strength. See topics related to password considerations for guidelines on creating a strong password.
During the installation, you must specify the following user names and passwords:
Administrator account user name and password
You use the Administrator Account user name and password to log in to the following areas:
- Cisco Unified Communications Operating System Administration
- Disaster Recovery System
- Command Line Interface
To specify the Administrator Account user name and password, follow these guidelines:
- Administrator Account user name—The Administrator Account user name must start with an alphabetic character and can contain alphanumeric characters, hyphens and underscores.
- Administrator Account password—The Administrator Account password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.
You can change the Administrator Account password or add a new Administrator account by using the command line interface. For more information, see the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions.
Application user name and password
You use the Application User name and password to access applications that are installed on the system, including the following areas:
- Cisco Unified Communications Manager Administration
- Cisco Unified Serviceability
- Real Time Monitoring Tool
- Cisco Unified Reporting
To specify the Application User name and password, follow these guidelines:
- Application User name - The Application User name must start with an alphabetic character and can contain alphanumeric characters, hyphens and underscores.
- Application User password - The Application User password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.
You can change the Application User name and password by using the command line interface. For more information, see the Command Line Interface Reference Guide for Cisco Unified Communications Solutions.
Security password
Cisco Unified Communications Manager systems use this password to authorize communications between nodes; this password must be identical on all nodes in the cluster.
The Security password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores.
Related References
Password considerations
The installation wizard checks to ensure that you enter a strong password. To create a strong password, follow these recommendations:
- Mix uppercase and lowercase letters.
- Mix letters and numbers.
- Include special symbols.
- Remember that longer passwords are stronger and more secure than shorter ones.
Avoid the following types of passwords:
- Do not use recognizable words, such as proper names and dictionary words, even when combined with numbers.
- Do not invert recognizable words.
- Do not use word or number patterns, like aaabbb, qwerty, zyxwvuts, 123321, and so on.
- Do not use recognizable words from other languages.
- Do not use personal information of any kind, including birthdays, postal codes, names of children or pets, and so on.
Server support
For information about Cisco Unified Communications Manager supported server models, refer to the following documentation:
- Release notes for your product release
- http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html.
Software restrictions
You must do all software installations and upgrades by using 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 Communications Manager with this version of Cisco Unified Communications Manager.
Browser requirements
You can access Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, Cisco Unified Reporting, Cisco Unified Communications Operating System Administration, and Disaster Recovery System by using the browsers and operating systems listed in the following table. Cisco does not support or test other browsers.
Node Server Installation Information
Use the following table to record the information about your server. Gather this information for each Cisco Unified Communications Manager 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, if you choose not to set up an SMTP host during installation, the parameter still displays, but you do not need to enter a value.
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 you can change a field after installation, and if you can, it provides the appropriate Command Line Interface (CLI) command.
Caution
If Cisco Unified Communications Manager is running on VMware, changing some of these values after installation will require you to obtain updated licenses.
Table 2 Node configuration data Parameter
Description
Can Entry Be Changed After Installation?
Administrator ID
This field specifies the administrator account user ID that you use for secure shell access to the CLI, for logging into Cisco Unified Communications Operating System Administration and for logging into the Disaster Recovery System.
No, you cannot change the entry after installation.
Note After installation, you can create additional administrator accounts, but you cannot change the original administrator account user ID.
Your entry:
Administrator Password
This field specifies the password for the Administrator account, which you use for secure shell access to the CLI, for logging into Cisco Unified Communications Operating System Administration and for logging into the Disaster Recovery System.
Ensure the password is at least six characters long; it can contain alphanumeric characters, hyphens, and underscore.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
Application User Name
You use the Application User name as the default user name for applications that are installed on the system, including Cisco Unified Communications Manager and Cisco Unified Serviceability.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
Application User Password
You use the Application User password as the default password for applications that are installed on the system, including Cisco Unified Communications Manager and Cisco Unified Serviceability.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
Country
From the list, choose the appropriate country for your installation.
Note The value you enter gets used to generate a Certificate Signing Request (CSR).
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
DHCP
If you want to use DHCP to automatically configure the network settings on your server, choose Yes.
If you choose Yes, you do not get prompted for DNS or static configuration settings.
If you choose No, you must enter a hostname, IP Address, IP Mask, and Gateway.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
DNS Enable
A DNS server resolves a hostname into an IP address or an IP address into a hostname. If you do not have a DNS server, enter No.
If you have a DNS server, Cisco recommends that you enter Yes to enable DNS.
Note When DNS is not enabled, you should only enter IP addresses (not host names) for all network devices in your in your Cisco Unified Communications Manager network.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
DNS Primary
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.
Consider this field mandatory if DNS is set to yes (DNS enabled).
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
DNS Secondary (optional)
Enter the IP address of the DNS server that you want to specify as the optional secondary DNS server.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
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.
Yes, you can change the entry after installation by using the following CLI command:
CLI > set network
Your entry:
Gateway Address
Enter the IP address of the network gateway.
If you do not have a gateway, you must still set this field to 255.255.255.255. Not having a gateway may limit you to only being able to communicate with devices on your subnet.
If DHCP is set to No, consider this field mandatory.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
Hostname
Enter a host name that is unique to your server.
The host name can comprise up to 64 characters and can contain alphanumeric characters and hyphens. The first character cannot be a hyphen.
If DHCP is set to No, consider this field mandatory.
Yes, you can change the entry after installation.
For information, refer to the document Changing the IP Address and Host Name for Cisco Unified Communications Manager for your product release at the following URL: http://www.cisco.com/en/US/ucts/sw/ps556/prod_maintenance_guides_list.html.voicprod.
Your entry:
IP Address
Enter the IP address of your server.
If DHCP is set to No, consider this field mandatory.
Yes, you can change the entry after installation.
For information, refer to the document Changing the IP Address and Host Name for Cisco Unified Communications Manager for your product release at the following URL: http://www.cisco.com/en/US/ucts/sw/ps556/prod_maintenance_guides_list.html.voicprod.
Your entry:
IP Mask
Enter the IP subnet mask of this machine.
If DHCP is set to No, consider this field mandatory.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
Location
Enter the location of the server.
The system uses this information to generate certificate signing requests (CSRs), which are used to obtain third-party certificates.
You can enter any location that is meaningful within your organization. Examples include the state or the city where the server is located.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
MTU Size
The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network. Enter the MTU size in bytes for your network. The default MTU is 1500 bytes.
The MTU size that you configure must not exceed the lowest MTU size that is configured on any link in your network. The MTU setting must be the same on all nodes in a cluster.
Caution When packets on UDP port 8500 that have the DF bit set are exchanged between nodes, if there is any policy on the WAN router to clear the DF bit and fragment large packets, this may cause dbreplication issues.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
NIC Duplex
Choose the duplex mode for the network interface card (NIC), either Full or Half.
Note This parameter only displays when you choose not to use Automatic Negotiation.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
NIC Speed
Choose the speed for the NIC, either 10 megabits per second or 100 megabits per second.
Note This parameter only displays when you choose not to use Automatic Negotiation.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
NTP Server
Enter the hostname or IP address of one or more network time protocol (NTP) servers with which you want to synchronize. NTP is required for VMware deployments.
You can enter up to five NTP servers.
Note To avoid potential compatibility, accuracy, and network jitter problems, the external NTP servers that you specify for the primary node must be NTP v4 (version 4). If you are usingIPv6 addressing, external NTP servers must be NTP v4.
Yes, you can change the entry after installation by using the Cisco Unified Communications Operating System:
Your entry:
Organization
Enter the name of your organization.
Tip You can use this field to enter multiple organizational units. To enter more than one organizational unit name, separate the entries with a comma. For entries that already contain a comma, enter a backslash before the comma that is included as part of the entry.
Note The value you enter gets used to generate a Certificate Signing Request (CSR).
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
Security Password
Servers in the cluster use the security password to communicate with one another.
The password must contain at least six alphanumeric characters. It can contain hyphens and underscores, but it must start with an alphanumeric character.
Note Save this password. You will be asked to enter the same security password for each subsequent node in the cluster.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
SMTP Location
Enter the hostname or IP address for the SMTP server that is used for outbound e-mail.
The hostname can contain alphanumeric characters, hyphens, or periods, but it must start with an alphanumeric character.
Note You must fill in this field if you plan to use electronic notification.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
State
Enter the state where the server is located.
Note The value you enter gets used to generate a Certificate Signing Request (CSR).
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
Time Zone
This field specifies the local time zone and offset from Greenwich Mean Time (GMT).
Choose the time zone that most closely matches the location of your machine.
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
Unit
Enter your unit.
Note The value you enter gets used to generate a Certificate Signing Request (CSR).
Yes, you can change the entry after installation by using the following CLI command:
Your entry:
Licensing
Licensing helps manage Cisco Unified Communications Manager licenses and enforces the licenses for Cisco Unified Communications Manager applications and the number of IP phones. See the Enterprise License Manager User Guide for information about generating and installing licenses.
Answer file generator
Cisco Unified Communications Answer File Generator, a web application, generates answer files for unattended installations. Individual answer files get copied to the root directory of a USB key or a floppy diskette and are used in addition to your Cisco Unified Communications Manager product DVD during the installation process.
The web application supports the following features:
- Allows simultaneous generation and saving of answer files for unattended installs on the publisher server and all subscriber servers.
- Provides syntactical validation of data entries.
- Provides online help and documentation.
The following usage requirements apply:
- The web application supports only fresh installs and does not support upgrades.
- If DHCP client is being used on the publisher server, and subscriber server answer files are also being generated, you must specify the publisher server IP address.
You can access the Cisco Unified Communications Answer File Generator at the following URL:
http://www.cisco.com/web/cuc_afg/index.html
The Cisco Unified Communications Answer File Generator supports Internet Explorer version 6.0 or higher and Mozilla version 1.5 or higher.
Note
Cisco requires that you use USB keys that are compatible with Linux 2.4. Cisco recommends that you use USB keys that are preformatted to be compatible with Linux 2.4 for the configuration file. These keys will have a W95 FAT32 format.
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 that you enter. If it cannot connect, 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) - This option allows you to review and modify the networking configuration. When detected, the installation program returns to the network configuration windows. Networking gets validated after you complete each networking window, so the message might display multiple times.
- 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. If you choose to ignore network errors, the installation may fail.
Installation overview
The installation process allows you to perform a basic installation or upgrade to a newer service release during the installation.
For a more detailed description of the different installation types, see the following table.
Install new operating system and application
This section describes how to install the operating system and the Cisco Unified Communications Manager application. You install the operating system and application by running one installation program.
Installation wizard
For instructions on how to navigate within the installation wizard, see the following table.
Table 4 Installation wizard navigation To Do This
Press This
Move to the next field
Tab
Move to the previous field
Alt-Tab
Choose an option
Space bar or Enter
Scroll up or down in a list
Up or down arrow
Go to the previous window
Space bar or Enter to choose Back (when available)
Get help information on a window
Space bar or Enter to choose Help (when available)
Install software
ProcedureTo start the installation, follow this procedure.
Note
If you are installing a subsequent node or adding a node to an existing cluster, you must configure the host name or IP address of the new node on the first node in the cluster. From Cisco Unified Communications Manager Administration on the first node, choose and enter the IP address or host name of the subsequent node. For more information, see the Cisco Unified Communications Manager Administration Guide.
Note
Because the Cisco Unified Communications Manager Business Edition 5000 software was preinstalled on the server, you do not need to reinstall the software unless you want to reimage the server with a later product release. Go directly to the procedure to enter the configuration information.
Step 1 If you have a USB key with configuration information that the Answer File Generator generated, insert it now.
Note If you have a new server with the software preinstalled, you do not need to install from a DVD, unless you want to reimage the server with a later product release. Go directly to the procedure to enter the configuration information. Step 2 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 DVD Found window displays. Step 3 To perform the media check, choose Yes or, to skip the media check, choose No. The media check checks the integrity of the DVD. If your DVD passed the media check previously, you might choose to skip the media check.
Step 4 If you choose Yes to perform the media check, the Media Check Result window displays. Perform these tasks: Step 5 The system installer performs the following hardware checks to ensure that your system is correctly configured. If the installer makes any changes to your hardware configuration settings, you will get prompted to restart your system. Leave the DVD in the drive during the reboot:
- First, the installation process checks for the correct drivers, and you may see the following warning:
No hard drives have been found. You probably need to manually choose device drivers for install to succeed. Would you like to select drivers now?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.
Note For MCS 7825 H3 and MCS 7828 H3 Server models, the installation process detects and disables the SATA RAID, if enabled. The System Rebooting Intermediately window appears with the message
System is going to reboot for SATA RAID to be disabled in BIOS Press any key to continueThis disables the SATA RAID and reboots the system. On reboot, the installation will continue and will activate the Linux SW RAID.
Note If this step repeats, choose Yes again.
- If the installation program must install a BIOS update, a notification appears telling you that the system must reboot. Press any key to continue with the installation.
After the hardware checks complete, the Product Deployment Selection window displays.
Step 6 In the Product Deployment Selection window, select the product to install; then, choose OK. You can choose from the following options:
- Cisco Unified Communications Manager
- Cisco Unity Connection
- Cisco Unified Communications Manager Business Edition 5000 (includes Cisco Unified Communications Manager and Cisco Unity Connection)
- Cisco Enterprise License Manager
Note The window indicates which products are supported and not supported by your hardware. If only one product is supported, you do not choose which product to install.
Note As part of this install, Enterprise License Manager is installed automatically. Following the install, Enterprise License Manager can be used to provide simplified, enterprise-wide management of user-based licensing, including license fulfillment. Enterprise License Manager handles licensing fulfillment, supports allocation and reconciliation of licenses across supported products, and provides enterprise level reporting of usage and entitlement. For more information, see the Enterprise License Manager User Guide.
Step 7 If software is currently installed on the server, the Overwrite Hard Drive window opens and displays the current software version on your hard drive 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 8 Choose one of the following options:
- To enter your configuration information manually and have the installation program install the configured software on the server, choose Proceed and continue with this procedure.
- To do any of the following tasks, choose Skip and perform the procedure to enter the configuration information.
- Manually configure the software that is preinstalled on your server - In this case you do not need to install the software, but you must configure the preinstalled software.
- Perform an unattended installation - In this case, you provide preexisting configuration information on a USB key or floppy disk.
- Install the software before manually configuring it - In this case the installation program installs the software, then prompts you to configure it manually. You can choose Skip if you want to preinstall the application on all your servers first and then enter the configuration information at a later time. This method might cause you to spend more time performing the installation than the other methods.
Step 9 Choose the type of installation to perform by doing the following steps. See Installation overview for more information on installation options. In the Apply Additional Release window, choose one of the options:
Step 10 In the Basic Install window, choose Continue to install the software version on the DVD or configure the preinstalled software. Continue to perform the basic software installation procedure.
Enter preexisting configuration information
ProcedureStart here if you have a server that has the product preinstalled or if you chose Skip in the Platform Installation Wizard window.
Step 1 After the system restarts, the Preexisting Installation Configuration window displays. Step 2 If you have preexisting configuration information that the Answer File Generator created, 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.
Note If a popup window states that the system detected new hardware, press any key and then choose Install from the next window.
The Platform Installation Wizard window displays.
Step 3 To continue with the Platform Installation Wizard, choose Proceed. Step 4 Choose the type of installation to perform by doing the following steps. See Installation overview for more information on installation options. In the Apply Additional Release window, choose one of the options:
Step 5 In the Basic Install window, choose Continue. Continue to perform the basic software installation procedure.
Apply a patch
ProcedureIf you choose Yes in the Apply a Patch window, the installation wizard installs the software version on the DVD first and then restarts the system. You must obtain the appropriate upgrade file from Cisco.com before you can upgrade during installation.
Note
You can upgrade to any supported higher release, so long as you have a full patch, not an ES or an SR, in which case you can only upgrade to a later service release within the same maintenance release.For information about supported upgrades, see the Release Notes for your product release and the Cisco Unified Communications Manager Compatibility Matrix at http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html.
You can access the upgrade file during the installation process from either a local disk (DVD) or from a remote FTP or SFTP server.
Step 1 The Install Upgrade Retrieval Mechanism Configuration window displays. Step 2 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.
- FTP - Retrieves the upgrade file from a remote server by using File Transfer Protocol (FTP). Skip to the Upgrade from a remote server.
- LOCAL - Retrieves the upgrade file from a local DVD. Continue with the Upgrade from a local disk.
Upgrade from a local disk
ProcedureBefore you can upgrade from a local disk, you must download the appropriate patch file from Cisco.com and use it to create an upgrade DVD. You must create an ISO image on the DVD from the upgrade file. Just copying the ISO file to a DVD will not work.
Step 1 When the Local Patch Configuration window displays, enter the patch directory and patch name, if required, and choose OK. The Install Upgrade Patch Selection Validation window displays.
Step 2 The window displays the patch file that is available on the DVD. To update the system with this patch, choose Continue. Step 3 Choose the upgrade patch to install. The system installs the patch, then restarts the system with the upgraded software version running. After the system restarts, the Preexisting Configuration Information window displays.
Step 4 To continue the installation, choose Proceed. The Platform Installation Wizard window displays.
Step 5 To continue the installation, choose Proceed or choose Cancel to stop the installation. If you choose Proceed, the Apply Patch window displays. Continue with the next step.
If you choose Cancel, the system halts, and you can safely power down the server.
Step 6 When the Apply Patch window displays, choose No. Step 7 The Windows Upgrade window displays. Step 8 Choose No and continue with the Basic software installation.
Upgrade from a remote server
ProcedureBefore you can upgrade from a remote server, you must download the appropriate patch file from Cisco.com to an FTP or SFTP server that the server can access.
If you are upgrading from release 5.1(3), you must download the appropriate patch file from Cisco.com, create an ISO image DVD from the patch file, then copy the contents of the DVD to a remote FTP or SFTP server that the server can access.
Cisco allows you to use any SFTP server product but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP). CTDP partners, such as GlobalSCAPE, certify their products with specified version of Cisco Unified Communications Manager. For information on which vendors have certified their products with your version of Cisco Unified Communications Manager, refer to http://www.cisco.com/pcgi-bin/ctdp/Search.pl. For information on using GlobalSCAPE with supported Cisco Unified Communications versions, refer to http://www.globalscape.com/gsftps/cisco.aspx.Cisco uses the following servers for internal testing. You may use one of the servers, but you must contact the vendor for support:
- Open SSH (for Unix systems. Refer to http://sshwindows.sourceforge.net/)
- Cygwin (http://www.cygwin.com/)
- Titan (http://www.titanftp.com/)
Note
For issues with third-party products that have not been certified through the CTDP process, contact the third-party vendor for support.
If you chose to upgrade through an FTP or SFTP connection to a remote server, you must first configure network settings so that the server can connect to the network.
Step 1 The Auto Negotiation Configuration window displays. Step 2 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.
Note To use this option, your hub or Ethernet switch must support automatic negotiation.
Step 3 If you chose to disable automatic negotiation, manually choose the appropriate NIC speed and duplex settings now and choose OK to continue. The MTU Configuration window displays.
Step 4 In the MTU Configuration window, you can change the MTU size from the operating system default. The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network. If you are unsure of the MTU setting for your network, use the default value.
Caution If you configure the MTU size incorrectly, your network performance can be affected.
- To accept the default value (1500 bytes), choose No.
- To change the MTU size from the operating system default, choose Yes, enter the new MTU size, and choose OK.
The DHCP Configuration window displays.
Step 5 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). Static IP addresses are recommended. If you use DHCP, use static DHCP. Step 6 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Node Server Installation Information for field descriptions. The DNS Client Configuration window displays.
Step 7 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Node Server Installation Information for field descriptions. After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays.
Step 8 Enter the location and login information for the remote file server. 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, remember that you are connecting to an FTP or SFTP server, so use the appropriate syntax, including:
- Begin the path with a forward slash (/) and use forward slashes throughout the path.
- The path must start from the FTP or SFTP root directory on the server, so you cannot enter a Windows absolute path, which starts with a drive letter (for example, C:).
The Install Upgrade Patch Selection window displays.
Step 9 Choose the upgrade patch to install. The system downloads, unpacks, and installs the patch and then restarts the system with the upgraded software version running. After the system restarts, the Preexisting Configuration Information window displays.
Step 10 To continue the installation, choose Proceed. The Platform Installation Wizard window displays.
Step 11 To continue the installation, choose Proceed or choose Cancel to stop the installation. If you choose Proceed, the Apply Patch window displays. Continue with the next step.
If you choose Cancel, the system halts, and you can safely power down the server.
Step 12 When the Apply Patch window displays, choose No. Step 13 The Windows Upgrade window displays. Step 14 Choose No and continue with the Basic software installation.
Basic software installation
Procedure
Step 1 When the Timezone Configuration displays, choose the appropriate time zone for the server and then choose OK. The Auto Negotiation Configuration window displays.
Step 2 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 MTU Configuration window displays.
Note To use this option, your hub or Ethernet switch must support automatic negotiation.
- To disable automatic negotiation, choose No and continue with the next step. The NIC Speed and Duplex Configuration window displays.
Step 3 If you chose to disable automatic negotiation, manually choose the appropriate NIC speed and duplex settings now and choose OK to continue. The MTU Configuration window displays.
Step 4 In the MTU Configuration window, you can change the MTU size from the operating system default. The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network. If you are unsure of the MTU setting for your network, use the default value, which is 1500 bytes.
Caution If you configure the MTU size incorrectly, your network performance can be affected.
- To accept the default value (1500 bytes), choose No.
- To change the MTU size from the operating system default, choose Yes, enter the new MTU size, and choose OK.
The DHCP Configuration window displays.
Step 5 For network configuration, you can choose to either set up a static network IP address for the node or to use Dynamic Host Configuration Protocol (DHCP). Static IP addresses are recommended. If you use DHCP, use static DHCP Step 6 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Node Server Installation Information for field descriptions. The DNS Client Configuration window displays.
Step 7 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Node Server Installation Information for field descriptions. The network restarts by using the new configuration information, and the Administrator Login Configuration window displays.
Step 8 Enter your Administrator login and password from Node Server Installation Information.
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 Information window displays.
Step 9 Enter your certificate signing request information and choose OK. The First Node Configuration window displays.
Step 10 You can configure this server as either the first node in a Cisco Unified Communications Manager cluster or as a subsequent node.
- To configure this server as the first Cisco Unified Communications Manager node, choose Yes and continue with the Set up first node.
- To configure this server as a subsequent node in the cluster, choose No and continue with the Set up subsequent node.
Step 11 Continue with the Set up first node.
Set up first node
ProcedureAfter you finish the basic installation, follow this procedure to configure the server as the first node in the cluster.
Step 1 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 5 or higher (meaning stratums 1-9). Subsequent nodes in the cluster will get their time from the first node.
Note When you are installing Cisco Unity Connection on a virtual machine, you must specify an external NTP server. Step 2 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 3 Enter the Security password from Node Server Installation Information.
Note The 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 4 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.
Step 5 Choose OK. The Application User Configuration window displays. Step 6 Enter the Application User name and password from Node Server Installation Information and confirm the password by entering it again. Step 7 Choose OK. The Platform Configuration Confirmation window displays. Step 8 To continue with the installation, choose OK; or to modify the platform configuration, choose Back. The system installs and configures the software. The DVD drive ejects, and the server reboots. Do not reinsert the DVD.
When the installation process completes, you get prompted to log in by using the Administrator account and password.
What to Do NextComplete the post-installation tasks that are listed in the Post-installation tasks.
Set up subsequent node
ProcedureTo configure a subsequent node in the cluster, follow these steps.
Caution
You must configure a subsequent node on the first node by using Cisco Unified Communications Manager Administration before you install the subsequent node. For more information, see the Cisco Unified Communications Manager Administration Guide.
Step 1 If you configured Network Time Protocol on the first node, ensure that it is synchronized with an NTP server before you install a subsequent node. From the Command Line Interface on the first node, enter utils ntp status. Ensure that the output indicates that the node is synchronized with an NTP server.
Note If the first node is not synchronized with an NTP server, installation of the subsequent node will fail.
Step 2 On the First Node Configuration window, read the Warning and make sure you have correctly configured the first node. To continue with the installation of the subsequent node, click OK. The Network Connectivity Test Configuration window displays.
Step 3 During installation of a subsequent node, the system checks to ensure that the subsequent node can connect to the first node.
- To pause the installation after the system successfully verifies network connectivity, choose Yes.
- To continue the installation with a pause, choose No.
The First Node Access Configuration window displays.
Step 4 Enter the first node connectivity information and choose OK. The system checks for network connectivity.
If you chose to pause the system after the system successfully verifies network connectivity, the Successful Connection to First Node window displays. Choose Continue.
Note If the network connectivity test fails, the system always stops and allows you to go back and reenter the parameter information.
The SMTP Host Configuration window displays.
Step 5 If you want to configure an SMTP server, choose Yes and enter the SMTP server name.
Note To use certain operating system features, you must configure an SMTP server; however, you can also configure an SMTP server later by using the operating system GUI or the command line interface.
The Platform Configuration Confirmation window displays.
Step 6 To start installing the software, choose OK, or, if you want to change the configuration, choose Back. Step 7 When the installation process completes, you get prompted to log in by using the Administrator account and password.
What to Do NextProceed to complete the post-installation tasks.
Related References
Post-installation tasks
After installing the Cisco Unified Communications Manager on your server, you must set some configuration parameters 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 the following table.
Table 5 Post-Installation Tasks Post-Installation Tasks
Important Notes
Log in as the Cisco Unified Communications Manager Application User and change the Application User passwords.
You can use Real Time Monitoring Tool to monitor system health, and view and collect logs.
For installation instructions and more information about Real Time Monitoring Tool, see the Cisco Unified Real Time Monitoring Tool Administration Guide.
Configure the netdump utility, if you installed a cluster of servers.
The netdump utility allows you to send data and memory crash dump logs from one server on the network to another.
For instructions for configuring the netdump utility, refer to the Troubleshooting Guide
Upload your Cisco Unified Communications Manager license files to the first node.
See the Install licenses.
Activate Cisco Unified Communications Manager feature services that you want to run.
Before you activate feature services, you must perform required preactivation tasks. For service activation requirements, refer to the Cisco Unified Serviceability Administration Guide.
Refer to Cisco Unified Serviceability Administration Guide.
See the Cisco Unified Serviceability.
Configure the backup settings.
Remember to back up your data daily.
The locale English_United_States installs automatically on the server; however, you can add new locales to the server, if required.
Perform this task only after you have completed the installation for the entire cluster, and set up the database.
Refer to Cisco Unified Communications Operating System Administration Guide.
Install COP enabler files for any custom device types that you want to use that do not ship with Cisco Unified Communications Manager. Perform this task only after you have completed the installation for the entire cluster, and set up the database.
If applicable, configure any network management systems in use at your site.
Refer to the Cisco Unified Serviceability Administration Guide.
If you want to set up a secure cluster, you can run your Cisco IP Telephony network in mixed mode.
For more information, see the Cisco Unified Communications Manager Security Guide.
Configure the system.
See theSet up database.
For more information, refer to the Cisco Unified Communications Manager System Guide.
Install Cisco Unified Communications Manager IM and Presence Service.
- Change default application user passwords
- Cisco Unified Serviceability
- Services activation
- Install licenses
- Apply security
- Set up database
- Log files
Change default application user passwords
The 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 Communications Manager Administration and change these passwords. Refer to Cisco Unified Communications Manager Administration Guide for the procedure for changing a password.
Cisco Unified Serviceability
To access Cisco Unified Communications Manager Administration or Cisco Unified Serviceability , you will need to use a web browser from a PC with network access to the Cisco Unified Communications Manager server.
Even though all 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 Serviceability . For service recommendations and more information, refer to Cisco Unified Serviceability Administration Guide .
Apply security
ProcedureUse the following procedure to apply security to a new node in a secure cluster after you have successfully added the node. For more information on adding a new node to a cluster, see the Install a new node in an existing cluster.
Note
For more information, refer to the Cisco Unified Communications Manager Security Guide.
Step 1 Activate the Cisco CTL Provider service on the new node. Step 2 Use an etoken from the existing CTL file and run the CTL client again to get the certificates from all the servers in the cluster, including the new server, into the CTL file. You must be running the Cisco CTL Provider on all servers in the cluster to generate the certificates and update the CTL file. Step 3 Restart the Cisco TFTP service on all TFTP servers. Step 4 Restart the Cisco CallManager service on all the nodes. Step 5 Reset all devices to distribute the new CTL file to the devices.
Set up database
After installing Cisco Unified Communications Manager, you use Cisco Unified Communications Manager Administration to begin configuring the database. The Cisco Unified Communications Manager 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 Communications Manager Administration or Cisco Unified Serviceability:
- In Cisco Unified Serviceability, activate the services that you want to run on each server in the cluster.
- Configure system-level settings, such as Cisco Unified Communications Manager Groups.
- Design and configure your dialing plan.
- Configure media resources for conferences, music on hold, and so on.
- Configure systemwide features, Cisco Unified IP Phone services, Cisco Unified Communications Manager Extension Mobility, Cisco Unified Communications Manager Attendant Console, and Cisco Unified Communications Manager Assistant.
- Install and configure the gateways.
- Enable computer telephony integration (CTI) application support; then, install and configure the desired CTI applications.
- Configure the users.
- Configure and install the phones; then, associate users with the phones.
For more information about configuring the Cisco Unified Communications Manager database, refer to the Cisco Unified Communications Manager Administration Guide, the Cisco Unified Communications Manager System Guide, or online help in the Cisco Unified Communications Manager application.
Log files
If you encounter problems with the installation, you may be able to 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
Command Syntax
file list install *To view the log file from the command line, enter
file view install log_filewhere log_file is the log file name.
You can also view logs by using the Real Time Monitoring Tool. For more information on using and installing the Real Time Monitoring Tool, refer to theCisco Unified Real Time Monitoring Tool Administration Guide.
COP files, dial plans, and locales
COP file installation
The following guidelines apply to installing COP files. If the documentation for a specific COP file contradicts these general guidelines, follow the COP file documentation:
- Install the COP file on every server in a cluster. Perform this task after you have installed Cisco Unified Communications Manager on ever server in the cluster and set up the database.
- After you install a COP file, you must restart the server.
NoteYou must restart Cisco Unified Communications Manager to ensure that configuration changes that are made during the COP file installation get written into the database. Cisco recommends that you perform this restart during an off-peak period.
Dial plan installation
You can install dial plan files from either a local or a remote source by using the same process for installing software upgrades. See the Upgrade Guide for Cisco Unified Communications Manager for more information about upgrading from a local or remote source.
After you install the dial plan files on the system, log in to Cisco Unified Communications Manager Administration and then navigate to to complete installing the dial plans.
Locale installation
Cisco provides locale-specific versions of the Cisco Unified Communications Manager Locale Installer on www.cisco.com. Installed by the system administrator, the locale installer allows the user to view/receive the chosen translated text or tones, if applicable, when a user works with supported interfaces.
TipSince the primary language spoken in Belgium is Dutch, you can download the Dutch (Netherlands) locale file, for example, cm-locale-nl_NL- 8.5.1.2100-1.cop.sgn (Cisco Unified Communications Locale Installer 8.5.1.21000-1 Dutch (Netherlands)). Secondary languages commonly spoken in Belgium are French and German.
User Locales
User locale files provide translated text and voice prompts, if available, for phone displays, user applications, and user web pages in the locale that the user chooses. User-only locale installers exist on the web.
Network Locales
Network locale files provide country-specific phone tones and gateway tones, if available. Network-only locale installers exist on the web.
Cisco may combine multiple network locales in a single locale installer.
Note
The Cisco Media Convergence Server (MCS) or Cisco-approved, customer-provided server can support multiple locales. Installing multiple locale installers ensures that the user can choose from a multitude of locales.
Changes do not take effect until you reboot every server in the cluster. Cisco strongly recommends that you do not reboot the servers until you have installed all locales on all servers in the cluster. Minimize call-processing interruptions by rebooting the servers after regular business hours.
Install locales
Install locales after you have installed Cisco Unified Communications Manager on every server in the cluster and have set up the database.
You can install locale files from either a local or a remote source by using the same process for installing software upgrades. See the Upgrade Guide for Cisco Unified Communications Manager for more information about upgrading from a local or remote source.
Note
To activate the newly installed locales, you must restart the server. You can install more than one locale before you restart the server.
Related References
Locale files
When you are installing Cisco Unified Communications Manager locales, you must install the following files:
- User Locale files - Contain language information for a specific language and country and use the following convention: cm-locale-language-country-version.cop
- Combined Network Locale file - Contains country-specific files for all countries for various network items, including phone tones, annunciators, and gateway tones. The combined network locale file uses the following naming convention: cm-locale-combinednetworklocale-version.cop
Error messages
See the following table for a description of the messages that can occur during Locale Installer activation. If an error occurs, you can view the messages in the installation log.
Table 6 Locale installer error messages and descriptions [LOCALE] File not found: <language>_<country>_user_locale.csv, the user locale has not been added to the database.
This error occurs when the system cannot locate the CSV file, which contains user locale information to add to the database. This indicates an error with the build process.
[LOCALE] File not found: <country>_network_locale.csv, the network locale has not been added to the database.
This error occurs when the system cannot locate the CSV file, which contains network locale information to add to the database This indicates an error with the build process.
[LOCALE] Communications Manager CSV file installer installdb is not present or not executable
This error occurs because a Cisco Unified Communications Manager application called installdb must be present; it reads information that is contained in a CSV file and applies it correctly to the Cisco Unified Communications Manager database. If this application is not found, it either was not installed with Cisco Unified Communications Manager (very unlikely), has been deleted (more likely), or the server does not have Cisco Unified Communications Manager installed (most likely). Installation of the locale will terminate because locales will not work without the correct records that are held in the database.
[LOCALE] Could not create /usr/local/cm/application_locale
/cmservices/ipma/com/cisco/ipma
/client/locales/maDialogs_<ll>_<CC>.properties.Checksum.[LOCALE] Could not create /usr/local/cm/application_locale/cmservices/ipma/com/cisco/ ipma/client/locales/maMessages_<ll>_<CC>.properties.Checksum.
[LOCALE] Could not create /usr/local/cm/ application_locale/cmservices/ipma/com/cisco/ ipma/client/locales/maGlobalUI_<ll>_<CC>.properties.Checksum.
[LOCALE] Could not create /usr/local/cm/ application_locale/cmservices/ipma/ LocaleMasterVersion.txt.Checksum.
These errors could occur when the system fails to create a checksum file; causes can include an absent Java executable, /usr/local/thirdparty/java/j2sdk/ jre/bin/java, an absent or damaged Java archive file, /usr/local/cm/jar/cmutil.jar, or an absent or damaged Java class, com.cisco.ccm.util.Zipper. Even if these errors occur, the locale will continue to work correctly, with the exception of Cisco Unified Communications Manager Assistant, which cannot detect a change in localized Cisco Unified Communications Manager Assistant files.
[LOCALE] Could not find /usr/local/cm/application_locale/cmservices/ipma/LocaleMaster Version.txt in order to update Unified CM Assistant locale information.
This error occurs when the file does not get found in the correct location, which is most likely due to an error in the build process.
[LOCALE] Addition of <RPM-file-name> to the Cisco Unified Communications Manager database has failed!
This error occurs because of the collective result of any failure that occurs when a locale is being installed; it indicates a terminal condition.
