If you open the 'File' pull down menu again you should see a checkmark next to 'Trace Options', indicating that troubleshooting output is now enabled. First, open SecureCRT's main 'File' pull-down menu and select 'Trace Options'.It's often useful to see 'trace options' output which provides debugging information that may help us better understand the problem that you're experiencing.

You might also want to view the entire thread, as the discussion was started with Cisco Config Backup automation as the initial topic. There is also an example script given here that reads from a host file, sends commands from a commands file and logs the results to individual files. I have attached an example script that allows for a command to be run in all connected tabs and the resulting data written to a file. However, it may be necessary to consider 'Plan B', logging the results of a 'show config' command. I will supply information at the end of this thread on how to enable 'Trace Options' to collect debugging information in SecureCRT. Do you have a debug log from the remote device? The only bit I am considering as perhaps the issue are the last two lines in the server.I would not even want to hazard a guess as to the issue without logging information. So the script is executing without error but is showing a failure in XMC: 22:07:22,300 DEBUG No match for success regex match: bytes copied: 22:07:22,300 DEBUG Looking for success regex match: bytes copied:

This works without issue as shown with the inventory script verbose logs enabled in XMC, below is an extract from the server.log file showing the commands where successful: BHR_N9K_2# copy running-config tĮnter vrf (If no input, current vrf 'default' is considered): Had to create a custom backup script for a Cisco Nexus as the boxed one was failing, the script looks like the following: - Use these scripts to manage Cisco devicesĭesc='Cisco Systems NEXSUS SSH/TFTP Scripts'

Download cisco backup config to tftp