United States: Arguments Against ILMT – What Does And Doesn't Work?

Last Updated: December 15 2015
Article by Christopher Barnett

Each of the major software publishers has one or two tricks up its sleeve – tricks that often are missed by licensees – affecting how its server products may be used in virtualized environments. For example, Microsoft SQL Server requires a minimum of four core licenses per vCPU, even if the actual number of vCPUs allocated to a VM is less than four. Oracle offers even more pitfalls for the unwary, in that it strictly – some would say unreasonably – limits and defines the specific virtualization technologies that may be used to license its products based on virtual resources (as opposed to host resources).

Falling somewhere between those two extremes is IBM.

IBM allows a wide array of its products to be licensed on a "sub-capacity" basis, and it also allows for a wide array of virtualization and processor technologies to be used to support sub-capacity-licensed virtualization environments. Moreover, while its Processor Value Unit (PVU) framework entails processor-specific PVU values to be used in licensing calculations, it does not apply an arbitrary minimum number of licenses that must be purchased for VMs as opposed to physical servers.

However, what it does require is that the licensee (1) deploy and use the IBM License Metric Tool (ILMT) in the virtualized environment to measure the resources allocated to the VMs running its products and (2) run at least quarterly reports out of ILMT to track that usage over time. The ILMT requirement is where most businesses get into trouble with IBM's PVU licensing.

In the face of that failure, it is not uncommon for businesses to try to turn the ILMT requirements against IBM. They may argue that the sub-capacity requirements were not properly incorporated into the agreements or not clearly communicated to the licensee, and, thus, that those requirements do not apply to the licensee. The big problem with this line of argument – other than the facts that IBM would reject it out of hand and that a business would face significant challenges convincing a court to accept it – is that the default licensing requirement for all IBM products licensed based on Value Units, PVUs, or other processor capacities is – and always has been – full capacity. If the sub-capacity requirements in the contract were somehow defective, then the business would be left with no choice other than to license its servers to their full, physical capacities.

Therefore, in the event of an audit, instead of attacking the contracts directly, it makes more sense to look at other aspects of the ILMT-deployment process and the relationship with IBM to see if there may be other defenses against the ILMT requirement. Here are three examples:

  • It really is IBM's fault. Sometimes, prior to an audit, a business will have signed an agreement with IBM for implementation services related to one or more sub-capacity-licensed products. If, in that agreement, IBM expressly or even impliedly undertook any responsibility to ensure that the products being deployed were correctly licensed – and then failed to deploy ILMT as part of the implementation project – then it may be possible to obtain a concession with regard to adverse audit findings affecting those products. Again, however, what is typically needed here is an agreement with IBM and not merely an authorized IBM reseller. If a reseller failed to deploy ILMT as part of such a project, IBM may agree to deeper discounts or other pricing concessions during negotiations to resolve the audit findings, but it typically will not agree to concede the findings altogether.
  • ILMT Does Not Work. ILMT is not an easy product to deploy or to use, and many businesses experience technical problems in attempting to implement it. If an audited company can show that it has tried to use ILMT and has sought assistance in getting the tool to work, then it may be possible to secure concessions with regard to adverse audit findings. However, the likelihood of success for this line of argument will be heavily dependent on the facts of each case. When did the company first try to deploy ILMT? Was it for the complete virtualization environment or just for one IBM product? Was IBM support contacted regarding the problem? What problems were reported regarding ILMT implementation? How diligent has the business been in working with support to resolve the problem? All of the above questions would be relevant to determining whether and to what extent any ILMT-deployment problems could affect the outcome of an IBM audit.
  • Sub-Capacity Levels Never Were Exceeded. Even if IBM never undertook any responsibilities for ILMT deployment and the licensee wholly failed to even try to install the tool, there is a third, potential option for avoiding adverse audit findings associated with that failure – historical reporting. If the audited business can produce historical, system-generated reports demonstrating (1) that the processor resources allocated to VMs running PVU-licensed products are and have been definitively capped and not subject to any automated augmentations based on system demands, and (ideally) (2) that historical usage of sub-capacity licensed products has not exceeded licensed levels, then it may be possible to avoid adverse findings associated with an ILMT deficiency. However, in our experience, relatively few businesses are able to produce historical reporting that satisfies IBM's requirements. In addition, even in the best cases, the outcome may be discounts or other pricing concessions and not alterations to the audit findings. Absent a separate agreement signed by IBM, no business should count on any non-ILMT reporting to satisfy IBM as being an acceptable substitute to the ILMT requirement described in IBM's license agreements.

Finally, it is important to keep in mind that even if any or all of the arguments above is successful, IBM still will insist that the audited company deploy ILMT going forward as a condition of settlement. Thus, if a decision has been made to reject ILMT under any circumstances, it may be necessary to formulate a different strategy for contending with the adverse audit findings.

IBM audits always are very fact-intensive exercises, and no two ever are exactly the same. Companies facing unexpected licensing shortfalls identified during an audit should consult with counsel or knowledgeable licensing advisors to determine whether the above arguments – or any other arguments – may help to mitigate the exposure associated with those shortfalls.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Christopher Barnett
In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.