Blade Enclosure Serial Number is Displayed Instead of Server Blade Serial Number - VMware ESXi 4.1

[rtuell]

VMWare  replied to issue with the BL460 G1 machines reporting the serial number of the enclosure instead of the blade itself, they said that it is an issue with HP that they can’t fix it.

"HP identifies their chassis at Type 17 (Rack Chassis) but it should be identified as Type 3 (Blade Chassis)”

has anyone come across this problem and know how to correct it?

[Jags_21]

Hi,

I suspect this could be an issue either of them vcenter itself or CIM providers

Point 1:

Though your servers running on ESXi 4.1 433742 which i believe is a patch update.

In ESXi 4.1 U1 release notes you can find the below statement, but this is for the IBM and Dell servers, assuming the same is effecting to the HP Blade servers as well.

CIM and API

• vCenter Server incorrectly reports the service tag of the blade chassis
  For blade servers that are running ESX, vCenter Server incorrectly reports the service tag of the blade chassis instead of that for the blade. On a Dell or IBM blade server that is managed by vCenter Server, the service tag number is listed in the System section of the vCenter Server under vCenter Server > Configuration tab underprocessors. This issue occurs due to the incorrect value for the SerialNumber property of the Fixed CIM OMC_Chassis instance. The issue is resolved in this release.

Click here for ESXi 4.1 U1 release notes.

Try updating to a later version and see if it gets resolved.

Point 2:

If you check the screenshot-1 Asset Tag shown as unknown, this could be in Server BIOS the Asset Tag is not properly entered or if there was an server board replacement, Asset Tag has to be re-entered.

Also on the ESXi 4.1 host if the CIM providers is native try installing the latest version of HP offline bundle and see if the HP WBEM provides proper information.

Click here for the latest HP Offline Bundle for ESXi 4.1 U1.

Click here for the latest HP Offline Bundle for ESXi 4.1 U2. (Use this version in case if you are updating the host to ESXi 4.1 U2)

Thanks,

-----------

If you like this post please click on the "KUDOS White Star" on the left pane of this post.