Create Discovery Profiles
Discovery profiles specify how discovery operates. Discovery profiles determine the IP domain, IP addresses, IP address ranges, and host names for discovery.
Discovery profiles specify how discovery operates. They determine the IP domain, IP addresses, IP address ranges, and host names for discovery. You can specify only one IP domain for each discovery profile. Newly-discovered devices are created in the selected IP domain. When you have multiple data collectors in an IP domain, each issues a discovery request to each device as specified by the discovery profile. When more than one data collector can contact a device,
DX NetOps Performance Managementrandomly selects one of the data collectors to monitor the device. Review the capacity of the data collectors and rebalance as required.
For more information, see Rebalance the Load on Data Collector.
Only users in the tenant space where the discovery profile was created can access the discovery profile. Users that are assigned to the Default Tenant can access discovery profiles in the Default Tenant space.
Administrators can manage discovery profiles through
NetOps Portalor through the Data Aggregator REST web services. Log in as a tenant administrator to perform these tasks.
For more information, see Data Aggregator REST WebServices.
The following video walks through a single device discovery:
In this article:
Create a Discovery Profile
To specify how inventory discovery operates in your environment, create discovery profiles. To optimize discovery and reduce SNMP traffic, set up granular discovery profiles:
- Use separate discovery profiles for each group of devices that share an SNMP profile.
- Use separate discovery profiles for groups of devices that require different rediscovery schedules.
You can also automate discovery profile creation by way of the data aggregator REST web services or use this API in your scripts for managing discovery profiles. For more information about this API, see Manage Discovery Profiles Using REST.
Follow these steps:
- Log in as a tenant administrator.
- Hover overAdministration,Data Sources, and then click the data aggregator data source.TheMonitored Devicespage appears.
- ClickDiscovery Profilesfrom theMonitored Inventorymenu.TheDiscovery Profilespage appears.
- ClickNew.TheDiscovery Profiledialog opens.
- Specify a name and select an IP domain.The following characters are not permitted: single quotes, double quotes, backward slashes, forward slashes, ampersands.
- On theIPs/Hoststab, do one or more of the following actions:
- (Optional) Navigate to and import a CSV file of IP addresses. The CSV file can contain a comma-separated list of IPv4 addresses, IPv6 addresses, IPv4 address ranges, and hostnames. ClickSelect a file to import, browse to select the file, and then clickOpen.To apply Chinese characters to the alias name, save the CSV file in UTF-8 format.
- Specify IP address ranges, individual IP addresses, and host names that you want to discover for IPv4 addresses. You can add comma-delimited values. IPv4 address ranges can contain the following characters:
If an IP range includes multiple IP addresses, and one of the IP addresses maps to the hostname, discovery always uses the hostname IP as the primary IP address.For more information about how to specify an IP address range, including viewing examples, see the "Discovery Profile IP Ranges" section.
- Wildcards (*). A wildcard represents a full range for an IP octet: 0-255.
- Hyphens (-). A hyphen can exist between the lower IP address and upper IP address. A hyphen can also be in the IP octets in the lower IP address.
- (Optional) To haveDX NetOps Performance Managementregularly update information for discovered devices and discover new devices, configure a schedule for the discovery profile. Select theScheduletab, and then specify a schedule. The discovery profile is in the "Scheduled" state, and the next scheduled run time appears in theNext Run Timecolumn of theDiscovery Profilespage.For more information about the methods you can use to run discovery, see Run Discovery.
- (Optional) To use specific SNMP profiles, select theSNMPtab, and then complete the following steps:Using a subset of SNMP profiles reduces SNMP traffic.
- SelectUse specific list of assigned SNMP profiles.Default:Cleared
- Move one or more SNMP profiles from the list of available profiles to the assigned list.
- Select theAdvancedtab, and then configure advanced options:
- Naming Order and Reconciliation OptionsChange the attribute priority, which the system uses to name the discovered devices. Any device item that the discovery profile creates is named with the highest available naming convention. If a higher priority attribute is unavailable for the device,DX NetOps Performance Managementuses the next highest priority attribute. For virtual machines,DX NetOps Performance Managementignores the naming order and uses the names from vCenter.If you use host name to name devices, the device name is updated automatically when the hostname changes. If you use another attribute, such as system name, the change to the device name occurs when the discovery profile runs again.In some configurations, the network might not have unique DNS host names. To reconcile devices by the IP address and system name only, selectExclude Host Name.Default:Cleared
- ICMP DiscoveryTo determine if a device can respond to ICMP, leaveUse ICMPselected.Default:SelectedTo create pingables for devices that respond to ICMP but not SNMP, leaveCreate Pingablesselected.Default:Selected
Discovery Profileslist. If the profile has a schedule, discovery runs at the scheduled time.
Discovery Profile IP Ranges
In a discovery profile, you can specify the IP address ranges that you want to discover for only IPv4.
Examples: Valid IP Ranges
- The following examples attempt to discover devices at every IP address from 10.25.1.0 to 10.25.1.190:10.25.1.0-10.25.1.190OR10.25.1.0-190
- The following examples attempt to discover devices at every IP address from 10.25.0.0 to 10.25.255.255:10.25.*.*OR10.25.0.0 - 10.25.255.255
- The following examples attempt to discover devices at every IP address from 10.25.0.3 to 10.25.0.40 and from 10.25.1.3 to 10.25.1.40:10.25.0-1.3-40OR10.25.0.3 - 10.25.0.40, 10.25.1.3 - 10.25.1.40
- The following examples attempt to discover devices at every IP address from 10.25.0.0 to 10.25.0.5, from 10.25.1.0 to 10.25.1.5, and so on, up to 10.25.255.0 to 10.25.255.5:10.25.*.0-5OR10.25.0.0 - 10.25.0.5, 10.25.1.0 - 10.25.1.5 ... 10.25.255.0 - 10.25.255.5
Examples: Invalid IP Ranges
- The following example is invalid because the upper IP address is incomplete:10.25.1.0 - 10.23
- The following example is invalid because when a hyphen (-) is used in an octet in the lower IP address, the upper IP address cannot be present:10.25.1.0-190 - 10.25.1.255
- The following example is invalid because when a wildcard (*) is used in an octet in the lower IP address, the upper IP address cannot be present:10.25.*.0 - 10.25.255.255
- The following example is invalid because it is unclear whether the wildcard octet (1*) implies 10.25.10-19.0 or 10.25.10-199.0:10.25.1*.0