IBM’s License Metric Tool (ILMT) is essential for maintaining sub-capacity compliance, yet many organizations only monitor a portion of their IBM software environment. Incomplete coverage creates significant audit risk and prevents accurate cost optimization. These seven practical strategies, drawn from enterprise implementations, help expand ILMT scanning scope systematically.

Start with a Solid Foundation
Before expanding the scope, validate your current ILMT infrastructure:
- Version Requirements: Run ILMT version 9.2.40 or later. Earlier versions lack critical fixes, and compliance features that IBM auditors expect to see.
- BigFix Platform: Keep your BigFix infrastructure current. While older versions function, they introduce security vulnerabilities and support complications that become magnified at scale.
- Database Performance: Ensure your database engine (typically DB2) is properly tuned and supported. Database bottlenecks that seem minor in small environments can cripple performance when scanning thousands of endpoints.
A stable foundation prevents small issues from becoming major problems as you scale.
Deploy Relay Servers Strategically
When extending ILMT to new environments or remote networks, relay servers are critical infrastructure components. They reduce load on the central BigFix server and enable reliable communication across network boundaries.
- Network Configuration: Open UDP port 52311 between endpoints, relays, and the core BigFix server. This port handles the primary communication for scan data transmission.
- Placement Strategy: Deploy relays in each major network segment, particularly across WAN connections or security zones where direct communication to the central server would be inefficient.
- Integrate Virtualization Platforms – Virtual machine discovery is mandatory for sub-capacity licensing eligibility. Without complete virtualization data, IBM treats all instances as full-capacity licensed during audits.
- VM Manager Configuration: Add all hypervisors (VMware vCenter, Hyper-V, etc.) through the VM Manager Tool. This requires specific firewall rules and service account permissions for each virtualization platform.
- Common Integration Issues: Verify that service accounts have read-only access to virtualization management interfaces. Many organizations struggle with Active Directory authentication or certificate-based connections to vCenter servers.
Automate Scan Scheduling
Manual scanning processes create compliance gaps. Automation ensures consistent data collection across your entire environment.
- Scan Types: Schedule software discovery scans, capacity scans, and VM manager scans independently. Each scan type serves different compliance requirements and operates on different schedules.
- Upload Automation: Configure automatic upload of scan results to the ILMT database. Manual upload processes frequently break down in large environments, creating data gaps that appear as non-compliance during audits.
- Frequency Requirements: IBM requires a minimum of quarterly scans, but monthly scanning is standard practice for dynamic environments with frequent changes.
Master Software Bundling
ILMT discovers software components but cannot automatically determine which IBM products they represent. This bundling process is manual and critical for accurate compliance reporting.
- Mapping Process: Each discovered component must be mapped to the appropriate IBM Program Identification Number (PID). Incorrect bundling can make you appear over-licensed or under-licensed.
- Documentation Requirements: Maintain clear documentation of bundling decisions. IBM auditors will review these mappings and may challenge configurations that seem aggressive or incorrect.
- Ongoing Maintenance: New software discoveries require prompt bundling. Unbundled components create reporting gaps that auditors interpret as potential compliance issues.
Optimize Performance at Scale
ILMT scanning can significantly impact system performance, particularly on older servers or systems with large file systems.
Resource Management:
- Exclude non-relevant file systems (backups, archives, test data) from scans
- Enable CPU throttling in scan configurations to prevent system overload
- Monitor scan duration and adjust scheduling to avoid business hours on critical systems
Infrastructure Tuning: As scanning scope expands, tune DB2 settings and adjust JVM heap allocations for ILMT components. Database performance becomes critical when processing scan data from thousands of endpoints.
Plan Platform Upgrades
Staying current with BigFix versions provides stability and compliance advantages that become more important as your environment grows.
- Current Upgrade Path: Plan migration from BigFix 10.0.x to version 11. This upgrade provides extended support timelines and improved security features.
- Audit Considerations: Running unsupported versions creates audit complications. IBM auditors may question the reliability of compliance data from out-of-support infrastructure.
- Implementation Strategy: Plan upgrades during maintenance windows and test thoroughly in development environments before production deployment.
Managing Expansion Risks
Expanding ILMT scope requires balancing compliance needs with operational stability. Key considerations include:
- Performance Impact: Larger scanning scope increases database load and network traffic. Monitor system resources and adjust scan scheduling to prevent service degradation.
- Change Management: Document all configuration changes and maintain rollback procedures. ILMT configuration errors can affect compliance reporting across your entire IBM software portfolio.
- Validation Testing: After scope expansion, verify that scan data is complete and accurate. Run test scenarios to ensure virtualization data, software discovery, and bundling are working correctly.
Scale BigFix and ILMT Infrastructure Proactively
As your ILMT scanning scope grows, the load on your BigFix and ILMT infrastructure increases. Planning for scalability ensures performance stability and prevents outages.
- Endpoint Growth Planning: Size your BigFix server and relay infrastructure for anticipated growth in endpoints, not just current demand.
- Database Scaling: As scan data grows, DB2 (or SQL, if used) may require partitioning, additional memory, or advanced tuning.
- Distributed Architecture: For very large environments, consider a distributed ILMT deployment with dedicated reporting servers to handle higher workloads.
Scaling proactively avoids downtime and ensures reporting keeps up with rapid infrastructure expansion.
Establish Daily Health Checks and Monitoring
Even with strong infrastructure, unnoticed issues can silently break compliance reporting. Daily monitoring catches problems early.
- Agent Health: Monitor BigFix agents for the last report times. Silent agents = missing scan data.
- Scan Status Validation: Check daily whether software, hardware, and capacity scans completed successfully across all endpoints.
- Upload & Import Logs: Validate that scan data uploads and imports into ILMT database occur without errors.
- Alerting: Set up automated alerts for failed scans, relay communication issues, or database errors.
Daily health checks reduce compliance gaps and prevent last-minute surprises during an audit.
Strengthen Security and Access Controls
ILMT and BigFix handle sensitive infrastructure data, including software inventories and virtualization configurations. Strong security practices protect both compliance and data integrity, as well as enterprise IT environments.
- Role-Based Access Control (RBAC): Restrict ILMT/BigFix console access to authorized personnel only.
- Audit Trails: Enable activity logging and review changes regularly. Auditors may request evidence of security controls.
- Certificate Management: Keep BigFix and ILMT certificates current to prevent authentication failures between agents, relays, and servers.
- Segregation of Duties: Separate administrative, reporting, and audit review roles to maintain compliance credibility.
Security not only reduces risk but also demonstrates to IBM auditors that your compliance data is trustworthy.
Frequently Asked Questions
Any unscanned systems are treated as full-capacity licensed during IBM audits. This assumption can result in significant financial exposure, particularly in virtualized environments where sub-capacity savings are substantial.
ILMT can automatically collect virtualization data through the VM Manager Tool, but only with proper configuration. This requires specific firewall rules and service account permissions for each virtualization platform.
IBM requires quarterly scans minimum, but monthly scanning is recommended for environments with frequent changes. Critical systems may benefit from weekly scanning.
Yes. Bundling maps discovered software to licensed IBM products. Without accurate bundling, ILMT reports cannot demonstrate compliance and may misrepresent your licensing position.
No. ILMT is built on the BigFix platform and requires BigFix agents for endpoint scanning and data collection. Maintaining current BigFix infrastructure is essential for ILMT functionality.
Need help expanding your ILMT coverage?
Schedule a consultation to review your scanning scope and identify potential compliance gaps before your next IBM audit.


