Viola! The vCenter Hardware Status is somehow pulling in the chassis serial number instead of the server blade serial number!! I tested this theory on a couple of other Chassis/Blade combinations and it is consistent. So that tells me that VMware vCenter web client is making an IPMI query of CIM data but somehow pulling in the WRONG serial number!! But where is it getting it? On a hunch I looked at the Cisco UCS Chassis where the blade server resides. PowerCLI C:\temp> $esxCLI = Get-esxCLI -VMHost $vmHost Devices found to be covered by an active service contract are indicated by a checkmark icon () in the Covered column. After entering valid serial numbers, the coverage status of each item is checked. Now I get the CORRECT serial number! PowerCLI The Cisco Device Coverage Checker tool allows you to determine the current contract status of your Cisco devices. I looked at the example script you linked to and pulled out the relevant lines of code. > vSphere ESXi 6.5.0 Hardware Sensors "( )" I actually found that same community forum question, but as above, the answer does not apply.īut I did I try the esxiCLI you recommended. > "( )" seems to be the same information as above, at least I don't see anything that helps my situation VMware KB article 2151238 does not address this. ![]() I am getting data populated to the Hardware Status tab, but it contains INVALID information - the WRONG serial number. ![]() BUT! In fact the description is one of the new method of obtaining IPMI data in the Hardware Status tab. > VMware Knowledge Base "( )" - shows this issue is resolved in VMware vCenter Server 6.5 U2 Ref: VMware vCenter Server 6.5 Update 2 Release Notes "( )" and we are running 6.5.0 Update 2c (Build 9451637) which should have this particular issue resolved. Thanks for replying Diego, but those links do not apply in our situation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |