Capturing 'External IPs' in CMDB class

[RK4334]

Use Case: Service Now is an authoritative source for us and we would like to maintain all the key data elements in CMDB. Currently we have 'External IPs" stored in Infoblox and want to store them in CMDB so that the data is available for key customers who are interested in consuming that data for various reasons. (Ex: Security)

Has anyone implemented this? Any suggestions on which class can be used?

[RK4334]

Hi AJ, any update on the above reply please?

[RK4334]

HI AJ we are waiting on you to give some solution please.

[Chambbe]

I had a similar case where external IPs weren’t tied to any CI directly. Ended up creating a custom table under the Network gear with a reference to the primary CI and added status fields for tracking. Also, to test external routing or geo-location stuff reliably, I needed to buy Dedicated Static ISP proxies—it helped simulate fixed IP behavior for consistency across different tools.

[Chambbe]

Interesting thread—has anyone tried leveraging a CI Relationship to model external IPs separately but still link them logically to the primary CI? That way, you avoid overloading cmdb_ci_ip_address while maintaining visibility and traceability.

[Syed zabiullah]

Hi @RK4334 

Use the cmdb_ci_ip_address class to store external IPs.

• Use the existing attribute: ServiceNow provides an out-of-the-box attribute called Internet Facing in the cmdb_ci_ip_address table. You can use this to flag external IPs instead of creating a custom field.
• Avoid duplication: If you're importing IPs manually or via a non-authoritative integration (not using Service Graph Connector), ensure you configure Identification and Reconciliation Engine (IRE) rules properly to prevent duplicate records when Discovery later finds the same IP .

If my response helped, please mark it correct and close the thread so that it benefits future readers.

Regards,

Syed K