What A Cluster! Request for comment on upgrade startegy!

[Hieronymous Merkin]

So here is the current environment:

CUCM Version 7.5 on MCS hardware, one PUB and 2 SUBS.

Unity Version 5 on MCS hardware!  Windows based!

UCCX Version 8.0 with two servers.

2 MGCP PRI Gateways about 100 users

Goal - Move to UC hardware, VMware and Version 10.5 across cluster.  All input is welcome! Trying to resolve the inter-dependencies as to which intermediate moves to make.   Get the entire cluster on a common version like maybe 8.0 or 8.5, then move to VMware, then upgrade?  Can you do the firmware at any time?  What is the best order to do this?   (we posted a question similar to this, but new info is the freaking Unity Version 5).

[Manish Gogna]

Hi,

For Unity Connection you should first upgrade to version 8.x as explained here

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/8x/upgrade/guide/8xcucrugx/8xcucrug022.html

Then follow the upgrade guide for Unity connection 10.x

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/install_upgrade/guide/10xcuciumgx/10xcuciumg030.html

For CUCM, you can use Prime Collaboration Deployment 10.5

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/pcdadmin/10_5_1/CUCM_BK_U35347D2_00_pcd-administration-guide-1051/CUCM_BK_U35347D2_00_ucmap-administration-guide-1051_chapter_010.html

Phone firmware can be upgraded first before the cucm upgrade.

Upgrade the Unity connection to 8.x first as it is compatible with CUCM 5.x and later

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/compatibility/matrix/cucsccpmtx.html

HTH

Manish

[DrVoIP · Accepted solution]

You are going to have to schedule multiple maintenance windows.  If you are trying to minimize impact on production system, you might consider this strategy:

1 Maintenance Window 1 20 hours

Build out Vmware Hosts (can be done during business hours)

Build out CUCM, Unity and UCCX  on VMware using Version 8.6

Build out CUCM on Current MCS hardware using Version 8.6

Backup Existing MCS CUCM Cluster and the Restore to New VMware Cluster

Note Service Impact  -  At this point CUCM servers are virtualized on 8.6 Unity and UCCX remain on MCS at current version. Each CUCM server will be off line during the upgrade to 8.6. and service impact to production system should be nominal and predictable.  This is to be accomplished on an Off-Network LAN as NIC connectivity is required, the same IP’s are used, but can not reside on production network.

3.2 Maintenance Window 2  20 hours

Build out Unity as 8.6 on VMware

Use CISCO Cobras restore Unity to VMware.

Retire Unity 5.0 Windows MCS server.       

Note Service Impact -  At this point CUCM and Unity are now on VMware versioin 8.6.  The production UCCX system will still be on MCS hardware. Service interruption should be nominal and predictable resulting in a modest interruption to Voice Mail  during the time Server is retired an VMware Host for Unity is put on line.

3.3 Maintenance Window 3 20 hours

Build UCCX on 8.6 virtualized (exact version as upgrade)
Upgrade UCCX MCS Server one
Backup and Restore to virtualized environment 8.6 environment
Take Vmware snapshot
Upgrade UCCX MCS Server two to 8.6
Backup and Restore to virtualized environment 8.6
Upgrade UCCX Server 1 to 10.5
Upgrade UCCX Server 2 to 10.5
Upgrade Desktop Clients (or migrate to Finesse and CUIC)

Note Service Impact – Production system is running on VMware as upgrade and move UCCX servers to VMware.   Service interruption is nominal and predictable

3.4 Maintenance Window 4 20 hours

Upgrade CUCM Servers to 10.5