Reconciliation cannot find match for instances during identification
If the Reconciliation Engine cannot find a match for an instance after applying all the identification rules, and if the instance is part of an Identification group that you did not specify to be auto-identified, the instance remains unidentified.
In such a case, you must manually identify the instance or modify the identification rules. To troubleshoot the unidentified instances issue
- Log in to CMDB Portaland in the Dashboard, under Currently Running Jobs in the side pane, click the number next to RE.
For information about logging in to BMC CMDB, see Accessing and navigating the CMDB Portal. - In the Reconciliation page, verify that the specific job was successfully executed after the modified date of the configuration item (CI).
- Verify that the Dataset ID of the CI matches one of the defined Dataset IDs.
- Verify that a qualification group is defined for the Identification activity.
- If a qualification group is defined, verify that the CI meets the qualification.
- Click Edit Server Configuration on the toolbar and configure the following settings for the Reconciliation Engine log:
Max Log File Size (kilobytes) = 20000
This setting enables you to zip the multiple log files for the same job and save them to another system in case the log files exceed 20 megabytes (MB).Logging level = Debug
- Start the Reconciliation Engine Job again and wait for it to complete.
Search for the Instance ID of your test instance in the Job log to find the entry, such as the following entry:
[DETAILS] [TID: 000006]: Started identifying instance <class = BMC.CORE:BMC_ComputerSystem, instance id = OI 1F94C10B39834F35BFDB59EEC3791F96>Note
The DETAILS and TRACE entries appear only if you set the logging level to Debug.
For information about how to search the log file for the identifying instance entry, see .
Was this page helpful? Yes No
Submitting...
Thank you
Comments
Log in or register to comment.