HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

C3000 "device identification data error"

 
Luca
Advisor

C3000 "device identification data error"

Recently a SB40c associated with a BL460c failed completely - it just died. The OA reported Management controller not responding. Anyhow HP sent us a logic board with backplane for the SB40 and we replaced it. Now the OA reports management controller OK but "device identification data error" and does not power on the blade. We tried reseating the SB40c, tried plugging it in another bay alone and with the server, rebooting the OA, power cycling the whole c3000, but nothing.
What could be the problem? Could it be another defective logic board?
13 REPLIES
Steven Clementi
Honored Contributor

Re: C3000 "device identification data error"

What firmware is the OA at?


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)
Luca
Advisor

Re: C3000 "device identification data error"

I forgot to mention it's the latest (3.21). I also tried reflashing the same firmware version.
Bhavin-Desai
Advisor

Re: C3000 "device identification data error"

What is the firmware on the SB40c and the controller in it ?...
Luca
Advisor

Re: C3000 "device identification data error"

This is the information we could retrieve from the OA:

Powered Off
Status Degraded

Device Information Blade Type Storage Blade
Manufacturer [Unknown]
Product Name [Unknown]
Part Number [Unknown]
System Board Spare Part Number [Unknown]
Serial Number [Unknown]
ROM Version 1.20

The controller is a P400 double channel but we don't know the firmware on the HBA as we cannot access it.

Additionally, an "update show" from the CLI does not list the blade so a rom upgrade is not possible.
gregersenj
Honored Contributor

Re: C3000 "device identification data error"

Does the server power on, without the SB40c?

If so.
Remove server
Remove SB.
Waite 30 secs.
Insert SB.
Waite a few minutes.
Insert server.

Wich bays do you use?

BR
/jag
gregersenj
Honored Contributor

Re: C3000 "device identification data error"

Could could try to upgrade the server BIOS / FW. If not allready on latest FW.

BR
/jag
Luca
Advisor

Re: C3000 "device identification data error"

It is not a server problem. The server works fine with or without the SB40c inserted. It has always worked fine - bay 1 the BL460 and in bay 2 the SB40c.
The OA reports the same error if we install it in bay 6, with or without a server inserted.

We did all the possible tests, powering off everything, only server in bay 1, removing server in bay 1 and reinserting and vice versa. The "device identification data error" from what I recall and reading other information about the c3000 is a rather problematic error, possibly related to the logic board and P400 firmware revision not recognizing it properly, or the logic board ROM version is too old for the P400 firmware for ex, but this is just my speculation.

Unfortunately, the OA does NOT list the SB40 using CLI so I cannot issue any update on the logic board ROM version. We also have an ultrium tape blade which gets listed fine, so the midplane seems fine as the rest of the infrastructure is ok.

I suspect it being a logic board problem or an incomaptibility between the revision installed and the HBA which we migrated from the old logic board.
Luca
Advisor

Re: C3000 "device identification data error"

Further insight can be found here:

http://h30499.www3.hp.com/t5/HP-BladeSystem-Server-Blades/C7000-amp-BL460-quot-Device-Identification-Data-Error-quot/td-p/1153544

It seems that there is a checksum error in the SB40c FRU (logic board) - something doesn't add up.
Luca
Advisor

Re: C3000 "device identification data error"

We finally got another mainboard logic and additionally another P400 replacement sent to us.
We tried replacing first the P400, but nothing changed.
Once we replaced the logic mainboard, the SB40c was correctly recognized and partnered with the adjacent server as usual and booted correctly. All data was intact.

So it turned out to be a defective logic/mainboard replacement as suspected.

Case closed.
Luca
Advisor

Re: C3000 "device identification data error"

Replaced (again) the SB40c main board as first replacement one was defective resulting in the OA reporting "device identification error".
gregersenj
Honored Contributor

Re: C3000 "device identification data error"

Greate :)

BR
/jag
Proliant VMS San Mgrs
Frequent Advisor

Re: C3000 "device identification data error"

You did not state if you have an HP maintenance contract, or this is warranty.

With the outsourcing of spare parts to UPS logistics, I have noticed that the quality of parts delivered to customer sites has suffered.

You might want to record the serial number of any board which is removed as suspect, or known defective; and make sure the same board doesn't come back again.

I have seen spare parts packages shipped from the depot without "defective" return labels...

Just my own private opinion. Your mileage may vary.
Problems Solved
Luca
Advisor

Re: C3000 "device identification data error"

Yes, we were fortunately under maintenance contract. I am aware that the replacemenet parts can "resurface" as not checked by logistics - we always stick the defective sticker on the box, but then how do we know what happens after, if the device gets checked properly or not. All I can say is that the replacement parts we receive look perfectly new and not used in any way. I suspect this problem to be an unsuccessful programming of the mainboard flash through the JTAG port - maybe the checksum values were not written correctly as the ROM worked. This defective board to me looked like an "origin" defect (manufacturing), not a repair problem. I point my finger to Quality Control here.