Highlighted
Honored Contributor.
Honored Contributor.
416 views

Potential reconciliation issues

Hi,

What is the main cause of duplication of servers or creation of incomplete nodes with the same name in UCMDB?
Is an error in the execution synchronization of the jobs?

I appreciate your contributions

0 Likes
4 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Cis duplicate with job host connection by wmi (windows) and VMware (node)

What is you CP version?

I would suspect that the WMware job doesn't retrieve the related CIs needed for reconciliation. It may be a permission problem for your VIM/CIM credentials.

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Cis duplicate with job host connection by wmi (windows) and VMware (node)

Also, there's a known issue for vCenter Topology job which creates weak nodes without a hostname hence they will reconcile a little bit later or at all.

https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/LID/QCCR1H109230

Kind regards,
Bogdan Mureșan

EMEA Technical Success
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: Cis duplicate with job host connection by wmi (windows) and VMware (node)

Is the Bios UUID field the main cause of the duplicity of virtual machines?
What happens if I remove this field from the reconciliation rules?
Why is this field so important?
Why does the Bios UUID change? Is not it supposed to be a unique identify? (vmotion???)
Does anyone know of virtualization? ---

Check: 

https://kb.vmware.com/s/article/1541

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Cis duplicate with job host connection by wmi (windows) and VMware (node)

Many brave engineers have tried in the past to alter the identification rules for node and they all got in the same failed state with unwanted duplicates. Please don't alter the identification rules for node CIT.

BIOS UUID can create duplicates, yes. That attribute doesn't change, there is always a reason why we "think" it changes. In the past, there were a lot of Support cases around this. It can be handled also on your particular scenario.

In 2018.11 we have a new option to assign reconciliation priority on attribute level based on discovery job so a particular attribute can have a higher priority on Host Connection by WMI versus Host Connection by Shell, as an example.

 

Kind regards,
Bogdan Mureșan

EMEA Technical Success
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.