For Cisco Prime Collaboration Release 11.5 and later

The following table lists the supported options to upgrade to Cisco Prime Collaboration 11.5.

After upgrading Cisco Prime Collaboration Provisioning, perform the following post upgrade tasks:

• 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 the server. Manually increase the vCPU reservation and power on the instances of the server. For more details on vCPU reservation, see Virtual Machine Requirements for Cisco Prime Collaboration Provisioning.

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

• It is recommended that you perform the following synchronization:

  • Domain synchronization

  • Infrastructure synchronization

  • Subscriber or User synchronization

• Issue:Snapshot revert on the VM instance , Time is not getting updated

  Recommended Action:

  Once you revert the snapshot on the VM instance, you can do either of the following options:

  • Reboot the PCP VM instance(Shut down Guest and Power On)

  • Run the following two commands on CLI by logging in with Troubleshooting account:

    • sudo timedatectl set-ntp true

    • sudo systemctl start ntpd

  Wait for 10 seconds.

  After following any one of the above options, try executing the date command on CLI and verify whether the correct date and time are displayed.

• Issue: Upgrade sequence completes in few seconds with a message, Domain/Device/Ldap sync in progress, could not do the upgrade.

  Recommended Action:

  • 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 older Mega-menu.

  Recommended Action: Perform one of the following actions:

  • Reboot the VMware Instance.

  • Clear the browser cache.

  • Open the provisioning application in a new browser.

• Issue: 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.

  Recommended Action:

  • Delete the standard license file from /opt/cupm folder.

• Issue: Migration from 11.x to 12.1, if the migration is not successful.

  Recommended Action:

  • Revert the snapshot of the PCP 12.1 application before migration.

  • Access the troubleshooting account, and check the PCP processes.