IP Address Management in ServiceNow

[davidmcdonald]

Hi all,

We're starting to look at ServiceNow for IP Address / Network Management. Not using Discovery just yet, just manual population.

We're considering using the IP Network (cmdb_ci_ip_network) table, but we're unsure if it's exclusively intended for anything else and will cause issues if exposed to manual entries.

Any tips for IP Address Management in ServiceNow, or know if it's safe to use the IP Network table for manual entry?

[davidmcdonald]

It looks like it is indeed safe to use the IP Network table for manual population.

There's the Correlation fields and the Discovery field to specify if an IP Network record it was automatically created during discovery, which should protect the manually created network records.

The form and list layout needs to be configured, and the network information can be expressed either in IPv6 / CIDR format in just the IP Address field (e.g. 192.168.5.0/24) or using both the IP Address and Subnet fields (e.g. IP: 192.168.5.0 Subnet: 255.255.255.0).

By showing both fields, how the network is expressed can come down to the favourite flavor of the user populating the networks, as both expressions are valid.

Are my assumptions correct?

[Phil32]

How would you assign the individual IPs from the IP_Networks table?

This is my view

[Les1]

Phil or @davidmcdonald where did this land for you, this is a question being posed at our company as well about using ip_network for IPAM related activity

did you add fields? extend the ip_network table?

thanks

[davidmcdonald]

I can't say that I've revisited the idea since I originally asked.

By the sounds if it, you can just add entries into that table as you like. It's better if it's populated through some sort of tool for consistency and linking the IP addresses to a CI every time, but it's still acceptable to fill it in however you like.