Upgrade CUCM from 10.5 to 11.x

[martin01]

Hi all 

i tried to upgrade CUCM from 10.5 to 11.x but i have this error

/usr/local/cm/script/cm-dbl-install L2 PostInstall 11.0.1.21900-11 10.5.1.10000-7 /usr/local/cm/ /partB/usr/local/cm/ /common/log/install/capture.txt failed (1)

failed to upgrade infrastructure_post components

/usr/local/bin/base_scripts/appmanager.sh -upgrade -basepath /common/rpm-archive/11.0.1.21900-11 -logfile /common/log/install/install_log_2016-02-03.09.25.05.log -resultfile /common/log/install/upgrade-results.xml failed (1)

you can also see in the attached file the installation log 

Please can you help me for this issue 

Thank

[Aman Soi]

Hi Martin,

From the logs I can see. Are u using RST or UNRST 10.x version and trying to upgrade to which RST or UNRST 11.x?

02/03/2016 10:06:00 upgrade_manager.sh|Not a restricted to unrestricted upgrade|<LVL::Info>

02/03/2016 10:06:00 upgrade_manager.sh|Invalidate upgrade

regds,

aman

[martin01]

Hi Aman 

hi tried to make a new upgrade from 10.5 to 11.x without change the file  and now i have this error message.

but when on the Show/software menu i see 

Partition Versions

Active Version 10.5.1.10000-7
Inactive Version 11.0.1.21900-11

see in the file attached

[Deepak Rawat]

Do you have ciscocm.version3-keys.cop.sgn file installed on your CUCM server. Post the output of show status

Check below:

http://docwiki.cisco.com/wiki/CUCM_Upgrades_and_Migrations_FAQ#What_COP_files_do_I_need.3F.3F

Regards

Deepak

[Aman Soi]

HI Martin,

Did u check the MD5 before uploading the iso? It should match as below

57bdeb7c3b540551892726466b33ae29 is the MD5 checksum

If yes, I was just going through bugs which of course is not related to your CUCM version but have a look. Also, suggest opening TAC case.

Install proceeds despite checksum failure

CSCtk08248

Description

Symptom:

Install continues and says it completes successfully despite a checksum failure. This is an issue for 7.1(5) through 8.0(3) only. It was resolved in 8.5.

Conditions:

This can occur if the next event comes in to soon with a success code before the system can detect the checksum failure.

Workaround:

Check the install logs for a similar message :

09/17/2010 15:35:15 upgrade_manager.sh|hpsum_help_en.htm failed checksum|<:ERROR>

If this message is present, verify the install media and perform the install again

[martin01]

hi