ADDM: When using "BMC Client Gateway connectivity", the second CMDB sync connection created in Discovery fails with "Sync target updating dataset BMC.ADDM on <ip >already exists"

Version 2
    Share This:

    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 Discovery 11.1


    APPLIES TO:

    Discovery 11.1.x and previous versions



    PROBLEM:

    Customer is using "BMC Client Gateway connectivity" to synchronize to three Remedy On Demand AR/CMDB servers (prod, qa and test).  Each of the AR/CMDB servers have their own IP address but in this case, Discovery has to use the IP of the BMC Client Gateway with a specific port. The gateway will redirect the traffic to the correct AR/CMDB server. In most cases, the dataset will be named "BMC.ADDM" on each of the three AR/CMDB servers.

    The customer can typicall create the first CMDB sync connection in Discovery with the IP of the gateway, dataset BMC.ADDM and the relevant port. 

    However, the second sync connection to be created fails with the error below:

    Unable to update CMDB RoD prod:  Sync target updating dataset BMC.ADDM on <ip> already exists 


    CAUSE:

    Discovery defect DRUD1-20252/DRUD1-16890


    SOLUTION:

    Fix to defects DRUD1-20252/DRUD1-16890 is included in Discovery version 11.2

    Workarounds:
    - use 3 distinct dataset names. For example: BMC.ADDM.PROD, BMC.ADDM.QA and BMC.ADDM.TEST (instead of 3xBMC.ADDM). This is the simplest workaround.
    - configure the DNS to bind 3 DNS names with the ip of the BMC Client Gateway. For example: prod.company.com, test.company.com and qa.company.com
    - use 1 single client gateway configured with 3 distinct ip addresses. This would allow you to keep one single dataset name. 
    - use 3 distinct client gateways (to have 3 distinct ips). 
     


    Article Number:

    000136654


    Article Type:

    Solutions to a Product Problem



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