Scanner catalogs are used by the scanner to
discover software on the endpoints. The catalogs are automatically updated after each import of the
IBM software catalog. Use this procedure only if the automatic update of the scanner catalogs
fails.
Before you begin
Before you force the update of scanner catalogs,
ensure that the following requirements are met.
- The License Metric Tool server is visible to the BigFix server.
- If Secure Socket Layer (SSL) is enabled in License Metric Tool, the BigFix server recognizes SSL certificates of License Metric Tool as valid.
Procedure
-
Check whether the action that automatically updates scanner catalogs was created.
-
Log in to the BigFix console.
-
In the navigation bar, click Actions.
-
In the upper-right pane, locate the Catalog Download (Version
version) action.
The source of the action should be Master Operator Site.
-
If the action exists, check whether it failed due to prefetch problems. If it does not exist,
go to step 3.
-
Select the Catalog Download (Version version)
action.
-
Open the Computers tab, and double-click a computer on which the status of
the action is Failed.
-
Check whether the reason of the failure is a problem with prefetching the catalog.
Failed prefetch catalog.xml.bz2
If the status is Failed, communication between the BigFix server and the License Metric Tool server is blocked. Ensure that the
servers can communicate. Then, download the Catalog Download Fixlet to force the catalog update. If
you cannot change the configuration to allow communication between servers, edit the fixlet so that
the License Metric Tool server can download catalogs from the
BigFix server, and then run the fixlet.
-
Download the fixlet for forcing the update of scanner catalogs.
-
Log in to License Metric Tool.
-
Go to the following URL:
https://<IP_address>:<port>/sam/catalog/catalog_updates/cit_download.
Where:
- <IP_address>
- IP address of the License Metric Tool
server.
- <port>
- Port that is used by the License Metric Tool
server.
Save the catalog_download.bes file to your computer.
- Optional:
If the problem is caused by the lack of communication between servers, edit the
catalog_download.bes file and substitute the IP_address and
port of the License Metric Tool server with values that
allow the server for downloading scanner catalogs from the BigFix server.
prefetch catalog.xml.bz2 sha1:24dcb13c743f2f92b0c5e9887e9df1d4491c4a66
size:398083 http://IP_address:port/sam/catalogs/CIT_catalog_WINDOWS.xml.bz2
sha256:1e81c865d7fc96468649dbd5c334a2d77b12c5dd252671e22a7e5df0bd7ccbbe
Important: Change the IP_address and port for all
catalogs.
-
Upload the catalog_download.bes file to the BigFix console and run the Catalog Download (Version:
version) fixlet.
-
Copy the file to the computer where the BigFix console is installed.
-
Log in to the BigFix console.
-
To import the file to the console, click .
-
Open the directory where you store the catalog_download.bes file, select
the file, and click Open. The file is imported.
-
In the left pane, click . The list of available fixlets opens in the upper right pane.
-
Select Catalog Download (Version: version), and click
Take Action.
-
Select computers on which you want to run the fixlet, and click
OK.
-
Wait for the next scheduled software scan and import of data or run these actions manually. For
more information, see: Initiating software scans and Scheduling
imports of data.
- Optional:
If the problem is not solved, manually copy the catalog files from the License Metric Tool server to the BigFix server.
-
Log in to the computer where the License Metric Tool server is
installed and go to the following directory.
-
/opt/ibm/LMT/wlp/usr/servers/server1/data/sam/public/catalogs
-
C:\Program Files\IBM\LMT\wlp\usr\servers\server1\data\sam\public\catalogs
-
Copy the following files to a temporary folder on the computer where the BigFix server is installed.
- CIT_catalog_AIX.xml.bz2
- CIT_catalog_HPUX.xml.bz2
- CIT_catalog_I5OS.xml.bz2
- CIT_catalog_LINUX.xml.bz2
- CIT_catalog_SUN.xml.bz2
- CIT_catalog_WINDOWS.xml.bz2
-
Open the catalog_download.bes file that you downloaded in step 3 in a text editor, and check the
sha1
value for each catalog file.
For example, the
sha1
value for the catalog on Windows is
24dcb13c743f2f92b0c5e9887e9df1d4491c4a66
.
prefetch catalog.xml.bz2 sha1:24dcb13c743f2f92b0c5e9887e9df1d4491c4a66
size:398083 http://host_name:port/sam/catalogs/CIT_catalog_WINDOWS.xml.bz2
sha256:1e81c865d7fc96468649dbd5c334a2d77b12c5dd252671e22a7e5df0bd7ccbbe
Change
the names of all catalog files to their
sha1
values.
-
Copy the renamed catalog files to the following directory.
-
/var/opt/BESServer/wwwrootbes/bfmirror/downloads/sha1
-
C:\Program Files (x86)\BigFix Enterprise\BES
Server\wwwrootbes\bfmirror\downloads\sha1
-
Wait for the next scheduled software scan and import of data or run these actions
manually.
Results
Scanner catalogs are imported to the computers in your infrastructure and are used to
discover the installed software.