Server ip address in cmdb

[snowtech1]

Hello,

What would be the best practice to store multiple IP addresses for Servers in servicenow.

We don't have discovery. Server Data has been maintained manually by class owners.

We are loading the last piece of server data outside servicenow. These servers have multiple IP addresses(some have 20+).

The OOB 'IP address' field is meant for one.

Is there any recommended practice to track multiple IP addresses,

Currently considering the following,

1.Make the IP address field multi line(bigger)

2.Make a related list table and track them on it.

Thanks in advance.

[jake_mckenna]

How we can leverage this need the best is to use the cmdb_ci_network_adapter related table to server/computer records. This is what Discovery uses and has the ability to capture multiple IP/Adapters against your CMDB items. Expanding the field might be hard to manage or track IP address against going forward so utilizing the list should make it easier to report off of in the future.

[snowtech1]

Thank you for the reply.

I had reviewed the CI IP's table, NIC(referencing network adapters) is mandatory I believe, we dont actively track NIC.

Having a m2m like table, for this purpose would be the best way forward?

[jake_mckenna]

Yes the idea of having a related list would be easier to manage compared to a long field. It is easier to track and manage as a general rule, and that also opens the door to track attributes on an IP, such as Public vs. Private, for example.

[Deepak Ingale1]

I will still go with OOB table of network adapters to track the IP address, this will help if in future we decided to move from manual import to discovery solution.