Cisco Unified Communications Operating System Administration Guide for Cisco Unified CCX and Cisco Unified IP IVR, Release 9.0(1)
Software upgrades
Download the complete book
Cisco Unified Communications Operating System Administration Guide for Cisco Unified CCX and Cisco Unified IP IVR, Release 9.0(1)Cisco Unified Communications Operating System Administration Guide for Cisco Unified CCX and Cisco Unified IP IVR, Release 9.0(1) (PDF - 1 MB)
 Feedback

Software upgrades

You can use the Install/Upgrade option to upgrade the Unified CCX software and install Unified CCX COP patch files.


Note

For more information regarding the supported versions of Unified CCX and Unified CM, see Cisco Unified Contact Center Express (Unified CCX) Software and Hardware Compatibility Guide.


Caution

When you upgrade from Unified CCX 8.x to 9.0(1) the system reboots as part of the upgrade process. Therefore, you may want to perform the upgrade during maintenance window to avoid service interruptions.

Pre-upgrade tasks

Before you begin the upgrade, perform the following tasks:

  • Read the release notes for the new release and be sure that you understand the new features, Cisco Option Package (COP) files, and how the upgrade interacts with the other products that are associated with your system, such as Java Telephony Application Programming Interface (JTAPI), Real Time Monitoring Tool (RTMT), and firewalls.
  • Ensure that you have the necessary license files for the new release. For more information on obtaining and installing licenses for Unified CCX 9.0(1), see the Cisco Unified Contact Center Express Installation Guide 9.0(1).
  • Before you begin the upgrade, back up your system. For more information, see the Disaster Recovery System Administration Guide.
  • Before you upgrade to a later release, refer to the documentation for your currently installed COP files to identify any special considerations related to upgrading Unified CCX.
  • Before you begin the upgrade, ensure that you are using the supported MCS server. For more information on the supported hardware for release 9.0(1), see the Cisco Unified Contact Center Express Software and Hardware Compatibility Guide.

Software upgrade considerations

Software upgrade overview

Unified CCX 9.0(1) software upgrade process consists of successful installation of the upgrade software to the inactive partition followed by the switch version process.


Caution

When you install upgrade software, there is a server outage. Once you kick off the upgrade using either the command line or graphical user interface, the system is automatically rebooted and the server outage(incase of refresh upgrade) begins. The system reboots multiple times during the upgrade process. The duration of this outage depends on the deployment and the amount of data.

When you install upgrade software, you install the software on the inactive partition. The system continues to function normally while you are installing the software, but there will be a temporary server outage while the Cisco Unified Contact Center Express software is being installed. When you are ready, you activate the inactive partition and reboot the system with the new upgrade software by running the switch version process. The current active partition is identified as the inactive partition when the system restarts. The current software remains in the inactive partition until the next upgrade. 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 since you upgraded the software is lost.

You can only make changes to the database on the active partition. The database on the inactive partition does not get updated. If you make changes to the database after an upgrade, you must repeat those changes after switching back the partition to the older version.

You can install an upgrade version from a DVD (local source) or from a network location (remote source) that the server can access. While upgrading the software in a single node deployment of Unified CCX, upgrade the publisher node1. After the upgrade is complete, initiate switch version on the publisher node. Ensure that the publisher comes up successfully after the switch version and shows appropriate active and inactive versions.


Caution

In a High Availability (HA) deployment of Unified CCX, upgrade both the nodes with first publisher then subscriber. After the upgrade is complete on both nodes, initiate the switch version on the publisher and after the publisher comes up successfully, initiate the switch version on the subscriber. Ensure both the publisher and subscriber come up successfully after the switch version and that they show appropriate active and inactive versions.

Data migration occurs only when a switch version is done from a lower to the higher version; when the switch version is done from a higher to a lower version the data migration does not happen.


Note

Unified CCX Real-Time Monitoring Tool, Unified CCX Editor, and Cisco Historical Reporting Client do not support automatic true upgrade process. You have to manually uninstall the existing version and then download and install the relevant one from the current active version.


Warning

In a High Availability (HA) deployment of Unified CCX, switch version of both publisher and subscriber cannot be done at the same time. In other words, you can switch version on the subscriber only after completing the switch version on the publisher.


Caution

If you upgrade the Operating System on the subscriber after completing switch version on publisher, there might be some data discrepancy (see Perform upgrade tasks) or the upgrade might fail.


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.


Caution

Switch version process must be initiated only from OS Administration application or from Command Line Interface (CLI). Initiating switch version process from recovery CD is not supported.

Configuration restrictions during upgrade

The administrator must not make any configuration changes to Unified CCX during an upgrade. Configuration changes include any changes that you make in Unified CCX Administration, Unified CCX Serviceability, and the User Option windows.

Any configuration changes that you make during an upgrade are lost after the upgrade completes, and some configuration changes can cause the upgrade to fail.

If you are upgrading your system, you must complete the upgrade tasks in Perform upgrade tasks before you perform any configuration tasks.


Caution

If you fail to follow these recommendations, unexpected behavior may occur; for example, ports may not initialize as expected.

Perform upgrade tasks

To successfully complete the upgrade, perform the upgrade tasks in the following order:


Note
Cisco strongly recommends that you do not perform configuration tasks until:
  • the upgrade is completed on all Unified CCX server(s) in the cluster,
  • you have switched the servers over to the upgraded partition, and
  • you have verified that database replication is functioning.
Procedure
    Step 1   Stop all configuration tasks; that is, do not perform configuration tasks in the various Unified CCX-related GUIs or the CLI (with the exception of performing the upgrade in the Cisco Unified Operating System GUI).
    Step 2   Upgrade the first node in the cluster (the publisher node).
    Step 3   Upgrade the subsequent node in the cluster (the subscriber node).
    Step 4   Ensure that you have completed the following:
    1. Switch over the first node to the upgraded partition.
    2. Switch over subsequent node to the upgraded partition.
    3. Ensure that database replication of the Unified CCX is functioning between the first node and the subsequent node using the CLI command - utils dbreplication status. If you are upgrading Unified CCX in a two-node (high availability) deployment, once you complete the switch version of second node, execute the following CLI command utils dbreplication repair all to remove any data discrepancy between the two nodes.
    Note   

    The Unified CCX historical reporting client always connects to the non-engine master node to gather reporting information. Hence the historical reports might not present all the information that was gathered in the engine-master until both the nodes are switched to the latest version and database replication is setup. Database replication is set only if both the nodes are in the same version.

    Step 5   When all other upgrade tasks are complete, you can perform the desired configuration tasks as required.
    Note   

    In a single-node deployment of Unified CCX, you can skip steps 3, 4, and 5 and continue to perform switch over for the publisher node.

    Types of upgrades

    Two types of upgrade are available:

    • Standard upgrades—Upgrades that do not reboot the server during the course of upgrade activity. All upgrades to Special Update/Engineering Special (SU/ES) invoke standard upgrade.
    • Refresh upgrades—Upgrades that require multiple reboots during the installation of upgrade software. Upgrades from Unified CCX 8.x to 9.0(1) invoke refresh upgrade.

    The server automatically determines whether you need to perform a standard upgrade or a refresh upgrade.

    Standard upgrades

    For standard upgrades, when you install upgrade software, you install the software as an inactive version. The system continues to function normally while you are installing the software. When the upgrade is complete, you activate the inactive partition and reboot the system with the new upgrade software by running the switch version process. When you reboot to the new software, the old software version remains on the system. This allows you to switch back to the old version in the unlikely event of issues with the new software.

    Refresh upgrades


    Note

    You must perform all refresh upgrades during a maintenance window, because the system will not be available during the upgrade.

    For refresh upgrades, the system automatically performs multiple reboots during installation of upgrade software. After upgrade is complete, the system boots back to the older version automatically. You can manually switch to the higher version at a later time.

    If for any reason you decide to revert to the earlier software version, you can switch version to the older version of the software. This switch version requires a reboot. Be aware that any configuration changes that you made after upgrading the software will be lost.

    Refresh upgrade overview

    If required, the server automatically determines whether you need to perform a standard upgrade or a refresh upgrade. A refresh upgrade is required when upgrading to Unified CCX 9.0(1) from a release earlier than 9.0(1). You can initiate standard and refresh upgrades in the same way using the Command Line Interface or the Unified CCX GUI.

    A refresh upgrade has the following differences from a standard upgrade:

    • Multiple reboots as part of the upgrade
    • After the upgrade starts, the console displays status information similar to that of a fresh installation
    • COP file installation is required for upgrades from Releases 8.0(1) to 8.5(1)
    • E-mail notification is sent upon successful completion of the upgrade

    Tip

    Several reboots occur during a refresh upgrade; therefore, you must perform a refresh upgrade during a maintenance window.

    You can install a Cop file only on Unified CCX Versions 8.0.2 SU4 (8.0.2.11005-20) or 8.5.1 SU3 (8.5.1.11003-32), which means that you can perform a refresh upgrade to 9.0(1) only from these versions. If you run a version older than these, you must perform an L2 upgrade to these versions before trying the refresh upgrade to 9.0(1).

    If you are performing a refresh upgrade on HA, follow these mandatory steps:

    1. Install Cop file on first node (Publisher)
    2. Install Cop File on second node (Subscriber)
    3. Complete refresh upgrade on node 1.
    4. Complete refresh upgrade on node 2.
    5. Run switch version to switch to 9.0(1) on node 1.
    6. Run switch version to switch to 9.0(1) on node 2.

    Note

    After you apply the Cop file you must reboot the node.

    Obtain upgrade file

    Before you begin the upgrade process, you must obtain the appropriate upgrade file from Cisco.com. You can access the upgrade file during the installation process from either a local DVD or from a remote FTP or SFTP server. Be aware that directory names and filenames that you enter to access the upgrade file are case-sensitive.

    Supported SFTP servers

    Cisco allows you to use any Secure File Transfer Protocol (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 versions of Unified CCX. For information on which vendors have certified their products with your version of Unified CCX, see the following URL:

    http://www.cisco.com/pcgi-bin/ctdp/Search.pl

    For information on using GlobalSCAPE with supported Cisco Unified Communications versions, see the following URL:

    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:


    Note

    For issues with third-party products that have not been certified through the CTDP process, contact the third-party vendor for support.

    Unified CCX server upgrade procedures

    This section is applicable for both single-node and HA deployments of Unified CCX with Unified CM deployment. This section provides procedures for upgrading Unified CCX server(s) from either a local or a remote source and contains the following subsections:

    If you are upgrading to Unified CCX 9.0(1), once you complete the Software Upgrade, you need to add a new license through the System > License Information > Add License(s) menu option from the Unified CCX Application Administration menu bar. See Cisco Unified CCX Administration Guide, Release 9.0(1) for detailed information on how to upload Unified CCX licenses.

    Upgrade with DVD

    To upgrade the software from local DVD, follow this procedure:


    Note

    If you do not have a Cisco-provided upgrade disk, create an upgrade disk by burning the upgrade file that you downloaded onto a DVD as an ISO image. Copying the .iso file to the DVD does not work. Most commercial disk burning applications can create ISO image disks.

    Procedure
      Step 1   Insert the new DVD into the disc drive on the local server that is to be upgraded.
      Step 2   Log in to Cisco Unified Communications Operating System Administration using platform credentials.
      Step 3   Navigate to Software Upgrades > Install/Upgrade. The Software Installation/Upgrade window appears.
      Step 4   From the Source list, choose DVD/CD.
      Step 5   Enter a slash (/) in the Directory field.
      Step 6   To continue the upgrade process, click Next. Within a few minutes, you can see the list of Options/Upgrades available along with a list of invalid upgrades, if any.
      Step 7   Choose the upgrade version that you want to install and click Next.

      The software downloads the iso image.

      Step 8   Enter your Email Destination and SMTP Server in the fields provided, to use the Email Notification feature.
      Step 9   Click Next to start the upgrade process.
      Step 10   Once the installation is completed successfully, remove the DVD from the disk drive.
      Note   

      If you want to initiate an upgrade through CLI, see Command Line Interface Reference Guide for Cisco Unified Contact Center Express and Cisco Unified IP IVR.

      If you have installed Unified CCX on HA deployment, perform Switch version only after successfully completing upgrade on the second node.

      Step 11   To restart the system and activate the upgrade, choose Settings > Version from the Cisco Unified Communications Operating System Administration web interface and click Switch Versions. A dialog box with the following message appears. Click OK to initiate the switch version process.

      A switch version request has been submitted. This can take a long time depending on the platform and database size. Continue to monitor the switch over process from the Cisco Unified Communications OS Platform CLI. You can verify the system restarts and the correct version is active.

      Step 12   Click OK to initiate the switch version process.
      Note   

      You can perform system validation only after applying the license file after switch version is completed. See Cisco Unified CCX Administration Guide, Release 9.0(1) for detailed information on how to upload Unified CCX licenses.

      What to Do Next

      As part of the successful switch version process ensure that the system restarts, Unified CCX services come up after the restart, the correct version is active, and the database replication is set successfully by following the steps listed in Verify software upgrade for single-node deployment or Verify software upgrade for high-availability deployment.

      Upgrade via network

      In single-node deployment of Unified CCX, perform the following procedure on the publisher node. In a HA deployment of Unified CCX, perform the following procedure on both publisher and subscriber nodes.


      Note

      Do not use the browser controls, such as Refresh/Reload, while you are accessing Cisco Unified Operating System Administration. Instead, use the navigation controls that are provided by the interface.

      Procedure
        Step 1   Put the upgrade file on an FTP or SFTP server that is accessible by the server that you are upgrading.
        Step 2   Log in to Cisco Unified Communications Operating System Administration.
        Step 3   Navigate to Software Upgrades > Install/Upgrade. The Software Installation/Upgrade window appears.
        Step 4   From the Source list, choose Remote Filesystem.
        Step 5   In the Directory field, enter the path to the directory that contains 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. 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:
        • 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:).
        Step 6   In the Server field, enter the server name or IP address.
        Step 7   In the User Name field, enter your user name on the remote server.
        Step 8   In the User Password field, enter your password on the remote server.
        Step 9   Select the transfer protocol from the Transfer Protocol field and click Next.
        Step 10   Enter your Email Destination and SMTP Server in the fields provided, to use the Email Notification feature.
        Step 11   Choose the upgrade version that you want to install and click Next.
        Step 12   In the next window, monitor the progress of the download.
        Note   

        If you lose your connection with the server or close your browser during the upgrade process, you may see the following message when you try to access the Software Upgrades menu again:

        Warning: Another session is installing software, click Assume Control to take over the installation.

        If you are sure you want to take over the session, click Assume Control. If Assume Control does not display, you can also monitor the upgrade with the Real Time Monitoring Tool.

        Step 13   To upgrade and manually reboot the upgraded partition at a later time, perform the steps 10 and 11 mentioned in Upgrade with DVD.
        What to Do Next


        Caution

        During the installation of upgrade software, if the new log messages stop appearing in the upgrade log, the upgrade has failed.. When the upgrade fails, you must cancel the upgrade and restart the upgrade procedure.

        Verify software upgrade for single-node deployment

        Procedure
          Step 1   If you have triggered a switch version from Cisco Unified OS Administration web interface, log in to Unified CCX Serviceability web interface and navigate to Tools > Control Center—Network Services menu option to verify whether or not all the Unified CCX Services have come up successfully. See Cisco Unified CCX Serviceability Administration Guide Release 9.0(1) for detailed information.
          Step 2   Both CLI and the serviceability page can be used to check the status of switch version. Using the CLI, do the following to check whether switch version is successful:
          1. Login to Cisco Unified Communications OS Platform Command Line Interface using platform credentials.
          2. Enter the following CLI command utils service list.
          3. Verify that all the services in the output window are in STARTED state, except for the following:

            Cisco AXL Web Service[STOPPED] Service Not Activated

            Cisco DirSync[STOPPED] Service Not Activated

            Cisco Serviceability Reporter [STOPPED] Service Not Activated

            Cisco UXL Web Service [STOPPED] Service Not Activated

            Unified CCX Reporting Server [STOPPED] Service Not Activated

          Step 3   Check the current active and inactive versions after the switch over process by doing one of the following:

          • Login to Cisco Unified Operating System Administration web interface and go to Settings > Version to find out the current active version and to ensure that the switch version was successful.

            The Version Settings web page shows the software version on both the active and inactive partitions appropriately.

          • Through the Cisco Unified Communications OS Platform CLI, execute the commands - show version active and show version inactive.

            If the switch version is successful, the correct version appears in the active and inactive versions.

          Step 4   After the upgrade and switch version is successfully completed on the node:
          1. Rerun the Unified CCX Desktop Client Configuration tool from Plug-ins page in Unified CCX Administration.
          2. After Unified CCX Desktop Client Configuration tool completes successfully, close all open Cisco Desktop clients such as CAD, CSD, CDA on the client desktops and relaunch the desktop clients.
          3. On launch of the desktop clients, the upgrade process automatically starts. The clients have the latest version of software.
          4. Unified CCX Real-Time Monitoring Tool, Unified CCX Editor, and Cisco Historical Reporting Client does not support automatic upgrades. Manually uninstall the existing version and then download and install the relevant one from the current active version.

          If you are doing a switch version from higher to lower versions, see Switch Version.

          Verify software upgrade for high-availability deployment

          In the case of a High Availability setup, initiate the switch-version process through Cisco Unified Operating System Administration web interface or CLI after completing the software upgrade installation on both the publisher and subscriber nodes, first with publisher then the subscriber node. To identify whether the switch-version is successful, follow the steps mentioned below after triggering the switch-version process. The time needed to trigger the switch-version process depends on the amount of data available.

          Procedure
            Step 1   Enter the CLI command utils service list. This command lists the Unified CCX services in the command output window. In the list of services, check to see if the "Cisco Unified CCX Cluster View Daemon" service is in STOPPED state.
            Step 2   The CAD/CSD/CDA clients pointing to the first node fails over to the second node. The system will reboot. On successful reboot, the switch-version process is completed.
            Step 3   Display version information by executing the CLI commands - show version active and show version inactive.

            For a switch version from a lower version to higher version, the active partition should show the higher version and the inactive partition should show the lower version, and vice versa if the switch version process is done from a higher version to lower version.

            For a switch version from a lower version to higher version of Unified CCX, it is mandatory to follow the steps below during the switch-version process:

            1. Close all open Cisco Desktop clients such as Cisco Agent Desktop (CAD), Cisco Supervisor Desktop (CSD), and Cisco Desktop Administrator (CDA) on the client desktops.
            2. Once you complete switch version on the nodes successfully, navigate to Tools > Plug-ins > Cisco Unified CCX Desktop Suites from Unified CCX Application Administration web interface and rerun the Unified CCX Desktop Client Configuration tool.
              Warning   

              When performing a HA upgrade, run Unified CCX Desktop Client Configuration tool only after both the nodes are upgraded and switched over to the new version. If you run this tool after only one node is upgraded then Cisco Agent Desktop tool does not automatically fail over to the second node.

            3. On successful execution of the Unified CCX Desktop Client Configuration tool, relaunch the desktop clients.
            4. On relaunch of the desktop client, the upgrade process automatically starts to upgrade the desktop clients.

            If you are doing a switch version from higher to lower versions, see Switch Version.

            Step 4   Check the DB replication status between two nodes in a HA deployment of Unified CCX.
            1. In a High Availability deployment of Unified CCX, set the DB replication if it is not ACTIVE/ CONNECTED. You can check the DB replication status for the datastores across all servers in the cluster using Unified CCX Serviceability Administration. Choose Tools > Datastore Control Center > Replication Servers from the Unified CCX Serviceability menu bar to view the replication status. The value in State field for both the servers in this web page must display ACTIVE/ CONNECTED. See Cisco Unified Contact Center Express Serviceability Administration Guide for more information on how to reset replication.
            Step 5   Ensure that database replication of the operating system is functioning between the first node and the subsequent node by doing the following:

            In the Cisco Real Time Monitoring Tool, access Performance object under the System tab to monitor database replication status. The following list indicates the database replication status progress:

            0— Initializing

            1—Replication setup script fired from this node

            2—Good replication

            3—Bad replication

            4—Replication setup did not succeed

            Before you proceed, ensure that you have a good database replication status. For more information about using the Real Time Monitoring Tool, see the Cisco Unified Real Time Monitoring Tool Administration Guide.

            Warning   

            Once you complete the switch version of second node, execute the following CLI command utils uccx dbreplication repair all to remove any data discrepancy between the two nodes.

            Step 6   Verify whether the switch was successful or not by doing the following:
            1. Go to Cisco Unified Communications Operating System Administration web interface.
            2. Choose Settings > Version. The Version Settings window appears.
            3. Verify that the correct product version is now running on the active partition.
            4. Verify that all activated services are running.
            5. Log in to Unified CCX Administration by entering the following URL and entering your user name and password: https://server-name/ uccxadmin
            6. Verify that you can log in and check to see if your configuration data exists.
            Step 7   After the upgrade and switch version is successfully completed on both the nodes:
            1. Rerun the Unified CCX Desktop Client Configuration tool from Plug-ins page in Unified CCX Administration.
            2. After Unified CCX Desktop Client Configuration tool completes successfully, close all open Cisco Desktop clients such as CAD, CSD, CDA on the client desktops and relaunch the desktop clients.
            3. On launch of the desktop clients, the upgrade process automatically starts. The clients are updated with the latest version.
            4. Unified CCX Real-Time Monitoring Tool, Unified CCX Editor, and Cisco Historical Reporting Client does not support automatic upgrades. You have to manually uninstall the existing version and then download and install the relevant one from the current active version.

            If you are doing a switch version from higher to lower versions, see Switch Version.

            Switch Version

            After upgrading, you can revert to the software version that was running before the upgrade, by using the Switch Version option to switch the system to the software version on the inactive partition.

            This section contains the following topics:

            Revert cluster to previous version

            To revert a cluster to a previous version, follow these major steps:

            Procedure
              Step 1   Revert the publisher node. See Revert publisher node to previous version.
              Step 2   Revert the subscriber node. See Revert subscriber node to previous version.
              Step 3   If you are reverting to an older product release, reset database replication within the cluster. See Database replication after reversion.

              Revert publisher node to previous version


              Note

              If you are doing a switch version from a higher to lower version, you need NOT rerun the Unified CCX Desktop Client Configuration tool from Unified CCX Administration.


              Note

              Cisco Desktop Utilities do not support automatic downgrade processes. Unified CCX Real-Time Monitoring Tool, Unified CCX Editor, and Cisco Historical Reporting Client do not support automatic downgrade processes.

              Procedure
                Step 1   Open Cisco Unified Communications Operating System Administration by entering the URL: https://server name/cmplatform/showHome.do (where server name specifies the host name or IP address of the Unified CCX server).
                Step 2   Enter your platform administrator user name and password.
                Step 3   Choose Settings > Version. The Version Settings window appears.
                Step 4   Click the Switch Versions button.
                Step 5   After you verify that you want to restart the system, the system restarts, which might take up to 15 minutes.
                Step 6   During the switch version process, follow the steps:
                1. Close all open Cisco Desktop clients such as Cisco Agent Desktop (CAD), Cisco Supervisor Desktop (CSD), and Cisco Desktop Administrator (CDA) on the client desktops.
                2. Once you complete switch version on the node(s) successfully, manually uninstall the existing Cisco Desktop clients and reinstall the new Cisco Desktop Clients from the current active partition.
                Note   

                If you are doing a switch version from a higher to lower version, you need NOT rerun the Unified CCX Desktop Client Configuration tool from Unified CCX Administration.

                Cisco Desktop Utilities do not support automatic downgrade processes. Unified CCX Real-Time Monitoring Tool, Unified CCX Editor, and Cisco Historical Reporting Client do not support automatic downgrade processes.

                Revert subscriber node to previous version

                Procedure
                  Step 1   Open Cisco Unified Communications Operating System Administration by entering the following URL:

                  https://server name/cmplatform/showHome.do

                  where server name is the host name or IP address of the Unified CCX server.

                  Step 2   Enter your Platform Administrator user name and password.
                  Step 3   Choose Settings > Version. The Version Settings window appears.
                  Step 4   Click the Switch Versions button. After you verify that you want to restart the system, the system restarts, which might take up to 15 minutes.
                  Step 5   To verify that the version switch was successful, follow these steps:
                  1. Log in to Open Cisco Unified Communications Operating System Administration again.
                  2. Choose Settings > Version. The Version Settings window appears.
                  3. Verify that the correct product version is now running on the active partition.
                  4. Verify that all activated services are running.
                  5. Alternatively, you can also verify that the version switch was successful through Cisco Unified Communications OS Platform CLI by using the CLI commands - show version active and show version inactive.

                  Database replication after reversion

                  If you revert the servers in a cluster to run an older product release, you must manually reset database replication within the cluster. To reset database replication after you revert all the cluster servers to the older product release, enter the CLI command utils dbreplication reset all.

                  When you switch versions by using Cisco Unified Communications Operating System Administration or the CLI, you get a message that reminds you about the requirement to reset database replication if you are reverting to an older product release.

                  COP files

                  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 provided along with the COP file package:

                  • Install the COP file on every server in a cluster.
                  • After you install a COP file, you must restart the server.

                  Note

                  You must restart Unified CCX 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.

                  TFTP File Management


                  Note

                  The Software Upgrades > TFTP File Management menu option is not applicable for Unified CCX.

                  Set up customized log-on message

                  You can upload a text file that contains a customized logon message that appears in Cisco Unified Communications Operating System Administration, Disaster Recovery System, and the command-line interface.

                  To upload a customized logon message, follow this procedure:

                  Procedure
                    Step 1   From the Cisco Unified Communications Operating System Administration window, navigate to Software Upgrades > Customized Logon Message. The Customized Logon Message window appears.
                    Step 2   To choose the text file that you want to upload, click Browse.
                    Step 3   Click Upload File. You cannot upload a file that is larger than 10kB. The customized logon message appears.
                    Step 4   To revert to the default log-on message, click Delete. Your customized logon message is deleted, and the system displays the default logon message.
                    1 In a single node deployment of Unified CCX, the node will be a publisher node by default.