ESXi Hardware Health tab is blank

Products

• VMware vSphere ESXi

Issue/Introduction

In the vSphere Web Client and in the ESXi Host UI, the Hardware Health tab appears blank.

Environment

VMware ESXi 8.0x

VMware ESXi 7.0x

VMware vCenter Server 7.0x

VMware vCenter Server 8.0x

Cause

In the vmkernel.log or the boot log will display similar IPMI failures.

2024-12-13T16:38:29.652Z cpu26:2098152)Loading module ipmi ... 
2024-12-13T16:38:29.653Z cpu26:2098152)Elf: 2119: module ipmi has license VMware 
2024-12-13T16:38:29.658Z cpu26:2098152)ipmi: ACPI IPMI Entry: Address: 0xcc0, System Interface: 0, Map Type: 0 
2024-12-13T16:38:29.658Z cpu26:2098152)ipmi: SMBIOS IPMI Entry: Address: 0xcc0, System Interface: 0, Alignment: 1, Map Type: 0 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: ipmi: KcsRegPort_Init:95: ipmi: Error registering IO resource for KCS data port address at 0xcc0.. Error: Bad address range 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: ipmi: IpmiSysIntKcs_Init:769: ipmi: Failure to inialize KCS registers. Error: Bad address range 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: ipmi: IpmiDriver_Init:219: ipmi: Failed to initialize IPMI system interface. Error: Bad address range 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: ipmi: CreateIpmiDrivers:1246: ipmi: Failed to initialize IPMI driver. Error: Bad address range 
2024-12-13T16:38:29.658Z cpu26:2098152)ipmi: No valid IPMI devices were discovered based upon PCI, ACPI or SMBIOS entries, attempting to discover IPMI devices at default locations 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: ipmi: KcsRegPort_Init:95: ipmi: Error registering IO resource for KCS data port address at 0xca2.. Error: Bad address range 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: ipmi: IpmiSysIntKcs_Init:769: ipmi: Failure to inialize KCS registers. Error: Bad address range 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: ipmi: IpmiDriver_Init:219: ipmi: Failed to initialize IPMI system interface. Error: Bad address range 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: ipmi: CreateIpmiDrivers:1246: ipmi: Failed to initialize IPMI driver. Error: Bad address range 
2024-12-13T16:38:29.658Z cpu26:2098152)IOResource: 405: Registered resource 0x430aac8049b0 from module 0 type 3 @ e4 len=1 
2024-12-13T16:38:29.658Z cpu26:2098152)IOResource: 405: Registered resource 0x430aac804a20 from module 0 type 3 @ e5 len=1 
2024-12-13T16:38:29.658Z cpu26:2098152)IOResource: 405: Registered resource 0x430aac804a90 from module 0 type 3 @ e6 len=1 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: ipmi: SanityCheckRegs:111: ipmi: Reading the BT Control Register produced an invalid value: 0xFF 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: ipmi: IpmiSysIntBt_Init:107: ipmi: Failed to initialize BT registers. Error: Failure 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: ipmi: IpmiDriver_Init:219: ipmi: Failed to initialize IPMI system interface. Error: Failure 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: ipmi: CreateIpmiDrivers:1246: ipmi: Failed to initialize IPMI driver. Error: Failure 
2024-12-13T16:38:29.658Z cpu26:2098152)ipmi: Failed to create any IPMI drivers 
2024-12-13T16:38:29.658Z cpu26:2098152)ipmi failed to load. 
2024-12-13T16:38:29.658Z cpu26:2098152)WARNING: Elf: 3139: Kernel based module load of ipmi failed: Failure  
2024-12-13T16:38:29.659Z cpu36:2097730)Jumpstart plugin restore-configuration-files activated.

 

Another cause for this issue could be outdated BIOS/Firmware on the physical host.

 

Resolution

To resolve this issue

• Update BIOS/Firmware on the physical host
• Ensure IPMI setting is enabled in the BIOS settings on the Physical Host
  • If assistance is required, please contact your Hardware Vendor.