Creating a generic job

This topics describes how to create a new generic job.

Warning

For jobs to function correctly, pop-up windows must not be blocked by your browser.

Note

For descriptions of the various job actions, see Understanding job actions.

To create a generic job

  1. Open the Add Job page by navigating to Network > Actions > Jobs.
    The Jobs page displays a list of defined jobs.
  2. Click Add.
    The Add Job page opens.
  3. In the Details tab, enter information in the following fields:

    Field

    Description

    Change ID

    (Optional) Track this span action to an external Change ID (for example, internal RFC process, Remedy, and so forth). To assist with change documentation, the Job Summary report summarizes the Job Details for each job referencing the same Change ID.

    Task ID

    (Optional) Track this span action to an external Task ID. To assist with change documentation, the Job Summary report summarizes the Job Details for each job referencing the same Task ID.

    Run At

    Select when to execute the job: Now or When Approved; or a future Date/Time.

    Send Email

    (Optional) Send email notifications to one or more recipients based on the selected job state changes (for example, when job completes with errors).

    Options

    (Optional) Select the following options as required:

    • On Error, Skip Remaining Actions: Skip remaining actions if a prior action fails (for example, when a change requires a sequence of ordered actions across different devices). By default, this option is disabled.
    • Include Debug Trace in Communication Transcripts: Enable logging of low-level debug statements in the job transcripts for all device command/response interactions included in this job. For security purposes, login passwords are {HIDDEN} in the transcript. When you select this option, additional lines starting with the prefix DEBUG: are added to the transcript output corresponding to the processing details of each <prompt>, <command>, and <response> XML tag from the device adapter being executed. Default value of this option depends on the current setting of the Include Debug Trace in Communication Transcripts system parameter.

      Recommendation:
      Include Debug Trace in Communication Transcript is a debug tool. BMC recommends that you enable it only when you are actively troubleshooting a device interaction issue. Leaving this setting on over long periods increases the size of the BMC Network Automation database hugely.
    Login User Name(Optional) If system parameters are configured to request device credentials at job creation time, enter the device login user name. The credentials are used for all devices in non-snapshot span actions. (Snapshot always uses the device security profile associated with the device.)
    Login Password(Optional) If system parameters are configured to request device credentials at job creation time, enter the device login password.
    Privileged User Name(Optional) If system parameters are configured to request device credentials at job creation time, enter the device privileged mode or enable user name.
    Privileged Password(Optional) If system parameters are configured to request device credentials at job creation time, enter the device privileged mode or enable password.

    User Assigned Dynamic Fields

    Additional Job fields, as configured by your administrator.

  4. If you want to add actions to the job, click  and select the type of action.


    Enter information for the action in the displayed fields and click OK to add the action. The job actions are displayed on the Actions tab:

  5. Click the  to view the proposed configuration changes for a span action. When the Deploy to Active or Deploy to Stored action enforces one or more rules, the Compliance Summary report is shown:


  6. Click  to display the change scripts built for the Deploy to Active action.
    SmartMerge generates the change script based on the current Running configuration. At execution time, the change script is generated once more based on the current Running configuration.
  7. When you are ready to save the job, you have two options:
    • Save as Draft: Job is saved but not submitted for approvals or scheduling. You can edit the Job multiple times when in Draft state.
    • Save and Submit: When Job approval is required, select the Job Approval Type. Even when Enable Job Approval is set under Admin > System Parameters (see Testing rules), Job approvals are not required for passive actions. These actions include Snapshot, Assign as Target, Log Event, Send Email, Send Trap, and Custom Actions configured for no approvals.
Was this page helpful? Yes No Submitting... Thank you

Comments