Starting version 8.9.03, BMC Network Automation is renamed to TrueSight Network Automation. This space contains information about BMC Network Automation 8.9.02 and previous versions. For TrueSight Network Automation 8.9.03 and later releases, see the TrueSight Network Automation documentation.

Committing a running configuration

A job with a Commit action is applicable to devices supporting a Startup configuration. The Commit action copies the device's Running configuration to the Startup configuration (for example, write memory). A commit ensures that the Startup configuration matches the Running configuration should the device restart.

To run a Commit action

  1. On the Add Job page, select Add Action > Span Actions > Commit.

  2. Enter information in the following fields:




    (Optional) Annotation assigned to the configurations created by the action.

    Network Span

    Select a realm, group, multiple devices, or a single device for the Commit action. When the Network Span is Realm or Group, you can use Filter Devices to select which devices to include in the action.

    When the action is triggered in an event-based Policy, additional options include: Same as Triggering Realm, Same as Triggering Group, Same as Triggering Device.

  3. Select any of the following options, as relevant:

    Check box


    Mark as Trusted

    When a new configuration file is detected, mark this new version as Trusted.

    Commit All Security Contexts When Applicable

    When a device that is being committed supports multiple security contexts, select this option to commit all contexts. If this option is not selected, only the security context referred to by the device is committed.

    Use Auxiliary Interface

    When the selected network span is a device, this option selects the auxiliary interface for connecting to the device. When not checked or when the span is not a device, the primary interface is used.

  4. Click OK to add the action to the job.
Was this page helpful? Yes No Submitting... Thank you