CUCM Patch Install to 10.5.1.11901-1 Fails

[dacole]

I have a cluster running 10.5.1.11901-1. Just tried to install a new subscriber, booting from 10.5.1.10000-9 and doing patch to 10.5.1.11901-1.

Failed with patch on DVD and also via SFTP.

Upgrade of original servers in cluster from 10.5.1.10000-9 to 10.5.1.11901-1 worked fine.

Error shown on console is:-

Critical Error

.......

"usr/local/cm/script/cm-dbms-install install

PostInstall 10.5.1.11901-1 10.5.1.11901-1 /usr/local/cm/usr/local/cm /common/log/install/capture.txt " failed (1)

Any ideas? I have repeated this in my lab with the same error.

Thanks,

Dave

[Rob Huffman · Accepted solution]

Hi Dave,

I believe you are seeing this bug;

CUCM 10.5 cannot be installed using upgrade patch method

CSCup36072

Symptom:
When doing a fresh install of a Call Manager node, there is an option to use an upgrade patch option.

For CUCM 10.5, this approach cannot be used. Not even by using the bootable image for 10.0 and upgrade file for 10.5

Conditions:
Installing CUCM 10.5 with bootable image of a lower version and upgrade file of CUCM 10.5

Workaround:
None -> Use Bootable image for CUCM 10.5 itself

Last Modified:

Oct 9,2014

Status:

Fixed

Severity:

3 Moderate

Product:

Cisco Unified Communications Manager (CallManager)

Support Cases:

6

Cheers!

Rob 

[dacole]

Thanks Rob,

Not sure what I do with the workaround though. 2 live servers upgraded already. I assume I can't run the install on the bootable and then upgrade? I need the Subscriber installed as 10.5.1.11901-1 in order to join the cluster?

Dave

[Brian Schultz]

Were you able to find a workaround to this?  I'm running into the exact same issue of trying to add a subscriber to a system already installed on 10.5.1.11901-1.

[dacole]

Brian, as I had only just upgraded, I was able to switch back to the 9.1 partition, add the new Subscriber then upgrade the extended cluster. Not ideal. My problem was the support contract had not been processed so I could not raise a TAC case at that time.

The workaround in the bug that Rob identified didn't seem much use but I think maybe I mis-understood it. Maybe TAC can supply a bootable 10.5.1.11901-1 image, in which case that gets around the issue (could always make a bootable 10.5.1.11901-1 iso using the boot sector from the 10.5.1.10000-9 but I try to keep this for the lab, haven't tried it with any 10 images yet).

I may raise a TAC case now just to see if I can get this bootable image, as if my customer lost a server, they could not rebuild.

[Brian Schultz]

Thanks.  I had to do the same thing.  Switched versions back to 10.5.1.10000 on the publisher in order to join the subscriber.  Then I was able to upgrade them both to 10.5.1.11901-1. 

[Joshua Learn]

We're requesting a bootable image from TAC for CUCM 10.5.1.11901-1 as a workaround.  Thanks for the information.