What are some best practices for managing or editing the data in the BMC.ADDM CMDB dataset? |
The BMC.ADDM dataset is managed by the BMC Discovery product. The only edits to the BMC.ADDM dataset should be made by BMC Discovery, Normalization, or Reconciliation. Occasionally the model stored in the CMDB dataset becomes out of step with the shadow copy for a CMDB connection and requires resynchronization. For example, if CMDB tools have been used to modify the dataset. In this case, when updates are written to non-existent nodes, instance errors are raised. When BMC Discovery registers these instance errors it attempts to fix them automatically, but sometimes a resynchronization is recommended.
Root node deletion synchronization failure
When a non-fatal error occurs during synchronization with the CMDB, the root node is re-queued so the synchronization is attempted again. A root node is re-queued up to three times if it fails repeatedly, then synchronization is not attempted again. When the outage is resolved, subsequent discovery runs trigger continuous synchronization and re-submit root node creations and updates. Deletions however are not automatically re-submitted, leading to orphaned graphs in CMDB dataset. Manual Workaround: When the network outage is resolved, perform a resynchronization to ensure the CMDB contents match the data in BMC Discovery. Alternatively, to synchronize a selection of the missed deletions, run the report “Aged-out Hosts and other devices that failed last CMDB sync”, found in Explore > Reports > BMC Discovery Deployment. Select one or more nodes from the list, and choose Actions > Sync to CMDB. " Here is a summary list of the recommendations:
1) Do not use cmdbdiag to edit BMC.ADDM 2) Do not manually modify CIs in BMC.ADDM 3) The only edits to the BMC.ADDM dataset should be made by BMC Discovery, Normalization, and Reconciliation. 4) If "orphaned" CIs are a concern, take one or more of the following actions: a) Ignore them. b) From the Discovery UI, choose: Explore->Reports->Aged-out Hosts and other devices that failed last CMDB sync If there are results, Select All, and Actions->Sync to CMDB Next, choose the Hosts and other devices that failed last CMDB sync report If there are results, Select All, and Actions->Sync to CMDB c) A resync could be performed. Keep in mind that this action can take a very long time, and that in many cases the orphan CIs will be resolved in the course of normal sync processing. 5) If there seems to be a large amount of incorrect data in the BMC.ADDM dataset, one of the following actions can be taken: a) raise a BMC Discovery support ticket, and/or b) run a resync from the Discovery UI 6) If the data seems incorrect for a few Hosts or Devices, the following actions can be performed: a) First, try another "sync" from the Discovery UI. Find the Host or Device, then click "Actions->CMDB Sync" b) If that does not help, then: Destroy the Host or Device from the Discovery UI This action marks as deleted all related CI's in BMC.ADDM c) Next, re-discover the Host or Device from BMC Discovery (with Continuous Sync enabled, or if not enabled, then manually sync the Host/Device after the re-scan) This action re-scans and then re-sync's the data to BMC.ADDM. |