Space banner This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments.

Reconciling jobs

Note

Reconciling jobs is only available if your site has performed the Remedy integration procedure and the system parameter Enable Continuous Compliance for Network Administration is selected. See BMC-Continuous-Compliance-for-Network-Automation-solution.

To track changes that occured without prior approval in the Change Management system, a network engineer can reconcile latent changes.

This is how it works: A TrueSight Network Automation operator reconciles to Remedy network changes that were made by an engineer without any approvals. BMC Remedy creates a change ticket, fills in the Change ID and Task ID, and assigns a Change Timing value of Latent. The ticket does not require an approval in BMC Remedy and is immediately closed.

The following types of network changes made without prior approval can be reconciled:

  • Network Automation jobs that make changes to network devices (for example, Deploy to Active or Custom Action)
  • Changes made outside Network Automation but detected after the system makes a snapshot of the device
  • Changes made by using the Network Automation Automation SSH proxy

Eligibility for job reconciliation

Network Automation can reconcile jobs that meet all of the following requirements:

  • The job is in one of the completed states.
  • The job contains a deployment action (for example, Deploy to Stored, Commit) that caused or detected changes that are not documented in the Change Management system that involve one of the following:
    • At least one device change
    • A snapshot action that detected at least one device change
  • The job's ChangeID and TaskID fields are empty.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*