(Suite Only) Universal Discovery Agent Overview

Universal Discovery (UD) Agent is a program that is installed on a discovery node.

Functionality

The following table shows the functionality that the UD Agent performs:

Functionality
Communication. Performs job scheduling and job execution functions with the Data Flow Probe and with the Scanner.
Shell. Provides a command line interface that provides access to services. The UD Agent uses the Universal Discovery protocol.
Software Utilization. Generates files that contains application utilization data. For more information, see Software Utilization.

Unique ID

The UD Agent generates a Unique ID (UUID) when it is installed on a discovery node. However, if there is a Unique ID already stored on the node, the UD Agent uses the existing Unique ID. Unique ID generation occurs when agent-based and agentless discovery methods are used. Additionally, generation might also occur when the Agent Driven Inventory Discovery, Inventory Discovery by Scanner, and Host Connection by Shell jobs run.

The Unique ID can be utilized as follows:

  • Reconciliation. The Unique ID is used for identification and validation criterion during reconciliation operations.
  • Authentication. The Data Flow Probe uses the Unique ID to validate that it is connecting to the correct discovery node when performing discovery.

The Unique ID must be unique. However, if you use disk cloning to distribute images that contain the UD Agent, some identical Unique IDs might occur, therefore, UCMDB server might merge the node CIs that have the identical Unique ID. To fix this issue, a new option UD_UNIQUE_ID_HostName is available starting from UCMDB 11.0. This option works as follows:

  1. Every time that the UD Agent generates a new Unique ID, it records the host name.
  2. When the UD Agent starts, it checks whether the host name is the same as the host name that was recorded when the Unique ID was created.
  3. If the host name is different, the UD Agent recreates a Unique ID (UCMDB is updated with this change when the Agent next communicates with Data Flow Probe).
  4. Result

    The change is displayed in the discagnt.log file. For example,

    Looks like the agent is cloned or copied because the host name changed from "BIBFNTFGEP" to "BIBFNTFGEP_cloned", UUID: 00d9ffd-f581-bab3-4a05-3c7d18453992
    New UUID is: 776bf11d-cafe-dcd4-3a7dcdc6ad2

Note  

  • If the UD_UNIQUE_ID_HostName option is empty, UD Agent will not recreate a Unique ID because most likely the Agent is upgraded from a previous version. In this scenario, update the value of UD_UNIQUE_ID_HostName to the current host name.
  • If you create a virtual machine image template that contains a UD Agent, also create a new Agent option UD_UNIQUE_ID_HostName with a new host name along with the Agent option UD_UNIQUE_ID.
  • For more information on where UD_UNIQUE_ID and UD_UNIQUE_ID_HostName is stored, see Universal Discovery Agent File Locations.

For details about deployment methods for the UD Agent, see Universal Discovery Agent Deployment.

Related Topics Link IconRelated Information