Understanding potential duplicate Discovered Items/CI records and Reclassification

gumayusi
Tera Contributor

- KB1349923 mentions that after reapplying the CI lookup rules, there will be records within unclassed hardware/incomplete IP with no use. 

- In The more you know - SecOps and CMDB Interactions - YouTube, Scenario 4, it states that incomplete IP class records are never reconciled or reclassified. In Scenario 3, the example shows an existing record getting re-classified into the correct class. This from my understanding is not creating a new record.

- In ServiceNow Vulnerability Response CI Matching Tuni... - ServiceNow Community, "IRE is then utilized to try and find a match with an Unclassed Hardware CI and can potentially reclassify the Unclassed CI to the correct class with data brought in from a CI discovery source" 

- In Understanding CI Reclassification: What You Need t... - ServiceNow Community, it states "Creation of New Record: A new record is created in the new class for the CI, but the CI retains its unique identifier (sys_id)" 

   - Since it's using the same sys id, this would still be 1 record total after the reclassification and no duplicates, correct?

 

Could someone help me answer the questions below?:

1. Will CMDB reclassify the existing (unclassed hardware) record into the new correct class while not creating a duplicate record? 

2. When will duplicate discovered items/CI records co exist? If an unclassed hardware record exists and Discovery finds a match to that unclassed hardware record, wouldn't it reclassify that existing unclassed hardware record and not create a duplicate?

3. This ties with question 2. Let's say if a hardware CI exists in the Computer class. After running the third-party scanner and attempting both CI lookup & IRE, it doesn't match to the existing Computer class record. Then we we'll technically have 2 records that reference the same asset. Now, going off of KB1349923's use case, if we reapply the correct CI lookup rules, that would match the unclassed hardware to the existing Computer class record. What happens to that unclassed hardware record and existing VITs & Discovered Item?

1 ACCEPTED SOLUTION

Mani A
Tera Guru

1. Yes , reconciliation rules will take care of it ,if existing Ci record is available and then it will update with new class if reconcile criteria met and if not we should Adjust/create reconciliation rules accordingly. 

2. Mostly when discovery rules are not met then there may be a chance it would create duplicate one but we should make sure that there should be atleast one correct identification and reconciliation rules to avoid duplication..

 

If Discover finds unclassed hardware existing records and if rules are met with reconciliation then it will definately reclassify it 

3. Same as 2nd point only..if existing matches when we reapply ci lookup rules ,it will update the record .

 

What happens to unclassed hardware record and existing ViTs&discovery item ?--> not sure but i think it should also map to Cis to reference asset

View solution in original post

2 REPLIES 2

Mani A
Tera Guru

1. Yes , reconciliation rules will take care of it ,if existing Ci record is available and then it will update with new class if reconcile criteria met and if not we should Adjust/create reconciliation rules accordingly. 

2. Mostly when discovery rules are not met then there may be a chance it would create duplicate one but we should make sure that there should be atleast one correct identification and reconciliation rules to avoid duplication..

 

If Discover finds unclassed hardware existing records and if rules are met with reconciliation then it will definately reclassify it 

3. Same as 2nd point only..if existing matches when we reapply ci lookup rules ,it will update the record .

 

What happens to unclassed hardware record and existing ViTs&discovery item ?--> not sure but i think it should also map to Cis to reference asset

gumayusi
Tera Contributor

Awesome, thank you for the response!