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.

The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found. 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 Actions > Span Actions > Reboot.
  2. Enter information in the following fields:

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.

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

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.

  4. In the Reboot Options field, select one of the following options:

    Note

    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 Save to add the action to the job.

 

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