Migration from version 7.5 to 9.0. IBM License Metric Tool & Software Use Analysis Questions and Answers ILMT Central Team

Transcription

1 Migration from version 7.5 to 9.0 IBM License Metric Tool & Software Use Analysis Questions and Answers ILMT Central Team

2 Agenda Introduction 01 Step 1: Prepare the environment 02 Step 2: Map the agents 03 Step 3: Migrate the content of SwKBT 04 Step 4: Scan the infrastructure 05 Step 5: Migrate 06 Step 6: Verify the migration 07 Migration statuses 08 Best practices

3 Introduction

4 Overview 02 The session applies to License Metric Tool and Software Use Analysis The products differ when it comes to the set of available functionalities. LMT is a free product for monitoring IBM software that provides only a subset of SUA functionalities. Unless stated otherwise, presented information applies to both products. Software Use Analysis License Metric Tool

5 Overview 02 Source application: LMT or TAD4D 7.5, all subsequent fix packs and interim fixes Target application: LMT or SUA Method: Migration of data, not of the application Side-by-side migration Two environments must be maintained until the end of migration Agent operating systems: All OSes supported for 7.5 except for IBM i (previously i5)

6 Prerequisites 02 A complete LMT or SUA environment: IBM Endpoint Manager server (version 9.0, 9.1 or 9.2) IBM Endpoint Manager database On Windows: SQL Server 2005, 2008, 2008 R2, or SQL Server 2012 On Linux: DB Enterprise server Edition 64-bit or Workgroup Server Edition 64-bit (locally) or IBM Data Server client 10.5 (remotely) IBM Endpoint Manager clients They must be installed on the same computers as the 7.5 agents. They work side-by-side until you complete the migration. LMT/SUA server (version ) LMT/SUA database (DB with FP2 or higher; DB2 10.5)

7 Supported migration paths LMT 7.5.x LMT LMT 7.5.x SUA TAD4D 7.5.x LMT TAD4D 7.5.x SUA

8 Step-by-step 02

9 Step-by-step 02

10 Step-by-step 02

11 Step-by-step 02

12 Step-by-step 02

13 Step-by-step

14 What is not migrated Raw data and scan results The whole software inventory is discovered by the scans in IEM clients must be installed on the same computers as 7.5 agents. Audit reports Audit reports are substituted with audit snapshots. Ensure that you export all of your audit reports from 7.5 and store them for compliance purposes.

15 What is not migrated Software bundlings which: Are not confirmed. Such bundlings are automatically associated in Group products shared between multiple products Group products that are already confirmed in Group components that are assigned to different products in and whose assignment was confirmed

16 What is migrated Confirmed software bundlings with 100% confidence which: Group only IBM products Group only products that can be discovered in If the scan cannot discover particular software, the bundling cannot be migrated Group products that belong to the default report group Group products that are assigned to different products in but their assignment was not confirmed

17 What is migrated Software exclusions Software instances excluded from pricing calculations, unless they are already defined in Directories excluded from scans All directories are migrated, unless they are already defined in VM managers Access details to VM managers are necessary to discover the capacity that the VMs can use. It is required to calculate the PVU consumption. All VM Managers are migrated, unless they are already defined in

18 Step 1: Prepare 01 the environment

19 Prepare the environment Before you migrate, prepare a complete environment. The All-in-One installer for LMT installs version To use this installation for migration, you must first upgrade it to version

20 Prepare the environment The console is required to run scanners and tasks specific to migration Install IBM Endpoint Manager Install IEM clients Install IEM console Enable the fixlet site Install LMT/SUA server Run the import Clients reside side-by-side with 7.5 agents

21 Step 2: Map the agents 02

22 Map the agents Software instances are linked to specific agents based on agent IDs. Mapping is the retrival of IDs and versions of 7.5 agents. Without the IDs, doesn't know where the software is installed. Agent ID: Software 1 Software 3 Software 2

23 Retrive agent IDs 1. In the IEM console, activate the LMT/TAD4D 7.x Agent Mapping analysis. It retrives agent IDs and versions. 2. Check the progress under the Results tab.

24 Preserve agent IDs If you plan to remove the 7.5 agents, run a task that will preserve the IDs and versions by copying them to the computer settings of the IEM clients. 1. In the IEM console, run the Map LMT/TAD4D 7.x Agents task. 2. Check the progress in the analysis that you activated before.

25 Step 3: Migrate the content of SwKBT 03 SUA only Optional

26 Migrate the content of SwKBT SUA only Software Knowledge Base Toolkit (SwKBT) is an application for creating complex software signatures. Migrate the content only if: You migrate from TAD4D to SUA You create custom catalog content LMT unavailable TAD4D obligatory SUA optional, simple signatures can be created in SUA

27 Migrate the content of SwKBT SUA only A separate instance of SwKBT is required. One instance cannot be shared between TAD4D and SUA. Migration tool (must be run on the computer where source SwKBT is installed) Tivoli Asset Discovery for Distributed + Software Knowledge Base Toolkit (or higher) for Sofwtare Use Analysis Software Knowledge Base Toolkit

28 Migrate the content of SwKBT SUA only 1. Install SwKBT that will be used with SUA. 2. Log in to SUA, and click Management > Catalog Servers. Provide the host name and port number of SwKBT. This will allow you to automatically retrieve the catalog from SwKBT once it is published.

29 Migrate the content of SwKBT SUA only 3. Go to the SUA installation directory, and open the migration directory. 4. Copy the swkbt directory to the computer where the source SwKBT is installed. 5. Edit the swkbt_migration.sh or swkbt_migration.bat file, and enter the installation directory of the source SwKBT. The default path is already specified.

30 Migrate the content of SwKBT SUA only 6. Export the custom catalog content to a canonical file: swkbt_migration.sh bat [-f filename.xml] [-f filename.xml] The name of the file to which the custom content is exported. The file is saved in the canonical 2.0 format. If you omit this parameter, the file is saved as canonical.xml.

31 Migrate the content of SwKBT SUA only 7. Import the created canonical file to the target SwKBT. a. Log in to the target instance of SwKBT. b. In the navigation bar, expand IBM Tivoli Software Knowledge Base Toolkit. c. Expand Manage Imports, and then click Canonical XML Document.

32 Migrate the content of SwKBT SUA only d. In the import window, click New Import. e. Select the Advanced mode check box, and browse for your canonical file. Click OK.

33 Migrate the content of SwKBT SUA only The catalog is imported: 8. Publish the catalog in SwKBT. It is automatically uploaded to SUA.

34 Step 4: Scan the infrastructure 04

35 Activate the analyses The software inventory is not migrated. It must be discovered by the scans. 1. In the IEM console, open the LMT/SUA fixlet site. 2. Go to Analyses and select all analyses. Right-click them to view the list of options, and then click Activate. Important: If you want to migrate directories that are excluded from scanning in version 7.5, activate the Excluded Directories analysis.

36 Run the fixlets 3. Go to Fixlets and Tasks, and run the software and capacity scans to discover software and hardware inventory. a) Run Install Scanner. b) Run Initiate Software Scan. This task becomes relevant only when the scanner is installed. c) Run Upload Software Scan Results. This task becomes relevant only when the software scan results are available. d) Run Capacity Scan and Upload Results.

37 VM manager tool VM manager tool is automatically installed on the IEM server during the installation of LMT/SUA. However, double-check it to avoid further issues. Without the the VM manager tool, VM managers will not be migrated. Migration supports only the centralized VM management approach - VMMs must have a direct connection to the IEM server.

38 VM manager tool 4. In the IEM console, run the following tasks against the IEM server: If the task cannot be run against IEM, it means that automatic installation was successful and you can omit this step. a. Run Install VM Manager Tool. b. Run Upload VM Manager Tool Scan Results. Important: Open the VM Managers panel to initiate the tool. In LMT/SUA, click Management > VM Managers. 5. When all scans are completed and the results collected, run a data import in LMT/SUA to process the results. Click, Management > Data Imports.

39 Step 5: Migrate 05

40 Before you begin 02 The migration tool is installed together with the LMT/SUA sever and must be run on the same computer. During the migration, the following must be running: LMT/TAD4D 7.5 database IEM server LMT/SUA server

41 Provide access details 1. From the LMT/SUA installation directory, go to migration/product. 2. Edit the migration.properties file and specify the access details of the source and the target applications.

42 Provide access details To view the user token in SUA, click Profile, and then Show Token.

43 Three stages of migration Export to CSV Simulation Migration

44 Export to CSV 02 Export to CSV Simulation Migration Recommended before the migration. All information eligible for migration is exported from LMT/TAD4D 7.5, regardless of whether the target environment fulfills the requirements. Useful for checking what items will be migrated.

45 Export to CSV 1. To start the export, run the following command:./migration.sh -export [-dir directory] [-dir directory] The directory to which the CSV files are exported. It must exist, otherwise you'll get an error. If you don't specify this parameter, the files are saved in the main directory of the migration tool.

46 Export to CSV 2. After the export completes, check the summary that is displayed in the tool. 3. Check the created CSV files.

47 Export to CSV: agents The list of all 7.5 agents is saved in the agents.csv file.

48 Export to CSV: agent mappings Agent mappings that were created after running the LMT/TAD4D 7.x Agents Mapping analysis, are saved in the agentsmap.csv file. You can compare this file with the list of all agents (agents.csv) to know which of the agents were already mapped and used in the migration.

49 Export to CSV: VM managers Definitions of VM managers are saved in the vmmanagers.csv file. Type: 1: Microsoft Hyper-V, 2: VMWare ESX, ESXi, vcenter, 3: KVM RHEV-M Shared Credentials Specifies whether a VM manager shares credentials with hosts in the same cluster. Available only for Microsoft Hyper-V.

50 Export to CSV: software bundlings Software bundlings are saved in the bundles.csv file.

51 Export to CSV: software exclusions Software exclusions are saved in the excludedsoftware.csv file.

52 Export to CSV: excluded directories Directories excluded from scanning are saved in the excludedirectories.csv file. Platform The directory is excluded on all computers with a particular OS Agent The directory is excluded on a specific agent

53 Simulation 02 Export to CSV Simulation Migration Simulates the migration but the migrated items are not saved in If something is not migrated during the simulation, you can correct it. You can run it until you are satisfied with the results.

54 Simulation 1. To start the simulation of migration, run the following command:./migration.sh -migrate [-dir directory] simulate [-dir directory] The directory to which the CSV files are exported. It must exist, otherwise you'll get an error. If you don't specify this parameter, the files are saved in the main directory of the migration tool.

55 Simulation 2. After the simulation is complete, check the summary that is displayed in the tool. Important: Items are first exported from 7.5 and then imported to If the number of exported and imported items is the same, the items were successful migrated. Items might be skipped if, for example, an Endpoint Manager client is not installed on an endpoint. The reason for skipping such items is provided in the CSV reports.

56 Simulation: VM managers The summary of migrating the VM managers is saved in the vmmanagers_report.csv file. Status succeeded skipped failed Description explanation of the status Type 1: Microsoft Hyper-V, 2: VMWare ESX, ESXi, vcenter, 3: KVM RHEV-M

57 Simulation: software bundlings & exclusions The summary of migrating the software bundlings and exclusions is saved in the software_report.csv file.

58 Simulation: software bundlings & exclusions

59 Simulation: software bundlings & exclusions

60 Simulation: software bundlings & exclusions

61 Simulation: excluded directories The summary of migrating the excluded directories is saved in the excluded_directories_report.csv file.

62 Simulation: excluded directories All directories that are excluded for a platform are always migrated and delivered to the IEM clients. The migration tool does not recognize if they were already migrated or not. Be careful when you repeat the migration. You might significantly increase the workload on the IEM server.

63 Migration 02 Export to CSV Simulation Migration can be run as many times as you want. Items that were already migrated are listed as skipped. Migration

64 Migration 1. To start the migration, run the following command:./migration.sh -migrate [-dir directory] [-dir directory] The directory to which the CSV files are exported. It must exist, otherwise you'll get an error. If you don't specify this parameter, the files are saved in the main directory of the migration tool.

65 Migration 2. Check the summary that is displayed in the tool after the migration is completed. Important: Items are first exported from 7.5 and then imported to LMT/SUA If the number of exported and imported items is the same, the items were successful migrated. Items might be skipped if, for example, an Endpoint Manager client is not installed on an endpoint. The reason for skipping such items is provided in the CSV reports.

66 Migration 3. Verify the CSV reports that were created after the migration: software_report.csv vmmanagers_reports.csv excluded_directories_report.csv

67 Migration In general, reports created after the migration are the same as in the case of simulation. However, simulation does not check the connection to IEM/LMT/SUA because the items are not saved in the target environment. Migration checks this connection. In case of connection problems, some items will be listed as failed even if they were skipped in simulation.

68 Step 6: Verify the migration 06

69 Verify VM managers Definitions of VM managers are added to LMT/SUA Access details are passed to VMM tool VMM tool collects capacity data Upload To speed up, run the Upload VM Manager Tool Scan Results task in the IEM console and then run the import to LMT/SUA. Every 12 hours Capacity data is uploaded to IEM After max. 2 daily imports All capacity data is available. VM status is OK

70 Verify VM managers Compare VM Managers in 7.5 and in In 7.5, click Infrastructure > VM Managers. In , click Management > VM Managers.

71 Verify software bundlings Compare software bundlings in 7.5 and in In 7.5, click Software > Manage Software Inventory. In , click Management > IBM Software Classification.

72 Verify software bundlings Switch the filter to All Classifications or Confirmed Classifications. The status of each migrated item on the panel is changed to Confirmed, which is not displayed by default. You can also use Host Name to find the specific items.

73 Alternative bundling verification Each click sends a request to the database. Export the software inventory to CSV files. Filter the files to find specific information. It might be time consuming! A set of CSV files from and 7.5 can even be compared and checked line-by-line.

74 Alternative bundling verification In 7.5, click Download as CSV to save the contents of the Manage Software Inventory panel to a CSV file. In , go to Reports > All IBM Metrics, and click Audit Snapshot

75 Verify software exclusions Compare software exclusions in 7.5 and in In 7.5, click Infrastructure > Manage Software Inventory. In , click Management > IBM Software Classification.

76 Migration statuses 07

77 Statuses: VM managers Succeeded VM manager was migrated and no action is required. Skipped VM manager was not migrated because it is already defined in Failed An error was returned from the LMT/SUA/IEM servers, e.g. connection problems. Check the tema.log to determine the cause. /opt/ibm/sua/wlp/usr/servers/server1/logs/tema.log.

78 Statuses: excluded directories Updated Directories were updated on the IEM server. The information will be delivered to the endpoints. Skipped Items were not migrated. Possible reasons: The IEM client is not installed Only items from endpoints that have both the 7.5 agent and the IEM client installed can be migrated. Directories are already excluded Directories are already excluded in They don t have to be migrated. Unsupported platform Directories are excluded on i5 systems, which are not supported by 9.x. They cannot be migrated.

79 Statuses: excluded directories Failed The directories were not migrated. Possible reasons: The Add Excluded Directories task cannot be found in the LMT/SUA fixlet site. The task is used to migrate the directories and is available starting from LMT/SUA Update the fixlet site to the latest version. The Add Excluded Directories task in the LMT/SUA fixlet site cannot be initiated. The task cannot be initiated, probably due to connection problems to the IEM server (wrong host, port, etc.). Check the migration.log files for details.

80 Statuses: software bundlings and exclusions Succeeded Items were successfully migrated and no action is required. Skipped Items were not migrated. Possible reasons: The IEM client is not installed. Only items from endpoints that have both the 7.5 agent and the IEM client installed can be migrated. The software exclusion already exists in the target instance. No need to migrate. The software bundling already exists in the target instance. No need to migrate. Shared components cannot be migrated. Components shared between multiple products cannot be migrated.

81 Statuses: software bundlings and exclusions Skipped, cont. Items were not migrated. Possible reasons: The report group ID is incorrect. Only software that belongs to the default group can be migrated. See: Reassigning the software instance to the default report group. The software was not discovered in the target instance. The software was not discovered by scans. It might be installed on remote disks. The software exclusion could not be migrated because the related software does not exist in the target instance. Same as above, the scans didn't discover the software. The component is assigned to a different product in the target instance. The migration tool cannot overwrite an assignment that is confirmed in Log in to LMT/SUA, go to Management > IBM Software Classification, and reassign the software manually, if needed.

82 Statuses: software bundlings and exclusions Failed An error was returned from the LMT/SUA/IEM servers, e.g. connection problems. Check the tema.log to determine the cause. /opt/ibm/sua/wlp/usr/servers/server1/logs/tema.log.

83 Best practices 08

84 Migrate in parts Migration of each endpoint produces significant amount of information that must be verified to ensure that the migration succeeded. Divide computers into groups to break the migration into parts Install IEM clients on a group of computers (fresh installation) Subscribe clients to the fixlet site in groups (if you already have the environment)

85 Migrate in parts Important: CSV files (after export) and CSV reports (after simulation and migration) still contain ALL items that can be migrated. Items from endpoints without the IEM client are listed as skipped with an explanation that the IEM client is not installed. This approach does not reduce your workload while checking the reports, however it makes the verification in LMT/SUA easier.

86 Install IEM clients on groups of endpoints Install IEM clients on a group of endpoints.

87 Install IEM clients on groups of endpoints Run the migration. Items are migrated only from endpoints that have both the 7.5 agent and the IEM client installed.

88 Install IEM clients on groups of endpoints After the first group is migrated and verified, install the clients on the next group.

89 Install IEM clients on groups of endpoints Repeat the migration (mapping, scanning, migrating). Only information from the new group is migrated.

90 Subscribe endpoints to the fixlet site in groups Install clients on all computers. Subscribe a group of clients to the Endpoint Manager site.

91 Subscribe endpoints to the fixlet site in groups Activate the LMT/TAD4D 7.x Agent Mapping analysis. It is activated only on the subscribed computers. Then, run the migration.

92 Subscribe endpoints to the fixlet site in groups Subscribe another group of clients to the Endpoint Manager site.

93 Subscribe endpoints to the fixlet site in groups Activate the analysis and repeat the migration.

94 Subscribe endpoints to the fixlet site in groups To limit the number of endpoints subscribed to the fixlet site: 1. Log in to the IEM console, and click on the fixlet site. 2. Switch to the Computer Subscriptions tab, and choose the computers.

95 Software catalog To avoid problems that might occur due to differences in discovered software, the version of the software catalog used in 7.5 and should be the same. LMT/TAD4D 7.5 LMT Catalogs for those applications are released in the same time. Update the catalog to the latest versions, both in 7.5 and Useful links: Importing software catalogs to LMT 7.5 Importing software catalogs to TAD4D 7.5 Downloading the software catalog in LMT

96 Software catalog LMT/TAD4D 7.5 SUA The catalog for 7.5 is released earlier than the one for SUA. To make the catalogs compatible, either wait until the newest one for SUA is released or upload a lower version to 7.5. Restriction: If you already uploaded the newest version to 7.5, you won't be able to upload the lower one. In such case, migrate on different catalogs and when the SUA catalog is released, repeat the migration.

97 Software catalog To download the same catalogs for 7.5 and : 1. Open catalog release notes. The document lists all software catalogs that are released for SUA. 2. Check the newest entry for the date that described the identical catalog in v7.5.

98 Software catalog 3. Download the catalog for 7.5 from one of the following URLs. Substitute date with the date that is provided in the release notes. LMT 7.5: ftp://public.dhe.ibm.com/software/tivoli_support/misc/cando/tivolicatalog/ibm/ilmt/ IBMUseOnlySoftwareCatalog_canonical_form_date.zip TAD4D 7.5: ftp://public.dhe.ibm.com/software/tivoli_support/misc/cando/tivolicatalog/ibm/swkbt/ IBMSoftwareCatalog_canonical_form_date.zip Example: If the date is , the URL is as follows: ftp://public.dhe.ibm.com/software/tivoli_support/misc/cando/tivolicatalog/ibm/swkbt/ IBMSoftwareCatalog_canonical_form_ zip

99 Software catalog 4. Import the downloaded catalog to LMT 7.5 or import the downloaded catalog to TAD4D Download the newest software catalog for SUA , and then update it in the application.

100 Beta program

101 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 Migration from version Expanded Oracle discovery For more information, see our Beta Program Community.

102 Useful links

103 Useful links Scalability Guide License Metric Tool Software Use Analysis YouTube IBMLicenseMetricTool IBM License Management (SUA) Forum License Metric Tool Software Use Analysis Wiki License Metric Tool Software Use Analysis Documentation License Metric Tool Software Use Analysis

104 Questions?

105 Thank you!