IBM Tivoli Software IBM Tivoli Software

[ Bottom of Page | Previous Page | Next Page | Contents ]


Documentation problems and corrections contained in this fix pack

User's Guide for Inventory

This section contains new and updated information for IBM(R) Tivoli(R) Configuration User's Guide for Inventory:

APAR IY88685

Add a new chapter called "Installing and uninstalling Common Inventory Technology (CIT)". The new chapter contains the following text:

Installing Common Inventory Technology (CIT)

Tivoli Configuration Manager 4.2.3 Fix pack 3 requires Common Inventory Technology (CIT) Version 2.3. When a Tivoli Configuration Manager activity is started on a workstation, Tivoli Configuration Manager checks if Common Inventory Technology (CIT) is already installed and installs it, if it is not found. CIT is installed using default paths, so during the installation the following directories are created:

CIT ini file directory
Where the cit.ini file and other programs needed during the installation are stored. This directory is /etc/cit on UNIX platforms, and %WINDIR%\cit on Windows platforms. The cit.ini file contains the list of each exploiter which installed CIT.
CIT product binaries directory
Where the binary files of the product are stored. This directory is /opt/tivoli on UNIX, and C:\Program Files\Tivoli\cit on Windows platforms.
CIT log and trace files directory
Where the log and trace files of the product are stored. This directory is /usr/ibm/tivoli/common/CIT/logs on UNIX platforms, and C:\Program Files\ibm\tivoli\common\CIT\logs on Windows platforms.

If you update from IBM Tivoli Configuration Manager, Version 4.2.3 Fix Pack 1 to IBM Tivoli Configuration Manager, Version 4.2.3 Fix Pack 3, the data created with CIT 1.1.1 is removed. For example, files such as wscanner*, libInvHW.*, libInvSW.* and libInvReg.* are removed from the lcf_root/inv/SCAN directory.

To enable the Inventory endpoint traces, run the wdistinv command using the inv_ep_debug option. Every time an Inventory scan is run on the endpoint, a log file called INVxxxxx.LOG (where xxxxx is the scan_id) is created under the inv/SCAN directory.

As an alternative to using default paths, you can install the CIT binary files in other directories by performing the following steps:

  1. If you have already installed CIT manually when installing IBM Tivoli Configuration Manager, Version 4.2.3 Fix Pack 2, run the following command to remove the installed software packages:
    $BINDIR/../generic/inv/SCRIPTS/CIT_import.pl -uninst
    If you have not previously installed CIT, move to step 2.
  2. On the Inventory server, run the following command:
    $BINDIR/../generic/inv/SCRIPTS/CIT_import.pl CD_ROM/CIT_SPB
    where
    CD_ROM/CIT_SPB
    Specifies the path where the CIT_Preinstall.spb and CIT.spb software packages are located on the IBM Tivoli Configuration Manager, Version 4.2.3 Fix Pack 3 CD 1.
    You can also copy the software packages to a local folder and run the command locally.
  3. As a result, two software packages are created in a new profile manager called Inventory_CIT_PM.
  4. On the Inventory server, run the following command to install the two software packages (CIT_Preinstall.CIT and CIT.2.3.1012 ) on custom paths:
    winstsp -f -DCIT_ExploiterID=ITCM  -DCIT_DestinationDirectory=/mydir
     @CIT_Preinstall.CIT @Endpoint:ep1
    where:
    /mydir
    Is the directory on the endpoint where CIT is installed.
    ep1
    Is the name of the endpoint.
  5. On the Inventory server, run the following command:
    winstsp -f @CIT.2.3.1012 @Endpoint:ep1 
    where:
    ep1
    Is the name of the endpoint.

This procedure must be completed before performing any Inventory or Tivoli License Manager operation based on CIT, because also Tivoli License Manager can install CIT on the same workstation. By following this procedure you can customize the CIT product binary directory, but you cannot customize the cit.ini directory and the CIT log files directory.

Uninstalling Common Inventory Technology (CIT)

You can uninstall CIT using the Software Distribution component of IBM Tivoli Configuration Manager. This operation requires uninstalling CIT for all its registered exploiters. Before uninstalling CIT, verify that it is no longer required by any of the exploiters listed in the cit.ini file.

You must uninstall CIT software packages in the following order.

  1. Uninstall the CIT_Preinstall.CIT software package for each registered exploiter. Each CIT exploiter is registered in the cit.ini file with the CITExploiterID key. The string identifying IBM Tivoli Configuration Manager is as follows: CITExploiterID=ITCM.
  2. Uninstall the CIT.2.3.1012 software package

To uninstall CIT using the Software Distribution component of IBM Tivoli Configuration Manager, perform the following steps:

  1. Set the environment to run the disconnected Software Distribution command line.
  2. Uninstall CIT for each exploiter registered in the cit.ini file. To perform this operation, run the following commands:
    1. set CIT_ExploiterID=exploiter_ID
      where
      exploiter_ID
      Is the ID of the exploiter as registered in the cit.ini file. The ID for IBM Tivoli Configuration Manager is ITCM.
    2. wdrmvsp -f CIT_Preinstall.CIT
    3. Repeat steps 2a and 2b for each registered exploiter.
  3. After uninstalling the CIT_Preinstall.CIT software package for each registered exploiter, type the following command to complete the uninstallation:

    wdrevsp -f @CIT.2.3.1012

Table 53

lists the errors which might occur if you do not correctly manage the list of exploiters in the cit.ini file:

Table 53. CIT return codes
Return code Error reason Recovery action
11 At least one exploiter is still registered in the cit.ini file. Remove the exploiter ID as explained in step 2.
12 You have not specified the exploiter name. Specify the exploiter name.
13 The exploiter you specified is unknown. Check the exploiter name in the cit.ini file and specify it again.
Managing the Inventory bundle dependency set

You can add, remove, and verify the automatic download of IBM Tivoli License Manager and CIT using the standard Framework bundle dependency set. To perform this operation, use the winvdeps command.

winvdeps

Specifies dependency sets that a method needs to run.

Syntax

winvdeps -a depset

winvdeps -r depset

winvdeps -s depset

Description

The winvdeps command specifies dependencies that a method needs to run. You can use the command to add, remove, and verify a dependency set.

Options

-a
Adds a dependency set.
-r
Removes a dependency set.
-s
Verifies the presence of a dependency set.
depset
The name of the dependency set. Supported values are as follows:
CIT
The name of the dependency set for CIT.
TLM
The name of the dependency set for TLM.

Return Values

The winvdeps command returns one of the following:

0
Indicates that winvdeps started successfully.
-1
Indicates that winvdeps failed due to a generic error.

Examples

To accept add the CIT dependency set, enter the following command:

winvdeps -a CIT

See Also

None.

Database Schema Reference

This section contains new and updated information for IBM Tivoli Configuration Database Schema Reference:

Defect 58465
In Chapter 4 "Queries", in the section "Pervasive device queries" the following information should be added:

DEVICES_NOT_BOOTSTRAPPED_QUERY

Returns all the Nokia devices which have not yet been bootstrapped.

Runs against the table DEVICE.

The column in this query is as follows:

BOOTSTRAPPED

Defect 58465
In Chapter 5 "Configuration repository tables", in the section "Pervasive device tables" the following information should be added:

DEVICE

Stores the details of the pervasive devices. One entry exists for each device registered on the Web Gateway.

Populated by a device creation on the Tivoli server, by an auto-enrollment, or by a Provisioning job successfully run.

The columns in this table are as follows:

COMPUTER_SYS_ID
DEVICE_NAME
FRIENDLY_NAME
DEVICE_CLASS_ID
LABEL
SERIAL_NUMBER
MAKE
MODEL
DEV_DESCRIPTION
DEVICE_STATUS
BOOTSTRAPPED
NEW_DEVICE
LAST_EVALUATED_TIMESTAMP
JOB_PROFILE_IGNORED
NOTIFICATION_TYPE
DEVICE_NAME_INUSE
ENROLLED_TIMESTAMP
CREATION_TIMESTAMP
LAST_MODIFIED                
Defect 58507
In Chapter 4 "Queries", in the section "Pervasive device queries" the following information should be added:

MO_TARM_LOCK_QUERY

Returns information on the MO_TARM object of the Nokia devices.

Runs against the view MO_TARM_LOCK_VIEW.

The column in this query is as follows:

LABEL
COMPUTER_SYS_ID
LOCK_LEVEL
MAX_AUTO_LOCK
AUTO_LOCK
RECORD_TIME
Defect 58507
In Chapter 5 "Configuration repository tables", in the section "Pervasive device tables" the following information should be added:

MO_TARM_LOCK

Stores the device information about the lock status.

The columns in this table are as follows:

COMPUTER_SYS_ID
LOCK_LEVEL
MAX_AUTO_LOCK
AUTO_LOCK
RECORD_TIME
Defect 58507
In Chapter 3 "Configuration repository views", in the section "Pervasive device views" the following information should be added:

MO_TARM_LOCK_VIEW

Returns information on the MO_TARM object of the Nokia devices.

Based on the MO_TARM_LOCK table.

The columns of this view are as follows:

LABEL
COMPUTER_SYS_ID
LOCK_LEVEL
MAX_AUTO_LOCK
AUTO_LOCK
RECORD_TIME
Feature MR0826056352
In Chapter 5 "Configuration repository tables", in the section "Inventory tables", the following information should be added to the LPAR table:

Add to the list of the table columns:

Feature MR0826056352
In Chapter 5 "Configuration repository tables", in the section "Inventory tables", the following new section should be added to the chapter:

PHYSICAL_PROCESSOR

Displays the correct number of physical processors, logical processors assigned to each core, and the cores on the physical processor in the inventory tables, views, and queries.

The columns in this table are as follows:

COMPUTER_SYS_ID
PROCESSOR_ID
CORE_PER_PK_COUNT
LOG_PROC_PER_CORE
MANUFACTURER
FAMILY
TYPE
CPU_FREQ
L2_CACHE_SIZE
L3_CACHE_SIZE
BRANDNAME
SIGNATURE
RECORD_TIME
Feature MR0826056352
In Chapter 3 "Configuration repository views", in the sections LOGICAL_PARTITIONS_VIEW and LPAR_SYSTEMS_VIEW, the following information should be added:

Add the following column to the LPAR_SYSTEMS_VIEW:

Add the following columns to the LOGICAL_PARTITIONS_VIEW:

Feature MR0826056352
In Chapter 3 "Configuration repository views", in the section PROCESSOR_NUM_VIEW, the following information should be added:

Based on the COMPUTER e PHYSICAL_PROCESSOR tables.

Add the following columns to the PROCESSOR_NUM_VIEW:

Feature MR0826056352
In Chapter 3 "Configuration repository views", the following new section for the PHYSICAL_PROCESSOR_VIEW should be added:

PHYSICAL_PROCESSOR_VIEW

Displays the correct number of physical processors, logical processors assigned to each core, and the cores on the physical processor in the inventory tables, views, and queries.

Based on the COMPUTER and PHYSICAL_PROCESSOR tables.

The columns in this view are as follows:

Feature MR0826056352
In Chapter 4 "Queries", in the section "Inventory queries", the following information should be added to the PROCESSOR_NUM_QUERY:

Add to the list of the query columns:

Feature MR0826056352
In Chapter 3 "Configuration repository views", in the section "Historical Inventory views", the following information should be added:

H_PHYSICAL_PROCESSOR_VIEW

Feature MR0826056352
In Chapter 5 "Configuration repository tables", in the section "History tables for Inventory", the following information should be added:

H_PHYSICAL_PROCESSOR

Man page missing updates

This section provides information about commands that have been added or changed but for which new man pages are not available.

Software distribution

The changes to these commands are documented in the IBM Tivoli Configuration Manager: Reference Manual for Software Distribution.

Activity Planner

The changes to this command are documented in the IBM Tivoli Configuration Manager: User' Guide for Deployment Services.


[ Top of Page | Previous Page | Next Page | Contents ]