Deploying to the startup configuration

A job with the Deploy to Stored action copies a configuration to a device's Startup configuration. The Deploy to Stored action only applies to devices that support a Startup configuration and allow external systems to directly write to the Startup configuration.

You can deploy the device's Trusted Startup, or one of the device's Historical Startup, Target, or a Template to the device's Startup configuration. You can choose to reboot or to mark the restored configuration as Trusted during the deployment.

After the Deploy to Stored action, the device's Startup configuration is compared to its Trusted Startup configuration. Differences are reported as configuration discrepancies on the Dashboard and Discrepancy reports. If the Trusted Startup is Deployed to Stored, all discrepancies are cleared. If a change is detected after the Deploy to Stored action, a historical Startup configuration is created.

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

To run the Deploy to Stored action

1. On the Add Job page, select Add Action > Span Actions > Deploy to Stored.
   
   

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.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
   

3. In the Configuration field, select the configuration file to deploy to the device's Startup configuration.
   • Trusted Startup: Deploy the device's Trusted Startup configuration.
   • Target: Deploy the device's Target configuration.
   • Template: Deploy the selected Template. If the Template uses runtime parameters, click Params and assign values to the parameters.
   • Historical Running/Startup: Deploy a historical running or startup configuration.
   • Remediate With: Select one or more rule sets and rules to apply to the current Startup configuration. Under certain conditions, TrueSight Network Automation can make the configuration compliant based on the rule grammar and device type. TrueSight Network Automation creates a full configuration to deploy.
   • Remediate With All Assigned: Apply all assigned rule sets to the current Startup configuration, to correct rules actively in violation. Under certain conditions, TrueSight Network Automation can make the configuration compliant based on the rule grammar and device type. TrueSight Network Automation creates a full configuration to deploy.
   • Historical Trail(s) By Date: Deploy the selected historical trails to the devices in the selected network span, to their stored configuration. Use this option when several different trails should always be deployed together, when they have inter-related settings. Select one or more trails, other than the startup trail from the drop-down menu of deployable trails, then choose the configuration active at that date/time. Only those trails applicable to a particular device are deployed to that device.
   • Historical Trail: Deploy a selected configuration to the selected device. Select the trail to be deployed, then select the particular configuration.

4. 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.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
   

5. Click OK to add the action to the job.

Additional information regarding remediation

When you choose Remediate With All Assigned, a device must be actively in violation of a rule for the Deploy to Stored corrective actions of the rule to be executed. When you choose Remediate With, a device need not be in violation.

Only the Deploy to Stored corrective actions in a rule are executed by a Deploy to Stored span action. Any corrective action that is a Deploy to Active, Deploy OS Image, or custom action is ignored when running a Deploy to Stored span action.

The Deploy to Stored span action expands into one or more Deploy to Stored sub-actions, each of which performs one corrective action. For example, you might have selected to remediate some rules whose corrective action pushes a template and other rules that push a compliant configuration. These would be represented as two sub-actions under the top-level Deploy to Stored action. You can observe this action and sub-action hierarchy on the Preview Sub-Actions and Scripts page, the Job Details page, and the Job Summary report.