bmc foundation discovery and bmc topology discovery · pdf filebmc foundation discovery and...

Release Notes

BMC Foundation Discovery andBMC Topology DiscoveryVersion: 1.5.00January 3, 2008

BMC Software is releasing version 1.5.00 of the BMC Foundation Discovery and BMC Topology Discovery products as a Controlled Availability (CA) release. These release notes provide information about the enhancements and resolved problems in this release. The information in this document supplements and supersedes information in the BMC Foundation Discovery and BMC Topology Discovery product manuals.

The following topics are discussed:

Controlled Availability release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Discovery server database requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Discovery server hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . 5Discovery client hardware and software requirements. . . . . . . . . . . . . . . . . . . . . . . 6BMC Atrium Configuration Management Database requirement . . . . . . . . . . . . . 6BMC Discovery Solution requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6BSM interoperability requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Downloading the product installation files from the web. . . . . . . . . . . . . . . . . . . . . . . . 8What’s new . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

BMC Discovery Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Installation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10License report utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Preference-based discovery during data collection . . . . . . . . . . . . . . . . . . . . . . . . . 11Normalization of discovered data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Definitive Software Library Product Dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Discovery default categorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Default class and attribute merge precedence values . . . . . . . . . . . . . . . . . . . . . . . 12Enabling communication between the discovery server and client when a

firewall separates the two . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

NOTE Before you install the products, check the Customer Support website at http://www.bmc.com/support_home for updated information about this version. Flashes, technical bulletins, and resolutions on the site contain details about any fixes that were issued for this version after its release.

Draft

*87103**87103*

*87103*

http://www.bmc.com/support_home

CMDB Connection Settings wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Discovery report for computer systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Synchronization error report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Discovery filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Synchronization filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Repository Legend / Filter pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14CI Lifecycle option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Viewing the synchronization results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Storage area network discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

SMIS method for the storage area network discovery. . . . . . . . . . . . . . . . . . . . 15New storage area network CIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15New storage inventory queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Virtual systems inventory discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16UNIX virtual systems discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Support for ESX Server 3.x and Virtual Center 2.0. . . . . . . . . . . . . . . . . . . . . . . 16

Key-based SSH authentication for UNIX asset inventory discovery . . . . . . . . . . . 16Universal Application Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Template processing phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Process list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Updated process properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Updated icon for the non-qualified application system CI. . . . . . . . . . . . . . . . 17

Synchronizing discovery data from multiple discovery servers with a single BMC Atrium CMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Inventory discovery task processing phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Data model documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Combining discovery domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

What’s changed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Product download method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Product documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Siebel, SAP, J2EE, and web services discovery types . . . . . . . . . . . . . . . . . . . . . . . . 20Discovery data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Updated discovery task messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Updated synchronization task messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Updated BMC Atrium CMDB Reconciliation Engine jobs, identification activities,

and merge activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Host inventory discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21SAP enterprise application discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Enhanced Windows asset inventory discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Enhanced UNIX asset inventory discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Enhanced network topology resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Removed aliases for CIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Open issues and resolutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Reconciling the topology import dataset with the asset dataset . . . . . . . . . . . . . . . . . . 24Open issues and resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Updating the BMC Topology Discovery configuration file to avoid an Out of Memory error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Corrected problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Support for BMC Foundation Discovery and BMC Topology Discovery . . . . . . . . . . 30

Levels of support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Product documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Draft

2 Release Notes January 3, 2008

Controlled Availability release

Where to view the latest product information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31How to obtain the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Customer support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Controlled Availability releaseThe BMC Foundation Discovery and BMC Topology Discovery 1.5.00 products have been released as Controlled Availability (CA). You must install BMC Foundation Discovery and BMC Topology Discovery 1.5.00 only if you do not already have a discovery server installed. If you have an earlier version of the discovery server installed, this CA release does not upgrade your existing discovery server to version 1.5.00 and does not include utilities to help you migrate your existing discovery settings for use in version 1.5.00.

The upgrade functionality and the utilities to migrate your existing discovery settings will be available in the General Availability (GA) release of BMC Foundation Discovery and BMC Topology Discovery.

System requirementsThis section describes the system requirements for the discovery server database and the discovery application server and client.

WARNING You must not change the system time on the discovery server after you install BMC Foundation Discovery or BMC Topology Discovery and start running discovery tasks.

The system time on the discovery server is used to maintain a record of when the discovery tasks were run and the configuration data in the datastore was added or updated. Any changes to the system time on the discovery server, except the Daylight Saving Time (DST) changes, will affect the way BMC Foundation Discovery or BMC Topology Discovery functions. For example, the CMDB synchronization task refers to the updated date of the configuration items (CIs) in the datastore to determine the delta that has to be synchronized with the BMC Atrium Configuration Management Database (BMC Atrium CMDB) product.

Draft

BMC Foundation Discovery and BMC Topology Discovery Version 1.5.00 3

Discovery server database requirements

Discovery server database requirements

You can use a local or remote database system. The database instance for the discovery datastore must be installed on the same computer on which you installed your database. The database can be one of the following database management systems:

■ Oracle® Database 9i Standard Edition or Enterprise Edition with patch set 9.2.0.7 or later

■ Oracle Database 10g Standard Edition or Enterprise Edition with patch set 10.2.0.3 or later

■ Microsoft SQL Server 2000 Standard Edition or Enterprise Edition with service pack 4 or later

■ SQL Server 2005 Standard Edition or Enterprise Edition with service pack 1 or later

BSM Interoperability and BMC Discovery Solution have been tested with SQL Server 2005 as the discovery database. For more information about BSM interoperability, see “BSM interoperability requirements” on page 7. For more information about the BMC Discovery Solution, see “BMC Discovery Solution requirements” on page 6.

The resources required to create the database instance on the Microsoft Windows operating system manually or to create the database instance on the UNIX® or Linux® platforms are in the Manual_DB_Creation folder, which is located in the Datastore directory. Follow the instructions in the BMC Foundation Discovery and BMC Topology Discovery: Planning and Installation guide. BMC Software recommends that these operations be performed by a database administrator.

NOTE If you are using SQL Server as your database, use a case-sensitive database and install the database and discovery server on separate computers.

WARNING Do not modify the database creation scripts to change the database options, including the character set, or any performance settings except when recommended by BMC Customer Support.

Draft


Discovery server hardware and software requirements

Discovery server hardware and software requirements

The discovery server requires a dedicated Windows server that meets the system requirements listed in Table 1.

Table 1 Discovery server requirements

Resource Minimum requirements Comments

hardware dual 2.1-GHz processors

four 2.1-GHz processors for large environments

The server must be dedicated to BMC Discovery.

If the database system is installed on a separate computer, it should also have dual 2.1 GHz processors at a minimum.

English operating systems

any of the following products:■ Windows 2000 Server, latest service pack■ Windows Server 2003 Standard Edition (32-bit),

latest service pack

For Windows Server 2003, 64-bit hardware is supported but the operating system must be running in 32-bit mode.

memory 2 GB RAM for the discovery server

2 GB RAM for the database, of which 1.3 GB RAM are required for the database instance

If you install both the database and the discovery server on the same computer (not recommended if you use SQL Server as your database), the system requires a minimum total of 4 GB RAM.

disk space 2 GB minimum for the discovery server

4 GB minimum for the database, with additional 4 GB disk space recommended to accommodate growth of the database tablespace and index tablespace (2 GB for each)

Separate drives are also recommended for the index tablespace and database tablespace.

For information about sizing the database, see the BMC Foundation Discovery and BMC Topology Discovery: Planning and Installation guide.

browser Microsoft Internet Explorer 5.5 or later You can download Internet Explorer from the Microsoft website (http://www.microsoft.com).

Draft


http://www.microsoft.com

Discovery client hardware and software requirements

Discovery client hardware and software requirements

Table 2 lists the requirements for the discovery client.

BMC Atrium Configuration Management Database requirement

If you plan to export discovery data to BMC Atrium CMDB, BMC Foundation Discovery and BMC Topology Discovery 1.5 require BMC Atrium CMDB version 2.0.01 with patch 005 or 2.1.00. For BMC Atrium CMDB installation instructions, see the BMC Atrium CMDB Installation and Configuration Guide.

BMC Discovery Solution requirements

You can use BMC Foundation Discovery and BMC Topology Discovery 1.5.00 as part of the BMC Discovery Solution 2.0.01. For more information about the BMC Discovery Solution, see “BMC Discovery Solution” on page 9. In addition to BMC Foundation Discovery and BMC Topology Discovery 1.5.00, the following products have been tested for BMC Discovery Solution 2.0.01:

■ A combination of BMC Atrium CMDB, BMC Atrium Integration Engine, and BMC Remedy Action Request System (BMC Remedy AR System):

— BMC Atrium CMDB 2.0.01 with patch 005, BMC Atrium Integration Engine 7.0.01 with patch 003, and BMC Remedy AR System 7.0.01

— BMC Atrium CMDB 2.1.00, BMC Atrium Integration Engine 7.1.00, and BMC Remedy AR System 7.1.00 with patch 002

Table 2 Discovery client requirements

Resource Required hardware or software

hardware 1.6-GHz processor

English operating systems any of the following products:■ Windows 2000 Professional with the latest service

pack■ Windows XP with the latest service pack

memory 1 GB

disk space 100 MB

browser Internet Explorer 6

Draft


BSM interoperability requirements

■ BMC Configuration Management 7.2.00

■ BMC Configuration Management Configuration Discovery Integration for CMDB 7.2.00

■ BMC Remedy Asset Management 7.0.02, with patch 007

■ BMC Discovery 1.5.00 for z/OS®

BSM interoperability requirements

You can use BMC Foundation Discovery and BMC Topology Discovery 1.5.00 as part of a Business Service Management (BSM) solution that can include BMC Impact Solutions, BMC Remedy Asset Management, and BMC Configuration Discovery. BMC Foundation Discovery and BMC Topology Discovery 1.5.00 provide support for BSM Interoperability 2.6.1, in addition to the support available for earlier versions. For more information about BSM Interoperability 2.6.1, see the BSM Interoperability 2.6.1 Installation Overview, the BSM Interoperability 2.6.1 Installation and Configuration Guide, and the BSM Interoperability 2.6.1 Release Notes.

In addition to BMC Foundation Discovery and BMC Topology Discovery 1.5.00, the following products and applications have been tested for BSM Interoperability 2.6.1:

■ BMC Analytics for Business Service Management 2.0.00■ BMC Atrium CMDB 2.1.00 with patch 001■ BMC Atrium Integration Engine 7.1.00 with patch 001■ BMC Capacity Management Essentials 1.1.00■ BMC Configuration Drift Management 7.2.00■ BMC Configuration Management 7.2.00, including BMC Desktop Deployment

Module■ BMC Configuration Management Configuration Discovery Integration for CMDB

7.2.00■ BMC Dashboards for Business Service Management (BMC Dashboards for BSM)

2.0.00■ BMC Discovery 1.5.00 for z/OS

NOTE At the Controlled Availability release of BMC Discovery Solution 2.0.01, BMC Remedy AR System 7.1.00 patch 002 is not available. Contact BMC Customer Support for HotFixes to issues SW00278236 and SW00278501.

Draft


Downloading the product installation files from the web

■ BMC Impact Solutions 7.1.00, including:— BMC Impact Administration Server— BMC Impact Explorer (BMC IX)— BMC Impact Integration for z/OS— BMC Impact Integration Web Services— BMC Impact Manager (BMC IM)— BMC Impact Service Model Editor— BMC Impact Publishing Server— Integration for BMC Remedy Service Desk (IBRSD) 7.1.00

■ BMC Portal 2.5.00, including the following modules:— BMC Impact Portal 7.1.00— BMC Performance Exception Detector 1.3.20— BMC Performance Manager Portal 2.5.00

■ BMC Remedy AR System 7.1.00 with patch 001■ BMC Remedy IT Service Management (BMC Remedy ITSM) 7.0.02 with patch 007,

including:— BMC Remedy Asset Management— BMC Remedy Change Management— BMC Remedy Service Desk (including BMC Remedy Incident Management

and BMC Remedy Problem Management)■ BMC Service Level Management 7.1.00■ BMC Service Request Management 2.1.00 with patch 001■ BMC Transaction Management Application Response Time (BMC TM ART) 3.2.00

(either Infrastructure Edition or Service Level Edition)■ BMC Transaction Management Real Experience Monitor (BMC TM REM) 1.2.00■ BMC Transaction Management Root Cause Analysis (BMC TM RCA) 1.5.00 (for

Microsoft Windows or J2EE™)

Downloading the product installation files from the web

Perform the following steps to download the BMC Foundation Discovery and BMC Topology Discovery 1.5.00 installation files from the BMC Software Electronic Product Download (EPD) website:

1 On the discovery server, create a temporary folder in which to download the installation files.

2 Go to the EPD website, http://webapps.bmc.com/epd.

Draft


http://www.bmc.com/ega

http://webapps.bmc.com/epd

What’s new

3 Type the user ID and password given to you by your BMC Software sales representative and click Submit.

4 Follow the steps on the site to navigate to the Download Files page for BMC Foundation Discovery and BMC Topology Discovery 1.5.00.

5 Download the appropriate product installation files.

For information about the files you need to download, see the BMC Foundation Discovery 1.5.00 Read This First or the BMC Topology Discovery 1.5.00 Read This First on the Download Files page.

6 Unzip any downloaded .zip file into the temporary folder that you created in step 1.

7 Complete the installation procedure by following the instructions in the BMC Foundation Discovery and BMC Topology Discovery: Planning and Installation guide.

What’s newBMC Foundation Discovery and BMC Topology Discovery have been enhanced with the following new features.

BMC Discovery Solution

BMC Foundation Discovery and BMC Topology Discovery 1.5.00 are part of the BMC Discovery Solution 2.0.01. This solution provides several features to achieve data normalization during data collection, preference-based discovery to reduce duplication, filtering at data collection and prior to import of the discovered data, and reconciliation of discovered configuration data with BMC Remedy Asset Management. For a list of all the products that have been tested for the BMC Discovery Solution, see “BMC Discovery Solution requirements” on page 6.

For more information about the BMC Discovery Solution, see the BMC Discovery Solution Planning and Implementation Guide and BMC Discovery Solution Installation and Tuning Guide.

Draft


Installation process

Installation process

The following improvements have been made to the product installation process:

■ The process of installing BMC Foundation Discovery and BMC Topology Discovery products has been simplified. You can now install BMC Topology Discovery before you install BMC Foundation Discovery. When you install BMC Topology Discovery, the installation process also installs BMC Foundation Discovery.

■ When you install BMC Foundation Discovery or BMC Topology Discovery, you can also configure a connection to BMC Atrium CMDB and install the required Common Data Model (CDM) extensions.

License report utility

To simplify how BMC Software conducts business with its customers and to enhance the ease of use of its products, the company is implementing a change in its product licensing method. BMC now provides a utility to help you track product usage and maintain product license compliance in your environment. If you are installing version 1.5.00 of BMC Foundation Discovery or BMC Topology Discovery, the reporting utility is installed with your product.

To use the license report utility

1 Navigate to Help => Save License Report.

2 In the File Name field, type the name you want to use to save the license report.

3 Click Save.

Draft


Preference-based discovery during data collection

Preference-based discovery during data collection

Preference-based discovery reduces the number of duplicate CIs collected, imported into, and reconciled with the production dataset when multiple discovery products discover configuration data on the same endpoint. If both BMC Configuration Management and BMC Foundation Discovery and BMC Topology Discovery discover configuration data on an endpoint, BMC Configuration Management becomes the preferred provider of the following common classes:

■ BMC_BIOSElement ■ BMC_Card ■ BMC_CDROMDrive ■ BMC_DiskDrive ■ BMC_FloppyDrive ■ BMC_LocalFileSystem ■ BMC_Monitor ■ BMC_Patch ■ BMC_Processor ■ BMC_Product

For more information, see the BMC Discovery Solution Planning and Implementation Guide.

Normalization of discovered data

When BMC Foundation Discovery and BMC Topology Discovery or BMC Configuration Management creates an instance of a class, certain CI attribute values are normalized using a variety of methods and for the following purposes:

■ Software titles are normalized against Product Dictionary (PD) entries in the Definitive Software Library.

■ Key attributes are populated and normalized to identify instances for reconciliation from multiple discovery providers.

■ The relationship name attribute is populated to define the specific type of relationship between a pair of CIs, based on their class and what the class represents.

For information about how BMC Discovery normalizes discovered data and a list of the key attributes, see the BMC Discovery Solution Planning and Implementation Guide.

Draft


Definitive Software Library Product Dictionary

Definitive Software Library Product Dictionary

For instances of the BMC_Product class, BMC Foundation Discovery and BMC Topology Discovery normalize the Model, VersionNumber, and ManufacturerName attributes against Product Dictionary entries in a local copy of the Definitive Software Library (DSL) before inserting the data into the discovery datastore.

Discovery default categorization

Product categorization standardizes the Category, Type, Item, ManufacturerName, and Model attribute values inherited from the BMC_BaseElement class. BMC Foundation Discovery and BMC Topology Discovery and BMC Configuration Management set default categorization values for discovered CIs. When a CI is inserted or updated in the BMC Atrium CMDB, categorization validation workflow runs to make sure that CIs are inserted only with valid categorization.

Default class and attribute merge precedence values

BMC Foundation Discovery and BMC Topology Discovery and BMC Configuration Management provide class and attribute merge precedence values for reconciliation by the BMC Atrium Reconciliation Engine. Merge precedence determines which provider’s CI is merged to the BMC Asset dataset if multiple providers were identified for reconciliation. If neither BMC Discovery provider has precedence, all discovery providers have equal precedence. For complete information about merge precedence, see the BMC Discovery Solution Planning and Implementation Guide.

Enabling communication between the discovery server and client when a firewall separates the two

By default, communications between discovery clients and the discovery server occur through an unspecified range of ports that are allocated dynamically. You cannot configure the discovery server to use a specific port or port range. However, if a firewall resides between the discovery client and the server, you can use the Discovery Gatekeeper server installation package that contains the Gatekeeper server software from Borland Corporation. The Gatekeeper server software enables clients to communicate across a firewall with the discovery server through a specified port.

Draft


CMDB Connection Settings wizard

CMDB Connection Settings wizard

If you do not configure a connection between the discovery server and BMC Atrium CMDB while installing the product or if you want to modify the configuration to add a CDM extension or change the CMDB host, you can use the CMDB Connection Settings wizard. To access the CMDB Connection Settings wizard, choose Administration => Configure CMDB Connection and Extension Deployment.

Discovery report for computer systems

To list the computer systems that were found by a discovery task, you can run the discovery report for computer systems. This report shows the discovery types and methods that were used to discover the computer systems and any error or warning messages that were generated for the discovery task. You can also export the discovery report, and you can filter it and export the filtered version.

Synchronization error report

When a CMDB synchronization task completes with errors, you can run the synchronization error report to view the individual CIs and relationships that generated the error messages during the CMDB synchronization task processing. You can add the CIs and relationships to a view, print the report, or export the report to different file formats.

Discovery filters

You can use discovery filters to exclude specific CIs from the discovery datastore. The discovery filters are applied to the results of the discovery tasks and the corresponding CIs are not added to the discovery datastore. You can set up new filters or modify the preprogrammed discovery filters. If you add or modify discovery filters, you can also return to the default settings.

Draft


Synchronization filters

Synchronization filters

When you set up a synchronization task, you can add or remove exclusion filters to control which CIs are synchronized with BMC Atrium CMDB. The BMC Foundation Discovery and BMC Topology Discovery products include preprogrammed filters that do not synchronize certain CIs with BMC Atrium CMDB. You can edit these filters to add or remove attribute criteria, or delete the filters if you want to include those CIs in CMDB synchronization.

Repository Legend / Filter pane

You can use the new Repository Legend / Filter pane to highlight CIs by repository in a map. The repositories are the discovery datastore, the BMC Topology Import dataset, and the BMC Asset dataset. If you select a box next to the repository name, all the CIs in the map that are stored in the selected repository are highlighted in the color assigned to that repository. You can change the default color that is assigned to each repository.

CI Lifecycle option

You can use the Show CI Lifecycle option for a CI in a map to view the following information:

■ The date that the selected CI was created in each of the repositories, if it is present in that repository. The repositories are the discovery datastore, the BMC Topology Import dataset, and the BMC Asset dataset.

■ The date that the CI was last updated in each of the repositories, if it is present in that repository.

■ The date of the last synchronization task that included the CI and the status of that task.

Viewing the synchronization results

After a synchronization task completes, you can create a view of the BMC Topology Import dataset to validate that the discovered CIs and relationships were successfully populated in BMC Atrium CMDB. To compare configuration data between the BMC Topology Import dataset and the discovery datastore, create a view of both the

Draft


Storage area network discovery

repositories. To add the CIs from the BMC Topology Import or BMC Asset dataset to a map, you can use the Query menu or the Add to View Related Instances In or Navigation option from the CI contextual menu. You can also select a CI and view how its attributes differ between repositories.

Storage area network discovery

The following changes have been made to the storage area network (SAN) discovery.

SMIS method for the storage area network discovery

You can discover a storage area network (SAN) using the SMIS method. This method uses the Storage Management Initiative Specification (SMIS) to collect information about SAN switches, host bus adapters (HBAs), and storage devices that are compliant with SMIS version 1.1. However, the storage area network discovery type supports only those SMIS-compliant devices that have passed the Storage Network Industry Association Conformance Testing Program (SNIA CTP).

New storage area network CIs

The following storage area network CIs are discovered by the SMIS method:

■ Server - the server that contains the HBA cards

■ HBA Card - the fibre channel interface card that connects a server to a storage area network

■ Virtual Disk - the virtual disk that is hosted by a disk array

■ Changer Device - the robotic arm of a tape library that is used to load and unload tape

New storage inventory queries

The following storage inventory queries have been added:

■ Disk Array Device by Name■ Servers with HBA Cards by Name■ Switch Device by Name■ Tape Library Device by Name

Draft


Virtual systems inventory discovery

Virtual systems inventory discovery

The following changes have been made to virtual systems inventory discovery.

UNIX virtual systems discovery

You can discover UNIX virtual systems by using the following virtual systems discovery types:

■ Zones for Solaris - Use this discovery type to discover the zones that are created on a Sun™ Solaris™ server.

■ LPar for AIX - Use this discovery type to discover the logical partitions (LPARs) on an IBM® AIX® server, and the Hardware Management Console (HMC) that manages these LPARs.

The Zones for Solaris and LPar for AIX discovery types use the SSH and Telnet methods to collect information about the UNIX virtual systems.

Support for ESX Server 3.x and Virtual Center 2.0

The VMWare VirtualCenter method now supports the VMware ESX server 3.x and VirtualCenter 2.0 releases.

Key-based SSH authentication for UNIX asset inventory discovery

You can set up key-based SSH authentication for the UNIX asset inventory discovery to secure the communication between the discovery server and the remote UNIX host. If you configure and enable key-based SSH authentication, the discovery server uses the user name that you specify in the discovery wizard and a passphrase file to connect to the remote UNIX hosts. The passphrase file comprises the private key and the passphrase in an encrypted format, and the private key file path.

Draft


Universal Application Discovery

Universal Application Discovery

The following changes have been made to Universal Application Discovery (UAD).

Template processing phase

The Template processing phase has been added to the existing UAD task processing phases. This phase is launched just before the discovered CIs and relationships are inserted in the datastore. It retrieves the settings information about computer systems, operating systems, or applications using Settings templates. The Settings templates are XML files that define what CIs are created or enriched, as well as the specific attributes that are populated.

Process list

You now manage processes using the process list instead of the application list. You can use the process list to add or delete a process, modify or duplicate a predefined or user-defined process, or reset a process to its original settings. Any change that you make to a predefined or user-defined process is applied to all the applications with which that process is associated.

Updated process properties

A process is now uniquely identified by a combination of the name or pattern, keyword, and size properties. When the name of a process is common to many applications, such as java.exe, you can add that process name more than once in the process list and distinguish each process by the size or keyword property.

Updated icon for the non-qualified application system CI

The icon for the non-qualified application system CI has changed to .

NOTE The BMC Topology Discovery documentation mentions that the Tuner method can be used to run a UAD discovery task. However, the Tuner method is not supported in the BMC Topology Discovery 1.5.00 CA release.

Draft


Synchronizing discovery data from multiple discovery servers with a single BMC Atrium CMDB

Synchronizing discovery data from multiple discovery servers with a single BMC Atrium CMDB

You can synchronize the discovery data from multiple discovery servers with a single BMC Atrium CMDB. The BMC Topology Import Multiple Identification, Merge and Purge reconciliation job handles the reconciliation when several discovery servers synchronize with the same BMC Atrium CMDB.

Inventory discovery task processing phase

The Explore and Scan discovery task processing phases have been merged into the inventory phase. The inventory phase

■ locates a data source on the IT systems that you want to explore (such as SNMP agents, JMX™ agents, or WMI-enabled hosts)

■ identifies the data source (such as a Cisco device or Catalyst 2900 switch)

■ packages the preceding information with the processing parameters that you specify in the discovery task

■ uses the packages to explore the IT systems

■ returns instances of the CIs that were discovered

Data model documentation

The class and attribute descriptions for all the CDM extensions have been updated. The updated descriptions are available in the BMC Atrium CMDB class manager and in the generated HTML data model documentation.

You can also review architectural diagrams for the following CDM extensions:

■ Network■ Advanced Network■ J2EE■ SAP®

■ Siebel■ SAN■ VMWare■ UNIX Virtualization■ Web Services

Draft


Combining discovery domains

For more information about each extension, see the BMC Foundation Discovery and BMC Topology Discovery 1.5 CDM Extension Diagrams.

Combining discovery domains

You can combine two existing discovery domains and apply the changes to one of the selected discovery domains, any other existing discovery domain, or a new discovery domain. When combining the discovery domains, you can choose to

■ keep all network identifiers from both discovery domains

■ keep only the network identifiers that are contained in both discovery domains

■ subtract the network identifiers of one discovery domain from the other discovery domain

What’s changedThese topics describe what has changed in this product release.

Product download method

BMC Foundation Discovery and BMC Topology Discovery 1.5.00 is an EPD-only release. For information about the product files and documentation that you need to download, see BMC Foundation Discovery 1.5.00 Read This First or BMC Topology Discovery 1.5.00 Read This First.

Product documentation

The BMC Foundation Discovery and BMC Topology Discovery documentation now includes information that helps you to plan the installation of the discovery server. The information about using the product and synchronizing data with the BMC Atrium CMDB has also been restructured.

The BMC Foundation Discovery and BMC Topology Discovery 1.5.00 product documentation includes the following books:

■ BMC Foundation Discovery and BMC Topology Discovery: Planning and Installation

Draft


Siebel, SAP, J2EE, and web services discovery types

■ BMC Foundation Discovery and BMC Topology Discovery: Discovering and Managing Configuration Data

■ BMC Foundation Discovery and BMC Topology Discovery: Populating BMC Atrium CMDB

Siebel, SAP, J2EE, and web services discovery types

The web services inventory discovery type and the Siebel, SAP, and J2EE enterprise application discovery types are part of BMC Topology Discovery and do not require a separate installation process.

Discovery data model

The discovery data model has been updated to align with the Common Data Model (CDM) version 2.1 and to improve reconciliation of CIs and relationships in the BMC Atrium CMDB.

Updated discovery task messages

The discovery task messages for all the discovery types have been updated to reflect the new inventory discovery task processing phase. For more information about the inventory phase, see “Inventory discovery task processing phase” on page 18.

Updated synchronization task messages

The synchronization task messages, which you might receive when you monitor a CMDB synchronization task, have been updated. When a computer system and its components are exported in a single page, a message indicating the computer system name is displayed. Similarly, when a Siebel, J2EE, or SAP application for which all the discovered components are grouped in a single page is exported, a message indicating the application name is displayed.

Draft


Updated BMC Atrium CMDB Reconciliation Engine jobs, identification activities, and merge activities

Updated BMC Atrium CMDB Reconciliation Engine jobs, identification activities, and merge activities

The BMC Atrium CMDB Reconciliation Engine jobs, identification activities, and merge activities included with BMC Foundation Discovery and BMC Topology Discovery have been modified.

■ The identification rules that identified server and workstation CIs that did not have qualified TokenID values have been simplified. Preprogrammed synchronization filters have been added that exclude unqualified or partially qualified BMC_ComputerSystem CIs from synchronization. For more information, see “Discovery reconciliation process definition” and “Managing filters that exclude CIs from CMDB synchronization” in the BMC Foundation Discovery and BMC Topology Discovery: Populating BMC Atrium CMDB guide.

■ The merge precedence groups have changed. For more information, see “Merge precedence” in the BMC Foundation Discovery and BMC Topology Discovery: Populating BMC Atrium CMDB guide

■ The BMC Topology Import Multiple - Identification Merge and Purge rule has been added to reconcile instances from multiple discovery servers to a single BMC Atrium CMDB. For more information, see “Discovery reconciliation process definition” in the BMC Foundation Discovery and BMC Topology Discovery: Populating BMC Atrium CMDB guide.

Host inventory discovery

The following changes have been made to host inventory discovery:

■ The Ping method for the host inventory discovery type has been removed. You can select only the TCP Port Scan method to run a host inventory discovery task.

■ You can update the default TCP ports that are scanned for the TCP Ports discovery type.

SAP enterprise application discovery

The following improvements have been made to SAP enterprise application discovery:

■ SAP enterprise application discovery now supports SAP Java™ Connector (SAP JCo) version 2.1.8.

Draft


Enhanced Windows asset inventory discovery

■ The BMC_Cluster class is created even if there is only one SAP application server in an SAP system. This class contains all the SAP application servers within an SAP system and is used to propagate an impact relationship from each SAP application server to the SAP system. The BMC_Cluster class can be added to the map view through Dynamic Navigation only after you have generated the impact relationships for the SAP discovery.

■ The impact relationships that are generated for the SAP enterprise application discovery have been updated.

Enhanced Windows asset inventory discovery

The following improvements have been made to Windows asset inventory discovery:

■ You can configure the authentication for the WMI method by selecting either NTLM or Kerberos authentication. The NTLM authentication encrypts only the communication, and the Kerberos authentication encrypts both the authentication and communication.

■ You can select the Computer discovery type when creating a Windows asset inventory discovery task. The Computer discovery type retrieves information such as the operating system, host name, and IP endpoint for the computer systems in the discovery scope. This discovery type does not retrieve information about the hardware, patches, and the installed products for the discovered computer systems.

■ If a BMC Configuration Management tuner is found on a computer system, the Windows asset inventory discovery task retrieves information only about the IP endpoint, MAC address, and operating system and not about the hardware, patches, and installed products.

■ You can create a WMI-enabled non-administrator account to run the Windows asset inventory discovery task.

■ You can customize Windows asset inventory discovery to

— retrieve serial numbers from target Windows systems if that information is not being retrieved as expected

— ignore computer systems with the workstation capability while running the discovery task

Draft


Enhanced UNIX asset inventory discovery

Enhanced UNIX asset inventory discovery

The following improvements have been made to UNIX asset inventory discovery:

■ You can select the Computer discovery type when creating a UNIX asset inventory discovery task. The Computer discovery type retrieves information such as the operating system, host name, and IP endpoint for the computer systems in the discovery scope. This discovery type does not retrieve information about the hardware and the installed products for the discovered computer systems.

■ If a BMC Configuration Management tuner is found on a computer system, the UNIX asset inventory discovery task retrieves information only about the IP endpoint, MAC address, and operating system and not about the hardware and installed products.

Enhanced network topology resolution

You can customize the scope of the network topology resolution by choosing one of the following options in the discovery wizard:

■ (default) Infrastructure Devices Only (Routers, Switches)

This option restricts the scope of the network topology resolution to infrastructure devices only, such as routers and switches.

■ Infrastructure Devices and Servers Hosting a SNMP Agent

This option extends the scope of the network topology resolution to include infrastructure devices and computers that host SNMP agents.

■ Try All Above and all Other Computer Systems

This option extends the scope of the network topology resolution to include infrastructure devices, computers that host SNMP agents, and other unknown or unclassified computers.

Removed aliases for CIs

In BMC Foundation Discovery and BMC Topology Discovery 1.5.00, you cannot add aliases to the datastore. Aliases were used in version 1.4.00 to manage duplicate CIs in the datastore. An alias was a unique identifier that was assigned to one instance of a CI and referenced from the second instance.

Draft


Reconciling the topology import dataset with the asset dataset

In BMC Foundation Discovery and BMC Topology Discovery 1.5.00, when a CI is generated by a discovery task, the application verifies that the CI has not already been discovered by a different task before adding it to the datastore. It accomplishes this by searching for existing CIs that have the same name, such as IP address, MAC address, or host name. In some instances, however, the same CI might be discovered under two different names. For example, one instance is found with an IP address using the TCP portscan method, and another instance is found with a host name using the WMI method. Additional rules are executed in the last phase of the discovery task to identify matching CIs using additional criteria beyond a simple name match before adding them to the datastore.

Reconciling the topology import dataset with the asset dataset

If a CI is deleted from the discovery datastore and then rediscovered before the next synchronization and reconciliation tasks are run, the CI is marked as deleted in the BMC Asset dataset after reconciliation. Run the reconciliation job again to reconcile the CI so that it is no longer marked as deleted.

For more information about reconciling the topology import dataset with the asset dataset, see the BMC Foundation Discovery and BMC Topology Discovery: Populating BMC Atrium CMDB guide.

Open issues and resolutionsThis section describes issues that remain open in this release. The table lists the tracking ID if one has been assigned to the issue.

Tracking ID Issue

SW00283609 You might get a timeout error when you run a Windows asset inventory discovery task.

Workaround: Make sure that multiple long-range discovery tasks are not running simultaneously and then re-run the Windows asset inventory discovery task. Also, make sure that the hardware specifications of the discovery server are compatible with the recommended discovery server requirements. For more information about the system requirements, see “Discovery server hardware and software requirements” on page 5.

SW00283533 If BMC Topology Discovery is synchronizing data with BMC Atrium CMDB and the replication service log is large, an Out of Memory error is displayed.

Workaround: To workaround this error, see “Updating the BMC Topology Discovery configuration file to avoid an Out of Memory error” on page 26.

Draft


Open issues and resolutions

SW00231158SW00280190SW00281445

A weak-relationship CI cannot be created if the CI is already associated to another lead CI that was previously soft-deleted.

For example, you might have a one-to-many relationship between computers and switches, defined such that one computer can be connected to only one switch, and one switch can be connected to several computers.

BMC Foundation Discovery discovers computer A connected to switch A, and creates corresponding CIs in BMC Atrium CMDB. At a later time, the user of computer A moves to an other room and connects to switch B. The initial relationship is soft-deleted, and a new relationship is created. The new relationship fails because of the cardinality constraint that demands that a computer can be connected to only one switch.

The verification process does not consider the soft-deleted relationship to be deleted, and believes that computer A is trying to connect to two different switches.

Workaround: If, during synchronization, you encounter a "cardinality" error message, restart the reconciliation job at the BMC Atrium CMDB level. The reconciliation purges soft-deleted CIs and allows the synchronization to be restarted. Apply this workaround each time you encounter this problem.

SW00263698 When BMC Topology Discovery exports a CI in BMC Atrium CMDB and that CI is propagated to the BMC Asset dataset after reconciliation and then used by BMC Service Impact Manager in a service model, any updates to the CI that are exported by BMC Topology Discovery to BMC Atrium CMDB are not propagated to the BMC Asset dataset after reconciliation.

SW00283269 The UAD discovery is not able to identify the HP True64 UNIX operating system exploration package sequence.

SW00282586 The UAD discovery might be deadlocked when several discoveries are running simultaneously.

SW00283758 The CMDB synchronization might randomly get deadlocked. To resolve the deadlock, you have to restart the discovery server.

SW00283634 The Query Recorder feature is not working.

SW00274580 BMC Topology Discovery does not correctly populate the ShortDescription attribute of the BMC_ComputerSystem class. Instead of including only the host name, the ShortDescription attribute includes the host name and the domain name.

SW00281446 For the Windows operating systems, BMC Topology Discovery does not correctly normalize the ShortDescription attribute of the BMC_Processor class.

SW00282204 If the BMC Atrium CMDB or the BMC Remedy Action Request System (BMC Remedy AR System) server reboots while BMC Topology Discovery is synchronizing data, BMC Topology Discovery does not automatically continue the synchronization after the BMC Atrium CMDB or BMC Remedy AR System server is available again.

SW00282840 A non-directed relationship between an Oracle Listener and the BMC Topology Discovery server cannot be qualified.

Tracking ID Issue

Draft


Updating the BMC Topology Discovery configuration file to avoid an Out of Memory error

Updating the BMC Topology Discovery configuration file to avoid an Out of Memory error

1 Open Windows Services and stop the BMCDiscovery service.

2 Open the TD_Home\ config\instances\domain\perform\host\manager\vm\manager\service\replication_service\replication_log\config.xml file in a text editor.

3 Navigate to the following line in the config.xml file:

4 In the line that you located in step 3, change Value="100000" to Value="10000".

5 Save and close the config.xml file.

6 Open the TD_Home\ config\instances\domain\perform\host\manager\vm\manager\service\cmdb_service\service_cmdb_log\config.xml file in a text editor.

7 Repeat step 3 and step 4.

SW00283158 When there are a large number of CIs in a view and you change the column sets, the BMC Topology Discovery client displays an Out of Memory error and you are logged off the discovery server.

SW00282209 The impact relationships between computer systems discovered by the Siebel discovery and the servers hosted on those computer systems are not being generated.

SW00282475 The Siebel enterprise application discovery is incorrectly reconciling Siebel Components.

SW00282477 If a user with admin rights (other than sadmin) runs a Siebel discovery, the Siebel applications are not discovered.

SW00282478 If you run a Siebel 7.5 discovery, all the Siebel components and component groups are not discovered.

SW00282479 If you run a Siebel 7.5 discovery, the label for a few Siebel components and component groups is displayed as “n/a”.

SW00282748 The CIs discovered by Siebel discovery and UAD discovery are not reconciled correctly.

SW00282841 If you select the Topology -> All Discoveries -> Listen Port and IP Address by Software query and select a Siebel discovery task in the Query Listen Port and IP Address by Software window, you get an empty result even if the CIs have been discovered.

<Property Name="CIRCULAR_SIZE" Value="100000" Type="string"></Property>

Tracking ID Issue

Draft


Corrected problems

8 Save and close the config.xml file.

9 Restart the BMCDiscovery service.

Corrected problemsThe following problems were reported in earlier releases of BMC Foundation Discovery and BMC Topology Discovery and have been corrected in this release:

Tracking ID Description

None The port.exe utility failed on systems running Windows 2000 SP4 with the error message Cannot access GetExtendedTCPTable in iphlpapi.dll.

QM001510283 The Impact Relationships By Application query produced incorrect results.

QM001512305 The Impact Relationships By Application Server query produced incorrect results.

QM001525837 For Windows asset inventory discovery using the WMI method, the rules that you can define for retrieving serial numbers from target Windows systems, if that information is not being retrieved as expected, have been enhanced. The alternate serial number can now be kept in a Windows Management Instrumentation (WMI) class, the registry, or the config file. For more information, see the BMC Foundation Discovery and BMC Topology Discovery: Discovering and Managing Configuration Data guide.

QM001526834 SAP discovery failed if the central instance application server was not at the first place in the scope.

QM001527313 Kerberos encryption has been added for the WMI protocol during the asset inventory discovery. For information on setting Kerberos encryption, see the BMC Foundation Discovery and BMC Topology Discovery: Discovering and Managing Configuration Data guide.

QM001528646 The NameFormat attribute for J2EE applications has a maximum length of 80 characters. If the value of NameFormat was longer than this, BMC Atrium CMDB truncated the value to the 80-character limit.

The format of the NameFormat attribute is now shorter than the 80-character limit in the following J2EE classes:

■ BMC_J2EEAdminDomain■ BMC_J2EECluster■ BMC_J2EEApplicationServer■ BMC_J2EEApplication

QM001529944 Export ran out of memory while processing associated updates.

QM001530113 The ProcessorArchitecture attribute was not populated for the x64 type processor.

QM001531709 After running a successful discovery on a J2EE hosting system, any J2EE clusters that were detected did not appear after creating the default view.

Draft


Corrected problems

QM001533284 BMC Topology Discovery showed the wrong disk drive capacity on HP-UX.

QM001533285 On all supported UNIX platforms, BMC Topology Discovery showed the total physical memory size incorrectly.

ISS03100015 The operating system type of UNIX operating systems discovered by asset inventory discovery was stored in the ShortDescription attribute, which was not visible in BMC Remedy Asset Management after CMDB synchronization. The operating system type is now stored in the OSType attribute of the BMC_OperatingSystem class. This field is visible in BMC Remedy Asset Management.

None BMC Configuration Management agent inventory discovery tasks would never complete when attempting to discover version 6.0.2.1 agents. A time out has been added for BMC Configuration Management agent inventory discovery tasks.

You can change the length of the time-out interval by editing the TimeOut property in the TD_HOME/etc/action_util/rpccd/config.prop file, where TD_HOME is the discovery application server installation directory. The time-out interval is measured in milliseconds.

None When you completed a Web Server inventory discovery, if the Use NMap (Port Scanning) option was not selected when configuring the HTTP method, the task would discover a web server at the specified port even if no web server was present.

QM001510569 BMC Topology Discovery did not correctly reconcile Web Server CIs discovered by Siebel application discovery tasks with Web Server CIs discovered by Universal Application Discovery tasks. This caused duplicate CIs in the discovery datastore.

QM001516538 For host discovery, the HP-UX computers were not discovered with a valid operating system value.

ISS03037856 BMC Topology Discovery could not resolve the memory for the IBM AIX operating system.

ISS03041309 The correct version for the Linux operating system was not identified.

ISS03070825 The Oracle 10g database was not discovered by BMC Topology Discovery. Now, if the Oracle 10g Listener has a password, the DataBaseServer, SoftwareServer, and Database CIs are created. If the Listener does not have a password, only the DataBaseServer and SoftwareServer CIs are created.

None If multiple UAD tasks were launched simultaneously, an error occurred when inserting the CIs into the discovery datastore.

None The discovery client did not free the memory when the views were closed.

None The SAP Java Connector component failed sometimes because of missing DLLs on the Windows operating system.

None The serial numbers for printers were not displayed.

None The UAD module did not discover the Windows 64-bit operating system.

None The VersionNumber attribute within the BMC_OperatingSystem class was not populated in BMC Atrium CMDB.

None The WebLogic J2EE servers for which the listen address was not configured were not discovered.


Draft


Corrected problems

None The WebLogic J2EE servers without an associated computer were not discovered.

QM001510005 If you right-clicked on a Siebel application in a map and selected Add to View => Detailed, the Inbound port option was displayed twice.

QM001510021 If you right-clicked on a Siebel application in a map and selected Add to View, the Hosting computer option was displayed twice.

QM001513895 BMC Topology Discovery did not populate a few Mainframe discovery CI properties. Now the Manufacturer property is populated for the Sysplex CI and the Model property is populated for the BMC_Sysplex and BMC_OperatingSystem CIs.

QM001514242 When BMC Atrium CMDB was extended, the class ID assigned to the ADV_Network:BMC_LMISERVICE and the J2EE:BMC_J2EEADMINDOMAIN classes was incorrect.

CAS01390207 Some disk drives discovered on Sun Solaris computer systems had a negative value for disk size. The negative value caused BMC Atrium CMDB synchronization to fail for those CIs.

QM000541451 Serial numbers of IBM computers were not being exported to the BMC.IMPORT.TOPO dataset correctly. The serial number for IBM computer systems was taken from the system enclosure instead of the BIOS, which caused multiple IBM computer systems to be discovered with the same serial number. Now both the system enclosure serial number and the BIOS serial number are discovered and stored as separate attributes.

QM001510846 When the Telnet only parameter was selected for UNIX asset inventory discovery, the discovery task failed to discover computer systems running the IBM AIX operating system.

QM001510849 An error message that could be generated by UNIX asset inventory discovery displayed login credentials in plain text in the task monitor and the log file.

QM001510850 WMI asset inventory discovery did not support discovery of operating systems in languages other than English.

QM001510851 When you sorted a table view by a column that contained a date, the table did not sort correctly.

QM001510852 The values in the Processor.Family attribute were not correct for Pentium 4 and Intel Xeon processors.

SW00254053 UAD did not work correctly for UNIX computer systems. The communication settings between servers were incorrect.

SW00254054 If you had a large number of scheduled discovery tasks, the client stopped responding when you opened the task scheduler due to an Out of Memory error.

SW00254056 The BMC_Product.versionNumber attribute was not synchronized during BMC Atrium CMDB synchronization.


Draft


Support for BMC Foundation Discovery and BMC Topology Discovery

Support for BMC Foundation Discovery and BMC Topology Discovery

This section provides information about

■ BMC support for BMC Foundation Discovery and BMC Topology Discovery■ documents that support the product■ how to obtain the latest information about the product■ how to obtain the product■ how to contact Customer Support

Levels of support

BMC supports the following product versions and releases:

For more information about the latest support policies, see the Customer Support website at http://www.bmc.com/support_home.

Product name and version Level of support

BMC Foundation Discovery 1.5.00 full

BMC Topology Discovery 1.5.00 full

BMC Foundation Discovery 1.4.00 full

BMC Topology Discovery 1.4.00 full

BMC Foundation Discovery 1.3.00 limited

BMC Topology Discovery 1.3.00 limitedDraft



Product documents

Product documents

The following documents support the product:

■ BMC Foundation Discovery and BMC Topology Discovery: Planning and Installation ■ BMC Foundation Discovery and BMC Topology Discovery: Discovering and Managing

Configuration Data■ BMC Foundation Discovery and BMC Topology Discovery: Populating BMC Atrium

CMDB■ BMC Foundation Discovery and BMC Topology Discovery 1.5 CDM Extension Diagrams■ BMC Discovery for z/OS Installation and User Guide■ BMC Discovery Solution 2.0.01 Planning and Implementation Guide ■ BMC Discovery Solution 2.0.01 Installation and Tuning Guide■ BMC Atrium CMDB 2.1.00 Installation and Configuration Guide■ BMC Atrium CMDB 2.1.00 User’s Guide■ BMC Atrium CMDB 2.0.01 Installation and Configuration Guide■ BMC Atrium CMDB 2.0.01 User’s Guide■ BSM Interoperability 2.6.1 Installation and Configuration Guide■ BSM Interoperability 2.6.1 Installation Overview

Where to view the latest product information

The latest product information is available on the Customer Support website at http://www.bmc.com/support_home.

From the Customer Support site, you can perform several tasks, including

■ viewing the latest product documentation (manuals, release notes, flashes, technical bulletins, online Help, and parameter information)

■ subscribing to proactive alerts to receive e-mail messages that inform you of new release notes, flashes, and technical bulletins for your products

■ searching for existing product resolutions and frequently asked questions (FAQs)

TIP If you do not already have a user name and password that allow you to fully access the Customer Support site, you can register for a user name and password on the site.

Draft



How to obtain the product

How to obtain the product

BMC Foundation Discovery and BMC Topology Discovery is available from the BMC Electronic Product Distribution (EPD) website at http://webapps.bmc.com/epd. You can obtain the product in the following ways:

■ To download the product or to upgrade to the latest version, download it from the EPD site. Use the user name and password that your BMC sales representative gave you.

■ If you do not have a current license for the product or if you cannot download the product and require a kit, contact a BMC sales representative by calling 800 793 4262.

Customer support

If you have problems with or questions about a BMC product, see the Customer Support website at http://www.bmc.com/support_home. You can view or download product documents, find answers to frequently asked questions, and download products and maintenance. If you do not have access to the web and you are in the United States or Canada, contact Customer Support at 800 537 1813. Outside the United States or Canada, contact your local BMC office or agent.

© Copyright 2008 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.

AIX, IBM, and z/OS are trademarks or registered trademark of International Business Machines Corporation in the United States, other countries, or both.

Linux is the registered trademark of Linus Torvalds.

Oracle is a registered trademark of Oracle Corporation.

SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries.

Solaris, Java, JMX, J2EE. and Sun are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries.

UNIX is the registered trademark of The Open Group in the US and other countries.

BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices in the product documentation.

BMC SOFTWARE INC2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA• 713 918 8800Customer Support: 800 537 1813 (United States and Canada) or contact your local support center

Draft



http://webapps.bmc.com/epd

bmc foundation discovery and bmc topology discovery · pdf filebmc foundation discovery and...

Documents