So are you getting an error or something occurring in CatTools when sending this command then?
Is it a 'Did not receive echo of [command]' error per chance?
Thanks for your quick reply.
This is what i get in my emailed error report
2012-11-27 18:30:13 devicename001 Did not receive echo of copy system:/running-config ftp://ftpuser0:firstname.lastname@example.org/devicename001 command
2012-11-27 18:30:13 devicename001 Aborting command entry due to error
(in my command script there is a %ctDeviceName instead of the string devicename01, what you see here is the expanded string)
In the captured data folder we see:
copy system:/running-config ftp://ftpuser0:email@example.com
Note that the line is chopped up in the .202 ip address octet
I created a support ticket for this issue. In the mean time i will try to reduce the length of the string that is sent to the device.
This turned out to be an issue on the ws5100 device. In the telnet character echo the device itself returned a <cr><cr><lf> on the 80th position, making the cattools engine mismatching the send string and the echoed string.
There was a "terminal width" cli command that defines this point, so i included "terminal width 120" as command before the actual command.