For example a single method call can send a command, collect the output and write it to a file named after the device. This module handles discovering the remote device OS, its prompt and hostname, and the interactions with the device. These various scripts are included in the repository so that someone can quickly download them and get started, but majority of the work has been put into building the securecrt_tools module which is designed to handle all of the low-level interactions with SecureCRT and make it as easy as possible to write new scripts. There are versions of this script for working with a single device or a list of devices. ![]() Search devices for specific existing IP helper/DHCP relay addresses and add new relays (optionally remove old) on any interface where the current relays are found.Capture the interface stats from all interfaces on a device into a spreadsheet to more quickly see which ports have errors, high rates of traffic, etc.This script uses the ARP table created above as input if you want MAC to IP mappings shown in the output. Create a spreadsheet that maps out every device on the switch, including interface description, MAC Address, MAC Vendor and IP address.There is also version that will build a single large ARP table from multiple devices (For when HSRP priorities are split across 2 cores, or multiple VRFs route different VLANs upstream). Write the ARP table for a device into a spreadsheet (CSV) file, either for manual lookups or to be leveraged by other scripts (see below).This script is useful either as a validate tool after routing changes (see a summary of route behavior before and after the change), or to help with discovery of new devices (There are 4000 routes in the table, but are there 3 or 30 exits that packets can take?) Summarize the route table of a device to see a list of all next-hops found in the route table and how many routes from which routing protocols are sending routes to each next-hop.Creation of SecureCRT sessions from the CDP information of a device, to quickly build your collection of sessions in SecureCRT's session manager.Write the detailed CDP neighbor information into a spreadsheet (CSV format) for easier viewing and re-use of the data.date, etc.) for a list of devices provided to the script in CSV format. Capture device inventory data (code version, model number, serial number, mfg.There are some different versions depending on if you want a single output or multiple outputs and from one or multiple devices. Save command outputs from devices into files that are automatically named with the hostname of the device (from the prompt) and a time/date stamp.While the documentation has a detailed list of every script in this collection and the specifics on how they work, below is a summarized list of the kinds of things these scripts will do. Please see the 2017 branch if you want the original class-based scripts use the JSON based settings files.Please see the Pre-2017 branch if you need to access the original versions (1.0) that were all function based.If you are looking for previous versions of the scripts, they can be found in the branches below: In addition there are methods for pushing configuration changes to devices that were not available previously. In addition to the new format for the settings, the newer version of these scripts now have support for initiating connections via Telnet and SSH to remote devices, as well as connecting via a jump/bastion host. There is no code to migrate your settings from the old JSON format to the INI format, so please check your settings and remove the old JSON files In addition instead of each script uses indivdiual settings having its own JSON file, now that settings are saved in the common "settings.ini" file under a separate heading for that script. The settings files for these scripts have been changed from using JSON files to the Python built-in ConfigParse module. Important Note For Users of Older Versions No ETA at this time due to time constraints. ![]() There is an open issue tracking the problem, but I'll need to find some time to try out the newer version and discover what has changed and how to fix it. ![]() It seems these scripts do not work with SecureCRT 9.x at this time. SecureCRT 9.x has changed they way that the python interpreter is bundled with the software. If you find that a script won't work on your machine, please post an issue to let us know! Note on SecureCRT 9.x ![]() These scripts should work on any version of SecureCRT that supports python. This repository contains a collection of SecureCRT scripts that automate various tasks, primarily around interacting with Cisco routers and switches.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |