Duplicate Virtual Machines are creating on cmdb_ci_vm_instance table.

Vini
Giga Guru

Hi Everyone,

we are discovering AWS Infrastructure in ServiceNow Jakarta Version. when ever we rerung the Jobs duplicate Ci's are created on

AWS tables with the same name and Object Id, only create time is different.

We set the below properties set to TRUE on syem.properties table. still issue was not resolved.

glide.identification_engine.skip_duplicates.threshold

glide.identification_engine.skip_duplicates.threshold

Please advice

Regards,

Vinil.

4 REPLIES 4

Patrick DeCarl1
ServiceNow Employee
ServiceNow Employee

Hi, 

 

Is this still an issue? Have you checked to see if you have CI identifier setup fro VM Instance (cmdb_ci_vm_instance)? 

karmeng
ServiceNow Employee
ServiceNow Employee

Hi,

By default, the identifier rule for "cmdb_ci_vm_instance" is object_id as criterion attribute

 

find_real_file.png

 

If this is out of the box in your environment, I'm suspecting the reason is because the object_id are different between them and therefore the CI get created in "cmdb_ci_vmware_instance". 
Although they have same name but the object id are different therefore the CI being created.

Based on

https://www.virtuallyghetto.com/2011/11/vsphere-moref-managed-object-reference.html 
Snippet from link: 
@@ 
A Managed Object Reference ID also known just as MoRef ID is a unique value that is generated by the vCenter Server and is guaranteed to be unique for a given entity in a single vCenter instance. 
@@ 

Different object id could means the entity from different vCenter instance.

 

Hope this helps.

 

Regards,

Kar Meng

 

 

Saketh
ServiceNow Employee
ServiceNow Employee

Hi Vinil,

 

I agree with Kar Meng on this.

Just as two servers can have the same name but different serial numbers, if serial numbers are used for identification, you will see two records in the server table with the same name.

 

Similarly, for cmdb_ci_vm_instance, the identifier is 'object_id' and there's good chance for above scenario to occur if the names are not unique.

 

Can you check the object_id's of the servers and get back to us?

 

Thank you,

Saketh

Parth10243
Tera Contributor

I came across similar issue. I think the reason why multiple records are created with the same name and same object ID is because they are hosted on different machine.

 

Just wondering what is the best way to deal with this? Should we some how find a way to have only one record point to a virtual machine instance irrespective of the host? If so, are there any suggestions on how to do so?