Document toolboxDocument toolbox

Defining Triggered Jobs

Note

An example of a triggering event is: NetMRI discovers a new Cisco switch on the network. This event is embodied in a bit of data called a Trigger Source, which defines the nature of the event. For more information, see  Automation Change Manager (ACM) Triggering Sources.

As part of the triggered job definition, you specify the triggering event, the time periods over which  you would like this trigger to be active, and the device and interface groups to whose members the trigger applies.
For triggering events, a job's settings, such as script and variable input, define a template for new jobs to perform remedial actions, gather further information from the device, and other actions. The triggered job runs once per affected device, when NetMRI detects an issue or policy rule violation on that device. If the condition clears, and subsequently occurs again, the triggered job runs again.

You can run a job immediately, automatically pre-approved, or schedule the job for up to a week in the future, in a pending-approval or pre-approved state.

To create a triggered job, do the following:

  1. Click the New button at the top right of the page. The Triggered Job Wizard opens.
  2. In the Select Trigger screen, specify a policy rule or issue that will trigger the job by selecting a Trigger Source.
  3. In the left panel, select the policy rule or issue in the list. Details appear in the right panel, where you verify that you have selected the correct policy rule or issue. Enter all or part of the name at the top of the panel.
  4. Click Next.
  5. In the Trigger Filters screen, specify the conditions that must be satisfied for the job to run:
    In the Device Groups list, click, CTRL+click or SHIFT+click to select the group(s) that can trigger the job. In the Active Time Window list, select the time period during which the job will respond to triggers.
    In the Severity list (available only if the Trigger Source is Issue), select the level of event to be reported. Issues are raised at one of three severity levels - this filter represents which severity levels will trigger the event for the given issue.
  6. Click Next. The Define Job screen appears.
    Specify the action to be taken in response to the trigger:
  7. If you don't want the job to run, uncheck the Enabled option. (You might want to prevent a job from running during maintenance or when manually changing settings.)
    In the lower left panel, select the script or job template to be run.
  8. Specify a Job Name: Select Use Script Name, or select Use Custom Name and enter a name in the field. To Edit an existing Triggered Job: Enter all or part of the name near the top of the panel.
    In the lower right panel, review the script details. If the script provides user-definable variables, fill in or set them as needed (be sure to scroll down to see all variables).
  9. Click Next. The Schedule Job Execution screen appears.
  10. To specify when the job should be run, select either Trigger Action: Run Job Immediately (if selected, then click Next) or Schedule Job.
  11. In the To Run At list, select a time to run the job.
  12. In the The Following list, select a day where to run the job.
  13. Click Pre-Approved if the job will run based on your approval. Uncheck Pre-Approved if the job must be approved by another user before execution.
  14. Click Next.
  15. In the Review and Save screen, review the job specifications.
  16. To make changes, click < Previous to return to the page(s) needing to be revised.
  17. If the job specifications are correct, click Save. The job is listed in the Triggered Jobs tab.

Once a job is listed in the table, check its Status, Last Run and Result in the Scheduled Jobs tab.
To view job details: Click Edit. The Triggered Job Wizard appears, listing a summary of the job. From this point, click Edit if you wish to edit the job by choosing new trigger sources and other settings.
To delete the job from execution: Click Delete, then confirm the deletion.