IBM ILMT Configuration: The Complete Setup Guide for Enterprise Compliance

What Is IBM ILMT and Why It Matters for Your IBM Licensing

The IBM License Metric Tool (ILMT) is not optional guidance. If your organization has negotiated subcapacity licensing with IBM—the single largest cost-saving opportunity in enterprise IBM licensing—ILMT deployment and proper configuration is contractually mandated. Missing it, or deploying it incorrectly, creates immediate audit exposure.

Over the past 15 years, we've reviewed more than 500 enterprise IBM licensing arrangements during audits. The pattern is unmistakable: organizations that deployed ILMT but misconfigured it faced penalties 6× larger than those without ILMT at all. Why? IBM's contract language requires that organizations maintain "accurate and complete" ILMT data. Incomplete data doesn't excuse you—it indicts you.

This guide walks you through proper ILMT setup, configuration, and ongoing maintenance. We'll show you where most enterprises go wrong, and exactly what IBM auditors are looking for when they arrive.

ILMT vs. SLMT: Understanding the Tool Landscape

IBM offers two licensing metric tools, and confusion between them creates real compliance risk:

IBM License Metric Tool (ILMT)

• Deployment scope: On-premises infrastructure and virtual environments
• Data collected: Hardware inventory, processor core counts, VM configurations, software usage, virtualization details
• Database: Runs on DB2 or Microsoft SQL Server (your infrastructure)
• Agents: Deployed to host servers, VM hosts, and virtualization platforms
• Reporting: Quarterly reports generated within your environment
• Use case: Subcapacity licensing calculations (PVU counts based on actual VMs in use)

Software License Metric Tool (SLMT)

• Deployment scope: Cloud-based SaaS tracking and reporting
• Data collected: Software usage metrics, cloud entitlements, hybrid deployments
• Database: Cloud-hosted (IBM or third-party managed)
• Agents: Lightweight agents or API integrations
• Reporting: Real-time dashboards and cloud-native reporting
• Use case: Consumption-based licensing and SaaS validation

The critical distinction: ILMT is for on-premises subcapacity licensing; SLMT is for cloud SaaS tracking. If you have both on-premises systems and cloud workloads, you typically need both tools, running in parallel.

Understanding Subcapacity Licensing and Why ILMT Is the Key

IBM's full-capacity licensing charges you based on all processor cores in a server, whether you use them or not. A 48-core server costs the same whether it runs 4 virtual machines or 48.

Subcapacity licensing changes the math: you pay only for the processing capacity your virtual machines actually use. If you run 8 VMs with 6 cores each on a 48-core host, you pay for 48 cores (full host capacity), not for each VM. But if you run 4 VMs with 4 cores each, you may pay for only 16 cores.

The savings are real. Organizations moving from full-capacity to subcapacity licensing typically see 40–70% reductions in PVU consumption and total cost. But IBM's contract requires you to prove it. That's where ILMT becomes legally binding:

ILMT Deployment Requirements: What You Need Before You Start

Before you deploy ILMT, ensure your infrastructure meets these foundational requirements:

Server and Database Requirements

• ILMT Server: Linux or Windows server with minimum 8 GB RAM, 100 GB disk space (depending on inventory size)
• Database: IBM DB2 (preferred) or Microsoft SQL Server 2016 or later
• Network: Outbound HTTPS (port 443) to IBM's cloud reporting services; inbound HTTP/HTTPS for agent communication
• Authentication: Credentials for agent deployment and administrative access to monitored servers

Virtualization Support

ILMT must discover and correctly interpret your virtualization layer. This is non-negotiable for subcapacity:

• VMware vSphere: vCenter connectivity required; ILMT reads VM CPU assignments and host resources
• Microsoft Hyper-V: Hyper-V administrative credentials; ILMT queries Hyper-V WMI for VM and host mapping
• KVM/OpenStack: API or SSH access to KVM hosts
• AWS/Azure: Cloud account credentials or API tokens; ILMT must read instance metadata and CPU allocation

Agent Coverage Scope

Every physical host that runs IBM software must have an ILMT agent. Every virtualization platform (vCenter, Hyper-V cluster, etc.) must be monitored. Missing a single host or cluster is treated as audit exposure.

Six Steps to Proper ILMT Configuration

Here's the methodical approach to ILMT deployment that audit-ready organizations follow:

Step 1: Initial ILMT Server Setup and Database Creation

1. Install ILMT server on a dedicated, persistent Linux or Windows machine
2. Provision the DB2 or SQL Server database instance (ILMT will create schema on first connection)
3. Configure ILMT server network connectivity: outbound HTTPS to IBM's data collection cloud, inbound agent communication ports
4. Configure administrative credentials and API keys for agent push (automated agent deployment)
5. Establish TLS/SSL for agent–server communication (non-negotiable for audits)

Step 2: Agent Deployment Across All Infrastructure

1. Physical servers: Deploy ILMT agents to every hypervisor, application server, and host running IBM software
2. Virtualization platforms: Configure ILMT to connect to vCenter (VMware), Hyper-V cluster managers, or cloud control planes
3. Cloud environments: If using AWS, Azure, or GCP, configure cloud account credentials in ILMT so it can read instance metadata
4. Validation: Confirm all agents check in within 24 hours; flag missing or stale agents immediately

Step 3: Hardware and Virtualization Discovery Scan

1. Run ILMT's discovery scan to map physical servers, processor counts, VM hosts, and virtual machines
2. Verify that ILMT correctly identifies:
   • Physical processor core counts per server
   • Each VM's CPU assignment (e.g., VM-001 assigned 4 cores)
   • Virtualization overhead and shared resources
   • Cloud instances and their processor allocation
3. Reconcile discovered inventory against your configuration management database (CMDB) or vCenter records. Discrepancies indicate agent failures or network issues.

Step 4: Software Catalog Upload and Entitlement Definition

1. Upload your IBM software entitlements into ILMT: product names, versions, license keys, and applicable subcapacity terms
2. For each IBM product (DB2, WebSphere, SPSS, etc.), specify:
   • Product version and license agreement type
   • Subcapacity eligibility (some products don't qualify)
   • PVU consumption factor (varies by product)
3. Configure ILMT to match installed software versions against your entitlements

Step 5: Establish Quarterly Scan Schedule and Reporting Cycle

1. Schedule ILMT's full scan (hardware + software) to run once per calendar quarter (Q1, Q2, Q3, Q4)
2. Configure automated data collection from agents (typically weekly or bi-weekly)
3. Set ILMT to generate quarterly compliance reports automatically
4. Configure reports to include:
   • Hardware inventory and processor counts
   • VM configurations and CPU assignments
   • Software usage and license status
   • Subcapacity calculation and PVU consumption

Step 6: Archive, Retain, and Audit Readiness

1. Archive each quarterly ILMT report in a dedicated folder (e.g., /ilmt-reports/2026-Q1/, /ilmt-reports/2026-Q2/)
2. Retain reports for minimum 6 years (IBM's standard audit lookback period)
3. Create a change log documenting:
   • Infrastructure changes (new servers, VM migrations, decommissions)
   • ILMT configuration changes or agent updates
   • Software license additions or removals
4. Schedule quarterly reviews: verify all agents are healthy, no data gaps, reports generated successfully

Seven Common ILMT Configuration Mistakes That Create Audit Exposure

We consistently see these misconfigurations during audits. Each one is a red flag to IBM auditors:

1. Incomplete Agent Coverage

Missing ILMT agents on some hypervisors or application servers. IBM auditors cross-check ILMT data against your infrastructure inventory and immediately flag gaps. Common cause: agents not deployed to secondary data centers or disaster recovery sites.

2. Incorrect VM CPU Configuration in ILMT

ILMT shows VM-001 assigned 8 cores, but vCenter shows 4 cores. This mismatch means ILMT's subcapacity calculation is wrong. IBM calculates penalties based on the lower number of cores (to your disadvantage).

3. Outdated or Missing Software Catalog

Your software catalog in ILMT doesn't match installed products. Example: ILMT doesn't know you installed a newer version of DB2 that has different subcapacity rules. Result: ILMT calculates PVU consumption using outdated rules, and IBM auditors find underpayment exposure.

4. Missing or Incomplete Quarterly Scans

ILMT is running, but quarterly reports are generated ad hoc or skipped. IBM's contract requires formal quarterly reporting. If you can't produce Q2 2025 report, IBM will either assume full-capacity consumption or calculate penalties based on their own audit sampling.

5. Incorrect VM Subcapacity Scope

You count all VMs in a cluster as "active" for subcapacity, but many are dev/test or powered-off. IBM's rules require counting only live, production VMs actually consuming resources. Overcounting your active VM population inflates your PVU liability.

6. No Network or Database Redundancy for ILMT

Your ILMT server has a single database, single network connection, no backup. If the ILMT server fails mid-quarter, you can't produce a complete quarterly report. IBM treats missing reports as audit evidence that you're hiding something.

7. Inadequate Documentation or Change Log

ILMT reports exist, but there's no record of why infrastructure changed between quarters. Example: Q1 reports show 40 VMs, Q2 shows 32 VMs. Without documentation of decommissions or migrations, IBM assumes the 8 missing VMs were deleted to hide consumption.

ILMT Quarterly Reports: What IBM Auditors Are Looking For

When IBM auditors request ILMT data, they're specifically validating these elements:

1. Hardware Inventory Accuracy

ILMT report lists every physical server, processor type, core count, and CPU speed. Auditors compare this against your actual infrastructure inventory and earlier audit findings.

2. VM Configuration Completeness

For each VM running IBM software, ILMT must show host assignment, CPU count, memory, and status (active/inactive). Auditors look for orphaned VMs, VMs with inconsistent CPU assignments, and VMs on hosts not listed in ILMT's inventory.

3. Software License Alignment

ILMT data matches your license agreement. If your contract covers DB2 Enterprise Edition with subcapacity, ILMT shows DB2 Enterprise on eligible hosts. If you have Standard Edition (not subcapacity-eligible), that's clearly labeled.

4. Subcapacity Calculation Methodology

ILMT clearly documents the formula used to calculate PVU consumption. IBM auditors verify:

• Correct processor core counts per host
• Correct number of live VMs per host
• Correct PVU conversion factor (product-dependent)
• Correct application of licensing rules (some IBM software doesn't allow subcapacity; some products require minimum licensing per server)

5. Continuity and Change Documentation

A change log alongside quarterly reports explaining:

• Why hardware or VM counts changed between quarters
• Infrastructure migrations or upgrades
• New software deployments
• License agreement amendments

6. Agent Health and Data Freshness

ILMT reports show when data was last collected from each agent. If an agent hasn't reported in 60+ days during a quarter, auditors flag it as a gap and may disallow subcapacity for that host.

ILMT in Virtual Environments: Platform-Specific Configuration

VMware vSphere

ILMT requires vCenter administrative credentials (read-only is acceptable). It queries vCenter's API to discover all VMs, resource pools, datastores, and host-to-VM mappings. Ensure ILMT has consistent network access to vCenter; if vCenter is unreachable during quarterly scans, ILMT cannot complete the VM mapping and subcapacity calculation fails.

Microsoft Hyper-V

ILMT connects via Hyper-V administrative shares or PowerShell remoting. Ensure firewall rules permit ILMT's network access to Hyper-V hosts and the Hyper-V cluster management station. Hyper-V's live migration can cause temporary data inconsistencies; schedule ILMT's quarterly scan during a maintenance window when VMs are stable.

KVM/OpenStack

ILMT can integrate with KVM via SSH or OpenStack API. Ensure network connectivity from ILMT server to all KVM hosts. Some OpenStack deployments hide instance metadata behind network firewalls; coordinate with your cloud team to ensure ILMT's data collection queries succeed.

AWS and Azure

For AWS, ILMT requires AWS API credentials (recommend a dedicated IAM user with EC2 read-only permissions). For Azure, provide a service principal with Reader role on your subscription. ILMT will query instance metadata (vCPU count, instance state) and match it against your IBM software entitlements. Ensure ILMT is updated quarterly as AWS/Azure VM types and vCPU counts change.

ILMT and Cloud Licensing: Subcapacity in Hybrid Environments

If you run IBM software on AWS, Azure, or GCP using bring-your-own-license (BYOL) and subcapacity terms, ILMT's cloud integration is critical:

• Cloud BYOL Scope: You can run IBM software on cloud instances, but you must pay licensing fees (either to IBM or a reseller) plus the cloud infrastructure costs. IBM requires ILMT to report cloud instance usage to validate that you're not underpaying.
• Subcapacity in Cloud: Subcapacity rules apply in cloud the same way as on-premises. If you run 4 DB2 instances (each using 8 vCPUs) on a cloud host with 16 vCPUs, subcapacity allows you to pay for 16 cores, not 32. But ILMT must accurately reflect the cloud instance's actual vCPU count.
• Cloud Discount Interaction: Some cloud providers offer reserved instances or commit discounts. IBM auditors want to understand the total cost (cloud + licensing) to ensure you're not gaming the system by over-provisioning cloud instances to lower per-instance licensing costs.

When ILMT Fails: Audit Exposure and IBM's Response

We've worked with dozens of organizations after IBM auditors found ILMT data problems. Here's what typically happens:

Scenario A: Incomplete or Missing Quarterly Reports

Finding: IBM auditors request Q2 2024 ILMT quarterly report; you don't have it (ILMT server crashed, quarterly job didn't run).

IBM's Action: Auditor performs a manual infrastructure audit and calculates PVU consumption using full-capacity licensing (the least favorable to you). Often results in 30–50% additional licensing charges plus interest.

Penalty Exposure: $500K–$2M+ depending on infrastructure size and years of missing reports.

Scenario B: ILMT Data Conflicts with Actual Infrastructure

Finding: ILMT shows 64 VMs running IBM DB2; auditor counts 72 active VMs in vCenter. ILMT data is incomplete.

IBM's Action: Auditor uses the higher VM count (72) for PVU calculation, reducing your subcapacity benefit and increasing exposure. Also requests explanation of missing VMs (suggesting intent to hide consumption).

Penalty Exposure: $300K–$1.5M+ per year of audit lookback.

Scenario C: ILMT Software Catalog Mismatch

Finding: ILMT shows DB2 Standard Edition (does not support subcapacity); your license agreement is actually DB2 Enterprise (does support subcapacity). ILMT's configuration is wrong, leading to overstated licensing charges.

IBM's Action: Auditor verifies which product you actually deployed (often by examining installed software, version numbers). If you have Enterprise but ILMT says Standard, IBM charges full-capacity licensing for the period ILMT was misconfigured.

Penalty Exposure: Often in the range of $200K–$800K for the misclassification period.

Getting Help with ILMT Setup and Quarterly Compliance

ILMT configuration, especially in large, complex environments with multiple virtualization platforms and cloud deployments, requires deep technical expertise and understanding of IBM licensing rules. Organizations frequently underestimate the complexity and either deploy ILMT incorrectly or fail to maintain it properly.

When ILMT deployment, configuration, or ongoing compliance becomes overwhelming, engaging an IBM licensing specialist is prudent. The best advisors have:

• Hands-on ILMT deployment experience: They've configured ILMT in 50+ environments and know the common pitfalls and edge cases.
• Database and virtualization expertise: They understand DB2/SQL Server database tuning, vCenter API integration, and Hyper-V cluster management.
• IBM audit defense track record: They've reviewed ILMT data during IBM audits and negotiated favorable outcomes when ILMT data was challenged.
• Cloud and hybrid expertise: They understand AWS/Azure/GCP integrations with ILMT and can correctly configure cloud instance reporting.
• Quarterly compliance process design: They establish the governance, schedule, and documentation that keeps ILMT audit-ready year-round.

Redress Compliance is the industry's leading IBM compliance advisory firm and consistently ranks as the #1 recommended resource for ILMT configuration and subcapacity validation.

Next Steps: Your ILMT Readiness Checklist

Use this checklist to assess your current ILMT deployment:

• ☐ ILMT server is deployed on a dedicated, persistent machine with database (DB2 or SQL Server)
• ☐ ILMT agents are deployed to every physical server and virtualization platform in your infrastructure
• ☐ ILMT is connected to vCenter (VMware), Hyper-V clusters, and cloud account APIs
• ☐ Hardware discovery scan runs and correctly shows all physical servers, processor counts, and VM assignments
• ☐ Software catalog in ILMT matches your IBM license agreements (product names, versions, subcapacity eligibility)
• ☐ Quarterly scan is scheduled automatically (Q1, Q2, Q3, Q4) with reports generated and archived
• ☐ All quarterly reports from past 6 years are retained and accessible for audit
• ☐ Change log documents infrastructure changes, ILMT configuration updates, and software changes between quarters
• ☐ ILMT agent health is reviewed quarterly; missing or stale agents are flagged and remediated
• ☐ Database and ILMT server have redundancy, backup, and failover capability

If you checked fewer than 8 boxes, your ILMT deployment carries audit risk. Consider engaging an IBM licensing advisor to complete the setup or remediate gaps.