Words and Phrases
Job Execution Policies
You can define periods of time when a Probe/probe cluster may not run. You can choose to disable specific jobs running on any Probe or all jobs running on a specific Probe or on Probes in a cluster. You can also exclude jobs from a job execution policy so that they continue running as usual.
For details on defining a job execution policy, see New/Edit Policy Dialog Box.
Say there are two policies, Total TCP Blackout and Always (the out-of-the-box policy). Total TCP Blackout does not allow any TCP discovery jobs to run. The policies appear in the list as follows:
A job (Class C IPs by ICMP) starts running. It checks the policies in the policy list from top to bottom. It starts by checking Total TCP Blackout. The job does not appear in this policy, so it continues down the list and checks Always. The job does appear here (Allow All is selected in the Edit Policy dialog box) so the job runs:
The next job (Software Element CF by Shell) starts running. It checks the policies in the policy list from top to bottom. It starts by checking Total TCP Blackout. The job appears in this policy (Disallowed Jobs is selected in the Edit Policy dialog box), so the job does not run:
Caution If a job is not connected to any policy, it does not run. To run these jobs, set the last policy in the list to Allow All.
Running Jobs When a Job Execution Policy Is Running
If a policy begins to operate while a Probe is executing a job, the job pauses. When the policy finishes, the job continues to run from where it ceased. For example, say a job contains 10,000 trigger CIs. The job finishes working on 7,000 of them and then the policy starts to operate. When the job continues (after the policy finishes), it works on the remaining 3,000 trigger CIs—the job does not start running from the beginning.
