![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains new and updated information for IBM(R) Tivoli(R) Configuration Manager Planning and Installation Guide:
Ensure that the password you specify does not contain a special character at the end.
This contains the installation image and the InstallShield wizard for a fresh installation or an upgrade of IBM Tivoli Configuration Manager on any workstation that is not a managed node or a Tivoli server.
This section contains new and updated information for IBM Tivoli Configuration Manager User's Guide for Deployment Services:
To use the Activity Plan Editor and the Activity Plan Monitor GUIs from the Tivoli desktop, the user password can contain all the special characters from ASCII 32 to ASCII 127. The only special character that cannot be used is "double quotes".
If you are using a Sybase database in your Tivoli environment and the manual configuration of the environment is performed before installing the Activity Planner component, then the same configuration should be repeated after the Activity Planner installation because the settings of the LD_LIBRARY_PATH environment variable are overwritten by the Activity Planner installation.
If you are using a Sybase database in your Tivoli environment and the manual configuration of the environment is performed before installing the Directory Query component, then the same configuration should be repeated after the Directory Query installation because the settings of the LD_LIBRARY_PATH environment variable are overwritten by the Directory Query installation.
This section contains new and updated information for IBM Tivoli Configuration Manager Reference Manual for Software Distribution:
The corequisite_file stanza comprises two different sets of attributes, the add_file set and add_directory set.
the following information:
When you create a package that contains:
and install it in transactional, the two corequisite files (coreq_install and coreq_commit) are downloaded on the target. During the package installation, the coreq_install file is used and then deleted. During the package commit, the coreq_commit file is used but it is not deleted, because it might be used in the remove operation if performed in transactional mode.
in the table row for "name" under the column "required" replace "yes" with "no".
This section contains new and updated information for IBM Tivoli Configuration Manager User's Guide for Inventory:
For more details on these files, refer to the IBM Tivoli Configuration Manager 4.2.3 Patch Management Guide.
SUS Files | WSUS Files |
---|---|
mssecure.cab | wsusscan.cab |
mbsacli.exe | WindowsUpdateAgent20-x86.exe |
ApprovedItems.txt | ApprovedChanges.txt |
Sybase Server Error: Msgno 3621 Level 10 State 0 Command has been aborted due to "unique constraint violation" errors caused by attempts to insertrows already present in the database.This error can cause a decrease in performance.
The wtransfer command uses TAR software to compress the files to be transferred from one managed node to another. Some HP-UX platforms do not allow long file names, the size limit depends on the specific HP-UX version. So if the TAR software on the source workstation allows long file names, and the TAR software on an HP-UX target workstation does not, the files are not transferred. This problem can be solved only if a patch for the specific HP-UX version is available.
Another way to change the CIT installation directory is to overwrite the default CIT_DestinationDirectory variable by editing the CIT_Preinstall.spb software package. The modified CIT_Preinstall.spb should then be distributed against all the gateway bundle directories replacing the old software package.
After installing any Tivoli Configuration Manager fix pack or interim fix and before performing any Tivoli Configuration Manager activity on the endpoints of your environment, perform the following steps:
CIT.2.5.1003 CIT_Preinstall.CIT
lcf_bundle.41100\lib\aix4-r1\inv\CIT\SPB\CIT_Preinstall.spb lcf_bundle.41100\lib\hpux10\inv\CIT\SPB\CIT_Preinstall.spb lcf_bundle.41100\lib\linux-ix86\inv\CIT\SPB\CIT_Preinstall.spb lcf_bundle.41100\lib\linux-ppc\inv\CIT\SPB\CIT_Preinstall.spb lcf_bundle.41100\lib\linux-s390\inv\CIT\SPB\CIT_Preinstall.spb lcf_bundle.41100\lib\solaris2\inv\CIT\SPB\CIT_Preinstall.spb lcf_bundle.41100\lib\solaris2-ix86\inv\CIT\SPB\CIT_Preinstall.spb lcf_bundle.41100\lib\w32-ix86\inv\CIT\SPB\CIT_Preinstall.spb
Lpar:YES
Scanning virtual environments
Inventory uses the CIT capability to collect LPAR information in a VMware environment.
VMware versions supported by CIT are shown in the table below:
VMWare versions tested on CIT |
---|
ESX Server 3.0 |
ESX Server 3.01 |
ESX Server 3.02 |
ESX Server 2.5.3 |
Standard Inventory functions are not impacted whether the scans are performed on guest or host operating systems. However, due to a limitation of the data export function in the virtualization software, hardware and software discovery operations performed on guest operating systems might report incorrect data.
CIT provides an enabler to export correct data to the guest systems so that CIT instances installed on each operating system partition can discover and return correct data.
The CIT enabler stores the correct hardware information on the guest operating systems. In this way when a hardware Inventory scan starts on a guest operating system, the correct hardware configuration data is retrieved and stored in the Inventory RDBMS. You can query the data by running the LOGICAL_PARTITION_QUERY and the LOGICAL_PARTITIONED_SYSTEMS_QUERY
Starting the enabler
The CIT enabler is installed on the physical workstation which hosts the guest operating systems. The CIT enabler does not require an installation process. To use the CIT enabler, copy the files listed below from the /cit_enabler folder on the IBM Tivoli Configuration Manager, Version 4.2.3 Fix Pack 5 CD 1 to the workstation which hosts the guest operating systems:
Virtual software | Supported OS | Files |
---|---|---|
VMware | Microsoft Windows |
|
Linux |
|
You must install VMware VmPerl Scripting API before starting the enabler for the first time.
To start the enabler, launch the executable file from a shell or command prompt. You can optionally specify the -v option to generate a log file named env_out.txt, which is created in the same directory where the executable file is located.
Enabler return codes
The following is a list of the return codes returned by the enabler. Return codes help you identify the result of the command.
A return code of 0 indicates that the command completed successfully:
OK: CIT ENABLER return code = 0
while a nonzero return code indicates that an error occurred. The following example shows the case in which the user does not have enough privileges, when running the CIT enabler executable:
OK: CIT ENABLER return code = 11 ERROR: dispatcher return code = 11"
A complete list of all nonzero return codes is provided in the table below:
Return value | Code | Description |
---|---|---|
RETRIEVE_NODECAPACITY_ERROR | 1 | Cannot collect host system processor number. |
RETRIEVE_NODEID_ERROR | 2 | Cannot collect host system serial number. |
RETRIEVE_VMCAPACITY_ERROR | 3 | Cannot collect number of processors assigned to virtual machines. |
RETRIEVE_VMID_ERROR | 4 | Cannot collect virtual machines IDs. |
SET_GUESTINFO_ERROR | 5 | Cannot transfer information from host system to guest systems. |
GET_VMLIST_ERROR | 6 | Cannot retrieve list of registered virtual machines. |
CONNECT_VM_ERROR | 7 | Cannot establish connection with virtual machines. |
NO_PRIVILEGES | 11 | User does not have enough privileges when running the CIT enabler executable. |
GENERIC_ERROR | -1 | A generic error has occurred. For more information, enter the command again with the -v option. The resulting information is logged into the env_out.txt file. |
VMWARENOTFOUND_ERROR | 100 | VMware Server not found on host system. |
VMWARENOTSUPPORTED_ERROR | 105 | VMware Server version not supported. |
VMPERL_NOT_FOUND | 120 | VmPerl Scripting API not found or incorrectly configured. |
On the Inventory server, run the following command:
winstsp -f -ty @CIT.2.5.1003 @Endpoint:ep1 wcommtsp -f @CIT.2.5.1003 @Endpoint:ep1
where:
On the Inventory server, run the following command:
$BINDIR/../generic/inv/SCRIPTS/CIT_import.pl -d CD_ROM/CIT_SPB
where
You can also copy the software packages to a local folder and run the command locally.
If you experience issues related to Inventory hardware and software scans, for example the scan fails or does not collect all the expected information, it is necessary to use a troubleshooting procedure specific for the Common Inventory Technology component.
Collect the configuration files that Tivoli Configuration Manager writes and passes to the Common Inventory Technology scanners as input parameters, and the command line syntax that Tivoli Configuration Manager uses when invoking the Common Inventory Technology scanners. Depending on the different customizations of the InventoryConfig profile and the platform on which the scan runs, the above-mentioned commands and configuration files are:
Windows | ||
---|---|---|
Type of scan | Command | Configuration file |
Hardware scan |
C:\Program Files\tivoli\cit \bin\wscanhw -c C:\win_ep_name\ \inv\SCAN\config.xml -o C:\win_ep_name\\inv\SCAN\ tivhscan.mif-m |
config.xml |
Scan for installed products using signature matching |
C:\Program Files\tivoli\cit \bin\wscansw -i C:\win_ep_name\ \inv\SCAN\wscansw.xml -o C:\win_ep_name\\inv\SCAN\ swscan.xml -c C:\win_ep_name\ \inv\SCAN\config.xml -e C:\win_ep_name\\inv\SCAN\ warning.out |
wscansw.xml, config.xml |
Scan files for basic information |
C:\Program Files\tivoli\cit \bin\wscanfs -c C:\win_ep_name\ \inv\SCAN\config.xml -o C:\win_ep_name\ \inv\SCAN\tivfscan.mif -m |
config.xml |
Scan files for header information |
C:\Program Files\tivoli\cit\ bin\wscanfs -c C:\win_ep_name\ \inv\SCAN\config3.xml -o C:\win_ep_name\\inv\SCAN\ tivwscan.mif -m |
config3.xml |
Scan registry for product information |
C:\Program Files\tivoli\cit\ bin\wscanvpd -c C:\win_ep_name\ \inv\SCAN\config.xml -o C:\win_ep_name\\inv\SCAN\ tivrscan.mif -m |
config.xml |
UNIX | ||
---|---|---|
Type of scan | Command | Configuration file |
Hardware scan |
/opt/tivoli/cit/bin/wscanhw -c /tivoli/unix_ep_name/ /inv/SCAN/config.xml -o /tivoli/unix_ep_name //inv/SCAN/ tivhscan.mif -m |
config.xml |
Scan for installed products using signature matching |
/opt/tivoli/cit/bin/wscansw -i /tivoli/unix_ep_name/ /inv/SCAN/wscansw.xml -o /tivoli/unix_ep_name/ /inv/SCAN/swscan.xml -c /tivoli/unix_ep_name//inv/ SCAN/config.xml -e /tivoli/ unix_ep_name//inv/SCAN/ warning.out |
wscansw.xml, config.xml |
Scan files for basic information |
/opt/tivoli/cit/bin/wscanfs -c /tivoli/unix_ep_name// inv/SCAN/config.xml -o /tivoli/unix_ep_name/ /inv/SCAN/tivfscan.mif -m |
config.xml |
Scan registry for product information |
/opt/tivoli/cit/bin/wscanvpd -c /tivoli/unix_ep_name//inv/ SCAN/config.xml -o /tivoli/ unix_ep_name//inv/SCAN/ tivrscan.mif -m |
config.xml |
The Common Inventory Technology scanners might return error codes. Return codes help you identify the result of the command: a return code of 0 indicates that the command completed successfully, while a nonzero return code indicates that an error occurred. A list of all nonzero return codes is given in Table 74:
Return value | Code | Description |
---|---|---|
WSRC_WRONG_PARMS | 1 | One or more CLI options are incorrect. |
WSRC_INPUT_FILE_PARSE_ERROR | 2 | An error occurred while parsing the configuration file. |
WSRC_SIGNATURE_FILE_PARSE_ERROR | 3 | An error occurred while parsing the signature file. |
WSRC_OUTPUT_FILE_ERROR | 4 | An error occurred while writing the output file. |
WSRC_INPUT_FILE_ERROR | 5 | An error occurred while reading the input file. |
WSRC_MISSING_SIGNATURE_FILE | 6 | No signature file was specified and no default signature file is available. |
WSRC_VALUE_OUT_OF_BOUND | 7 | One of the values you specified exceeds the assigned limits. |
WSRC_INTERNAL_ERROR | 8 | An internal error has occurred. |
WSRC_TIMEOUT_ELAPSED | 9 | The specified timeout has expired. |
WSRC_UPGRADE_IN_PROGRESS | 10 | CIT is being upgraded and commands are momentarily not responding. |
WSRC_FILE_READ_ONLY | 11 | The output file is read only. |
WSRC_INIFILE_NOT_FOUND | 12 | The cit.ini file was not found. |
WSRC_CITFILE_NOT_FOUND | 13 | The CIT configuration file was not found. |
WSRC_CCLOGFILE_NOT_FOUND | 14 | The CitTrace.properties file was not found. |
WSRC_KEY_NOT_FOUND | 15 | The value you specified is incorrect. |
WSRC_VALUE_NOT_VALID | 16 | The specified value is not valid. |
WSRC_KEY_CANNOT_CHANGE | 17 | The specified key cannot be modified. |
WSRC_FILE_CANNOT_OPEN | 18 | Cannot open the specified file. |
WSRC_FILE_CANNOT_RENAME | 19 | Cannot rename the specified file. |
WSRC_FILE_CANNOT_DELETE | 20 | Cannot delete the specified file. |
WSRC_CITFILE_NOT_VALID | 21 | The cit.ini file is corrupt. |
WSRC_CIT_TRACEFILE_NOT_VALID | 22 | The trace file is corrupt. |
WSRC_INVALID_AGE | 24 | The age you specified is incorrect. |
WSRC_INVALID_TIMEOUT | 25 | The timeout you specified is incorrect. |
WSRC_INVALID_ATTRIBUTE | 26 | The attribute you specified is incorrect. |
WSRC_INVALID_OUTPUT_FORMAT | 27 | The output format you specified is not supported. |
WSRC_CANNOT_LOAD_PROVIDER | 28 | The required .dll or shared library file is not available. |
WSRC_QUERY_TIMED_OUT | 29 | The query has reached the timeout. |
WSRC_QUERY_FAILED | 30 | The query has failed. |
WSRC_PROCESS_INTERRUPTED | 31 | The process was interrupted. |
WSRC_NO_CONFIG_NAME | 32 | No configuration file was specified. |
WSRC_NO_CONFIG_OPTION | 33 | No configuration option was specified. |
WSRC_NO_OUTPUT_NAME | 34 | No output file was specified. |
WSRC_NO_PARMS | 35 | No parameters were specified. |
WSRC_EMPTY_CONFIG_ELEMENT | 36 | The configuration file contains an empty element. |
WSRC_FAILURE | 37 | An internal error has occurred. |
WSRC_NO_SORT_FIELD_NAME | 38 | You specified the sort option in the command without specifying a sort criterion. |
WSRC_INVALID_SORT_FIELD_NAME | 39 | The sort criterion you specified is incorrect. |
WSRC_WARNING_FILE_ERROR | 40 | An error has occurred while attempting to create the warning file during a software scan. |
WSRC_UNABLE_TO_INITALIZE | 41 | The process initialization failed. |
WSRC_MISSING_XSS_SCHEMA_FILE | 42 | Cannot find the signature catalog schema. |
WSRC_UNABLE_INSTALL_DRIVER | 45 | Cannot install the CITMDRV_IA64.SYS, CITMDRV_AMD64.SYS, CITMDRV.SYS drivers. |
WSRC_UNABLE_LOAD_CITMEMDLL | 46 | Cannot load the CITMEM.DLL library. |
WSRC_UNABLE_LOAD_SYMBOL_
IN_CITMEM |
47 | Cannot load the symbols in the CITMEM.DLL library. |
WSRC_UNABLE_READ_CITMEMDLL | 48 | Cannot read the CITMEM.DLL library. |
WSRC_FILE_ACCESS_DENIED | 49 | The user does not have sufficient rights to access the file. |
WSRC_NOT_AUTHORIZED | 50 | The user does not have sufficient rights to perform the operation. |
WSRC_FILE_NOT_FOUND | 51 | The specified file or directory does not exist. |
The default installation of Common Inventory Technology is performed on the endpoints using the Tivoli Configuration Manager Software Distribution disconnected command line.
Use the following troubleshooting procedure when installing Common Inventory Technology on Tivoli Configuration Manager workstations:
[#MOBILE] product_dir=C:\swdis working_dir=C:\swdis\work backup_dir=C:\swdis\backup profile_dir=C:\swdis\work\profiles trace_level=0 trace_size=1000000 send_timeout=300 autopack_dir=C:\swdis\autopack staging_dir=swdis\service user_file_variables=C:\swdis\swdis.var import_libraries=spd,libecimp
The current path under "On Windows systems" should be replaced with:
C:/Program Files/ibm/tivoli/common/CIT/logs/traceCIT.log
The current path under "On UNIX systems" should be replaced with:
/usr/ibm/tivoli/common/CIT/logs/traceCIT.log
winvmigrate -c C:\temp\ITLM22ForIBM_SoftwareCatalog_2006-06-30.xmlwith:
winvmigrate -c C:\temp\IBM_SoftwareCatalog.xml
From the following FTP Web site
ftp://ftp.software.ibm.com/software/tivoli_support/misc/CandO/TivoliCatalog/
you can download the following catalog files:
Since June 2007 the new naming convention of these files is the following:
This section contains new and updated information for IBM Tivoli Configuration Manager Database Schema Reference:
The extended signatures are not displayed by the MATCH_SWARE_VIEW, while they are displayed by the INST_SWARE_VIEW.
The following columns:
FILE_COMMENTS FILE_INTERNAL_NAME FILE_PRODUCT_NAME FILE_COMPANY_NAME FILE_LEG_COPYRIGHT FILE_PROD_VERSION FILE_DESCRIPTION FILE_LEG_TRADEMARK FILE_PRIVATE_BUILD FILE_VERSION FILE_ORIG_FILENAME FILE_SPECIAL_BUILD
are populated only by data coming from scans run against pervasive devices.
ALL_NET_ADAPTER
Describes the physical and virtual network adapter installed on a system. One record exists for each network adapter for each system scanned.
Populated by an inventory hardware scan.
The columns in this table are as follows:
COMPUTER_SYS_ID (primary key)
ADAPTER_ID (primary key)
PERM_MAC_ADDR
CURRENT_ADDR
ADAPTER_TYPE
ADAPTER_MODEL
MANUFACTURER
INST_DATE
RECORD_TIME
ALL_NET_CARD_QUERY
Returns information about network cards on target systems.
Runs against the view ALL_NET_CARD_VIEW.
The columns in this query are as follows:
TME_OBJECT_LABEL
TME_OBJECT_ID
COMPUTER_SYS_ID
ADAPTER_ID
PERM_MAC_ADDR
CURRENT_ADDR
ADAPTER_TYPE
ADAPTER_MODEL
MANUFACTURER
INST_DATE
RECORD_TIME
ALL_NET_CARD_VIEW
Displays information about physical and virtual network cards on target systems.
Based on the COMPUTER and ALL_NET_ADAPTER tables.
The columns in this view are as follows:
This section contains new and updated information for IBM Tivoli Configuration Manager Patch Management Guide:
In Chapter 2 "Installing the automated patch management solution", in the "Upgrading the Patch Management Automation Server driver" section, replace step 6 with the following text:
ls -la "$TIO_HOME"/xml
In Chapter 7 "Troubleshooting", at the end of the "Other common problems" section, add the "Wrong code set" sub-section:
Cause: If you are defining a name for a group, a patch, or any other object, containing a character code set that is not defined in the Tivoli environment, the character is not displayed correctly in the name.
Solution: Set the TIS_CODESET variable to the appropriate code set as follows:
odadmin environ get >env.out
TIS_CODESET = TIS_CODESETwhere TIS_CODESET is the new value of the code set.
odadmin environ set < env.out
reexec oserv all
At the end of the wsusscn2.cab description add the following note:
At the end of the Add tioadmin login description add the following note:
Windows Update Agent (WUA) does not work properly
For the Microsoft Windows Update Agent (WUA) to work properly, ensure that the following Windows services are enabled and set to Automatic:
In addition, for the WUA to receive necessary updates from other Microsoft products, ensure that Windows Installer 3.1 is installed.
This section contains new and updated information for IBM Tivoli Configuration Manager User's Guide for Operating System Deployment Solution:
After you customized the rembo.ini file, you must stop and start the Activity Planner engine by running the following commands from the Tivoli server bash shell:
wstopapm wstartapm
Operating System Requirements:
The Tivoli Provisioning Manager for Operating System Deployment servers must be installed on Windows platforms only.
Configure the Rembo Server service to run logged on as a user that is a member of the Windows Administrators group, and that has one of the following Tivoli authorization roles:
Customize the config.csv file according to the guidelines described in:
and store a copy in the directory you created in the previous step for all the Tivoli Provisioning Manager for Operating System Deployment servers in your production environment.
Stop and start the Rembo Server service to load the customized config.csv file.
Enter a RAD file name that does not include special characters. This is because the Update Slaves activity passes the file name to a Tivoli bash script and the Tivoli bash does not support special characters.
This section contains new and updated information for IBM Tivoli Integration Pack for NetView User's Guide:
The NetView database and the Tivoli Report are updated only with those resources having the transport protocol set to AF_INET.
This section contains new and updated information for IBM Tivoli Configuration Manager Messages and Codes:
Defect 55666
The command you are using requires integration with Inventory.
The operation failed.
If inventory integration is required, use the wswdmgr software distribution command and the wsetinvswd Inventory command to enable integration. See: IBM Tivoli Configuration Manager: Reference Manual for Software Distribution, SC23-4712 and IBM Tivoli Configuration Manager: User's Guide for Inventory, SC23-4713 for more information.
Defect 55824
See message.
The install operation failed.
Ensure you defined the source host as a Tivoli gateway or a repeater. Check that the Tivoli gateway or the repeater is running. See the wrpt or wgateway commands in the Tivoli Management Framework: Reference Manual, GC32-0806.
This section contains new and updated information for IBM Tivoli Configuration Manager Release Notes:
The "temporary tables" feature does not apply to Sybase and Informix, because these two RDBMS databases do not clean up the contents of a temporary table after the commit operation, but only after releasing the session to the database. You can therefore receive the following error message, which might cause a performance decrease:
Sybase Server Error: Msgno 3621 Level 10 State 0 Command has been aborted.
The Windows Server Update Services (WSUS) server version 3.0 is not supported. Use the WSUS server version 2.1.
This section contains new information for the Software Package Editor online help:
Use this dialog box to specify whether you want a logoff operation to be performed on Windows endpoints and to define the settings for the logoff operation. You can select one or more of the following options:
For more information on defining conditions, see the Conditions help panel.
Select this check box to maintain the file or directory access attributes and the ownership if the file or directory already exists on the target. If the file or directory does not exist, the check box selection has no effect, and the default value (Use system value check box), or the ones that you selected, are assumed.
This section provides information about commands that have been added or changed but for which new man pages are not available.
The changes to these commands are documented in the IBM Tivoli Configuration Manager: Reference Manual for Software Distribution.
The changes to this command are documented in the IBM Tivoli Configuration Manager: User' Guide for Deployment Services.
The changes to these commands are documented in the IBM Tivoli Configuration Manager: User's Guide for Inventory.
The new and changed commands are documented in Configuration Manager: License Manager Extension
[ Top of Page | Previous Page | Next Page | Contents ]