CI update process for OS migrations

[Allen_Deepak]

HI,

I'm trying to update the CI update process for OS migrations.

We have a CI 'xyz' with OS A1. Now this CI is migrating to higher OS version OS A1.1. After the migration, the discovery is creating new CI with same CI name 'xyz' and same IP address only with different OS version and different serial number.

Here the discovery should be updating the same CI record instead od creating duplicate record. But that's not working. And when checking the IRE, the unique identifier is Serial number & correlation ID. What can be the proper IRE rule to avoid these duplicates?

What are some of the process things, that will help us to avoid duplicates during these migrations?

Please help with best practice.

Thanks.

[Ashok Sasidhara]

What is the CI class? Correlation ID is likely to be the issue here. Are there any other data sources populating this CI class? 

In the following article, I have explained in detail about IRE and some best practices. 

https://servicenowguru.com/cmdb/servicenow-cmdb-identification-and-reconciliation-engine-ire/

[Allen_Deepak]

@Ashok Sasidhara  Thank you for the response.

Its a Linux Server. RHEL VM.

Due to the OS migration, the old VM is now terminated and now the server got new serial number (Correlation ID of new VM). Is there a way to update the existing CI for these OS migrations even with the change in serial numbers? Every time we ned up with duplicates whenever there are migrations. How to define IRE in this case?

Thanks.

[Community Alums]

hi @Allen_Deepak , 

May be this a old post to respond. Did you look at the install status and operational status fields of old CI's and check for any there any inclusion rules configured in your instance. With inclusion rule there is an option to exclude certain ci's from IRE based on the filter conditions. May be your old ci's are getting excluded from the IRE that's why it is creating a new ci even though serial number is same. 

Regards, 

Srinija