Knowledge Article
Client Management: How the GUID / GloballyUniqueID is managed in BCM? How do we merge GUIDs?
It depends if you are running a version before or after 12.6 included.
BMC Client Management
Client Management
BMC Client Management (BCM) < 12.6 and BCM >= 12.6
It is generated from several criteria set into Global Settings > System Variables > Connection Management of the console:
A- From 12.6 and onward:
All the criteria from the list above are used to generate the Globallyuniqueid (GUID) without freedom to chose. The options above will only be used to merge GUIDs on fewer criteria: e.g only MERGE on the host ID as shown above. B- Before 12.6: the GUID was generated from what is set into Global Settings > System Variables > Connection Management: e.g: only GENERATE the GUID based on its host ID. A- After 12.6: If a device updates: - the same guid than the one known for this same device in the DB, the device is updated in the database (DB) - a GUID not already known in DB then the master verifies if a device already exist in the DB with the same value for the GUID Criterion that is selected in the system variables: A- If there is a match with an existing device, then related records are updated in the DB (GUID, IP, Mac...).
B- If no device matches then a new record is created in the DB. - a different GUID that has actually been generated as the 12.6 and onward format, it is updated in the column "GloballyUniqueID" of the table Devices in the DB as long as what is set in the tab "Connection Management" made made both match. The old GUID that was in this column before is moved to the column "PreviousGUID". - a different guid than the one known for this device in the DB, it is NOT updated, so the device will become/remain red until either: - the GUID is manually updated in the db, then the service of the client BCM agent is restarted
- the GUID is updated manually in the ini file, then the service of the client BCM agent is restarted - the original entry for that device is deleted from the console and wait for the next identity update. - "Allow Duplicate Device Names" is set in the tab Global Settings > System Variables > Connection Management. The "new" device will then be created with its device name but it will have a (1) at the end. B-Before 12.6: If a device updates: - the same guid than the one known for this device in the DB, it is updated - a different GUID that has actually been generated by a GUID scheme change, it is updated in the column "GloballyUniqueID" of the table Devices in the DB. The old GUID that was in this column before is moved to the column "PreviousGUID" - a different guid than the one known for this device in the DB, it is NOT updated, so the device will become/remain red until you'll have updated the GUID in the db, or in the ini file, or simply deleted the device from the console and wait for the next identity update. C- After Deprecation: The GUID is deleted from the DB. If the agent from the deprecated device, Device1, uploads a new identity, then the agent will appear in green in the console with its actual name "Device1". The deprecated device will be renamed to "Device1 (0)". Note: If a device is already named as "Device (0)" then the device that is deprecated again will be named "Device (0) and the older one will be renamed "Device (1)". etc D- Troubleshooting: New customers frequently encounters issues because the agent was not installed the right way, or at the right time. The following KA - Helps identify devices that could share a duplicate GUID - Provides solutions to solve issues with duplicate GUIDs: |
Attachment(s):