IBM

Licensing
Tools
ILMT and IBM
License Service

User Guide

Effective: January 2022

Last update: August 2022

2 Version History IBM Licensing Tools

Version History

Version Updates

February 2022 – Initial version

April 2022 – Added detail regarding the various possible configurations of ILMT, and the
components of ILMT which are necessary for a functioning system.

– Provided further context relating to how ILMT discovers components and

assigns them to programs (using the built-in software catalog or software
tags).

– Added content to the IBM License Service section reflecting the recently added
capability to account for Hyperthreading and Simultaneous Multithreading
(SMT), and provide links that explain how to enable this functionality.

– Updated the ILMT Lite Scenario to explain that ILMT Lite is now pre-approved
for environments up to 500 virtual environments.

– Added a new Scenario relating to the recently announced Flexera One

products.

August 2022 – Added detail regarding ILMT capability to collect metrics other than capacity
based.
3 Contents IBM Licensing Tools

Contents

Overview 4

Key Terms 4

Introduction 5

Detail 7

Scenarios 19

FAQs 21

Further Reading 25
4 Overview IBM Licensing Tools

Overview
The use of an approved license metering tool is necessary to comply with the eligibility requirements of
IBM Virtualization Capacity licensing policies for Sub-Capacity and Container Licensing. Clients often have
difficulty ensuring that their deployment of these tools is complete and accurate. An improperly configured or
incompletely deployed metering tool may report inaccurate license requirements. It may also mean that the
client does not meet the Sub-Capacity or Container Licensing terms and is therefore required to license its
IBM programs on a Full-Capacity basis. This can lead to significant findings in an audit context.

This guide is intended to provide information and best practice on setting up and managing the two IBM
license metering tools: IBM License Metric Tool (ILMT) and IBM License Service. ILMT is one of the two eligible
tools which clients must deploy to take advantage of Sub-Capacity licensing; IBM License Service is the only
tool which allows clients to take advantage of Container Licensing.

This guide describes relevant scenarios and best practices but it is not intended to provide advice for specific
client circumstances. Always consult your IBM representative should you have any questions or concerns
about ILMT and IBM License Service tools in your IBM estate.

Key Terms
The following terms are used throughout this document and are fundamental to understanding its contents.
This is not an exhaustive list, and some concepts may be discussed in other licensing guides or rely on
assumed knowledge.

Activated Processor Core International Passport Advantage Agreement

(“IPAA”)
A processor core that is made available to an
IBM program, either in a physical or virtual An agreement which sets out licensing terms for
machine, regardless of whether the capacity of all IBM programs licensed under the Passport
the processor core can be (or is) limited through Advantage program. It is available here.
virtualization technologies, operating system
commands, BIOS settings or similar restrictions. International Passport Advantage Express

CPU Limit Agreement (“IPAEA”)

A setting which constrains the processing An agreement which sets out licensing terms for
capacity consumed by containers in a Kubernetes all IBM programs licensed under the Passport
Namespace. Advantage Express program. It is available here.

Full-Capacity Kubernetes

The licensing of all the activated processor cores A program which manages (or “orchestrates”) the
installed on the physical machine. In other words, running of containerized applications. Kubernetes
the licensing of the full processing capacity of the is a management platform and can manage
physical machine. multiple types of container technology.

IBM License Metric Tool (“ILMT”) Kubernetes cluster

An IBM tool used to measure consumption of One or more worker nodes working together to run
certain IBM software metrics. Use of ILMT or containerized applications.
HCL BigFix Inventory is one of the eligibility
requirements for Sub-Capacity licensing.
5 Overview
Introduction IBM Licensing Tools

Pod Virtualization Capacity

A set of one or more containers running on Methodology to measure consumption of licenses

Kubernetes. only for the CPU cores consumed by the virtual
environment(s) where the IBM program is
Service Provider installed. The alternative is Full-Capacity, in which
license consumption is calculated based on the
An entity that provides information technology entire processing capacity of the physical machine
services for end user clients, either directly or or infrastructure.
through a reseller. This term is defined in the
IPAA (clause 1.14), IPAEA (clause 1.10) and IPLA Worker Node
(clause 11).
A machine that provides a containerized
vCPU environment for running tasks.

Virtual Central Processing Unit. In IBM licensing, a Worker Node Capacity

vCPU is also referred to as a Virtual Processor Core
(VPC). For those processors where hyperthreading The total capacity available to the worker node,
or simultaneous multithreading (SMT) is enabled, measured by either virtual or physical processor
a vCPU represents an available thread of the cores.
physical processor core.

Introduction
Assumed Knowledge
This guide assumes knowledge of the following These reports must be completed at least
topics which are the subject of other guides. They quarterly, retained for a period of two years, and
are all available on this page. provided to IBM and/or its auditors on request.
Failure to do so, or failure to correctly configure the
– Virtualization Capacity: Sub-Capacity
tools, requires the IBM programs to be licensed on
– Virtualization Capacity: Container Licensing a Full-Capacity basis.

– Cloud Paks

– Public Cloud Mandatory tools license usage

Tracking and reporting
IBM’s Licensing Tools
ILMT and IBM License Service are IBM license
Traditional Kubernetes
metering tools, use of which is generally required
to take advantage of IBM’s Virtualization Capacity
VMs/LPARs
licensing. The tools perform the task of identifying Private
&
IBM programs and counting the number of licenses &
Physical
required under certain capacity-based license Public Cloud
Servers
metrics. They measure license use frequently
and track this over time so that reports can be
License
generated that demonstrate the peak license use ILMT
over a defined period. Service
6 Introduction IBM Licensing Tools

ILMT
ILMT is a tool developed by IBM and provided free of charge. It is required for metering and reporting license
usage of IBM products deployed in “traditional” virtualization environments to take advantage of Sub-Capacity
licensing. IBM approves the use of certain alternate tools in lieu of ILMT. These are listed on the official IBM
Sub-Capacity Licensing page.

IBM License Service

IBM License Service is the only tool permitted by IBM for clients to take advantage of the benefits of IBM
Container Licensing. Like ILMT, it meters and reports license usage based on capacity made available to
IBM programs (that is, the ‘cpu_limit’ settings of the containers where IBM programs are deployed), but it is
specific to deployments in containers managed by Kubernetes.

In addition to IBM License Service, IBM License Service Reporter allows you to consolidate IBM License
Service reports across multiple Kubernetes Clusters to present the aggregated peak license use of each IBM
program across all relevant clusters. IBM License Service Reporter also accepts ILMT as a data source, so that
you can report your Virtualization Capacity license use across both traditional virtualization technologies and
containerized deployments in one report.

The key points of similarity and difference between ILMT and IBM License Service are summarized in the table:

ILMT IBM License Service

Purpose To allow clients to take advantage of IBM Virtualization Capacity licensing. Identifies IBM
programs, counts their license requirement and records this periodically to enable the
reporting of peak license use across a specified period.

Supported Technologies Traditional virtualization technologies such Containerized deployments of IBM

as VMware, Hyper-V, PowerVM. programs on environments which are
managed (orchestrated) by Kubernetes.

Where is it deployed? An agent is installed on each virtual (or Installed as a self-contained Pod on
physical) machine with IBM program(s) each Kubernetes Cluster upon which
installed. IBM programs are running.

How does it discover IBM Components are discovered using software Uses Kubernetes Annotations to identify
programs? ID tags. A software catalog is used to IBM programs, relationships between
match these to IBM programs and identify programs (Bundled or Supporting, Cloud
bundled and supporting programs. Paks, and so on) and license metrics.

Creating Reports Each ILMT Managing Server will report all Will only report those installations in
deployments reported by agents connected the same cluster. IBM License Service
to it. Reporter can be used to aggregate
these reports from multiple IBM License
Service installations, otherwise this
must be performed manually.

This guide discusses ILMT and IBM License Service in greater depth than in the relevant Virtualization
Capacity license guides.
7 Detail IBM Licensing Tools

Detail
ILMT Key Configuration Steps
ILMT is a free of charge IBM program which There are five steps that must be performed upon
operates on a client-server basis. Agents are initial installation and configuration of ILMT:
installed on each virtual (or physical) machine
on which IBM programs are deployed and are
configured to ‘talk’ to the ILMT Managing Server to
1 Install and update ILMT
report measurement data on a periodic basis.
2 Configure the hardware and software scans
ILMT’s main purpose is to:

– Discover and report the IBM products 3 Classify the identified components
deployed on your distributed (Linux/Unix/
Windows) systems.
4 Review the license usage report
– Identify the hardware configurations (both
physical infrastructure and virtual environment
configuration settings) for “traditional” and 5 Generate the Audit Snapshot and archive it
eligible virtualization technologies such as
VMware, Microsoft Hyper-V and IBM PowerVM.

– Measure and record the license use of Subsequent changes to the IT environment or
identified IBM programs which have a deployment of IBM programs will require these
capacity-based license metric such as PVU or steps to be reperformed: for example, adding a
VPC. new virtual machine will require a new installation
and configuration. Steps 4 and 5 will need to
The requirement under IBM Virtualization Capacity be performed each time you generate a license
licensing is to generate complete and accurate use report, which should be carried out at least
reports of your license use at least every quarter quarterly.
and to retain these reports for two years. They
must be made available to IBM and its auditors If you encounter difficulties properly installing
upon request. and configuring ILMT in accordance with these
steps, best practice is to ensure that you open
an IBM Support call to record that you have
ILMT, like any other program, must be installed, encountered issues. This can be an important
configured and managed carefully. Merely reference point in any subsequent audit. However,
installing ILMT will not give you the reporting opening an IBM Support call does not remove
capability necessary to comply with the or relax the Virtualization Capacity eligibility
Virtualization Capacity licensing rules. It is not requirements for the associated IBM program
‘set and forget’. deployments. IBM Support calls are intended to
be used cooperatively to address any impediment
to compliance with the requirement to use ILMT.
If a client provides a support ticket as evidence
While this document provides guidance and for difficulties in installing ILMT, or creating and
best practices, always reference the official and retaining the required license use reports, we
comprehensive ILMT product documentation. reserve the right to review this to determine
whether prompt and reasonable steps have been
taken to comply and whether a real technical
impediment has prevented compliance.
8 Detail IBM Licensing Tools

The five steps are discussed in more detail below: once installed, are automatically gathering
capacity data and IBM Software inventory that
Step 1: Install and update ILMT: are stored into output packages on the local
VM/LPAR. Clients can use their own solutions
ILMT is an IBM program licensed through Passport
to support deployment of ILMT disconnected
Advantage with dedicated part numbers for the
scanners and data gathering of outputs
Base License and for annual S&S. Even though
packages generated by the ILMT Disconnected
there is no license charge for ILMT, you need to
Scanners to transfer them into a central
have the base license and active S&S on your
location for ILMT to import and use.
entitlement records. The part numbers required
and instructions on how to order ILMT are
documented here. This support page provides
reference links to the ILMT software download of If you wish to use the ILMT Lite configuration
ILMT packages accordingly to the provided ILMT (or you already use this configuration) and
deployment options with references to the ILMT you have more than 500 VMs and LPARs in
product documentation. scope for Virtualization Capacity, you must get
approval from IBM. Please contact your IBM
ILMT provides three deployment options to representative or send email to talk2sam@
accommodate clients’ environments and license [Link].
usage metering needs:

– ILMT with HCL’s BigFix platform: For clients

who already use HCL’s BigFix products or Regardless of the deployment option chosen, all
those who require the endpoint management require the installation of:
capabilities of HCL’s BigFix platform. The
– The ILMT Managing Server
platform manages the deployment and status
of ILMT scanners, schedules software scans – The ILMT Database
and consolidates the data retrieved and
imports them into ILMT. It is a highly scalable – The ILMT Agent or Disconnected Scanner
platform, capable of managing hundreds of
thousands of VMs or LPARs where clients The ILMT Managing Server
require Virtualization Capacity licensing. The ILMT Managing Server can be deployed on
either Red Hat Enterprise Linux (RHEL) for x/86 or
– ILMT with Red Hat Ansible: For clients who
on a supported Windows Server operating system.
already use Red Hat Ansible or are looking
The ILMT managing server’s reporting capabilities
for an alternative task automation solution to
allow you to generate reports for specific purposes
support environments of scale. Ansible can
using only one installation of the ILMT Managing
be either the open source or commercially
Server, such as:
supported product. ILMT with Ansible is a
pre-approved deployment configuration. We (a) Generating reports by IBM Sub-Capacity
recommend ILMT version 9.2.26, released in Regions
December 2021, is used. ILMT with Ansible
uses the ILMT Disconnected Scanner to (b) Generating reports by Passport Advantage sites
automatically collect deployment data from
(c) View license use per business unit (for internal
endpoints.
chargeback purposes)
– ILMT Lite: A highly simplified deployment
(d) Aggregating VMs/LPARs by ILMT Computer
of ILMT suitable for clients with a small
Groups and generating license usage and audit
Virtualization Capacity environment. ILMT Lite
reports by Computer Group. For more information
is pre-approved by IBM for up to 500 target
please read the tutorial provided in the ILMT
VMs or LPARs. ILMT Disconnected Scanners,
documentation.
9 Detail IBM Licensing Tools

The ILMT Database Updates

If the Managing Server is deployed on RHEL, the ILMT is updated every quarter with new features
only supported database is IBM DB2. This program and fixes. New features include support for
is included in the ILMT software package and is updated virtualization technologies and operating
licensed as a Supporting Program for ILMT. It may systems, updates to the PVU Table and the
only be used for the purposes of supporting the software catalog, as well as security updates
functionality of the ILMT Managing Server. and support fixes. ILMT versioning takes the
form “9.2.x” where x is incremented with every
If the ILMT Server is deployed on a Windows quarterly release.
Server operating system it requires an installation
of Microsoft SQL Server database. This is not You must keep ILMT up to date and current
included in the ILMT software package and must in order to use the latest PVU table and IBM
be provided by the client. software catalog and to enable support for the
latest environments. The latest PVU table and IBM
For more information on how to install the ILMT software catalog are included in the ILMT Server
Server and database: component. This means you do not need to update
– with HCL’s BigFix platform please refer to this all the components separately every quarter: in
link. most cases an update of the ILMT Managing Server
will suffice.
– ILMT with Ansible and ILMT Lite prefer refer to
this link. Documentation on updating ILMT is available here.
Further helpful links include:
The ILMT Agent or Disconnected Scanner – A summary of new features each quarter
ILMT with HCL’s BigFix platform: You must deploy
– A detailed list of ILMT application updates and
the ILMT Scanner together with the BigFix agent
content
on every physical or virtual machine where IBM
programs are deployed for which you wish to – “My Notifications” allows you to subscribe to
apply sub-capacity licensing. This includes non- be notified of any updates to documents
production environments.

ILMT Lite and ILMT with Ansible: Similar to ILMT

with HCL’s BigFix platform, you must deploy the
ILMT Disconnected Scanner on every virtual
machine where IBM programs are deployed
for which you wish to apply sub-capacity
licensing, and on every physical machine where
IBM programs licensed under Full-Capacity
are deployed which you wish to include for
completeness purposes. This includes non-
production environments.
10 Detail IBM Licensing Tools

Step 2: Configure the Hardware and Software scans

The ILMT product documentation describes how to setup hardware and software scans, best practices and the
required configurations. There are two relevant documents:

– For BigFix deployments

– For disconnected scanners

The following points are also important to ensuring a complete and accurate scan of hardware, software and
related license counts:

Consideration More Detail

Cessation of eligibility IBM maintains a list of all eligible virtualization technologies here. However, as Link
for legacy virtualization platforms age and their vendors cease mainstream support, technologies cease to
technologies be eligible for Virtualization Capacity. IBM typically waits 180 days after the vendor
has ceased mainstream support before removing eligibility, so that most clients will
have already moved off the affected platforms. A regularly updated list of impending
changes to eligibility is kept at the link to the right.

If you do not move your IBM programs to an eligible platform, once eligibility
has ceased these installations must be licensed on a Full-Capacity basis.

x86 Virtualization: VM For certain x86 virtualization technologies such as VMware and Hyper-V, ILMT Link
Manager Configuration must collect hardware capacity data from the infrastructure used to deploy any
virtual machines. This is required to calculate any caps on the number of activated
processor cores or other capacity measures, as well as to assign the correct “PVU
per core” value for each activated processor core made available to an IBM program
licensed with the Processor Value Unit (PVU) metric.

To achieve this, ILMT needs to use an additional component called “VM Manager”.
The VM Manager connects to the Hypervisor and gathers information relating to the
hardware configuration of host machines and clusters.

Failure to configure the VM Manager will result in ILMT using default

placeholder values for PVU per core, and ILMT will also be unable to limit the
number of licenses to the processing capacity of the host. It is likely ILMT will
report an increased license requirement as a result.

ILMT’s default behavior is to consider each virtual machine as a physical machine

and to assign 120 PVUs per core to each activated processor core. Use of the
maximum 120 PVUs per core rating ensures that you are not under-licensed, but
your processors may only require 70 or 100 PVUs per core.

When Virtualization data are missing the Server Name on which the VM/LPAR is
hosted on is reported by ILMT with the TLM_VM prefix followed by the UID (unique
identifier) of the VM/LPAR too and the Computer status within the Hardware
inventory report of ILMT is set to No VM Manager Data.
11 Detail IBM Licensing Tools

Consideration More Detail

Public Cloud You do not need to configure ILMT’s VM Manager component unless you are fully BigFix: Link
managing the Hypervisor of the server too. However, you must configure the ILMT
agent or apply a “Tag” to the servers so that ILMT will apply the flat rate of 70 PVUs Disconnected
per vCPU, as per the BYOSL policy for Eligible Public Clouds. Scanners:
Link
If you do not do this, ILMT will apply a rate of 120 PVUs per vCPU.

LMT Disconnected ILMT Disconnected Scanners are used by ILMT Lite and ILMT with Ansible ILMT
Scanners deployments by default. ILMT Disconnected Scanners can also be used with ILMT Disconnected
with HCL’s BigFix platform configuration deployment when a machine with IBM Scanner
programs installed does not have connectivity to an ILMT Managing Server, or it is
not feasible to create this connection. The ILMT Disconnected Scanner can then be
used to collect the hardware and software information to be loaded into the ILMT
Managing Server.
12 Detail IBM Licensing Tools

Step 3: Classify the identified Newer releases of IBM programs make use of
software identification tags (as defined by ISO
components
19770-2). These tags reside in the file system.
Software classification is a key step in ensuring an ILMT finds and uses these to identify the
accurate inventory of IBM programs so that the components of IBM programs.
related license usage reports can be created for
Virtualization Capacity. The Overview and Key Concepts sections of the
ILMT documentation provide more information
ILMT discovers software components, and about how the ILMT Software Catalog is
maps these components to products based on conceptually organized: from software signatures
data contained in a software catalog which is to components to related products.
loaded into ILMT and must be kept up to date
as IBM releases updates so that the software While the ILMT product documentation discusses
identification is as complete and accurate as the related tasks needed to classify IBM products
possible. The software catalog is a collection of in some detail, ILMT also has some built-in logic
definitions of software products, their relationships and processes to assign discovered components to
and signatures that are used to detect software as IBM programs. The following guidance will help to
installed or used in an IT environment. ensure this is performed accurately:

Consideration Description

Currency of the The ILMT software catalog is updated every quarter along with ILMT Managing Server updates
Software Catalog and will often be updated automatically if you update your ILMT Server promptly. Failure to
keep the software catalog updated may cause inaccurate software classifications which would
need manual intervention to rectify until the software catalog is updated to the latest version.

Bundled and ILMT discovers software components and assigns them to IBM programs. Some components
Supporting Programs may be included as a Bundled or Supporting Program of a Principal Program and are therefore
not licensable themselves if they are used in accordance with the terms of the License
Information document.

ILMT’s software catalog contains the definitions of IBM programs, including non-chargeable
components. Keeping the catalog up to date is therefore important. The catalog enables
ILMT to make decisions automatically as to the status of Bundled or Supporting Programs
when these are installed on the same machine. Where these programs are installed across
multiple machines ILMT will be unable to determine the relationship between these programs.
This therefore requires manual intervention during software classification to mark relevant
installations as Bundled or Supporting.

Where the License Information document specifies that a license is required for the use for the
program as a whole and Bundled or Supporting Programs are installed on multiple machines,
these bundled or supporting programs must be assigned to the Principal Program name so
that the license calculation can be performed across the entire installation footprint. See the
‘Bundled and Supporting Programs’ license guide on the Guides page for more information.

Part Numbers Always import the list of part numbers that you have entitlement to and which you are Link
deploying.

While ILMT will use the software catalog to identify IBM programs from the installed
components, ILMT will perform a ‘best guess’ as to which IBM program the components
belong to. Importing your entitled part numbers increases ILMT’s accuracy as it narrows down
the number of possible IBM programs which a discovered component can be assigned to.
13 Detail IBM Licensing Tools

Consideration Description

Use comments It is possible to exclude discovered components from the license counts, or to suppress them
from the reports entirely. When doing so you are required to provide a comment to explain your
reasons.

Be as accurate and descriptive as possible when providing comments. Add IBM Support Ticket
numbers (TSxxxxxx) or any Problem Management (PMR) numbers to clarify the situation and
provide a trail for IBM to follow in our own internal documentation.

These comments can be useful in an audit context to justify exclusions.

Cloud Paks IBM Cloud Paks can also be deployed on traditional virtualization technologies, either solely or Link
as part of a hybrid approach including containerized deployments.

If you are deploying programs that are licensed within one of the IBM Cloud Paks, you must
classify them in ILMT as belonging to the IBM Cloud Pak program so that ILMT can perform
the correct license use report.

This is a two-step process:

1. First, assign the discovered components to the related IBM program and the correct
license metric
2. Then, assign the IBM program to the related IBM Cloud Pak.
14 Detail IBM Licensing Tools

Step 4: Review the license usage reports Regularly review the licensing usage
The primary source of information about license data to avoid pitfalls
usage is the “All Metrics” report. The report can To ensure completeness and accuracy of license
be filtered to show the relevant IBM products and usage data within your reports, ensure:
PVU and VPC license metrics for which you need
to generate and archive the related quarterly audit – All devices where you have deployed IBM
snapshots. You can also drill down further: products are included in the report and
software scan data is collected from the entire
– Clicking the product name shows a list of environment. To verify whether there are any
components classified as belonging to the problems, check the Software Scan Health
program (as performed during software widget on the Overview panel.
classification)
– Capacity data is collected from the entire
– Clicking the metric quantity shows a list environment and the proper PVU per core
of machines where the program has been values are being used. To verify whether there
installed and deployed, along with related are any problems, check the Capacity Scan
license use data Health widget on the Overview panel.
For every product, you can specify a metric – Software instances have been correctly
threshold to verify whether metric utilization is classified. Verify that IBM products licensed
above or below your expectations. For example, under IBM Cloud Paks have been properly
you could set your threshold to be the number assigned to the related Cloud Pak they a
of licenses that you hold to each IBM program, component of.
enabling you to easily see whether you require
additional licenses. – Verify that data imports have been successful.
To check the import history, go to ILMT Web
You can also create a snapshot of the report, UI: Management > Data Imports.
and store it for audit purposes (see the following
paragraph for more info: Generate the Audit
Snapshot and Archive it)

Make sure the reported license data is

current
In the “All Metrics” report or any other reports
such as the “PVU Sub-Capacity report”, look out
for red square icons within any of the values of
the metric quantity column. These red squares
indicate that the license usage data is not up to
date and must be recalculated. To address these
red squares, you need to click on the “recalculate”
task.

This situation might arise, for example, when you

perform software classification and make changes
to the classification of discovered components.
Changes will require a recalculation of the license
requirements.
15 Detail IBM Licensing Tools

Step 5: Generate an audit snapshot and Programs measured by metrics other

archive it than capacity-based
Eligibility for Virtualization Capacity requires the While ILMT has traditionally been used mainly for
generation of an audit snapshot at least quarterly the monitoring and reporting of license use for
and for these snapshots to be archived for at least programs measured on a capacity basis and for
two years so that they can be provided to IBM and/ eligibility for Sub-Capacity licensing, ILMT can
or its auditors on request. consolidate your license use across many metrics
and for IBM Programs that are not measured on a
The audit snapshot is generated from the capacity basis.
“All Metrics” or “PVU Sub-Capacity” reports
available in the ILMT Web UI. The process of This capability allows ILMT to function more as
generating the Audit Snapshot is set out in the a general Software Asset Management tool for
ILMT documentation. The Audit Snapshot is a IBM programs and enables a consolidated view
.zip package with a naming convention “audit_ of your IBM licensing position for each snapshot
snapshot_[date]_[time].zip”. The purpose of each generated on an (at least) quarterly basis.
file within the package is documented here, and
a fuller description of the contents of each file is Supported programs can be configured to count
documented here. the number of licenses required and store
this information locally in “Software License
The generated zip packages are digitally signed Management” (.slm) files files within the
to protect their contents from tampering. The installation directory of the program. The ILMT
package must be provided in full to IBM. Partial scanner will recognize these SLM files and import
or compromised audit snapshots can lead to them into the ILMT database along with the usual
your IBM programs being licensed on a Full- hardware and software configuration data.
Capacity basis.
IBM maintains a list of programs which support
How to review and reconcile the data included in this functionality. Each product and version is
the package back to the original ILMT reports (“All listed, along with a link to a page which explains
Metrics” or “PVU Sub-Capacity”) is documented how to enable the functionality.
here.
Generally, the steps to enable the functionality are
You can regenerate the audit snapshot at any as follows:
time for those dates where data is still available
in the ILMT database. If you need to update or 1. Install and configure the tool which creates the
regenerate the audit snapshot you can run it again SLM files (“SLMTool”)
and provide comments or attach additional files 2. Ensure that ILMT Scanner is installed on each
when generating them. machine where the SLM files need to be
picked up

3. Perform any necessary configuration

changes to the ILMT Scanner to ensure
that it successfully finds the SLM files (for
example, if the SLM files are being saved to
a non-standard location, or if the installation
directory of the IBM program has been
customized)

The ILMT documentation explains how ILMT

handles this information.
16 Detail IBM Licensing Tools

IBM License Service Key Configuration Steps

IBM License Service performs the same role There are three steps that must be performed to
for Container Licensing that ILMT performs for use IBM License Service correctly and generate
Sub-Capacity deployments. IBM License Service complete license usage reports to comply with
monitors the use of processing capacity over IBM Container Licensing:
time and enables you to create reports which
demonstrate the number of licenses needed to 1 Deploy IBM License Service
cover the peak level of use observed.

The Container Licensing policy covers the use of 2 Discovery of IBM programs
IBM programs in containerized environments. For
IBM licensing purposes, these containers must be
managed by a program called Kubernetes. This 3 Generation of audit snapshots
management is referred to as “orchestration”,
and so you will often see the term “Kubernetes-
orchestrated” in IBM documentation. If any of these steps is not properly performed, you
may need to be licensed on a Full-Capacity basis.
Unlike ILMT, IBM License Service does not require Always open an IBM Support call in case of issues
you to perform any software classification because with any of the required steps.
it makes use of Kubernetes Annotations to identify
which Pods belong to IBM programs. These
Annotations (which are conceptually similar to the
software tags used by ILMT) identify a program
as being standalone, or part of a bundled solution
such as a Cloud Pak. They also allow IBM License
Service to apply the licensing rules under the IBM
Container Licensing policy and to identify the
metric and applicable Cloud Pak ratios.

IBM License Service is included in the foundation

services which come with every Cloud Pak, so
it does not need to be ordered and licensed
separately for Cloud Paks. For other IBM Programs
available as standalone containerized software
(for example, IBM Certified Containers), which do
not include a copy of IBM License Service, you can
download the IBM License Service Operator from
GitHub.
17 Detail IBM Licensing Tools

Step 1: Deploy IBM License Service

IBM License Service is a Pod itself. For the most part it is automatically enabled when deploying IBM Cloud
Paks.

An instance of IBM License Service is required for each Kubernetes Cluster. A single instance of IBM License
Service will monitor all Cloud Paks or IBM containerized programs running on the same cluster as itself.
It uses Kubernetes capabilities to discover IBM programs and gather license usage-related data from the
running Pods.

To do this correctly, the IBM License Service Operator requires certain cluster permissions which are detailed
in the table below (although see the official documentation for the most up to date guidance):

API group Resources Verbs Description

‘blank’ pods Get The cluster permissions for the ibm-license-

List service service account are read-only access
namespaces permissions that are required to properly discover
the running IBM applications to report license
nodes usage of the Virtual Processor Core (VPC) and
Processor Value Unit (PVU) metrics.

[Link] servicecas List These permissions are required to generate the

TLS certificate for License Service.

[Link] ibmlicensings Create The cluster permissions for the ibm-

licensing-operator service account are
ibmlicenseservicereporters Delete required to properly manage the status of the IBM
License Service operator.
ibmlicensings/status Get

ibmlicenseservicereporters/ List
status
Patch
ibmlicensings/finalizers
Update
ibmlicenseservicereporters/
finalizers Watch

IBM License Service has minimal impact on the performance of the cluster: it works transparently in the
background and does not require any configuration or user engagement once enabled.

IBM Container Licensing requires physical cores to be counted. Processors which support Hyperthreading (or
Simultaneous Multithreading – SMT) present multiple “virtual” cores which IBM License Service must account
for when determining the number of physical cores in each Kubernetes cluster which need to be licensed. You
need to enable hyperthreading in IBM License Service for each cluster to ensure it properly accounts for this
and counts license usage accurately.

Please refer to the IBM License Service documentation for more information about how to verify
Hyperthreading enabled values for your Kubernetes cluster and how to configure your installation(s) of IBM
License Service accordingly:
18 Detail IBM Licensing Tools

Step 2: Discovery of IBM programs An example of what a Kubernetes Annotation

might look like is below:
IBM License Service uses Kubernetes Annotations
to identify the Pods running IBM programs Program Example Kubernetes Annotation
and which IBM program they represent. The
Annotations state whether the IBM program is IBM productID:
licensed on its own (i.e., standalone) or whether it WebSphere “87f3487c22f34742a799164f3f3ffa78”
Application
is part of a solution bundle such as an IBM Cloud
Server Liberty productName: “IBM WebSphere
Pak (i.e., whether it is a Bundled or Supporting
Core (PVU) - Application Server Liberty Core”
Program).
standalone
install productMetric: “PROCESSOR_VALUE_
UNIT”
Kubernetes Annotations are essential for IBM
programs to be eligible for the IBM Container productChargedContainers: “All”
Licensing policy and metered by IBM License
Service. Missing or inaccurate Annotations may IBM cloudpakName: “IBM WebSphere Hybrid
require a program to be licensed on a Full- WebSphere Edition”
Capacity basis. Application
Server Liberty cloudpakId:
Core licensed “6358611af04743f99f42dadcd6e39d52”
as part of an
The Kubernetes Annotations are applied to Pods IBM Cloud Pak productCloudpakRatio: “8:1”
automatically via the provided IBM Operators
for the related IBM programs. If IBM Certified productID:
Containers can be included in a client’s custom “87f3487c22f34742a799164f3f3ffa78”
application or custom deployments, IBM provides
productName: “IBM WebSphere
the appropriate Kubernetes Annotations in the
Application Server Liberty Core”
program documentation. You must ensure that you
reflect these Annotations correctly.
productMetric: “VIRTUAL_PROCESSOR_
CORE”

productChargedContainers: “All”
19 Detail IBM Licensing Tools

Step 3: Generation of audit snapshots

The Passport Advantage Addendum for Container Licensing requires you to generate license usage reports
at least on a quarterly basis. This is the contractual minimum frequency but we recommend that reports are
generated monthly to help you maintain compliance with your license limits.

An audit snapshot consists of the following files:

File name Content

[Link] The unique checksums that are a proof that the audit snapshot was not
tempered with.

data_condition.txt Audit snapshot metadata that includes information about the cluster, the time
and date when the report was generated, and the reported period.

products_<reported_ The highest license usage for each product that is deployed on the cluster within
period>_<cluster hostname>.csv the reported period.

products_daily_<reported_ The highest license usage for each product that is deployed on the cluster within
period>_<cluster hostname>.csv the reported period daily.

bundled_products_<reported_ The highest license usage for each bundled product that is included in the IBM
period>_<cluster hostname>.csv Cloud Pak solutions that are deployed on the cluster within the reported period.

bundled_products_ The highest license usage for each bundled product that is included in the IBM
daily_<reported_ Cloud Pak solutions that are deployed on the cluster within the reported period
period>_<cluster hostname>.csv daily.

pub_key.pem The public key file that can be used to verify the [Link] file against the
[Link] file.

[Link] A digital signature that can be used to verify whether the [Link] file was
tampered with.

unrecognized-apps- <reported_ A list of pods from which the license usage data was not collected on a specified
period>.csv date. The pods have incomplete or missing product annotations that provide the
product metadata that is needed for measurements. The information is provided
for every date within the reported period. The list contains the namespace
followed by a pod name.
20 Detail IBM Licensing Tools

You must retain each audit snapshot for at least

two years and provide it to IBM or its designated
auditors upon request. If an audit snapshot
demonstrates that you have exceeded your
entitled use, you must promptly order the required
number of licenses from IBM or an Authorized IBM
Reseller to maintain compliance.

When generating your audit snapshots, we

recommend you validate the completeness of the
license usage data and follow any of the provided
warnings as documented on IBM License Service
documentation.

Before you decommission a cluster, be sure to

generate the audit snapshot up to the day of
decommissioning and archive the snapshots.

IBM License Service Reporter

When IBM programs are deployed on multiple
Kubernetes clusters you need to report the
aggregated license usage across all clusters. You
may prepare a consolidated report manually,
but for IBM Cloud Paks you can use IBM License
Service Reporter. This is included in every Cloud
Pak.

The License Service Reporter is an extension of

IBM License Server which does the aggregation
across multiple clusters for you and consolidates
license usage data into a single report.

One central IBM License Service Reporter instance

is deployed on a cluster, and you can configure
the data sources which need to be aggregated.
This could be IBM License Service instances on
other clusters, or even ILMT instances that are
monitoring traditional virtual environments. This
enables you to have a consolidated view of your
license usage across both container and traditional
virtualization environments.

Please refer to the IBM Cloud Pak foundational

services documentation for more detailed
information on the License Service Reporter and
how to deploy, configure, and leverage license
usage reports and aggregated audit snapshots.
21 Scenarios IBM Licensing Tools

Scenarios
ILMT Lite The key steps for effective deployment and use of
ILMT Lite are:
If your environment consists of up to 500
computers (VMs/LPARs), you can opt to use the
ILMT Lite deployment configuration. ILMT Lite does Step 1: Install In the case of ILMT Lite, you need
not require the BigFix platform to be installed as and configure to install ILMT Server and its
it uses disconnected (stand-alone) scanners to (Lite scenario) database. Then, you need to install the
collect software and hardware information. disconnected (standalone) scanner on
every machine where you want to collect
ILMT Lite is pre-approved for up to a total of 500 hardware and software inventory data.
targets (that is, VMs and LPARs). Environments
larger than this require approval from IBM. Step 2: The application discovers software that
Classify is installed on your machines where
While standard ILMT configurations which use the
discovered the disconnected scanners have been
BigFix platform automate the scheduling of scan
software (Lite used. The components are automatically
result uploads, it is your responsibility to do this at
scenario) assigned to licensable IBM programs.
least once per week if you use ILMT Lite. These assignments must be reviewed
and either confirmed as accurate or
You can use one of the following approaches to
modified based on your knowledge of
upload scan results:
your license entitlement.

Manually upload the scan results

Step 3: Generate the audit snapshot periodically
This approach is not recommended as it is prone Generate (at least quarterly) and store it for at least
to errors and might cause delays in uploading the audit two years to remain eligible for Sub-
the data. These delays might in turn result in snapshot (Lite Capacity licensing.
inaccurate reporting. scenario)

Automate the uploads using Red Hat

Ansible
Failure to properly implement and manage any of
ILMT includes appropriate playbooks to achieve these steps may lead to your IBM programs being
this. This will significantly reduce the amount of licensed at Full-Capacity. The same guidelines,
effort required and the likelihood of errors. warnings and guidance in respect of standard ILMT
deployments apply also for ILMT Lite deployments.
Automate the uploads using
automation software of your choice View full ILMT Lite documentation here.

You are always responsible for ensuring timely,

complete and accurate uploads of data. ILMT and Red Hat Ansible
With effect from ILMT version 9.2.25, IBM allows
As with a standard ILMT deployment you need to you to use Red Hat Ansible (“Ansible”) Automation
properly install, configure, and manage ILMT Lite Platform in place of BigFix platform when
to generate accurate license usage reports and to deploying ILMT.
comply with the Virtualization Capacity terms.
22 Scenarios IBM Licensing Tools

Ansible can be used to manage the ILMT HCL BigFix Inventory

disconnected scanners but requires you to be
BigFix Inventory is now an HCL product; IBM and
able to configure and maintain Ansible without
HCL have established a collaboration agreement
support from IBM. Ansible is not included and
aimed at continuing BigFix Inventory’s acceptance
delivered with ILMT, and it is not supported by
as an alternative solution to ILMT for the purposes
IBM’s ILMT support provision. It is an open-source
of Virtualization Capacity.
program that is available free-of-charge or can be
commercially licensed from Red Hat with optional If you wish to use the HCL BigFix Inventory
support. Alternatively, you can use a commercially product instead of ILMT you must use an
available Ansible Tower product which includes accepted and IBM-validated BigFix Inventory
Red Hat support. version, release or update. See the FAQ for more
information about this.
The blueprints of the automation tasks run by
Ansible are known as “playbooks”. The playbooks Further information about HCL BigFix Inventory is
that are delivered with ILMT are the only part of available on HCL’s website.
the Ansible deployment that is supported by IBM
ILMT support.
Other approved Flexera One products
You can learn more about installing and configuring The following products are pre-approved by IBM to
ILMT disconnected scanners with Ansible here. be used in lieu of ILMT:
The same guidelines, warnings and guidance in
respect of standard ILMT deployments apply also – Flexera One IT Asset Management by Flexera –
ILMT deployments using Ansible. SaaS based solution

– Flexera One with IBM Observability IT Asset

Migrating/Moving/Reinstalling the ILMT Management by IBM – SaaS based solution
environment The Flexera One solution does not currently
There are circumstances where you might need support all virtualization technologies eligible for
to migrate or move your datacenters, replace or IBM Sub-Capacity licensing. ILMT must continue
upgrade systems with newer servers, or migrate/ to be used for eligible virtualization technologies
move your software deployments from on-premise which are not supported by Flexera One.
to public clouds. Any of these situations may also
require you to migrate your ILMT deployment. For more information about the eligible
virtualization technologies supported by Flexera
If such an event occurs, ensure that you perform One, please refer to the Flexera One section of the
the following tasks prior to decommissioning the Sub-Capacity licensing page.
legacy ILMT Server:
For more information about Flexera One with IBM
– Generate and archive the quarterly audit Observability IT Asset Management please visit
snapshots reports until you commission the the IBM product page.
new ILMT Server. They need to be archived for
up to 2 years.

– Back-up and archive the database used by the

ILMT Server, particularly if you are starting
afresh with a new database in the newly-
commissioned ILMT Server.

– Back-up and archive the ILMT Server image.

23 FAQs IBM Licensing Tools

FAQs
IBM License Metric Tool Is ILMT “set and forget”?
No. ILMT requires detailed configuration to
How can I be kept up to date with ILMT supported ensure it is reporting a complete and accurate
and eligible virtualization environments? measurement of the IBM software licenses
For updates on the development of ILMT, use required. In addition, key data sets used by ILMT
the ‘IBM Notifications’ portal to search for and to identify and measure the IBM software are
subscribe to notifications about ILMT. For example, updated periodically and included in the ILMT
search for ‘IBM License Metric Tool’ and then Server component, which needs to be updated on
select the document types you wish to be notified a regular basis.
about as changes occur.

For updates on eligible virtualization/processor Where should ILMT agents be installed?

technologies and products, please consult the
ILMT agents must be installed in every Eligible
Sub-Capacity Licensing page.
Virtualization Environment hosting Sub-capacity
Eligible Products. Additionally, for some
virtualization technologies, agents need to be
How frequently should ILMT reports be run? installed on system hosting virtual machines. You
The Virtualization Capacity terms require quarterly should also install ILMT agents on any backup
reporting at a minimum to remain eligible for server where IBM programs are deployed. You can
Virtualization Capacity licensing. This frequency then exclude such IBM Program instances from
should suffice for clients with stable environments PVU/VPC calculations if a license is not required
that are not subject to frequent change. Clients (typically warm/cold back-ups, but the license
with dynamic environments that are subject to requirement can vary by product). For specifics,
frequent change may prefer to run reports more refer to the product’s announcement letter by
often than this (for example, monthly or even searching the Offering Information page or the
weekly) to ensure that any additional license need product’s License Information Document by
is identified promptly. conducting a software license agreements search.

Each ILMT audit snapshot official report should be

kept for a period of two years and provided to IBM
Why do I need to order ILMT? What is the part
(or to the third-party auditor) on request.
number to use, and do I need to renew Software
Subscription and Support for ILMT?
IBM provides the same support for ILMT that we
Am I required to use ILMT even if I have an
do for our other mission-critical middleware. So
existing tool that provides the same information?
even though ILMT is a no-charge product offering,
Yes. The approved monitoring tools are the only an order must still be placed to establish an IBM
tools IBM considers capable of performing the entitlement record for the license as well as
ongoing monitoring of virtual environments software subscription and technical support (S&S)
to measure the maximum (peak) number of coverage.
activated processor cores made available to the
IBM software, and report these requirements as The initial order for ILMT should use Part Number
measured in IBM license metrics such as PVU and D561HLL. To maintain an entitlement record, S&S
VPC. must be renewed annually using Part Number
E027NLL. Please note that keeping ILMT up to
date is a requirement of the sub-capacity offering
terms and our guidance is to ensure that ILMT
Server is always updated with the latest version
of the IBM Software Catalog for accurate software
classification and Inventory. S&S renewal is
therefore a requirement for any client required
to use ILMT as it gives access to new versions,
releases and updates.
24 FAQs IBM Licensing Tools

IBM License Service and License Service If I have multiple clusters where containerized
Reporter software is running, does License Service need
to be installed on each cluster or does a single
Can I use IBM License Service on third party cloud installation suffice?
environments? In the case of multiple clusters, License Service
Yes, you can take advantage of our Bring Your Own is installed in each cluster where containerized
Software License (“BYOSL”) policy for deploying software is deployed (the client should verify
IBM software on Eligible Public Clouds. The installation and keep License Service healthy).
Eligible Public Clouds are listed on the BYOSL
page.
How can I consolidate license usage data among
multiple clusters?
What if I do not use IBM License Service? IBM License Service will output data that can
Clients who do not use IBM License Service will be used for this consolidation but this must be
be charged for all cores in the entire Kubernetes done manually. Alternatively, clients can use
cluster. This is because when using Kubernetes IBM License Service Reporter to automate this
containers can run on any node throughout the task with the option to incorporate outputs from
cluster. It is possible therefore that a single ILMT installations which monitor Sub-Capacity
program might have containers which take deployments as well.
advantage of the entire capacity of the cluster at
once.
How does IBM License Service Reporter work with
IBM License Service?
How quickly do I have to install IBM License IBM License Service Reporter collects and
Service? aggregates data from IBM License Service from
New Container Licensing clients are required to multiple clusters and from IBM License Metric
implement IBM License Service within 90 days Tool. For more details consult the IBM License
of their first Eligible Product deployment within a Service documentation.
container. For subsequent deployments the IBM
License Service must be deployed and enabled
immediately. Is it necessary to have IBM License Service on
disaster recovery or backup Clusters?
Yes. You need to install IBM License Service on any
What are the exceptions to the requirement to use disaster recovery or backup Kubernetes Cluster.
IBM License Service for Container Licensing? Any IBM Program running Pod within the disaster
There are no exceptions. recovery or backup Kubernetes Cluster will then be
counted for IBM Container Licensing.

Where does IBM License Service run in my

environment? How can I get IBM License Service?

IBM License Service runs in a Pod within a IBM License Service may come preinstalled when
worker node within the Cluster as determined by deploying containerized software via each IBM
Kubernetes scheduler. Cloud Pak’s services and within IBM Certified
Containers. Please verify the installation upon your
first container deployment. If IBM License Service
is not installed, contact product support.
25 FAQs IBM Licensing Tools

What is the part number used to order IBM Does IBM License Service report license usage for
License Service? “Monthly API Call” or other metrics aside from
There is no part number associated with IBM Processor Value Unit (PVU) and VPC?
License Service. IBM License Service collects information about
PVU and VPC metrics automatically for the
IBM programs which are enabled for reporting.
Does IBM License Service come with Red Additionally, IBM License Service can report
Hat OpenShift Container Platform (RHOCP) license usage for any other metric, including
entitlement? “Monthly API Call”. Enabling a program to be
measured by IBM License Service requires the
No. IBM License Service does not come with a free IBM product teams to incorporate the mechanism
RHOCP entitlement. License Service is included for delivering measurement data to IBM License
in the IBM Cloud Pak services and therefore Service into the program itself. If your program
leverages available RHOCP entitlements of the does not currently have this capability, and you
Cloud Pak or direct entitlements that the client would like it to have it in the future, please contact
obtains from Red Hat. When IBM License Service IBM Support. Understanding client needs in this
is being utilized outside Cloud Paks, you are area will allow IBM to prioritize the integration of
responsible for any overhead that License Service this feature appropriately.
may require.

Am I entitled to deploy IBM WebSphere Liberty

How much resource does IBM License Service throughout the cluster as part of an IBM Cloud
consume? Pak? Do I need to report the license usage of IBM
IBM License Service is a lightweight tool that WebSphere Liberty?
consumes very little resources. Please refer to First, you need to assess whether you are using
the knowledge center documentation for more a free version of IBM WebSphere Liberty, or an
information. IBM-supported version. License use does not
need to be reported for free versions. A proper
reporting mechanism of license use must be used
Am I required to use ILMT if I am using IBM for an IBM-supporting version. Check the IBM
License Service? WebSphere Liberty documentation or contact
If you are only running a containerized Support for details.
environment, then ILMT is not required. However,
ILMT is still a requirement for Sub-Capacity
environments. If you have a hybrid environment, Can I install IBM License Service in an offline
then both tools must be installed. environment without installing IBM Cloud Pak
foundational services?
Yes. You can use a standalone instance of IBM
Can I reset the values that are reported by IBM License Service for validation and testing. For
License Service? I have been testing IBM License more information, see the Offline Installation
Service to see how it reports Virtual Processor documentation.
Core (VPC) programs, or to understand how
changes to the deployments affects the reported
values. How can I check whether my IBM program is
No. You cannot reset the values that are reported enabled for IBM License Service reporting?
by IBM License Service. You can, however, change Review the product documentation. If the
the reporting period to compare how the metrics information is not there, contact Support.
are reported over time, or use a status page for
more details.
26 FAQs IBM Licensing Tools

Are service quota limits taken into consideration

when calculating license use?
No. The namespace quota limits are not
considered for IBM Container Licensing. For each
product, the CPU limits of Pods are considered
and capped at the capacity of the Worker Node(s).
Therefore, while the namespace quota is capping
the real use of capacity, it is possible for the
number of licenses required by Pods to exceed
the namespace quota because Kubernetes
could throttle, but not terminate, Pods when the
available CPU capacity is lower than “cpu_max”
or Pods are using less CPU resources than their
cpu_max setting. This mechanism is the result of
the Container Licensing rules.

Can I sign up for a demo of IBM License Service?

Are such sessions available?
No. There is no IBM License Service demonstration
environment for common access and use. In
addition, IBM License Service demonstration
sessions are not currently held. If you are
interested in setting up a demonstration
environment, enquire with your IBM Cloud Pak or
containerized IBM program product team.

I have IBM App Connect Enterprise (“ACE”) Virtual

Processor Core Hybrid Entitlement and the ACE
is installed on IBM Cloud Kubernetes. Can I use
fractional cores when calculating license use?
The products that you license are always licensed
according to your license agreement. For reporting
license use, IBM License Service measures
fractional values and rounds the totals to the
nearest whole number for each cluster.
27 Further Reading IBM Licensing Tools

Further Reading
IBM License Service Operator IBM Notifications
A GitHub repository providing information on IBM The IBM Portal where you can subscribe to
License Server and detailed instructions on how to notifications about various documents and keep up
deploy IBM License Service for Container Licensing. to date with the latest news that affects your IBM
[Link] licensing.
[Link]

IBM Cloud Pak Foundational Services

A page providing documentation relating to IBM Sub Cap Eligible Processor Technologies
License Service and IBM License Service Reporter. A list of processor technologies which are deemed
[Link] eligible for Sub-Capacity licensing.
tracking-license-usage-in-multicluster-environment- [Link]
license-service-reporter passportadvantage/SubCapacity/Eligible_Processor_
[Link]

IBM License Information Documents

A searchable repository of documents, each of which Sub Cap Eligible Programs
discusses in detail the licensing terms for an individual A description of the products that are eligible for Sub-
IBM program (or family of programs). Capacity licensing and a list of products which are not.
[Link] [Link]
passportadvantage/SubCapacity/Sub_Capacity_
Eligible_Programs.pdf
IBM BYOSL Policy on Public Cloud
The BYOSL policy detailing the terms and conditions
for deploying IBM software in an eligible public cloud. Sub Cap Eligible Virtualization and OS Technologies
[Link] A list of virtualization technologies and operating
eligible_public_cloud_BYOSL_policy.html systems which are deemed eligible for Sub-Capacity
licensing.
[Link]
IBM Cloud Paks passportadvantage/SubCapacity/Eligible_
A page that provides details and useful resources Virtualization_Technology.pdf
relating to IBM Cloud Paks.
[Link]
Sub Capacity License Counting Rules
Provides links to the documents which explain how
IBM Certified Containers to count the number of activated processor cores on
A page that details the features of an IBM certified various virtualization technologies.
container. [Link]
[Link] Counting_Software_licenses_using_specific_
private/3.2.0?topic=started-cloud-paks-certified- virtualization_technologies.html
containers

Technologies No Longer Eligible for Sub Capacity

International Passport Advantage Express A frequently updated list of technologies that will no
Agreement (“IPAEA”) longer be eligible for Sub-Capacity licensing, and the
The agreement relating to software licensed under date at which they case to be eligible.
Passport Advantage Express [Link]
[Link]/terms?id=Z125-6835

International Passport Advantage Agreement Flexera One with IBM Observability

(“IPAA”) The IBM product page for Flexera One with IBM
The agreement relating to software licensed under Observability.
Passport Advantage [Link]
[Link]/terms?id=Z125-5831
28 Further Reading IBM Licensing Tools

IBM Products that deliver SLM tags

The list of programs which can be configured to create
SLM files for ILMT to determine license use
[Link]

ILMT Documentation for collection and reporting of

‘Other Metrics’ data
The official documentation for ILMT which discusses
the reporting of license metric data for programs
measured by metrics which are not based upon
processing capacity.
[Link]
tool?topic=metrics-other
© Copyright International Business Machines Corporation 2022

IBM, the IBM logo, and [Link] are trademarks of International

Business Machines Corp., registered in many jurisdictions
worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM
trademarks is available on the web at “Copyright and trademark
information” at [Link]/legal/[Link]. This document
is current as of the initial date of publication and may be
changed by IBM at any time. The most recent version of this
document is published at [Link]/about/software-
licensing/licensing/guides.

Not all offerings are available in every country in which IBM

operates.

IBM Licensing and User Guides provide general guidance to

help clients navigate common IBM licensing and compliance
topics. The guides’ content is provided for general information
purposes only and is not intended as legal advice. IBM reserves
the right to review the materials from time to time and to amend
them to reflect changes in IBM’s licensing terms.

The guides do not supersede your license agreement with IBM.

For the exact terms and conditions which govern the usage of
a specific IBM software program, refer to the specific contract
terms, License Information Documents and any additional
agreements under which the software was obtained.

THE INFORMATION IN THIS DOCUMENT IS PROVIDED “AS IS”

WITHOUT ANY WARRANTY, EXPRESS OR IMPLIED, INCLUDING
WITHOUT ANY WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY
OR CONDITION OF NON-INFRINGEMENT. IBM products
are warranted according to the terms and conditions of the
agreements under which they are provided.

Questions and Comments:

If you have questions regarding the content of this user guide,

or any aspect of IBM’s licensing terms and conditions, please
contact us at [Link]/about/software-licensing/contact.