Name |
Enter a unique, descriptive name for your
schedule. |
Discover |
Select one of the following scan types:
- Configuration items: Uses
Discovery identifiers to match devices with CIs in
the CMDB and update the CMDB appropriately.
Perform a simple discovery by selecting a specific
MID Server to scan for all protocols (SSH, WMI,
and SNMP). Or, perform advanced discoveries with
discovery behaviors. When you select a behavior,
the MID Server field is not
available.
- IP addresses: Scans
devices without the use of credentials. These
scans discover all the active IP addresses in the
specified range and create device history records,
but do not update the CMDB. IP address scans also
show multiple IP addresses that are running on a
single device. Identify devices by class and by
type, such as Windows computers and Cisco network gear. The
Max range size Shazzam probe
property determines the maximum number of IP
addresses Shazzam scans. See Configure Shazzam probe for details.
- Networks: Discovers IP
networks (routers and switches). Results from this
search are used to populate the IP Network
[cmdb_ci_ip_network] table in with a list of IP addresses and
network masks. Network scans update routers and
layer 3 switches in the CMDB.
- Service: Discovers
services for the Service Mapping application. See
Schedule a top-down discovery by Service Mapping for instructions.
- Serverless: Finds CIs
without needing to run discovery on a host, or CIs
on a proxy host that is already in the CMDB. See
Serverless Discovery for more information.
- Cloud application:
Discovers only the cloud resources for the
patterns that you specify. See Cloud Discovery for instructions.
- Cloud resources:
Discovers resources for one of the supported
cloud providers. This option only appears
when you run
Discovery on a cloud service account. You
cannot select it from a new Discovery
schedule.
- Certificates. Discovers
certificates based on URLs. Selecting this option
adds the Certificate Discovery Type field: URL
Certificate Discovery. See Run Certificate Discovery via URL scans for
more information.
|
MID Server selection method |
Select the method that Discovery uses to select a MID
Server:
- Auto-Select MID Server:
Allow Discovery to select the MID Server
automatically based on the Discovery IP Ranges you
configure. To find a matching MID Server, you must
configure MID Servers to use:
- The Discovery application, or ALL
applications. This setting authorizes the MID
Server access from Discovery.
- The IP Range that includes the ranges you
configure on the Discovery Schedule.
- Specific MID Cluster: Use
a preconfigured cluster of MID Servers. Select the
cluster. You are not required to specify one
member of the cluster. The MID Server cannot be
part of multiple clusters, such as one that
supports load balancing and one that supports
failover. You can add any cluster regardless of
the application that the MID Servers are assigned
to. When you select the cluster, the
Discovery application is
automatically added when it does not exist for the
MID Servers in the cluster.
- Specific MID Server: Use
only one MID Server. If that MID Server is part of
a cluster, only that MID Server is
used.
The cluster is not used. You can
add any MID Server regardless of the application
it is assigned to. The
Discovery application is
automatically added when it is not already
assigned for the MID Server you select. You can
assign a specific MID Server for all types of
Discover scans except
Service.
- Use Behavior: Use a behavior when a single schedule
requires the use of multiple MID Servers to
perform any of the following activities:
- Scans requiring multiple Windows
credentials.
- A schedule that must execute two or more
particular protocols (SNMP, SSH, or WMI) using
more than one MID Server.
- Load balancing for large discoveries where a
single MID Server would be inadequate.
- Scanning multiple domains.
Note: The Discovery schedule enforces domain
separation. The MID Servers that are available for
selection are limited to the same domain of the
user who is configuring the schedule.
See MID Server selection sequence for Discovery schedules for additional information. |
MID Server |
Select the MID Server to use for this schedule. This
field is available if MID Server selection
method is set to Specific MID
Server, or if you discover IP addresses,
networks, or web services. To verify that the MID
Server you selected is up and validated, look at the
MID Server dashboard. |
MID Server Cluster |
Select the MID Server cluster to use for this
schedule. This field is available if MID Server
selection method is set to Specific
MID Cluster. |
Behavior |
Select a behavior configured for the MID Servers in
your network. This field is available only if
MID Server selection method is
set to Use Behavior. |
Active |
Select the check box to enable this schedule. If you
clear the check box, the schedule is disabled, but you
can still run a discovery manually from this form, using
the configured values. |
Location |
Choose a location to assign to the CIs that the
schedule discovers. If this field is blank, then no
location is assigned. |
Max run time |
Set a time limit for running this schedule. When the
configured time elapses, the remaining tasks for the
discovery are canceled, even if the scan is not
complete. Use this field to limit system load to a
desirable time window. If no value is entered in this
field, this schedule runs until complete. |
Run and related fields |
Determines the run schedule of the discovery.
Configure the frequency in the
Run field and the other
fields that appear to specify an exact time. Note: The
run time always uses the system time zone. If you
add the optional Run as tz
field, it has no effect on the actual
runtime. |
Include alive |
Select this check box to include alive devices, which
are devices that have at least one port that responds to
the scan, but no open ports. Discovery
knows that there is a device there, but has no
information about it. When you set Include
alive on a Discovery
schedule, every device that has an open port, is
added to the Devices tab in
the Discovery Status form. If this
check box is cleared, Discovery returns
all active devices, which are devices that have at least
one open port. |
Log state changes |
Select this check box to create a log entry every
time the state changes during a discovery, such as a
device going from Active to
Classifying. View the discovery
states from the Discovery Devices related list on the Discovery Status form. The Completed activity
and Current activity fields display the
states. |
Shazzam batch size |
Enter the number of IP addresses that each Shazzam
probe can scan. Dividing the IP addresses into batches
improves performance by allowing classification for each
batch to begin after the batch completes. rather than
after all IP addresses have been scanned. The probes run
sequentially. For example, the value is set to 1000 and
a discovery scans 10,000 IP addresses using a single MID
Server. It creates 10 Shazzam probes with each probe
scanning 1000 IP addresses. By default, the batch size
is 1000. A UI policy enforces a minimum batch size of
256 because batch sizes below 256 IP addresses do not
benefit from clustering. The policy converts any value
below 256 to a value of zero. The value for this field
cannot exceed the value defined in the maximum range
size property for the Shazzam probe. |
Shazzam cluster support |
Select the check box to distribute Shazzam processing
among multiple MID Servers in a cluster and improve
performance. This setting works with the Shazzam batch
size. For example, a schedule is created to scan 100,000
IP addresses, with 10 MID Servers assigned to do the
work. Each MID Server is assigned to scan 10,000 IP
addresses. If the Shazzam batch size is set to 5,000 IP
addresses per probe, the schedule runs two Shazzam
probes per MID Server (10,000 IP addresses/5,000 per
batch). These probes are run in sequence and not
concurrently. |
Use SNMP Version |
Use this field to designate the SNMP version to use
for this discovery. Valid options are
v1/v2c,
v3, or
All. |
URL Certificate Batch Size |
Define the number of URLs to discover per batch
during Discovery. Leave the batch size as it is unless
recommended to change. |
Quick ranges |
Define IP addresses and address ranges to scan by
entering IP addresses in multiple formats (network,
range, or list) in a single, comma-delimited string. For
more information, see Create a Quick IP range for a Discovery schedule. |
Discover now |
Use this link to immediately start this
Discovery. |
Related
lists |
IP Ranges |
This related list defines the ranges of IP addresses
to scan with this schedule. If you are using a simple CI
scan (no behaviors), use this related list to define the
IP addresses to discover. |
Discovery Range Sets |
This related list defines each range set in a
schedule to scan by one or more Shazzam probes. |
Discovery Status |
This related list displays the results of current and
past schedule runs. |
Certificate URLs |
This related list displays the URLs that are
discovered using this schedule. You can add or delete
URLs from this list. |