Use the Cisco Unified Communications Manager License Count Utility to generate a license report and save it in CSV format. To shorten the upgrade time, delete or purge Call Detail Records (CDRs) or log files that you no longer need. įollow the below steps to reduce the downtime during upgradation process. Upgrading without a current backup can result in lost data, lost node configuration, or disruption to services if there are complications during the upgrade process.ĭetermine if the versions of the devices and applications in use in your organization-such as endpoints, gateways, voicemail, presence, or other applications-are supported by Unified Communications Manager Release 9.1(x), You can refer the below link to know more about the compatible devices. Perform a Disaster Recovery System (DRS) backup up of your entire cluster before each upgrade. If you have Cisco support for your Unified setup, Make sure that you consult with Cisco TAC team before proceeding with the Migration process.īefore migrating your production environment, try to emulate the upgradation setup in a lab to avoid last minute issues.
For example, record the number of each type of registered IP phone, gateway, and each FXS, FXO, T1CAS, PRI, MOH, MTP, CFB, or XCODE device resource.
For each node, record the number of each device type that is displayed.
In addition to the above, you must determine the registration counts by using the RTMT or the Unified Communications Manager device count summary.
This post will help you understand how to Migrate CUCM from version 8.0.2 to 9.1.2. After the successful installation of 8.0.2, I planned to migrate my 8.0.2 CUCM to 9.1.2 and recorded the steps involved in the upgradation.
In my last post, I showed how to install CUCM 8.x on Vmware.