[cisco-voip] CUCM 6.1(5) upgrade fail

[Ryan Ratliff]

Most of the new versions are pretty good refusing to run the upgrade if it's on unsupported hardware.

Other common failures are caused by a DRS restore where user locales are not reinstalled post-restore but the error Dana provided seems to indicate it is failing at reading the upgrade source.

-Ryan

On Jul 8, 2010, at 11:00 AM, Matthew Saskin wrote:

Have to ask the semi-obvious - are they on hardware that's supported by 6.1(5)?  Don't assume that just because it works with 6.1(3) it will work with later versions.  There are drastically different hardware requirements for 6.1(5) and a few other recent versions than for any previous version of CUCM.

Matthew Saskin
msaskin at gmail.com
203-253-9571

July 18, 2010 - 1500m swim (in the hudson), 40k bike, 10k run
Please support the Leukemia & Lyphoma Society
http://pages.teamintraining.org/nyc/nyctri10/msaskin


On Thu, Jul 8, 2010 at 8:00 AM, Dana Tong <Dana.Tong at ivision.com.au> wrote:
Hi all,

I have a customer who has a 6.1(3)a cluster. They are wanting to upgrade to 6.1(5) because they are experiencing some bugs in 6.1.3.

6.1(3)a is a supported direct upgrade to 6.1(5) per the CUCM upgrade matrix however the upgrade is failing.
I've tried the official Cisco media, and the .sgn.iso file direct from CCO. I've also tried a 6.1(4)a ISO from CCO.
Both of these files have a positive check for MD5 hash. I've also used the 6.1(5) media previously for another customer and had successful upgrades.

This particular upgrade was a fresh install with a DMA import from CCM 4.
There is currently no inactive partition. There are no special options (locale, IDP) installed on this cluster.
The upgrade processes for around 12-13 minutes and appears to setup the inactive partition but fails the upgrade reporting "an error occured while accessing the upgrade file".

I'm guessing it's going to be something specific to this cluster but I can't be certain. I'm waiting for the TAC engineer to decypher the upgrade logs but would value any other ideas?

Thanks
Dana

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100708/bb739d13/attachment.html>