Skip to main content

Automation Tools for Cisco SD-WAN Powered by Viptela

Project description

published

Sastre - Automation Tools for Cisco SD-WAN Powered by Viptela

Sastre provides functions to assist with managing configuration elements in Cisco vManage, including backup, restore and delete tasks.

Introduction

Sastre has a set of base parameters as well as task-specific arguments.

The command line is structured as follows:

sdwan <base parameters> <task> <task-specific parameters>

Currently available tasks:

  • Backup: Save vManage configuration items to a local backup.
  • Restore: Restore configuration items from a local backup to vManage.
  • Delete: Delete configuration items on vManage.
  • List: List items configured on vManage or from a local backup. Display as table or export as csv file.
  • Show-template: Show details about device templates on vManage or from a local backup. Display as table or export as csv file.

Notes:

  • Either 'sdwan' or 'sastre' can be used as the main command.
  • The command line described above, and in all examples that follow, assumes Sastre was installed from PyPI, via PIP.
  • If Sastre was download from GitHub, then 'sdwan.py' or 'sastre.py' should used instead. Please check the installation section for more details.

Base parameters

% sdwan -h
usage: sdwan [-h] [-a <vmanage-ip>] [-u <user>] [-p <password>] [--port <port>] [--timeout <timeout>] [--verbose] [--version] <task> ...

Sastre - Automation Tools for Cisco SD-WAN Powered by Viptela

positional arguments:
  <task>                task to be performed (backup, restore, delete, list, show-template)
  <arguments>           task parameters, if any

optional arguments:
  -h, --help            show this help message and exit
  -a <vmanage-ip>, --address <vmanage-ip>
                        vManage IP address, can also be provided via VMANAGE_IP environment variable
  -u <user>, --user <user>
                        username, can also be provided via VMANAGE_USER environment variable
  -p <password>, --password <password>
                        password, can also be provided via VMANAGE_PASSWORD environment variable
  --port <port>         vManage TCP port number (default is 8443)
  --timeout <timeout>   REST API timeout (default is 300s)
  --verbose             increase output verbosity
  --version             show program's version number and exit

vManage address (-a), username (-u) and password (-p) can also be provided via environment variables:

  • VMANAGE_IP
  • VMANAGE_USER
  • VMANAGE_PASSWORD

A good approach to reduce the number of parameters that need to be provided at execution is to create rc text files exporting those environment variables for a particular vManage. This is demonstrated in the Getting Started section below.

Task-specific parameters

Task-specific parameters and options are defined after the task is provided. Each task has its own set of parameters.

% sdwan backup -h
usage: sdwan backup [-h] [--workdir <directory>] [--regex <regex>] <tag> [<tag> ...]

Sastre - Automation Tools for Cisco SD-WAN Powered by Viptela

Backup task:

positional arguments:
  <tag>                 One or more tags for selecting items to be backed up. Multiple tags should be separated by space. Available tags: all, policy_definition,
                        policy_list, policy_security, policy_vedge, policy_vsmart, template_device, template_feature. Special tag 'all' selects all items.

optional arguments:
  -h, --help            show this help message and exit
  --workdir <directory>
                        Directory used to save the backup (default will be "backup_10.85.136.253_20191207").
  --regex <regex>       Regular expression matching item names to be backed up, within selected tags.

Important concepts:

  • vManage URL: Built from the provided vManage IP address and TCP port (default 8443). All operations target this vManage.
  • Workdir: Defines the location (in the local machine) where vManage data files are located. By default it follows the format "backup_<vmanage-ip>_<yyyymmdd>". The --workdir parameter can be used to specify a different location. Workdir is under a 'data' directory. This 'data' directory is relative to the directory where Sastre is run.
  • Tag: vManage configuration items are grouped by tags, such as policy_apply, policy_definition, policy_list, template_device, etc. The special tag 'all' is used to refer to all configuration elements. Depending on the task, one or more tags can be specified in order to select groups of configuration elements.

Getting Started

Create a directory to serve as root for backup files, log files and rc files:

% mkdir sastre
% cd sastre

When Sastre is executed, data/ and logs/ directories are created as needed to store backup files and application logs. These are created under the directory where Sastre is run.

Create an rc-example.sh file to include vManage details and source that file:

% cat <<EOF > rc-example.sh
 export VMANAGE_IP='10.85.136.253'
 export VMANAGE_USER='admin'
 export VMANAGE_PASSWORD='admin'
EOF
% source rc-example.sh

Test vManage credentials by running a simple query listing configured device templates:

% sdwan list template_device
+-----------------+--------------------------------------+-----------------+-----------------+
| Name            | ID                                   | Tag             | Type            |
+-----------------+--------------------------------------+-----------------+-----------------+
| DC_ADVANCED     | bf322748-8dfd-4cb0-a9e4-5d758be239a0 | template_device | device template |
| DC_BASIC        | 09c02518-9557-4ae2-9031-7e6b3e7323fc | template_device | device template |
| VSMART_v1       | 15c1962f-740e-4b89-a269-69f2cbfba296 | template_device | device template |
| BRANCH_ADVANCED | ad449106-7ed6-442f-9ba8-820612b85981 | template_device | device template |
| BRANCH_BASIC    | cc2f7a24-4c93-49ed-8e6b-1c107797ba95 | template_device | device template |
+-----------------+--------------------------------------+-----------------+-----------------+

Any vManage parameters not specified via environment variables need to be provided via command line. For instance, the password can be left off the rc file and then provided when Sastre is executed:

% sdwan -p admin list template_device

Perform a backup:

% sdwan --verbose backup all
INFO: Starting backup: vManage URL: "https://10.85.136.253:8443" > Local workdir: "backup_10.85.136.253_20191206"
INFO: Saved device template index
INFO: Done device template DC_ADVANCED
INFO: Done device template DC_BASIC
INFO: Done device template DC_BASIC attached devices
INFO: Done device template DC_BASIC values
<snip>
INFO: Done SLA-class list Realtime_Full_Mesh
INFO: Task completed successfully

Note that '--verbose' was specified so that progress information is displayed. Without this option, only warning-level messages and above are displayed.

The backup is saved under data/backup_10.85.136.253_20191206:

% ls
data		logs		rc-example.sh
% ls data
backup_10.85.136.253_20191206

Additional Examples

Customizing backup destination:

% sdwan --verbose backup all --workdir "my_custom_directory"
INFO: Starting backup: vManage URL: "https://10.85.136.253:8443" > Local workdir: "my_custom_directory"
INFO: Saved device template index
INFO: Done device template DC_ADVANCED
INFO: Done device template DC_BASIC
<snip>
INFO: Done SLA-class list Realtime_Full_Mesh
INFO: Task completed successfully

Restoring from backup:

% sdwan --verbose restore all        
INFO: Starting restore: Local workdir: "backup_10.85.136.253_20191206" > vManage URL: "https://10.85.136.253:8443"
INFO: Loading existing items from target vManage
INFO: Identifying items to be pushed
INFO: Inspecting template_device items
INFO: Inspecting template_feature items
INFO: Inspecting policy_vsmart items
INFO: Inspecting policy_vedge items
INFO: Inspecting policy_security items
INFO: Inspecting policy_definition items
INFO: Inspecting policy_list items
INFO: Pushing items to vManage
INFO: Done: Create SLA-class list Best_Effort
INFO: Done: Create SLA-class list Realtime_Full_Mesh
INFO: Done: Create site list All_Sites
INFO: Done: Create class list af2
<snip>
INFO: Done: Create device template BRANCH_ADVANCED
INFO: Done: Create device template BRANCH_BASIC
INFO: Task completed successfully

Restoring from a backup in a different directory than the default:

% sdwan --verbose restore all --workdir my_custom_directory
INFO: Starting restore: Local workdir: "my_custom_directory" > vManage URL: "https://10.85.136.253:8443"
INFO: Loading existing items from target vManage
INFO: Identifying items to be pushed
INFO: Inspecting template_device items
INFO: Inspecting template_feature items
<snip>
INFO: Task completed successfully

Restoring with template attachments and policy activation:

% sdwan --verbose restore all --attach
INFO: Starting restore: Local workdir: "backup_10.85.136.253_20191206" > vManage URL: "https://10.85.136.253:8443"
INFO: Loading existing items from target vManage
<snip>
INFO: Attaching WAN Edge templates
INFO: Waiting...
INFO: Waiting...
INFO: Waiting...
INFO: Waiting...
INFO: Completed DC_BASIC,BRANCH_BASIC
INFO: Completed attaching WAN Edge templates
INFO: Attaching vSmart template
INFO: Waiting...
INFO: Waiting...
INFO: Completed VSMART_v1
INFO: Completed attaching vSmart template
INFO: Activating vSmart policy
INFO: Waiting...
INFO: Waiting...
INFO: Completed Central_policy_v1
INFO: Completed activating vSmart policy
INFO: Task completed successfully

Overwriting items with the --force option:

  • By default, when an item from backup has the same name as an existing item in vManage, it will be skipped by restore. Leaving the existing one intact.
  • When an item, say a device template, is modified in vManage. Performing a restore from a backup taken before the modification will skip that item.
  • With the --force option, items with the same name are updated with the info found in the backup.
  • Sastre only updates the item when its contents differ from what is in vManage.
  • If the item is associated with attached templates or activated policies, all necessary re-attach/re-activate actions are automatically performed.
  • Currently, the --force option does not apply to changes in template values.

Example:

% sdwan --verbose restore all --workdir state_b --force
INFO: Starting restore: Local workdir: "state_b" > vManage URL: "https://10.85.136.253:8443"
INFO: Loading existing items from target vManage
INFO: Identifying items to be pushed
INFO: Inspecting template_device items
INFO: Inspecting template_feature items
INFO: Inspecting policy_vsmart items
INFO: Inspecting policy_vedge items
INFO: Inspecting policy_security items
INFO: Inspecting policy_definition items
INFO: Inspecting policy_list items
INFO: Pushing items to vManage
INFO: Done: Create community list LOCAL_DC_PREFIXES
INFO: Done: Create community list REMAINING_PREFIXES
INFO: Updating SLA-class list Best_Effort requires reattach of affected templates
INFO: Reattaching templates
INFO: Waiting...
INFO: Waiting...
INFO: Completed VSMART_v1
INFO: Completed reattaching templates
INFO: Done: Update SLA-class list Best_Effort
<snip>
INFO: Done: Update device template DC_BASIC
INFO: Task completed successfully

Deleting vManage items:

Dry-run, just list without deleting items matching the specified tag and regular expression:

% sdwan --verbose delete all --regex "^DC"  --dryrun
INFO: Starting delete, DRY-RUN mode: vManage URL: "https://10.85.136.253:8443"
INFO: Inspecting template_device items
INFO: DRY-RUN: Delete device template DC_BASIC
INFO: DRY-RUN: Delete device template DC_ADVANCED
INFO: Inspecting template_feature items
INFO: Inspecting policy_vsmart items
INFO: Inspecting policy_vedge items
INFO: Inspecting policy_security items
INFO: Inspecting policy_definition items
INFO: Inspecting policy_list items
INFO: Task completed successfully

Deleting items:

% sdwan --verbose delete all --regex "^DC"
INFO: Starting delete: vManage URL: "https://10.85.136.253:8443"
INFO: Inspecting template_device items
INFO: Done: Delete device template DC_BASIC
INFO: Done: Delete device template DC_ADVANCED
INFO: Inspecting template_feature items
INFO: Inspecting policy_vsmart items
INFO: Inspecting policy_vedge items
INFO: Inspecting policy_security items
INFO: Inspecting policy_definition items
INFO: Inspecting policy_list items
INFO: Task completed successfully

Deleting with detach:

When vSmart policies are activated and device templates are attached the associated items cannot be deleted. The --detach option performs the necessary template detach and vSmart policy deactivate before proceeding with the delete.

% sdwan --verbose delete all --detach
INFO: Starting delete: vManage URL: "https://10.85.136.253:8443"
INFO: Detaching WAN Edge templates
INFO: Waiting...
INFO: Completed BRANCH_BASIC
INFO: Completed DC_BASIC
INFO: Completed detaching WAN Edge templates
INFO: Deactivating vSmart policy
INFO: Waiting...
INFO: Completed Central_policy_v1
INFO: Completed deactivating vSmart policy
INFO: Detaching vSmart template
INFO: Waiting...
INFO: Completed VSMART_v1
INFO: Completed detaching vSmart template
INFO: Inspecting template_device items
INFO: Done: Delete device template vManage_template
<snip>
INFO: Task completed successfully

Listing items from vManage or from a backup:

The list task can be used to list items from a target vManage, or a backup directory, matching a criteria of item tag(s) and regular expression.

List device templates and feature templates from target vManage:

% sdwan --verbose list template_device template_feature
INFO: Starting list: vManage URL: "https://10.85.136.253:8443"
INFO: List criteria matched 45 items
+---------------------------+--------------------------------------+------------------+------------------+
| Name                      | ID                                   | Tag              | Type             |
+---------------------------+--------------------------------------+------------------+------------------+
| BRANCH_ADVANCED           | 6ece1f27-fbfa-4730-9a8f-b61bfd380047 | template_device  | device template  |
| VSMART_v1                 | ba623cf6-5d2c-4676-a763-11b9cf866074 | template_device  | device template  |
| BRANCH_BASIC              | 5e362c85-8251-428a-b650-d364f8e15a22 | template_device  | device template  |
<snip>
| vSmart_VPN0_Interface_v1  | be09349e-308e-4ca5-a306-fb7bcd5bcb28 | template_feature | feature template |
+---------------------------+--------------------------------------+------------------+------------------+
INFO: Task completed successfully

List all items from target vManage with name starting with 'DC':

% sdwan --verbose list all --regex "^DC"
INFO: Starting list: vManage URL: "https://10.85.136.253:8443"
INFO: List criteria matched 2 items
+-------------+--------------------------------------+-----------------+-----------------+
| Name        | ID                                   | Tag             | Type            |
+-------------+--------------------------------------+-----------------+-----------------+
| DC_BASIC    | 2ba8c66a-eadd-4a63-97c9-50d58a43b6b5 | template_device | device template |
| DC_ADVANCED | b042ed29-3875-4118-b800-a0b00542b58e | template_device | device template |
+-------------+--------------------------------------+-----------------+-----------------+
INFO: Task completed successfully

List all items from backup directory with name starting with 'DC':

% sdwan --verbose list all --regex "^DC" --workdir backup_10.85.136.253_20191206
INFO: Starting list: Local workdir: "backup_10.85.136.253_20191206"
INFO: List criteria matched 2 items
+-------------+--------------------------------------+-----------------+-----------------+
| Name        | ID                                   | Tag             | Type            |
+-------------+--------------------------------------+-----------------+-----------------+
| DC_ADVANCED | bf322748-8dfd-4cb0-a9e4-5d758be239a0 | template_device | device template |
| DC_BASIC    | 09c02518-9557-4ae2-9031-7e6b3e7323fc | template_device | device template |
+-------------+--------------------------------------+-----------------+-----------------+
INFO: Task completed successfully

Similar to the list task, show tasks can be used to show items from a target vManage, or a backup. With show tasks, additional details about the selected items are displayed. The item id, name or a regular expression can be used to identify which item(s) to display.

% sdwan show-template values --name DC_BASIC
Device template DC_BASIC, values for vedge-dc1:
+-----------------------------------+--------------------------------------+--------------------------------------------------------------------+
| Name                              | Value                                | Variable                                                           |
+-----------------------------------+--------------------------------------+--------------------------------------------------------------------+
| Status                            | complete                             | csv-status                                                         |
| Chassis Number                    | b693be59-c03f-62d0-f9a4-2675374536b8 | csv-deviceId                                                       |
| System IP                         | 10.255.101.1                         | csv-deviceIP                                                       |
| Hostname                          | vedge-dc1                            | csv-host-name                                                      |
| Hostname(system_host_name)        | vedge-dc1                            | //system/host-name                                                 |
| System IP(system_system_ip)       | 10.255.101.1                         | //system/system-ip                                                 |
| Site ID(system_site_id)           | 101                                  | //system/site-id                                                   |
| IPv4 Address(vpn_if_ipv4_address) | 10.101.1.4/24                        | /10/ge0/2/interface/ip/address                                     |
| IPv4 Address(vpn_if_ipv4_address) | 5.254.4.110/24                       | /20/ge0/3/interface/ip/address                                     |
| AS Number(bgp_as_num)             | 65001                                | /20//router/bgp/as-num                                             |
| Address(bgp_neighbor_address)     | 5.254.4.1                            | /20//router/bgp/neighbor/bgp_neighbor_address/address              |
| Remote AS(bgp_neighbor_remote_as) | 65111                                | /20//router/bgp/neighbor/bgp_neighbor_address/remote-as            |
| Preference(transport1_preference) | 100                                  | /0/ge0/0/interface/tunnel-interface/encapsulation/ipsec/preference |
+-----------------------------------+--------------------------------------+--------------------------------------------------------------------+

Device template DC_BASIC, values for vedge-dc2:
+-----------------------------------+--------------------------------------+--------------------------------------------------------------------+
| Name                              | Value                                | Variable                                                           |
+-----------------------------------+--------------------------------------+--------------------------------------------------------------------+
| Status                            | complete                             | csv-status                                                         |
| Chassis Number                    | 0dd49ace-f6de-ce86-5d73-ca74d6db1747 | csv-deviceId                                                       |
| System IP                         | 10.255.102.1                         | csv-deviceIP                                                       |
| Hostname                          | vedge-dc2                            | csv-host-name                                                      |
| Hostname(system_host_name)        | vedge-dc2                            | //system/host-name                                                 |
| System IP(system_system_ip)       | 10.255.102.1                         | //system/system-ip                                                 |
| Site ID(system_site_id)           | 102                                  | //system/site-id                                                   |
| IPv4 Address(vpn_if_ipv4_address) | 10.102.1.3/24                        | /10/ge0/2/interface/ip/address                                     |
| IPv4 Address(vpn_if_ipv4_address) | 5.254.5.105/24                       | /20/ge0/3/interface/ip/address                                     |
| AS Number(bgp_as_num)             | 65002                                | /20//router/bgp/as-num                                             |
| Address(bgp_neighbor_address)     | 5.254.5.1                            | /20//router/bgp/neighbor/bgp_neighbor_address/address              |
| Remote AS(bgp_neighbor_remote_as) | 65222                                | /20//router/bgp/neighbor/bgp_neighbor_address/remote-as            |
| Preference(transport1_preference) | 0                                    | /0/ge0/0/interface/tunnel-interface/encapsulation/ipsec/preference |
+-----------------------------------+--------------------------------------+--------------------------------------------------------------------+

Notes

Regular Expressions

It is recommended to always use double quotes when specifying a regular expression to --regex option:

sdwan --verbose restore all --regex "VPN1"

This is to prevent the shell from interpreting special characters that could be part of the pattern provided.

Matching done by --regex is un-anchored. That is, unless anchor marks are provided (e.g. ^ or $), the specified pattern matches if present anywhere in the string. In other words, this is a search function.

The regular expression syntax supported is described in https://docs.python.org/3/library/re.html

Logs

Sastre logs messages to the terminal and to log files (under the logs directory).

Debug-level and higher severity messages are always saved to the log files.

The --verbose flag controls the severity of messages printed to the terminal. If --verbose is not specified, only warning-level and higher messages are logged. When --verbose is specified, informational-level and higher messages are printed.

Restore behavior

By default, restore will skip items with the same name. If an existing item in vManage has the same name as an item in the backup this item is skipped from restore.

Any references/dependencies on that item are properly updated. For instance, if a feature template is not pushed to vManage because an item with the same name is already present, device templates being pushed will now point to the feature template which was already in vManage.

Adding the --force option to restore modifies this behavior. In this case Sastre will update existing items containing the same name as in the backup, but only if their content is different.

When an existing vManage item is modified, device templates may need to be reattached or vSmart policies may need to be re-activated. This is handled by Sastre as follows:

  • Updating items associated with an active vSmart policy may require this policy to be re-activated. In this case, Sastre will request the policy reactivate automatically.
  • On updates to a master template (e.g. device template) containing attached devices, Sastre will re-attach this device template using attachment values (variables) from the backup to feed the attach request.
  • On Updates to a child template (e.g. feature template) associated with a master template containing attached devices, Sastre will re-attach the affected master template(s). In this case, Sastre will use the existing values in vManage to feed the attach request.

The implication is that if modified child templates (e.g. feature template) define new variables, re-attaching the master template will fail because not all variables will have values assigned. In this case, the recommended procedure is to detach the master template (i.e. change device to CLI mode in vManage), re-run “restore --force", then re-attach the device-template from vManage, where one would have a chance to supply any missing variable values.

Installing

Sastre requires Python 3.6 or newer. This can be verified by pasting the following to a terminal window:

% python3 -c "import sys;assert sys.version_info>(3,6)" && echo "ALL GOOD"

If 'ALL GOOD' is printed it means Python requirements are met. If not, download and install the latest 3.x version at Python.org (https://www.python.org/downloads/).

The recommended way to install Sastre is via pip. For development purposes, Sastre can be installed from the github repository. Both methods are described in this section.

PIP install (recommended)

To install Sastre:

% python3 -m pip install --upgrade cisco-sdwan

Verify that Sastre can run:

% sdwan --version

Github install

Install required Python packages:

% python3 -m pip install --upgrade requests

Clone from the github repository:

% git clone https://github.com/reismarcelo/sastre

Move to the clone directory:

% cd sastre

Verify that Sastre can run:

% python3 sdwan.py --version

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for cisco-sdwan, version 0.34
Filename, size File type Python version Upload date Hashes
Filename, size cisco_sdwan-0.34-py3-none-any.whl (36.6 kB) File type Wheel Python version py3 Upload date Hashes View hashes
Filename, size cisco-sdwan-0.34.tar.gz (39.7 kB) File type Source Python version None Upload date Hashes View hashes

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page