Golden Configuration fundamentals and workflow

This document covers the following topics:

About Golden Configuration

Cisco Crosswork Network Controller Golden Configuration is designed to streamline the management and deployment of network device configurations.

Crosswork Network Controller Golden Configuration combines the simplicity and power of Jinja templating with the robust orchestration capabilities of Cisco Network Services Orchestrator (NSO). This enables network operators to define desired device configurations, tokenize them with variables using Jinja templating, and apply these configurations across diverse network devices through an intuitive graphical user interface.

The core purpose of Golden Configuration is to simplify and automate configuration changes while ensuring configuration compliance across the network. It empowers operators to leverage their existing native configuration knowledge without requiring deep NSO coding or service package development expertise.

Golden Configuration represents an evolution from earlier script-based tools to a fully integrated GUI application, incorporating default Methods of Procedure (MOPs) that automate configuration workflows, ensuring structured, auditable, and reliable deployments.

Golden Configuration benefits

  • Simplified configuration management: Users can define configurations in any of native, C-Style, J-Style, XML, and JSON formats, enhanced with Jinja templating for dynamic variables.

  • User-friendly UI: The Crosswork Network Controller UI provides an intuitive experience for creating, managing, and applying templates, replacing manual CLI-based processes and external template editors.

  • Enhanced automation and control:

    • Supports global variables for network-wide settings and template/job-level variables for device-specific customization.

    • Dry run previews allow users to validate the exact configuration before deployment, reducing errors.

    • Multi-device and multi-template job application with scheduling and monitoring capabilities.

    • MOP-based structured and auditable deployments ensure operational rigor. These MOPs are reusable and customizable workflows that serve as the middleware’s command structure, enabling seamless orchestration and automation of configuration tasks. You can monitor job execution status and results in real time through the UI, enhancing operational visibility and control.

    • Supports the use of JSON formatted variables combined with Jinja2 templating to handle these intricate scenarios.

  • Robust conformance and remediation:

    • Periodic or on-demand conformance checks verify device configurations against assigned Golden Templates.

    • Detailed difference reports highlight discrepancies between desired and actual configurations.

    • One-click automated remediation restores compliance by reapplying the Golden Template.

  • Scalability and flexibility: Supports multi-vendor environments and complex configurations, including advanced Jinja logic such as loops and conditionals, and JSON-formatted variables for intricate topologies.

  • Reduced learning curve: By focusing on native configuration formats and an intuitive UI, Golden Configuration lowers the barrier for you to utilize NSO’s automation capabilities effectively. This approach eliminates the need to learn complex YANG models or develop NSO service packages.

Leverage NSO capabilities and Jinja templating

Golden Configuration uses Jinja templating to tokenize native device configurations with variables, enabling dynamic and reusable configuration templates. These templates are managed and applied through NSO’s orchestration engine, which handle the deployment, compliance checking, and remediation workflows.

This integration allows Golden Configuration to automate complex configuration tasks reliably and at scale, seamlessly interfacing with the Crosswork Network Controller UI for ease of use.

Golden Configuration also supports advanced Jinja templating features including loops, conditionals, and JSON-formatted variables, allowing for the creation of highly flexible and scalable configuration templates suitable for complex network topologies.

Golden Configuration includes default MOPs that automate deployment and remediation workflows, providing structured, auditable, and repeatable processes that were not available in traditional device templates or service packages.

Golden Configuration template types

A Golden Configuration template is a native configuration snippet designed to be reusable and dynamic through the use of tokenized variables. These templates allow network operators to define device configurations in their original, human-readable formats while enabling automation and consistency across multiple devices.

Templates leverage Jinja syntax to represent dynamic elements within the configuration. Variables are enclosed in double curly braces, for example, {{ variable_name }}, which allows the template to be parameterized and customized per device or deployment scenario. This approach simplifies configuration management by separating static configuration elements from those that vary.

Golden Configuration supports a variety of native configuration styles to accommodate diverse network environments and device types. These include native, C-style, J-style, XML and JSON based on NSO support.

By supporting native configuration format, Golden Configuration templates provide flexibility and allow operators to work with the configuration style they are most familiar with, reducing the learning curve and increasing adoption.

In summary, Golden Configuration templates are powerful, native-format configuration snippets enhanced with Jinja templating to enable dynamic, scalable, and automated network device configuration management.

Code Golden Configuration templates in any of these formats, known as Config types (short for configuration types):

  • Native: The Native configuration type is for configurations coded using CLI commands that are native to devices. Here is a sample configuration for a Cisco IOS XR device. 

    router bgp {{ as }}
 bgp router-id 150.1.1.1
 address-family vpnv4 unicast
 exit
 vrf testNewXR   
  rd auto
  address-family ipv4 unicast
   redistribute connected
   redistribute static
  exit
  neighbor 7.7.7.1
   remote-as 400
   bfd minimum-interval 200
   bfd multiplier 16  
   ebgp-multihop 5
   update-source GigabitEthernet0/0/1/1
   address-family ipv4 unicast
    route-policy PASS_ALL in
    route-policy PASS_ALL out
    allowas-in 5
    site-of-origin 10:4
    as-override
   exit
  exit
 exit
    In this sample of a tokenized config, as is a variable and its value must be defined by the user: 
    router bgp {{ as }}

Define global variables

Follow these steps to define a global variable.

Before you begin

You will want to decide on the name and the value you want to assign to the global variable before defining it. The variable name can have a maximum length of 64 characters. The first character must be an upper or lowercase letter, followed by any mix of upper and lower case letters, numbers, and underscores. The variable value can be a string of characters of any length.

Remember that the variable names service and device are reserved for internal use. Although you can refer to them and make use of them in your templates, you cannot redefine them.

Procedure

Step 1

From the main menu, select Device Management > Golden Config > Global variables.

Step 2

To add a new global variable: Click + Add Variable.

To edit a global variable: Find it in the table and click on its name in the Name column. Click Save when you are done editing the variable.

To delete a global variable: Find it in the table, click on the selection box next to its Status, then click Delete. Click Delete again to confirm.

Step 3

Complete the fields on the Add Variable window as follows:

Name: Enter the name of the global variable.

Value: Enter the value of the global variable.

Step 4

Click Add.

Managing Golden Configuration templates

Golden Configuration is designed to simplify and automate how you manage network device configurations. You can find, edit, clone, and delete configuration templates directly within the UI to maintain accurate and consistent device configurations.

This approach reduces the complexity traditionally involved in configuration management by removing the need for deep Cisco Network Service Orchestrator (NSO) coding or service package development expertise.

With Golden Configuration, you can create and manage configuration templates that apply consistently across multiple devices. This process helps ensure configuration compliance and reduces human error.

Golden Configuration uses NSO capabilities and integrates with Methods of Procedure (MOPs) to automate configuration deployment and remediation.

These tasks enable you to quickly locate the right templates, make necessary adjustments, replicate templates for similar use cases, and remove outdated or unnecessary templates.

Create a new Golden Configuration template

If you are new to using the Golden Config solution, you will probably want to start by copying a configuration you have already prepared offline and pasting it into a new configuration template you create, as explained below.

Use these steps to create a new configuration template from an existing configuration you have already prepared offline.

Procedure

Step 1

From the main menu, select Device Management > Golden Config > Templates.

Step 2

Click + Create template.

Step 3

Complete the fields on the New Template window as follows:

In this field...

Enter or select

Template name *

The template name can have a maximum length of 64 characters. The first character must be an upper or lowercase letter, followed by any mix of upper and lower case letters, numbers, underscores, or hyphens.

Description

An explanation of the template's scope or purpose. The description can be a string of characters of any length.

Tag

One or more flexible, user-defined tags that will assist you and other users to categorize, search and filter your templates. You can create as many of these as you want, on the fly, by entering them in this field, separated by commas.

Mode

Select the way you want the template configuration to be applied to the device's existing configuration: Merge to merge the template with the existing configuration, Replace to replace the existing config.

Config type *

Select the type of template coding you will use: Native, C-style, J-Style, XML, or JSON. For more help, see Configuration types.

Vendor *

The name of the vendor for the devices that are the targets for the configuration template. Choices include: Cisco Systems, Juniper Networks, and others.

Software type *

The vendor operating system: IOS-XR, IOS-XE, or JUNOS.

Product series *

The vendor's name for the product series or family that includes the devices that are the target for the configuration template.

Step 4

The setting Audit as part of global schedule is on by default. If you want this template not to be audited, click the radio button to disable the setting.

Step 5

Copy and paste your configuration code into the new template, as follows:

  1. Copy your configuration code to the clipboard.

  2. In the Config template window on the right, click Config.

  3. Locate your cursor on line 1 in the edit window and right click to display the dropdown menu.

  4. From the dropdown menu, select Paste to paste your configuration code into the Config template edit window.

Step 6

When you are finished, click Create to save the new configuration template.

Step 7

Select the Variables tab in the New Template window to define the template variables.

  1. Add values for any variables that are referenced in your configuration.

  2. Enter the variable name and its corresponding value in the provided fields.

  3. You may add multiple variables to match your template requirements.

Step 8

Select Dry run.

Note

 

For detailed steps, see the Perform a template dry run section.

Find configuration templates

Learn how to locate configuration templates. View key details in the template inventory to manage templates effectively.

Follow these steps to find an existing configuration template.

Procedure

Step 1

From the main menu, select Device Management > Golden Config > Templates.

Step 2

Step 3

You can use one of these methods to find the template you want:

  • Scroll through the Templates table to locate the template name you want.

  • Begin entering characters in the Search field to display only templates with names or tags that match your search.

  • Select a value in the Vendor, Software type, Product series, or Tags filter fields to display only templates that match your selected values.

  • Select the Filters icon to set values in filter fields. Select Apply to display only templates with matching values. Select Reset all to remove the filters.

  • Select any table column heading such as Name, Description, or Vendor to sort the template listings alphabetically.

  • If there is more than one page of listings, use the Rows per page and page number buttons at the bottom of the table to go to the page that contains the template you want.

  • Select the Table settings icon in the heading row at the far right to change how the table is displayed and to adjust the number of columns shown.

Step 4

When you find the template, select its Name to view detailed information.

Step 5

After reviewing, select Cancel or the Templates link to return to the inventory view. The template inventory provides a consolidated overview of all configuration templates:

  • The number of devices each template is applied to.

  • Conformance details, such as counts of non-conformant devices.

  • Supported vendors and product series.

Within the detailed view, you can see these details:

  • Full template definition.

  • A list of devices associated with the template.

  • Status of each device, highlighting any deviations.

You can also navigate to the associated service for any device to perform further actions.

Edit configuration templates

Edit an existing configuration template using these steps.

Procedure

Step 1

From the main menu, select Device Management > Golden Config > Templates.

Step 2

Use the methods in Find configuration templates to find the template you want to edit.

Step 3

Click the template's Name to select it. Alternatively, to the right of the template's Name, under the Table settings icon in the last column, click the More icon (…) and select Edit.

The Settings window with the template content is displayed.

Step 4

Edit the template as needed. The Template name cannot be changed.

Step 5

When finished, click Save changes.

Clone configuration templates

Use these steps to clone an existing configuration template.

Most fields, including some that are required, are empty in the cloned template. The application assigns a new, editable name. It retains your configuration area code.

Procedure

Step 1

From the main menu, select Device Management > Golden Config > Templates.

Step 2

Refer to the task Find configuration templates to locate the template you want to copy.

Step 3

Locate the More icon (…) to the right of the template's Name, under the Table settings icon in the last column.

Click the More icon, then select Clone.

You see the Clone template window with part of your cloned template.

Step 4

Edit the template content. Change the Template name.

Step 5

When you are finished, click Save changes.

Delete configuration templates

Follow these steps to edit an existing configuration template.

Procedure

Step 1

From the main menu, select Device Management > Golden Config > Templates.

Step 2

Use the methods in Find configuration templates to find the template you want to delete.

Step 3

Click on the template's Name to select it. Or: To the right of the template's Name, under the Table settings icon in the last column, click the More icon (…) and select Delete.

The Settings window displays the template content.

Step 4

Click Save changes.

Perform a template dry run

Conducting a dry run allows you to validate a configuration template before applying it to devices. You can view what the configuration would do without applying the changes. You can copy and save the results and compare them with the results from other dry runs.

Procedure

Step 1

From the main menu, select Device Management > Golden Config > Templates.

Step 2

Use the methods in Find configuration templates to find the template for which you want to conduct a dry run.

Step 3

Click Name to select the template.

The Settings window displays the template content.

Step 4

Click Dry Run.

Note

 

You will see Set variables fields only if there are variables declared in the configuration template code. You will not see these fields if the template contains no variables.

Step 5

Complete the fields as follows:

  1. Select device *

    The device against which you want to perform the dry run.

  2. Set variables

    One or more fields under the Set variables heading will prompt you for values for any variables declared in the template code.

    You must supply values for any template variables declared in the template code.

    Values for any global variables declared in the template code will appear with the previously determined global variable value filled in. You can override this by entering a new value.

    Values for the reserved variable names device and service, if declared in the template code, are supplied by to the device node you select and the service you are configuring. You cannot override these values.

    For more help, see Configuration variables.

Step 6

When you are finished, click Dry Run to conduct the dry run.

Crosswork Network Controller performs the dry run of the configuration and displays the results in a Dry Run Result window.

Crosswork Workflow Manager performs the dry run of the configuration and displays the results in a Dry Run Result window.

Step 7

Scroll the Dry Run Result window to view the results of the configuration. Click Copy to save the result to the clipboard. When you are finished, click Done to exit the Dry Run Result window and return to the template window.

Apply a Golden Configuration template

Use the Golden Configuration application to automate the deployment of native configurations across your network.

When you apply a Golden Configuration template, a job is created that pushes the tokenized configurations to one or more target devices. During this process, you can override variable values, perform a final dry run, and select specific Methods of Procedure (MOPs) to govern the deployment.

Before you begin

Onboard the target devices before you create and validate the configuration templates.

  • Create and validate the configuration templates you intend to use.

Follow these steps to apply a Golden Configuration template:

Procedure

Step 1

From the main menu, choose Device Management > Golden Config > Templates.

You can also start the process by clicking Run golden config from the main list, or by selecting Apply template in the detail view of a specific template.

Step 2

In the Select Devices section, select the boxes for the target devices you want to configure, then select Next.

Step 3

In the Select Templates section, select one or more templates to apply to the chosen devices.

Step 4

In the Set Variables section, review and provide values for the variables:

  • Global Variables: These are pre-filled with values defined at the global level. You can override them for this specific job.

  • Template Variables: These are pre-filled with values defined within the template. You can override them here.

  • Job Variables: Enter values for any variables that require device-specific information (for example, interface names).

Values set at this job level have the highest priority and override template and global settings.

Note

 

Review these rules to understand how the system resolves overlapping values and handles specific internal variables before you proceed to the dry run.

  • Variable Execution Priority: Variable values set at the job level have the highest priority and override values set at the template or global level. Similarly, values set at the template level override values set at the global level. This hierarchy ensures that you can meet requirements you set for individual jobs and templates without affecting broader configurations.

  • Reserved Variable Names: The variable names service and device are reserved for internal use. These two variables are injected into configuration templates so users can use them, typically to access network service and device nodes and information under these nodes in their configurations.

Step 5

Select Dry Run to see the combined configuration rendered for the selected devices and templates.

Note

 

This optional step allows you to verify the final syntax before deployment.

Step 6

Select Next to open the MOP and Execution Settings window.

Step 7

Complete these fields:

  1. Select MOP: Select the appropriate MOP (for example, Cisco MOP or Juniper MOP).

  2. Job name: Enter a unique name for the configuration job.

  3. Job tags (optional): Enter tags to help categorize and search for the job later.

  4. Parallel execution: Enter the number of devices to be executed in parallel.

  5. Acceptable failures: Enter a number for the allowed failures to apply Golden Configuration template.

  6. Execution time: Select Run Now or Schedule for Later to define when the job starts.

Step 8

Select Next to view the Summary page.

Review the target devices, selected templates, and variable overrides.

Step 9

Select Run Job to submit the configuration task.

What to do next

Select the Jobs tab within the template or the main Automation Jobs page to track execution status and view the final device configuration.

Monitor Golden Configuration job results

After applying a Golden Configuration template to your devices, you can monitor the deployment progress and verify the final rendered configuration. This process ensures that all variables were correctly resolved and the configuration was successfully pushed to the target devices.

Before you begin

You must have initiated an Apply Golden Configuration job.

Procedure

Step 1

From the main menu, select Device Management > Golden Config > Templates.

Step 2

In the Templates table, click the Name of the template used in the deployment job.

Step 3

Click the Jobs tab. This tab displays a list of all automation jobs associated with the template, including the number of devices targeted.

Step 4

Click the link for the specific automation job you want to monitor. The job progress page opens.

Step 5

Track the real-time status of the job. The page provides details on scheduling, parallel execution, and acceptable failures defined during job creation.

  • Parallel execution: View the progress of multiple devices being configured simultaneously based on the Max Parallel settings.

  • Acceptable failures: Monitor if the job continues to run despite individual device failures, provided the number of failures stays within the acceptable failures threshold defined during job creation.

Step 6

To verify the actual configuration applied to a device, open the Jobs tab for the template or the device list. Then, select View final device config.

Step 7

Review the native configuration displayed in the window.

The window displays the final configuration pushed to the device after the system rendered Jinja variables.

What to do next

After a successful job, devices may initially be marked as Non-conformant by default. The system automatically runs a conformance report in the background to update the compliance status.

You can monitor the progress and final status of this conformance run in System Tasks.

Once complete, the compliance status will reflect the current state of the devices without any additional action required.

Run a conformance report

A conformance report allows you to verify that the configuration that is currently running on a network device remains in sync with the assigned Golden Configuration template.

This process identifies changes made outside the designated parameters or modifications performed outside of Crosswork Network Controller. The system also provides a detailed discrepancy report.

Conformance reports help you maintain network compliance by checking device configurations against Golden Configuration templates on a recurring basis or when needed.

If a device is non-conformant, the system highlights the specific lines of code that differ so you can quickly fix the issue.

After you make configuration changes or perform troubleshooting, verify compliance for specific templates and devices by using this targeted, on-demand procedure.

Before you begin

  • Create a Golden Configuration template and apply it to at least one device.

Procedure

Step 1

From the main menu, select Device Management > Golden Config > Templates.

Step 2

In the Templates table, select the Name of the template you want to verify.

Step 3

Select the Devices tab to see the list of devices associated with this template.

Step 4

To initiate a check, select Run Conformance.

Step 5

Monitor the Status column for these results:

  • Conformant: The device configuration matches the template.

  • Non-conformant: Discrepancies were detected between the device and the template.

Step 6

If a device is non-conformant, select View non-conformant details (or the status link) to view the exact configuration differences and the NSO service path where the change occurred.

Use this procedure to schedule recurring, wide-scale audits. These audits ensure long-term configuration integrity for your network and run automatically, so you do not need to take additional action.

If a device is non-conformant, the system highlights the specific lines of code that differ. This enables rapid remediation.

  1. From the main menu, select Device Management > Golden Config > Templates.

  2. To determine whether a template is included in automated, recurring runs, check the Audit setting:

    • Select the … icon next to a template and select Edit.

    • Make sure the Audit as part of global schedule toggle is enabled.

    • Select Save changes.

  3. Select Run.

  4. On the Template list page, review the number of devices that are conformant or non-conformant for each template. To see detailed conformance information for individual devices, select the template name, then select the Device tab.

What to do next

If a device is identified as non-conformant, restore the intended configuration by completing the steps in Remediate non-conformant devices.

Remediate non-conformant devices

When a device's configuration deviates from the assigned Golden Configuration template, often due to out-of-bound changes made directly on the device CLI, the device is flagged as non-conformant.

Remediation is the process of identifying these discrepancies and reapplying the template to restore the device to its golden state.

In addition, Golden Configuration provides a robust mechanism to detect and correct configuration drift. When a conformance check identifies a discrepancy between the intended golden state and the actual device state, you can review the changes before taking corrective action.

Before you begin

  • A Golden Configuration template must be applied to the device.

  • A conformance report must have been run (either on-demand or using the daily 12 AM schedule) to identify the non-conformant status.

Use these steps to remediate out-of-bound changes and restore device compliance.

Procedure

Step 1

From the main menu, select Device Management > Golden Config > Templates.

Step 2

Select the Name of the template associated with the non-conformant device to open the detailed template view.

Step 3

Select on the Devices tab to view the list of associated devices and their current conformance status.

Step 4

Locate the device marked as non-conformant and select View non-conformant details.

This opens a diff view that highlights the exact configuration lines that have changed and identifies the specific NSO service path where the deviation occurred.

Step 5

Select Reapply template.

This initiates a job to overwrite the out-of-bound changes by pushing the original template configuration back to the device.

Step 6

Optionally, run a new conformance report for the template to verify that the device status has returned to Conformant.

Use this procedure to identify out-of-bound modifications made to a device that was not orchestrated through NSO.

Out-of-bound changes are modifications made to a device without orchestration through NSO. During a conformance run, the system compares the rendered Jinja template against the device's running configuration. If they do not match, the device is marked as non-conformant.

  1. From the main menu, select Device Management > Golden Config > Templates.

  2. Select the template you wish to audit.

    The inventory view displays a count of conformant and non-conformant devices in the Conformance column.

  3. In the template's detailed view, navigate to the Devices list.

  4. For any device showing a non-conformant status, select the option to View non-conformant details.

    The UI highlights the specific discrepancies. Review these to ensure that reapplying the template will not overwrite a critical manual change.

  5. To restore compliance, select Reapply template.

Using JSON variables

Standard string variables are sufficient for simple configuration changes. However, complex network tasks—such as configuring OSPF topologies or managing multiple interfaces—require more advanced logic.

Golden Configuration supports the use of JSON formatted variables combined with Jinja2 templating to handle these intricate scenarios.

Why use JSON variables?

JSON variables allow you to pass structured data into a template. When combined with Jinja2 logic, you can:

  • Use loops: Iterate over a list of items. For example, configure ten interfaces with a single template.

  • Apply conditionals: Use if/else statements to apply configuration only when specific criteria are met.

  • Define hierarchies: Group related data together, such as IP addresses, descriptions, and costs for a specific routing protocol.

Example: OSPF interface configuration

In this example, a JSON variable is used to define a list of interfaces, and a Jinja for loop iterates through that list to generate the native CLI. 

router ospf 1
{% for intf in interfaces %}
  interface {{ intf.name }}
    ip address {{ intf.ip }} {{ intf.mask }}
    cost {{ intf.cost }}
{% endfor %}

Corresponding JSON variable value

{
  "interfaces": [
    {
      "name": "GigabitEthernet0/0/0/1",
      "ip": "10.0.0.1",
      "mask": "255.255.255.0",
      "cost": "10"
    },
    {
      "name": "GigabitEthernet0/0/0/2",
      "ip": "10.0.0.2",
      "mask": "255.255.255.0",
      "cost": "5"
    }
  ]
}

Before you begin

Complete these steps to create and validate a Golden Configuration template with JSON variables and advanced Jinja logic.

Procedure

Step 1

Create a new template and set the Config type to match your device.

Step 2

Enter your configuration code using Jinja2 loop or conditional syntax.

Step 3

Define a variable as a JSON type in Set Variables.

Step 4

Run a Dry Run to confirm that the JSON data produces the expected native configuration for the selected device.

Deleting Golden Configurations

You can remove Golden Configurations by deleting the applied configurations from specific devices, or by performing a force delete on the template, which removes its associated configuration from all devices in the network.

Before you begin

To begin the process of deleting Golden Configurations, complete these steps:

Procedure

Step 1

From the main menu, select Device Management > Golden Config > Templates.

Step 2

Verify the deletion by accessing the device console or check the Jobs tab to confirm that the configuration has been successfully removed from the target hardware.

Step 3

Use these steps to delete an applied configuration from a specific device:

  1. Select the Name of the template to open the detailed view.

  2. Select the Devices tab to see the list of devices where this template is applied.

  3. Select the target devices from the list.

  4. Select Delete from device.

The system initiates a delete action in Network Services Orchestrator (NSO) that removes the configuration snippet associated with the template from the device.

Step 4

Use these steps to force delete a template and all associated configurations:

  1. In the Templates inventory list, locate the template you wish to remove.

  2. Select the More icon (…) and select Delete.

  3. In the confirmation dialog, select the force delete option.

  4. Select Confirm.

When you perform a force delete, the system removes the template definition from Crosswork Network Controller and automatically deletes the associated configuration from every device where it was previously applied.

Customize MOPs

Golden Configuration leverages Methods of Procedure (MOPs) to provide a structured, repeatable, and auditable framework for deploying network configurations.

The system replaces manual, ad hoc changes with a standardized middleware structure. It does this by ensuring that every configuration job follows a sequenced set of phases, including pre-check, configuration, and post-check stages.

Default MOPs

Crosswork Network Controller includes pre-loaded MOPs specifically designed for Cisco and Juniper environments.

These default MOPs are optimized to handle the Apply Config stage. This stage renders Jinja2 templates and pushes the native configuration to target devices.

MOP-based execution

Every Golden Configuration job is associated with a specific MOP selected during the job submission process.

This selection governs the sequence of actions the system performs to ensure the device is properly prepared for the update and remains functional after the configuration is applied.

MOP flexibility and customization

While the default MOPs provide a robust starting point, the system allows for the inclusion of additional operational steps.

You can customize the workflow by adding specific actions to the pre-configuration or post-configuration phases. This flexibility allows you to tailor the deployment process to meet specific organizational requirements or complex network scenarios.

For detailed instructions on how to modify existing MOPs or create new, specialized workflows, see the Cisco Crosswork Network Controller 7.2 MOP User Guide.