#Ssh copy config from cisco swtich how to

Since trace options can contain sensitive information, feel free to send it as an attachment via e-mail to Please reference 'Attn Brenda - Forum Thread #5775' in the subject line. Once the problem occurs, please right-click inside the terminal window and choose 'Select All', then right-click again and choose 'Copy' to transfer the information to the Windows clipboard.ДЇinally, open a text editor like 'Notepad', paste the information from the Windows clipboard into the editor program, and save it as a text file. With trace options enabled, you will notice debugging information displayed in the terminal window that isn't normally there by default when SecureCRT is attempting to establish a connection, and at certain times throughout the lifetime of the connection. 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.

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.ДЇirst, open SecureCRT's main 'File' pull-down menu and select 'Trace Options'. 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.

#Ssh copy config from cisco swtich how to

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? I would not even want to hazard a guess as to the issue without logging information.