You don't need a licensing tool or a consultant to check the core count on a renewal quote. You need an RVTools export, a spreadsheet, and about fifteen minutes, most of which goes to figuring out which hosts belong in the count.
The Three Columns That Matter
Everything comes from the vHost tab. Ignore vInfo for this; it's per-VM, and VM vCPU counts have nothing to do with how the platform is licensed. On vHost you need, for each host:
- # CPU, the number of physical sockets.
- Cores per CPU, physical cores on each socket.
- # Cores, the host total, which you'll use as a sanity check.
Keep Host, Cluster, and Datacenter next to them so you can group the results later. Those are the same columns licensing tools ask for when they ingest an RVTools file (Licenseware's minimum RVTools columns), which is a decent sign you're looking in the right place.
One trap before you start: hyperthreading. Some views in vCenter show logical processors, double the physical core count on most hosts. Licensing counts physical cores. If a host reports 48 cores on two 12-core CPUs, you're looking at threads.
The Formula
Every CPU is licensed at 16 cores or its actual core count, whichever is higher (KB 313548). Add two columns next to the export:
Licensed cores per host = [# CPU] * MAX([Cores per CPU], 16)
Paid for but not present = [Licensed cores per host] - [# Cores]
Total both columns. The first total should land close to the core count on your quote. The second is the part of the quote that buys no capacity.
If the first total doesn't match the quote, don't assume the quote is wrong yet. It usually means the host list is different, which is the next section.
Hosts That Fall Out of the Count
Broadcom's rule covers every ESXi host you intend to license. An RVTools export covers every host one vCenter can see. Those aren't the same list.
- Other vCenters. RVTools exports one vCenter at a time. A DR site, an edge vCenter, or a lab that somebody licensed under the same agreement needs its own export. In VMware Cloud Foundation, the management domain has its own vCenter, so its hosts don't appear in an export from a workload domain vCenter. They still count toward the license, and every VCF instance has a management domain.
- Standalone hosts. An ESXi host managed directly, never joined to vCenter, doesn't appear at all. Branch offices are the usual suspects.
- Hosts in maintenance mode or powered off. They show in the export. Whether they belong in the count depends on whether you intend to run them in the term, which is a decision, not a data question.
- Decommissioned hosts still in inventory. The opposite problem. They inflate your count until someone removes them.
I'd rather find a 17-host discrepancy in a spreadsheet on a Tuesday than in a true-up conversation after the renewal is signed.
What This Count Doesn't Cover
vSAN capacity is a separate count, based on total raw physical storage across all vSAN clusters, and Broadcom's KB warns that the capacity the vSphere Client shows isn't a reliable number for licensing. Use the method in KB 313548 for that one rather than RVTools' datastore figures.
The export also won't tell you anything about edition, term, order minimums, or renewal timing. It tells you what your hardware requires, which is the number every other part of the conversation builds on.
Before You Send the Spreadsheet Anywhere
Did every vCenter under the agreement get exported?
Are standalone hosts listed separately?
Does each host's # Cores equal # CPU times Cores per CPU?
Which hosts are in the count by decision rather than by default?
RVTools exports contain host names, IP addresses, and VM names. Treat the file like any other inventory document and share it on a need-to-know basis. For a single host configuration, the core calculator does the same math without a spreadsheet.