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.

Restarting a device

A job with the Reboot action restarts the device causing the device to load the Startup configuration into the Running configuration. For devices supporting only a Running configuration, at times a reboot is required for certain configuration changes to become active.

BMC Network Automation performs a configuration snapshot after the reboot. If a change is detected after the reboot, a historical configuration is created. You can select to make the current configurations trusted after the reboot.

For more generic information about job creation, see Creating a job.

To run a Reboot action

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

  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 Reboot 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:



    Mark as Trusted

    (Optional) Mark the current Running and Startup configurations as trusted following the reboot action.

    Use Auxiliary Interface

    (Optional) 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. In the Reboot Options field, select one of the following options:


    This field is ignored for devices with only a Running configuration.

    • Commit changes prior to reboot (Default): Save unsaved changes to a device, if the device prompts how to handle unsaved changes during the reboot process. This is usually equivalent to performing a Commit, saving the current Running configuration to the Startup configuration and making those saved settings active after the reboot.
    • Ignore uncommitted changes and reboot: Discard the unsaved changes to a device, if the device prompts how to handle unsaved changes during the reboot process.
  5. Click OK to add the action to the job.
Was this page helpful? Yes No Submitting... Thank you