upgrade guide from CUCM 5.1.3 to 7.1.x then to 8.0(2)

[ramon.yu.jr]

We are planning to upgrade our CUCM 5.1.3 to 8.0(2) but since there is no direct upgrade to 8.0(2) from 5.1.3 need to go to 7.1.x first. Can someone share me the link on how to actually do the upgrade from the versions mentioned?  Thanks!

[Rob Huffman · Accepted solution]

Hi Ramon,

From

Unified Communications Manager (CallManager) Upgrade Tool

Here is the "getting started" info for CUCM 5.1(3)x to 7.1(3). These are significant

upgrade paths so make sure to do your Due Diligence

Release Information

• CUCM 7.1(3) was originally released on September 24, 2009.

• The full version number is 7.1.3.10000-11.

Download Information

• The files required for this upgrade are not available on cisco.com.

• The media that comes with your upgrade kit will contain the files required for the upgrade.

Special Notes for 5.1(3) to 7.x Upgrades via SFTP

If your current version is 5.1.3.4111-1 or lower:

• You must install a special patch to allow the upgrade file to be detected on the SFTP server.

• You must raise a TAC service request and ask for the ciscocm.5x_ftp_fix.cop.sgn file to be posted for you.

If your current version is 5.1(3e) or 5.1.3.6xxx-y:

• You must download and install the ciscocm.5.13e_upgrade.cop.sgn file from the CUCM Software Center prior to attempting the upgrade.

• For more information reference the CUCM 7.1(2) Operating System Administraion Guide.

Maintaining your inactive partition

• You can upgrade to this version directly from your current version and maintain your current version in the inactive partition.

• CUCM 5.x installs create disk partitions using a fixed size,regardless of actual disk size. In CUCM 6 we began using percentages ofdisk size for partition sizing.

• Upgrading from CUCM 5 to CUCM 6 or 7 will not resize yourpartitions. This can cause upgrade failures and RTMT alertspost-upgrade due to low available space on the active partition,particularly on systems with multiple CUCM locales installed.

• Cisco recommends after any 5.x to 6 or 7 upgrade you take a backup, reinstall the server from scratch at the new version to take advantage of the new partition sizes, and then restore from backup.

Licensing Information

• CUCM 7 requires an additional Software Feature License that was not required in CUCM 5.

• In order to upgrade to this version you must purchase the upgrade kit from a Cisco Partner or order it via the Product Upgrade Tool.

• Included with the upgrade kit will be the PAK required to generate the Software Feature License.
• Once you have obtained your upgrade kit you can submit the PAK to the Cisco Product License Registration website.

Here is the "getting started" info for CUCM 7.1(3) to 8.0(2c)

Release Information

• CUCM 8.0(2c) was originally released on May 6, 2010.

• The full version number is 8.0.2.40000-1.

Bridged Upgrade Available

• This version allows for bridged upgrades in the case where your current hardware is not supported with the destination version.

This feature allows you to upgrade and take a DRS backup of the newversion on unsupported hardware while not running any services. Thisallows you to install and and do a DRS restore on the supportedhardware.Reference the Operating System Administration Guide for more information on the bridged upgrade feature.

Download Information

• The files required for this upgrade are available for download on cisco.com.

• Click here to be directed to the Software Center downloads for CUCM.

Maintaining your inactive partition

• You can upgrade to this version directly from your current version and maintain your current version in the inactive partition.

Licensing Information

• The Software Feature License for CUCM 6 and 7 is not valid for CUCM 8.

• In order to upgrade to this version you must purchase the upgrade kit from a Cisco Partner or order it via the Product Upgrade Tool.

• Included with the upgrade kit will be the PAK required to generate the Software Feature License.

• Once you have obtained your upgrade kit you can submit the PAK to the Cisco Product License Registration website.

End of Life Information

• End of Sale/End of Life has not been announced for this version.
• Engineering Specials are being built to incorporate new bug fixes until October 25, 2010.
• CUCM 8.0(1), 8.0(2), 8.0(2a), and 8.0(2b) have been deferred due to CSCtg50662.  Click here for the deferral notice.

Cheers!

Rob

[ramon.yu.jr]

Thanks Rob

[kraghavansag]

I have a similar upgrade question. We are in the process of upgrading call manager from 5.1.3 to 7.1(5b). The servers are MCS-7835 with 2X1GB memory and 2X72GB HDDs. As part of hardware requirements to run 7.x, we have purchased and installed 2GB of memory. We want to upgrade the HDDs to 2X146GB so that server complies with the hardware requirements. I am kind of thinking of the robust ways to handle this upgrade. Any help is appreciated.

Scenario 1 :

Upgrade 5.1.3 to 7.1 in the existing server with 4GB memory and 2X72GB HDDs (if possbile). Take a backup. Install the new 2X146 GB HDDs. Do a  fresh install of 7.1 and restore the backup.

Scenario 2:

back up existing version of 5.1.3. Do a fresh install of 7.1 and build the call manager database (add phones, configuration information captured from old version. in case of any failure insert the old HDDs.

[thisisshanky]

i would vote for option 1. you will have the flexibility of checking the upgrade in the 5.x system itself without disrupting anything as upgrade happens in inactive partition. If the upgrade fails because of unsupported hardware you can always backup 5.x and put 146gb in, install the a brand new copy of 5.1.3 (provided you have discs) and then restore the data on the 146gb and then upgrade to 7.x Worst case if all scenarios fail, you can manually export the data or use a third party tool like IPTAS..

[ramon.yu.jr]

Hi kraghavansag ,

We did our upgrade using option 1 although we didn't have to upgrade our HDD to 146GB.  Below are the specs of our CUCM for your reference:

Server: MCS-7845H2

Memory: 4GB

HDD: 72GB

Partition: 16.5GB / 16.5GB

Our set-up is 1 PUB and 2 SUB, we disconnect the PUB and SUB2 from the network so the phones register to SUB1 on version 5.  Initially we were able to upgrade from 5 to 7 with no issue but when upgraded to 8 we encountered issue.  We remain PUB and SUB2 on version 7, connect them back to the network and disconnect SUB1 while working with Cisco TAC in investigating the issue.  Later on it was discovered that we didn't have enough space in our partition.  We back-up config on SUB1, increased partition to 16.5GB and did a fresh install of 7 then upgrade to 8 and restore the configuration leaving version 7 on the inactive partition for contingency.  After confirming the upgrade was successful, we rolled-back SUB1 to version 7 and connect it back to the network / cluster.  Disconnect PUB and SUB2 from network, confirm phones register to SUB1.  Promoted SUB1 also as publisher (note you need to do some license changes on this).  Increased partition and fresh install 7 on PUB and SUB2 then upgraded to 8.  Disconnected SUB1, put back PUB and SUB2 to network.  Re-installed SUB1 to 7 then upgrade to 8.  Take note these done over four weekends to minimize impact to our business but that may differ with yours.

Hope this helps you plan your migration.  Also, please take note just in case your CallManagers sit on a DMZ.  You will need to open TCP 2445 in the ACL or firewall to get the Corporate Directory working on 794x and 796x phones.  On version 8, these phones use a Initial Trust List which communicates to the CallManager over that port. 

Regards,

Ramon

[kraghavansag]

thank you Ramon.

[kraghavansag]

thank you for the help. I will take this into consideration.

[Gajanan Pande]

Excellent documentation Rob ( +5 ), you are indeed an asset to this forum.

GP.