Prerequisites

We recommend
that you take a full backup of your machine, and/ or the OVA snapshot. If you
do not take a backup, you cannot bring back your old system intact in case of
an upgrade failure, since roll back is not possible.

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 detach the servers, go to
Administration > System
Setup > Assurance Setup > Cisco Prime 360
Integration on the Prime Collaboration Assurance
server. You can attach the servers after upgrade.

You must
delete the
/storeddata/Installed/cpcm directory, with root login
before performing the upgrade.

We do not recommend that you upgrade directly to a different
Prime Collaboration 10.6 deployment model than what you currently have in Prime
Collaboration 10.x, for instance, from Prime Collaboration 10.x small
deployment model to Prime Collaboration 10.6 medium deployment model.

For example, the recommended path to upgrade from a Prime
Collaboration 10.x small deployment model to Prime Collaboration 10.6 medium
deployment model is:

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

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.
Before you take
a snapshot of the VM instance:

To upgrade to Prime
Collaboration
10.6 Assurance, ensure you have reviewed the prerequisites,
and then perform the following steps:

Step 1

Shut down the
Prime Collaboration
10.x VM, and
then update the CPU and RAM settings to ensure that you meet the system
requirements. See the
Prerequisites 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, log in as root and
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, log in 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
VM console using the vSphere client.

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

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. As the admin user, enter the following commands:
admin#
application stop cpcm

Wait
approximately 10 to 15 minutes for all the processes to stop, after which you
will receive a message indicating the successful completion of the command. To
confirm if the processes have stopped, run the command
show
application status cpcm.

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.

During the upgrade, messages appear on the admin console
indicating the progress of the upgrade. Wait for the upgrade successful
message.

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.

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.

application stop
cpcm

application start
cpcm

Step 10

If you have
deployed Prime Collaboration Assurance - Standard, you can start using the
application. For Prime Collaboration Assurance - Advanced, you must rediscover
the devices. For details on how to rediscover the devices, see the Discovering
Devices section in the
Cisco Prime Collaboration
Assurance Guide - Advanced.

Step 11

For Prime Collaboration Assurance - Advanced Enterprise mode, if you
have created multiple users, log in to the Prime Collaboration Assurance server
with the administrator privilege and enter https://pc-service-ip/emsam/service/newusermgmt/updateUserDomain in
the browser URL; where,
pc-service-ip is the Prime Collaboration Assurance server IP
address.

While
upgrading Prime Collaboration Assurance very large OVA, you can choose to
either upgrade to Prime Collaboration Assurance and Prime Collaboration
Analytics or Prime Collaboration Assurance only.

If you want
to enable Prime Collaboration Analytics during the Prime Collaboration
Assurance upgrade, you require two virtual machines—Database and Application.
For more information on how to enable and disable Prime Collaboration
Analytics, see the Cisco Prime Collaboration
Analytics Guide.

Post Prime Collaboration
Analytics Upgrade

After upgrading to Prime collaboration
Assurance
10.6, you need to run
the following scripts to ensure that the new features work as expected.

To run the script:

Step 1

Go to the URL:
https://<IP_address>/emsam/index.html#pageId=com_cisco_emsam_page_diag_links.

Click
Submit.
Logs
will be displayed, once the script execution is over.

Note

Each script will take more
than 3 hours to complete execution, depending on the available data.

Only one
script can be executed at a time.

Upgrade Cisco Prime
Collaboration Provisioning

Prerequisites

We recommend that you take
a full backup of your machine, and/or the OVA snapshot. If you do not take a
backup, you cannot bring back your old system intact if there is an upgrade
failure, since rollback is not possible.

Note

In a
distributed environment, perform upgrade only on the application server.
Separate upgrade for database server is not required. The Database server is
upgraded automatically, while running the upgrade procedure for the application
server.

Database
server should be active and running, while upgrading the application server.

To upgrade to Cisco Prime
Collaboration Provisioning
10.6, perform the following steps:

Step 1

Download the
application bundle. You can place the application bundle either on an FTP
server or the local disk folder in the Cisco Prime Collaboration server.
If you intend
to place the application bundle in the local disk directory, log in as root and
SFTP the application bundle to the /localdisk directory.

Note

Use port
22 when you do SFTP to the Cisco Prime Collaboration server.

Step 2

Verify whether
the Message Digest 5 (MD5) checksum of the application bundle matches with the
value in the download site. To do this, log in as root and enter:
md5sum<application bundle name>

To view the
MD5 checksum of the application bundle available in Cisco.com site, hover your
mouse on the filename.

Step 3

Log in to the
Cisco Prime Collaboration server as the administrator, through theVM console using the vSphere Client. It is recommended to
perform the upgrade using a console connection in order to prevent losing the
active SSH session while upgrade is in progress.

The application bundle name, for example, is
PCProvisioning-appbundle-10.6-320.x86_64.tar.gz

The upgrade process takes approximately 40 to 60 minutes. During
the upgrade, messages appear on the admin console indicating the progress of
the upgrade. Wait for the Cisco Prime Collaboration Provisioning upgrade
complete message before proceeding with the next step.

Step 7

Power off and power on the
VMware instance.

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

Note

In the
case of a distributed environment, after the upgrade,

Power
off the application VMware instance first and then power off the database
VMware instance.

Power
on the database VMware instance first and then power on the application VMware
instance.