Create a Discovery Schedule You can use a Discovery Schedule as part of creating a Discovery Status to launch probes and sensors. Navigate to Discovery > Discovery Schedules and create a new record. (Optional) Set the ranges of IP addresses based on the settings from the Discovery Schedule Quick Ranges. Complete the Discovery Schedule form (see table). Click Submit. Table 1. Discovery Schedule Form Field Description Name Enter a unique, descriptive name for your schedule. Discover Select one of the following scan types: Configuration items: Configuration item scans use discovery identifiers to match devices with CIs in the CMDB and update the CMDB appropriately. You can perform a simple discovery by selecting a specific MID Server to scan for all protocols (SSH, WMI, and SNMP), or perform more advanced discoveries with discovery behaviors. When you select a behavior, the MID Server field is not available. IP addresses: 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. Devices are identified by class and in some cases 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 the Shazzam probe for details. Networks: Network scans discover IP networks (routers and switches). Results from this search are used to populate the IP Network [cmdb_ci_ip_network] table in Discovery > IP Networks with a list of IP addresses and network masks. Network scans update routers and layer 3 switches in the CMDB. Web Service: Starting in Fuji, This scan discovers resources on Amazon Web Services. Results from this search are used to populate the AWS Resource table [cmdb_ci_aws_resource]. For EC2 instances, the information may appear as reference in the AWS Resource table. Behavior Select a behavior configured for the MID Servers in your network. When you select a behavior, the MID Server field is no longer visible. Use a behavior when a single schedule requires the use of multiple MID Servers to perform any of the following: 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. This field is available only if Discover is set to Configuration items. MID Server Select the MID Server to use for this schedule. This field is available if Discover is set to Configuration items or Networks. If you select a MID Server, you cannot select a behavior for the schedule. 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 are discovered by this schedule. 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 cancelled, 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 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 timezone. If you add the optional Run as timezone 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. 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 scans. 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, if this value is set to 1000 and a discovery must scan 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 5000. 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 maximum range size property for the Shazzam probe. This field is available starting with the Eureka release. Shazzam cluster support Select the check box to distribute Shazzam processing among multiple MID Servers in a cluster and improve performance. Works with the Shazzam batch size. For example, if the cluster contains 100,000 IP addresses and there are 10 MID Server Schedules, every MID Server will process 10,000 addresses (100,000 IP Addresses/10 MID Servers). If the Shazzam batch size contains the default 5,000 IP addresses per probe, a Schedule runs two Shazzam probes per MID Server (10,000 IP addresses/5,000 per batch). This field is available starting with the Eureka release. Use SNMP Version Use this field to designate the SNMP version to use for this discovery. Valid options are v1/v2c, v3, or All. 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. Discovery 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 be scanned by one or more Shazzam probes. Discovery Status This related list displays the results of current and past Discovery schedule runs. Table 2. Options for a Discovery Run Schedule Run option Description Daily Runs every day. Use the Time field to select the time of day this discovery runs. Weekly Runs on one designated day of each week. Use the Time field to select the time of day this discovery runs. Monthly Runs on one designated day of each month. Use the Day field to select the day of the month. Use the Time field to select the time of day this discovery runs. If the designated day does not occur in the month, the schedule does not run that month. For example, if you designate day 30, the schedule does not run in February. Periodically Runs every designated period of time. Use the Repeat Interval field to define the period of time in days, hours, minutes and seconds. The first discovery runs at the point in time defined in the Starting field. The subsequent discoveries run after each Repeat Interval period passes. Once Run one time as designated by the date and time defined in the Starting field. On Demand Does not run on a schedule. Click the Discover now link to run this discovery. Weekdays Runs every Monday, Tuesday, Wednesday, Thursday, and Friday. Use the Time field to select the time of day. Weekends Runs every Saturday and Sunday. Use the Time field to select the time of day. Month Last Day Run the last day of every month. Use the Time field to select the time of day. Calendar Quarter End Runs on March 31, June 30, September 30, and December 31. Use the Time field to select the time of day. To change these dates, modify the script include DiscoveryScheduleRunType. After Discovery Allows you to sequentially stagger the schedule. Use this option to run this schedule after the Discovery designated in the Run after field finishes. Check the Even if canceled check box to designate that this discovery should run even if the Run after Discovery is canceled before it finishes. This option is not valid when the Discovery is started via DiscoverNow, or when using the Discover CI feature. You cannot designate an inactive Discovery schedule. You cannot create a loop by designating the run after Discovery to be the same Discovery. This Discovery does not run if the Run after discovery does not finish, with the exception that the Even if canceled box is checked and the Discovery is canceled.