VMware Cloud Community
T3Steve
Enthusiast
Enthusiast
Jump to solution

HP BL465c G5 Problems?

I have 20 BL-465-C G2 servers that have been running rock solid for a year on ESX3.02. Not a single hardware problem with these 20.. EVER.

Our new infrastructure is being built on BL465C G5 w/quad cores and I've had A LOT of hardware failures on the first 7 hosts.

CDW has replaced 2 of the hosts and one is how randomly rebooting. Nothing fruitful is in the logs.. it's as if the power was pulled.

I have 2 other hosts that are now offline due to random reboots. I have not ruled out this new blade enclosure, but wondering if anyone else out there is having problems with the BL465c G5 servers.

Is HP being cheap and building these without even testing them? Are we pushing the vendors to build these faster as most IT shops are doing some sort of virtualization and has realized the beneifts of blades.

- Flyinverted

VCP3|VCP4|VSP|VTSP
0 Kudos
1 Solution

Accepted Solutions
sheetsb
Enthusiast
Enthusiast
Jump to solution

We have had the same problem. Last week HP sent a digital photo of a 4gb memory DIM and asked if we had the same memory. I checked and we did. They sent all new memory for both systems (64gb in all) without explaining why. I have the case numbers for VMware and HP if that would help. It is my interpretation that there may be some bad memory in some of the systems. In the meantime, you might want to compare the memory in your systems to the attached photo.

Bill S.

View solution in original post

0 Kudos
8 Replies
java_cat33
Virtuoso
Virtuoso
Jump to solution

Nope we haven't had any issues - however ESX is running on 480's. HP Firmware maintenance CD has been updated pretty frequently..... is your firmware level current?

0 Kudos
aaron_s_andrews
Contributor
Contributor
Jump to solution

Did you ever get resolution?

0 Kudos
sheetsb
Enthusiast
Enthusiast
Jump to solution

We have had the same problem. Last week HP sent a digital photo of a 4gb memory DIM and asked if we had the same memory. I checked and we did. They sent all new memory for both systems (64gb in all) without explaining why. I have the case numbers for VMware and HP if that would help. It is my interpretation that there may be some bad memory in some of the systems. In the meantime, you might want to compare the memory in your systems to the attached photo.

Bill S.

0 Kudos
Anders_Gregerse
Hot Shot
Hot Shot
Jump to solution

I had some nasty problems (PSOD and cpu may be halted) on the DL385G5 (same processor) and it was due to an older firmware when running update 2, so I would recommend verifying that your are running a correct firmware version. Also did you test memory with memtest before putting the blade into production? vmware have a special SMP edition, that you can request from their support.

0 Kudos
sheetsb
Enthusiast
Enthusiast
Jump to solution

We updated the firmware to the current version suggested by VMware and HP, which was the most current available and the systems still rebooted. VMware suggested running memtest as well but the system rebooted during the run.

Bill S.

0 Kudos
Adam_B
Contributor
Contributor
Jump to solution

We're having exactely the same problems with DL 385 G5's with the 4GB DIMMs in the picture! I'll contact HP and attempt to get all the memory replaced (256GB in total!).

This has been a problem for weeks now so it's good to hopefully have a possible resolution!

0 Kudos
T3Steve
Enthusiast
Enthusiast
Jump to solution

Here's a link to a semi-offical statement about that memory.

http://www.hpfuwu.cn/post/5.html

I definitley had this memory in a few blades that had random rebooting issues and the replacement memory fixed the issue.

VCP3|VCP4|VSP|VTSP
0 Kudos
sheetsb
Enthusiast
Enthusiast
Jump to solution

I've been out the last two weeks and just now have time to respond to some of these messages. HP replaced the memory in the two systems exhibiting the reboot symptom and they have both been up and running for the last two weeks. I still haven't gotten any official response but it looks like the link you posted hits the nail on the head.

Bill S.

0 Kudos