We recommend 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 possible.
In Cisco Prime
Collaboration Provisioning, 11.0 the vCPU reservations are increased. Thus when
you are upgrading to Prime Collaboration Provisioning 11.0, 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:
is in released state.
synchronization is in progress state.
is in active state.
(Cisco Unified Communications Manager, Cisco Unified Communications Manager
Express, Cisco Unified Presence, Cisco Unity Connection, and Cisco Unity
device) with 8.x or lower versions is present. If device with 8.x or lower
version is present, upgrade them to 9.x or later version.
environment, first follow the upgrade procedure for the database server, reboot
the database server, and then repeat the procedure for the application server.
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 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.
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.
distributed environment, log in to the database server for the database server
upgrade. For the application server upgrade, log in to the application server.
If the 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
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.
Power off and power on the
If a session is
already open in the browser, clear the browser cache and refresh the browser
before you start using the upgraded application.
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.
Upgrade sequence completes in few seconds with a message,
Domain/Device/Ldap sync in progress, could not do the upgrade.
that the prerequisites are satisfied and continue with the upgrade process.
in-progress activities listed in the message.
Issue: After Upgrading,
the provisioning UI still shows the older Mega-menu.
Perform one of the following actions:
distributed environment, database server should be restarted first followed by
the application server.
provisioning application in a new browser.
Issue:After upgrade, Apache server is down and doesn't