Discovery creating Duplicates for CI's- one with Serial Number and another with empty Serial Number

Suvetha S
Tera Contributor

Hi All,

We have a scenario in server table where Discovery is creating Duplicate CI's in the format like one CI is created with Serial number and the same CI is getting created after 2 months with empty serial number and same name and IP. When we run quick discovery the Discovery is updating the CI with Serial Number. Any idea why its happening? I have observed the above behavior for 50+ windows and linux servers. 

1 REPLY 1

Ethan Davies
Mega Sage
Mega Sage

Serial Number is one of the criterion used in the Identification Rules that come out of the box, so if Discovery sees a Server in your estate with no Serial Number and pulls that information back, then it is going to create a new entry in the CMDB if it cannot match with an existing Server.

EthanDavies_0-1700674967329.png

Note that these Identification Rules that come out of the box are inherited all the way down from the Hardware Class, so it might be prudent to start thinking of ones that are specific to your Server Classes to account for the nature of your environment.

 

The bigger question here is why is the Serial Number attribute disappearing for your Servers, you will want to chat to your Network Team about that. The outcome of that conversation might mean that you need to think about alternative Identifier criterion.

 

In the meantime, if you want to avoid CIs getting created without a Serial Number then you can create an IRE Data Source Rule to block the insert of any Windows or Linux Server that tries to enter the CMDB without a Serial Number.