Upgrading CUCM 7.0.2-20000-5 to 7.1.3

[nikger1980]

Hello pro's !

I have a CUCM cluster that runs on version 7.0.2-20000-5.

One publisher and one subscriber.

Last week, the publisher needed to be reinstalled, because of an inconsistency error.

After backing up the publisher, we have the following behavior.

All the ipphones register to the sub, normally, we make changes to the pub, it seems ok, but no changes are made to the phones.

For example, we cannot reset an ipphone from CUCM pub's web page.

When we restart the subscriber and the registration goes to publisher, the changes are possible.. !

Also, we can see some data replication alerts.

I believe that the bug "CSCso81531" is what we are facing right now.

=====

"DB replication does not occur when connectivity is restored on lost node
Symptoms:
DB replication does not occur when connectivity is restored on lost node recovery"

=====

So, i guess that an upgrade to a later version should solve the problem.

I believe that i will not have any licencing issues going to 7.1.3 and above version, right ?

All opinions are more than welcome..

Thanks,

Nick

[Rob Huffman]

Hi Nick,

First things first, there are no new Licenses required for a 7.0 to 7.1 upgrade

so you would be good to go there

I would try to repair the DB replication first using the Workaround shown in the Bug notes;

CSCso81531            Bug Details

DB replication does not occur when connectivity is restored on lost node

Symptoms: DB replication does not occur when connectivity is restored on lost node recovery Condition: Problem reproducible on Unison throttle4 v 7.0.0.39731-4 dbl_repl_output_Broadcast_... log has 0 length, and remains this way for more than an hour. (means the cdr check is stuck or very slow) Failure seen in dbl_repl_cdr_Broadcast* log Processing ccmdbtemplate_se013_pub3c_ccm7_0_0_39731_4_1_346_device with 30 rows group 6 ------   Statistics for ccmdbtemplate_se013_pub3c_ccm7_0_0_39731_4_1_346_device ------ Creating Shadow Repl sync_6530_131419_1208467904 (the cdr check is stuck in a loop here, due to a delete on device table) ------------- Workaround: "utils dbreplication stop" on the sub(s) - can run all at once "utils dbreplication stop" on the pub (wait until the stop on the sub(s) is complete) "utils dbreplication clusterreset" from the pub When you run the command the log name is listed, the file will be here: file list activelog cm/trace/dbl/sdi* file view activelog cm/trace/dbl/filename watch file for status "utils dbreplication reset all" from the pub Stop and restart all the services on all the subs (or restart/reboot all the systems (subs))  in the cluster to get the services changes.  Do this only after "utils dbreplication status" shows status 2.

There is a direct upgrade path from 7.0(2) to 7.1(3) so that is good as well;

Table 7     Supported Cisco Unified Communications Manager Upgrades for Release 7.1(3x)

Cisco Unified Communications Manager	7.1(3b)SU2	7.1(3b)SU1	7.1(3b)	7.1(3a)SU1a	7.1(3a)SU1	7.1(3a)	7.1(3)
System Version	7.1.3.32900-4	7.1.3.31900-1	7.1.3.30000-1	7.1.3.21901-1	7.1.3.21900-4	7.1.3.20000-2	7.1.3.10000-11
Release Date	Feb 18 2010	Dec 15 2009	Dec 15 2009	Dec 8 2009	Dec 1 2009	Nov 4 2009	Sep 22 2009
Standard Support	Direct upgrade: 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a) SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3)	Direct upgrade: 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a) SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3)	Direct upgrade: 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a) SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 5.1(3g), 5.1(3f), 5.1(3e)1, 5.1(3d), 5.1(3c), 5.1(3b), 5.1(3a), 5.1(3)	Direct upgrade: 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a) SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3)	Direct upgrade: 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a) SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3)	Direct upgrade: 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a) SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 5.1(3g), 5.1(3f), 5.1(3e)1 , 5.1(3d), 5.1(3c), 5.1(3b), 5.1(3a), 5.1(3)	Direct upgrade: 7.1(2b)SU1, 7.1(2b), 7.1(2a) SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3)
	Direct upgrade using DMA: none	Direct upgrade using DMA: none	Direct upgrade using DMA: 4.3(2), 4.2(3), 4.1(3)	Direct upgrade using DMA: none	Direct upgrade using DMA: none	Direct upgrade using DMA: 4.3(2), 4.2(3), 4.1(3)	Direct upgrade using DMA: 4.3(2), 4.2(3), 4.1(3)
Note Refer to the Notes about Engineering Specials (ESs), Service Updates (SUs), and Windows Service Release (SR) Upgrades concerning upgrades from ESs.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html#wp43011

After getting to 7.1(3), it has been recommended by many people here that 7.1(3b)SU2 is a very

stable build, so try to move in that direction right away.

Cheers!

Rob

[nikger1980]

Thanks Rob for your answer !

As i see to the Compatibility Matrix that you've posted, i could make a direct upgrade to the 7.1(3b)SU2, or i miss something?

Thanks again,

Nick

[Rob Huffman]

Hi Nick,

Yes, you are most correct my friend

I just checked using

Unified Communications Manager (CallManager) Upgrade Tool

and here is the outcome;

Introduction

This tool is used to identify the steps necessary to upgrade your Cisco Unified Communications Manager appliance.

Usage Guidelines

Pick the version you are uprading from and the version you are upgrading to.

Current Version	8.0(2c)SU18.0(2c)8.0(2b)8.0(2a)8.0(2)8.0(1)7.1(5b)7.1(5a)7.1(5)SU17.1(5)7.1(3b)SU27.1(3b)SU17.1(3b)7.1(3a)SU1a7.1(3a)SU17.1.3.ES7.1(3a)7.1(3)7.1(2b)SU17.1(2b)7.1(2a)SU17.1(2a)7.1.2.ES7.1(2)7.0(2a)SU27.0(2a)SU17.0(2a)7.0.2.ES7.0(2)7.0(1)SU1a7.0(1)SU17.0(1)6.1.5.ES6.1(5)6.1(4a)SU26.1(4a)6.1(4)SU16.1.4.ES6.1(4)6.1(3b)SU16.1(3b)6.1(3a)6.1.3.ES6.1(3)6.1(2)x5.1(3)x	7.0.2.10000-18
Destination Version	Not Selected8.0(3a)8.0(3)8.0(2c)SU18.0(2c)7.1(5b)SU27.1(5b)7.1(5a)7.1(5)SU1a7.1(5)SU17.1(5)7.1(3b)SU27.1(3b)SU17.1(3b)7.1(3a)SU1a7.1(3a)SU17.1(3a)7.1(3)	7.1.3.32900-4

Release Information

• CUCM 7.1(3b)SU2 was originally released on February 18, 2010.
• The full version number is 7.1.3.32900-4.

• The base ES for this version is 7.1.3.32012-1.

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

• There are no licensing changes or requirements involved with this upgrade.

Cheers!

Rob