10-06-2010 01:03 AM - edited 03-16-2019 01:11 AM
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!
Solved! Go to Solution.
10-06-2010 06:51 AM
Hi Ramon,
From
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
Download Information
Special Notes for 5.1(3) to 7.x Upgrades via SFTP
If your current version is 5.1.3.4111-1 or lower:
If your current version is 5.1(3e) or 5.1.3.6xxx-y:
Maintaining your inactive partition
Licensing Information
Here is the "getting started" info for CUCM 7.1(3) to 8.0(2c)
Release Information
Bridged Upgrade Available
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
Maintaining your inactive partition
Licensing Information
End of Life Information
Cheers!
Rob
10-06-2010 06:51 AM
Hi Ramon,
From
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
Download Information
Special Notes for 5.1(3) to 7.x Upgrades via SFTP
If your current version is 5.1.3.4111-1 or lower:
If your current version is 5.1(3e) or 5.1.3.6xxx-y:
Maintaining your inactive partition
Licensing Information
Here is the "getting started" info for CUCM 7.1(3) to 8.0(2c)
Release Information
Bridged Upgrade Available
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
Maintaining your inactive partition
Licensing Information
End of Life Information
Cheers!
Rob
10-06-2010 08:24 PM
Thanks Rob
06-28-2011 03:49 PM
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.
06-28-2011 03:52 PM
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..
06-28-2011 11:08 PM
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
06-29-2011 10:51 AM
thank you Ramon.
06-29-2011 10:51 AM
thank you for the help. I will take this into consideration.
02-01-2012 06:27 AM
Excellent documentation Rob ( +5 ), you are indeed an asset to this forum.
GP.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide