Reprocess existing CIs via IRE

MFO1911
Tera Contributor

Hello,

 

We have a lot of CIs automatically created from manually created Assets. So the Discovery Source is empty so they are not processed through IRE. With the help of a Knowledge Article we bulk updated the Discovery Source to "Manual Entry" but this was not triggering the IRE. So the questions are How can we simply process existing CIs through the IRE? and Is there a attribute on CI that marks if a CIs is passed through IRE?

 

Many thanks 

 

MFO

1 ACCEPTED SOLUTION

Ashish37
Mega Guru

Hi @MFO1911 ,

 

So we have to run our Discovery or the SGC against these CIs to pass them through IRE. When a identification rule is affected the Discovery Source field on the CI is then updated to: "ServiceNow" or "SG-Intune".

>> Yes correct, as soon as these manually entered CI's are seen by Discovery or SGC Intune they will go through IRE to find a match based on Serial Number or Name) and you will see Discovery source SGC-Intune or ServiceNow updated with other discovered fields including Data Source History entries.

 

I also checked KB article KB0829078:

Play 4: Fix Play: Add IRE to any active Discovery Sources talks about how to manually import CI's via IRE.

Just a thought, if you export Name, Serial Number and Class from cmdb_ci_hardware and import them again in CMDB via transform map created in Play 4 then you will be able to achieve what you want to (Discovery Source will be Import step in this case). But I don't think that is necessary as you have ServiceNow and SG-Intune to populate the data.

 

Thanks,

Ashish

View solution in original post

5 REPLIES 5

Yashsvi
Kilo Sage

Hi @MFO1911,

To process existing Configuration Items (CIs) through the Impact Relationship Explorer (IRE) in ServiceNow,

 

1. Update Discovery Source:
- Ensure that the Discovery Source field of the CIs is correctly set to "Manual Entry" for those CIs that were manually created from Assets. This can be done manually or through bulk update operations.

2. Trigger IRE Processing:
- Once the Discovery Source is updated, you need to trigger the IRE processing for these CIs. This can be achieved by running a Discovery on these CIs or by manually triggering the Impact Analysis.

3. Run Discovery:
- Run a Discovery job specifically targeting the CIs that need to be processed through IRE. This will initiate the discovery process and update the relationships for these CIs based on the discovery results.

4. Manual Triggering:
- Alternatively, you can manually trigger the Impact Analysis for these CIs. Navigate to the CI record in ServiceNow, and from the related list or action menu, select "Run Impact Analysis" or similar option to initiate the IRE processing.

Regarding your second question, there isn't a specific attribute on the CI that directly marks if a CI has been processed through IRE. However, you can use indicators such as the presence of Impact Relationships or the Last Processed timestamp to determine if a CI has undergone IRE processing.

Conclusion:
- Ensure Discovery Source is set to "Manual Entry" for relevant CIs.
- Trigger IRE processing through Discovery or manual methods.
- Use available indicators like Impact Relationships to confirm IRE processing status.

 

Thank you, please make helpful if you accept the solution.

MFO1911
Tera Contributor

Hi @Yashsvi,

Thank you for your response. My question is regarding the Identification and Reconciliation Engine (IRE).
I did not found something about the you mentioned Impact Relationship Explorer, sorry for the confusion.

 

However your steps seems more for that what im looking for. As i explained before we already have updated the Discovery source for all CIs to Manual Entry. Triggering the IRE via Discovery is in the moment no option, so we have to trigger the IRE manually. On the CIs Form or List i do not find any related link or ui action etc. to trigger the IRE processing manually. Do i have to install a plugin or build up an own action to use this functionality? 

 

Unfortunately this steps are not solving our issues, thank you for your efforts.

 

Maybe someone else have similar issues and can share some more input? This will be very interesting.

 

Best Regards and many thanks

 

MFO

 

Ashish37
Mega Guru

There are mainly 2 ways CI's gets created:

1. By creating Assets manually or via bulk import on alm_asset or alm_hardware table, it creates CI based on the Model category selected (not all model categories creates CI) - If CI is created by this way it does not go through IRE and hence Discovery source, Most recent discovery fields are empty and no data source history - This is perfectly fine.

2. Discovery first approach: By running ServiceNow discovery or any integration (like SCCM, Tanium, Intune or it could be even by loading  CI through excel/csv via CMDBTransformUtil API ) - CI's created in this case goes through IRE (Identification and Reconciliation) process. Assets will also get created based on Model Id.Model Category value,

 

In your case you first imported Assets which might have created CI (in cmdb_ci_* tables) without going through IRE. Now whenever you discover these CI or populate them via any other discovery source these CI should get updated based on Identification rules defined for the classes they are in provided these CI have the attributes populated (for example if CI class is cmdb_ci_computer, CI should have unique Serial Number or Name). 

 

I have few questions before answering your question "How can we simply process existing CIs through the IRE?"

1. what are the CI classes?

2. what discovery sources you have in place to populate these CI classes ?

MFO1911
Tera Contributor

Hello @Ashish37,

 

Thank you for your response.

 

Regarding your questions:

 

1. What are the CI classes?

The CI Classes we wanted to pass through IRE are starting from cmdb_ci_hardware to all extended child classes. 

 

2. What discovery sources you have in place to populate these CI classes ?

In the moment we use the ServiceNow Discovery and the Service Graph Connector for Intune. 

 

So we have to run our Discovery or the SGC against these CIs to pass them through IRE. When a identification rule is affected the Discovery Source field on the CI is then updated to: "ServiceNow" or "SG-Intune".

 

The KB Article: CIs Processed Via IRE - Data Foundations - Now Support Portal (KB0829078) recommends to bulk update the CIs not created by an automatically Discovery Source field to: "Manual Entry". However this is not triggering the IRE, hits no identification rule and also dont marks a CI as processed via IRE. It seems to be no possibility to trigger the IRE manually for a Class or single CI without Discovery

 

Do you have any further ideas?

 

Many thanks and Best regards

 

MFO