Child pages
    • Important information for users of BMC Atrium CMDB
    Skip to end of metadata
    Go to start of metadata

    To integrate BMC Atrium Discovery with BMC Atrium CMDB, there are some prerequisites, known issues, and limitations that you must 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:

    Changed behavior in BMC Atrium Discovery 10.1 and later

    In previous releases and with TKU 2014-Nov-1 onwards installed, when BMC Atrium Discovery encountered NetApp devices, they were modeled using NetworkDevice nodes. The default CDM mappings allowed these to be synchronized to the CMDB. With the introduction of storage discovery, they are now modeled as StorageDevice nodes. The default CDM mappings only synchronize storage data when StorageSystem nodes exist, which are only produced by the Storage TKU.

    As a consequence, in BMC Atrium Discovery 10.1, NetApp devices are only synchronized to CMDB if the Storage TKU is installed.

    Prerequisites for CMDB synchronization

    Before you can synchronize data to a supported BMC Atrium CMDB version, you must complete the following required tasks in the given order:

    Integrating with earlier versions of BMC Atrium CMDB

    BMC Atrium CMDB versions earlier than 7.6.04 are no longer supported and are not recommended for use. Synchronizing data to these earlier versions required you to complete some additional tasks. For more information, see the BMC Atrium Discovery 8.3 documentation.

    1. Create the BMC.ADDM dataset: Manually create the BMC.ADDM dataset in the CMDB before attempting synchronization.
    2. Create the Job to merge the BMC.ADDM dataset with BMC.ASSET: Create the job to reconcile the BMC.ADDM dataset with the BMC.ASSET dataset.
    3. Check the BMC.ADDM dataset configuration: When using ITSM 7.0 with a backward compatibility patch, you must ensure that the BMC.ADDM dataset is trusted.

    After completing the preceding tasks, 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.3.00 and later, you should consider tuning the database which BMC Atrium CMDB (or BMC Remedy AR System) is using.

    Max-Entries-Per-Query parameter on BMC Remedy AR System server

    To prevent BMC Discovery generating duplicate CIs in the BMC.ADDM dataset when running a resynchronization, you must set the BMC Remedy AR System server parameter Max-Entries-Per-Query to at least 5000.

    For more information, see the following documentation corresponding to your product version:

    Co-existence with other data providers

    The following issues exist in the corresponding BMC product that can lead to duplicate CIs in the BMC Atrium CMDB ASSET dataset when reconciling with BMC Atrium Discovery:

    Fixes which are available as hot fixes will be rolled into future patches. BMC recommends you to see the latest patch release notes for the defect number to see if the hot fix is already included.

    BladeLogic

    The minimum product version recommended is BladeLogic Server Automation 8.0 SP2 with fixes for the following issues and defects.

    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 (for example: 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 its 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

    The minimum product version recommended is BMC Performance Manager Portal 2.7.00.040.

    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

    The minimum product version recommended is BMC BladeLogic Client Automation 8.1.01.

    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.

    • No labels

    2 Comments

    1.  

      1.