Issue with NIC on Servicenow Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-01-2020 07:39 AM
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?
Regards,
SB
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-01-2020 08:42 AM
Hi,
If the attributes in the identifiers are matched with the existing and incoming data then it will update that record and it will not duplicate it.
Why you are creating them manually?
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-01-2020 11:28 PM
Yes that is correct but since the Heritage data does not have any NIC information hence we had to create a Dummy NIC which does not have the actual details.
My point is if we would want to update this dummy record with actual details from Discovery can we do it, i know if there is no match on MAC address and Name it wil create a new record, but is there any possible way to stop it and update the dummy record instead of creation?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-02-2020 02:28 AM
Hi,
You should setup proper relationship between NIC and IP. There is a check in where we see if the relationship exist then update. See Dougs comment below.
You can allow discovery to create this instead of creating manually.
If you want to update the exiting record then create relationship between NIC and CI properly.
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-02-2020 03:02 AM
Thanks Ashutosh for your comment.
The reason that we are creating dummy NIC is because that is the only way we can attach an IP to a CI, now my question is if we create a OWNS:OWNED by relationship in CMDB_REL_CI table between NIC and CI, will the discovery update the same dummy NIC or will it still go ahead and create a new NIC because Identifier would not match the MAC Address and Name(identifiers on Network Adapter table) since both these fields are not actual.
I understand that we should rely on Discovery for creating these, but the reason for manual creation is that Discovery go live will be later, and till then we need the CI's correctly mapped to IP's in the system, for this the manual creation is in place.
IF we update Alias field of NIC with CI name and put it in identifier rule for Network Adapter, can it solve the issue, or any suggestions that you have?