Issue with NIC on Servicenow Discovery

[SNOW9]

Hi All,

We are in process of data port and enabling discovery on our instance.For Heritage Data we are getting the CI and IP address and to map a CI to IP address we have to create a dummy NIC record in Network Adapter table.

Now when Discovery runs we can see that it goes ahead and creates a new NIC record in the Network Adapter table with details it gathers through Patterns. This is causing duplication of records, i understand that manual process is not creating a relationship in cmdb_rel_ci table, but even if we do that will the IRE not duplicate the NIC, would it update the dummy NIC created, if we add an additional field to the identification rule on Network Adapter table.

Any thoughts or pointers would help in how to resolve this issue of  duplication?

@doug.schulze 

Regards,

SB

[Ashutosh Munot1]

Hi,

If the Relationship is implemented then it all depends on your identifiers. If the identifiers and attributes are no proper then it will create new records.

You can give priority to alias then in your identifiers.

Thanks,
Ashutosh

[doug_schulze]

That is because there are no relationships between the network adapter and the base CIs. If the pattern doesn't see that relationship it creates its own records.

I cover a lot of that in the video on this post when migrating from probes to patterns. In your case, you are dealing with manual data but the same cause.

Not sure if the migration scripts would be helpful with this data as it seems you are starting with patterns, but would be an interesting test in a sandbox to see if it would work.

[SNOW9]

One question since the data brought in through Integration for NIC is dummy, if we go ahead and bring in the relationship in cmdb_ci_rel table Owns:Owned by and map CI to Network Adapter, will it solve the issue of duplication?

Because Servicenow when firing the IRE will find all details through pattern and it won't be a match on the Identification rules set for Network Adapter table, because the Mac Addess and name both will be different.

Can you suggest a way that instead of creating a new NIC we update the dummy one?

regards,

SB

[doug_schulze]

I don't see how. You have to ultimately have some level of shared value along with the relationship for the IRE to match. Curious to this use case, though why not after discovery of the targets that you just table clean to remove the records that aren't matched?

[Jimbo2]

Hi Doug, I understand this is an old post - we're facing similar issue - do you have a new link for the video you mention?