Explanation of relevance expressions

Edit online

Each relevance expression checks whether a particular condition is met to ensure that a fixlet or task can complete successfully. If any condition is not met (results of the analysis show "False"), the fixlet or task is not relevant. Analyze the meaning of relevance expressions from the fixlets that are most commonly used to learn how to troubleshoot problems with fixlet relevance.

Important: Relevances are based on the content of site in version 150. If you have fixlets from a different version of the site, relevance numbers or their content might differ. To check the version of your site, see: Checking the version of the fixlet site.

Install or Upgrade Scanner

Table 1. Relevance expressions from the Install or Upgrade Scanner fixlet
Relevance Number	Relevance Explanation	Troubleshooting
1	This relevance checks whether the BigFix® client is a proxy agent.	The task is relevant only on clients that do not serve as BigFix proxy agents.
2	This relevance checks whether scans that are scheduled on the endpoint were blocked by using the Add Targeting Exception to Temporarily Disable Scans fixlet. When you run this fixlet on an endpoint, it blocks the installation or upgrade of the scanner.	To revert this change, run the Remove Targeting Exception to Resume Scans fixlet.
3	This relevance checks whether the operating system is supported by the scanner.	The operating system is not supported by the scanner. Verify whether the operating system is supported by the disconnected scanner. If yes, run the Download the Disconnected Scanner Package (version) fixlet to download the disconnected scanner and install it. If not, the operating system is not supported by License Metric Tool at all. For the list of supported operating systems, see: Supported operating systems.
4	This relevance checks whether the scanner is already installed.	The version of the scanner that you are attempting to install is already installed on the computer. If your BigFix server is installed on a computer with Internet access, you have the latest version of the scanner installed on the target computer. If your BigFix server is on a computer without the Internet access, verify whether you have the latest fixlet site available. If not, update the content of the fixlet site. Then, re-run the fixlet. For more information, see: Checking the version of the fixlet site.
5	This relevance checks disk space requirements.	Ensure that the computer meets disk space requirements. For more information, see: Disk space requirements for the BigFix client (BigFix scenario).
6	This relevance checks whether the catalog-based scan is currently running on the computer. Upgrade of the scanner is not possible during the scan.	Wait for the scan to complete and retry.
7	This relevance checks whether the software identification tags scan is currently running on the computer. Upgrade of the scanner is not possible during the scan.	Wait for the scan to complete and retry.
8	This relevance checks whether the capacity scan is currently running on the computer. Upgrade of the scanner is not possible during the scan.	Wait for the scan to complete and retry.
9	This relevance checks the version of `x1C.rte` and `xlC.aix61` libraries.	Upgrade the libraries to version 13.1.0.0 or higher.

Run Capacity Scan and Upload Results

Table 2. Relevance expressions from the Run Capacity Scan and Upload Results fixlet
Relevance Number	Relevance Explanation	Troubleshooting
1	This relevance checks whether the BigFix client is a proxy agent.	The task is relevant only on clients that do not serve as BigFix proxy agents.
2	This relevance checks whether scans that are scheduled on the endpoint were blocked by using the Add Targeting Exception to Temporarily Disable Scans fixlet. When you run this fixlet on an endpoint, it blocks the installation or upgrade of the scanner.	To revert this change, run the Remove Targeting Exception to Resume Scans fixlet.
3	This relevance checks whether the scanner is installed on the endpoint.	Install the scanner. For more information, see: Installing the scanner (BigFix scenario).
4	This relevance checks whether the capacity scan is currently running on the computer. Running two scans at the same time is not possible.	Wait for the scan to complete and retry.
5	This relevance checks whether License Metric Tool is registered as an exploiter of the scanner. The scanner might be installed as part of a different application.	Install the scanner. For more information, see: Installing the scanner (BigFix scenario).
6	This relevance checks whether the LMT/CIT folder exists in the installation directory of the BigFix client. The directory is used to store scan results and should be automatically created during the installation of the scanner.	Install the scanner. For more information, see: Installing the scanner (BigFix scenario).
7	This relevance checks whether the cit_config.xml legacy configuration file exists in the following directories: C:\Program Files (x86)\BigFix Enterprise\BESClient\LMT\CIT var/opt/BesClient/LMT/CIT	Upgrade the scanner and retry.
8	This relevance checks whether `gzip` package is available on the endpoint.	Perform the following actions. If you use an older version of the scanner, update the scanner to the latest version and retry. If you use the latest version of the scanner, uninstall the scanner and install it again. Then, retry. Install `gzip`.

Initiate Software Scan

Table 3. Relevance expressions from the Initiate Software Scan fixlet
Relevance Number	Relevance Explanation	Troubleshooting
1	This relevance checks whether the BigFix client is a proxy agent.	The task is relevant only on clients that do not serve as BigFix proxy agents.
2	This relevance checks whether scans that are scheduled on the endpoint were blocked by using the Add Targeting Exception to Temporarily Disable Scans fixlet. When you run this fixlet on an endpoint, it blocks the installation or upgrade of the scanner.	To revert this change, run the Remove Targeting Exception to Resume Scans fixlet.
3	This relevance checks whether the scanner is installed.	Install the scanner. For more information, see: Installing the scanner (BigFix scenario).
4	This relevance checks whether the scanner is in version 2.7.0.2034 or higher.	The scanner is obsolete. Update the scanner to the latest version and retry.
5	This relevance checks whether the catalog-based scan is currently running on the computer. A new scan cannot be started when another scan is already in progress.	Wait for the scan to complete and retry.
6	This relevance checks whether the software identification tags scan is currently running on the computer. A new scan cannot be started when another scan is already in progress.	Wait for the scan to complete and retry.
7	This relevance checks whether License Metric Tool is registered as an exploiter of the scanner. The scanner might be installed as part of a different application.	Install the scanner. For more information, see: Installing the scanner (BigFix scenario).
8	This relevance checks whether the software catalog exists. It should be automatically placed on the endpoint during the installation of the scanner.	If you use an older version of the scanner, update the scanner to the latest version and retry. If you use the latest version of the scanner, uninstall the scanner and install it again. Then, retry. If the problem persists, contact IBM Support.
9	This relevance checks whether `bzip2` or `7zip` archiver is installed. It should be automatically installed on the endpoint during the installation of the scanner.	Perform the following actions. If you use an older version of the scanner, update the scanner to the latest version and retry. If you use the latest version of the scanner, uninstall the scanner and install it again. Then, retry. Install `bzip2` or `7zip`. If the problem persist, contact IBM Support.
10	This relevance checks whether the cit_config.xml legacy configuration file exists in the following directories: C:\Program Files (x86)\BigFix Enterprise\BESClient\LMT\CIT var/opt/BesClient/LMT/CIT	If you use an older version of the scanner, update the scanner to the latest version and retry. If you use the latest version of the scanner, uninstall the scanner and install it again. Then, retry. If the problem persists, contact IBM Support.
11	This relevance checks whether the zip.exe file exists in the C:\Program Files (x86)\BigFix Enterprise\BESClient\LMT\CIT directory. This relevance checks whether `gzip` package is available on the endpoint.	Perform the following actions. If you use an older version of the scanner, update the scanner to the latest version and retry. If you use the latest version of the scanner, uninstall the scanner and install it again. Install `gzip`. If the problem persist, contact IBM Support.

Upload Software Scan Results

Table 4. Relevance expressions from the Upload Software Scan Results fixlet
Relevance Number	Relevance Explanation	Troubleshooting
1	This relevance checks whether the BigFix client is a proxy agent.	The task is relevant only on clients that do not serve as BigFix proxy agents.
2	This relevance checks whether the following directory contains any scan results to be packed and uploaded: C:\Program Files (x86)\BigFix Enterprise\BESClient\LMT\CIT var/opt/BesClient/LMT/CIT	New software scan results are not available to be uploaded. A new scan did not run yet according to the schedule or the last scan did not complete successfully. Re-run the software scan. Monitor computer statuses to see whether there are any further problems. For more information, see: Statuses on the Software Scan Health widget.
3	This relevance checks whether scans that are scheduled on the endpoint were blocked by using the Add Targeting Exception to Temporarily Disable Scans fixlet. When you run this fixlet on an endpoint, it blocks the installation or upgrade of the scanner.	To revert this change, run the Remove Targeting Exception to Resume Scans fixlet.
4	This relevance checks whether the catalog-based scan is currently running on the computer. Scan results cannot be packed and upload when the scan is in progress.	Wait for the scan to complete and retry.
5	This relevance checks whether the software identification tags scan is currently running on the computer. Scan results cannot be packed and upload when the scan is in progress.	Wait for the scan to complete and retry.
6	This relevance checks whether `bzip2` or `7zip` archiver is installed. It should be automatically installed on the endpoint during the installation of the scanner.	Perform the following actions. If you use an older version of the scanner, update the scanner to the latest version and retry. If you use the latest version of the scanner, uninstall the scanner and install it again. Then, retry. Install `bzip2` or `7zip`. If the problem persist, contact IBM Support.
7	This relevance checks whether the zip.exe file exists in the C:\Program Files (x86)\BigFix Enterprise\BESClient\LMT\CIT directory.	If you use an older version of the scanner, update the scanner to the latest version and retry. If you use the latest version of the scanner, uninstall the scanner and install it again. If the problem persists, contact IBM Support.

Upgrade to the latest version of IBM License Metric Tool 9.x

Table 5. Relevance expressions from the Upgrade to the latest version of IBM License Metric Tool 9.x fixlet
Relevance Number	Relevance Explanation	Troubleshooting
1	This relevance checks whether the BigFix client is a proxy agent.	The task is relevant only on clients that do not serve as BigFix proxy agents.
2	This relevance checks whether the operating system is supported by the version of License Metric Tool to which you are upgrading.	Verify that the operating system is supported. For more information, see: Supported operating systems. If the current version of the operating system is no longer supported, upgrade the operating system or migrate the License Metric Tool server to a computer with a supported operating system. For more information, see: Migrating between computers.
3	This relevance checks the version of the License Metric Tool server that is currently installed. It also checks whether the LMT_Server_Path_[user_ID] parameter is set on the endpoint.	Verify what version of License Metric Tool is currently installed. For more information, see: Checking the version of License Metric Tool. If you have the latest version installed, no further action is required. Otherwise, set the LMT_Server_Path_[user_ID] parameter on the endpoint. For more information, see: Installation and upgrade problems.
4	This relevance checks whether upgrading the License Metric Tool server by using a fixlet is supported for the version of the server that is currently installed.	Upgrade of the server by using a fixlet is not possible if the server was installed by a non-root user. Upgrade the server manually in silent or interactive mode. Upgrade directly to the latest version is not possible if your current License Metric Tool server is older than eight releases. In such case, you must use an intermediate installer. For more information, see: Upgrading to the latest version.
5	This relevance checks whether the version of the database that is currently used is supported by the version of the License Metric Tool server to which you are upgrading.	Verify what versions of the database are supported. For more information, see: Software requirements (BigFix scenario). Upgrade the License Metric Tool database to a supported version.
6	This relevance checks whether enough free disk space is available on the drive where the License Metric Tool server is installed.	Review disk space requirements that are provided in the fixlet description. Ensure that enough disk space is available on the endpoint and re-run the fixlet.
7	This relevance checks whether enough free disk space is available in the system temporary directory.	Review disk space requirements that are provided in the fixlet description. Ensure that enough disk space is available on the endpoint and re-run the fixlet.
8	This relevance checks whether enough free disk space is available in the BigFix client installation directory to download the License Metric Tool installer.	Review disk space requirements that are provided in the fixlet description. Ensure that enough disk space is available on the endpoint and re-run the fixlet.