What are the options to connect to ILMT, TADd and Bigfix Inventory?
Snow offers out-of-the-box connectors for all of these sub-capacity eligible IBM technologies. The most popular technology is definitely ILMT since this is the only free of charge technology for this purpose. It is clear that there is much more benefit in using this connector than just seeing the data in Snow’s user friendly interface:
1.The first advantage we offer, which is highly appreciated by our customers, is to prevent the full-capacity risk thanks to the ILMT integration. Snow Inventory will determine machines not having ILMT agents where they should have been. Whenever PVU based software is identified on a machine through Snow Inventory where there is no PVU consumption data through ILMT, TADd or Bigfix Inventory, we will show these systems in a report so the customer can mitigate the full-capacity risk by installing ILMT on those machines. It is essential to understand your unknown unknowns since this is one of the highest risk areas during an IBM audit:
2. A second advantage is to be able to manage compliance and cost management in one single solution, being Snow License Manager. Since ILMT is merely a discovery tool, cost management and compliance management is not something you can manage within ILMT as a stand-alone tool. Furthermore, user friendliness is considered poor in ILMT.
3. A third advantage relates to optimization. Since we gather both the sub-capacity and full-capacity deployment values from the IBM SIM connectors, we can now identify environments where it is optimal to deploy new software or to move existing machines in order to lower the license requirements for IBM software. We are able to identify machines where products reside having sub-capacity license requirements equaling the respective full-capacity deployment values. This means the underlying physical hardware is fully utilized. Adding new machines to such environments would not require additional license requirements for the IBM product or savings could be accomplished in case Virtual Machines are moved to such environments:
Here-under you can find a short overview on the technicalities of the different connectors in the SIM. Please refer to the product documentation to have the latest and more detailed info:
Peter, why do you write that "ILMT is merely a discovery tool [...] and compliance management is not something you can manage within ILMT"? According to the International Passport Advantage Agreement, sections 1.13 and 1.14, ILMT is contractually obliged for this specific purpose.
What do you mean by "PVU consumption data"? Do you mean peak value for the product?
If a customer has BigFix/ILMT 9 and also the Snow Inventory client, which connecor delivers the best additional information or should they use both the ILMT CSV/API connector and the Bigfix Inventory Connector ? Does these SIM connectors result in additional software inventory and recognition ?
Snow License Manager relies on the integration connectors to gather the IBM related data. The Snow inventory client will gather a lot of information, both hardware and software related, but will not gather PVU/RVU related data. Specific IBM data is gathered by using integration connectors that will import data into Snow License Manager from ILMT, TADd or Bigfix.
The quality of data depends on the configuration of the tool the organisation is using to collect IBM related data.
The use of these connectors result in enrichment of total data set for IBM.
Hi, we are running the Bigfix connector and are getting duplicates in the Snow console. How do we ensure that the data hierarchy takes the data from the bigfix connector and not the snow agent?
We have the same issue. The Snow agent is giving fully qualified domain name for hosts running RedHat 7 or higher but ILMT report all without DQDN. Then we get dublicates since SLM is not able to match RH7-Host (ILMT) and RH7-Host.domain.com (SLM) ... For RedHat 6 the agent is reporting hostname only.
We do have the same situation as well, we import data from vCenter and from ILMT/BigFix which leads to duplicated VMware ESXi hosts in Snow License Manager.
marcel.hirsch david.kasper - would you mind to assist on this?
we need to have a closer look at this. Can you please send me an email with all required customer information and the case description? I will then initiate the next action steps.
/marcel/marcelCustomer Success ManagerDid someone answer your question? Make sure to mark it as answered!Welcome to Snow! Discover more here: Welcome to Snow – Where to start and things to know
Retrieving data ...