Cisco Unified Communications Operating System Administration Guide for Cisco Unified Presence Release 6.0(1)
Software Upgrades
Downloads: This chapterpdf (PDF - 407.0KB) The complete bookPDF (PDF - 2.49MB) | Feedback

Software Upgrades

Table Of Contents

Software Upgrades

Software Upgrade and Installation

Upgrade Considerations

From Local Source

From Remote Source

Locale Installation

Installing Locales

Locale Files

Error Messages

Managing TFTP Server Files


Software Upgrades


You can use the Software Upgrades options to perform the following types of installations and upgrades:

Install/Upgrade—Use this option to upgrade the application software, install Cisco Unified Communications Manager Locale Installers and dial plans, and upload and install device packs, phone firmware loads, and other COP files.

TFTP File Management—Use this option to upload various device files for use by the phones to the TFTP server. The TFTP server files that you can upload include custom phone rings, callback tones, and phone backgrounds.

Software Upgrade and Installation

The Software Upgrade windows enable you to upgrade the Cisco Unified Communications Operating System software from either a local or a remote source.

The software upgrade process also enables you to back out of an upgrade if problems occur. You install the software for the upgrade on the inactive partition of the system and perform a restart to switch the system to the newer version of the software. During this process, the upgraded software becomes the active partition, and your current software becomes the inactive partition. Your configuration information migrates automatically to the upgraded version in the active partition.

If for any reason you decide to back out of the upgrade, you can restart the system to the inactive partition that contains the older version of the software. However, any configuration changes that you made after upgrading the software will be lost.

CAPF uses the Certificate Manager Infrastructure to manage its certificates and keys. Because of this, CAPF keys and certificates automatically regenerate. You must then rerun the CTL Client application to upgrade the CTL file.


Note If you have a two-node cluster, where Node A is the publisher server and Node B is the subscriber server, you must upgrade node A prior to upgrading node B. The system transfers specific files and a copy of the database from Node A to Node B during an upgrade. Also, you cannot perform a fresh installation on Node A and then perform an upgrade on Node B.


Upgrade Considerations


Tip Tip For detailed information about migrating to Cisco Unified Presence 6.0(1), as well as other required configuration procedures, refer to the Cisco Unified Presence Deployment Guide.


When you are upgrading to Cisco Unified Presence 6.0(1), be aware of the following considerations:

If you are upgrading your associated Cisco Unified Communications Manager from Release 5.x to Release 6.0(1), you must upgrade to Cisco Unified Presence 6.0(1) first. You cannot synchronize Cisco Unified Communications Manager 6.0(1) with an earlier release of Cisco Unified Presence.

If you have a Cisco Unified Presence cluster, you must upgrade all nodes in the cluster.

After upgrading Cisco Unified Communications Manager to Release 6.0(1), you must stop and restart and the Cisco Unified Presence Sync Agent service. To restart the Sync Agent service, navigate to Cisco Unified Serviceability and choose Tools > Control Center - Network Services.

After upgrading Cisco Unified Communications Manager to Release 6.0(1), you must configure a SIP PUBLISH trunk on Cisco Unified Communications Manager to communicate with Cisco Unified Presence. For more information, refer to the Cisco Unified Communications Manager System Guide.

You must also enable the SIP trunk on the Cisco Unified Presence Settings window. For more information, refer to the Cisco Unified Presence Administration Guide.

After upgrading to Cisco Unified Presence Release 6.0(1), you must map line appearances to users to support presence. In Cisco Unified Presence 6.0(1), the system does not base presence on a line appearance mapping to the primary extension of a user.

For additional upgrade considerations, refer to the Cisco Unified Presence Deployment Guide.

From Local Source

You can install software from a CD or DVD that is located in the local disc drive and then start the upgrade process.


Note Be sure to back up your system data before starting the software upgrade process. For more information, see the Disaster Recovery System Administration Guide for Cisco Unified Presence.


To install or upgrade software from a CD or DVD, follow this procedure:

Procedure


Step 1 If you plan to download the upgrade file, create a CD or DVD by doing the following steps:

a. Download the appropriate upgrade file from Cisco.com.


Note Do not unzip or untar the file. If you do, the system may not be able to read the upgrade files.


b. Copy the upgrade file to a writeble CD or DVD.

Step 2 Insert the CD or DVD into the disc drive on the local server that is to be upgraded.


Note Because of their size, some upgrade files may not fit on a CD and will require a DVD.


Step 3 Navigate to Software Upgrades > Install/Upgrade.

The Software Installation/Upgrade window displays.

Step 4 From the Source list, choose DVD/CD.

Step 5 In the Directory field, enter the path to the patch file on the CD or DVD.

If the file is in the root directory, enter a slash (/).

Step 6 To continue the upgrade process, click Next.

Step 7 Choose the upgrade version that you want to install and click Next.

Step 8 In the next window, monitor the progress of the download, which includes the filename and the number of megabytes that are getting transferred.

Step 9 When the download completes, verify the checksum value against the checksum for the file that you downloaded that is shown on Cisco.com.


Caution The two checksum values must match to ensure the authenticity and integrity of the upgrade file. If the checksum values do not match, download a fresh version of the file from Cisco.com and try the upgrade again.

Step 10 Choose whether you want the system to automatically reboot to the upgraded partition after installing the upgrade software:

To install the upgrade and automatically reboot to the upgraded partition, choose Reboot to upgraded partition.

To install the upgrade and then manually reboot to the upgraded partition at a later time, choose Do not reboot after upgrade.

Step 11 Click Next.

The Upgrade Status windows displays and displays the Upgrade log.

Step 12 When the installation completes, click Finish.

Step 13 To restart the system and activate the upgrade, choose Settings > Versions; then, click Restart.

The system restarts and runs the upgraded software.


From Remote Source

To install software from a network drive or remote server, use the following procedure.


Note Be sure to back up your system data before starting the software upgrade process. For more information, see the Disaster Recovery System Administration Guide for Cisco Unified Presence.


Procedure


Step 1 Navigate to Software Upgrades > Install/Upgrade.

The Software Installation/Upgrade window displays.

Step 2 From the Source list, choose Remote Filesystem.

Step 3 In the Directory field, enter the path to the patch file on the remote system.

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 that you want to specify. 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.

Step 4 In the Server field, enter the server name.

Step 5 In the User Name field, enter your user name.

Step 6 In the User Password field, enter your password.

Step 7 from the Transfer Protocol field, select the transfer protocol.

Step 8 To continue the upgrade process, click Next.

Step 9 Choose the upgrade version that you want to install and click Next.

Step 10 In the next window, monitor the progress of the download, which includes the filename and the number of megabytes that are getting transferred.

Step 11 When the download completes, verify the checksum value against the checksum for the file that you downloaded that is shown on Cisco.com.


Caution To ensure the authenticity and integrity of the upgrade file, the two checksum values must match. If the checksum values do not match, download a fresh version of the file from Cisco.com and try the upgrade again.

Step 12 Choose whether you want the system to automatically reboot to the upgraded partition after the upgrade software is installed:

To install the upgrade and automatically reboot to the upgraded partition, choose Reboot to upgraded partition.

To install the upgrade and then manually reboot to the upgraded partition at a later time, choose Do not reboot after upgrade.

Step 13 Click Next.

The Upgrade Status windows displays and displays the Upgrade log.

Step 14 When the installation completes, click Finish.

Step 15 To restart the system and activate the upgrade, choose Settings > Versions; then, click Restart.

The system restarts and runs the upgraded software.


Note After upgrading from Cisco Unified Presence Release 1.0(2) to Release 1.0(3), ensure that LDAP search works in Cisco Unified Personal Communicator. If LDAP search does not work, delete the Cisco Unified Personal Communicator LDAP Profile in Cisco Unified Presence Administration and then re-create it. For more information, see the LDAP Profile chapter in the Cisco Unified Presence Administration Guide.


Locale Installation

Cisco provides locale-specific versions of the Cisco Unified Communications 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.

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.


Installing Locales

You can install locale files from either a local or a remote source by using the same process that is described earlier in this chapter for installing software upgrades. See Software Upgrade and Installation for more information about this process.


Note To activate the newly installed locales, you must restart the server.


See Locale Files for information on the locale files that you must install. You can install more than one locale before you restart the server.

Locale Files

When installing locales, you must install both of 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 Table 7-1 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 7-1 Locale Installer Messages and Descriptions 

Message
Description

[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, which 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] CSV file installer installdb is not present or not executable

You must ensure that an application called installdb is present. It reads information that a CSV file contains and applies it correctly to the target database. If this application is not found, it did not get installed with the Cisco Unified Communications application (very unlikely), has been deleted (more likely), or the server does not have a Cisco Unified Communications application, such as Cisco Unified Communications Manager or Cisco Unified Presence, installed (most likely). Installation of the locale will terminate because locales will not work without the correct records 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, which 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, causes. 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/LocaleMasterVersion.txt in order to update Unified Unified CM Assistant locale information.

This error occurs when the system does not find the file in the correct location, which is most likely due to an error in the build process.

[LOCALE] Addition of <locale-installer-file-name> to the database has failed!

This error occurs because the collective result of any failure that occurs when a locale is being installed causes it; it indicates a terminal condition.

[LOCALE] Could not locate <locale-installer-file-name>

The system will not migrate this locale during an upgrade!

The downloaded locale installer file no longer resides in the download location. The platform may have moved or deleted it. This is noncritical error indicates that after the Cisco Unified Communications application has been upgraded, you need to either reapply the locale installer or download and apply a new locale installer.

[LOCALE] Could not copy <locale-installer-file-name> to migratory path. This locale will not be migrated during an upgrade!

You cannot copy the downloaded locale installer file to the migration path. This is noncritical error indicates that after the Cisco Unified Communications application has been upgraded, you need to either reapply the locale installer or download and apply a new locale installer.

[LOCALE] DRS registration failed

The locale installer could not register with the Disaster Recovery System. A backup or restore record will not include the locale installer. Record the installation log and contact Cisco TAC.

[LOCALE] DRS unregistration failed

The locale installer could not deregister from the Disaster Recovery System. A backup or restore record will not include the locale installer. Record the installation log and contact Cisco TAC.

[LOCALE] Backup failed!

The Disaster Recovery System could not create a tarball from the downloaded locale installer files. Reapplication of the locale installer before attempting a backup should succeed.


Note Manually reinstalling locales after a system restore achieves the same goal.


[LOCALE] No COP files found in restored tarball!

Corruption of backup files may prevent successful extraction of locale installer files.

Note Manual reapplication of the locale installer will restore the locale fully.

[LOCALE] Failed to successfully reinstall COP files!

Corruption of backup files may damage locale installer files.

Note Manual reapplication of the locale installer will restore the locale fully.

[LOCALE] Failed to build script to reinstall COP files!

The platform could not dynamically create the script used to reinstall locales.

Note Manual reapplication of the locale installer will restore the locale fully. Record the installation log and contact TAC.


Managing TFTP Server Files

You can upload files to the TFTP server for the phones to use. Files that you can upload include custom phone rings, callback tones, and backgrounds. This option uploads files only to the specific server to which you connected, and other nodes in the cluster do not get upgraded.

Files upload into the TFTP directory by default. You can also upload files to a subdirectory of the TFTP directory.

If you have two Cisco TFTP servers that are configured in the cluster, you must perform the following procedure on both servers. This process does not distribute files to all servers, nor to both of the Cisco TFTP servers in a cluster.

To upload and delete TFTP server files, follow this procedure:

Procedure


Step 1 From the Cisco Unified Communications Operating System Administration window, navigate to Software Upgrades > TFTP File Management.

The TFTP File Management window displays and shows a listing of the current uploaded files. You can filter the file list by using the Find controls.

Step 2 To upload a file, follow this procedure:

a. Click Upload File.

The Upload File dialog box opens.

b. To upload a file, click Browse and then choose the file that you want to upload.

c. To upload the file to a subdirectory of the TFTP directory, enter the subdirectory in the Directory field.

d. To start the upload, click Upload File.

The Status area indicates when the file uploads successfully.

e. After the file uploads, restart the Cisco TFTP service.


Note If you plan to upload several files, restart the Cisco TFTP service only once, after you have uploaded all the files.


For information about restarting services, refer to the Cisco Unified Presence Serviceability Administration Guide.

Step 3 To delete files, follow this procedure:

a. Check the check boxes next to the files to delete.

You can also click Select All to select all the files or Clear All to clear all selections.

b. Click Delete Selected.



Note If you want to modify a file that is already in the TFTP directory, you can use the CLI command file list tftp to see the files in the TFTP directory and file get tftp to get a copy of a file in the TFTP directory. For more information, see Appendix A "Command Line Interface."