Duplicates for Azure/EC2 and VM Instances and Network Interfaces

Lisa O_Brien · ‎10-20-2023

Our CMDB is being inundated with Duplicate Tasks like the ones shown below. There are items in the Azure Network Interface Card class that have the same identifier - Object ID, as in the Cloud Mgmt Network Interface class. Similarly, items in the Azure and EC2 Virtual Machine Instance classes have the same Object ID as items in the Virtual Machine Instance class. Has anyone else run into this? Any suggestions on how to resolve this would be greatly appreciated.

Mateus Oliveira · ‎10-24-2023

Hello @Lisa O_Brien

Have you confirmed that there has been no modifications to the Identification Rules of this classes? Is it really identifying these duplicates because of the Object ID? Object ID are normally unique in the cloud, so maybe something changed in the IRE rules in your instance.

If this is not the case, I could pick some cases and check the values in Azure itself to confirm discovery is picking it correctly.

Lisa O_Brien · ‎10-25-2023

I appreciate your response. The Identification Rules have not been modified. Should 2 instances ever have the same Correlation ID or Object ID ? If they are showing this way, are they really the same item ?

Mateus Oliveira · ‎10-26-2023

Hi Lisa,

If the Identifications Rules have not been modified, IRE should be relying on Object ID for the identification of the VMI class, as OOTB. In this case, you don't have to worry much about Correlation ID. Normally this is a reference to another CI to which the VMI is related to.

Now for the Object ID, this should really be unique to the VM. If they are showing the same, it is likely they actually represent the same machine. Here you can check more about the Object ID for AWS Cloud Discovery: Amazon AWS Cloud Discovery (servicenow.com) "DescribeInstancesResponse.reservationSet.item.instancesSet.item.instanceId"

Another thing you should review, is the source of creation for these CI's. I fear that one of them is being manually created (I can see that by the Most Recent Discovery date being empty in your screenshot). This would explain why IRE was not capturing this duplicate at the moment of the CI discovery. I would recommend to review it as well and make sure everything is going through IRE for proper reconciliation. I hope this helps you.

Please, mark my response as helpful 👍 in case it helped you. Also, please mark the question as answered in case your issue is solved. This really helps future readers.