This repository contain samples of python scripts for "on-the-box" automation on IOS-XR routers. For scripts in other languages, please reach out to Cisco Systems Inc. or refer to the IOS-XR release manuals.
This feature was introduced in 7.3.2 IOS-XR release with limited support and additional functional support is added in subsequent releases as outlined in Cisco's release documentation.
For the rest of this document all references to scripts stand for python scripts.
There are 6 types of scripts:
An exec script is a script that gets triggered via a XR-CLI or a rpc over netconf. The script should be able to do whatever a management script can do from an external controller: connect to netconf/gNMI server on the same box, configure the box, query oper data, all model based, or XR-CLI driven (via Cisco libraries). To get the yang models please refer to : https://github.com/YangModels/yang/tree/master/vendor/cisco/xr.
A config script is used to enforce that the router configuration adheres to one or more customer-defined constraints. It is triggered automatically during configuration commits, and may either reject the commit (if invalid) or make changes to the contents of the commit (to make the resulting configuration valid). This ability to modify the contents of the commit can also be used to effectively automate repetitive configuration tasks, by making additional config changes that relate to the changes originally in the commit.
An EEM (Embedded Event Manager) script is triggered via a predefined set of events. Events supported are syslog, timer, traceback and telemetry events along with logical correlation of events, rate-limit, occurrence and period. Every eem script has a maxrun (default is 20 seconds and can be overridden via config). If the script doesn't terminate in "maxrun" time, the script is killed.
A process script will try to run forever as part of its design, and if it exits due to abnormal reasons (it crashes itself, some other processes kill it, etc.), XR will try to restart the process script. XR does the “life cycle management” of this script. It is different compared to exec/eem/config scripts that are transient in nature, start running due to an external trigger (a XR-CLI, an event or a commit action) and run for a short period of time and then cease running. If exec/eem/config scripts cease running as part of normal code flow, or due to a mishap (it crashes itself, or some other processes kills it), XR does not attempt to run it again without next external trigger.
A SNMP scripts is used to add support for an SNMP OID that is not supported by XR. It could also be used add support for a custom OID that will retrieve custom data. The idea is that when an external SNMP manager (outside box) query the box for an OID that is not supported by IOS-XR, and if a custom SNMP script is tied to that OID, then this script will be triggered to get the data for the OID. [suported release: IOS-XR 7.5.2 and later]
A pre-commit script is used to verify the target configuration (new configs added/modified/deleted) adheres to one or more customer-defined constraints when the config commit operation is performed. This differs from the config scripts in that the config scripts verifies the full running configs that would result from the commit but the pre-commit script verifies only the target configs. [supported release: IOS-XR 7.5.4 and later]
Clone git repo: https://github.com/CiscoDevNet/iosxr-ops.git
$ git clone https://github.com/CiscoDevNet/iosxr-ops.git
Copy python files to router's harddisk or a tftp location
Add script:
script add {config,eem,exec,process} {tftp:<path>,/harddisk:\<path>} <filename> [checksum <value>] [<filename> [checksum <value>] … ]
Two methods to add scripts to script management repository
Script add using http
Example:
script add exec http://10.85.67.235/scripts exec_upgrade_check.py checksum 023aa948b76e4177e9decf16911eff04896809f70deaaae9161d1dd2761da297
Copy script to harddisk using scp/copy CLI.
Script add from harddisk
Example:
Note:
-
For eem script checksum is configured with the event manager action and details can be found in the eem script docstrings.
-
For config script user must commit the configuration "configuration validation scripts" before configuring a specific script.
Checksum configuration is MANDATORY to run scripts
Syntax for exec, config and process script: config terminal script {config,exec,process} checksum {sha256 }
Example:
Check script status using the cli show script status. It should be "Ready"
RP/0/RP0/CPU0:ios#show script status
Tue Jun 21 16:35:14.877 UTC
======================================================================================================
Name | Type | Status | Last Action | Action Time
------------------------------------------------------------------------------------------------------
test_cli_config.py | exec | Ready | NEW | Tue Jun 21 16:32:57 2021
======================================================================================================
RP/0/RP0/CPU0:ios#
To see more details:
RP/0/RP0/CPU0:ios#show script status detail
Tue Jun 21 16:37:05.928 UTC
======================================================================================================
Name | Type | Status | Last Action | Action Time
------------------------------------------------------------------------------------------------------
test_cli_config.py | exec | Ready | NEW | Tue Jun 21 16:32:57 2021
------------------------------------------------------------------------------------------------------
Script Name : test_cli_config.py
Checksum : dcfad756c7d0e8a23782dc7a159179bb6226e1d4edd689f31457f405ff79b1a6
History:
--------
1. Action : NEW
Time : Tue Jun 21 16:32:57 2021
Checksum : dcfad756c7d0e8a23782dc7a159179bb6226e1d4edd689f31457f405ff79b1a6
Description : User action IN_CLOSE_WRITE
======================================================================================================
RP/0/RP0/CPU0:ios#
