tivoli inventory release notes version 4 -...

Tivoli InventoryRelease NotesVersion 4.0April 2001

Tivoli Inventory Release Notes

Copyright Notice© Copyright IBM Corporation 2001. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is not intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose.U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.

TrademarksIBM, the IBM logo, Tivoli, the Tivoli logo, AIX, OS/2, Tivoli Enterprise, Tivoli Enterprise Console, and TME are trademarks or registered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Intel and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others.

NoticesReferences in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

Tivoli Inventory Release Notes i

Chapter 1—Release NotesAccessing Publications Online ........................................................................... 1-1

Ordering Publications ......................................................................................... 1-2

Providing Feedback about Publications.............................................................. 1-2

Contacting Customer Support............................................................................. 1-3

New Features ...................................................................................................... 1-3

New Graphical User Interface.................................................................... 1-3

Scanning Improvements ............................................................................. 1-4

Improved Hardware Scanning ........................................................... 1-4

Improved Software Scanning ............................................................ 1-4

Desktop Management Interface Capabilities on OS/2 ............................... 1-5

Redesigned Schema.................................................................................... 1-5

History Tracking ........................................................................................ 1-6

Wake-on-LAN Technology........................................................................ 1-6

Mobile Endpoint Support ........................................................................... 1-6

Endpoint-Initiated Scans ............................................................................ 1-6

System Requirements.......................................................................................... 1-6

Software Requirements .............................................................................. 1-7

Operating Systems ............................................................................. 1-7

RDBMS and RIM Hosts.................................................................... 1-9

Web Browsers.................................................................................... 1-9

Hardware Requirements ............................................................................. 1-9

TMR Server and Managed Nodes ................................................... 1-10

Gateways ......................................................................................... 1-11

Endpoint Files.................................................................................. 1-11

Installation Notes .............................................................................................. 1-12

Coexistence with Previous Product Versions........................................... 1-12

Installation Directories ............................................................................. 1-14

Patches Included in This Release...................................................................... 1-15

Defects Fixed in This Release........................................................................... 1-15

Known Product Defects, Limitations, and Workarounds ................................. 1-17

ii Version 4.0

Known Documentation Defects........................................................................ 1-24

Internationalization ........................................................................................... 1-25

Enabling Language Support .................................................................... 1-25

International Defects Fixed ...................................................................... 1-26

International Defects, Limitations, and Workarounds ............................. 1-26

Product Notes.................................................................................................... 1-28

Tivoli Inventory Release Notes 1–1

1Release Notes

This Release Notes document provides important information about Tivoli Inventory, Version 4.0. These notes are the most current information for the product and take precedence over all other documentation.

Please review these notes thoroughly before installing or using this product.

Both Tivoli and TME 10 are used in our sales, marketing, and product information materials. These terms are interchangeable. References to TME 10 will be removed in future product releases.

These release notes include the following topics:

■ New Features

■ System Requirements

■ Installation Notes

■ Patches Included in This Release

■ Defects Fixed in This Release

■ Known Product Defects, Limitations, and Workarounds

■ Known Documentation Defects

■ Internationalization

■ Product Notes

Accessing Publications OnlineThe Tivoli Customer Support Web site (http://www.tivoli.com/support/) offers a guide to support services (the Customer Support Handbook); frequently asked questions (FAQs); and technical information, including release notes, user’s guides, message documentation, redbooks, and white papers. You can access Tivoli publications online

1–2 Version 4.0

at http://www.tivoli.com/support/documents/. The documentation for some products is available in PDF and HTML formats. Translated documents are also available for some products.

To access most of the documentation, you need an ID and a password. To obtain an ID for use on the support Web site, go to http://www.tivoli.com/support/getting/.

Resellers should refer to http://www.tivoli.com/support/smb/index.html for more information about obtaining Tivoli technical documentation and support.

Business Partners should refer to “Ordering Publications” for more information about obtaining Tivoli technical documentation.

Ordering PublicationsOrder Tivoli publications online at http://www.tivoli.com/support/Prodman/html/pub_order.html or by calling one of the following telephone numbers:

■ U.S. customers: (800) 879-2755

■ Canadian customers: (800) 426-4968

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoli products and documentation, and we welcome your suggestions for improvements. If you have comments or suggestions about our products and documentation, contact us in one of the following ways:

■ Send e-mail to [email protected].

■ Fill out our customer feedback survey at http://www.tivoli.com/support/survey/.


Contacting Customer SupportThe Tivoli Customer Support Handbook at http://www.tivoli.com/support/handbook/ provides information about all aspects of Tivoli Customer Support, including the following:

■ Registration and eligibility.

■ How to contact support, depending on the severity of your problem.

■ Telephone numbers and e-mail addresses, depending on the country you are in.

■ What information you should gather before contacting support.

New FeaturesThe following sections describe the new features for Tivoli Inventory, Version 4.0.

New Graphical User InterfaceThe new Tivoli Inventory graphical user interface (GUI) provides the following features:

■ A DMI scan configuration dialog box that enables you to configure DMI scans for each type of DMI layer in your enterprise. Tivoli Inventory also automatically generates an SQL script that you can use to create the appropriate tables in the configuration repository for DMI scan data.

■ A window that enables you to add, edit, or delete software signatures.

■ A window that enables you to create a custom filter for software scans.

■ Dialog boxes that enable you to select which hardware components to scan for. Separate controls are provided for Windows and UNIX scans.

■ Context-sensitive online help.

1–4 Version 4.0

Scanning ImprovementsThe following sections describe the improvements to hardware and software scanning for Tivoli Inventory, Version 4.0.

Note: In Tivoli Inventory, Version 4.0, you can scan only endpoints. If you want to scan a system currently configured only as a managed node, you must install a Tivoli Management Framework endpoint on that system.

Improved Hardware Scanning

The following improvements have been made to hardware scanning for Tivoli Inventory, Version 4.0:

■ A new UNIX hardware-scanning engine enables you to collect the following information from a UNIX scan: processor, operating system, IP address, partition, keyboard, memory, storage, network adapter, pointing device, and UNIX system parameters.

■ For both PC and UNIX hardware scans, you can select the type of information to be returned from a hardware scan and reduce the amount of data generated by the scan. This can improve the speed with which the scan runs, reduce the network bandwidth required to transport the scan data, and reduce the amount of time to write the data into the Tivoli Inventory database.

■ Tivoli Inventory can now collect data from endpoints using Windows Management Instrumentation (WMI). This feature is used automatically when it is available.

Improved Software Scanning

The following improvements have been made to software scans in Tivoli Inventory, Version 4.0:

■ You can now perform software signature matching at the endpoint rather than in the configuration repository. Using this method, software signature scans return data only for files that match a software signature. Because only data for matching files is sent to the configuration repository, software signature scans now return less data through the collector hierarchy. Also, because each endpoint performs the processing necessary to compare the


software signatures to the scanned files, this scan is more efficient than performing signature matching at the configuration repository.

■ You can now scan the headers of files on supported Windows systems for header information. This information usually includes the company name, product name, and product version.

■ On Windows systems, you can scan the Windows registry for information about installed products. On UNIX systems, you can scan the operating system for information about installed products and patches.

■ The number of UNIX software signatures is increased significantly in Tivoli Inventory, Version 4.0.

■ You can now generate checksum values for scanned files. The following checksum options are provided:

• The Quick CRC option uses the CRC-32 algorithm to produce a 32-bit value based on the first 1 KB of each file.

• The Full CRC option uses the CRC-32 algorithm to produce a 32-bit value based on the full contents of each file.

• The MD5 option produces a 128-bit value based on the full contents of each file.

Desktop Management Interface Capabilities on OS/2The same capabilities that previous versions of Tivoli Inventory had for retrieval of Desktop Management Interface (DMI) data on Windows platforms is extended to supported OS/2 platforms.

Redesigned SchemaThe schema has been simplifed and designed to more closely resemble the CIM standard for inventory data. The DATE data type is now supported.

1–6 Version 4.0

History TrackingHistory tracking is an optional feature of Tivoli Inventory that enables you to track changes made to configuration repository tables. When enabled, this feature records every change or addition to inventory scan data. Previous versions of Tivoli Inventory stored only the last change.

Wake-on-LAN TechnologyTivoli Inventory can use MDist 2 functionality to automatically power up, or “wake up,” machines that have a wake-on-LAN-enabled network card that uses the Intel Wired for Management specification.

Mobile Endpoint SupportYou can create a profile for a customized inventory scan that can be pushed to a mobile or remote endpoint and scheduled to run when the endpoint is disconnected; the data is sent the next time the endpoint is reconnected to the network.

Endpoint-Initiated ScansTivoli Inventory enables you to initiate a scan from an endpoint instead of distributing the scan from an inventory profile. This feature has many uses. For example, you can use endpoint-initiated scans to perform the following actions:

■ Scan a machine each time it is rebooted

■ Scan a laptop system each time a mobile user logs in to the network

■ Scan a machine that is disconnected from the network

System RequirementsThis section describes the software and hardware requirements for Tivoli Inventory, Version 4.0.


Software RequirementsThe following subsections contain information about Tivoli Inventory, Version 4.0, requirements for applications and platforms.

Operating Systems

This subsection contains information about the supported operating system versions and required patches (if any) for each supported hardware architecture. Tivoli does not distribute or maintain operating system patches from hardware vendors. Contact your hardware vendor for information on obtaining and installing operating system patches. If you are not sure how to contact your hardware vendor, contact your Tivoli support provider for the recommended procedure. For more information about supported platforms and patch levels, see the Tivoli Management Framework Release Notes.

Platform Supported Version

AIX Gateway, Managed Node, Endpoint:

IBM RS/6000 series running AIX, Versions 4.3.0, 4.3.1, 4.3.2, and 4.3.3. Only 32-bit versions are supported.

HP-UX Gateway, Managed Node, Endpoint:

HP9000 series running HP-UX, Versions 10.20, 11.00, and 11 SP1. Only 32-bit versions are supported.

NetWare Gateway or Endpoint:

IBM-compatible PCs Pentium or higher running Novell NetWare, Versions 4.11, 4.2, and 5.

OS/2 Gateway or Endpoint:

IBM-compatible PCs Pentium or higher running IBM OS/2 Warp 4.0 and OS/2 Warp Server for e-business.

1–8 Version 4.0

Notes

• Tivoli products are not supported on NetWare systems running the SFT III high-availability configuration or the SMP (Symmetric Multi Processor) add-on package.

• The GUI for Tivoli Inventory, Version 4.0, requires Java Runtime Environment (JRE) 1.2.2, which can be installed as a product from the Tivoli Management Framework CD. Not all operating systems that are supported by Tivoli Inventory are

Solaris Gateway, Managed Node, Endpoint:

Sun SPARC series running Solaris, Versions 2.6 and 7. Only 32-bit versions are supported.

Windows Endpoint:

IBM-compatible PCs Pentium or higher running Microsoft Windows 98 and Windows Me

Windows NT Gateway, Managed Node, or Endpoint:

IBM-compatible PCs Pentium or higher running Microsoft Windows NT 4.0 SP 4 (requires Y2K patch), 4.0 SP 5, and 4.0 SP 6a. This includes Windows NT Server (including 32-bit), Workstation, and Enterprise Edition.

Windows 2000 Gateway, Managed Node, or Endpoint:

IBM-compatible PCs Pentium or higher running Microsoft Windows 2000 Server and Advanced Server.

Endpoint only:

IBM-compatible PCs Pentium or higher running Microsoft Windows 2000 Professional.

Platform Supported Version


compatible with JRE 1.2.2. Currently, the minimum required operating system version for JRE 1.2.2 is as follows:

■ AIX 4.3.3

■ HP-UX 11

■ Solaris 2.6

■ Windows NT 4.0 and Windows 2000

This information is subject to change. Check the documentation for your operating system to determine the minimum operating system version and patch level that JRE 1.2.2 requires.

RDBMS and RIM Hosts

An RDBMS must be installed and configured. Refer to your RDBMS documentation for database installation instructions and requirements. Also, see “Using RIM and the RDBMS” in Chapter 2 of the Tivoli Inventory User’s Guide, Version 4.0, for more information about configuring the RDBMS and the RIM host. In addition to installing the RDBMS, you must designate a managed node as the RIM host in the TMR.

See the Tivoli Management Framework Release Notes, Version 3.7.1, for information about supported RDBMS versions, RIM requirements and considerations.

Web Browsers

To access the Tivoli Inventory Web pages, you must have a Web browser that supports HTML 1.0. You can access the Tivoli Inventory Web pages with Netscape 4.x or later and Microsoft Internet Explorer (MSIE) 4.x or later.

Hardware RequirementsThis section provides the estimated disk space needed to perform a full installation of Tivoli Inventory, Version 4.0.

1–10 Version 4.0

The following sections provide space requirements for the items listed:

■ TMR Server and Managed Nodes

■ Gateways

■ Endpoint Files

Note: Use the space requirements that follow as general guidelines. The actual space required for each item depends on the size and configuration of your TMRs.

TMR Server and Managed Nodes

The tables in this section list the estimated disk space needed to install Tivoli Inventory, Version 4.0, and Scalable Collection Service (SCS) on the TMR server and managed nodes. The disk space includes space for the binaries (Bins, Generic Bins), temporary installation configuration files (Cfg Files), manual pages (Man Pages), and message catalogs (Msg Cats).

Tivoli Inventory Server, Version 4.0

The following table lists the disk space required to install Tivoli Inventory Server, Version 4.0, on the TMR server and managed nodes.

Platform Bins Generic Bins Cfg Files Man

Pages Msg Cats

AIX 5.57 MB 9.52 MB 265 KB 131 KB 69.8 KB

HP-UX 6.19 MB 9.52 MB 265 KB 131 KB 69.8 KB

Windows NT and 2000

4.38 MB 9.52 MB 267 KB N/A 69.8 KB

Solaris 6.83 MB 9.52 MB 265 KB 131 KB 69.8 KB


Scalable Collection Service

The following table lists the disk space required to install SCS on the TMR server and managed nodes.

Gateways

To install Tivoli Inventory Gateway, Version 4.0, on managed nodes, regardless of the platform, you need at least 9.18 MB of disk space.

Endpoint Files

The Tivoli Inventory software that is necessary to scan endpoints is installed on the gateway. When you distribute a Tivoli Inventory profile to an endpoint, the Tivoli Inventory files that are required for that type of endpoint are sent from the gateway to the endpoint. The following table provides the disk space requirements for files that are downloaded to the endpoints during an inventory scan.

Platform Bins Generic Bins Cfg Files Man

Pages Msg Cats

AIX 1117 KB 1.71MB 62.5 KB 13.7 KB 9.59 KB

HP-UX 989 KB 1.71 MB 62.5 KB 13.7 KB 9.59 KB

Windows NT and 2000

260 KB 1.71 MB 63.5 KB 70.5 KB 9.59 KB

Solaris 1055 KB 1.71 MB 62.5 KB 13.7 KB 9.59 KB

Platform Endpoint Files

AIX 799 KB

HP-UX 660 KB

NetWare 1714 KB

OS/2 844 KB

1–12 Version 4.0

In addition to the requirements mentioned in the preceding table, you must consider the following factors to determine disk space requirements for endpoints:

■ The endpoint must have adequate space for the MIF files created by the scan. Depending on the type of scan and the size of the system being scanned, the MIF files can vary from a few KB to several MB.

■ Software signature scans send the software signature file to the endpoint. The file that contains the default software signatures is approximately 800 KB. If you add custom software signatures, the file will be larger.

■ If you filter scans for basic information, the filter file is sent to the endpoint. The size of the filter file varies according to the number of filter entries that you create.

Installation NotesThis section provides information about installing Tivoli Inventory, Version 4.0. This information supplements the Tivoli Inventory User’s Guide, Version 4.0, which contains detailed procedures for installing Tivoli Inventory.

Coexistence with Previous Product VersionsTivoli Inventory, Version 4.0, is a new product and not an upgrade of Tivoli Inventory, Version 3.6.2. While this new product does not require the installation of previous versions of Tivoli Inventory, it can coexist within a TMR with Tivoli Inventory, Version 3.6.2.

Solaris 576 KB

Windows 98 3032 KB

Windows NT and 2000 1845 KB

Platform Endpoint Files


See defect CMVC-118631 in “Known Product Defects, Limitations, and Workarounds” on page 1-17 for coexistence issues related to Tivoli Inventory, Version 4.0.

You might choose to install both the new version and a previous version of Tivoli Inventory to do the following:

■ Ease the migration from a previous version to the new version.

■ Keep your current, customized environment operational while beginning to exploit the new features offered by Tivoli Inventory, Version 4.0.

The following changes were made in Tivoli Inventory, Version 4.0, to enable coexistence:

■ Command line interface (CLI) commands that were changed between Version 3.6.2 and Version 4.0 have been renamed.

■ The InventoryProfile resource type has been renamed InventoryConfig.

■ The BasicInventoryProfile policy object has been renamed BasicInventoryConfig.

■ The $LCF_BASE_DIR/inv/SCANNER directory is created to provide coexistence with previous versions. Tivoli Inventory, Version 4.0, uses the $LCF_BASE_DIR/inv/SCAN directory.

■ The default user name for the Tivoli Inventory, Version 4.0, RIM objects has been changed from tivoli to invtiv.

■ The inventory receiver has been renamed the inventory data handler. The name of the inventory data handler object is InvDataHandler.

■ Unique RIM objects are created for use by Tivoli Inventory, Version 4.0.

■ Tivoli Inventory, Version 4.0, has a new schema. This schema should not exist in the same tablespace as the Tivoli Inventory, Version 3.6.2 schema.

■ The query library and query names have been revised.

1–14 Version 4.0

Installation DirectoriesThe following table lists the file types that are installed when you install Tivoli Inventory, Version 4.0, and the directories in which those file types are installed.

The Tivoli Inventory files are installed into several directories under the Tivoli directory structure. The environment variable $BINDIR is the path to the Tivoli Management Framework and Tivoli Inventory executable files. $DBDIR is the path to the object database directory that is also created during installation of Tivoli Management Framework. See the Tivoli Management Framework Planning for Deployment Guide for more information about these variables.

File Type Location

Executable files $BINDIR/TME/INVENTORY $BINDIR/../generic/TME/INVENTORY$BINDIR/bin

Tivoli object database updates

$DBDIR

Man pages(UNIX only)

The man directory in the directory where the Tivoli Management Framework is installed.

HTML and Java files $BINDIR/../generic/HTTPd/Inventory$BINDIR/../generic/HTTPd/Inv$BINDIR/../generic/HTTPd/UserLink$BINDIR/../generic/inv/jars

CGI scripts $BINDIR/TAS/HTTPd/cgi-bin/InvServer$BINDIR/TAS/HTTPd/cgi-bin/InvEndpt$BINDIR/TAS/HTTPd/cgi-bin/UserLink

RDBMS configuration repository scripts

$BINDIR/../generic/inv/SCRIPTS/RDBMS

Inventory query scripts $BINDIR/../generic/inv/SCRIPTS/QUERIES

Software signature files $BINDIR/../generic/inv/SIGNATURES


Patches Included in This ReleaseThe following Tivoli Inventory, Version 3.6.2, patches are included in Tivoli Inventory, Version 4.0.

■ Tivoli Inventory patches:

• 3.6.2-INV-0001

• 3.6.2-INV-0003

• 3.6.2-INV-0004

• 3.6.2-INV-0005

• 3.6.2-INV-0010

• 3.6.2-INV-0018

• 3.6.2-INV-0022

■ SCS patches:

• 3.6.2-CLL-0001

• 3.6.2-CLL-0002

Defects Fixed in This ReleaseThis section lists the defects that have been fixed for this release of Tivoli Inventory. The APAR number (if any) precedes the description of each defect and the CMVC number (if any) follows the description.

Defects fixed for Tivoli Inventory, Version 4.0, include the following:

■ If you use an Informix RIM host and errors occur, RIM now returns appropriate error messages.

Gateway files $BINDIR/../lcf_bundle.40

Inventory endpoint scanner files

$BINDIR/../lcf_bundle.40/bin/$INTERP/inv/SCAN

Inventory endpoint executable files

$BINDIR/../lcf_bundle.40/bin/$INTERP/TME/INVENTORY

File Type Location

1–16 Version 4.0

■ Scans no longer return inaccurate information regarding video resolution and number of colors for multiple machines that have the same type of video card. (CMVC-75631)

■ Scans of PC platform types (Windows, Windows NT, and OS/2) no longer return path information inconsistently. (CMVC-79753, 79758)

■ Tivoli Inventory can now scan specific volumes on NetWare machines. (CMVC-79759)

■ Uninstalling Tivoli Inventory Gateway from multiple managed nodes no longer creates errors. (CMVC-81292, 115110)

■ In the Inventory Profile dialog box, managed resources no longer “move” from one nested profile manager to another. (CMVC-82399)

■ The SQL scripts created by Tivoli Inventory now produce column names that are the appropriate length. (CMVC-82723)

■ APAR-IX82845: For OS/2 Warp 4.0 and later, network card information is now populated correctly.

■ APAR-IX84578: Tivoli Inventory software scans now support file names up to 254 characters.

■ APAR-IX88405: The User Data Form responds correctly after you click the Submit Form button.

■ APAR-IY01749: Tivoli Inventory now scans Iomega Zip drives.

■ APAR-IY02540: Hardware scans now detect IDE hard-disk drives on Solaris 7 systems that have a PCI bus.

■ APAR-IY02653: Tivoli Inventory now supports 254 characters for object names in TME_OBJECT_LABEL field.

■ APAR-IY02931: Scans no longer return duplicate information when scanning UNIX systems with multiple processors.

■ APAR-IY03107: Hardware scans no longer duplicate MAC addresses in the configuration repository.

■ APAR-IY03347: Tivoli Inventory no longer produces an error while parsing the MIF file if a hardware scan reads a BIOS value that contains double quotation marks (").


■ APAR-IY13575: Tivoli Inventory no longer overwrites the userlink.htm file on endpoints to convert host names to the equivalent IP address.

Known Product Defects, Limitations, and Workarounds

This section describes known defects in Tivoli Inventory, Version 4.0. Where applicable and known, suggested workarounds are identified. Note that this might not be a complete list of defects.

Current defects, limitations, and workarounds for Inventory 4.0 include the following:

■ You might encounter warning messages when installing Tivoli Inventory Gateway on an OS/2 gateway. When you install Tivoli Inventory Gateway, you will see the following message:

Installing product:Tivoli Inventory Gateway, Version 4.0The following problems were encountered:Host link.dev.tivoli.com: Could not find a valid Binariesmedia packet listed in the installation index (.IND) filefor this type of platform. Check that the cdrom imagedirectory is set correctly for what you are trying to do.

Ignore the message and proceed with the installation. The gateway will function correctly.

■ When the database transaction log is full, Tivoli Inventory scans do not complete, and you cannot perform any operations that require access to the Tivoli Inventory configuration repository. No status, response, or error is provided. (CMVC-35663)

Workaround: Clear the transaction log. Contact your database administrator for assistance and other options.

■ Uninstalling Tivoli Inventory, Version 3.6.2, or Version 4.0, does not remove all components. Moreover, following an uninstall, reinstallation of some components fails. (CMVC-81012, 81016, 118324, 118632, 118634, 118636, 118637, 118640, 118641)

1–18 Version 4.0

Workarounds:

• If a RIM object fails to uninstall, delete the RIM object using the wdel command. For more information about the wdel command, see the Tivoli Management Framework Reference Manual.

• If you see the following error message when reinstalling Tivoli Inventory, Version 4.0:

repeater manager timeout

remove InventoryServer_ALIDB in the $DBDIR/.installed directory.

• To remove Tivoli Inventory Gateway, perform the following steps:

1. In the lcf_bundle.40/.installed directory, remove InventoryGateway_LCFNEW.

2. In the $DBDIR/.installed directory, remove InventoryGateway_ALIDB.

3. In the $BINDIR/.installed directory, remove InventoryGateway_BIN.

■ When a message to indicate an SCS exception to the status collector is returned, the scan ID might display incorrectly. (CMVC-81189)

■ If you place a firewall between a pair of collectors or between a collector and the inventory data handler, certain configurations might prevent SCS data from passing through the firewall. This problem usually occurs when port filtering rules restrict both the allowable source port ranges and the allowable destination port ranges for a given connection. (CMVC-82376)

Workaround: To prevent this problem, reconfigure the port filtering rules as follows, if allowed by the network administration guidelines for your organization. Assuming that SCS traffic flows from the far (outer) side of the firewall towards the inside:

• Do not constrain the source port range for connections coming in from the far (outer) side of the firewall.


• Continue to constrain destination port range for connections coming in from the far (outer) side of the firewall.

■ If you reduce the depot size using the wcollect –z command, and then restart the collector without deleting the data from the existing depot directory, an error occurs. (CMVC-82708)

Workaround: To reduce the size of a depot, follow these steps:

1. Make sure the depot is empty. If any data is present in the depot, wait until it has been processed.

2. Reduce the size of the depot using the wcollect command.

3. Delete the existing depot directory.

4. Restart the collector to activate the changes.

For more information about using the wcollect –z command to configure depot size, see the Tivoli Inventory User’s Guide.

■ If you have a negative value in a MIF table, an exception occurs. (CMVC-110549)

Workaround: Do not use any negative values in MIF tables. Negative values are allowed in group definitions, however.

■ The DMI GUI does not check to see whether table and column names you enter are longer than the maximum size allowed by the database. (CMVC-114818)

Workaround: When entering data in the Tivoli Inventory DMI GUI, make sure that the table name and column name are not longer than the longer than the maximum size allowed by the database and do not use SQL reserved words. The table name and column names must contain only the following characters:

• Lowercase a through z

• Uppercase A through Z

• Numeric characters 0 through 9

You cannot use spaces; names must start with a letter.

■ If you attempt to perform a task without the proper authorization, the task fails, but the Tivoli Inventory GUI does not return an error to indicate that the task was not performed. (CMVC-115305)

1–20 Version 4.0

■ In the Software Scan Configuration dialog box, when you change a directory from Include to Exclude by clicking Include and using the menu to change the value to Exclude, no error checking is performed. (CMVC-116729)

■ While using UserLink, when you add a MIF group or attribute using invalid characters, the following error message is displayed:

Group Name n contains space

This message is incorrect. The error message should read:

Group Name n contains invalid characters

(CMVC-117738)

Workaround: Use valid characters for MIF groups and attributes. Valid characters are as follows:

• Lowercase a through z

• Uppercase A through Z

• Numeric characters 0 through 9

• Underscores

You cannot use spaces; MIF group and attribute names must start with a letter.

■ When entering a software signature in the Tivoli Inventory GUI, the maximum length of any entry in any field cannot exceed 254 bytes or 127 double-byte character set (DBCS) characters. The signature will not be saved if any field exceeds the maximum length. (CMVC-117794)

■ In the HDISK_QUERY query, the HDISK_SIZE_MB field displays data in KB rather than MB. (CMVC-118012)

■ When distributing a profile, you cannot select subgroups from within the list of subscribers assigned to the profile and distribute the profile only to those subscribers. You must distribute the profile to all subscribers in the profile or create a new profile containing the subgroups to which you want to distribute the profile. (CMVC-118151)


■ When video memory is not detected, Tivoli Inventory reports a 0 for WMI systems and a -1 for non-WMI systems. (CMVC-118173)

■ If you run the default DMI scan without configuring it, the scan returns a MIF parse error. (CMVC-118196)

Workaround: Configure the default DMI scan before running the scan.

■ The Tivoli Inventory GUI might not add the DMI layer for OS/2 systems. (CMVC-118206)

Workaround: Run the following command at the endpoint:

dmiscan.exe -x dmidump.xml

You can either telnet to the OS/2 endpoint or run the command directly from the OS/2 endpoint.

■ In the DMI Scanner Configuration window in the Tivoli Inventory GUI, the Cancel button might not reload the previous DMI layers into memory, and any modified but canceled DMI layers still appear. (CMVC-118233)

Workaround: Close and login again to the Tivoli Inventory GUI.

■ With a Sybase database, after running the winvrmnode -l endpoint command to remove an endpoint, the history queries H_INST_FILE_QUERY, H_NATIVE_SWARE_QUERY, and H_NOSIG_FILES_QUERY return no data. The database, however, is updated. (CMVC-118263)

Workaround: Access the tables using isql commands to return the updated data.

■ While using UserLink, when you delete attributes, you might get the following error message:

couldn’t set locale correctly

Ignore the message. The attributes are still deleted. (CMVC-118356)

■ You cannot configure a DMI scan for the DMI layer of an endpoint across an interconnected TMR. (CMVC-118382)

1–22 Version 4.0

Workaround: Access the endpoint from the local TMR. Or, to access the endpoint across interconnected TMRs, you can change the role map for the super role in the remote TMR. However, this is a potential security risk, so if you choose to use this method, be sure to restore the role map for the super role when you are finished, as described in steps 6 and 7 of the following procedure. To access the endpoint in the remote TMR, follow these steps:

1. In the local TMR, run the wlsconn command to get the remote TMR’s region ID (remote_TMR_region_ID).

2. Run the following command to delete the role map for the super role in the remote TMR:

odadmin region delete_role_map remote_TMR_region_ID \super

3. Run the following command to add the role map for the super role in the remote TMR:

odadmin region add_role_map remote_TMR_region_ID \super super

4. Verify that the role was mapped using the following command:

odadmin region list_map remote_TMR_region_ID

5. Configure DMI scan options for the DMI layer of the endpoint in the remote TMR.

6. Run the following command to delete the role map for the super role in the remote TMR:

odadmin region delete_role_map remote_TMR_region_ID \ super

7. Run the following command to add the map for the super role in the remote TMR:

odadmin region add_role_map remote_TMR_region_ID \super user

■ When you double-click a profile, if you enter a non-existing user in the Tivoli Management Environment login window and click OK, the login window disappears; it does not matter what you enter for the password if the user does not exist. (CMVC-118497)


Workaround: You must enter a valid user at the Tivoli Management Environment login window.

■ The Tivoli Inventory GUI cannot start on a managed node if the managed node name does not match the host name. (CMVC-118552)

Workaround: If you receive the following error when trying to start the GUI:

"The Inventory Configuration Console host ’managed_node_name’ cannot be found in this TMR"

issue the following command to change the managed node name to match the host name:

echo "managed_node_name" | idlcall managed_node_object_id _set_label

where managed_node_object_id is the object ID of the managed node. See the Tivoli Inventory User’s Guide, Version 4.0, for information about determining the object ID of a system.

■ RIM truncates the names of tables and columns that begin or end with an underscore character (_). (CMVC-118557)

Workaround: Do not begin or end the name of a custom table or column with an underscore character.

■ If you install Tivoli Inventory, Version 3.6.2, and Tivoli Inventory, Version 4.0, within the same TMR, the status collectors for both of the versions write to the same directory. An error message similar to the following is displayed:

The restore operation could not be performed for file‘c:\name-tmr2\db\name.db\inventory\stat_dir\inv_stat_1.cfg’ scan id ‘1’.The file contains invalid data.

(CMVC-118631)

Workaround: To resolve this issue, complete the following procedure.

1. Move the status collector directory for one of the installations of Tivoli Inventory. To move the Version 3.6.2 status collector, use the following command:

wsetinvrcvr -d new_362_directory

1–24 Version 4.0

Or, to move the Version 4.0 status collector, use the following command:

wsetinvdh -d new_40_directory

2. Specify a different location for the run-time directory.

To move the Version 3.6.2 run-time directory, run the following command:

wcollect -l new_362_directory \ @InventoryReceiver:inv_receiver

Or, to move the Version 4.0 run-time directory, run the following command:

wcollect -l new_40_directory \ @InvDataHandler:inv_data_handler

3. Kill the inv_stat_meths process. This process restarts automatically the next time it is called.

■ The Full checksum option is not generated. (CMVC-118663)

Workaround: Select the Quick or MD5 checksum option instead.

■ Tivoli Inventory populates the BIOS_MANUFACTURER column with hardware manufacturer values rather than BIOS manufacturer values. (CMVC-118666)

■ The PRFL_ACTION (profile action) column in history tables contains an incorrect value in some circumstances. (CMVC-118683)

■ When you run dmiscan.exe locally on an endpoint, it creates incorrect MIF files and SQL scripts. (CMVC-118687)

Workaround: Use the Tivoli Inventory GUI to run DMI scans.

■ Software scans fail on NetWare 4.x endpoints. (CMVC-118819)

Known Documentation DefectsIn the Tivoli Inventory online help and in the Tivoli Inventory User’s Guide descriptions of wsetinvpcfiles and wsetinvunixfiles, the examples for specifying directories to exclude in a scan using wildcards are incorrect. You cannot use an asterisk as a part of a directory name, for example *abc or abc/def*. In these examples, the asterisk is treated


as a literal character. However, you can use an asterisk to represent an entire directory name or sequence of directory names, for example, */abc or /abc/*. In these examples, */abc matches any path that ends with the directory /abc, for example /def/abc/ and /abc/. The entry /abc/* matches any path that begins with the directory /abc/, for example /abc/ and /abc/def/.

InternationalizationTivoli Inventory is available in a number of languages. This section covers issues specific to internationalized versions of Tivoli Inventory. For other information about internationalization issues, see the Tivoli Management Framework Release Notes.

Enabling Language Support Tivoli Inventory is translated into the following languages:

■ Brazilian Portuguese

■ Chinese (Simplified)

■ Chinese (Traditional)

■ French

■ German

■ Italian

■ Japanese

■ Korean

■ Spanish

To enable these languages, install the appropriate language support pack from the Tivoli Inventory Language Support Version 4.0 CD. You can also install multiple language support packs for a single product. For installation instructions, see the procedures in the Tivoli Enterprise Installation guide for installing a product.

1–26 Version 4.0

International Defects FixedIn the Korean version of Tivoli Inventory, profile distributions no longer fail from a Windows NT managed node to a Windows NT or Windows 95 endpoint. (CMVC-54591)

International Defects, Limitations, and WorkaroundsThis section describes the known defects in international versions of Tivoli Inventory, Version 4.0. The APAR number (if available) precedes the description of each defect and the CMVC number (if available) follows the description. Where applicable and known, suggested workarounds are identified.

■ HP-UX systems cannot display Asian (Chinese, Japanese and Korean) characters because Asian TrueType fonts are not available on the HP-UX platform. HP is working on providing those fonts on HP-UX. In the meantime, you must use TrueType fonts from other vendors. For more information, see the SDK release notes for version 1.2.2.05 at http://www.unix.hp.com.

■ For the winvsig command, the following message is not internationalized:

Each dot represents 100 lines processed

■ The component names used with the wsetinvpchw and wsetinvunixhw command options are not internationalized.

■ In the French and German versions of Tivoli Inventory, if you right-click a system icon to select the Software Tivoli Inventory option and no information is found for that system, the error message

No data found for ...

is not translated. (CMVC-54564, 62138)

■ In the Korean version of Tivoli Inventory, profile distributions fail on Solaris and Windows NT managed nodes. (CMVC-54582)

■ On AIX 4.xJ systems, if you display output of a query that has been saved to a file, some of the DBCS characters appear as question marks (??). (CMVC-54587)


■ In the French version of Tivoli Inventory, in the Create Query dialog, if you click the Table Description button, the words String and Integer are not translated in the window that is displayed. (CMVC-54653)

■ Bold characters are not displayed in the online help that contains DBCS languages. This defect is a restriction of Java 1.2.2. (CMVC-115805)

■ In international versions of the Tivoli Inventory GUI, if you click Custom Filters, click the right arrow in the window, and click Show Filter Row, the status message

<no filter>

is not translated. (CMVC-115975)

■ The component names used with the wgetinvpchw and wgetinvunixhw command options are not internationalized. (CMVC-116097, 116116)

■ Some menu key combinations are not translated. (CMVC-116465)

■ For DBCS online help, whenever DBCS characters follow single-byte character set (SBCS) characters, the DBCS characters show up on the following line. (CMVC-116663)

■ In international versions of the Tivoli Inventory online help, the text above tables might be truncated. (CMVC-116166)

■ The Simplified Chinese fonts in the Tivoli Inventory GUI might not display clearly. This is a restriction with JDK 1.2.2. (CMVC-116708)

■ For Traditional Chinese, the underscore characters overwrite the text when hypertext link is selected. (CMVC-116793)

■ In the Tivoli Inventory GUI, the Select Input Method menu is not translated. (CMVC-117044)

■ The keywords with the wdistinv command not translated. The date format also does not support all possible date formats. (CMVC-117114)

■ The Windows system fonts are different from the fonts used in the Tivoli Inventory GUI and online help. This is a restriction with JDK 1.2.2. (CMVC-117337)

1–28 Version 4.0

■ The User Data Template does not display text correctly for Japanese versions of Tivoli Inventory if the code page for the operating system does not match the code page for the browser. (CMVC-118161)

Workaround: Use a browser that is compatible with the code page for your operating system.

■ On Japanese systems, files names entered in the custom filter in the Tivoli Inventory GUI do not display correctly after the display is refreshed. (CMVC-118351)

Product NotesThis section contains important information that you should consider when using Tivoli Inventory.

The APAR number (if available) precedes the description of each defect and the CMVC number (if available) follows the description. Where applicable and known, suggested workarounds are identified.

■ You can run the Tivoli Inventory GUI on a managed node only.

■ Default inventory hardware scans can get BIOS information (such as serial numbers) for system management BIOS (SMBIOS)-compatible machines only. To get BIOS information for a non-SMBIOS-compatible machine, you must scan the DMI service layer of the machine. For more information about the DMI scanner, see the Tivoli Inventory User’s Guide. To determine whether your systems are SMBIOS-compatible, contact your hardware vendor.

■ When you install Tivoli Management Framework on any of the UNIX architectures, you should create a tmersrvd or nobody account under which Tivoli Management Framework will run. The account varies with each architecture. On Windows NT, Tivoli Management Framework requires the tmersrvd user account and the Tivoli_Admin_Privileges group account. These accounts are automatically created during the installation process and should not be deleted. For more information, see the Tivoli Management Framework Release Notes.


■ Using Tivoli Inventory and SCS, you can configure multiple database connections to write data to the configuration repository in parallel. To avoid locking problems, you should set the locking for your RDBMS to the smallest granularity possible. (For example, row locking is smaller granularity than page locking.) If possible, do not permit table locking in your RDBMS. Table locking can potentially slow or halt inventory scans.

Tivoli Inventory uses the current locking settings of your RDBMS. (An exception is Informix RDBMSs, which use row-level locking. For Informix, locking is set in the inv_infx_schema.sql and h_inv_infx_schema.sql scripts.) For information about changing locking settings, consult the documentation for your RDBMS.

■ Tivoli Inventory uses WMI whenever possible to return information about hardware. However, when WMI is not available, Tivoli Inventory uses other methods to return information about these devices. The information collected using WMI might be described differently than that collected using other methods. For example, WMI might return “Windows 2000 Professional” while other methods return “Windows 2000.”

■ For NetWare and OS/2 gateways, it is possible that all endpoints on the gateway will return their scan data at or near the same time. Therefore, you must ensure that there is enough space in the depot to hold scan data for all endpoints on each NetWare or OS/2 gateway. It is recommended that you use no more than five endpoints per NetWare or OS/2 gateway.

■ Tivoli Software Distribution users who want to access the configuration repository for Tivoli Inventory, Version 4.0, must run the following CLI command on a managed node or the TMR server:

winvrim40

This command renames the "inventory" RIM object “inv_362,” and renames the "inv_40" RIM object "inventory." Doing this enables the RIM object named "inventory" to access the version 4.0 configuration repository.

1–30 Version 4.0

To restore the original names of the RIM objects so that Tivoli Software Distribution accesses the version 3.6.2 configuration repository, run the following command:

winvrim362

Note: The winvrim362 and winvrim40 commands do not affect Tivoli Inventory.

■ Tivoli Inventory cannot distinguish between multiple identical devices on a single system, such as two identical CD-ROM drives on one workstation. Therefore, if you remove one of the devices, the history table shows a delete record for one of the devices, but does not specify which device was removed.

■ Large MIF files can cause memory errors. When a MIF file is read, its contents are stored in memory. If the MIF file is very large, it can exceed the memory limits of a machine. To avoid this problem, use multiple smaller MIF files rather than one large MIF file, or add memory to your system. For more information about creating MIF files, see “Using Custom MIF Files” in Chapter 7, “Collecting Custom Information with Tivoli Inventory,” in the Tivoli Inventory User’s Guide, Version 4.0.

■ The message index button on the Tivoli Assistant is disabled for Tivoli Inventory, Version 4.0. The message index feature is not supported for this release.

■ When creating a RIM object with the wcrtrim command, passwords must be limited to eight characters.

■ In general, Tivoli does not support virtual disk drive software when recognizing either hardware devices, logical drives, or scanning for software.

■ To view online help for dialog boxes that do not have a help icon, first launch the Tivoli Assistant from a GUI window that has the icon. Next, open the desired dialog box. The Tivoli Assistant automatically displays the online help for that dialog box. Alternatively, you can use the index for the online help to locate the desired online help document.

■ If the system TrueType fonts are installed in a location other than the default path


(/usr/openwin/lib/locale/$LANG/X11/fonts/TrueType), the FONTPATH variable in inv_gui.sh should be modified to reflect this location.

■ If fonts do not display properly on an HP-UX system, set the JAVA_FONTS environment variable to point to the location of the fonts on your system. For example, if the fonts are located in the /usr/lib/X11/fonts/ms.st/typefaces directory, set the JAVA_FONTS environment variable as follows:

export JAVA_FONTS=/usr/lib/X11/fonts/ms.st/typefaces

■ HP does not provide a TrueType font as part of the operating system. To run the Java GUI on an HP-UX 11 system, you must install a TrueType font on the machine.

■ The winvrmnode command does not remove data from custom tables in MS SQL Server or Sybase RDBMSs. Moreover, the winvrmnode command removes data from custom tables in supported DB2, Informix, and Oracle RDBMSs only if you create a foreign key constraint that enables cascading deletes. For more information about cascading deletes, see Chapter 7, “Collecting Custom Information with Tivoli Inventory,” in the Tivoli Inventory User’s Guide, Version 4.0.

■ When Tivoli Inventory scans an endpoint, it stores a file on the endpoint named sd_scan.nfo. This file contains the same information as a MIF file generated by a hardware scan. This file is used by the Tivoli Software Distribution product only.

■ When both Version 3.6.2 and Version 4.0 of Tivoli Inventory are installed in the same TMR, the pop-up menu that appears when you right-click on an endpoint in the Profile Manager dialog box displays the Execute Query option twice. You can select either option; they are identical.

■ If a scan fails, the following directory is not deleted: $DBDIR/inventory/INVnnnn, where nnnn is the scan ID. You can delete these directories manually if desired, but it is not necessary to delete them.

■ Tivoli Inventory does not create indices for tables in the configuration repository. If desired, you can create indices to optimize the mining of historical data from the configuration

1–32 Version 4.0

repository. See a database administrator for more information. For example, you could create an index for COMPUTER_SYS_ID to sort data by system, or for RECORD_TIME to sort data by the time of the scan. Or, you could create an index for multiple attributes.

■ It is recommended that the number of output threads for the inventory data handler match the total number of RDBMS connections set for all RIM objects used by the inventory data handler. By default, the RIM object has one RDBMS connection, and the inventory data handler has five output threads. Therefore, you might see the following error message:

The Inventory Data Handler was unable to find or connect to a valid RIM object. Please check your RIM connections for the Inventory Data Handler

To resolve this error, set the number of output threads for the inventory data handler match the total number of RDBMS connections set for all RIM objects used by the inventory data handler. For the procedures to complete these tasks, see the Tivoli Inventory User’s Guide, Version 4.0.

■ APAR-IY04686: Although it is possible to configure Tivoli Inventory and TEC to share a database instance or schema, Tivoli does not recommend using this configuration. If you choose to use this configuration, you should consult with a qualified DBA on the proper use of tuning parameters to ensure the best performance for both applications involved. In addition, you should thoroughly test your environment to ensure that it works properly.

tivoli inventory release notes version 4 -...

Documents