Licensing IBM software on VMware: the cluster capacity rule.

Why the cluster, not the host.

IBM sub-capacity licensing lets you license only the virtual cores running IBM software rather than the full physical host. On VMware that benefit comes with a condition: because vMotion and DRS can move a virtual machine to any host in the cluster, IBM treats the eligible count as the capacity the software can reach. Unless you constrain where the workload can run, that means every core in the cluster the VM is able to migrate to, not just the cores it happens to be using today.

The arithmetic is unforgiving. A WebSphere instance using 4 of 32 cores on one host is 480 PVU under a clean sub-capacity claim. If that VM can migrate freely across a four host cluster of identical 32 core machines, the reachable capacity is 128 cores, and a denied or unbounded claim can be charged against all of it. The difference between a contained workload and an unbounded one is an order of magnitude.

How auditors read the environment.

An auditor inspecting a VMware estate looks at three things: which clusters the IBM workloads live in, whether VM placement is actually restricted, and whether ILMT was deployed and reporting against the right scope. Where DRS is set to fully automated and no host affinity rules exist, IBM will argue the workload reaches the whole cluster. Where ILMT was missing or its VM Manager connection was not configured, IBM defaults to full capacity for the period, which on a large cluster is the worst possible outcome.

• Confirm an eligible tool such as ILMT was deployed within 90 days of first eligible deployment
• Show continuous operation with quarterly reports retained for two years
• Document VM Manager connections so ILMT sees the true virtual topology
• Record any host affinity or pinning rules that bound where the workload can run

Where the buyer side defense lives.

Most VMware findings are not won by arguing the rule. They are won by proving the scope. If host affinity rules pinned the workload to a defined subset of the cluster, the reachable capacity is that subset, not the whole estate. If ILMT data shows the eligible conditions were met for a given quarter, the sub-capacity position is reinstated for that quarter rather than charged at full capacity. The work is to reconstruct, period by period, what the environment actually permitted and what the tool actually recorded.

What this means under audit.

The cluster capacity rule is the single largest swing factor in a VMware audit, which is why it sits at the center of the Reconcile and Challenge steps of Contain, Reconcile, Challenge, Settle. Before any number is discussed, the question is whether IBM has scoped the claim to the capacity the workload could truly reach, and whether the sub-capacity conditions were met for each period in the lookback. Answered on the facts you control, a cluster-wide claim frequently collapses back to the contained footprint.