CUCM 5.1 to 7.1 Upgrade

Unanswered Question
Feb 18th, 2010
User Badges:

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;}

Looking for some guidance regarding the upgrade of an existing three node CUCM 5.1 cluster to a NEW three node CUCM 7.1 cluster.

The upgrade guides don't seem to be of much help.  I'm making some assumptions here, but it looks to me as if I need to upgrade the current cluster to 7.1(3b) (latest 7.1 direct upgrade), followed by a backup of this cluster and a restore to the new cluster (assuming running 7.1(3b).

Am I heading down the right path?  Is there not a way of performing this upgrade without impacting the current production environment? 

I'm also wondering, both with or without UCSS, how does the customer obtain these interim releases?  It may be simple via the PUT tool with UCSS (I'm guessing), but if they don't have UCSS and are willing to purchase 7.1 for the new/upgraded cluster, how can they obtain the interim releases required for the upgrade (the new MCS servers may ship with 7.1(4)).

Has anyone performed a similar upgrade?

What would be the most efficient way to achieve this upgrade?

Current CUCM 5.1.3.4106-2

Current Servers are 7825H3

Future Servers are 7825I4

Supported Server Models:

http://www.cisco.com/en/US/partner/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html

Supported CUCM Upgrades:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html#wp43011

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Tommer Catlin Thu, 02/25/2010 - 07:37
User Badges:
  • Green, 3000 points or more

I cant confirm, but if you can upgrade your current 5.x hardware to 7.1x, I would go that route.


In place upgrade from 5.x to 7.x

Reload your Subscriber (do not try and upgrade it, not worth the time)

license it all and have it run for about a week.


After running sucessfully for the week, DRS your Publisher


Re-install your publisher on the new hardware and DRS Restore


Reload your Subscriber

Add in the additional subscriber



I have had issues where the 5x disc will not boot up on new hardware.  This is why you have to do an in place upgrade.  You could be safe and build the cluster offline.  IE....  DRS the 5.x, restore on the new hardware offline.  Upgrade to 7.x test in the lab.  If all is good, then go back to the in place upgrade of production and run.



Dont worry about what ships with the server.  You can download whatever you want from CCO.  As long as you have a 7.x bootable media, you are good.


For the actual upgrade licenses, etc..    it is confusing and a mess.   Use the PUT tool and check out everything you need for the nodes.  Cisco will then ship the PAK key and media to you.

Your additional node that you ordered should come with a PAK key in the box.


If you happen to have a 7.x bootable media, you can start the process and email [email protected] and request a 60 day temp license to run your cluster.  Include in the email your SO, PO and smartnet contract that the 7.x has been ordered.

Actions

This Discussion