cucm 10.5 to 11.5

[miket]

I am planning to do a 10.5 to 11.5 upgrade of CUCM only. I am wondering what issues people have seen during this upgrade. I am doing a hospital so I am trying to make sure I have covered all my bases.

[Simon Coventry]

Hey Mike, 10.5 to 11.5 is quite straight forward if you are using the same hardware. One thing i would look out for is the end-of-support for some legacy endpoints such as Cisco 7912 phones.

As of Cisco Unified Communications Manager Firmware Release 11.5, the following phones are not supported:

• Cisco IP Phone 12 SP+ and related models

• Cisco IP Phone 30 VIP and related models

• Cisco Unified IP Phone 7902

• Cisco Unified IP Phone 7905

• Cisco Unified IP Phone 7910

• Cisco Unified IP Phone 7910SW

• Cisco Unified IP Phone 7912

• Cisco Unified Wireless IP Phone 7920

• Cisco Unified IP Conference Station 7935

If you use any of these phone models on an older release of Cisco Unified Communications Manager and you upgrade to Release 11.5, the phone will not work after the upgrade completes

[Manish Gogna]

Hi Mike,

"Plan the Upgrade or Migration" section of the upgrade guide details this, some imp tips for this standard upgrade

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/11_5_1/cucm_b_upgrade-guide-cucm-115/cucm_b_upgrade-guide-cucm-115_chapter_011.html

Table 2 Recommended Sequence for Performing Standard Upgrades in the Least Amount of Time

Sequence	Cisco Unified Communications Manager Nodes	IM and Presence Service Nodes
1	Upgrade the publisher node to the new software version. The new software is inactive.	—
2	Upgrade the subscriber nodes. The new software is inactive.	Upgrade the IM and Presence database publisher node in parallel with the Cisco Unified Communications Manager subscriber nodes.
3	—	Upgrade the subscriber nodes. The new software is inactive.
4	Switch the software version on the publisher node and reboot it. The new software is active.	—
5	Switch the software version on the subscriber nodes in parallel and reboot them. The new software is active.	Switch the software version on the database publisher node and reboot it.
6	Ensure that database replication is complete and functioning between the publisher node and all subscriber nodes before proceeding.	Switch the software version on the subscriber nodes in parallel and reboot them.
7	—	Ensure that database replication is complete and functioning between the publisher node and all subscriber nodes.

Note

In addition to following the recommended sequence, you must also verify that your phones and devices are configured for redundancy through the use of Cisco Unified CM Groups (CMGs) with primary subscriber nodes and backup subscriber nodes. As part of your upgrade planning, ensure that you have assigned nodes and devices to CMGs so that when one of the nodes in the CMG is unavailable, the remaining nodes within the CMG can support all of the devices that are assigned to the CMG. This configuration allows you to ensure availability throughout the upgrade.

Table 6 Minimum Time Required for Upgrade Tasks

Task	Minimum Time	Service Impact
Upgrade the Cisco Unified Communications Manager publisher node to an inactive version	2 to 4 hours Add 1 hour if a refresh upgrade	Refresh upgrades: no access to the UI
Upgrade the Cisco Unified Communications Manager subscriber nodes to an inactive version	1 to 2 hours	Refresh upgrades: phones are unavailable if no backup subscribers are configured
Switch the Cisco Unified Communications Manager publisher node to the new software version and reboot	30 minutes	—
Switch the Cisco Unified Communications Manager subscriber nodes to the new software version and reboot	30 minutes	Standard upgrades: phones are unavailable if no backup subscribers are configured
Cisco Unified Communications Manager database replication	30 minutes for deployments with small clusters or small databases 2 hours for megaclusters or large databases Note    WAN latency of 80ms or more can significantly lengthen these times	Phones are available with dial tone but end-user features are unavailable until upgrade is complete
Upgrade the IM and Presence database publisher node to an inactive version	2 to 4 hours Add 1 hour if a refresh upgrade	IM and Presence high availability is disabled Jabber is unavailable
Upgrade the IM and Presence subscriber nodes to an inactive version	1 to 2 hours	IM and Presence high availability is disabled Jabber is unavailable
Switch the IM and Presence publisher node to the new software version and reboot	30 minutes	IM and Presence high availability is disabled Jabber is unavailable
Switch the IM and Presence subscriber nodes to the new software version and reboot	30 minutes	IM and Presence high availability is disabled Jabber is unavailable
IM and Presence database replication	30 minutes for deployments with small clusters or small databases 2 hours for megaclusters or large databases Note    WAN latency of 80ms or more can significantly lengthen these times

HTH

Manish

[tonyperla]

Hi Manish,

I do have one question in relation to performing a 10.5 to 11.5 CUCM/IM&P upgrade.  At what point in the process your provided above does IM and Presence Sync Agent need to be stopped and when should HA be disbaled on the Presence Redundancy Groups?

Thanks In Advance!

Tony

[somya130488]

Hi Mike,

The Cisco Sync agent in IMP PUB and SUB will be stopped before you start installing the upgrade file on CUCM PUB.

Once the upgrade process is complete and the CUCM and IMP nodes are on 11.5, then you will be starting the Cisco Sync agent service on the IMP PUB and SUB nodes.

[sharath2424]

Hi Manish,

The upgrade process from 10.5 to 11.5 looks good where the clusters have CUCM servers and IM&P servers.....but we also have Jabber Edge Servers (Cisco Express Way E and Cisco Expressway E Servers) which are used for the users to access their jabbers on their mobile phones. Right now those servers version is 8.5  Do we need to upgrade those servers also...if yes, do we need to do in parallel with CUP servers or can do later also?

Thanks in advance..

Regards,

Sharath K.

[Jaime Valencia]

MRA requirements per VCS version are in the MRA configuration guide, you'll need to cross check the minimum release that is required to determine the upgrade path that is required.

[Ratheesh Kumar]

Hi there

If you have upgraded the CUCM/CUC/IMP to 11.5S3 or SU4, go ahead and upgrade the y X8.10.1 or later. 

Hope this helps!

Cheers
Rath!

***Please rate helpful posts***

[sharath2424]

Thanks Rath and Jaime

[Anil Sharma]

hello,

I see this is old post, however can you suggest if there is anything needed from license perspective when upgrading from 10.5 to 11.5 ?   assuming 10.5 licenses are hosted on central PLM. what all do I need to do to upgrade CUCM to 11.5 for licenses.

[TONY SMITH]

Licences need to be upgraded as they are major version specific.   Assuming this is an upgrade under contract,  email Cisco Licensing with a brief explanation and the following ..

(1) License request from the existing 10.x PLM, or the existing 10.x licence file

(2) Licence request from the new one PLM, if different

(3) SWSS contract number

(4) Upgrade Sales Order number