Setting up the CMDB synchronization connection

The CMDB Sync page enables you to configure a synchronization from BMC Atrium Discovery to BMC Atrium CMDB.

Before you can synchronize BMC Atrium CMDB with BMC Atrium Discovery, you must prepare the CMDB.

To set up CMDB synchronization

  1. From the Model section of the Administration page, click CMDB Sync. If no CMDB Sync has been configured, a banner displays stating that the appliance has not been set up for CMDB Sync.
    This screen illustrates a banner indicating that the appliance has not been set up for CMDB synchronization.
  2. Click the Configuration tab to configure a default export to your Atrium server.
  3. Click Edit to change settings on the Configuration page.
  4. Type the following information on the CMDB Sync page:

    Field

    Description

    Atrium CMDB Server

    The hostname or IP address of the BMC Atrium CMDB host.
    (info) If BMC Atrium CMDB is installed with an AR System server group, you must enter the following based on the high availability status of the server group:

    • (If high availability is configured) The host name or IP address of the load balancer.
    • (If high availability is not configured) The host name or IP address of the primary AR System Server.
      To learn about the AR System server groups configuration, see the corresponding documentation for versions 8.1, 8.0, 7.6.04, and
      7.5. To learn about the AR System server high availability configuration and hardware load balancer, see the corresponding documentation for versions 8.1, 8.0, 7.6.04, and 7.5.

    Specify TCP Port

    The communication port. BMC Atrium CMDB typically uses a portmapper service to automatically choose a suitable communication port. If this is not appropriate in your environment, you can configure the CMDB to listen on a specific port, and then specify that port in this field.

    Username

    The username of the BMC Atrium CMDB user that is at least a member of a group having the CMDB Data Change All role. If in doubt, create a dedicated discovery user with the same profile as the standard CMDB Demo user.
    (info) The CMDB Demo user permissions at least are required for multitenancy to work.
    Note that a user is not permitted to connect to BMC Atrium CMDB from a second IP address within 4 hours of their last activity at the first IP address. For a failover scenario, you could also create a second discovery user to connect from the failover appliance.

    Password

    The password of the CMDB user (or blank if the user has no password).

    Dataset ID

    The ID of the dataset used for Discovery data. The default is BMC.ADDM.

    Data model

    The data model for your CMDB. Different versions of the CMDB have different data models, so the data from BMC Atrium Discovery must be transformed differently according to the CMDB version.
    The preferred value for Data model is CMDB 7.6.03 and later.
    Choosing CMDB 7.6.03 and later (with impact relationships) option is only required if using BMC Service Impact Management version 7.4 or earlier and should be avoided otherwise.

    Do not use mixed modes with CMDB 7.6.03 and later (with impact relationships)

    If you specify the CMDB 7.6.03 and later (with impact relationships) option, CMDB synchronization creates Impact relationships as a relation (IaaR). Normalization in the CMDB using the default setting of auto impact creates Impact relationships as an attribute (IaaA).
    You must change your CMDB Normalization setting so that it does not use auto impact when the Data model is set to CMDB 7.6.03 and later (with impact relationships) in BMC Atrium Discovery. Do not use a mixed mode of (IaaA) and (IaaR).

    Choose the correct data model from the menu. If you choose an incorrect value, you might encounter errors during synchronization.

    Sync threads

    The default is one. CMDB synchronization can simultaneously process data from multiple control threads. Depending on the configuration of your CMDB and the characteristics of the network between BMC Atrium Discovery and the CMDB, the rate at which data is synchronized to the CMDB might be increased by choosing a non-default number of Sync threads. The number of Sync threads in BMC Atrium Discovery must be fewer than the number of Fast Threads defined in the CMDB, and fewer than the value of the Next-Id-Block-Size parameter in the CMDB. Increasing the number of Sync Threads should only be undertaken with the assistance of your AR and CMDB System Architects.
    Note: each root CI (Host, NetworkDevice, Printer, MFPart) is processed by a single thread. If you are processing several root CI's, multiple threads are used. However if you are processing a single root CI, only one thread is used, even if additional threads are configured.

    Multitenancy

    Multitenancy support. Selecting this check box enables you to choose a company name from the Default Company menu, which assigns that company name to a discovery run during an initial scan, and assigns that company name to the Company attribute to the CIs created in BMC Atrium CMDB. Once the CMDB Sync connection is established (after clicking Test Connection below), click Lookup Companies to populate the Companies list.
    (info) The CMDB Demo user permissions at least are required for Multitenancy to work.

  5. Click Apply.
  6. If necessary, click Edit to change configuration settings.
  7. Click Test Connection to test that BMC Atrium CMDB can be reached.
    You can now click Lookup Companies to populate the Companies list.
  8. Click Manage Blackout Windows to configure times at which no synchronization should occur with the CMDB. This is described in CMDB Sync blackout windows.

Status

Comprehensive status information is also available in the CMDB Sync page. Click the Status tab to display the status window.
The page displays a summary of the number of devices that are queued, which devices are currently processing, and those that have recently completed synchronization. If any errors occur during synchronization, error information is shown towards the bottom of the page.

The following table describes the fields in the Most recent synchronized devices section.

Field

Description

Time

The time at which the synchronization started.

Label

The device name.

Kind

The CMDB device kind.

Attributes written

The total number of attributes which have been written or updated on all nodes which belong to that particular device. Where the number of attributes written or updated is fewer than the possible total it means that not all attributes have been updated. A scenario in which this may occur is where a node is shared between two root nodes, such as an IPConnectivitySubnet node. The first time it is created, its attributes are set. When another root node that is also linked is created, the shared node's attributes are counted as candidates for writing or updating, but are already set so are not updated.

Configuration items

The number of configuration items considered, inserted, updated or deleted for this device. Where the number of CIs considered is greater than the number inserted, the number of attributes written (see Attributes written above) is fewer than the possible total.

Relationships

The number of relationships considered, inserted, updated or deleted for this device. Where the number of relationships considered is greater than the number inserted, the number of attributes written (see Attributes written above) is fewer than the possible total.

The status window automatically refreshes itself so it always shows up-to-date information.

Click Show all in the Devices that failed last CMDB sync field to show a list view of devices that failed to synchronize.

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

Comments

  1. Jesse Richardson

    It is worth mentioning that the preferred value of 'Data Model' is "7.6.03 or later" withOUT impact relationships, unless using BMC Service Impact Management version 7.4 or earlier. If not using a product version which requires this older IaaR format of impact relationships, the recommendation is to allow Atrium Normalization to create and manage the impact relationships using the newer IaaA format.

    Feb 21, 2012 02:44