Post on 12-Mar-2018
transcript
Enhancements and new features in
ILMT/SUA 9.2.0.2IBM License Metric Tool &
Software Use AnalysisQuestions and Answers
Enablement Team
Agenda
03PowerShell as the
communication
interface for Hyper-V
04Hiding free instances
06Migrating SUA from
version 2.2 to 9.2.0.2
05Collecting capacity
data from KVM hosts
Coexistence of ILMT
and SUA on one IEM
02
2Contact us at: LMTHelp@us.ibm.com
Introduction
01Rebranding
07
Demo
08
Questions
09
Introduction 013
• Discovers detailed
information about hardware,
installed IBM software and
third party software
• Delivers flexible options for
monitoring software usage
• Integrates with IBM Control
Desk for discovered hardware
and software assets
Software Use Analysis
Introduction 02
The session applies to License Metric Tool and Software Use Analysis 9.x. Unless
stated otherwise, presented information applies to both products.
• Discovers PVU software• Measures maximum core capacity in
PVUs available to the deployed software
• Required for subcapacity licensing
License Metric Tool
4Contact us at: LMTHelp@us.ibm.com
Coexistence of LMT &
SUA 9.2.0.2 on one IEM 025
Coexistence 02
To put it simple, coexistence means that you can connect both LMT and SUA to one IBM Endpoint
Manager platform.
SUALMT
IEM
CC
C
C
CC
C
C
C C6
Coexistence 02
How?
By enabling two Fixlets sites in one IEM console.
So, my endpoints are both in LMT and in SUA?
No.
Endpoints are separated. They can report to only one
application at given moment, either LMT or SUA.
You can switch at any time, though.
CC
C
CSUA
C C7
Coexistence 02
Actually, everything is separated.
Fixlet sites, Fixlets, scans, endpoints, application servers, catalogs. Everything.
LMT and SUA work as two different/separate applications.
So, what does this coexistence do?
It gives you the possibility to use one IEM server, and one IEM console, to manage two
applications.
Documentation
8
Coexistence 02
# Use Case:
The coexistence can be used to extend your current LMT deployment with extra capabilities of
SUA.
You can monitor your servers (which only need to be compliant) with LMT, and apply SUA to your
workstations to discover extra software and their usage.
9
LMT SUA
Coexistence 02
STEP 1: Buying a license for SUA.
• LMT -> SUA: If you’re adding SUA, you must first purchase it. Your free LMT license is not
enough. You can use Beta, though, it’s free.
Click here to learn how -> Beta.
• SUA -> LMT: You’re good. Your SUA license already contains entitlements for LMT.
10
Coexistence 02
STEP 1: Buying a license for SUA.
1. Go to Passport Advantage and purchase entitlements for IBM Endpoint Manager for Software Use Analysis.
2. Check the serial number of your current License Metric Tool license:
a) In the IEM console, click BigFix Management.
b) In the navigation tree, click License Overview.
11
Coexistence 02
3. Email TEM@dk.ibm.com and include the following information:
• Your current serial number
• Your personal data that helps to recognize you as an IBM customer
• Details of the SUA license that you purchased
• A request for expanding your current serial number with the entitlements for SUA.
All free LMT licenses are in the same pool. This step is required so that your license can be
recognized and extracted from the pool. It is then connected with the new license for SUA.
Result: Your serial number remains the same (so you don’t have to reinstall IEM), but you can
now also use SUA.
12
Coexistence 02
4. You will receive a notification from TEM@dk.ibm.com that your license was updated, but you
can keep checking that also in the IEM console.
5. Click Check for license update.
If you get the message: *Site certificate update detected*, something is on.
13
Coexistence 02
5. Go to the IEM server and run BESAdmin to propagate the updated license info to your
endpoints.
LINUX:
a) Go to /opt/BESServer/bin.
b) Run the command:
./BESAdmin.sh –syncmastheadandlicense –sitePvkLocation=path_to_license.pvk
WINDOWS:
a) Go to C:\Program Files (x86)\BigFix Enterprise\BES Server.
b) Run BESAdmin.exe.
c) When prompted, provide the path to license.pvk, and enter the password.
d) In the Masthead Management tab, click OK.
14
Coexistence 02
STEP 2: Enabling the Fixlet sites.
• Fixlets sites contain all fixlets, tasks, and analyses that you use to config and use SUA.
• You have to enable them to download LMT/SUA, install scanner, run scans, etc.
• The possibility to enable both the LMT and SUA fixlet sites is COEXISTENCE.
That’s a Fixlet (content) site.
15
Coexistence 02
The Fixlet sites can be enabled in the IBM Endpoint Manager console:
16
Coexistence 02
Result:
After this step, you should have two Fixlet
sites enabled. Each of them contains
a separate set of Fixlets.
TIP: No Internet? Use Airgap Tool
and the BES Download Cacher to load
the content.
17
Coexistence 02
STEP 3: Dividing endpoints between computer groups (separating),and subscribing each group to each Fixlet site.
• Endpoints must be separated, some will use LMT, and some will use SUA. NOT BOTH.
• Plan ahead which endpoints will use which application.
• Create computer groups (in IEM), one with LMT endpoints, one with SUA endpoints. You can create more.
• You can manage computer groups instead of single endpoints. Much easier.
18
Coexistence 02
You can divide your endpoints between the groups by creating manual or automatic computer
groups in the IBM Endpoint Manager console.
Then, you can subscribe each group to a particular Fixlet site. Groups are easier, but you can also
subscribe single endpoints.
19
Coexistence 02
Results:
After this step, some endpoints should be subscribed to the LMT site, and some to the SUA site.
What to do next:
Install and configure the coexisting applications (or only the one that you’re adding). Perform a
normal installation, the coexistence does not affect this area.
20
Coexistence 02
NEW FIXLET:
We want to make sure that none of your computers are subscribed to both sites.
If that happens, you can take a look at a Fixlet that will warn you about „multiple” subscriptions.
If the Fixlet is relevant for any computer, remove it from one of the groups. The Fixlet only shows
endpoints, you don’t have to run it.
21
Coexistence 02
LIMITATION
VM Managers can be configured in the UI only for ONE application.
Recommendation: Use the UI with the application that it was already used with. If you had the IEM server in the LMT site, keep it that way.
Note: VM Managers will be visible in both UIs.
22
Coexistence 02
Why?
The „UI” VM Managers (default/centralized approach) are managed by VM Manager Tool that is installed on the IEM server. And you can install only one.
IEM
VMM TOOl
23
Coexistence 02
So, what about other app?
You have to use advanced (decentralized/distributed) VM management.
You install additional VM Manager Tool, configure VM managers in configuration files, and manage them in the command line. You don’t see them in the UI.
Any computer
Additional
VMM TOOl
24
PowerShell as the
communication
interface for Hyper-V03
25
Using PowerShell
• VM Manager Tool must be installed on a Windows computer
The use of PowerShell depends on what operating system the IEM server is installed, because
the main VM Manager Tool is installed along with the server:
Windows
You configure a Hyper-V VM manager in the UI and choose PowerShell as the communication
interface.
Linux
You use advanced VM management to install additional VM Manager Tool on any Windows
computer, and then specify a Hyper-V VM manager in a configuration file. Such a VM manager is
not visible in the UI, but is managed through the VM Manager Tool command line.
Can be IP address or host name.
26
Hiding free instances 0427
Hiding free instances
You can hide software instances for which all bundling options are free of charge regardless of
whether the bundlings are already confirmed or not.
To save the setting and refresh the panel, click Update. The setting is applied globally for all users
and all sessions. To show the free-of-charge instances, clear the check box.
28
Audit snapshot content
The other_products.csv file is substituted with the bundling_options.csv file.
Information about software that is not
licensed under full or subcapacity
licensing, and does not generate any
PVU or RVU MAPC consumption.
You had to combine it with other CSV
files from the audit snapshot to get a
view of all software.
Contains information about all IBM
software regardless of its license type
and consumption.
29
Collecting capacity data
from KVM hosts 0530
Collecting capacity data from KVM hosts
Before:
Data collected by VM Manager Tool
KVMs managed by RHEV-M (version 3.0 or 3.1)
Now: Is the KVM managed by RHEV-M?
Yes No
VM Manager Tool connects to RHEVM
and collects data from KVM hosts
Use the Run Capacity Scan
and Upload Results task on the
enpoint with VM Manager Tool
Docs
Use the Run Capacity Scan
on Virtualization Hosts task on the
KVM host
Docs
Data is collected directly
from KVM hosts31
Migrating SUA from
version 2.2 to 9.2.0.2 0632
SUAonly
Feature Version 2.2 Version 9.2.0.2
IBM and non-IBM software discovery and inventory
Hardware discovery *More detailed information available
out-of-the-box
Collection of usage data
Integrated software catalog management *Enhanced with custom catalog export
and import
Unrecognized software management
ETL scope Data from all computers regardless of their site subscription
Data only from computers subscribed to the SUA site
Continuous delivery Only critical defects New features, enhancements, and fixes on a regular basis
IBM subcapacity reporting and automated bundling definitions
Virtualized hardware inventory
Shared file systems support
Automatic distribution of the software catalog and catalog versioning
Public REST API
Dashboard
Enhanced user interface and reorganized menu
Improved performance and serviceability
Open Beta Program
IBM subcapacity reporting and automated bundling definitions
Subcapacity licensing allows you for licensing an eligible software product for less than the full capacity of
your server or group of servers.
Processor Value Unit (PVU) is a unit of measure by which the program can be licensed. The number of
PVU entitlements required is based on the processor technology defined within the PVU Table by
processor vendor, brand, type and model number and by the number of processors made available to the
program.
More information: http://www-01.ibm.com/software/passportadvantage/subcaplicensing.html
IBM subcapacity reporting and automated bundling definitions
Example:
Cores to license Partition 1 Partition 2 Subcapacity Full capacity
MQ software 4 4 8 8
WebSphere Software 4 - 4 8
Partition 1:
4 virtual cores
Partition 2:
4 virtual cores
8 physical cores
MQ
WebSphere
MQ
IBM subcapacity reporting and automated bundling definitions
You can use SUA to monitor PVU and RVU MAPC consumption of IBM products under full and subcapacity
licensing terms.
IBM subcapacity reporting and automated bundling definitions
The discovered software is classified based on the automated bundling definitions. You can confirm the
initial classification or reassign components to reflect your actual purchases.
IBM subcapacity reporting and automated bundling definitions
You have a detailed overview of all actions that influence the value on the PVU and RVU MAPC
consumption reports.
IBM subcapacity reporting and automated bundling definitions
You can generate an audit snapshot which is a record of the PVU and RVU MAPC consumption in your
enterprise. The snapshot is used for IBM auditing purposes.
Virtualized hardware inventory
You have detailed information about computers and virtual machines in your infrastructure, including:
• Processor details (vendor, brand, type, model, cores, PVU value per core, physical and virtual shared
pools)
• Hypervisor status
Dashboard: overview of the infrastructure health
The widget shows whether agents are
connecting to the IEM server, have an
outdated version, and information
about the most important issues that
might occur while agents are operating
such as problems with disk space or
missing software prerequisites.
The widget shows the health of scans
that are running in your infrastructure.
You can drill down to reports for specific
computers with scan problems.
The widget shows whether agents are
correctly configured to collect all data
for the hardware and software that is
present in your infrastructure.
Dashboard: overview of the software inventory
The widget presents top five publishers
with the largest number of defined
contracts defined. The publishers are
ordered according to the number of
computers on which their software is
installed, regardless of the number of
contracts.
The widget presents a summary of the
IBM software that is installed in your
infrastructure, computers, and computer
groups in your infrastructure.
The widget presents links to publishers,
software products, versions, releases,
components, and signatures in the current
catalog.
Dashboard: overview of PVU subcapacity and software classification
The widget presents products with
the highest PVU consumption rate.
It shows how many PVUs a product
consumes but does not relate this
information to your license entitlements.
A maximum of five products are
displayed by default.
The widget presents the number of
confirmed and unconfirmed software
installations in your infrastructure.
Enhanced user interface and reorganized menu
New reports and panels
Improved performance
5:01
3:583:58
2:41
0:00
1:12
2:24
3:36
4:48
6:00
SUA 2.2 Patch 8 SUA 9.2.0.2
Environment size: 35k endpoints Machine: 2 x 2,4 GHz, 24 GB RAM
Initial import Re-import (10% software scan change % 70% usage change
Improved serviceability
You can easily troubleshoot problems that might occur thanks to:
• Fixlets and analyses for software and hardware scan troubleshooting
• Fixlet for running the scanner diagnostic tool
• Fixlet for gathering information about the SUA and IEM environment
Open Beta Program
New to LMT or SUA?
Join the Beta program to get the hands on experience with the application and see the benefits that it
brings to your enterprise: a clear and organized overview of your software assets, reduced time of
managing software for license reconciliation or compliance purposes, and many others.
Already using LMT or SUA?
Participate in the Beta to find out what new features are currently being developed and provide feedback to
influence their final shape. During the Beta, you will have a unique opportunity to chat with developers who
will do their best to answer your questions and quickly solve any problems that you might encounter.
For more information, see the Beta Program Community.
Additional resources
Documentation: https://ibm.biz/sua_22_92_migration
Cookbook: https://ibm.biz/migration_paths
Rebranding 0751
Rebranding
Coming soon!
IBM Endpoint Manager IBM BigFix
IBM Endpoint Manager for Software Use Analysis IBM BigFix Inventory
IBM License Metric Tool IBM License Metric Tool (no change)
Demo 0853
Questions?
54
09
Useful links
55
Wiki
IBMLicenseMetricTool
Forum
Signature community
@ILMTCentralTeam
Documentation
License Metric Tool
Scalability Guide
Migration cookbook (LMT)
Development plans
56Contact us at: LMTHelp@us.ibm.com
Wiki
IBM License Management
Forum
@IBMEndpoint
Documentation
IBM Endpoint Manager
#IEM4SUA
Software Use Analysis
Scalability Guide Development plans
57Contact us at: LMTHelp@us.ibm.com
Thank you!
58