White Paper · IBM

IBM ILMT and Sub Capacity Licensing Guide

The buyer side framework for IBM License Metric Tool deployment and sub capacity compliance. Defensible licensing across virtualized estates.

Portrait of Morten Andersen
Written byMorten AndersenCo Founder · ex IBM, ex Oracle
Read Time20 Minutes
Last UpdatedMay 2026

Now that you have the framework

Apply it to your IBM situation.

25 minute call with our IBM practice lead. We will walk through your specific renewal, audit, or contract and tell you what we would do next. No follow up sales pressure unless you ask for one.

HomeIBM HubWhite PapersIBM ILMT and Sub Capacity Licensing Guide
The Short Version

If you read nothing else

Bottom Line

IBM sub capacity licensing requires ILMT compliance. Without compliance, sub capacity reverts to full host counting. The 90 day cure period exists for documented gaps; few customers know it exists or use it.

Key Takeaways

Five conclusions

ILMT is the foundational requirement. Without it, sub capacity rights revert to full host counting on virtualized infrastructure.
SCRT generates the quarterly compliance report. Two year retention is contractually required; many customers do not retain.
Sub capacity rules vary by hypervisor. VMware, PowerVM, Nutanix, KVM each have distinct configuration requirements.
Cure period mechanics protect against gaps. IBM permits 90 day cure for documented ILMT failures; customers who know the rule use it.
Manual measurement substitutes where ILMT cannot run. Air gapped environments, legacy systems, specific licensing categories.
Recommendations by Role

What to do this quarter

CIO
  1. Treat ILMT compliance as ongoing, not project based.
  2. Build readiness into the FinOps cadence.
  3. Engage independent advisory before audit notices arrive.
Software Asset Manager
  1. Maintain ILMT data current at all times.
  2. Generate SCRT quarterly with two year retention.
  3. Document sub capacity configuration per platform.
Infrastructure Director
  1. Configure VMware affinity rules for sub capacity.
  2. Document PowerVM LPAR profiles.
  3. Maintain Nutanix node configuration records.
CFO
  1. Reserve provisional liability for ILMT compliance gaps.
  2. Capitalize the readiness program.
  3. Track readiness ROI.
The Framework

Eight ideas

ILMT is foundational

IBM License Metric Tool deployment is required for sub capacity licensing of PVU products on virtualized infrastructure. Without ILMT, IBM contractually requires full host counting; sub capacity rights are forfeited.

SCRT and retention

Sub Capacity Reporting Tool generates quarterly compliance reports. Two year retention is contractually required. Customers who skip retention cannot defend prior periods during audit.

VMware sub capacity

VMware sub capacity requires capped clusters with documented affinity rules. Uncapped clusters default to full host counting. The framework documents the configuration patterns that maintain defensibility.

PowerVM sub capacity

PowerVM sub capacity requires explicit LPAR profiles with documented entitled processor units. Shared processor pool configurations require specific documentation to support sub capacity.

Nutanix and other hypervisors

Nutanix AHV, KVM, Hyper V each have distinct sub capacity requirements. The framework includes platform specific configuration checklists.

Cure period mechanics

IBM permits 90 day cure for documented ILMT failures. Customers who experience temporary ILMT outages can preserve sub capacity rights through documented remediation. The provision is rarely volunteered by IBM.

Manual measurement substitutes

Air gapped environments cannot run ILMT. Manual measurement following published methodology can substitute for ILMT in defined scenarios. The framework documents the qualifying conditions.

Recurring readiness cadence

Compliance drifts. Quarterly review captures and holds readiness. Without it, the next audit finds gaps.

Reference

Acronyms

ILMTIBM License Metric Tool.
SCRTSub Capacity Reporting Tool.
PVUProcessor Value Unit.
RVUResource Value Unit.
LPARLogical Partition.
WPARWorkload Partition.
SPPShared Processor Pool.
AHVAcropolis Hypervisor.
PAPassport Advantage.
BATNABest Alternative To a Negotiated Agreement.
Methodology & Sources

This white paper draws on Redress Compliance engagements, public vendor documentation, and the active Redress benchmark program.

Portrait of Morten Andersen
About the Author

Morten Andersen

Co Founder, Redress Compliance
Connect on LinkedIn →
Have a renewal coming up this quarter?
Talk to an Advisor
Related

Continue

Skyscraper
Ready?

Stop overpaying. Start negotiating.

We work for the buyer. Always. There is no other side of our table.

The Licensing Insider

Vendor watch, contract clauses, audit trends. Monthly briefing for buy side leaders.