Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..
408 views

DISPLAY MONITOR ISSUE

Hi experts!

We have a problem with the conciliation of the dislplay monitors, in the push job to Asset Manager.
When a monitor changes its parent Node (container), the integration tries to create it as a new monitor, instead of changing the assignment to the new device.
The reconciliation is done by GlobalId, Folder and lParentId.

In the old integration with Connect-It, there was an option in the reconciliation of the display monitors, called "Used to change parent".
Is there something similar in the push job of the Generic Adapter?
Any suggestions?

0 Likes
4 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: DISPLAY MONITOR ISSUE

Hi,

 

unless you have changed the Reconciliation Rule for DisplayMonitor, it is root_container + name. Therefore if you change the parent CI, it is a new CI for UCMDB. Check in the CI History if global_id changes.

Petko

Likes are appreciated!
0 Likes
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: DISPLAY MONITOR ISSUE

Hello,
Thanks for the reply.
How can we check the reconciliation rules of this CI? (we are beginners in uCMDB).
What happens is that in the uCMDB 1 display monitor is created for each container it has been associated with, and they have a different global Id.
Sometimes we look for a display monitor in the uCMDB by serial number and they appear up to 3 ci.
We appreciate any help.
 
Thnaks in advance!
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: DISPLAY MONITOR ISSUE

Hi MVOB,

you can read the capter https://docs.microfocus.com/itom/Universal_CMDB:2018.11/dfm/recon_intro_chap about how the reconciliation engine, identifying the CIs work.

Cheers,

Petko Popadiyski

Freelance Microfocus CMS UCMDB Consulting

Likes are appreciated!
Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Re: DISPLAY MONITOR ISSUE

Hi Petko

Thanks for your recommendation, following the guide we have solved some problem.
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.