Localized CLI Policy

The following steps are involved in the conversion and export of Localized CLI policy configuration to a vManage or as a Sastre archive in the form of vManage’s UI Builder based policies:

  1. Upload
  2. Convert
  3. Export

Upload

The user initially uploads a configuration file of Localized CLI policy that they want to convert and export to a vManage or as a Sastre archive in the form of vManage’s UI Builder based policies. The configuration file is parsed and validated by the SD-WAN Conversion Tool to ensure it conforms with the structure and configuration blocks of a Localized CLI policy. In case of any errors, the line numbers of the errors and the string containing the error messages are returned to the UI for the user to identify and fix the specific issues in the uploaded config.


Activity Window

The activity window for the Upload step allows the following two options to the user for uploading a Localized CLI policy configuration file:

  • Drag and drop
  • Manually browse for a file
_images/cli_policy_upload.png

Figure 1. Upload activity window

Upload Workflow

  1. The first step required by the user is to upload the Localized CLI policy configuration file which is to be converted and exported as vManage’s UI Builder based policies. The SD-WAN Conversion Tool supports two ways to upload the configuration file:
  • Drag and Drop: To upload a file, simply drag and drop it to the activity window. The name of the file will be displayed next to the browse icon, as shown in the figure below.
_images/localized_upload_aw2.png

Figure 2. Uploaded Localized CLI policy file

  • Manually Browse: To upload a file manually, click on the browse icon and browse the file in your computer’s directory.

Note

Currently, SD-WAN Conversion Tool supports text files with plain text or a config file without any extension.

  1. Click on Next to upload the file on SD-WAN Conversion Tool. A loading screen will appear as shown in the figure below.
_images/upload_loading_screen.png

Figure 3. Loading screen in Upload step

  1. Upon successfully uploading the file in SD-WAN Conversion Tool, the contents of the original file will be displayed in an on-screen editor.
_images/localized_cli_upload_successful.png

Figure 4. Upload successful

See also

In case of an error, refer to the Upload Error: Localized/Centralized CLI Workflow section in Appendix A.

Convert

The SD-WAN Conversion Tool converts the Localized policy CLI configuration to XML format using Cisco NSO NEDs. The converted configuration is then consumed by the feature template generator tool in the subsequent step.


Activity Window

This section gives the details of the available functionalities for the Convert step in the activity window. An example activity window for this step is shown in the figure below.

_images/localized_cli_conversion_successful.png

Figure 1. Conversion successful

Field Name Description
Converted File This is the configuration file that is generated in the conversion process based upon the Localized CLI policy configuration. The user can download this config file by clicking on download.
Non-editable Window It displays the contents of the converted policy config file. No changes can be made to the config file at this point.

Convert Workflow

Once the Localized CLI policy config file has been uploaded successfully, the next step is to convert this configuration to XML format.

  1. After the config file has been successfully uploaded, click on Next to proceed. A loading screen will appear on the application window that indicates the beginning of the conversion process.
_images/cli_policy_conversion_loader.png

Figure 2. Loading screen in Convert step

  1. Upon successfully converting the config file to XML format, the following screen will appear on the application window indicating a successful conversion process.
_images/localized_cli_conversion_successful.png

Figure 3. Conversion successful

See also

In case of an error, refer to the Conversion Error: Localized/Centralized CLI Workflow section in Appendix A.

Export

The SD-WAN Conversion Tool generates UI Builder based policies using the converted policy configuration. In case of vManage as a target, the generated policies are created in user-selected vManage for consumption from vManage UI. The credentials provided for vManage can be saved by the user for subsequent workflows in the future. In case of Sastre archive as a target, the tool creates a Sastre archive that contains these policies which can be downloaded from the tool’s UI.


Activity Window

This section gives the details of the available functionalities for Export step in the activity window. An example activity window for this step is shown in the figure below.

_images/cli_policy_export_aw.png

Figure 1. Export activity window

Field Name Description
Target Type Type of target (Live vManage or Sastre archive) for the conversion.
vManage IP/New IP This is the IP or domain name of the running vManage to which the UI Builder based policies will be exported. The user can either enter a new IP or select from the list of previously saved vManage IPs from the drop-down menu. This field is disabled when Sastre archive is selected as the target type.
vManage Port This is the port of the vManage to which the UI Builder based policies will be exported. This field is disabled when Sastre archive is selected as the target type.
Username This is the username of the server on which vManage is running. It is disabled when Sastre archive is selected as the target type.
Password This is the password of the server on which vManage is running. It is disabled when Sastre archive is selected as the target type.

Export Workflow

Once a Localized CLI policy config file has been converted successfully, the next step is to export this config file.

  1. After the config file has been successfully converted to XML format, click on Next to proceed. The following screen will appear.
_images/cli_policy_export_aw.png

Figure 2. Export activity window

  1. Fill in the required fields by entering the relevant configuration details of the target to proceed with the export process. An example is shared in the figure below.
_images/cli_policy_filled_export_form.png

Figure 3. Export - filled fields

  1. Once the user has filled in the relevant fields, click on Next to proceed. A loading screen will appear on the application window that indicates the beginning of the export process in which the policies are exported to vManage or as a Sastre archive.
_images/cli_policy_export_loader.png

Figure 4. Loading screen in Export step

  1. After the policies have been successfully exported to vManage or as a Sastre archive, a screen will appear on the application window indicating a successful export process. The successful export screen would vary based on the target environment chosen earlier by the user. In case of Sastre target type, the user will be additionally shown a Sastre archive available for download. The screenshots for both scenarios are shown below.
_images/cli_policy_export_to_vManage.png

Figure 5. Export success - vManage

_images/cli_policy_export_as_sastre_archive.png

Figure 6. Export success - Sastre

See also

In case of an error, refer to the Export Error: Localized/Centralized CLI Workflow section in Appendix A.

On the export successful screen, the following two buttons are available to the user:

  • Convert: To perform another configuration conversion, click the Convert button. This will take the user back to the workflow selection screen.
  • History: To view the history of the configuration conversion workflows, click the History button. This will take the user to the History tab.