This topic provides instructions for configuring synchronization from BMC Discovery to one or more instances of BMC Atrium CMDB.
Before you begin
Before you can synchronize from BMC Discovery to any instance of BMC Atrium CMDB, you must have prepared that CMDB.
CMDB synchronization and clusters
When configuring CMDB synchronization from a cluster, you can use any machine for the initial configuration and subsequent updates. All data synchronized to any connected BMC Atrium CMDB is sent from the coordinator.
Do not change the CMDB synchronization configuration at the same time as changing the cluster configuration.
- Changing the CMDB sync configuration means, adding connections, removing connections, and starting or stopping a resync.
- Changing the cluster configuration means adding members, removing members, moving the coordinator, or changing fault tolerance.
To configure a CMDB synchronization connection
From the main menu, click the Administration icon.
The Administration page displays.
From the Model section, click CMDB Sync.
If no CMDB Sync has been configured, a banner displays stating that the no CMDB Sync connections are configured.
Click Add CMDB Connection to configure the first connection to a BMC Atrium CMDB server.
If CMDB Sync connections exist, click Add CMDB Connection to configure another connection to a BMC Atrium CMDB server.
- Enter the following information on the Add CMDB Connection page:
Name The name of the CMDB Sync connection.
The BMC Atrium CMDB host. This can be specified as one of the following:
- Hostname or FQDN
- IPv4 or IPv6 address
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, and 7.6.04.
To learn about the AR System server high availability configuration and hardware load balancer, see the corresponding documentation for versions 8.1, 8.0, and 7.6.04.
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.
Specify RPC Queue
Specify a private RPC queue to use on BMC Atrium CMDB. Ensure that you have configured private queues on the CMDB before using this setting. See Configuring CMDB synchronization through a private queue for more information. The following queue numbers can be used:
- 390696 (the default, which is also used by the CMDB for various tasks)
- 390698 (used by Reconciliation)
- 390699 (used by Normalization)
The username of the BMC Atrium CMDB user that is at least a member of a group having the
CMDB Data Change Allrole. If in doubt, create a dedicated discovery user with the same profile as the standard CMDB Demo user.
The CMDB Demo user permissions at least are required for multitenancy to work.
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.
The password of the CMDB user (or blank if the user has no password).
Continuous Sync Select the checkbox to enable continuous sync for this CMDB connection.
During continuous CMDB synchronization, whenever BMC Discovery finishes scanning a device, it is added to the synchronization queue. Similarly, whenever a device node is removed due to aging, it is also queued for synchronization, meaning that the deletion is propagated into the CMDB. In this way, the CMDB stays completely synchronized with BMC Discovery.
Enables you to configure the batch size used for batch operations. If you experience timeouts during a batched operation, most likely during a resync, these may be prevented by setting it to a lower value. You can set the batch size to anything between 1 and 1000. The default is 100, which was the fixed batch size in previous releases.
Enables you to specify the number of workers used by the CMDB sync process. You can set the number of workers from 1 to 20. The default is 1.
The best practice is to start from the default and gradually increase the number up to when sync rate keeps up with discovery rate.
The ID of the dataset used for Discovery data. The default is
The data model for your CMDB. Different versions of the CMDB have different data models, so the data from BMC Discovery must be transformed differently according to the CMDB version.
The preferred value for Data Model is CMDB 7.6.03 and later (with impact attributes).
Choose the correct data model from the menu. If you choose an incorrect value, you might encounter errors during synchronization.
Data model value CMDB versions Effect
CMDB 7.6.03 and later (with impact attributes)
7.6.03 and later
HasImpact and ImpactDirection attributes are set as appropriate
CMDB 7.6.03 and later (no impact details)
7.6.03 and later
No impact details are set by ADDM. They may be set by Impact
Normalization in the CMDB
Multitenancy support. Selecting this check box enables you to choose a default company name from the dropdown list to assign to a discovery run during an initial scan. The list of companies is not populated until one connection has been successfully tested, or you click Get Companies (which also tests the connection).
This section is always displayed. However, if another connection exists, instead of the multitenancy configuration options, a message stating Configure multitenancy from the overview page is displayed along with a link to the CMDB Sync page.
Click Test Connection to verify that the Atrium CMDB server can be reached, and that the credentials are valid. Testing the connection also retrieves the list of companies from the CMDB.
Ensure that the connection is successful before proceeding.