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

Edit online

9.2.5 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.

Before you begin

  • To perform this task, you must have the following privileges.
    • IBMi *ALLOBJ authority
    • UNIX root
    • Windows administrative privileges with elevation
  • UNIX Ensure that crontab is installed.
  • Solaris For Solaris, install the scanner on all required zones and domains. For more information, see: Installation of the disconnected scanner on Oracle Solaris.

About this task

Scanner installation path is the location where you upload the installation files. After you install the disconnected scanner, its installation path cannot be changed. To install the disconnected scanner in a different location, back up the endpoint_id.txt file, configuration files, packages with scan results, and logs. Then, uninstall the scanner, move the files to a different directory, and install the scanner in the new location. For more information, see: Upgrading the disconnected scanner (disconnected scenario).

Procedure

  1. Go to the directory where you unpacked the disconnected scanner package.
  2. Linux 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 debugfs 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. Solaris 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. 9.2.23 If the computer runs on a public cloud, go to the config folder, open the setup_config.ini file, and specify the type of the public cloud in the PUBLIC_CLOUD_TYPE parameter. For more information, see: Configuration parameters of the disconnected scanner (disconnected scenario).
  5. Change to the directory where you copied the disconnected scanner files.
    • IBMi Run QSH to enter the Qshell, and run the following command. 
      cd /cit
    • UNIX Windows 
      cd <disconnected_scanner_dir>
  6. To install the disconnected scanner and set up regular scans, run the following script.
    • IBMi ./setup_all.sh
    • UNIX ./setup.sh
    • Windows 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.
    • IBMi Capacity scan
    • UNIX Windows Software and capacity scans
    For more information about scan frequency, see: Schedule of disconnected scanner actions (disconnected scenario).
  7. Validate the content of the computer.yml file. For more information, see: Content of the computer.yml file (disconnected scenario).
    • IBMi <disconnected_scanner_dir>/config/computer.yml
    • UNIX Windows <disconnected_scanner_dir>/work/computer.yml

Results

The scanner was installed. As a result, a number of actions were performed or scheduled. For more information, see: Actions created by the disconnected scanner (disconnected scenario).

What to do next