Cisco Prime Collaboration Upgrade and Migration Guide, 10.0
Upgrading to Prime Collaboration 10.0
Downloads: This chapterpdf (PDF - 250.0KB) The complete bookPDF (PDF - 586.0KB) | Feedback

Table of Contents

Upgrading to Prime Collaboration 10.0

Upgrading Assurance

Before you Begin

Performing a Prime Collaboration Assurance (Includes Analytics) Upgrade

Upgrading Provisioning

Before you Begin

Performing a Prime Collaboration Provisioning Upgrade

Upgrading to Prime Collaboration 10.0

This section details the procedure to upgrade from Prime Collaboration 9.x to Prime Collaboration 10.0.

If you are running Prime Collaboration in converged mode, then you should detach Prime Collaboration Assurance and Provisioning, and then upgrade Assurance and Provisioning separately to version 10.0, and then attach the servers. See Cisco Prime Collaboration 10.0 Assurance- Advanced Guide for details about how to detach Prime Collaboration Assurance and Provisioning.

Upgrading Prime Collaboration Assurance

You can upgrade to Prime Collaboration 10.0 from a small, medium, large, or very large deployment using the upgrade application bundle available on Cisco.com. You can upgrade on a Prime Collaboration 9.5 installation which has none, any, or all of the three available Prime Collaboration patches installed, and also from Prime Collaboration 9.0.

Before you Begin

Before you upgrade to Prime Collaboration 10.0, you must review the System Requirement section in the Cisco Prime Collaboration 10.0 Quick Start Guide .

Prime Collaboration 10.0 includes Prime Collaboration Analytics. If your system does not have the sufficient resources to run Cisco Prime Collaboration Assurance and Analytics, then, upon upgrade, Prime Collaboration Analytics will be disabled.

If you meet the system requirements, you can evaluate Prime Collaboration Analytics. If you do not wish to evaluate Prime Collaboration Analytics, you can disable Prime Collaboration Analytics. See Enabling and Disabling Analytics for details about enabling and disabling Prime Collaboration Analytics.

You may choose to enable Prime Collaboration Analytics in the evaluation mode anytime within the evaluation period. However, the evaluation period for Prime Collaboration Analytics will not be extended from initial upgrade date.

After the evaluation period is over, you must add the Prime Collaboration Analytics license for Prime Collaboration Analytics to work. Before you add the Prime Collaboration Analytics license, you must ensure that you have met the system requirements.

Important Notes

  • The same deployment model in Prime Collaboration 9.x requires more memory and/or CPU in Prime Collaboration 10.0.
  • If you upgrade to Prime Collaboration 10.0 without changing the system requirements, then both Prime Collaboration Assurance and Prime Collaboration Analytics will be installed, however, Prime Collaboration Analytics will be disabled by default.
  • If you upgrade to Prime Collaboration 10.0 after you meet the system requirements, then both Prime Collaboration Assurance and Prime Collaboration Analytics will be installed, and Prime Collaboration Analytics will be enabled by default.

See Prime Collaboration Analytics Licensing in Cisco Prime Collaboration 10.0 Quick Start Guide for details about Prime Collaboration Analytics support on different deployment models.


Caution We recommend that you take a snapshot of the VMware instance before you start the upgrade so that you have a clean backup in place to be used if the database is corrupted during the upgrade.

We do not recommend that you upgrade directly to a different Prime Collaboration 10.0 deployment model than what you currently have in Prime Collaboration 9.0 or 9.5, for instance, from Prime Collaboration 9.0 small deployment model to Prime Collaboration 10.0 medium deployment model.

For example, the recommended path to upgrade from a Prime Collaboration 9.0 small deployment model to Prime Collaboration 10.0 medium deployment model is:

  • Move from Prime Collaboration 9.0 small deployment model to Prime Collaboration 9.0 medium deployment model, and then upgrade to Prime Collaboration 10.0 medium.

Or,

  • Upgrade to Prime Collaboration 10.0 small deployment model, and then move to Prime Collaboration 10.0 medium. See Cisco Prime Collaboration 10.0 Quick Start Guide for details about the procedure to move from one deployment model to another within a version.

Note Running commands that are not documented in this Guide might result in errors.


Performing a Prime Collaboration Assurance (Includes Analytics) Upgrade

To upgrade to Prime Collaboration 10.0 Assurance:


Step 1 Shut down the Prime Collaboration 9.x VM, and then update the CPU and RAM settings to ensure that you meet the system requirements. See the Before you Begin section for details.

Step 2 Download the application bundle from Cisco.com . You can place the application bundle either on an FTP /SFTP server or the localdisk directory in the Prime Collaboration server.

If you intend to place the application bundle in the localdisk directory, SFTP the application bundle to the /localdisk directory.


Note Use Port 26 when you do SFTP to the Prime Collaboration server


Step 3 Verify whether the Message Digest 5 (MD5) Checksum of the application bundle matches with the value in the download site. To do this, login as root and run the following command:

md5sum < application bundle name>.

To view the MD5 Checksum of the application bundle available in Cisco.com site, rest your mouse pointer on the filename.

Step 4 Log in to the Prime Collaboration server as admin, through vSphere client.


Note We recommend you to use vSphere client instead of SSH to avoid failure in the upgrade process because of network issues.


Step 5 Enter the following commands to create a repository:

admin# configure terminal

admin(config)# repository <repository name>

repository name is the name of repository that you create .

Step 6 Enter the following commands:

    • If the application bundle is available in an FTP server:

admin(config-Repository)# url sftp://ftpserver/directory (for example)

admin(config-Repository)# user admin password plain cisco (for example)

    • If you have placed the application bundle at localdisk directory under the root directory of the Prime Collaboration server:

admin(config-Repository)# url disk:

  • admin(config-Repository)# exit
  • admin(config)# exit

You can verify whether the repository configuration is correct and the application bundle is available in the repository. To do this, log in as admin and run the following command:

admin# show repository <repository name>

This should list the application bundle.

Step 7 Stop the services. To do this, run:

admin# application stop cpcm

Ensure that the processes are stopped, before you proceed. A message is displayed when the processes are stopped.

Step 8 Enter the following command:

admin# application upgrade <application bundle name> <repository name>

application bundle name—The application bundle name, for example, PCAssurance-appbundle-10.0.0.xxxx.x86_64.tar.gz

repository name—Name of the repository where you have placed the application bundle.

For example, if the repository name is test, you need to run:

admin# application upgrade PCAssurance-appbundle-10.0.0.xxxx.x86_64.tar.gz test

Step 9 Enter yes to save the current ADE-OS running configuration.

The duration of the upgrade process depends on the system data and the deployment model. The upgrade process can take approximately 30 minutes for small deployment model, and up-to 4.5 hours for a very large deployment model.

To verify whether the upgrade is successful, run the following command:

show version

This displays the Prime Collaboration Assurance version details.

After the upgrade completes wait for ten minutes for the system to be up.

Step 10 Install the Prime Collaboration 10.0 Assurance and Analytics Service Pack 1. This service pack contains feature updates, new software support and bug fixes; see Readme for detailed information. You can download this service pack and Readme from the Prime Collaboration 10.0 Download Software web site.

Step 11 Log in as root and run the script:

./opt/emms/emsam/bin/refreshPhone.sh
 

When prompted for the password, enter cmuser.

After the running this script, wait for ten minutes for the system to be up.

Step 12 Rediscover the devices, before you start using Prime Collaboration to manage your network.


 

In case of issues, check the /var/log/ade/ADE.log and /var/log /cpcmupgrade.log files

In case of an Application failed to start error in the upgrade console, you need to stop all the processes and run the start command again.

Upgrading Prime Collaboration Provisioning

You can upgrade to Prime Collaboration10.0 from a small, medium, large, or very large deployment using the upgrade application available on Cisco.com. You can upgrade to Prime Collaboration Provisioning 10.0 from Prime Collaboration 9.0 and 9.5.

Before you Begin

Before you upgrade, you must ensure that the following operations, if running, are complete:

  • Infrastructure synchronization
  • Domain synchronization
  • Subscriber synchronization

See the Synchronizing Processors and Domains section in the Cisco Prime Collaboration 10.0 Provisioning Guide for details about how to check synchronization status.

If you perform an upgrade while any of these operations are running, the database could become corrupted.

Also, you must ensure that there are no active batch projects or orders in released state.

If you are upgrading on a large deployment, you need to upgrade only the application server.

If you want to upgrade to a different deployment model from your existing one, you may first run the Prime Collaboration upgrade process and then perform the OVA upgrade, or vice versa.

If you are upgrading Prime Collaboration 9.0 and you have configured OpenSSL, then they will have to manually configure OpenSSL for Prime Collaboration Provisioning 10.0 after the upgrade. See Cisco Prime Collaboration 10.0 Quick Start Guide for details.

Provisioning Attributes (Domain, Service Area and User Role) from Prime Collaboration 9.x gets converted to Service Templates in Prime Collaboration 10.0. Review the Feature Support After Upgrade—Prime Collaboration Provisioning section to know about the changes and for details about how to customize the provisioning attribute conversion.


Caution We recommend that you take a snapshot of the VMware instance before you start the upgrade so that you have a clean backup in place to be used if the database is corrupted during the upgrade.

Performing a Prime Collaboration Provisioning Upgrade

Before you begin the upgrade, ensure that you have reviewed the Before you Begin section.

To upgrade to Prime Collaboration 10.0 Provisioning:


Step 1 Download the application bundle. You can place the application bundle either on an FTP server or the localdisk folder in the Prime Collaboration server.

Step 2 Log in to the Prime Collaboration server as admin, through vSphere client.


Note We recommend you to use vSphere client instead of SSH to avoid failure in the upgrade process because of network issues.


Step 3 Enter the following commands to create a repository:

admin# configure terminal

admin(config)# repository <repository name>

Step 4 Enter the following commands:

    • If the application bundle is available in an FTP server:

admin(config-Repository)# url ftp://111.222.333.444 (for example)

admin(config-Repository)# user admin password plain cisco (for example)

    • If you have placed the application bundle at /localdisk directory of the Prime Collaboration server:

admin(config-Repository)# url disk

admin(config-Repository)# exit

admin(config)# exit

Step 5 Enter the following command:

admin# application upgrade <application bundle name> <repository name>

application bundle name—The application bundle name, for example, PCProvisioning-appbundle-10.0.0-757.x86_64.tar.gz

The upgrade process takes approximately an hour to complete.

You can check the /opt/cupm/sep/logs/upgrade-10.0-application.log file to see the progress of the upgrade. You must open another vSphere client session into the Prime Collaboration Provisioning server and log in as root, to view this log file.


Note We recommend you to use vSphere client instead of SSH to avoid failure in the upgrade process because of network issues.


Step 6 Reboot the VMware instance.


Note In the case of a distributed environment, after the upgrade, you must restart the database server first, and then the application server.


If a session is already open in the browser, you must clear the browser cache and refresh the browser before you start using the upgraded application.


 

After the Upgrade, the application goes to the Standard mode. When you add the 10.0 license, it goes into Advanced mode. See Cisco Prime Collaboration Provisioning Guide, 10.0 for details about features available in Standard and Advanced modes.