Identification rule based on Name is sufficiently unique for some classes such as BMC_LOCALFILESYSTEM, BMC_DISKDRIVE, etc

Version 2
    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 Atrium CMDB Suite


    APPLIES TO:

    BMC Atrium CMDB Suite



    PROBLEM:

     

    BMC Atrium CMDB Enterprise Manager version 2.1.00

      

     

      

    Why is identification based on Name sufficiently unique for some classes such as BMC_LOCALFILESYSTEM, BMC_DISKDRIVE, BMC_OPERATINGSYSTEM, BMC_BIOS, BMC_PROCESSOR, BMC_OPERATINGSYSTEM?

      

    There are many LocalFileSystems where Name = C, so the value of this attribute is not very selective.

     


    SOLUTION:

     

    Legacy ID:KA314444

      
      Identification of system components such as BMC_LOCALFILESYSTEM, BMC_DISKDRIVE, BMC_OPERATINGSYSTEM, BMC_BIOS, BMC_PROCESSOR, BMC_OPERATINGSYSTEM  
     always use an additional qualification of SystemName = SystemName, which means the CI must be related to the same system.  
      
        
      
      This is done internally in the Reconciliation Engine based on the Class of CIs that are identified. 
      
        
      
      For example, a LOCALFILESYSTEM CI has Name = C, which is not unique. 
      
     
    But the identification qualification used by the Reconciliation Engine during identification looks for a match on the related Parent Computer System as well, which makes it unique. So the actual qualification is like: 
      
     
      'Name' = $Name $ and 'SystemName' = $SystemName $, when looking for a match on LocalFileSystem. 
      
        
      
      In the Reconciliation Job logs, you can see it reporting the value of RelLeadClassId and RelLeadInstanceId - which is a reference to the parent computer system of the LocalFileSystem.  
      
        
      
      As long as there is a non-NULL value of SystemName for the system components, the identification should work as desired.   There is an knowledge article   
      20018162 Multiple match or Error 120092 occurs during identification of weak-related SystemComponents  
    that describes error conditions and avoidance for cases where SystemName = NULL. 
      
    Related Products:  
       
    1. BMC Atrium CMDB Suite

     


    Article Number:

    000085898


    Article Type:

    Solutions to a Product Problem



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