Important This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Mapping for the BMC Discovery formats

The topics in this section describe the mapping for the BMC Discovery (formerly known as BMC Atrium Discovery and Dependency Mapping or BMC Atrium Discovery) formats.

Important

Starting from version 8.9.04, The device import task no longer supports the following mapping formats for the BMC Discovery versions that are End of Life: 

  • BMC Foundation Discovery 1.5
  • BMC Atrium Discovery and Dependency Mapping 7.5
  • BMC Atrium Discovery and Dependency Mapping 8.2+

After upgrade to version 8.9.04, any device import tasks referring to above formats are automatically upgraded to use the BMC Discovery 11.0+ (XML API) format. If you do not want the automatic upgrade, edit your device import tasks to use any other format other than the above mentioned formats before you start upgrading. If you have not edited these tasks, validate whether these tasks are working as expected after upgrade.

BMC Discovery 11.0 and later (REST API) format

BMC Discovery versions 11.0 and later (specified as 11.0+ in the GUI) use the REST API to perform the import task, unlike earlier device imports. 

Enter these details in the REST API Access fields.

  • URL: Format the URL in the following format: https://Discovery_Server:port/api/v1.0/data/search
  • User Name: Discovery UserName
  • Password: password
  • Query Parameter Name: query
  • Query Parameter Value: search NetworkDevice show name,#InferredElement:Inference:Associate:DiscoveryAccess.endpoint, sysobjectid

Substitute the following values in the query URL:

Note

The TrueSight Network Automation application server automatically performs URL encoding on any blank spaces or other special characters.

The API call returns the following response:

[
    {
        "count": 2,
        "headings": [
            "name",
            "#InferredElement:Inference:Associate:DiscoveryAccess.endpoint",
            "sysobjectid"
        ],
        "kind": "NetworkDevice",
        "offset": 0,
        "results": [
            [
                "bcan-cisco1200-01.bmc.com",
                "172.19.216.22",
                "1.3.6.1.4.1.9.1.525"
            ],
            [
                "bcan-cisco7010-01",
                "172.19.216.68",
                "1.3.6.1.4.1.9.12.3.1.3.612"
            ]
        ]
    }
]

The results element contains the device details, such as device name, device address, and snmpoid.

BMC Discovery version 8.2, 10.2, 11.0 and later (XML API) format

BMC Discovery versions 8.2, 10.2, 11.0 and later (specified as 10.2 (XML API) and 11.0+ (XML API) in the GUI) use the XML API to perform the import task, unlike earlier device imports.

Note

For BMC Discovery version 11.0+, ensure that your Discovery user is added to the api-access group in BMC Discovery. For more information, see XML-API in the BMC Discovery documentation. 

Format the URL as shown in the following example (all on a single line). Enter this URL on the import page into the Source field in the File Access section.

https://DISCOVERY_SERVER/ui/api/XmlApi?query=search NetworkDevice show name,#InferredElement:Inference:Associate:DiscoveryAccess.endpoint, sysobjectid&username=DISCOVERY_USERNAME&password=DISCOVERY_PASSWORD

Substitute the following values in the query URL:

Note

The TrueSight Network Automation application server automatically performs URL encoding on any blank spaces or other special characters.

The query returns the following values:

BMC Atrium Discovery version 7.5 format

The import task maps the BMC Atrium Discovery version 7.5 database fields to the device record as follows:

Mapping for the BMC Foundation Discovery 1.5 format

The import task maps the BMC Foundation Discovery 1.5 database fields to the device record as follows.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*