Importing IP Ranges

[doug_schulze]

Seems allot of folks are looking for easier ways to bring in tons of IP ranges into their discoveries without having to manually enter hundreds of IP networks. Well Service-now.com to the continued rescue with an already existing product technology, Import Sets.

First, gather the list of IP ranges from the customer and have them properly formatted. You want   the IPs in a network/subnet format and identify what location or grouping they want to manage them by.

Next, identify the target ServiceNow table. This is going to be important the first

time so you can find exactly where the import of data is going to go. There is an OOB range set that you can use for reference.

As you see below, it's going to be the discovery Range Item table

Now that you know where the records are going, it's time to clean up your data and get it ready for import. In an excel sheet, you need a minimum Network, Subnet, Type and Range (set) Name.

Once the data is properly formatted, then perform a standard data import and transform.

Message was edited by: Doug Schulze

[tgryziec]

We used your idea as a base line. Instead of a direct Datasource because we could not get it to work. We now have a Powershell script which queries Nedi a freeware application for active IPs in our network. The Powershell script then emails the csv of IP address' to our instance which is processed by an inbound email action to create a Data Source. Works great. We have also setup another table which has all of our networks associated with different schedules, this allows us to keep the location and distribute to different MID servers based on where the devices are.

[doug_schulze]

Very nice! Love seeing how users take ServiceNow to the next level!

[nikhilagr20]

Hi Doug,

How can we import IP addresses or host name for discovery scan?

Regards,
nikhil

[doug_schulze]

importing IP addresses is the exact same method.. you would just change the type