ESXi CPU sockets are incorrectly reported in vCenter UI, Host web client and CLI

Products

• VMware vSphere ESX 7.x
• VMware vSphere ESX 8.x

Issue/Introduction

The CPU socket configuration at the ESXi level does not align with the physical hardware details. 

For Example, in a DELL server :

- iDRAC reports 2 physical sockets. 
- However, ESXi reports 4 physical sockets 

CLI -

4 sockets and inconsistent core configuration - 

 

vCenter UI -

In boot log,

CpuTopology will not report multiple NUMA nodes per package,

└─$ less boot | grep -i cputopology
0:00:00:03.273 cpu0:2097152)CpuTopology: 609: Multiple LLCs per NUMA node detected
0:00:00:03.273 cpu0:2097152)CpuTopology: 614: Multiple LLCs per package detected 


Expected outcome in boot log if there are 2 Physical sockets, 

└─$ less boot | grep -i cputopology
0:00:00:00.992 cpu0:2097152)CpuTopology: 572: Detected <6, 85> has 2 NUMA nodes per package
0:00:00:01.314 cpu0:2097152)CpuTopology: 614: Multiple LLCs per package detected

Environment

ESXi 7.x
ESXi 8.x

Cause

The mismatch may occur because the SRAT table reports inconsistent NUMA node sizes.

Resolution

Kindly contact the Hardware Vendor to review the SRAT table.