To view answers, simply expand a question.
Unless a customer qualifies for one of the stated contractual exceptions, ILMT is a mandatory requirement. IBM BigFix Inventory may be used in lieu of ILMT. The stated exception can be found in the International Passport Advantage Agreement (IPAA) or by visiting the Sub-capacity ILMT information page.
2. I already have a tool in place that provides the same information as IBM's tool, would IBM still insist that I use ILMT?
Yes. While there are many tools that are able to determine the software inventory and perhaps even the processor core type available to a physical server or partition (physical or virtual), ILMT and IBM BigFix Inventory are the only tools capable of the on-going monitoring of virtualized server environments to measure the maximum (peak) capacity available to the IBM software – and report those requirements as measured in PVUs.
3. For a customer who qualifies for an ILMT exception and is doing manual tracking/reporting, what tools can the customer use to supplement manual efforts?
For the announced exceptions to the ILMT requirement, the manual counting/reporting requirement can be supplemented by alternative tools as long as they assist in an accurate measure of the peak PVU capacity by software product. There are several products in the marketplace that can perform simple software inventory scans and even fewer solutions exist that can determine the type of processor core on the hardware server (a requirement to determine the number of PVUs to be licensed). But unlike ILMT, these tools are unable to provide on-going monitoring of changes to the processor core capacity of a virtualized partition, to capture the maximum (peak) capacity available to the IBM PVU-based software.
Even ILMT can be used in unsupported, yet eligible server virtualization technology environments to assist in capturing the servers' basic hardware processor core and software inventory information -- but if ILMT doesn't support the virtualization technology, it will not generate the correct answer for partitions, LPARs, VMs, domains, etc. That data must be captured manually using whatever means provided by the operating systems, virtualization technologies, change management logs, etc.
No. ILMT is server/agent-based solution designed to provide on-going monitoring of sophisticated server virtualization technologies across complex server configurations. Most customers capable of deploying complex virtualized server technologies such as PowerVM and VMware, will have the capability of deploying ILMT. However, ILMT needs to leverage a customer's IT asset management processes and disciplines. Customers who already have these in place will find that ILMT complements their efforts.
5. Does IBM require that customers report their Sub-capacity results each quarter similar to how SCRT is used for System z Software?
No. Customers are required to provide ILMT reports only upon IBM’s request. SCRT (Sub-capacity Reporting Tool) is only used in support of System z software. For more information on Sub-capacity licensing for System z software visit IBM Z software pricing, select 'Licensing' and then 'Sub-capacity licensing'.
New Sub-capacity customers are required to implement IBM License Metric Tool (ILMT) or IBM BigFix Inventory within 90 days of their first Eligible Sub-capacity product deployment on an Eligible Virtualization Environment. Existing Sub-capacity customers should promptly upgrade to new versions, releases or modifications when they are made available per the IPAA. Note that IBM intentionally does not prescribe a specific period of time for this term to accommodate various customer sizes. The intent is for customers to imply as soon as possible given their specific IT framework.
7. Does this mean I have to install ILMT in addition to the commercial version of IBM BigFix Inventory?
No, IBM does not require both products to be installed.
8. Does a customer who has a product such as WAS need to generate a report on all servers that have WAS?
Yes, if the customer intends to license WAS for less than the full capacity of the servers where it is deployed.
9. If a customer has multiple instances or packages of a product running in a single partition, how are the PVUs counted?
PVUs are licensed based on the processor core capacity that is available to the IBM middleware. From a licensing perspective, a partition can have any number of "instances" or "packages" (not a legally defined term) of a product running, we do not count those multiple instances of that product -- we only license based on the maximum (peak) processor cores assigned to that partition and available to that product. If the number of instances causes the partition's capacity to be increased, ILMT will capture that "high water mark" so that the customer can ensure compliance with our terms.
The Sub-capacity terms reflect quarterly reporting as the maximum amount of time allowed before having to analyze and reconcile ILMT reports. Most customers will probably need to perform this effort on a monthly basis. Some customers, with very dynamic server environments, where partitions are resized/moved frequently and/or with changes in their software inventory, may need to create weekly reports in order to keep up with the volume of change. Only customers with the most stable of virtualized server environments would be able to maintain compliance with IBM licensing terms by doing quarterly reports.
12. Where can I find general information to learn more, additional FAQs specific to ILMT, examples of the available reports, requirements and additional ILMT support?
General Information to learn more: ILMT’s Information Center for specific release version.
13. Is it necessary to have ILMT on disaster recovery back-up servers to monitor the processor core capacity required for licensing terms?
Yes, you should install agents on any backup server where ILMT is also installed on the primary server/partition.
You can then exclude such instances from PVU calculation if a license is not required (typically warm/cold back-ups, but the license requirement can vary by product). For specifics, refer to the product's announcement letter [by searching the Offering Information Web] or the product's License Information Document [by conducting a Software license agreements search].