This documentation supports the 20.02 (12.0) version of BMC Discovery.To view an earlier version of the product, select the version from the Product version menu.

Discovery Run node


A Discovery Run is a scan of one or more Discovery endpoints, specified as an IP address or addresses or ranges which are scanned as an entity. These ranges might be being scanned locally on from the appliance, or be the result of appliance consolidation.

For each Discovery Run, a Discovery Run node is created which records information such as the user who started the run, the start and end time, and so on. A Discovery Run contains a number of Discovery Access nodes. In turn, Discovery Access nodes contain all other non-integration DDD nodes.

Additionally a Discovery Run node can also contain Provider Access nodes. A Provider Access node is created for a particular IP address as a result of a SQL Discovery access. In turn, Provider Access nodes contain all other Integration related DDD nodes.

Discovery Run lifecycle

The following section describes the scenarios in which a Discovery Run is created or destroyed. DDD nodes are never updated.

Creation

A Discovery Run node is created when a Discovery Run starts; when a range that has been configured to be scanned starts actually scanning or, if the appliance is a Consolidation Appliance, when a Scanning Appliance's scan starts to be consolidated. The Discovery Run remains open until all of the endpoints (IP addresses) in the range have been scanned or consolidated.

Removal

Discovery Runs are removed when all of their contained Discovery Access have been destroyed through the Aging process. When the Discovery Run node is destroyed any linked Integration Access nodes and their associated DDD nodes are also destroyed.

Discovery Run node attributes

The attributes of a Discovery Run node are as described in the following table below:


Starting from v10.0 the Discovery Run node has no run_type attribute.

Discovery Run node relationships

The relationships of a Discovery Run node are as described in the following table:


 

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