Retrying a Failed Job on Devices in Security Director
You can retry jobs that did not complete successfully on devices where they were configured to run from the Job Management page. Retrying a failed job allows you to save time because you do not need to create the job again and execute it, but can retry the failed job.
The following jobs can be retried if they fail:
Deploy Configuration
Discover Network Elements
Reboot Devices
Resynchronize Network Elements
To retry a job on the devices on which it failed:
Setting |
Guideline |
---|---|
Evict CLI/J-Web edit mode users |
Select the option to terminate CLI/J-Web edit mode user session. Starting in Security Director Release 21.3R1 hot patch v3, when you retry the update job on devices that failed due to device lock failures, you can terminate CLI user sessions on a device from Security Director. |
Type |
Specify whether the job should be run immediately or later. If you specify that the operation should be run later, you must specify a start date and time (in MM/DD/YYYY and HH:MM:SS 24-hour or AM/PM formats) for the job. |
Recurrence |
Specify whether the job should be done on a recurring basis. This field is displayed if the job was created as a recurring job. |
Repeat |
Specify the periodicity of the recurrence:
|
Every |
Specify the period at which the job retry should recur. For example, if you specified a periodicity in hours (Hourly), enter the number of hours after which the job retry should recur. |
On |
Specify one or more days on which you want the job to recur. Note:
This field is displayed only when you specify a weekly periodicity (Weekly). The day on which the retry is scheduled is disabled. For example, if you scheduled the retry on a Wednesday, then Wed is selected by default and disabled. You can select other days by enabling the corresponding check boxes. |
Ends |
Specify one of the following:
|
Summary |
Displays a summary of the recurrence. |