Commit Template Modifications
For supported software information, click here.
When you change the configuration in an existing configuration or service template, you must commit the changes so that the new configuration is deployed on the associated devices. You can commit all changes, and you can merge the changes into the existing configuration.
In Releases 22.1.1 and later, you can apply an individual template to a device instead of applying all the latest templates to the device. You can also disassociate an individual template from a device while retaining the remaining templates.
Commit a Modified Template
To commit a modified template:
- In Director view, select the Administration tab in the top menu bar.
- Select Appliances in the left menu bar.
- In the Status column in the main pane, check whether Reachability is green and Service is Up. If the device is not reachable or if the service is not up, the commit may not succeed.
- Click Commit Template.
- In the Commit Template To Select Devices window, select which templates to commit to which devices. You can select either All the Associated Templates or Only Selected Templates. Some of the fields will change depending on which option you select. The All the Associated Templates option is selected by default.
- To commit all the templates associated with the device, click All the Associated Templates, and then enter information for the following fields.
Field Description All the Associated Templates (For Releases 22.1.1 and later.) Click to commit all the templates for the device or devices. Organization (Required)
Select the organization to which to apply the template. Select Devices By (Required)
Select where to commit the changes, and then select the template, device group, or device:
- Device Group
- Search for a Device
- Service Template
- Template
Select Option Select an option:
- If you Select Devices By Device Group, select a device group to which to apply the revised template.
- If you Search for a Device, select one or more devices to which to apply the revised template.
- If you Select Devices By Service Template, select a configured service template on which to apply the revised template.
- If you Select Devices By Template, select a configured configuration template on which to apply the revised template.
Automerge Click to merge the configuration changes with the existing configuration in the template. Overwrite Click to overwrite the existing configuration with the changes. Reboot After Commit Click to reboot the Versa Operating SystemTM (VOSTM) devices after template is committed. Fetch Devices Click to display a list of the VOS devices associated with the selected organization. You can select individual devices to which to apply the template. - To commit all selected templates associated with the device, click Only Selected Templates, and then enter information for the following fields.
Field Description Only Selected Templates (For Releases 22.1.1 and later.) Click, and then select individual templates to associate with or disassociate from the device.
Associate Templates (For Releases 22.1.1 and later.) Select to associate one or more individual templates with a device. Disassociate Templates (For Releases 22.1.1 and later.) Select to disassociate one or more individual templates from a device. Organization (Required)
Select the organization to which to apply the template. Select Devices By (Required)
Select where to commit the changes, and then select the template, device group, or device:
- Service template
- Template (configuration template). Note that this option is available only if you are associating templates.
Select Option Select an option:
- If you Select Devices By Service Template, select one or more configured service templates on which to apply the revised template to use.
- If you Select Devices By Template, select one or more configured configuration templates on which to apply the revised template. Note that this option is available only if you are associating templates.
Reboot After Commit Click to reboot the Versa Operating SystemTM (VOSTM) devices after template is committed. Add Filter Click to filter based on the options you chose in the Select Option field. The selected options display under Selected Templates. Fetch Devices Not applicable.
- To commit all the templates associated with the device, click All the Associated Templates, and then enter information for the following fields.
- In the Differences column, click the Eye icon to review the configuration changes. The Diff View popup window displays the differences between the existing configuration and the new configuration.
- Click Cancel to close the Diff View popup window.
- Click Review. The Commit Template to Devices Review window displays.
- Click Commit to commit the template changes.
- To schedule the commit for a later date or time, click Schedule & Commit. In the Schedule Your Commit popup window, set the schedule.
- Click OK.
Merge Templates
Normally, you create a baseline configuration for VOS devices by creating a template using the screens on the Versa Director Workflows tab. You can change the configuration in a template from the Workflows tab, the Configuration tab, or the CLI. After you make the changes, you merge them back into the template that you created with Workflows. There are two ways to merge the changes back into the template:
- Automatic merge—Merge all configuration changes into the template. This is the default merging style. It is recommended that you use automatic merging to minimize the time required to change device configurations and to reduce the chances for configuration errors.
- Manual merge—You individually select which configuration changes to incorporate into the template. Use this merging style when you want to selectively add configuration changes to a template. However, you must ensure that you apply the changes correctly so that you do not introduce errors into the device configurations.
Automatically Merge Configuration Changes
To automatically merge configuration changes into a template that you created with Workflows:
- Log in to Versa Director.
- Make the desired configuration changes to the template from the Director Workflows or Director Configuration tab, or from the CLI.
- Deploy the configuration changes. You can do this in one of the following ways:
- In the Configuration or Workflows tab, click Commit Template.
- In the Versa Director Workflow, click Redeploy. The Diff and Merge popup displays. The left side of the popup shows the current configuration, and the right side shows the newly generated configuration.
- In the merge-mode box, ensure that the Automerged (Recommended) option is selected. This is the default option.
- Click Deploy to push the configuration changes to all VOS devices that are using the template.
Manually Merge Configuration Changes
To manually merge configuration changes into a template that you created with Workflows:
- Log in to Versa Director.
- Make the desired configuration changes to the template on the Versa Director Workflows tab, on the Versa Director Configuration tab, or from the CLI.
- Deploy the configuration changes. You can do this in one of the following ways:
- In the Configuration or Workflows tab, click Commit Template.
- In the Versa Director Workflow, click Redeploy. The Diff and Merge popup window displays. The left side of the popup window shows the current configuration, and the right side shows the newly generated configuration.
- In the merge-mode box, select Manual.
- Review the configuration changes.
- To add a configuration block to the template, select the configuration block in the Current box and then click the right arrow to move the configuration block to the Newly Generated box. You can also drag the configuration block to the right, to the Newly Generated box.
- Click Deploy to push the configuration changes to all VOS devices that are using the template.
Encrypt Sensitive Information
For Releases 21.1.1 and later.
Director nodes encrypt all sensitive information in configurations before pushing them to VOS devices. This sensitive information includes IPsec preshared keys (PSKs), the LDAP server profile bind password, the OSPF authentication key (for the simple password type), and the passwords for local database users and user-authentication users. This sensitive information is also encrypted on the Director node itself.
To disable encryption of sensitive information, issue the set system settings encrypt-data enable-encrypting-sensitive-info false CLI command.
To enable encryption of sensitive information, issue the set system settings encrypt-data enable-encrypting-sensitive-info true CLI command.
Supported Software Information
Releases 20.2 and later support all content described in this article, except:
- Release 21.1.1 supports encryption of sensitive information.
- Release 22.1.1 supports applying and disassociated individual templates to a device.