Skip to content

Latest commit

 

History

History
51 lines (29 loc) · 3.14 KB

README.md

File metadata and controls

51 lines (29 loc) · 3.14 KB

Managing License Metric Tool disconnected scans with Ansible

Disconnected scans allow for discovering software and hardware inventory by running scripts that are provided in the disconnected scanner package. The scripts initiate software and capacity scans, and create a package with scan results that you later need to upload to the License Metric Tool server. You can automate management of disconnected scans by using Ansible.

The current version of License Metric Tool playbooks is 9.2.33

Prerequisites

  • Supported version of Ansible

    Ensure that you have Ansible in version 2.10.2 or higher. If you have an earlier version of Ansible, upgrade your environment, preferably to the latest available version. Otherwise, License Metric Tool playbooks will not work.

  • Supported version of the disconnected scanner

    The minimal supported version of License Metric Tool disconnected scanner to use with Ansible automation is 9.2.22.

  • Supported operating systems

    Playbooks that are delivered with License Metric Tool are supported on AIX, Linux, Solaris and Windows. They are not supported on IBM i. For information about exact versions, see the list of operating systems that are supported by the disconnected scanner.


Overview

After you install License Metric Tool, set up Ansible to manage disconnected scans by using playbooks. If Ansible is not yet implemented in your organization, refer to Ansible documentation for information how to install and configure it. If you already have Ansible implemented, ensure that it meets all requirements of License Metric Tool and configure it to manage the selected computers.

After you configure Ansible, run the lmt_install_or_upgrade_scanner playbook to install the disconnected scanner on the managed nodes. The playbook also performs initial configuration of the scanner. By default, it schedules weekly software scans and daily generation of packages with scan results. Next, run the lmt_collect_results playbook to schedule daily collection of scan results from the managed nodes.


Table of contents


Other resources