ILMT and Sub-Capacity

ILMT Health Check: The 20 Point Audit

Most sub-capacity findings are not surprises to the auditor. They are configuration gaps that were sitting in plain sight for years. A disciplined health check surfaces those gaps on your terms, while there is still time to fix them, rather than on IBM's terms inside a finding.

Why a health check beats a surprise

The IBM License Metric Tool is only as useful as its configuration. It miscategorizes installs by default, it goes blind when an agent stops reporting, and it inflates counts when it cannot see your virtualization. Each of those is invisible until someone looks. The auditor will look. A self-administered health check, run on a regular cycle, lets you find and close the same gaps before they are priced.

The 20 points

Group the checks into five areas. Each point is a yes or no question, and any no is a gap to remediate.

Coverage and agents

Software classification

Virtualization and capacity

Reporting and retention

Operation and governance

Reading your own results

A single no is rarely fatal, but the pattern matters. Gaps in coverage and reporting expose you to full-capacity charging for the unevidenced periods. Gaps in classification inflate the count today. Gaps in virtualization turn a small virtual footprint into a large physical one. Fix the reporting and retention points first, because those are the ones an auditor cannot un-see once the look-back begins.

Frequently asked questions

How often should an ILMT health check run?

At least quarterly, aligned to the report cycle, and again after any hypervisor upgrade, cluster change, or credential rotation that could break the VM manager connection.

Does a clean health check guarantee sub-capacity eligibility?

It is necessary but not sufficient. Eligibility also depends on retained quarterly reports, continuous operation, and eligible virtualization technology across the entire look-back period.

What is the most common failure?

Miscategorized installations and broken or missing agents, because both quietly inflate the processor value unit count or void the sub-capacity claim for the affected period.

What this means under audit

Run the 20 points on a schedule, not in a panic. Every gap you close before a notice arrives is a finding the auditor never gets to make. The reporting and retention points carry the largest exposure, so start there.