Missing RAC details

[vPinballas]

Hi guys

Found that after upgrading our hosts from ESXi 6.0 build 4600944 to ESXi 6.5 build 7388607 and running "get-esxinventory" we no longer get any "RAC IP, RAC MAC or RAC Firmware" details in the export, the collection runs without issues and just leave the fields blank.

vDocumentation version 2.4.0

Any ideas here?

Thanks

Johan

[stalmon]

What Hardware vendor do you use?

If you have DELL Servers:

DELL|EMC discontinued the automated installation of the iDRAC service module for ESXi 6.5 (see http://www.dell.com/support/manuals/de/de/debsdt1/vmware-esxi-6.5.x/esxi6.5.x_ig_pub/important-information-for-the-dell-emc-customized-esxi-image?guid=guid-c56c0861-2580-4541-a586-cce63b5be011&lang=en-us)

To get iDRAC information through your ESXi host you have to install the iDRAC service module (http://www.dell.com/support/home/us/en/19/Products/software/ent_sys_mgmt/ent_sys_mgmt_idrac_svc_module)

[arielsanchezmora]

Thanks @stalmon , I didn't know that! @edmsanchez check this out :)

There's a general bug with CIM in 6.5 that we told @kmruddy about - he says it may get fixed soon. We'll try to continue using the old method, which is vendor agnostic

[edmsanchez]

2 important changes on 6.5 1) https://kb.vmware.com/s/article/2148910 - WBEM services are not started/disabled by deafult 2) PowerCLI CIM session Ticket fails to authenticate with ESXi 6.5 WBEM

if you have upgraded to 6.5 then #1 is not a problem, but if its a new install then you will need to enabel that first. for #2 is what @kmruddy had the bug opened for; I have a workaround for that... and its that you use the root credentials to query for iDRAC/iLO IPs. Given that all your hosts have the same root password then this would work - this is what I use today.

if you see this would benefit you, then I could add the workaround and publish it, it will prompt for root credentials using get-credential and those will be relayed securely... sort of the same way get-esxspeculative execution is done today.

[Pinballas]

Hi Edgar

Sorry i missed your reply earlier. All our hosts will be classified as upgrades so #1 is good to go, for #2 it would be of great help if you can share the workaround code. Thank you in advance

[arielsanchezmora]

I know this was fixed in 6.7 and later 6.5's - please open up a new issue with your host versions if the issue remains, since we know it's not our code that's causing this.