Skip to contentSkip to conversation

IPMI sensor names with VMware ESXi

DISCUSSION Paul Fertser 1 participant 2 messages Jul 25, 2022 – Aug 19, 2022

lore
Share & tools
lore
#0 lore raw

Hello,

We're facing what might be an interoperability issue between OpenBMC sensors exposed via IPMI to the host system and VMware ESXi (version 7.0u2).

The official document[0] states "All hardware sensors that conform to the IPMI standard are collected. Third parties do not need to add software providers to take advantage of this functionality."

And indeed they are collected but the web-interface, WBEM via https and "esxcli hardware ipmi sdr list" all give "Unspecified 1" for all the IPMI sensors "captions". At the same time "/opt/ipmitool/ipmitool sdr list" from https://vswitchzero.com/ipmitool-vib/ shows all the names properly.

When the M.2 SSD with this system is removed from our server and installed into a very similar Wiwynn Tioga Pass board running AMI MegaRAC and their UEFI implementation, all the sensor names appear without any tweaks.

I'm having hard time trying to obtain any related documentation or source code, can't for the life of me find any clue about their CIM configuration. Is it using some undocumented SMBIOS entries (I see a bunch (117) of "type 192, 23 bytes" but no idea if that's related)? Or probably some ACPI tables? Or something specific it doesn't like about OpenBMC's IPMI implementation?

Surely it's not the first time OpenBMC is used with ESXi so please share your hints.

[0] http://www.vmware.com/files/pdf/techpaper/hwhm41_technote.pdf

Signature · 2 lines
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:[email protected]
#1 lore raw

Re: IPMI sensor names with VMware ESXi. Found the answers.

Hello,

I've figured out the issues and the fixes, so answering myself here to get it recorded in the mailing list thread and indexed by the search engines.

Quoted 3 lines · Paul Fertser

We're facing what might be an interoperability issue between OpenBMC sensors exposed via IPMI to the host system and VMware ESXi (version 7.0u2).

...

Quoted 1 line

"Unspecified 1" for all the IPMI sensors "captions".

Long story short, I asked ever-helpful neotic on #vmware IRC channel and he suggested to take a look at libipmi-4.5 (OpenSolaris heritage) from their "open source" bundle. Writing a test app based on that reproduced the problem, so debugging became straightforward.

In my testing the "Unspecified" part of the name was the textual representation of Entity Id (0 by default), 1 was the Entity Instance. I documented ways to make it specified with intel-ipmi-oem (or the new dbus-sdr phosphor-host-ipmid support) in another mail[0]. When using the static yaml sensors description for phosphor-host-ipmid "entityID" and "entityInstance" keys need to be set for each sensor individually.

The actual names are ignored as they're transmitted using what IPMI specification calls a "Unicode" encoding, in this case libipmi returns an empty string. I fixed [1] it for intel-ipmi-oem by using "8-bit ASCII + Latin 1" which makes the library copy strings verbatim. If this is approved I'll send the corresponding change to phosphor-host-ipmid (to fix both dbus-sdr and static sensorhandler).

[0] https://lists.ozlabs.org/pipermail/openbmc/2022-August/031723.html
[1] https://gerrit.openbmc.org/c/openbmc/intel-ipmi-oem/+/56626

Signature · 2 lines
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:[email protected]