cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

AMA-CUCM Troubleshooting: Best Practices for Reading Trace Files

Operational Guide for Cisco Unified Communications Manager.pdf

19182
Views
1
Helpful
17
Comments

As customers plan to upgrade their Cisco Unified Communications Manager to take advantage of new features, and if the upgrade includes moving to virtual machines, the procedural steps to accomplish these tasks are not clear.   Cisco does provides documentation on how to upgrade, how to migrate to a virtual machine and what versions/servers are supported, but there is no one document that combines these 3 key areas into a single document that details the 'best practices' for planning an upgrade and migration. 

The Operational Guide for Cisco Communcations Manager is the one document that details the best practices for upgrading and migrating to Cisco Unified Communications Manager v9.x.  The document details upgrade from 6.x/7.x/8.x installs on physical MCS servers to 9.x servers running in a virtual machine. 

Comments
Participant

Hi Dan, great Document. We will be upgrading from CUCM 6.1.4 to  CUCM 10.0.1.10000-24. Couple of quick questions.

1. Is it necessary when we make the visualization jump to go to 8.0(3) or could it go something like 8.0(2) instead?

2. From the above should we use the 9.1 OVA template or use 10.0 OVA template when we install 8.0(3) as a vm? (looks like the version of Linux is different per 9.1 and 10.0 OVA)

3. Could we save time to and instead of upgrading an existing subscriber install new and join to cluster?

Thanks,

Dan

Cisco Employee

Dan,

If you are going to be upgrading to 10.0, I would recommend you look at Prime Collaboration Deployment (PCD) to do this migration.  PCD is a no cost line item that can be added when ordering UCM 10.0.  PCD makes your questions above moot.  PCD will allow you to do a one step, direct upgrade from your 6.1(x) cluster to 10.0.  If you need high availability, you can PCD migrate the cluster to a new set of IP's and hostnames, test the new version, then allow PCD to rehost/reIP the 10.0 servers back to the 6.x hostname/IP and bring up the cluster.

If PCD is not an option, then to answer your question:

1) The intermediate target can be any version that the customer chooses.   But I would recommend you choose an 8.0(2) - 8.5(x) as the interim release because that range has the largest to/from base.

2) Use the OVA specific to the install.  So if you are installing 8.0(3), use the 8.0(3) OVA.  When you start the successive upgrades, you will need to modify the OVA per the release notes. 

3) Cisco does not have a documented procedure on just upgrading the publisher.  So the supported method for upgrade/migration is to do full cluster (all nodes) upgrades/migration.  Part of the reason we do not document this is because installing a new subscriber to an upgraded publisher will be missing OS level configuration that will cause the subscriber to might not be in the same state after the install (service activation, certs, hosts tables, etc.).

Thanks,

Dan Keller

Technical Marketing Engineer

CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards