IP address related tables

[Koji Yanase]

I found ip_address_collection, ip_address_item, ip_address_list_item_m2m, ip_address_subnet_dscy_status_m2m tables. How do you use this? I'd like to know the best practice. 

Thanks.

[Daniel Slocum]

Hi Koji,

The tables you've identified would be auto-populated by ServiceNow Discovery when writing data to the CMDB. The results would then be visible as related lists to the CI where the IP Address was found.

[Koji Yanase]

Hi Daniel,

Thank you for your answer. So we should not use those tables manually? We need to manage IP addresses to see which address is used or which address is not used.

Thanks.

[Hitoshi Ozawa · Accepted solution]

They are used by Discovery and should not be used manually.

ip_address_list_item_m2m has fields ip_address_item and ip_address_list referencing respective tables. ip_address_subnet_dscy_status_m2m has field discovery_status and ip_address_subnet. These tables seems to be used by Discovery to keep track of ip addresses and subnets and their status.

Caution: IP ranges identified by Discovery are stored in the IP collection [ip_address_collection] table, which is only used for MID Server IP range auto-assignment in the Jakarta release. This table is intended for future development and should not be used in any customizations, including column additions, business rules, or scripting actions.

https://docs.servicenow.com/bundle/paris-servicenow-platform/page/product/mid-server/concept/mid-ser...

cmdb_ci_ip_address table is the table that should be used.

[KKrabbenhoft]

I have a need to use the cmdb_ci_ip_address table to populate the cmdb_ci_computer attribute "ip address" I have tried using the SG_SCCM-Network-Computer (cmdb_ci_computer) integration hub ETL. I keep getting the error "SCCM must have a source native key added. "

I added the "resource id" as a source native key but it keeps getting stripped out. 

any help on this would be appreciated.