Client Management: How to find devices having the same GloballyUniqueID / GUID and to blacklist them

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 Client Management


    COMPONENT:

    Client Management


    APPLIES TO:

    Any version of BMC Client Management (BCM)



    PROBLEM:

    Some of my devices disappear then reappear in the console.

    Assignments I made to some devices are actually assigned to others.

    When I want to take control of a device it actually takes control of another device.


    CAUSE:

    Various Conditions, commonly the result of Capturing an OS for use in future OS Deployments (Cloning)


    SOLUTION:

     

    Devices are not supposed to share a GUID, when they do it can, as an example, seem to make devices appear, then disappear, then reappear etc. More information in the following Knowledge Article (KA): Client Management: Troubleshooting - Devices disappear from the console.

    1- Identify the devices
    The following queries will help identify the devices that run the same GUIDs and will display the associated GUIDs to blacliskt in the console.

    Run the following queries on the database, depending on the type of database the master runs on:

      
    A- Microsoft SQL Server:  
      
       
    SELECT d.DeviceID   ,d.DeviceName as Current_Name   ,substring (description,2,charindex('}',description)-2) as Prior_Name   ,d.GloballyUniqueID   ,min(elog.IntegrationDate) as min_eventdate   ,max(elog.IntegrationDate) as max_eventdate   ,COUNT(eventlogid) as NumberOfChanges   from bcmdbuser.EvLog_ObjType_710 elog  join bcmdbuser.Devices d on d.DeviceID=elog.DeviceID  where EventType='_DB_EVENTTYPE_DEVICENAME_CHANGE_ENUM_'     and d.DeviceName <> substring (description,2,charindex('}',description)-2)     and d.TopologyType in ('_DB_DEVTYPE_CLIENT_','_DB_DEVTYPE_MASTER_','_DB_DEVTYPE_RELAY_')  group by d.deviceid   ,d.DeviceName   ,d.TopologyType   ,d.GloballyUniqueID   ,substring (description,2,charindex('}',description)-2)  having count(elog.eventlogid) > 1  order by numberofchanges desc;
       
      2- ORACLE   
    select d.DeviceID    ,elog.eventdate as Event_log_date    ,d.devicename As Current_Name    ,substr(elog.description,2,instr(elog.description,'}')-2) as Prior_Name    ,elog.description as Event_log_entry  from EvLog_ObjType_710 elog  join Devices d on d.DeviceID=elog.DeviceID  where elog.EventType='_DB_EVENTTYPE_DEVICENAME_CHANGE_ENUM_'    and d.TopologyType in ('_DB_DEVTYPE_CLIENT_','_DB_DEVTYPE_MASTER_','_DB_DEVTYPE_RELAY_')    and elog.deviceid in       (        select d2.DeviceID        from EvLog_ObjType_710 elog2        join Devices d2 on d2.DeviceID=elog2.DeviceID        where elog2.EventType='_DB_EVENTTYPE_DEVICENAME_CHANGE_ENUM_'          and d2.DeviceName <> substr(elog2.description,2,instr(elog2.description,'}')-2)        group by d2.deviceid        Having Count(elog2.eventlogid)>2      )  order by d.deviceid, eventdate desc;
       
      3- postgresSQL
      
    select d.DeviceID,     COUNT(eventlogid) as "#_Name_Changes",    d.devicename As Current_Name,     substring(description from 2 for position('}' in description)-2) as Prior_Name,    d.netbiosname as Current_NetbiosName  from EvLog_ObjType_710 elog  join Devices d on d.DeviceID=elog.DeviceID  where EventType='_DB_EVENTTYPE_DEVICENAME_CHANGE_ENUM_'  and lower(DeviceName) <> lower(substring(description from 2 for position('}' in description)-2))  group by d.deviceid ,d.devicename, d.netbiosname, Prior_Name  having count(eventlogid) > 2  order by d.deviceid,"#_Name_Changes" desc;
      

    2- Blacklist the GUIDs  
       
    1. Go to Global Settings > System Variables > Connection Management
    2.  
    3. Set this/these GUIDs in the field "List of banned GUIDs"
      

    When a device with a GUID that is in this black list will upload a new identity to the master, the device will get the order to regenerate its GUID automatically and will then come up with the right GUID into the console.

       If several GUIDs where output by the query then all these must be added to the blacklist. They must be separated by a ",".


    3- Fix the issue 
    The following KAs provide solutions to solve this issue so it is not necessary to use the blacklist anymore:
          
    Note: The following KA explains how are GUIDs are generated when it works properly: Client Management: How is the GUID / GloballyUniqueID managed in BCM? How do we merge GUIDs?

     


    Article Number:

    000115403


    Article Type:

    Solutions to a Product Problem



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