Archive FTP path '550 Filename invalid' error

[Brett Verney]

Hi all,

I am attempting to automatically backup a switch configuration to an Filezilla FTP server (Windows) using the the following configuration:

ip ftp source-interface Vlan900
ip ftp username configadmin
ip ftp password 7 xxxxxxxxx
!
archive
path ftp://192.168.201.50\HQ\$h\$h-$t.bak
write-memory
!
kron policy-list Config_Backup
cli write memory
cli archive config
!
kron occurrence Config_Backup at 4:00 Fri recurring
policy-list Config_Backup
!

However, both the debugs from the switch and Filezilla server show the following:

May 4 15:42:55.617: FTP: ---> USER configadmin
May 4 15:42:55.619: FTP: 331 Password required for configadmin
May 4 15:42:55.619: FTP: ---> ****
May 4 15:42:55.621: FTP: 230 Logged on
May 4 15:42:55.621: FTP: ---> TYPE I
May 4 15:42:55.623: FTP: 200 Type set to I
May 4 15:42:55.623: FTP: ---> PASV
May 4 15:42:55.626: FTP: 227 Entering Passive Mode (192,168,201,50,10,52)
May 4 15:42:55.628: FTP: ---> STOR HQ/hqtestswitch/hqtestswitch--May--4-15-36-06.753.bak-1
May 4 15:42:55.630: FTP: 550 Filename invalid
May 4 15:42:55.630: FTP: ---> QUIT
May 4 15:42:55.634: FTP: 221 Goodbye

I have also tried:

path ftp://192.168.201.50/HQ/$h/$h-$t.bak

Any ideas?

The switch is a Cat9200  running 17.03.03

Thanks!

-Brett

[marce1000]

       - Does it work with a manual ftp (tryout) . from the switch ?

 M.

[balaji.bandi]

path ftp://192.168.201.50\HQ\$h\$h-$t.bak

check the "/" correct format - try manually first before making use of archieve ?

Format :

• copy system:running-config ftp: [[[// [username [: password ]@ ]location]/ directory ]/ filename ] or

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9200/software/release/16-9/configuration_guide/sys_mgmt/b_169_sys_mgmt_9200_cg/managing_configuration_files.html#task_gzx_znx_m1b

[Brett Verney]

Hi all,

It seems that there are Windows Server permissions that could not be resolved (outside of my control). I was able to get the server admins to create the directories listed in my config on the server manually in the root directory (/HQ/ for example), and the backups from that point on worked fine.

Thanks for your help