Troubleshooting

IBM License Metric Tool v9 &

Software Use Analysis v9Questions and Answers

ILMT Central Team

Agenda

02Deployment

03Restarting services

08Migration, Beta program &Release plans

07Logs

06Opening SRs

05Managing software

04Discovering

software

09Useful linksIntroduction

01

Introduction 01

Introduction 02

The session applies to License Metric Tool and Software Use Analysis 9.x. The

products differ when it comes to the set of available functionalities. LMT is a free

product for monitoring IBM software that provides a subset of SUA functionalities.

Unless stated otherwise, presented information applies to both products.

Software Use Analysis

License Metric Tool

Deployment 02

Hardware requirements

Environment size Topology CPU RAM

Small:Up to 5000 endpoints

1 server IEM + LMT/SUA + DB2 2-3 GHz, 4 cores 8GB

Medium: 5000 – 50 000 endpoints

2 servers* IEM 2-3 GHz, 4 cores 16GB

LMT/SUA + DB2 2-3 GHz, 4 cores 12-24GB

Large:Over 50 000 endpoints

2/3 servers* IEM 2-3 GHz, 4-16 cores 16-32GB

LMT/SUA + DB2 2-3 GHz, 8-16 cores 32-64GB

* A distributed environment, where LMT/SUA is separated from DB2, is advisable.

Ensure that you fulfill the requirements before you start the installation. It saves time.

Operating systems

The only supported operating system for the LMT/SUA server is:

Red Hat Enterprise Linux 6.3, or a higher 6.x version.

Support for Windows is planned for the near future. You can try it out in the Beta Program.

The following and any other operating systems are not supported and cannot be used for installing LMT/SUA:• CentOS• SUSE Linux• Oracle Linux

Failed generation of the IEM license file

The file must be generated from a computer with the Internet access. If the generation fails, the problem might be caused by a connection timeout. To solve the problem, edit the generate_license.sh script. Adjust the wget timeout setting (-T parameter) to 1000 seconds or remove the wget timeout altogether.

Original setting:wget -T 60 -t 3 -q -O "${MY_REQ_PATH}" "${MY_URL}"

After modification:wget -T 1000 -t 3 -q -O "${MY_REQ_PATH}" "${MY_URL}"orwget -q -O "${MY_REQ_PATH}" "${MY_URL}"

Restarting services 03

Restarting services on Linux

IEM server/etc/init.d/besserver start | stop | restart

IEM Web Reports/etc/init.d/beswebreports start | stop | restart

IEM client (agent)/etc/init.d/besclient start | stop | restart

ILMT/SUA server/etc/init.d/LMTserver start | stop | restart/etc/init.d/SUAserver start | stop | restart

Restarting services on Linux

DB2 server1. Switch user to the DB2 instance owner.su db2inst1

2. Close connections to the database.db2 force application all

3. Stop and start the database.db2stopdb2start

Restarting services on Windows

1. Type 'services' in the Start Menu search box.2. Click Services.

Restarting services on Windows

3. Right-click on a service, and select start, stop, or restart.

Service names:• IEM serverBES Root Server

• Web ReportsBES Web Reports Server

• IEM clientBES Client

• MSSQLSQL Server *component

Discovering software 04

Discovering software

1. Activate analyses

2. Run the Install Scanner fixlet.The scanner must be installed on every endpoint that you want to monitor.

3. Run the Initiate Software Scan fixlet.Important: When the fixlet shows 100% complete, it means that the software scan was

successfully initiated on the endpoint, not that it finished. To check the status of the software scan,

open the Software Scan Status analysis

4. Run the Upload Software Scan Results fixlet.

5. Run the Run Capacity Scan and Upload Results fixlet.

Updating scanner catalogs

Checking whether the automatic update of the scanner catalogs succeeded

1. Import the software catalog (Management > Catalog Upload). Scanner catalogs are created after each upload of the software catalog.

2. In the Endpoint Manager console, click Actions.

3. Select Catalog Download. The action is responsible for delivering scanner catalogs to your computers.

Updating scanner catalogs

4. Switch to the Computers tab.5. Check the status next to each computer.

6. Double-click on each computer for more information (completed and failed steps)

Updating scanner catalogs

Manually updating the catalog

1. Log in to LMT/SUA and import the software catalog (Management > Catalog Upload)2. Hover over the question mark (?). Help box is displayed.3. Click Catalog Download Fixlet. The catalog_download.bes file is downloaded.

Updating scanner catalogs

4. Copy the catalog_download.bes file to the computer where IEM console is installed.5. In the Endpoint Manager console, click File > Import.

6. Choose catalog_download.bes. The file is added to the Master Action site.

Updating scanner catalogs

7. In the navigation bar, click Sites > Master Action Site > Fixlets and Tasks.8. Select Catalog Download, and click Take Action.

9. Select all computers as targets. The catalogs are delivered.

Managing software 05

Managing software

What to do if software is not discovered?LMT: Update the software catalog to the latest version. If the software is still not discovered, open a PMR.

SUA: Create a custom signature or search the signature community. For more informationand resources, see the SUA wiki: https://ibm.biz/BdE63r.

What to do if a component can't be assigned to a product?Open a PMR.

Managing software

What to do if the software is incorrectly bundled?Reassign it on the IBM Software Classification panel.

Opening SRs 06

What's an SR?

Service Request

(former PMR)

Document for managing technical issues

Created by submitting a Service Request

through the Service Request Tool

Updates sent vie e-mail

Further information might be required

Before you open an SR

1. Open the Computers report to verify that data from the given endpoint is available.

2. If no data is available, check the import log for warnings.

Before you open an SR

3. If nothing can be found in the import log, check the Software Scan Status analysis.4. If you are not able to solve the problem, run the Initiate Scanner Diagnostic Tool fixlet

on the problematic endpoints. 5. After the diagnostic data is gathered, run the Upload Scanner Diagnostic Data fixlet. It

uploads the ScannerDebugData compressed file to the computer where the IEM server is installed to the following directory:

<BES Server>\UploadManagerData\BufferDir\sha1\<last_2digits_of_computer_ID>\<computer_ID> directory.

An SR package

If you are not able to solve the problem, open an SR. A good SR package should

contain:

• Information gathered by the Gather Environment Information fixlet

• Scanner diagnostic data gathered by the Initiate Scanner Diagnostic Tool fixlet

• IEM client logs

• LMT/SUA server log

• Import logs

Logs 07

Installation logs

During the installation:$HOME/LMT_version $HOME/SUA_version$HOME/ia.log $HOME/ia.log

Incomplete installation:$HOME/LMT_version_timestamp_logs.tar.gz$HOME/SUA_version_timestamp_logs.tar.gz

Successful installation: install_dir/LMT_version_timestamp_logs.tar.gzinstall_dir/SUA_version_timestamp_logs.tar.gz

Installation log content

<Message Id="CODIN0215W" Severity="WARN"> <Time Millis="1381929782997"> 2013-10-16 15:23:02.997+02:00</Time> <Server Format="IP">NC040226</Server><ProductId>COD</ProductId><Component>Install</Component> <ProductInstance></ProductInstance> <LogText><![CDATA[CODIN0215W The following ports are in use: 9081. The installation process can be continued but the server will not be started. The server has to be started manually after resolving the ports conflict.]]></LogText> <Source FileName= "com.ibm.license.mgmt.install.ia.common.CommunicationCommon" Method="okToContinue"/> <TranslationInfo Type="JAVA" Catalog="userLocales.InstallMessageEWI" MsgKey="checkPorts"><Param><![CDATA[9081, ]]></Param></TranslationInfo> <Principal></Principal> </Message>

Database creation logs

Database creation log:/tmp/createdb_20131018-131841

Return codes:

Server logs

Server log:install_dir/wlp/usr/servers/server1/logs/tema.log

Changing server log settings:install_dir/wlp/usr/servers/server1/server.xml

logDirectory='install_dir/wlp/usr/servers/server1/logs' maxFileSize='10' maxFiles='20' messageFileName='tema.log'

Location of the log file

The maximum size (in MB) that a log file can reach before it is rolled over. Deafult vealue is 10. To disable this attribute, set the value to 0.

The maximum number of iterations of the server log file. If the log file reaches the maximum size ste in the maxFileSize parameter, the remaining messages roll over to another iteration of the file.

Name of the log file

Server logs

Changing server log level:install_dir/wlp/usr/servers/server1/config/log4j.properties

Use the log4j.rootCategory property to change the logging level. The default level is INFO.

Log levels:FATAL: the task cannot continue and component, application, and server cannot function ERROR: error events that might still allow the application to continue runningWARN: potential error or impending error. This level can also indicate a progressive failureINFO: general information that outlines the overall task progressDEBUG: fine-grained informational events that are most useful to debug an application

Logging memory consumption

1. Go to:/etc/init.d/LMTserver/etc/init.d/SUAserver

2. Set the LOG_MEMORY environment variable to true.

Example:SERVER_NAME=server1WLP_PATH=/opt/IBM/SUA/wlpexport JAVA_HOME=/opt/IBM/SUA/jre/jreexport TEMA_HOME=/opt/IBM/SUA/wlp/usr/servers/server1export PATH=${PATH}:/opt/IBM/SUA/wlp/usr/servers/server1/binexport LOG_MEMORY=true

IEM client logs

Client logs on Windows:C:\Program Files\BigFix Enterprise\BES Client\__BESData\__Global\LogsC:\Program Files\BigFix Enterprise\BES Client\LMT

Client logs on UNIX/Linux:/var/opt/BESClient/__BESData/__Global/Logs/var/opt/BESClient/LMT

Import logs

Import log:install_dir/wlp/usr/servers/server1/logs/imports

The latest import log can also be accessed from the navigation bar. Click Management > Data Imports.

Enabling debug logging for imports

1. Go to install_dir/wlp/usr/servers/server1/ and open the jvm.options file. 2. Add the following line to the file: -DTEMA_LOG_DEBUG=1

3. Restart the LMT/SUA server by run the following command: /etc/init.d/LMTserver restart /etc/init.d/SUAserver restart

Migration

Beta program &

Release plans

08

Beta program

If you want to try out the new features that we are currently working on, join our beta

program.

In the current drop you can test:

• Installation on Windows

• Expanded Oracle discovery

For more information, see our Beta Program Community at: https://ibm.biz/ILMT_Beta

Migration from version 7.5

Two cookbooks have been published recently:

● Migration of License Metric Tool from version 7.5 to version 9.0

● Migration from Tivoli Asset Discovery for Distributed to Software Use Analysis

We encourage all the users who plan to migrate to version 9 to get familiar with them.

https://ibm.biz/ILMT9_MigrationCookbook

https://ibm.biz/TAD4D_MigrationCookbook

ILMT/SUA release plans

ILMT development team is pleased to announce that some of our plans are now publicly

available.

Feel free to:

● read

● vote

● comment

All actions possible to take here: https://ibm.biz/SUA_DevPlans

Useful links 09

Useful links

@ILMTCentralTeamLicense Metric Tool

Software Use Analysis

License Metric ToolSoftware Use Analysis

IBMLicenseMetricTool

IBM License Management

(SUA)

License Metric ToolSoftware Use Analysis

Forum

Wiki Documentation

Twitter

YouTubeScalability Guide

License Metric Tool

Software Use Analysis

@IBMEndpoint

Thank you!

Questions?