Installing the disconnected scanner and gathering scan results (disconnected scenario)

Available from 9.2.5.

After you distribute the disconnected scanner package to the computers in your infrastructure, install the scanner and run the scans.

1. Go to the directory where you unpacked the disconnected scanner package.
2. For older versions of Linux on z Systems, you might need to provide the machine type, processor type, shared pool capacity, and system active processors.
   Note: Provide the information only on systems where automatic capacity configuration is not supported. Automatic capacity configuration is supported on Linux on z/KVM, on z/VM and on System z10 starting from model E64 (type 2097) mainframes with z/VM 6.3. Additionally, such systems must meet the following requirements:

   • Must support the Store Hypervisor Information (STHYI) instruction.
   • Global performance data control option must be set in HMC for LPARs.
   • The debugs file system must be mounted.

   Starting from application update 9.2.21, you can provide the information by exporting the following variables before you run the scanner installation script. In older version of the disconnected scanner, or if you do not export the variables, the script prompts for these parameters if the scanner cannot collect them automatically.

   export TLM_MACHINETYPE=
   export TLM_PROCESSORTYPE=
   export TLM_SHAREDPOOLCAPACITY=
   export TLM_SYSTEMACTIVEPROCESSORS=

   For example, to export variables for a z9 machine with 12 IFL processors that run on a shared pool with a capacity of 20, set the variables as follows.

   export TLM_MACHINETYPE=z9
   export TLM_PROCESSORTYPE=IFL
   export TLM_SHAREDPOOLCAPACITY=20
   export TLM_SYSTEMACTIVEPROCESSORS=12

3. For Solaris systems that run on SPARC, specify whether the system is in Dynamic System Domains. Starting from application update 9.2.21, you can do this by exporting the following variable before you run the scanner installation scripts. In older version of the disconnected scanner, or if you do not export the variable, the script asks for this parameter.

   export DSD_MODE=no

4. If the computer runs on a public cloud, specify the type of the public cloud in the PUBLIC_CLOUD_TYPE parameter in the setup_config.ini file. For more information, see: Configuration parameters of the disconnected scanner (disconnected scenario).
5. Change to the directory where you copied the disconnected scanner files.
   • Run QSH to enter the Qshell, and run the following command.

     cd /cit

   • 

     cd <disconnected_scanner_dir>

6. To install the disconnected scanner and set up regular scans, run the following script.
   • Run QSH to enter the Qshell, and run the setup_all.sh script.
   • setup.sh
   • setup.bat

   Important: If you use the default configuration, the following types of scans are scheduled to run regularly in accordance with the requirements of subcapacity licensing.

   • Capacity scan
   • Software and capacity scans
7. Validate the content of the computer.yml file. For more information, see: Content of the computer.yml file (disconnected scenario).
   • <disconnected_scanner_dir>/config/computer.yml
   • <disconnected_scanner_dir>/work/computer.yml

Results

The scanner was installed. The following actions were performed or scheduled.

Action	Comments	IBM i	UNIX	Windows
Initial capacity scan was run and the computer.yml file was created.	The initial capacity scan collects data about the computer, and creates the computer.yml file that identifies this computer. The file contains information about the operating system, such as the host name, and a unique computer ID. The file is added to each package with scan results to help in cataloging and correctly displaying scan results in License Metric Tool.	✓	✓	✓
Regular capacity scan was scheduled.	The capacity scan is scheduled to run every 30 minutes to gather current results for virtualized environments where the capacity can change dynamically depending on the allocated resources. If you want to collect capacity data once outside of the regular schedule, run the setup script with the -noschedule option. The -noschedule option is not applicable on Linux. To run a one-time capacity scan, configure the HW_SCAN_SCHEDULE_ENABLED parameter. For more information, see: Configuration parameters of the disconnected scanner (disconnected scenario).	✓	✓	✓
Regular software scan was scheduled.	The software scan is scheduled to run weekly by default. Such setup allows for complying with the requirements of subcapacity licensing.		✓	✓
A package with the disconnected scan results was created.	You need to set up daily transfer of the package to the License Metric Tool server. For more information, see: Setting up daily transfer of scan results to the License Metric Tool server (disconnected scenario).		✓	✓
The endpoint_id.txt file was created in the config directory.	The file contains the host name, and the time stamp of the first setup of the disconnected scanner. The combination of these two elements becomes an identifier of a computer. In case of scanner upgrade, or re-installation, the existing identifier from the file is used. If the file is missing, a new identifier is created for the computer that causes duplication of the discovered software in License Metric Tool.	✓	✓	✓