CUCM Upgrade from 7.1.5 to 8.5.1 fails

[AlexW75]

Hello Together,

i've tried to do an upgrade from CUCM 7.1.5 to CUCM 8.5.1 (actual downloadable CCO Version).

Problem:

At the end of the upgrade i get the following ErrorMessage:

File	UCSInstall_UCOS_8.5.1.10000-26.sgn.iso
Start Time	Mon Dec 13 16:56:18 CET 2010
Status	Error encountered: This hardware is no longer supported.

But the Serverhardware is listed in the Matrix as supported server:

http://www.cisco.com/en/US/partner/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html

Server hardware: MCS7835I3-K9-CMC2 v02

admin:show tech system hardware
-------------------- show platform system --------------------
Hardware Model: 7835I3
Processors    : 1
Type          :  Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
Speed         : 2000 MHz
Memory        : 4096 MB

With an "old" MCS7835-H2 it's working fine.

Does anybody has the same problem, or knows a solution ?

Many thanks for your help, ideas  and

best regards

Alex

[Jaime Valencia]

Do you meet both the memory and HDD requirements?

MCS  7835

2 GB for -H2, -I2 and  older. For version 8.0(3) through 8.5, 4 GB strongly recommended 4 GB for -I3 and HP  DL380G6

72 GB for -H2, -I2 and  older. For version 8.0(3) through 8.5, 146 GB strongly recommended 146 GB for -I3 and HP  DL380G6

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

[David Hailey]

FWIW, I have found in VMWare testing of 8.5 install/upgrade that the HDD seems to be key...I ultimately had to specify a HDD size of 160GB (146 will work I'm sure, I just didn't want to go thru the hours involved with a failed upgrade).  So my VM setup is 4GB of RAM with 160GB HDD and that does the trick.  CUC is a different story.

Hailey

Please rate helpful posts!

[AlexW75]

The MEM requirements should be fullfilled but with the Harddisk i'm not sure if its a "show" issue.

The datasheet of the server are 2x 146GB harddisks listed.

The RAID settings are:

Logical Drives Information:
==========================
Virtual Disk: 0 (Target Id: 0)
Name:
RAID Level: Primary-1, Secondary-0, RAID Level Qualifier-0
Size:135.972 GB
State: Optimal
Stripe Size: 128 KB
Number Of Drives:2
Span Depth:1
Default Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Access Policy: Read/Write
Disk Cache Policy: Disabled
Encryption Type: None

Physical Disks Information:
==========================
Slot Number: 0
Device Id: 0
Sequence Number: 2
Media Error Count: 0
Other Error Count: 0
Predictive Failure Count: 0
Last Predictive Failure Event Seq Number: 0
PD Type: SAS
Raw Size: 136.731 GB [0x11176d60 Sectors]
Non Coerced Size: 136.231 GB [0x11076d60 Sectors]
Coerced Size: 135.972 GB [0x10ff2000 Sectors]
......

Media Type: Hard Disk Device

Slot Number: 1
Device Id: 1
Sequence Number: 2
Media Error Count: 0
Other Error Count: 0
Predictive Failure Count: 0
Last Predictive Failure Event Seq Number: 0
PD Type: SAS
Raw Size: 136.731 GB [0x11176d60 Sectors]
Non Coerced Size: 136.231 GB [0x11076d60 Sectors]
Coerced Size: 135.972 GB [0x10ff2000 Sectors]
.....
Media Type: Hard Disk Device

HW Platform       : 7835I3
Processors        : 1
Type              : Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
CPU Speed         : 2000
Memory            : 4096 MBytes
Object ID         : 1.3.6.1.4.1.9.1.585
OS Version        : UCOS 4.0.0.0-44

[David Hailey]

Your show output is correct. A 146GB drive is never actually a full 146GB

so what you're seeing is the formatted size of the drive. What errors do

you receive on upgrade? Are they strictly hardware related?

Hailey

Please rate helpful posts!

On 12/13/10 10:34 AM, "awillems"

[AlexW75]

That's all i can see on the Upgrade-page. The upgrade runs through till starting the ciscosec, than this message is shown:

[David Hailey]

That's a tough one to workaround because the installer is pretty literal

when it reads what hardware it likes or doesn't like. I've seen newer

servers that support a version of CCM fail initial install via an older

version on DVD just because the installer hardware check is hardcoded to

look for specific hardware types (7835-I1), etc. Likewise, I've seen the

contrary as well. This is obviously stemming from the Beta trial so here

is what I would suggest - for parity and to see if there is something

buggy in the installer of the FCS 26 release. Back down one rev the the

FCS 10 release (1 level prior to the last FCS post) and see if that

version will install. A lot of work I know but you'll be eliminating the

possibility of a bug or just an install check that is missing your

hardware type.

May end up in the same result - but can't hurt to try.

Hailey

Please rate helpful posts!

On 12/13/10 10:43 AM, "awillems"

[AlexW75]

I agree with you. I've already installed the FCS -23. This works fine and is running.

For me its seems to be an issue with the installer.

Thanks for your help

and best regards

Alex

[martin.schoonbroodt]

Hello people,

I made an upgrade from CUCM 8.0(3) to 8.5(1) - I figured out that the VMware server was not mounting anymore. We are partner of Cisco and we purchased demo licenses for CUCM 8. Should we purchase new licenses for 8.5? Could you please telle me if 8.5 is considered as a major upgrade coming from 8.0?

All I can tell you is that the CUCM after upgrade was not reachable anymore on the network. I had to do a switch back version via CLI to rebuild the CUCM environement. The installation was successfully completed.

Thanks for your feedbacks.

Regards,

Martin

[AlexW75]

Hi Martin,

as far as i know, if you do an upgrade on a CUCM version which  has only a Demolicense , the licfile is no longer valid.

This would also affect the whole CUCM but maybe i'm wrong.

Best regards

Alex

[David Hailey]

I don't believe this is entirely true. I do a lot of work in VMWare so

there may be some differences in behavior on actual hardware (however, I

don't think it would be that drastic)...but I do upgrades on systems with

demo licenses regularly without issue. While you may be having a license

issue in a particular case, I don't think the previous posts can be taken

a blanket statement of truth; however, I've been wrong before. In my

experience, upgrades typically fail due to hardware or other issues...if

you have a licensing issue it is typically seen once an install/upgrade is

complete (e.g., services won't start, licensing errors in logs, etc).

Just my 2 cents.

Hailey

Please rate helpful posts!

On 12/14/10 3:17 AM, "awillems"

[Glenn de Wysockie]

Thanks for the tip on HDD size, I was able to upgrade from 8.0.3 to 8.5.1

After I switched versions to 8.5.1 I could not ping the pub server. The sh network eth0 looked ok (ie link up)

Its not the VM because I switched versions back to 8.0.3 and I could immediately ping the pub.

Anyone else seen this?

I'm running VMware server 2.0.2 on ubuntu 64bit 8.0.4

cheers

Glenn

[David Hailey]

I spent time testing installs of 8.5 apps recently and here's what I found: 8.5 doesn't behave or even install in some cases on VMWare Server which is what I've typically used. I suspect that they now require ESXi and all references to installation of 8.5 in VMWare in the various Cisco docs I've reviewed appear to validate that . Previously, VMWare installs were allowed but not supported but with the advent of UC on UCS and official support for VMWare ESXi I suspect there are some new checks and balances in place. I experienced the same issue as you with CUCM and CUC failed to install or upgrade from previous versions in multiple virtual HW configurations. This was my personal experience so if others have been successful with 8.5 on VMWare Server then I'd love to compare lab specs, configs, etc. However, I personally am going to migrate to ESXi and likely on a C Series UCS server (it's a supported platform which saves me time).

Hailey

Please rate helpful posts!

[PATRICK GESCHWINDNER]

I just upgraded my demo CUCM 8.0.2 running on VMware workstation 6.5 to CUCM 8.5.1. The VM-disk is 80G and I assigned 2GB of RAM. So it seems that the minimum of 72G HDD and 2G RAM is good to satisfy the upgrade procedure. ESXi4 is also not a must for a system operating on demo licenses.

[martin.schoonbroodt]

Hello people,

I've the same behavior than Glenn. In fact, I made an upgrade from 8.0.3 to 8.5.1 on a VMWare workstation 7 client with approximatively 2vCPU 2.8Ghz, 160Gb disk and 6Gb RAM.

The workstation OS is Windows 2008 64bits.

All I can tell you is that when I'm switching the versions, after restart of the server - I can't ping anymore the cucm publisher.

Any idea how to solve this issue? I'd like to test some video features.

Regards,

Martin