Discovery: Not all scanned data (SI version, DB details, etc) is getting consolidated. Message "Request for information not part of the consolidated data" reported for discovery runCommand() method

Version 3
    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.2


    APPLIES TO:

    BMC Discovery



    PROBLEM:

     

    Not all scanned data (SI version, DB details, Software Components, etc) is getting consolidated. 

    It was observed that on the scanner, some commands run by patterns are collecting the required details. However, for the same commands the consolidator is reporting message "Request for information not part of the consolidated data" in the discovery runCommand() method.

      
        
      

     

     


    SOLUTION:

     

    Root Cause 1:  This is a documented limitation in versions prior to 11.1. See https://docs.bmc.com/docs/display/DISCO110/Consolidation:

      
      Missing information when patterns run commands on other hosts   

    When a host is discovered and patterns are triggered which run commands on a second host, the DDD on both hosts is updated. When the original host is consolidated, the DDD on the second host is not available to the patterns that trigger on the consolidator. When the second host is consolidated, the DDD created on it when discovering the first host is not included. Consequently the consolidator will always report that the information from the second host is unavailable. The error "Request for information not part of the consolidated data" will be reported in the consolidated DiscoveryAccess. This can lead to missing nodes (licensing Detail, SoftwareComponents, etc) and relationships on the consolidator. To work around this behavior, scan the original host from the consolidator.

    To confirm the root cause, check the DiscoveryAccess of the database server. It should have some message like "Request for information not part of the consolidated data" at the bottom.

      
      
      The DiscoveryAccess nodes affected by this issue can be listed with the query below: 
      
      search DiscoveryAccess where _last_marker traverse :::ProviderAccess traverse :::IntegrationResult where failure_reason="Request for information not part of the consolidated data"  
     
    This limitation is removed in Discovery version 11.1. With this version, a scanner sends the results of requests on the second host with the consolidation data from the original host. This allows commands run against other host to be successfully consolidated. 
      
        
      
      Workarounds for earlier versions:  
      
      1- Rescan the hosts from the consolidator. This requires network/firewall configuration changes (documented in the link above) 
      
      2- Record the scan result on the scanner and play it back on the consolidator. (This workaround can't be automated.)  
     
      Root Cause 2:  There is a difference in TKU versions loaded on the Scanner and Consolidator.  This can be confirmed by comparing the versions of the TKUs present in the scanner and consolidator from "Manage>Knowledge" in the UI.   
     
      Solution 2: If any of the TKUs are different, the solution is to update them to the same version.  
     
      Root Cause 3 :  The scanners are on Discovery version 11.1.0.5 and the consolidator is on version 11.2.0.6.  
    11.2.0.6 embeds a new feature "discovery command path restriction. See    https://docs.bmc.com/docs/display/DISCO112/Restricting+paths+on+which+you+can+execute+discovery+commands . 
    This feature makes sure the commands that are used to scan have an authorized path according to organizational policies.  
    The patch that embeds the related feature in 11.1 is 11.1.0.8.  
    Since the scanner doesn't have this feature, needed information that is supposed to be contained in the DDD is not there. The consolidator filters the results of some commands, these do not trigger the expected pattern and then some data is missed.  
     
      Solution 3: In general, consolidation works across supported versions of Discovery and there is not a strict requirement that scanning appliances and consolidating appliances are on the same versions. However in this case, if the consolidation appliance is on the latest patched version, and the scanning appliance does not have the latest patch, some data will be lost in consolidation.  
     
    In this case, the major version is not important, so it is still possible to consolidate from (for example) 11.0 to 11.2 if both appliances have the latest patch. However, the best practice is to have all appliances at the same version and patch level.  
     
     
      Root Cause 4 :  The consolidator is on Discovery version 11.3.0.5, and the scanners are on a lower patch of 11.3, or are on a lower version (such as 11.2) but not the latest patch.  
    The documentation at    https://docs.bmc.com/docs/discovery/113/consolidation-788110329.html says:  
     
    "Consolidating from an unpatched to a patched appliance   

    The latest patch release (11.3 patch 5) has created potential loss of data between unpatched scanning appliances and patched consolidating appliances."

       

    In general consolidation works across supported versions of Discovery and we do not insist that scanning appliances and consolidating appliances are the same versions.
    However it is now the case that if your consolidating appliance is on the latest patched version, and a scanning appliance is not yet patched to the latest patch version some data will be lost in consolidation.

       

    The simple solution right now is to upgrade any scanners to the latest patch level; these are:

       
        
    • 11.0 patch 6
    •   
    • 11.1 patch 8
    •   
    • 11.2 patch 6
    •   
    • 11.3 patch 5"
    •  
        Solution 4: The doc mentioned above also says:   

    "In general consolidation works across supported versions of Discovery and we do not insist that scanning appliances and consolidating appliances are the same versions.
    However it is now the case that if your consolidating appliance is on the latest patched version, and a scanning appliance is not yet patched to the latest patch version some data will be lost in consolidation.

       

    The simple solution right now is to upgrade any scanners to the latest patch level; these are:

       
        
    • 11.0 patch 6
    •   
    • 11.1 patch 8
    •   
    • 11.2 patch 6
    •   
    • 11.3 patch 5"
    •  
    In this case, the major version is not important, so it is still possible to consolidate from (for example) 11.2 to an 11.3 f both appliances have the latest patch. However, the best practice is to have all appliances at the same version and patch level.  
     
     
      Legacy ID:KA409545

     


    Article Number:

    000085316


    Article Type:

    Solutions to a Product Problem



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