Discovery IP address configuration

Use one or more of these methods in any combination to define the network or network segment for Discovery to query.

Note: If you do not know the IP addresses in the network, run Network Discovery first to determine the IP networks. Then, convert the IP networks into IP address range sets.
There are three types of IP collections:
IP collection type Description
IP address list Use IP address lists to add individual addresses to query. These addresses are not included in any existing IP range or IP network. You can enter the IP address of the device or a host name (DNS name). If you enter a host name, it must be resolvable from the MID Server system.
IP address range You can define arbitrary ranges of IP addresses to query. This process is a good way to include selected segments of a network or subnet. However, Discovery has no way of knowing if the IP range includes addresses for private networks or broadcast addresses, and scans all the addresses in the range. If the network and broadcast addresses are included, then the results are inaccurate. Discoveries configured to detect IP networks are more accurate than discoveries configured for IP address ranges. Only those IP addresses in your range that are reserved for manageable devices on the public network should be included.
IP network

You can also scan an entire IP network. An IP network includes the range of available IP addresses in that network. The scan also includes the network address (the lowest address in the range) and the broadcast address (the highest address in the range). After you run network discovery, convert the IP networks that were found into range sets for use in discovering other devices.

An example of a class C network range is 192.168.0.0 to 192.168.0.255. In the Range Set form, this network can be entered with either of the following notations:
  • 192.168.0.0/24
  • 192.168.0.1/255.255.255.0

This notation indicates that Discovery is scanning an IP network, and does not scan the highest and lowest numbers in the range. Significant errors are prevented and introduced into the Discovery data by the broadcast address. All devices are returned in the network, and the network address, which can add an arbitrary number of redundant devices. This built-in control makes IP networks the best method of defining which IP address ranges to query.

IP address selection properties

You can use system properties to control the selection of IP address for specified CI classes.

Use these properties to determine if the system should replace the IP address returned by Discovery in a device's CI record if the address does not match that of a network interface (NIC) on the device. This is important for the discovery of devices with management IP addresses that differ from IP addresses associated with one or more NICs on the device. Because a device's management IP is used in the Discovery schedule for that device, this is the address that Discovery returns. Use these properties to determine which IP address to use for CIs of any class.

Property Description
glide.discovery.enforce_ip_sync Prevents the system from using a discovered IP address in the CI record if the address doesn't match that of a NIC on the device. If this property is true, Discovery checks the IP address returned to determine if it is associated with a NIC on the device. If the address is not associated with a NIC, Discovery uses the IP address from one of the NICs instead.
  • Type: true | false
  • Default value: true
glide.discovery.exclude_ip_sync_classes Defines CI classes whose IP addresses should not be substituted if the address returned by Discovery does not match one of the devices' NICs. Use a comma separated list to define multiple classes. By default, the system uses the management IP of a load balancer returned by Discovery in the CI record, rather than substituting it for the IP address of one of the load balancer's NICs.
  • Type: string
  • Default value: cmdb_ci_lb

Create a Quick IP range for a Discovery schedule

Quick ranges allow administrators to define IP addresses to scan in a single comma-delimited string without creating separate records.

Before you begin

Only MID Servers that are up and validated are used with quick ranges. The MID Servers must specify the Discovery application (or ALL applications) and have IP ranges configured if you use the auto-select feature on the Discovery schedule.

About this task

You can enter IP addresses in one of the following formats:
  • An IP range defined by a slash and the number of bits in the subnetwork. For example, the string 10.10.10.0/24 scans 24 bits of IP addresses from 10.10.10.0 to 10.10.10.254.
  • An IP range defined by a dash. For example, the string 10.10.11.0-10.10.11.165 scans the IP addresses from 10.10.11.0 to 10.10.11.165.
  • A comma-separated list of specific IP addresses. For example, the string 10.10.11.200,10.10.11.235 scans the IP addresses 10.10.11.200 and 10.10.11.235.

Procedure

  1. Click the Quick Ranges related link on the Discovery Schedule form.
  2. Enter the IP ranges and specific IP addresses to scan.
  3. Click Make Ranges.
    Note: The Quick Range interface is for entering IP addresses only and cannot be used to edit IP addresses that have already been submitted.
    Figure 1. Entering a quick range from a Discovery schedule
    Entering a quick range
    The instance automatically displays the entries in the proper format.
  4. For changes to IP address ranges, select the IP address records in the Discovery Range Sets related list.

Import IP ranges into Discovery schedules with import sets

The most efficient method of entering large numbers of IP networks into Discovery schedules is by using import sets.

About this task

Common groups of IP addresses, known as ranges can be used in Advanced Discovery schedules.

Use a data source that can be mapped. Include these fields:
  • Start IP: the first IP address in the range (inclusive).
  • End IP: the last IP address in the range (inclusive).

Procedure

  1. Navigate to System Import Sets > Load Data.
  2. Identify the file or data source that contains the desired information.
  3. Create a table name, such as ipnetworks.
  4. Select Upload an Excel file and browse to the source file.
  5. Click Go to import the file.
    Figure 2. Data Source
  6. Navigate to System Import Sets > Create Transform Map and map the items in the Excel spreadsheet to the fields of the CMDB in the target table IP Range [ip_address_range] table.
  7. Give the Transform Map a unique and descriptive name.
  8. Submit the form, and then click New in the Field Maps Related List.
  9. Map the fields from the Excel spreadsheet to the fields in the IP Range (ip_address_range) table. The fields you need values for are the Start IP and End IP addresses.
  10. Click the Mapping Assist Related Link and use the lists that appear to resolve the fields between the table and the data source (the Excel spreadsheet in this example).
  11. Click Save.

    The view returns to the Table Transform Map form.

  12. Click Transform in the Related Links to move the data into the proper fields in the IP Range ([ip_address_range]) table.

    The imported IP ranges are available now for use in any advanced Discovery schedule.