Restoring sub capacity rights after an ILMT gap.

When ILMT lapses, IBM defaults you to full capacity across whole hosts. The exposure can be enormous, but a gap is not automatically a loss. Here is how to rebuild the evidence and defend the period.

Sub capacity licensing is conditional. IBM grants the right to license only the virtual cores running its software, provided an approved tool is deployed within 90 days of first eligible deployment, runs continuously, and produces quarterly reports retained for two years. Break the continuity and the default is unforgiving: IBM charges full capacity across every physical core in the host for the affected period. The gap between the two can be a factor of eight or more on a large server.

Why a gap is not the end of the argument

Auditors present a tool gap as an automatic full capacity charge. In practice the position is more contestable than that. The real deployment did not change because a tool stopped reporting, and there is usually other evidence of the actual virtual capacity in use during the gap. The objective is to reconstruct what was genuinely deployed and to narrow the period to which any default applies.

The restoration sequence

• Scope the gap precisely. Establish the exact start and end of the lapse. IBM often claims a wider window than the evidence supports, and every quarter you can document is a quarter removed from full capacity exposure.
• Get the tool healthy now. Restore continuous scanning, correct categorizations, and purge stale machines so the current position is clean and defensible going forward.
• Backfill from other evidence. Hypervisor logs, configuration records, change tickets, and CMDB history can all corroborate the virtual capacity that was actually running during the gap.
• Reconstruct the deployment. Build a defensible view of real consumption in the gap period rather than accepting the full capacity default by silence.
• Carry it into the settlement. Where a residual exposure remains, fold the restored sub capacity position and a forward compliance plan into the settlement terms.

The forward fix

Restoring rights for the past only holds if the future is solid. Continuous scans, retained quarterly reports, and routine cleanup keep the sub capacity claim alive so the same gap cannot reopen. A documented remediation also signals to IBM that the lapse was an operational fault now corrected, not a pattern of non compliance.

A tool gap is the single most expensive failure in IBM licensing, but it is an argument, not a verdict. The companies that limit the damage are the ones that reconstruct the real deployment instead of accepting the full capacity number on the page.