Dec 11, 2019 - 03:15 AM
1. Does this mean IBM have a programme running to enable other SAM/ITAM tools to be certified as ILMT-equivalents. As far as I know, only Flexera Flexnet is considered at least partly certified as an ILMT replacement. As HCL are a completely independent company I don't see why/how IBM could restrict other tool providers from becoming certified
2. Q11 on the faq states:
"11. Will products divested to HCL be update in ILMT’s product catalog?
IBM will not be updating ILMT’s catalog for new releases of products divested to HCL. "
Given that there are bunch of products sold to HCL that could have been licensed by PVU that begs the question - how are HCL now licensing them? What do you need to do to qualify for sub-capacity licensing?
Dec 11, 2019 - 05:24 PM
I also suspect that the 'certification' discussed is a marketing tool likely agreed in the divestment. It seems silly and unnecessarily circular to have to certify a product IBM asked to be developed for them. I imagine the process is there to meet their own internal compliance demands. They need to prove to shareholders that they are protecting the value of investments made. Flexera was approved as a replacement, however if you read the fineprint usually Flexera needs ILMT to feed it content for the configuration to be approved. It was never a way to avoid ILMT completely for most clients.
In regards to monitoring divested products - IBM retain the right to audit for up to 2 years after your contract ends. If a client no longer holds IBM product but is running PVU products that were divested, I would strongly recommend they run ILMT for a few years to avoid risks. I'm not sure about HCL's contractual obligations and it's yet to be seen how they plan to evolve product metrics.
Dec 23, 2019 - 01:09 AM
Since June 30 th 2019 BigFix has become a HCL product. What does this mean for your IBM Sub-capacity support and reporting obligations conform Passport Advantage agreement (PA).
IBM’s default is based on Full-capacity, but in most cases Sub-capacity is financially very attractive.
Generally IBM allows 4 methods of reporting to adhere to IBM Sub-capacity conditions:
1. Reporting with IBM’s License metric tool (ILMT)
2. Reporting with Flexera FlexNet Manager Suite (FNMS)
FNMS can be used after a signed PA addendum agreement by both IBM and the customer, and the technical implementation is done correctly.
3. Manual Reporting is allowed:
When ILMT does not yet support the virtualization environment or product
Client is not a Service provider and
Client has not contracted with a Service provider and
Client has < 1000 employees and
Client has < 1000 PVU
4. Reporting with HCL’s BigFix tool
IBM and HCL have established a collaboration agreement aimed to continue to have BigFix accepted as an alternate solution to ILMT for IBM Virtualization Capacity reporting (Sub-capacity).
When requested by HCL, IBM will perform validation of BigFix Inventory updates to verify equivalence to ILMT version/release/updates.
The following lists BigFix Inventory versions/releases/modifications (V/R/M) that have been validated by IBM for equivalence to the corresponding V/R/M of ILMT for IBM Virtualization Capacity reporting requirements.
· ILMT 9.2.x (GA 20 March 2015). Validated BigFix equivalent 9.2.x
· ILMT 9.2.15 (GA 26 March 2019). Validated BigFix equivalent 9.2.15
· ILMT 9.2.16 (GA 08/05/2019). Validated BigFix equivalent 126.96.36.199
In the event that HCL opts to terminate the validation process of BigFix Inventory or if the BigFix Inventory is not validated, Customers will be given up to 6 months to move to ILMT (or other IBM-approved sub-capacity licensing tool) to continue to meet the requirements for IBM Virtualization Capacity licensing. Customers can continue to use BigFix Inventory to generate audit reports during this time frame.
Carefully planning is necessary for new eligible processors, operating systems or virtualizations. BigFix support for new eligible processors, operating systems or virtualizations in relationship to IBM virtualization Capacity will be available only after validation has been done by IBM. Customers should wait for IBM validation of BigFix Inventory before using it on newly added operating systems, virtualization platforms or processors supported by ILMT.
See following link for additional information:
For more information on these specific Sub-capacity conditions, please contact me to help you to choose the best option to be compliant and save money.
Dec 23, 2019 - 01:58 AM
Have to say that this seems to be completely impractical:
"Carefully planning is necessary for new eligible processors, operating systems or virtualizations. BigFix support for new eligible processors, operating systems or virtualizations in relationship to IBM virtualization Capacity will be available only after validation has been done by IBM. Customers should wait for IBM validation of BigFix Inventory before using it on newly added operating systems, virtualization platforms or processors supported by ILMT"
Did it also apply to ILMT? How frequently was the ILMT catalog updated? And is there a lag between an ILMT catalog update and BigFix being updated?
Dec 23, 2019 - 02:23 AM
This quote from PassPort Advantage:
For Sub-Capacity usage of EPs, Client agrees to install and configure the most current version of IBM's license metric tool (ILMT) within 90 days of Client's first Sub-Capacity-based Eligible Sub-Capacity Product deployment, to promptly install any updates to ILMT that are made available, and to collect deployment data for each such EP. Exceptions to this requirement are i) when ILMT does not yet provide support for the Eligible Virtualization Environment or Eligible Sub-Capacity Product
So an exception exist when ILMT does not yet support the new environment.
May 12, 2020 - 11:29 AM
Have you had a problem with "new eligible processors, operating systems or virtualizations" not being compatible with BigFix Inventory?
I am just wondering because in 5 years of use, I have never encountered such a problem. Most of our issues have been with missing signatures and collecting hypervisor hardware data such as Sun/SPARC serial numbers and accurate license snapshots for 3-tier vurtualizatino hiearchy - physical server/global zone/zone.