![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains new and updated information for IBM Tivoli Configuration Manager User’s Guide for Inventory:
add the following information:
Symptom catalog and log files adapters
Starting from the Autonomic Computing AC Log and Trace 4.5.0.3 fix pack, adapters are supported for the mcollect.log file.
In this fix pack are available also the symptom catalogs for Tivoli Configuration Manager version 4.3.1.
add the following row to the "Versions of VMware tested on CIT" table:
ESX Server 3.5
Signature data includes the name, size, and usually the quick checksum value of the file used to identify the software product.
with the following text:
Signature data includes the name and the size of the file used to identify the software product.
Signature data includes the name, size, and usually the Quick checksum value of the file used to identify the software product.
with the following text:
Signature data includes the name and the size of the file used to identify the software product.
Adds one or more signatures to the configuration repository, and modifies existing signatures. Each signature must have a unique file name and size. If the specified signature already exists, the information for the existing signature (for example, the description or version) is modified.
Specifies the name of a file that contains the data for one or more signatures. The signature data in the file must be in the following format:
<I>,name,size,description,version
The signature file supports also the XML file format.
Setting the CIT processes priority on Windows
On Windows platforms, you can specify locally on each endpoint the priority for the different CIT processes by editing the cit.properties file and adding, for example, the following priorities:
fscanner.changepriority=low swscanner.changepriority=low hwscanner.changepriority=low vpdscanner.changepriority=lowIf you want to add the priority settings directly to the CIT_win.spb package used to install CIT, perform the following steps:
wdubldsp.exeThe command extracts a software package (.sp file) and the CIT files.
fscanner.changepriority=low swscanner.changepriority=low hwscanner.changepriority=low vpdscanner.changepriority=lowSave the file.
wdbldspb.exeThe new CIT_win.spb now includes the new cit.properties file with the priority settings that you set.
ORA-00918: column ambiguously definedYou can run the command only with Tivoli queries where only one table and view have the TME_OBJECT_ID field.
This section contains new and updated information for IBM Tivoli Configuration Manager Database Schema Reference:
Configuration repository view | Columns added to the view |
---|---|
V_ACT_ST |
COUNTER |
V_ACT_STATUS_EX |
TARGETS GATEWAYS DEPOTS |
V_PLAN_STATUS |
TGT_RESOURCE_TYPE |
V_PLAN_STATUS_EX |
ACTIVITIES REC_NUM |
V_TGT_ACT_DEP_ST |
DEPOT_LABEL COUNTER START_TIME COMPLETION_TIME |
V_TGT_ACT_GW_ST |
COUNTER START_TIME COMPLETION_TIME |
V_TGT_ACT_ST |
COUNTER |
V_TGT_GW_FLTR |
COUNTER START_TIME COMPLETION_TIME |
ASP_VIEW |
COMPUTER_SYS_ID TME_OBJECT_ID |
CHECK_PACKAGES |
PLATFORM |
COMPUTER_VIEW |
OS_ARCH |
IP_ADDR_VIEW |
PERM_MAC_ADDRESS |
LPAR_VIEW |
NODECAP_IN_CORES LPARCAP_IN_CORES SHAREDPC_IN_CORES PHYS_SHAREDPC PHYS_SHAREDPC_CORES LPAR_ONLINE_VP_COUNT LPAR_IS_SHARED_TYPE LPAR_IS_CAPPED LPAR_ENTITLEMENT LPAR_MIN_VP_COUNT LPAR_MAX_VP_COUNT LPAR_MIN_CAPACITY LPAR_MAX_CAPACITY LPAR_IDLE_CP_WEIGHT SMT_IS_ENABLED NODE_ACT_PROC_COUNT |
LOGICAL_PARTITIONS_VIEW |
PHYS_SHAREDPC PHYS_SHAREDPC_CORES LPAR_ONLINE_VP_COUNT LPAR_IS_SHARED_TYPE LPAR_IS_CAPPED LPAR_ENTITLEMENT LPAR_MIN_VP_COUNT LPAR_MAX_VP_COUNT LPAR_MIN_CAPACITY LPAR_MAX_CAPACITY LPAR_IDLE_CP_WEIGHT SMT_IS_ENABLED NODE_ACT_PROC_COUNT |
MEM_MODULES_TOTAL |
TME_OBJECT_ID |
OS_VIEW |
OS_ARCH |
PACKAGE_FILE_VIEW |
PLATFORM |
PC_BIOS_VIEW |
UPTIME |
SERVICE_INFO_VIEW |
TME_OBJECT_LABEL TME_OBJECT_ID |
SMBIOS_DATA_VIEW |
SYS_PRODUCT_NAME POWERON_PASSWORD |
SWARE_MATCH_CRC32 |
CHECKSUM_CRC32 |
SWARE_MATCH_MD5 |
CHECKSUM_MD5 |
SWARE_MATCH_QUICK |
CHECKSUM_QUICK |
EP_PATCHES_VIEW |
GUID UPDATEID REBOOTBEHAVIOR |
PM_PATCHES_VIEW |
GUID UPDATEID REBOOTBEHAVIOR |
SP_PATCHES_VIEW |
GUID UPDATEID REBOOTBEHAVIOR |
DEV_DET_BEA_VIEW |
DEVICE_ID |
DEV_DET_EXT_VIEW |
DEVICE_ID |
DEV_INFO_BEA_VIEW |
DEVICE_ID |
DEV_INFO_EXT_VIEW |
DEVICE_ID |
DMACC_CON_EXT_VIEW |
DEVICE_ID |
MO_LOGIN_VIEW |
NAME TW LOGINTY DATA RECORD_TIME |
Configuration repository view | Columns removed from the view |
---|---|
V_PLAN_STATUS_EX |
REC_NUMBER |
SMBIOS_DATA_VIEW |
PRODUCT_NAME |
NOSIG_FILES_VIEW |
PATH |
DEV_DET_BEA_VIEW |
LABEL |
DEV_DET_EXT_VIEW |
LABEL |
DEV_INFO_BEA_VIEW |
LABEL |
DEV_INFO_EXT_VIEW |
LABEL |
DMACC_CON_EXT_VIEW |
LABEL |
Query | Columns added to the query |
---|---|
ASP_QUERY |
TME_OBJECT_ID COMPUTER_SYS_ID |
COMPUTER_QUERY |
OS_ARCH |
INST_FILE_QUERY |
FILE_SIZE_KB |
INVENTORY_SWARE |
ACCESSED_TIME |
IP_ADDR_QUERY |
PERM_MAC_ADDRESS |
LOGICAL_PARTITIONED_SYSTEMS_QUERY |
NODECAP_IN_CORES |
LOGICAL_PARTITIONS_QUERY |
LPARCAP_IN_CORES NODECAP_IN_CORES SHAREDPC_IN_CORES PHYS_SHAREDPC PHYS_SHAREDPC_CORES LPAR_ONLINE_VP_COUNT LPAR_IS_SHARED_TYPE LPAR_IS_CAPPED LPAR_ENTITLEMENT LPAR_MIN_VP_COUNT LPAR_MAX_VP_COUNT LPAR_MIN_CAPACITY LPAR_MAX_CAPACITY LPAR_IDLE_CP_WEIGHT SMT_IS_ENABLED NODE_ACT_PROC_COUNT |
MEM_MODULES_TOTAL |
TME_OBJECT_ID |
OS_QUERY |
OS_ARCH |
SERVICE_INFO_QUERY |
TME_OBJECT_LABEL TME_OBJECT_ID COMPUTER_SYS_ID RECORD_TIME |
SOLARIS_CPU_QUERY |
PROCESSOR_NUM |
MO_AP_NAP_QUERY |
RECORD_TIME |
MO_AP_NAPB_QUERY |
RECORD_TIME |
MO_AP_NAPD_QUERY |
RECORD_TIME |
MO_AP_NAPN_QUERY |
RECORD_TIME |
MO_AP_PX_QUERY |
RECORD_TIME |
MO_AP_PXA_QUERY |
RECORD_TIME |
MO_AP_PXD_QUERY |
RECORD_TIME |
MO_AP_PXN_QUERY |
RECORD_TIME |
MO_AP_PXNO_QUERY |
RECORD_TIME |
MO_AP_PXP_QUERY |
RECORD_TIME |
MO_DS_DB_QUERY |
RECORD_TIME |
CM_STATUS_QUERY |
TME_OBJECT_ID |
Query | Columns removed from the query |
---|---|
ALL_NET_CARD_QUERY |
ADAPTER_ID |
SERVICE_INFO_QUERY |
SPATH_NAME SSTARTED |
MO_AP_NAP_QUERY |
DEVICE_ID |
MO_AP_NAPB_QUERY |
DEVICE_ID |
MO_AP_NAPD_QUERY |
DEVICE_ID |
MO_AP_NAPN_QUERY |
DEVICE_ID |
MO_AP_PX_QUERY |
DEVICE_ID |
MO_AP_PXA_QUERY |
DEVICE_ID |
MO_AP_PXD_QUERY |
DEVICE_ID |
MO_AP_PXN_QUERY |
DEVICE_ID |
MO_AP_PXNO_QUERY |
DEVICE_ID |
MO_AP_PXP_QUERY |
DEVICE_ID |
MO_DS_DB_QUERY |
DEVICE_ID |
Configuration repository table | Columns added to the table |
---|---|
COMPUTER |
OS_ARCH |
FILE_DESC |
FILE_SIZE_KB |
INST_SERVICE_INFO |
DNAME SDESC SPATH_NAME STYPE SSTARTED SSTART_MODE SDISPLAY_NAME SSTATE SSTATUS |
INST_SMBIOS_DATA |
POWERON_PASSWORD |
IP_ADDR |
PERM_MAC_ADDRESS |
LPAR |
PHYS_SHAREDPC PHYS_SHAREDPC_CORES LPAR_ONLINE_VP_COUNT LPAR_IS_SHARED_TYPE LPAR_IS_CAPPED LPAR_ENTITLEMENT LPAR_MIN_VP_COUNT LPAR_MAX_VP_COUNT LPAR_MIN_CAPACITY LPAR_MAX_CAPACITY LPAR_IDLE_CP_WEIGHT SMT_IS_ENABLED NODE_ACT_PROC_COUNT |
MATCHED_SWARE |
MD5_ID |
PM_PATCH_INFO |
GUID UPDATEID REBOOTBEHAVIOR |
PM_PATCH_PKG |
GUID |
SYNCDM_DMACC |
ADDR |
Configuration repository table | Columns removed from the table |
---|---|
PM_PATCH_PKG |
PROD_MAJOR_VER PROD_MINOR_VER PROD_LANG OS_BASE_NAME OS_ARCHITECTURE OS_TYPE OS_SUBTYPE OS_SP_MAJOR_VER OS_SP_MINOR_VER |
SYNCDM_DMACC |
ADDRESS NAME |
By default, the h_database_schema.sql scripts create a table to correspond to every inventory table in the inv_database_schema.sql script that contains the attribute COMPUTER_SYS_ID. If there are tables for which you do not want to keep history tables, perform the following steps:
You can find the SQL statements for performing these operations in the h_inv_*_schema_431_FP01.sql script file.
Column Name | Description |
---|---|
MANUFACTURER | Processor manufacturer. Examples: Intel, AMD, IBM, SUN, HP. If the manufacturer is not recognized (is not in the list of families supported by Common Inventory Technology) then this field has value of "Unknown". |
FAMILY | Processor family. Examples: Pentium 4, Xeon, Athlon 64, POWER5, UltraSparc-T1, PA-RISC. If the family is not recognized (not in the list of families supported by Common Inventory Technology) then this field has value of "Unknown". |
TYPE | Processor type. Examples: 170 for AMD Opteron 150, 670 for Intel Pentium 4 670. If Common Inventory Technology does not support type identification for the family of processors then this field has value of an empty string. If Common Inventory Technology supports type identification for the family of processors but the type of processor is not recognized then this field has value of "Unknown". |
CPU_FREQ | Processor frequency in MHz. This field is optional and vendor specific. Depending on the processor family it might be nominal or current CPU frequency. CPU frequency might be interpreted differently across processor architectures and families. If not valid this field is 0. |
L2_CACHE_SIZE | Size of L2 cache in Kilobytes. This field is optional, 0 if not valid. |
L3_CACHE_SIZE | Size of L3 cache in Kilobytes. This field is optional, 0 if not valid or there is no L3 cache. |
SIGNATURE | Processor signature. This field is optional and platform- and vendor-specific. The value of this field might be taken from different sources on each platform and even for different processor families. If available this is the processor model identifier reported by CPUID instruction, BIOS or OS. This field is for internal Common Inventory Technology purposes only; the exploiter should make no assumption on contents or format of this field. |
Whether the printer is a local printer or a network printer, and is the default printer or not. This column can assume one of the following values:
This section contains new and updated information for IBM Tivoli Configuration Manager Patch Management Guide:
Before starting the Tivoli Configuration Manager Automation Server installation, checks the correctness of the directories for the configuration files and that Windows Instrumentation Service is not running to prevent the failure of the MQ Series component.
with the following text:
Before starting the Tivoli Configuration Manager Automation Server installation, checks the correctness of the directories for the configuration files.
The new output of the mount -m command will be:
mount -f -s -b "C:/cygwin/bin" "/usr/bin" mount -f -s -b "C:/cygwin/lib" "/usr/lib" mount -f -s -b "C:/cygwin" "/"
This section contains new and updated information for IBM Tivoli Configuration Manager Planning and Installation Guide:
If you are using a Windows workstation and the password policy rules are enabled, the password that you specify for the new tivapm user must meet the operating system password requirements. Otherwise the Activity Planner installation completes successfully, but the user is not created.
Tivoli_MD2GUI_L10N | The language support packages for the Distribution Status console, version 4.3.1. The prerequisite for this package is Tivoli_MD2GUI. |
Troubleshooting a Tivoli Management Framework silent installation
When you install IBM Tivoli Configuration Manager on Windows 2008 platforms in Japanese language using a silent installation, the Tivoli Management Framework installation might hang. As a workaround, proceed first with the Tivoli Management Framework installation using Tivoli Management Framework CD 1. When this installation is complete, launch the usual IBM Tivoli Configuration Manager installation using the product CD 5.
This chapter describes how to upgrade Tivoli Management Framework and the IBM Tivoli Configuration Manager components.
Tivoli Management Framework backward compatibility rules
The upgrade is based on the following Tivoli Management Framework version 4.3.1 backward compatibility rules:
Tivoli Configuration Manager backward compatibility rules
The upgrade is also based on the following IBM Tivoli Configuration Manager 4.3.1 backward compatibility rules:
The upgrade can be performed using the classical procedure based on Tivoli Management Framework, the InstallShield MultiPlatform (ISMP) installation on the supported platforms, or the Tivoli Software Installation Service (SIS) on the supported platforms.
The IBM Tivoli Configuration Manager version 4.3.1 release does not contain enhancements that require changes in the Inventory schema. The Inventory schema upgrade modifies only the schema from the starting IBM Tivoli Configuration Manager release to the latest 4.2.3 maintenance level.
To upgrade the Inventory schema, apply the same procedure used when installing a IBM Tivoli Configuration Manager fix pack.
The images of IBM Tivoli Configuration Manager version 4.3.1 contain all the SQL scripts released with any 4.2.2 and 4.2.3 fix pack, up to 4.2.2-TIV-TCM-FP0006. You must run a subset of these scripts depending on the database vendor and the starting IBM Tivoli Configuration Manager release or fix pack.
To migrate large environments, it is recommended that you first upgrade to Tivoli Management Framework 4.3.1, and then start upgrading to IBM Tivoli Configuration Manager 4.3.1.
To upgrade Tivoli Management Framework, it is recommended that you use the following order (top-down approach):
At the end of this phase you will have the Tivoli Management Framework infrastructure upgraded to 4.3.1 and IBM Tivoli Configuration Manager still working at 4.2.x level.
To upgrade IBM Tivoli Configuration Manager, it is recommended that you use the following order (bottom-up approach):
If during the upgrade phase you want to run an Inventory scan from a back level Configuration Manager server to 4.3.1 endpoints attached to gateways on which IBM Tivoli Configuration Manager has already been upgraded to 4.3.1, run the following command against each gateway that has already been upgraded to Tivoli Management Framework 4.3.1:
wlevlmeth -a gateway_name (| all)
The wlevlmeth utility is located under the /utils folder of the IBM Tivoli Configuration Manager version 4.3.1 CD. Use the wlevlmeth command to force the endpoints already upgraded to Tivoli Management Framework 4.3.1 to download binaries starting from the gateway bundles older than the 4.3.1 ones.
To upgrade IBM Tivoli Configuration Manager, perform these steps:
backlevel_methods: NULL
You cannot perform a Fresh Install of 4.2.3 Configuration Manager gateway components, after upgrading to 4.3.1 Tivoli Management Framework on the managed nodes of your environment.
If you cannot exclude the possibility that an old 3.7.x or 4.1.x endpoint connects to a Configuration Manager environment already migrated to 4.3.1, to minimize the impact caused by a mismatch between the Configuration Manager 4.3.1 schema and the 4.3.1 scanners we suggest that you:
For more details about disk space requirements, refer to IBM Tivoli Configuration Manager: Release Notes version 4.3.1.
Common Inventory Technology is installed using the following default paths:For more details about how to install Common Inventory Technology, refer to IBM Tivoli Configuration Manager: User's Guide for Inventory version 4.3.1
Common Inventory Technology does not interact with a Tivoli Configuration Manager Inventory component installed before 4.2.3 Fix Pack 2, until it is upgraded to 4.3.1. Ensure that you plan to install Common Inventory Technology in a controlled way before upgrading to 4.3.1.This section contains new and updated information for IBM Tivoli Configuration Manager Reference Manual for Software Distribution:
The sections where these stanzas are described show the structure in which you should define each stanza and provide examples.
add the following paragraph:
At installation time, the installation of a software package starts only if, during the check of the conditions specified in all software package stanzas, all these conditions are verified.
add the following note:
On UNIX platforms if you set this attribute to y when creating software packages, to which a directory is added containing backward slashes, performing the winstsp command on the software package fails. To successfully install the software package on UNIX platforms, do not add to the package a directory containing backward slashes.
This section contains new and updated information for IBM Tivoli Configuration Manager User's Guide for Deployment Services:
add the following information:
Symptom catalog and log files adapters
Starting from the Autonomic Computing AC Log and Trace 4.5.0.3 fix pack, adapters are supported for the apmlog0 log file.
From this fix pack also the symptom catalogs for Tivoli Configuration Manager 4.3.1. are available.
This section contains new and updated information for IBM Tivoli Configuration Manager Release Notes:
On Red Hat Linux® Enterprise Server, version 5 32-bit operating systems, the following packages are required:
On Red Hat Linux Enterprise Server, version 5 64-bit operating systems, the following packages are required:
APAR IZ44669
Problem: When installing Tivoli Configuration Manager version 431 on Red Hat Linux Enterprise Server version 5 in Japanese language, the installation wizard panels display garbled characters because some language font files are missing.
Workaround: Before installing Tivoli Configuration Manager version 431, perform the following steps:
ftp://submit.boulder.ibm.com/download/typography/fonts/worldtype/ archive/wt__/2002-02-13/
ttmkfdir > fonts.dir
chkfontpath --add JRE_HOME/lib/fonts
/opt/IBMJava2-131/jre/lib/fonts
When you install IBM Tivoli Configuration Manager on Windows 2008 platforms in Japanese language using a silent installation, the Tivoli Management Framework installation might hang.
Workaround: Proceed first with the Tivoli Management Framework installation using Tivoli Management Framework CD 1. When this installation is complete, launch the usual IBM Tivoli Configuration Manager installation using the product CD 5.
This section contains new and updated information for IBM Tivoli Configuration Manager License Management with License Compliance Manager Version 2.3 Fix Pack 4:
<!DOCTYPE agentRemappings SYSTEM "agtRemappings.dtd">with the following line:
<!DOCTYPE agentRemappings SYSTEM "AgentRemappings.dtd">
The absolute path to the XML file containing the list of agent IDs and Tivoli® OIDs to be remapped to different divisions. This file must be located in the same folder as the document type definition (DTD) file. The DTD file is copied to the path
$INSTALL_DIR/admin/SLM_Admin_Application.ear\slm_admin.war\webdoc\xml\ import\agentRemappings.dtd
with the installation of the License Compliance Manager administration server infrastructure element.
with the following text:
The absolute path to the XML file containing the list of agent IDs and Tivoli OIDs to be remapped to different divisions. Add to the XML file a DOCTYPE line containing the full path to the document type definition (DTD) file as shown in the following example:
<!DOCTYPE agentRemappings SYSTEM "C:\Program Files\IBM\TLM\admin\ SLM_Admin_Application.ear\slm_admin.war\ webdoc\xml\import\AgentRemappings.dtd">
[ Top of Page | Previous Page | Next Page | Contents ]