ILMT compliance isn’t a one-time exercise. If you’re using IBM sub-capacity licensing to reduce your PVU liability, the IBM License Metric Tool needs to be running correctly, consistently, every single month, or IBM won’t accept your quarterly audit reports.
That’s a significant exposure. A failed or incomplete ILMT environment can result in IBM reverting you to full-capacity pricing for the period in question. The cost difference between sub-cap and full-cap on a large deployment can run into hundreds of thousands of dollars. What follows is the monthly ILMT run book our consultants use to keep clients compliant and audit-ready throughout the year.

Why ILMT Compliance Requires Monthly Attention
Most organizations treat ILMT like a set-and-forget tool. They install it, configure it, and assume it’s doing its job. It usually isn’t. ILMT relies on BigFix for its scanning infrastructure, and BigFix environments are rarely static. Servers come and go. VMs migrate. Hypervisor configurations change. Signature files fall out of date. Any one of these shifts can silently break your audit data without triggering an alert.
IBM’s sub-capacity licensing rules require that ILMT be “properly maintained.” That phrase does a lot of work. In practice, it means your quarterly audit snapshot needs to reflect accurate, continuous data collection, which only happens when someone checks the tool’s health every month. The 12 checks below are the minimum standard for keeping an ILMT environment in a defensible state.
If you already know your ILMT environment has fallen behind, our ILMT Health Check and Repair service is a useful starting point before introducing a monthly runbook process.
Check 1: Confirm ILMT Is on the Latest Version
Running an outdated version of ILMT is one of the most common findings in IBM audit situations, and IBM has used it as grounds to question the validity of audit reports. Version updates introduce support for newer hypervisors, fix calculation errors, and recognize recently released IBM software. An ILMT instance that hasn’t been updated in six months may be miscounting PVU consumption, which won’t surface until IBM’s auditor examines the underlying data.
The check here is simple: verify the installed ILMT version against IBM’s current release, and if there’s a gap, schedule the update before the end of the month.
Check 2: Download and Propagate PVU and Signature Files
ILMT’s software recognition depends on signature files, and its PVU calculations depend on processor value tables. Both are updated by IBM regularly. If your ILMT instance is using outdated signature or PVU files, it may misclassify software, miss newly bundled products, or apply incorrect PVU values to hardware.
This check confirms that the latest files have been downloaded from IBM’s catalog and successfully propagated to BigFix clients across your environment. Propagation failures are common in larger, segmented networks, so the check needs to verify endpoint-level receipt, not just a successful download at the server.
Check 3: Download and Deploy Fixlets
Fixlets are BigFix’s mechanism for deploying ILMT-related updates, configuration changes, and patches. IBM regularly publishes new fixlets that address scanning issues, update software definitions, and improve the accuracy of capacity calculations. Many organizations download fixlets without verifying that they’ve been successfully deployed to all relevant endpoints.
This check should confirm that any open fixlets have been deployed, that no deployment failures are outstanding, and that the fixlet baseline is consistent across all managed endpoints. Fixlet deployment failures in DMZ segments or cloud environments are particularly common and worth specific attention.
Check 4: Reconcile Scanned Servers Against Your CMDB
ILMT can only measure what it can see. If a server exists in your environment but hasn’t been onboarded to BigFix, it won’t appear in your audit data — and if it’s running IBM software, that’s an undisclosed compliance gap. IBM auditors cross-reference ILMT data against other sources, and a significant discrepancy between what ILMT reports and what actually exists in your data center is a red flag.
The monthly reconciliation compares the server inventory in ILMT with your CMDB, asset register, or an equivalent authoritative source. Any server that appears in one but not the other needs to be investigated and resolved before the quarterly audit snapshot is generated.
Check 5: Verify All Servers Are Reporting Successfully
Getting a server into ILMT is step one. Keeping it reporting is step two, and it’s where most ongoing maintenance effort goes. BigFix clients can stop reporting for a variety of reasons: network changes, agent updates, OS patching, VM migrations, or certificate issues. A server that missed three months of scans has effectively been invisible to ILMT for that period.
This check involves reviewing the last-reported timestamps for every managed endpoint and flagging anything that hasn’t reported within a defined threshold. Any endpoint that’s missed more than one scan cycle needs to be investigated and reconnected before the data gap becomes material.
Incomplete ILMT reports are among the most common ways organizations discover compliance problems after the fact, rather than before. See also: Why Your IBM ILMT Licensing Reports Are Probably Wrong.
Check 6: Confirm All VM Managers Are Reporting Back
In virtualized environments, VM Manager data enables ILMT to calculate sub-capacity PVU consumption. Without accurate VM Manager feeds, ILMT can’t track which VMs run on which physical hosts, so it can’t apply sub-capacity rules correctly. IBM’s sub-capacity audit requirements specifically require that all hypervisors in scope be connected and reporting.
The monthly check here confirms that every VM Manager in the ILMT configuration has successfully reported within the current cycle, that no VM Managers have been added to the environment without being registered in ILMT, and that the topology data being imported reflects the current state of the virtualization layer.
Check 7: Understand Differences Between This Month’s and Last Month’s Reports
One of the most valuable things a monthly run book forces is a comparison of the current audit report against the previous month’s baseline. Unexplained increases in PVU consumption, new software appearing in the report, or servers dropping off the inventory — all of these are signals that something has changed in the environment and needs to be understood before it becomes an audit issue.
The key word is “understood.” Some changes are legitimate: a new server was deployed, a software deployment was expanded, and a VM cluster was rebalanced. Others are artifacts of a configuration problem. Either way, the monthly review ensures that nothing unexpected appears in the quarterly ILMT audit snapshot without a documented explanation.
Check 8: Confirm Previous Month’s Issues Are Resolved
Monthly ILMT reviews almost always surface issues. Run book discipline ensures those issues don’t simply accumulate. If last month’s review identified three endpoints that had stopped reporting, this month’s check should confirm that all three have been remediated and are now current.
A backlog of unresolved ILMT issues is a compliance risk in its own right. If an IBM audit finds that you identified problems in your monthly reviews but didn’t resolve them, that’s evidence that the sub-capacity management process wasn’t functioning as required. Documented resolution is as important as the fix itself.
Check 9: Raise Incidents for New Issues Found This Month
Anything identified during the current month’s review that can’t be resolved immediately needs to be logged as a formal incident in your ITSM system. This isn’t bureaucracy for its own sake. A documented incident trail demonstrates that your organization takes ILMT compliance seriously and responds to issues in a structured way.
This documentation becomes particularly important if an issue affects audit data. Being able to show IBM that you identified the problem on a specific date, raised an incident, and tracked it to resolution is a very different position from having no record of the issue at all.
Check 10: Raise PMRs With IBM for BigFix and ILMT Technical Issues
Some ILMT and BigFix issues can’t be resolved internally — they require IBM support. When that’s the case, a Problem Management Record (PMR) should be raised with IBM promptly. This matters for compliance as much as it matters for resolution. IBM’s sub-capacity licensing terms require that you take reasonable steps to maintain ILMT, and raising a PMR is evidence that you did exactly that when a technical problem was outside your control.
Organizations that have faced audit challenges related to ILMT data gaps have been in a significantly stronger position when they could show an open PMR that pre-dated the audit inquiry. Don’t wait until the quarterly report is due to raise support cases that have been outstanding for weeks.
Check 11: Escalate Any Open Issues When the Quarterly Report Is Due
If the quarterly audit snapshot is approaching and there are unresolved issues that could affect the data, those issues need to be escalated immediately — not noted in a run book comment and moved along. The quarterly report is the document IBM receives and may later audit. Submitting a report you know contains gaps is far worse than pausing the report cycle, resolving the issues, and submitting late with a documented explanation.
This check is about applying judgment: are the outstanding issues minor and non-material, or do they affect the integrity of the PVU calculations? If it’s the latter, the quarterly submission needs to be held until they’re resolved. This is also the moment to loop in legal or procurement if there’s any risk the report exposes a compliance position IBM could act on.
Check 12: Report to Management on ILMT Health and Compliance Risks
ILMT compliance isn’t just a technical function — it carries financial and contractual risk that management needs to be aware of. A monthly report to the relevant stakeholders covering the health of the ILMT environment and any identified sub-capacity compliance risks keeps the right people informed and creates a paper trail that demonstrates active governance.
The content of that report doesn’t need to be lengthy. A brief summary of open issues, the status of the quarterly report, any material changes in PVU consumption, and any unresolved vendor support cases is typically sufficient. What matters is that it’s consistent, dated, and distributed to the people who would need to make decisions if a serious issue arose.
If you’re not confident in the current state of your ILMT environment, an independent ILMT Health Check can identify what’s broken and what it would take to get to a defensible position before your next audit snapshot.
What Happens If ILMT Isn’t Properly Maintained
It’s worth being explicit about the consequences of a poorly maintained ILMT environment, because it’s more serious than most organizations realize until they’re in an audit. IBM’s sub-capacity licensing entitlement is conditional. If IBM determines that ILMT wasn’t properly maintained during a given period, they can require you to license on a full-capacity basis for that period — meaning PVU charges based on the total physical capacity of every server in scope rather than the sub-capacity peak measured by ILMT.
For large virtualized environments, the difference between sub-cap and full-cap can be substantial. We’ve seen cases where a 12-month ILMT maintenance failure resulted in a retroactive full-capacity liability of seven figures. The monthly run book process exists precisely to prevent that scenario.
If you’re currently without one, an independent review of your ILMT environment is a sensible first step before your next quarterly report is due. Our IBM Audit Defense team has worked through these scenarios with organizations at every stage of the audit process.
Conclusion
Keeping ILMT compliant is an ongoing operational commitment, not a project with a completion date. The 12 checks above form a practical monthly process that any organization using IBM sub-capacity licensing should implement. Run them consistently, document what you find, and resolve issues before they compound.
Key takeaways:
- ILMT version currency, signature files, and fixlet deployment need to be verified every month, not just at installation.
- Server and VM Manager coverage gaps are the most common source of compliance exposure in audit situations.
- Documented incident management and IBM PMRs are as important as the technical fixes themselves.
- The quarterly audit snapshot reflects the health of your ILMT environment throughout the quarter — not just on the day you generate the report.
- If your ILMT environment has fallen behind, get an independent health check before your next quarterly submission.
FAQ
The IBM License Metric Tool (ILMT) is IBM’s approved software for measuring sub-capacity PVU consumption in virtualized environments. If you want to license IBM software on a sub-capacity basis — paying only for the virtual processor resources actually allocated to IBM workloads rather than the full physical capacity of the host — IBM requires that you run ILMT and submit quarterly audit reports generated from it. Without ILMT, IBM’s default position is that you’re liable on a full-capacity basis.
IBM releases ILMT updates periodically, and organizations are expected to remain reasonably current. There’s no hard rule requiring you to be on the latest release within a fixed number of days, but running a version that’s significantly outdated — particularly one that doesn’t support your current hypervisor or IBM software versions — is a risk during an audit. Monthly version checks are the recommended practice.
A server that stops reporting creates a data gap in your ILMT history. When it comes back online, ILMT will resume scanning it, but the gap period won’t be retroactively filled. Depending on the length of the gap and the IBM software running on that server, IBM may take the position that the server should have been licensed on a full-capacity basis during the period it wasn’t visible to ILMT. Documenting the gap, the cause, and the remediation is important.
The process involves generating the audit snapshot from within the ILMT interface, reviewing it for anomalies before submission, and retaining a copy for your records. We’ve covered the specific steps in our guide to downloading an ILMT audit snapshot.
IBM does allow alternative tools under certain conditions, but the approved alternatives are limited and the approval process is not simple. For most organizations running standard virtualized environments, ILMT via BigFix remains the practical path. If you’re exploring alternatives, that conversation should involve someone who understands both the technical requirements and the contractual implications.
A VM Manager is the connection between ILMT and your hypervisor layer—VMware vCenter, Microsoft Hyper-V, IBM PowerVM, and similar platforms. ILMT uses VM Manager data to understand the relationship between virtual machines and their physical hosts, which is the basis for sub-capacity PVU calculations. If a VM Manager isn’t connected or isn’t reporting, ILMT can’t correctly calculate sub-capacity consumption for the VMs in that cluster.
Don’t submit a report you believe to be wrong. The first step is to identify the source of the discrepancy — outdated signature files, a VM Manager gap, missed scans, or a version-related calculation issue are the most common causes. If you can’t identify or resolve it internally, raise a PMR with IBM and engage an independent IBM licensing advisor before the quarterly deadline. Submitting a report you know is incorrect is a worse position than submitting late with documentation.


