Default language.

Important This documentation space contains information about the on-premises version of BMC Helix Discovery. If you are using the SaaS version of BMC Helix Discovery, see BMC Helix Discovery (SaaS).

Consolidating the inferred model


Configuring consolidation is a two-step procedure. Initially, you must enable consolidation on the appliance or instance which is to be the receiver. Then you register one or more senders with the receiver. To configure consolidation, you need the permissions detailed in Consolidation Permissions.

Clusters operate in a similar manner to stand-alone appliances. Stand-alone senders can consolidate to any member of a cluster. When using a cluster as a sender, you configure consolidation on any member UI, but the cluster coordinator sends information to the receiving cluster. The sending cluster can consolidate to any member of the receiving cluster. 

Note

Inferred data consolidation uses port 443 to communicate. The sender must be able to connect to port 443 on the receiver. You must configure any firewalls between senders and receivers to allow this traffic. 

You cannot use consolidation if the appliance is named Discovery_Appliance or when an instance is called BMC Helix Discovery. A warning, including a link to where you change the appliance or instance name, is displayed.

To configure consolidation of the inferred model

  1. Perform the following steps on the sender: 
    1. From the main menu, click the Administration Settings icon, and then select Discovery Consolidation.
      InferredConsolidationNotStarted.png 
    2. On the Discovery Consolidation page, select Enable Consolidation.
      The appliance can now be configured for consolidation.
      InferredConsolidationEnabled.png
  2. Perform the following steps on the receiver:
    1. From the main menu, click the Administration Settings icon, and then select Discovery Consolidation.
    2. On the Discovery Consolidation page, select Enable Consolidation.
    3. Copy the DNS Name (preferred) or the IP address by using the copy icon:
      InferredIPCopyIcon.png
  3. Perform the following steps on the sender: 
    1. Click + Add Destination to show the Add Consolidation Destination panel.
    2. Select Inferred Model.
    3. Paste the copied IP address into the Destination Address field.
      InferredAddDestination.png
    4. Click Add to establish the connection to the receiver. The screen updates and the status shows Pending Approval
      InferredSenderPendingApproval.png
      The connection request must be approved in the receiver UI.
  4. Perform the following steps on the receiver:
    1. From the Actions menu, select Approve.
      InferredReceiverApprove.png
  5. Perform the following steps on the sender:
    1. After a short delay, the connection status is updated to Approved and Resync required.
      InferredSenderApproved.png
    2. To resynchronize the sender and that sender's partition on the receiver, select Start resync from the Action menu.
      InferredStartResync.png
      The resynchronization proceeds. If there is a lot of data in the system, the resynchronization can take some time.
      InferredResyncInProgress.png
      Until the resynchronization is completed.
      ResyncComplete.png

      Consolidation of inferred data from the sender to the receiver is configured. When changes occur to the inferred model on the sender during normal discovery operations, they are sent to the receiver. When discovery runs occur on the sender, they are also displayed on the receiver.

If you are consolidating to a BMC Helix Discovery instance, the Discovery Status page shows a warning if you do not have a BMC Discovery Outpost connected. Ignore the warning if you only want to receive data from inferred consolidation.



 

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