[cisco-voip] Upgrade CUCM 7.0(3a) to 8.0(3) and move to UCS

[Ryan Ratliff]

In general you should be fine there.  Make sure you do your phone loads prior to the upgrade so you don't get stuck with all the phones upgrading when you are trying to come back into production.

If you can do everything with the UCS cluster in a dead-net it will be less stressful watching that DRS restore go since you can leave the MCS servers up.

I sincerely hope you aren't planning to stay on 8.0(3) for any length of time.  If you are a partner you should look into the migration scenarios for the Drive 2 Nine program (https://communities.cisco.com/community/partner/collaboration/migration) for more info and how 9.1(2) will make this upgrade process easier for you.  There is a customer portal with similar info in the works.

-Ryan

On May 4, 2013, at 2:41 PM, Reto Gassmann <voip at mrga.ch> wrote:

Hello group
 
We plan the upgrade from our CUCM 7.1(3a) Cluster (8 Servers) to 8.0(3). After the upgrade we also want to virtualize the cluster from MCS Servers to UCS. To reduce downtime we plan to do the upgrade with the following steps:
1.       Setup a new CUCM 8.0(3) cluster on UCS with different IP addresses
2.       Upgrade CUCM 7.1(3a) to 8.0(3) on MCS
3.       Take backup (DRS) of upgraded CUCM 8.0(3) on MCS
4.       Shutdown MCS Cluster
5.       Change IP addresses to match old IP addresses on UCS cluster
6.       Restore CUCM 8.0(3) on UCS servers
 
Can I do the upgrade as described or do I run into any issues?
 
If I want to upgrade the IP Phone (7960 / 7961) firmware a few days before the upgrade where do I have to install the firmware software package, just on the TFTP server or on all servers in the cluster?
 
Any comments are welcome.
 
Regards Reto
 

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130506/5cd77880/attachment.html>