April 2023 Update: Please note that the ipmitool VIB provided here is not compatible with ESXi 8.0. VMware introduced some new security features, architectual changes as well as new VIB packaging requirements in 8.0 that prevent this VIB from working. It will work on ESXi 6.x and 7.x hosts only. For more information, please see the section below titled “ESXi 8.0 Complications, Upgrades and Workarounds”
—
Although ESXi does allow for limited hardware reporting from via IPMI, you may find yourself in a situation where you need to interact with your BMC. A tool that I’ve been using for some time for this purpose is ipmitool, which can be obtained for just about any Linux distribution. The ipmitool utility can be used to pull fan and sensor data, change the BMC network configuration and can even be executed against an IPMI compliant BMC remotely over the network.
Normally, you can just use the web-based IPMI user interface to do a lot of what ipmitool can do, but there are situations where this won’t cut it. A couple of examples would be locking yourself out of the BMC by setting an incorrect VLAN tag or having to modify a setting that isn’t exposed in the UI. My motivation for getting ipmitool running within the ESXi shell was the latter. I needed to be able to modify fan thresholds to keep my slow-spinning fans from triggering critical alarms on my hosts. These fan thresholds aren’t exposed in the web UI and I have to modify them using ipmitool. Normally, to do this I’d have to shut down the host, and boot it up using an install of Debian on a USB stick – a bit of a pain. Why not just run ipmitool from directly within ESXi instead?
A Bit of Background
I first came across this post, which pointed me in the right direction. I couldn’t find a copy of the correct binary, so I just went ahead and compiled a build of ipmitool from source to get a 32-bit Linux executable. Unfortunately, the newest version of ipmitool that ESXi seems to satisfy the library dependencies for is a relatively old 1.8.11 from almost ten years ago. I tried compiling versions 1.8.18 and 1.8.12, but neither would run in ESXi 6.7 U2. Thankfully, 1.8.11 still seems to work fine for most systems and provides the basic functionality required.
Once I had a functional executable, I was able to package it using the really handy ESXi Community Packaging Tools at v-front.de.
File Download
You can download the files here:
ipmitool-esxi-vib-1.8.11-2.zip
Within the zip file, you’ll find the following:
ipmitool-1.8.11-2-offline_bundle.zip - offline bundle for Update Manager or ISO customization. ipmitool-1.8.11-2.x86_64.vib - standalone VIB for CLI installation readme.txt - installation instructions and examples
MD5 checksums:
ipmitool-esxi-vib-1.8.11-2.zip = 444af4ce1dc68418583dba2926093980 ipmitool-1.8.11-2-offline_bundle.zip = 44cb77cc8bd7f969b8e74eb33aec8d71 ipmitool-1.8.11-2.x86_64.vib = 173db5b9f205d9c10d9458ff76d8954b
Installing the VIB
To make installation and removal easier, I packaged up the ipmitool executable as a VIB as well as an offline bundle. To install the VIB, use the following steps:
- If you haven’t already done so, you’ll need to set your software acceptance level to ‘CommunitySupported’. This can be accomplished by running the following command:
[root@esx-e1:~] esxcli software acceptance set --level=CommunitySupported Host acceptance level changed to 'CommunitySupported'.
- Next, copy ipmitool-1.8.11-2.x86_64.vib to the ESXi host. To do this you can SCP file file over using WinSCP or the scp command in Linux. The /tmp location is recommended for this purpose. Don’t forget to enable SSH on the ESXi host or you won’t be able to scp the file over. Alternatively, you can copy the file to a shared datastore that the host has access to using the datastore browser.
- Install ipmitool using the esxcli software vib install -v /tmp/ipmitool-1.8.11-2.x86_64.vib –no-sig-check command:
[root@esx-e1:~] esxcli software vib install -v /tmp/ipmitool-1.8.11-2.x86_64.vib Installation Result Message: Operation finished successfully. Reboot Required: false VIBs Installed: ipmitool_bootbank_ipmitool_1.8.11-2 VIBs Removed: VIBs Skipped:
Note: If the install fails, try to add the –no-sig-check option to bypass the file signature check. It’s not necessary to reboot the host after installation.
- If ipmitool installed successfully, you can run the ipmitool command from the /opt/ipmitool/ directory. If you get the help output returned, it was successful:
[root@esx-e1:~] /opt/ipmitool/ipmitool No command provided! Commands: raw Send a RAW IPMI request and print response i2c Send an I2C Master Write-Read command and print response spd Print SPD info from remote I2C device lan Configure LAN Channels chassis Get chassis status and set power state power Shortcut to chassis power commands event Send pre-defined events to MC mc Management Controller status and global enables sdr Print Sensor Data Repository entries and readings sensor Print detailed sensor information fru Print built-in FRU and scan SDR for FRU locators <snip>
- You can validate the VIB was installed by running the following command:
[root@esx-e1:~] esxcli software vib get -n ipmitool ipmitool_bootbank_ipmitool_1.8.11-2 Name: ipmitool Version: 1.8.11-2 Type: bootbank Vendor: ipmitool Acceptance Level: CommunitySupported Summary: ipmitool 1.8.11 CLI utility Description: Used for managing IPMI baseboard controllers on the host. ReferenceURLs: kb|https://vswitchzero.com/ipmitool-vib Creation Date: 2019-08-20 Depends: Conflicts: Replaces: Provides: Maintenance Mode Required: False Hardware Platforms Required: Live Install Allowed: True Live Remove Allowed: True Stateless Ready: True Overlay: False Tags: ipmi, tool, utility Payloads: ipmitool
The executable will be installed to the /opt/ipmitool/ location on the ESXi host:
[root@esx-e1:~] ls -lha /opt/ipmitool/ipmitool -r-xr-xr-x 1 root root 787.6K Aug 20 16:00 /opt/ipmitool/ipmitool
Also included in the download is an offline bundle .zip file. This file can be used for including the VIB in custom ISOs or for uploading multiple hosts via Update Manager. It is not necessary for installing on an individual host.
Removing ipmitool
Removing ipmitool is simple. Use the esxcli software vib remove command as listed below:
[root@esx-e1:~] esxcli software vib remove -n ipmitool Removal Result Message: Operation finished successfully. Reboot Required: false VIBs Installed: VIBs Removed: ipmitool_bootbank_ipmitool_1.8.11-1 VIBs Skipped:
A host reboot is not required. You can validate that it was removed successfully if the executable is gone:
[root@esx-e1:/tmp] ls -lha /opt/ipmitool/ipmitool ls: /opt/ipmitool/ipmitool: No such file or directory
Using ipmitool
I won’t get too much into using ipmitool as it’s well documented, but a few examples you include the following:
Get an output of all sensor readings:
[root@esx-e1:~] /opt/ipmitool/ipmitool sensor CPU Temp | 34.000 | degrees C | ok | 0.000 | 0.000 | 0.000 | 84.000 | 87.000 | 89.000 System Temp | 36.000 | degrees C | ok | -9.000 | -7.000 | -5.000 | 80.000 | 85.000 | 90.000 Peripheral Temp | 38.000 | degrees C | ok | -9.000 | -7.000 | -5.000 | 80.000 | 85.000 | 90.000 PCH Temp | 52.000 | degrees C | ok | -11.000 | -8.000 | -5.000 | 90.000 | 95.000 | 100.000 P1-DIMMA1 TEMP | 44.000 | degrees C | ok | 1.000 | 2.000 | 4.000 | 80.000 | 85.000 | 90.000 P1-DIMMA2 TEMP | 44.000 | degrees C | ok | 1.000 | 2.000 | 4.000 | 80.000 | 85.000 | 90.000 P1-DIMMB1 TEMP | 43.000 | degrees C | ok | 1.000 | 2.000 | 4.000 | 80.000 | 85.000 | 90.000 P1-DIMMB2 TEMP | 41.000 | degrees C | ok | 1.000 | 2.000 | 4.000 | 80.000 | 85.000 | 90.000 P1-DIMMC1 TEMP | 42.000 | degrees C | ok | 1.000 | 2.000 | 4.000 | 80.000 | 85.000 | 90.000 P1-DIMMC2 TEMP | 41.000 | degrees C | ok | 1.000 | 2.000 | 4.000 | 80.000 | 85.000 | 90.000 P1-DIMMD1 TEMP | 44.000 | degrees C | ok | 1.000 | 2.000 | 4.000 | 80.000 | 85.000 | 90.000 P1-DIMMD2 TEMP | 42.000 | degrees C | ok | 1.000 | 2.000 | 4.000 | 80.000 | 85.000 | 90.000 FAN 1 | 300.000 | RPM | ok | 75.000 | 75.000 | 75.000 | 18975.000 | 19050.000 | 19125.000 FAN 2 | 300.000 | RPM | ok | 75.000 | 75.000 | 75.000 | 18975.000 | 19050.000 | 19125.000 FAN 3 | na | RPM | na | na | na | na | na | na | na FAN 4 | 1050.000 | RPM | ok | 75.000 | 75.000 | 75.000 | 18975.000 | 19050.000 | 19125.000 FAN A | 300.000 | RPM | ok | 75.000 | 75.000 | 75.000 | 18975.000 | 19050.000 | 19125.000 Vcore | 0.880 | Volts | ok | 0.480 | 0.512 | 0.544 | 1.488 | 1.520 | 1.552 3.3VCC | 3.376 | Volts | ok | 2.816 | 2.880 | 2.944 | 3.584 | 3.648 | 3.712 12V | 12.349 | Volts | ok | 10.494 | 10.600 | 10.706 | 13.091 | 13.197 | 13.303 VDIMM | 1.504 | Volts | ok | 1.152 | 1.216 | 1.280 | 1.760 | 1.776 | 1.792 5VCC | 5.088 | Volts | ok | 4.096 | 4.320 | 4.576 | 5.344 | 5.600 | 5.632 CPU VTT | 1.000 | Volts | ok | 0.872 | 0.896 | 0.920 | 1.344 | 1.368 | 1.392 VBAT | 3.440 | Volts | ok | 2.816 | 2.880 | 2.944 | 3.584 | 3.648 | 3.712 VSB | 3.568 | Volts | ok | 3.008 | 3.072 | 3.136 | 3.856 | 3.920 | 3.984 AVCC | 3.376 | Volts | ok | 2.816 | 2.880 | 2.944 | 3.584 | 3.648 | 3.712 Chassis Intru | 0x0 | discrete | 0x0000| na | na | na | na | na | na
Get detailed information for a specific sensor:
[root@esx-e1:~] /opt/ipmitool/ipmitool sensor get "FAN 1" Locating sensor record... Sensor ID : FAN 1 (0x41) Entity ID : 29.1 Sensor Type (Analog) : Fan Sensor Reading : 300 (+/- 0) RPM Status : ok Lower Non-Recoverable : 75.000 Lower Critical : 75.000 Lower Non-Critical : 75.000 Upper Non-Critical : 18975.000 Upper Critical : 19050.000 Upper Non-Recoverable : 19125.000 Assertion Events : Assertions Enabled : lcr- lnr- unc+ ucr+ unr+ Deassertions Enabled : lcr- lnr- unc+ ucr+ unr+
Set all “FAN 1” alarm thresholds to 750RPM:
[root@esx-e1:~] /opt/ipmitool/ipmitool sensor thresh "FAN 1" lower 750 750 750 Locating sensor record 'FAN 1'... Setting sensor "FAN 1" Lower Non-Recoverable threshold to 750.000 Setting sensor "FAN 1" Lower Critical threshold to 750.000 Setting sensor "FAN 1" Lower Non-Critical threshold to 750.000
Get IPMI LAN configuration:
[root@esx-e1:/tmp] /opt/ipmitool/ipmitool lan print Set in Progress : Set Complete Auth Type Support : NONE MD2 MD5 PASSWORD Auth Type Enable : Callback : MD2 MD5 PASSWORD : User : MD2 MD5 PASSWORD : Operator : MD2 MD5 PASSWORD : Admin : MD2 MD5 PASSWORD : OEM : MD2 MD5 PASSWORD IP Address Source : Static Address IP Address : 172.16.1.61 Subnet Mask : 255.255.255.0 MAC Address : 00:25:90:7d:ea:1e SNMP Community String : public IP Header : TTL=0x00 Flags=0x00 Precedence=0x00 TOS=0x00 BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled Default Gateway IP : 0.0.0.0 Default Gateway MAC : 00:00:00:00:00:00 Backup Gateway IP : 0.0.0.0 Backup Gateway MAC : 00:00:00:00:00:00 802.1q VLAN ID : 1 802.1q VLAN Priority : 0 RMCP+ Cipher Suites : 1,2,3,6,7,8,11,12 Cipher Suite Priv Max : aaaaXXaaaXXaaXX : X=Cipher Suite Unused : c=CALLBACK : u=USER : o=OPERATOR : a=ADMIN : O=OEM
Change the BMC’s VLAN ID:
[root@esx-e1:~] /opt/ipmitool/ipmitool lan set 1 vlan id 1
ESXi 8.0 Complications, Upgrades and Workaround
There are several complicating factors that prevent this VIB and the ipmitool binary contained within from working on an ESXi 8.0 host. These include:
- All software VIBs/offline depots require SHA256 checksums. Public/community VIB packaging tools do not support this right now. This will also prevent upgrades to ESXi 8.0 if the VIB was installed in an older version of ESXi (see below).
- The ipmitool binary I compiled for use in this VIB is 32bit and is no longer functional in ESXi 8.0. A compatible 64bit binary is required due to architecture changes.
- By default, ESXi 8.0 will block all attempts to run untracked executables from the command line. This means that simply copying over the ipmitool binary won’t work because an executable must be installed by a VIB/depot to be allowed run.
On a positive note though, ESXi 8.0 fulfills all of the dependancies for the latest version of ipmitool (1.8.18) to work. In ESXi 6/7, the newest working version is 1.8.11. It is possible to compile a compatible 64bit binary of ipmitool, and copy it over to an ESXi 8.0 host, but the security feature called execInstalledOnly would need to be disabled for this to work. This security feature has been around for some time, but it is now enabled by default in ESXi 8.0. You can find more information on this and how to configure it in this write-up and in VMware KB 87802. VMware does not recommend disabling this behavior for security reasons.
You may also encounter an error during upgrade attempts to ESXi 8.0 due to the VIB SHA256 checksum requirements and will need to remove the ipmitool VIB before proceeding. Below is an example error you may receive in this situation:
ERROR: esximage.Errors.ProfileValidationError: In ImageProfile (Updated) ESXi-8.0.0-20513097-standard, the payload(s) in VIB ipmitool_bootbank_ipmitool_1.8.11-2 does not have sha-256 gunzip checksum. This will prevent VIB security verification and secure boot from functioning properly. Please remove this VIB or please check with your vendor for a replacement of this VIB
Before upgrading to ESXi 8.0, you should remove this VIB using the following CLI command:
[root@esx:~] esxcli software vib remove -n ipmitool Removal Result Message: Operation finished successfully. Reboot Required: false VIBs Installed: VIBs Removed: ipmitool_bootbank_ipmitool_1.8.11-2 VIBs Skipped:
I literally spent hours trying to manually create a VIB and depot file, editing metadata, calculating checksums – but my efforts were in vain, unfortunately. Unless new/updated VIB packaging tools become available I will not be able to update this VIB for ESXi 8.0.
Updates
1.8.11-2 – August 20, 2019: If you downloaded the older version that I had originally posted (1.8.11-1) please remove it and install the 1.8.11-2 version posted above instead. I had used /bin/ to store the executable in the older version. Although it worked fine, this causes a lot of unnecessary log messages from VisorFS in vmkernel.log similar to the following:
2019-08-19T18:29:56.215Z cpu14:2150082)WARNING: VisorFS: 1093: Attempt to remove non sticky dir/file from tar mount
The executable is now stored in /opt/ipmitool/ instead, which means this won’t happen. As an added bonus, the –no-sig-check option is no longer required while installing.
1.8.11-1 – August 19, 2019: Original release version.
Many many thanks for this fantastic tutorial !
Hi there,
could you please tell me what’s the tool chain you used to compile for ESXi 6.x? I only found a very outdated tut for ESXi 5.x with CentOS 3.9 32bit.
TIA!
Chris
Thank you so much, lifesaver 🙂
Thank you very much !!! Worked great with ESXI 6.7
ESXI 6.7 U2 on HP Z420, i installed successfully the tool but when i runt it i get this error:
[root@DESKTOP-J4KT0LP:~] /opt/ipmitool/ipmitool sensor
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
Get Device ID command failed
Unable to open SDR for reading
Please help me to solve it. Many Thanks
Hi Mihai, unfortunately the HP Z420 workstation does not have a hardware IPMI module, so that is why ipmitool can’t find /dev/ipmi0. I have the same issue with my Dell T5810 workstations. IPMI functionality is generally only found in servers.
Is ther e a way to map the BMC IPMI ethernet port to the EsXI Physical NICs?
Hi David, no unfortunately not. BMC nics are dedicated for the baseboard management controller and can’t be repurposed as far as I know. This is true for any operating system, not just ESXi. That said, some IPMI systems (like supermicro for example) allow you to use the onboard NICs for IPMI purposes instead of the dedicated NIC. This can save you some switch ports. But the dedicated IPMI nic is stuck serving that purpose only.
Does not seem to work on ESX 7.0 :
Message: Host is not changed.
Reboot Required: false
VIBs Installed:
VIBs Removed:
VIBs Skipped: ipmitool_bootbank_ipmitool_1.8.11-2
are you installing it from /tmp?
Hi Mario, sorry for the slow reply on this. I haven’t tried yet, but I believe the VIB should work on 7.0. It’s definitely broken on 8.0 though. Are there any more details on the screen for why the VIB was skipped? You can also check in /var/log/esxupdate.log for more info. Thanks
Thanks for the feedback. What I ended up doing, is getting the source. Compiling it on Ubuntu 20 and simply copy the resulting executable onto ESX 7 and it worked. To my surprise.
Hi,
please let me know if IPMI (version for ESXi 6.5) will allow to reset the password for the USERID account in IMM2 (Lenovo System X server)?
Thank you in advance for the information.
Hi Chrys, sorry for my slow reply on this. I’ve never tried but the ipmitool syntax should be the same as any other OS (I.e user set password). I’m pretty sure system x systems use the IPMI protocol, so I expect it would work. I know my reply was probably too late to help you but please do let me know if you had any success. Thanks! Mike
Hi Mike,
Yes, I confirm, it worked perfectly.
Thank you :]
Great, thanks for letting me know!
Hi, I seem to get the same error as everyone else. I have installed it but the modules won’t load or don’t exist. I am in root when I am using this command on esxi host. I read some posts where it seems the modules are not loaded so I tried that and it still does not work.
1) Error below when Input is : /opt/ipmitool/ipmitool raw 0x32 0x66
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
Unable to send RAW command (channel=0x0 netfn=0x32 lun=0x0 cmd=0x66)
2) Trying to load the drivers gives me the error below.
[root@alu-esxi04:~] vmkload_mod ipmi_si_drv
vmkmod: VMKModCheckMod: Access to file /usr/lib/vmware/vmkmod/ipmi_si_drv failed: Not found
vmkmod: VMKMod_Load: VMKMod_ComputeModPath(ipmi_si_drv) failed: Not found
Cannot load module ipmi_si_drv: not found
[root@alu-esxi04:~] vmkload_mod ipmi_devintf
vmkmod: VMKModCheckMod: Access to file /usr/lib/vmware/vmkmod/ipmi_devintf failed: Not found
vmkmod: VMKMod_Load: VMKMod_ComputeModPath(ipmi_devintf) failed: Not found
Cannot load module ipmi_devintf: not found
3) Then tried to look in the folder and I don’t see those drivers but only ipmi. Trying to load the vmkmod ipmi gave an error.
[root@alu-esxi04:/usr/lib/vmware/vmkmod] vmkload_mod ipmi
vmkmod: VMKModLoad: VMKernel_LoadKernelModule(ipmi): Failure
Cannot load module ipmi: Failure
Please help as I am trying to reset the bmc password and have been unsuccessful using this tool. The only other option for me is to flash the bmc with the new firmware.
Thank you!
Hi Bishwarup, what hardware platform are you trying to run this on? I could be wrong, but the errors seem to imply that this host doesn’t support IPMI. Some OEM BMCs are proprietary if I’m not mistaken.
Is there ipmitool available for Esxi-7.0? Could you share the link to download for Esxi-7.0?
Hi Ravat, I haven’t had a chance to test this VIB on 7.0 or 8.0 yet, but I’m pretty sure it doesn’t work on 8.0. I’ll be testing it out again soon and making some updates. Will share any new versions on this page.
Hi – Many thanks for the awesome vib – been using this for some time on my ESXi 7 hosts.
I attempted an upgrade from ESXi 7 to 8 last night and received the following error, preventing the upgrade.
esxupdate: 2368415: root: ERROR: esximage.Errors.ProfileValidationError: In ImageProfile (Updated) ESXi-8.0.0-20513097-standard, the payload(s) in VIB ipmitool_bootbank_ipmitool_1.8.11-2 does not have sha-256 gunzip checksum. This will prevent VIB security verification and secure boot from functioning properly. Please remove this VIB or please check with your vendor for a replacement of this VIB
Looking at the manifest file I can see gunzip is sha-1 encrypted
checksum-type=”sha-1″ verify-process=”gunzip”>f33e8f8dfbd695c686b34f42347d9fb6b5d5f98f
How feasible is repacking the vib with the community tool to support sha-256 gunzip encryption?
Excuse my ignorance – first time having a look at custom vibs!
Kind Regards
Hi Chris,
Glad to hear the VIB has been useful for you! I haven’t had a chance to use vSphere 8 much but will try to have a look and see if it can be repackaged. I imagine there were some changes in requirements for the software packaging for 8.0. Hopefully the VIB packaging tool I used has been updated for vSphere 8. I’ll take a look and keep you posted.
Hi all,
how to install ipmitools on ESXi 8.0? When trying it, I get the following error:
[ProfileValidationError]
In ImageProfile (Updated) ESXi-7.0U3-18644231-standard, the payload(s) in VIB ipmitool_bootbank_ipmitool_1.8.11-2 does not have sha-256 gunzip checksum. This will prevent VIB security verification and secure boot from functioning properly. Please remove this VIB or please check with your vendor for a replacement of this VIB
Please refer to the log file for more details.
I had to unistall this VIB before updating to ESXi 8.0. Now I want to install it again. The parameters –no-sig-check and -f don’t work.
Thank You
Hi Stefan, it appears that there is an issue with the checksum verification of this VIB in vSphere 8. I will need to repackage it for compatibility. Will update this page when I get it fixed. Thanks.
Hi Mike,
thank you for your quick reply. Would it be possible to repackage it with the ipmitool 1.8.19 which is the latest release? This would be great!
For now I’ve found an option to do this with an Windows version of the ipmitools from https://www.dannynieuwenhuis.nl/download-windows-ipmitool-exe-version-1-8-19/. You can connect remotely to the IPMI board an set thresholds of fans for example.
Kind Regards
Hi Mike,
thank you for your quick reply. Would it be possible for you to update the version of ipmitools to the latest release 1.8.19 when repackaging it? This would be really great.
For now I use a Windows compilation of version 1.8.19 from https://www.dannynieuwenhuis.nl/download-windows-ipmitool-exe-version-1-8-19/. So I can connect from a Windows system remotely to the IPMI to configure the FAN thresholds fpr example.
Kind Regards
Thanks I could install ipmitool on supermicro server. I want to use it to detect correctable memory errors. I tried this command
/opt/ipmitool/ipmitool -v sel list
SEL Record ID : 0008
Record Type : 02
Timestamp : 12/01/2022 01:43:01
Generator ID : 0021
EvM Revision : 04
Sensor Type : Memory
Sensor Number : 53
Event Type : Sensor-specific Discrete
Event Direction : Assertion Event
Event Data : 00ffff
Description : Correctable ECC
But this doesn’t tell which DIMM slot the error occured like DIMMA1 etc.
How can i get the exact location of where the correctable ECC occured?
Thank you
Dee
This was a big help for me. Worked great on esxi 7.0. Hoping that an 8.0 will come at some point
Also, I created the following install script to help me remember the steps.
#!/bin/sh
#https://vswitchzero.com/ipmitool-vib/
VIB=IPMICFG_1.34.0_build.220906_ESXi.vib
esxcli software acceptance set –level=CommunitySupported
cp ${VIB} /tmp
esxcli software vib install -v /tmp/${VIB} –no-sig-check -f
Hi, under vsphere 8.0 says me:
“[ProfileValidationError]
In ImageProfile (Updated) ESXi-8.0.0-20513097-standard, the payload(s) in VIB ipmitool_bootbank_ipmitool_1.8.11-2 does not have sha-256 gunzip checksum. This will prevent VIB security verification and secure boot from functioning properly. Please remove this VIB or please check with your vendor for a replacement of this VIB”
its any chance get work on 8.0 ?
The 8.0 workaround – moving ESXi7 ipmitool binary over – didn’t work for me.
[root@lu0570v8:~] /opt/ipmitool/ipmitool
-sh: /opt/ipmitool/ipmitool: Operation not permitted