Schedule Discovery on a logical datacenter You can schedule the Discovery of resources in a logical datacenter (LDC) that runs automatically at specified intervals. Before you begin Role required: sn_cmp.cloud_admin A cloud account with service accounts and associated LDCs About this taskYou can also run Discovery on demand (Discover Now) if you do not want to wait for the next scheduled Discovery. Note: Scheduled Discovery only discovers the LDCs that are part of the cloud account when the schedule is created. If datacenters have been added since the time you created the schedule, Discovery does not run on them. Delete the old schedule and create a new one every time the LDCs in the datacenter changes. Procedure Navigate to Cloud Management > Cloud Admin Portal > Manage > Cloud Accounts. Click an cloud account to open it. From the left pane, select a datacenter and click Discovery Jobs. Click Schedule Discovery. Fill out the form fields (see table). Field Description Name Enter a unique, descriptive name for your schedule. 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 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. Time Enter the exact time (in hours, minutes, and seconds) for the schedule discovery to run. Table 1. Discovery schedule run options 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. Click Submit. Result Discovery runs at the specified times. The CMDB is populated and updated with the discovered resources. Information about the discovered resources appears in the Resources tab. What to do next View results of the discovery in the Discovery Log pane:The Discovery Log provides the following information: Field Input value Created Timestamp of the Discovery activity. Each timestamp defines the approximate time of the activity. Several Discovery events may occur in random order within a second. Level Classifies the activity into one of the following levels for general sorting: Error Information Warning Short Message Informative message detailing the outcome of the activity or the Discovery progress. Look here for the result of a classify probe or for authentication failure. ECC queue input The related input record from the ECC queue for this discovery. You can also view these records from the ECC Queue related list. CI Names a device for which a matching CI was found in the CMDB. Click this link to drill down into the CI record for the device. Source Names the particular activity, such as the Shazzam probe or a UNIX classify probe. Device Lists the IP address of the CI discovered. All devices identified by IP address appear in the log, even if they refused all invitations to communicate. Any port activity from a device places it into the log, even if all subsequent efforts to identify it fail. Click the IP address of the device to view the events associated with discovering that device. Move the state to Published.