Discovering software and hardware on IBM i

Available from 9.2.5. You can discover software and hardware inventory on IBM i systems by using disconnected scans that do not require direct connection between the scanned computers and BigFix server. Scripts that are provided in the disconnected scanner package initiate software and capacity scans, and prepare scan results that you later on upload to BigFix Inventory.

Important: Because BigFix client is not available for IBM i, the disconnected scanner is the only method of software and hardware discovery on IBM i systems. Unlike on other operating systems, approval from IBM Compliance is not required to use disconnected scans on IBM i.

Disconnect Scanner for IBM i is provided by IBM and HCL redistributes the same with BigFix Inventory. The IBM i Disconnected Scanner includes an embedded IBM i Catalog. So, the option to update catalog using BigFix Inventory generated catalog for IBM i has been disabled since version 9.2.17.

You must periodically update the IBM i Disconnected Catalog to update any currency change. You can also use newer IBM i Disconnected Scanner package with older BigFix Inventory versions

Ignore any notification about outdated catalog for IBM i endpoint in BigFix Inventory version below 10.0.2. BFI Server automatically ignores the notification since BFI Server version 10.0.2.

Disconnected scanner package

To collect the software and hardware inventory data, you need an endpoint package that consists of:
  • Scanner
  • Configuration files
  • Scripts to run the scans and prepare the scan result package
The scripts initiate software and capacity scans, gather scan results, and adjust them to the format that is compatible with BigFix Inventory. If the scripts are not appropriate for your environment, you can edit and customize them, or create new scripts that better fit your needs. You can also use a manual procedure. However, it is not recommended for inexperienced users.

Scalability

You can collect data from up to 25000 disconnected endpoints on condition that the computer where the BigFix Inventory server is installed meets hardware requirements for very large environments. For more information about the requirements, see Hardware requirements.

Additionally, to ensure good performance of importing the scan results, complete the following configuration.

  • Run the software scan on weekly basis.

  • Distribute the import of result packages over the week so that a subset of packages is imported every day. For example, import 5000 packages every day from Monday to Friday.

  • Set up automatic removal of scan results from the disconnected data source directory after the results are successfully imported to BigFix Inventory. To automatically remove the packages, go to Management > Advanced Server Settings and set the value of the delete_successfully_imported_scans parameter, to true.

  • Configure the transaction logs size and increase the Java heap size. For more information, see: Tuning performance in medium and large environments.

Scan frequency

The disconnected scanner triggers the software and capacity scan. Each of these scans consists of a set of scripts and binaries that use up to 5 jobs. Thus, if you use the same queue, make sure that the job limit is set to 10 or more.

For information about default and minimal scan frequency as well as recommended frequency of importing scan results, see: Frequency of scans and uploads of data.

The disconnected scanner triggers the following scans:
  • Capacity scan - The scan runs via the BFI_HW jobs that are scheduled during the installation as QSECOFR user on its default queue. The capacity scan runs every 30 minutes.
  • Software scan - You can schedule the software scan to run according to your preference and use any specified queue. The recommended scan frequency is once a month.

A software scan scheduled / run on demand by end user using user/queue specified by end user. Recommended to be executed once a month.

Multiple environments

When you have multiple environments, for example test and production, ensure that the following requirements are met:
  • Every computer reports only one of the environments.
  • Results of the disconnected scan from one environment are not uploaded to BigFix Inventory that monitors the other environment.

Limitations

  • Resource utilization, and metering data are not supported. For more information, see: Raw utilization of license metrics.
  • Scanning remote shared file systems is not supported.
  • Detailed hardware scan cannot be collected if you use the disconnected scan.
  • The disconnected scanner always collects full scans, not delta scans.
  • The disconnected scan does not include additional computer properties that are defined by the user. To collect these details, you need to define additional entries in the computer.yml file.