Highlighted
Outstanding Contributor.
Outstanding Contributor.
242 views

What are the advantages and disadvantages of stamping?

Jump to solution
In UCMDB 10 Inventory Discovery there are options; enableStamping and onlyStampingClient. What are the benefits of turning on stamping? Why only stamp client devices? Are there any disadvantages of stamping devices client or datacenter?
0 Likes
1 Solution

Accepted Solutions
Highlighted
Contributor.
Contributor.

Re: What are the advantages and disadvantages of stamping?

Jump to solution

This is the description form the documentation:

enableStamping :  Determines whether or not ud_unique_id is stamped on the managed computer. Default: false.

 

onlyStampingClient : Determines whether or not to only stamp the client machine. If set to false, both data-center and client machine are stamped. Default: true.

 

Stamping is a very important concept in inventory discovery which is inherit from DDMI, stamping is a very fast way to identify two different nodes(CI) as same one (reconciliation), if two nodes have same stamping(actually it is a GUID written in registry in win/file in *nix), in UCMDB they will be considered as same CI and will merge. With this stamping option, if inventory discovery job doesn't find any stamp in remote machine, it will put a stamp on it.   

Also, the option 'stamping only on client' is used for stamping for ONLY devices which are in client environments and not Data Center. This is because in Data center environments, IP addresses are static and can be used as the stamping. This way the job is not leaving any information in data center host. 

 

No stamping is not UD Unique ID, UD unique IDs are created for all agents.

HP Support
If you find that this or any post has resolved your issues please mark it as solved.

View solution in original post

0 Likes
4 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: What are the advantages and disadvantages of stamping?

Jump to solution

Hello John,

 

Hope you are fine,

 

I will take a look on our sources for an accurate response and i'll be back soon.

 

Thanks,

0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: What are the advantages and disadvantages of stamping?

Jump to solution

Are you still checking on a solution?

 

Stamping is the process that creates the UD unique ID, correct?

0 Likes
Highlighted
Contributor.
Contributor.

Re: What are the advantages and disadvantages of stamping?

Jump to solution

This is the description form the documentation:

enableStamping :  Determines whether or not ud_unique_id is stamped on the managed computer. Default: false.

 

onlyStampingClient : Determines whether or not to only stamp the client machine. If set to false, both data-center and client machine are stamped. Default: true.

 

Stamping is a very important concept in inventory discovery which is inherit from DDMI, stamping is a very fast way to identify two different nodes(CI) as same one (reconciliation), if two nodes have same stamping(actually it is a GUID written in registry in win/file in *nix), in UCMDB they will be considered as same CI and will merge. With this stamping option, if inventory discovery job doesn't find any stamp in remote machine, it will put a stamp on it.   

Also, the option 'stamping only on client' is used for stamping for ONLY devices which are in client environments and not Data Center. This is because in Data center environments, IP addresses are static and can be used as the stamping. This way the job is not leaving any information in data center host. 

 

No stamping is not UD Unique ID, UD unique IDs are created for all agents.

HP Support
If you find that this or any post has resolved your issues please mark it as solved.

View solution in original post

0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: What are the advantages and disadvantages of stamping?

Jump to solution

Thank you for the reply! The ud_unique_id sounds like the UCMDB version of the NMID that was used in DDMI.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.