that you make a full backup of your database server and application server,
and/or the OVA snapshot of both. If you do not make a backup, you cannot bring
back your old system intact if the upgrade fails, since a rollback is not
For Cisco Prime
Collaboration Provisioning 11.0 and later, the vCPU reservations are increased.
Thus when you are upgrading to Prime Collaboration Provisioning 11.0 and later,
power off the instances of application and database server. Manually increase
the vCPU reservation and power on the instances of application and database
server. For more details on vCPU reservation, see
Virtual Machine Requirements for Cisco Prime Collaboration Provisioning.
Ensure that the
following prerequisites are satisfied before you begin the upgrade process:
No order is
in released state.
synchronization is in progress state.
No wizard is
in active state.
upgrading, you need to install an engineering special in Cisco Unity
Connection(10.5.x & 11.0) for successful subscriber synchronization.
Contact TAC to obtain the Cisco Unity Connection engineering special for the
bug (CSCux67499). If you are using Cisco Unity Connection release below 10.5,
then you must upgrade to Cisco Unity Connection version 10.5.x and then apply
the engineering special.
Cisco Prime Collaboration Provisioning, we recommend you to perform 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.
22 when you do SFTP to the Cisco Prime Collaboration server.
the Message Digest 5 (MD5) checksum of the application bundle matches with the
value in the download site.
To view the MD5
checksum of the application bundle available in Cisco.com site, hover your
mouse on the filename.
Log in to the
Cisco Prime Collaboration server as the administrator, through the VM 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.
distributed environment, log in to the database server for the database server
upgrade. For the application server upgrade, log in to the application server.
application bundle is available in an FTP server, enter:
user admin password plain cisco (for example)
If you have placed the
application bundle at /localdisk directory of the Cisco Prime Collaboration
admin(config-Repository)# url disk
<application bundle name><repository name>
The application bundle name, for example, is
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.
Power off and
power on the VMware instance.
step is not applicable for upgrade in a distributed environment.
If a session is
already open in the browser, clear the browser cache and refresh the browser
before you start using the upgraded application.
Upgrade Cisco Prime Collaboration Provisioning in Distributed
To upgrade Cisco Prime Collaboration Provisioning in distributed
Before rebooting the application server ensure that the database
server reboot is complete.
Cisco Prime Collaboration Provisioning Upgrade
Upgrade sequence completes in few seconds with a message,
Domain/Device/Ldap sync in progress, could not do the upgrade.
Make sure that the prerequisites are satisfied and continue with
the upgrade process.
Clear the in-progress activities listed in the message.
Issue: After Upgrading, the provisioning UI still shows the
Perform one of the following actions:
Reboot the VMware Instance.
For distributed environment, database server should be restarted
first followed by the application server.
Clear the browser cache.
Open the provisioning application in a new browser.
If you upload a new production license file when the standard
license file is already present, the authorization role does not list
individual domains because of the presence of the standard license file.
Delete the standard license file from /opt/cupm folder.