Highlighted
Acclaimed Contributor.
Acclaimed Contributor.
654 views

Duplicate Node CI type instance

Jump to solution

UCMDB 10.33 on Windows

We are noticing multiple discovery on same server is creating duplicate Node CI type instances.

I am aware of Node CI type identification, validation rules and why duplicate CI instances are getting created.

But I want to know is there any way to find out which validation or verification rule is failing, so that merging of CIs is not happening.

Can this information can be obtained from reconcilation or any other logs.

Please advise.

0 Likes
1 Solution

Accepted Solutions
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Hello there, 

  • Increase the reconciliation log rotation (conf\log\reconciliation.properties) from  10 to 30 and file size from 5M to 10MB. Also, the log level from ERROR to DEBUG
  • Reproduce the discovery
  • Note the time periods and CIT or CI names so we can search them in the logs
  • Extract the logs via JMX using executeServerLogParser with the time intervals from the job trigger until the moment the CIs were updated.

 

Keep in mind that you will have a heavy log output and you need to move quickly so the logs won’t be overwritten.

Kind regards,
Bogdan Mureșan

EMEA Technical Success

View solution in original post

3 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Hello there,

the logical steps are to put reconciliation logs on debug with increased size. Keep in mind that this logs rotate fast and have a big output.

You will find there what was the input data, CIs to update or merge and so on. They aren't pretty logs and you will have some challenges in decoding them but the information is there and it can be used for any kind of reconciliation analysis.

RnD is actively working on a new tool which will enable customers to easily explore the reconciliation process in an HTML5 interface.

 

Kind regards,
Bogdan Mureșan

EMEA Technical Success
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

John

Can you please let me know how to put reconcilation logs to debug.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Hello there, 

  • Increase the reconciliation log rotation (conf\log\reconciliation.properties) from  10 to 30 and file size from 5M to 10MB. Also, the log level from ERROR to DEBUG
  • Reproduce the discovery
  • Note the time periods and CIT or CI names so we can search them in the logs
  • Extract the logs via JMX using executeServerLogParser with the time intervals from the job trigger until the moment the CIs were updated.

 

Keep in mind that you will have a heavy log output and you need to move quickly so the logs won’t be overwritten.

Kind regards,
Bogdan Mureșan

EMEA Technical Success

View solution in original post

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.