Example: Cisco Save Config to File
Updated 05 Jun, 2020
Ever wanted to quickly save a copy of your Cisco router's running-config or startup-config to a file on your local machine so that you could have something to compare against or restore to? If so, this script is an example you can start with.
Comments within the script file itself provide explanation of how to set it up and what to expect, but if you're looking for a quick way to get started with this example:
On Windows, when you press the button you've mapped and the script completes, the saved file will be selected in a Windows Explorer file view.
Note: The example is written in Python code so as to be able to run in SecureCRT on Windows, Linux, or Mac OS X platforms.
Note: The same script will save either the running-config or the startup-config, depending on argument you supply when configuring the script to be launched.
Note: The default behavior is to store resulting config files in your "Documents" folder, in a sub-folder named "Config-Saves".
Examples Uses of Arguments:
Save the startup-config to a file, prompting for filename using default template values. SecureCRT continues running after the script completes.
Update (jdev: 05 Jun, 2020): Merged two example scripts into a single script. This updated version supports Nexus/Catalyst devices, and provides for unattended operation as well as other options as documented above. Note: the Unattended version is no longer being updated.
Update (jdev: 14 Sep, 2017): Added variant of the example script to be useful for unattended backups. See example "Cisco-SaveDeviceConfigToFile-Unattended(NoLongerReceivingUpdates).py.txt"
Update (jdev: 06 Apr, 2018): Updated script to allow for additional argument(s) to 'sh run' to be specified in the button bar configuration. Note: These changes were not made to the 'Unattended' script example.
Update (jdev: 27 Jun, 2017): Use 'more system:running-config' form of the command instead of 'show running-config' for ASA devices so that the resulting output isn't masked (thanks to mike1572 in forum thread 12738 for the tip.).
Update (jdev: 07 Sep, 2016): Updated script to account for other shell/environment differences on ASA devices (use 'term pager 0', and other minor mods). Script now verified working on a Cisco 881W, a 2900 router, a 2960 switch, and an ASA5510 (thanks to forum user mike1572 for assistance).
Update (jdev: 29 Aug, 2016): Updated script to account for shell prompts from ASA devices that have trailing spaces; also account for 'sh term' output that might be longer than one page of data (handle the --more-- prompts if they occur in this scenario).
Update (jdev: 11 Apr, 2016):Updated script to allow/detect hostnames that have digits and dots in them.
YouTube Channel: https://www.youtube.com/vandykesoftware
Last edited by jdev; 06-05-2020 at 05:33 PM. Reason: Updated example to allow for additional arguments (sh run all)
|Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)|
|Display Modes||Rate This Thread|