Important information for users of BMC Atrium CMDB

If you plan to use the integration between BMC Atrium Discovery 8.3 and Atrium CMDB, there are some pre-requisites and known issues and limitations that you need to be aware of.

Interaction of BMC Atrium Discovery with other BMC data providers

BMC Atrium Discovery can co-exist with other BMC data providers. To prevent any potential duplicated Configuration items (CIs) in the BMC Atrium CMDB Asset dataset, BMC recommends the following minimum product versions when using other data providers with BMC Atrium Discovery:

  • BMC Atrium CMDB currently supported versions (8.1, 8.0, 7.6.04, and 7.6.03): No patches required.
  • BMC Atrium CMDB 7.6: Recommended Patch 001 and Hot Fix for defect SW00355736.
  • BMC Atrium CMDB 7.5: Recommended Patch 004 and Hot Fix for defect SW00355736.
  • BMC BladeLogic Server Automation: Recommended BladeLogic Server Automation 8.0 SP2 and Hot fixes for SW00355142 and QM001646701. For details, see the BladeLogic section.
  • BMC Performance Manager (BPM) and BMC Performance Assurance (BPA): Recommended BMC Performance Manager Portal 2.7.00.040. For details, see the BPM/BPA section.
  • BMC BladeLogic Client Automation (BBCA): Recommended BMC BladeLogic Client Automation 8.1.01. Version 8.1.01 contains the fix of two known issues. For more details, see the BBCA section.

Prerequisites for CMDB synchronization

Before you can synchronize data to BMC Atrium CMDB, you must satisfy the following prerequisites:

  1. Extend the CMDB - In order to tightly integrate the two models, it is necessary to store a BMC Atrium Discovery-specific identifier on the corresponding BMC Classes in BMC Atrium CMDB. Additional mainframe-specific classes and relationships are required if you are discovering mainframe systems. The identifier and the mainframe classes and relationships are only present in the default CMDB data model after CMDB version 7.6.03. Versions prior to 7.6.03 require the ADDM Integration Extension and the mainframe discovery extensions.
  2. Create the BMC.ADDM dataset - the BMC.ADDM dataset must be manually created in the CMDB before a synchronization is attempted.
  3. Create the Job to merge the BMC.ADDM dataset with BMC.ASSET - After the BMC.ADDM dataset has been created, you must then create the job to reconcile it with the BMC.ASSET dataset.
  4. Check the BMC.ADDM dataset configuration - When using ITSM 7.0 with a backwards compatibility patch, you also need to ensure that the BMC.ADDM dataset is trusted.

In versions earlier than 7.6 Patch 001 and 7.5 Patch 004, you must modify the standard reconciliation rules before running the first reconciliation from BMC.ADDM to BMC.ASSET.

After you have performed these steps, you can start synchronizing BMC Atrium Discovery data to BMC Atrium CMDB.

Performance considerations

To obtain the maximum synchronization performance when using CMDB synchronization with BMC Atrium Discovery version 8.2.03 and later, you should consider tuning the database which BMC Atrium CMDB (or BMC Remedy AR System) is using. For more information, see the following documentation corresponding to your product version:

Supported previous versions of Discovery

New installations of BMC Atrium Discovery 8.3 are compatible with the following, previous versions of discovery products:

  • BMC Atrium Discovery: 7.5
  • BMC Foundation Discovery: 1.6 (upgrade to version 7.5)
  • BMC Topology Discovery: 1.6 (upgrade to version 7.5)
  • BMC Discovery for zOS: 1.6 (upgrade to version 7.5)

If you are migrating data from prior versions to version 8.3, you must ensure that you have upgraded any prior versions of your Discovery products to BMC Atrium Discovery 7.5.01.03. For more information on migrating your existing data to BMC Atrium CMDB, see Migrating from version 7.5 to 8.3.

Co-existence with other data providers

The following issues exist in other BMC Products that can lead to duplicate CIs in the Atrium CMDB ASSET dataset when reconciling with BMC Atrium Discovery.

All dates mentioned regarding future releases are subject to change. Fixes which are available as hot fixes will be rolled into future patches, so check the latest patch release notes for the defect number to see if the hot fix is already included.

  • BMC Atrium CMDB: Currently supported versions of BMC Atrium CMDB, which are 8.0, 7.6.04, and 7.6.03, are recommended. If you are on an earlier version, BMC Atrium CMDB 7.6 is recommended with Patch 001 and Hot Fix for defect SW00355736 and BMC Atrium CMDB 7.5 is recommended with Patch 004 and Hot Fix for defect SW00355736. See below for details.
  • BladeLogic: Recommended BladeLogic Server Automation 8.0 SP2 and Hot fixes for SW00355142 and QM001646701. See below for details.
  • BPM/BPA: Recommended BMC Performance Manager Portal 2.7.00.040. See below for details.
  • BBCA: Recommended BMC BladeLogic Client Automation 8.1.01. See below for details.

BMC Atrium CMDB

Issue

Description

Fix

SW00355736

The standard Atrium CMDB reconciliation rules for BMC_ComputerSystem do not cope with the situation when one tool gets the serial number and another does not, but where Hostname, Domain, isVirtual, Primary Capability match. In this situation duplicate BMC_ComputerSystem CIs will be created.

Download Hot Fix for defect SW00355736 (7.5 P4 Hotfix - available, 7.6 P1 Hotfix - available now)

SW00348852
SW00352573

The standard Atrium CMDB reconciliation rules for BMC_Application, BMC_SoftwareServer and BMC_ConnectivitySegment have fallback rule based only on the Type attribute. These rules should be based on Name. The impact of this is that duplicate BMC_Application, BMC_SoftwareServer and BMC_ConnectivitySegment CIs will be created during reconciliation with BMC Atrium Discovery.

Atrium 7.5 Patch 004
Atrium 7.6 Patch 001

BladeLogic

Issue

Description

Fix

SW00355356

Serial number is a strong indicator of identity for the BMC_ComputerSystem and is therefore used in reconciliation. On older Solaris Sparc platforms serial number is not available. BL would set the serial number to a value derived from hostid of the BMC_ComputerSystem class. In this situation duplicate BMC_ComputerSystem CIs would be created.

Contact BMC Customer Support requesting BladeLogic Server Automation 8.0 SP2

SW00355142

For Windows Hosts BladeLogic sets the Domain attribute for BMC_ComputerSystem to be the Windows Domain and not its DNS Domain. The Domain attribute forms a part of the TokenID for a BMC_ComputerSystem CI. In this situation duplicate BMC_ComputerSystem CIs will be created.

Contact BMC Customer Support requesting Hot Fix for defect SW00355142

SW00355359

isVirtual attribute incorrectly set to No for Physical system. In this situation duplicate BMC_ComputerSystem CIs will be created.

Contact BMC Customer Support requesting BladeLogic Server Automation 8.0 SP2

QM001646701

When executing the BL reconciliation job after the BMC Atrium Discovery reconciliation job the CIs associated with a merged BMC_ComputerSystem class ( e.g.: BMC_Processor and BMC_IPEndpoint) are not merged and result in duplicate CIs.

Contact BMC Customer Support requesting Hot Fix for defect QM001646701

QM001642175

Server name should be picked up from FQ_HOST instead of Host property on it's product. When a ComputerSystem is discovered by both BladeLogic and BMC Atrium Discovery this issue can result in the ComputerSystem not being reconciled when the case of the Hostname is not the same for the data from the two products.

Contact BMC Customer Support requesting BladeLogic Server Automation 8.0 SP2

BPM/BPA

Issue

Description

Fix

QM001609002

BPM has no concept of Virtual Hosts. Therefore when it sets TokenID for a BMC_ComputerSystem it uses the format defined for Physical Hosts. The reconciliation of this data with data from other providers that are aware of virtualization will fail if you reconcile the BPM data after another discovery provider. This will result in duplicate CIs.

BMC Performance Manager Portal 2.7.00.040

BBCA

Issue

Description

Fix

SW00355355

Serial number is a strong indicator of identity for the BMC_ComputerSystem and is therefore used in reconciliation. On older Solaris Sparc platforms serial number is not available. BBCA would set the serial number to a value derived from hostid of the BMC_ComputerSystem class. In this situation duplicate BMC_ComputerSystem CIs would be created.

Fixed in BMC BladeLogic Client Automation 8.1.01.

SW00355361

isVirtual attribute incorrectly set to No for Physical system. In this situation duplicate BMC_ComputerSystem CIs will be created.

Fixed in BMC BladeLogic Client Automation 8.1.01.

Was this page helpful? Yes No Submitting... Thank you

Comments