ADDM:  What happens in the CMDB when the identity of a host changes?

Version 2
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Discovery


    COMPONENT:

    BMC Atrium Discovery and Dependency Mapping


    APPLIES TO:

    BMC Atrium Discovery and Dependency Mapping



    QUESTION:

    When a new scan result is significantly different from the previous one, ADDM may create a new host (see "Endpoint identity" in  https://docs.bmc.com/docs/display/DISCO110/Host+node)

    What happens in the CMDB in this case?


    ANSWER:

     

    Legacy ID:KA387418

      

    When the identification of a Host changes, the attributes below appear in the Host page:
    "Endpoint Used To Be Identified As"
    "Endpoint Now Identified As"

      

    A new CI will be created in BMC.ADDM by synchronization.

      

    In certain cases, this new CI will not match the existing CI in BMC.ASSET. At the end of the reconciliation process, the existing CI in BMC.ASSET will be replaced with a new one. This depends on the RE identification rule and the type of change between the old and the new scan. 

      


    In most of the cases:
    - the new CI will match the existing CI in BMC.ASSET
    - the next reconciliation job will try to identify the old and the new CI of BMC.ADDM with the same CI in BMC.ASSET.
    - this will fail because BMC.ADDM already contains a CI identified with the one in BMC.ASSET (nothing will change) As a result, the scan result sent by ADDM in the new CI won't be merged into BMC.ASSET until the old CI in BMC.ADDM is deleted.

      

    The expected RE errors are:

      

    ARERR[120092] The dataset ID and Reconciliation Identity combination is not unique.
    [...]
    Found multiple matches (instances) for class <BMC.CORE:BMC_ComputerSystem>

      


     The deletion of the old CI will
    - set the MarkAsDeleted attribute to yes in the BMC.ASSET CI (at the next reconciliation job)
    - the following reconciliation job will allow the identification/merge of the new CI of BMC.ADDM with the one in BMC.ADDM.
     
    If possible, we recommend to let the ADDM deletion process and the reconciliation process delete the old CI and then promote the new one in BMC.ASSET.
     
    If you want, you can accelerate the process of deletion of the "old CI". To do this you can:

    1. Change the settings below
    "Host/Network Device/Mainframe aging time limit"
    "Host/Network Device/Mainframe aging access failures"

    Note this is a global setting and reducing these values could lead to premature aging of hosts (before they are really gone)

    Reference: https://docs.bmc.com/docs/display/DISCO110/Configuring+model+maintenance+settings

    OR

    2. Identify, manually destroy, and synchronize the old Host nodes.
     
    To identify them, you can use the report "Devices with Endpoint Identity Change" (see the Reports page in the UI).
     
    You can also list the hosts that are now identified as other hosts with the following query:

        search Host where nodecount(traverse Previous:EndpointIdentity:Next:Host)
     
    If you select them and choose Actions > Destroy and Actions > Sync with CDMB, it will speed up the deletion of the old CI from BMC.ADDM.

     


    Article Number:

    000030001


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles